Microsoft Dynamics AX (Archived)

Vendor or Customer that is both TRADE and NON-Trade

(0) Share

Report

Posted on by Community Member

Hi good day,

We have a customer or vendor that are sometimes TRADE and NON-TRADE.

Example:

Name: Customer1

Cust Group: Trade

Posting Profile: Gen

During Entries:

We simply modify the posting profile from Gen to NTRADE so that GL Entries will be posted to Non-Trade..

But, how can we generate Customer Aging that will seperate the TRADE and NON-TRADE.?

Thanks.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (2)

Verified answer

Chandra Wijaya Seti... 1,145 on at

Like (1)

Report

This is bad setup in my opinion

You should create two cistomer instead belong to two different customer group

And you will have headache during payment too if user pay with trade to invoice with no trade posting profile

And aging is also another impact you must customize

And GL reconciliation is another problem

What is the reason you decide this way? Can u propose to change or split the customers in to two instead?

The problem with this is that you can't generate customerstatement for both customers but as long as u can convince customer the reason should be fine

I hope it makes sense

Was this reply helpful? Yes No
Weaveriski 23,618 Moderator on at

Like (0)

Report

How is a customer a "Trade" customer but in some circumstances not - what is making you change that order to non-trade?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Oh... Ok.. Thank you for your opinion I will change the setup.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

About creating separate Cust or Vendor for TRADE and NON-TRADE.

We have multiple company in AX and Company1 use Vendor1 as TRADE while Company2 use Vendor1.1 as Non-TRADE.

So, how can I limit that Copany1 that can only view Vendor1 and cannot view Vendor1.1

Our Vendor Table is part of Virtual Company.

Was this reply helpful? Yes No
Weaveriski 23,618 Moderator on at

Like (0)

Report

By making them virtual you are saying the record is the same. To make it different by company you have no choice but to create a second vendor across all companies. If you then want to hide it you need to start looking at the extended security and seeing if you can achieve what you want.

This is the downside of making records virtual rather than using the vendor copy to legal entity function. Virtual companies were not recommended by Microsoft in Ax2012. I have implemented them but you need to agree everything beforehand.

You might be better off staying with the manual change

Was this reply helpful? Yes No
Verified answer

Chandra Wijaya Seti... 1,145 on at

Like (1)

Report

Why do you need to limit those in the first place?

You can put distinct naming convention in vendor code let say NTxxxxx for non-trade TXXXxx for trade

If you want to validate user mistakenly user vendor code one think i can think of is create financial dimension trade and nontrade and assign this structure for customer/vendor control account and apply differently to each company.

1. Create financial dimension call vendorNature: value trade, non-trade.

2. Assign default dimension for vendor NT0001 to nontrade, assign vendor T0001 to Trade financial dimension.

3. Account structure for company1:

GL code 2001 AP Trade can only accept TRADE.

GL code 2002 AP Non trade can only accept TRADE financial dim

4. Account structure for company2

GL code 2001 AP Trade can only accept NON-TRADE financial dim

GL code 2002 AP NOn trade can only accept non0trade financial dim

You can try if company1 use non-trade vendor upon posting will fail because it dimension combination not valid.

For record level security approach as per Steven Weaver suggestion then you can refer to following:

technet.microsoft.com/.../aa570084.aspx

community.dynamics.com/.../ax-2012-and-the-use-of-the-new-extensible-data-security-framework

the later is recommended because the former will be not supported by next version, however the later approach need technical /development to build. First approach only need functional knowledge.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Greate thanks,.. I will try this and let the accounting team validate if this concept best fitted for them. I never thought of using findim for trade and non-trade.. Thank you so much.

Was this reply helpful? Yes No