Cannot derive Chart of Account ID from xyz from organization Definitions -2

In addition to my explanation about the error "Cannot derive Chart of Account ID from xyz from organization Definitions" in the post Cannot derive Chart of Account ID from xyz from organization Definitions , Please note that this error is raised by Oracle application while driving the COGS.

Few of my readers has commented that why on earth system is validating the "Ship From Org ID " of the original Sales order while doing the receiving against RMA.

And ANSWER is - For an RMA application will always drive the COGS account from the Original Sales Order refered by RMA ( if RMA is referring Sales order ) , but if RMA is not referring any Sales order then COGS will be derived from the RMA ( in such scenario original Sales order will not comes into picture at all , and neither this error).

Hope that Helps...

Cannot derive Chart of Account ID from xyz from organization Definitions-1

recently encounter error "Cannot derive Chart of Account ID from xyz from organization" while performing receiving for an RMA.

While doing investigation I have found the

1. User was performing receiving against an RMA , and
2. RMA was referring sales order (Original Sales Order).
3. At the same time Ship from org ID ( warehouse ) referred  on the Original Sales Order was disabled.

It is this disabled warehouse (ship from org ID) on the original Sales order that results in this error "Cannot derive Chart of Account ID from xyz from organization Definitions" .

To fix this issue  we enabled the warehouse again and performed receiving against RMA and disabled the warehouse again.

Sync between Drop Ship Sales Order and corresponding PO

For a Drop Ship Sales Order where Requisition and purchase order has already been created.........

1. Only Primary Quantity (Order qty) changes on SO will trigger Secondary Qty Syn in Purchasing.
2. Grade will not be auto Sync between SO and PO.
3. Shipping Method info from SO will be pass to PO ( Reason - Shipping Method Info. is required by the drop Ship Supplier , to ship the good to customer).
4. Similarly Shipping Instructions will be pass from SO to PO ( and finally to supplier).
5. Also a new Menu Option "View Sales Order" is now available in PO to check the status of Drop Ship Sales Order ( Important - this is visible only if Drop Ship PO has already created in system).

NOTE - Please note that Purchasing Module will not Store the SO data elements in Requisition or PO tables, instead this information is taken from SO lines whenever required.

What if we Cancel the drop Ship Purchase Order in Oracle Application.

For a drop ship sales order , if Requisition and PO has already created and PO is APPROVED too , in such a scenario if user by some reason Cancelled the PO then connection between drop ship sales order and PO will be broken.Now user has following option
1.Cancel the drop ship sales order line and that will cancel the PO requisition too. OR
2.Navigate to AutoCreate and create a New PO from Purchasing Requisition.