About synchronization of disposition codes [AX 2012]

Updated: October 17, 2012

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

To support intercompany returns, Microsoft Dynamics AX enables you to map externally defined disposition codes to the corresponding internal disposition codes. When an intercompany chain is being set up, the disposition actions in the two companies that are mapped to each other must be the same. If they differ, the synchronization process will be unsuccessful.

Disposition codes are synchronized from the intercompany sales order line to the original sales order line. However, synchronization has only one immediate effect on the original sales order line. This effect is that miscellaneous line charges are deleted based on the disposition code and miscellaneous charge that are set up in Company A. Company A is the company that is creating the return order.

In a three-legged direct delivery chain, all disposition actions are supported on the intercompany sales order line. However, if a product is being returned to the customer, you should confirm that the delivery address in the return order matches the customer delivery address that is specified in the original order.

NoteNote

Disposition codes do not exist for purchase orders. Therefore, synchronization of disposition codes from the intercompany sales order to the original return order must be performed from sales order to sales order.

If a returned item is being replaced, and a replacement order has already been created in Company B, a disposition code cannot be selected, and no additional replacement order is created in Company A.

The following general rules apply to original return orders in scenarios that involve intercompany direct deliveries:

  • If the underlying disposition action on the original sales order line is Credit and Scrap, Credit, or Return to Customer, the Credit disposition action is applied. However, the Return to Customer action code sets the net amount to 0 (zero) on the existing line and on the newly synchronized line from the intercompany sales order. In addition, scrap lines are never synchronized. When a line is added to an intercompany sales order, it is never synchronized for a sales order that has a positive quantity and a disposition action of Scrap (for example, Credit and Scrap or Replace and Scrap).

  • An underlying disposition action of Credit and Replace or Scrap and Replace is not overruled. It is treated as a disposition action of Credit and Replace or Scrap and Replace. This rule applies even if no scrap line is created in Company A and no replacement order is created in Company B (the company that received the returned item). A replacement order is created in Company A only when a packing slip update is performed.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

ADD
Show: