Having the reputation of excellence in Dynamics AX implementations, and founded by original developers of axapta, Arbela Technologies possesses tremendous knowledge and expertise around the solution as well as best practices associated with it. Our blog is designed to share that knowledge with the Dynamics AX community, thus enabling them to take full advantage of their investment in this technology.
Inter-company Transactions are those that are made between two or more related internal legal entities. The transactions are trigged by demand for an item that has been set up to be sourced by an inter-company vendor. Inter-company vendors are related to inter-company customers in the sourcing entity.
When a purchase order for an inter-company vendor is firmed, the corresponding sales order in the sourcing company is automatically created by Dynamics AX. Dynamics AX allows planned order demand to be reviewed all the way through to the bottom of the supply chain. The requirement date for the associated planned order is determined by the lead time setup on the item in the company from which the demand originated. In situations where a constraint of material or capacity is encountered and the required date cannot be met, it becomes necessary for the planners to have that knowledge. Although planners cannot see the constraint of the upstream supply in the planned order screen of the demand company, Dynamics Ax does provide this information through the use of the “outbound planned inter-company demand” screen.
Consider the following scenario:
The illustrations below show the relationships for item “testplan2” in companies 60 and 91.
This screen shot shows the “net requirements” view from within company 60. Here it can be seen that a planned purchase order has been created by the master planning system to fulfill the demand for pegged sales order 60SO0000237 in a quantity of 45,000. In this view it cannot be seen that the planned purchase order date of 6/1/2012 will not be met until 6/21/2012.
This screen shot shows the “net requirements” view from within company 91. Here it can be seen that a planned batch order has been created by the master planning system to fulfill the demand for pegged inter-company demand. In this view it can be seen that the planned batch order date of 6/20/2012 will not meet the required demand date of 6/1/2012.
The planner in company 91 can review the action and futures messages that where created by the system and determine that the order will be twenty days late.
The operator cannot see the delay in the “net requirements screen” of company 60 and only in the “net requirements screen” of company 91 can it be determined that the item will be delayed.
Dynamics AX does provide a solution so that the operator can see the delay from within company 60. The “outbound planned inter-company demand” screen has been developed for this purpose. This screen is found in (Master planning > Inquires > “outbound planned inter-company demand” ) . For any item requiring inter-company supply the operator can review this screen. As you can see below, this screen provides a clear view of the fact that the demand cannot be met by the supply company.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13