A Company has 50 branches spread across different location. Each Branch is involved in purchase and sales activity. AP/AR is to be maintained separately for each branch. Inter Branch sales and purchases happens. Each branch follows a different Invoice Serial number. Stock transfer between branches has to be routed thru Financial General Ledger also. How to Configure this in Axapta Option A : Should the branches be defined as Dimensions. If yes then how to handle the Separate Invoice serial number Option B: Should 50 branch be treated a separate entity in Axapta and consolidation can be done at top level. If yes in the consolidation entity how to get the vendor wise, customer wise, itemwise aggregate totals.
quote:
A Company has 50 branches spread across different location. Each Branch is involved in purchase and sales activity. AP/AR is to be maintained separately for each branch. Inter Branch sales and purchases happens. Each branch follows a different Invoice Serial number. Stock transfer between branches has to be routed thru Financial General Ledger also. How to Configure this in Axapta Option A : Should the branches be defined as Dimensions. If yes then how to handle the Separate Invoice serial number A good one! We have 4 plants in the US producing the same stuff. We decided to use Item Dimension to differentiate them, they can now have their own costs. Some goods are going back and forth but they are not “sold” or “bought” so we have chosen this solution. We have the problem of not being able to give separate numbering sequences to different plants… that is a customization and not an easy one, we were told. But the Item Dimension works perfectly as an identifier of a plant. Some extra work with user defaults … is necessary to avoid errors in data entry (one user keying in items of the other plant). If your separate numbering sequence of invoicing is critical, you have no choice then go with Axapta companies, but creating 50 companies sounds like a wild theater. BUt it could be justified. The buy/sell between companies in Axapta is very easy and works instanteneously. (see chapter on INtercompany in the T*L manual) Then your question about setting up “shared” information becomes critical. I have no experience with that but it seems with “Company” items you can make that easier. Financial tables, unit of measurement etc can be “shared” also but somebody else has to help you with that Option B: Should 50 branch be treated a separate entity in Axapta and consolidation can be done at top level. If yes in the consolidation entity how to get the vendor wise, customer wise, itemwise aggregate totals.
Originally posted by Ramprasad - 2005 Jan 10 : 11:16:51
Probably option 2 is your solution. By creating a virtual company, the branches could share vendor-, customer- and item-information. Be aware of the limited amount of companies in basic Ax3.0 Johan