E1: 32: DMAAI 4335 Being Invoked on PO Receipt (P4312) Due to Configured Item Being Defined with an F4105 Cost
(Doc ID 2432043.1)
Last updated on APRIL 26, 2022
Applies to:JD Edwards EnterpriseOne Configurator - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.
With a configured item (Stocking Type C), when receiving a direct ship order-generated purchase order (Document Type OD) via P4312, the system is invoking DMAAI 4335 (Standard Cost) being invoked when the configured Item has a cost (even if the cost is $0) at the Primary Location. If there is no cost in the F4105, then the system does not write to AAI 4335.
A configured purchase order cost is calculated based on the Configurator Costing Method (alias CMETH) is defined in the Item Master (P4101). You can cost via one of four options (By component F4105 Purchasing cost, by the F4105 Purchasing cost of the configured parent, by X Cost Rules only, or by components discounted cost). In general, configured items should NOT have an F4105 cost in the Primary Location so the short answer is to purge the F4105 record with a data file utility tool. However, there is ONE scenario in which it IS valid to have a Purchasing cost defined in the Primary Location in the F4105. This is when the Configurator Costing Method (alias CMETH) is defined as '2' to cost configured purchase orders by the F4105 cost of the parent item. THIS specific setup warrants entry of a Bug.
Note 1 - This issue occurs regardless of how the Configurator Costing Method (alias CMETH) is defined in the Item Master (P4101).
Note 2 - This issue does not exist with a typical purchase order (for example OP). This appears to only be an issue with a purchase order document type (in this case OD) that gets generated from a Direct Ship sales order.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document