E1: 31F: Unable To Exclude Apparel Hierarchy Items From R3482/R3483 - Suggest Adding C9FSKU To F4101/F4102
Last updated on JUNE 28, 2017
Applies to:JD Edwards EnterpriseOne Apparel Management - Version 9.2 and later
Information in this document applies to any platform.
Apparel/Attribute Management items are managed within a hierarchy with parent root-level pseudo-items and "child" SKU items that are stocked and sold. If a Safety Stock quantity is to be applied to a higher level in the hierarchy it will cascade down to the SKUs. This is desirable for the SKU but leaves a Safety Stock on the parent apparel style ROOT item. When MRP/DRP runs it creates Order Messages against these higher hierarchy items.This is not desirable since these are not items that can be purchased or stocked. A workaround if to define the setting in the F4102 Item/Branch Planning Code MPST to 0 (zero). However this has to be done manually through P41026 for every Branch/Plant which is a lot of work with a potential of failure.
Currently, there is no "SKU Y/N" flag in to F4102 or F4101 for reporting purposes. A workaround is done by linking to the FCW02 where SKU Items always have a Size Attribute at Level 9. However this is soft coded. It is usable in general reporting but in programs like MRP Generation (R3482/R3483), no such linkage is possible
The enhancement proposal is to have the SKU (Y/N) Flag (data item C9FSKU) which already exists in FCW07 Collection Detail be added to the Item Master file (F4101) and Item B/P File (F4102) to future release of the software. The flag will be added automatically through PCW51. Items created only through P4101/P41026 without an FCW02 will have the flag set to "Y" automatically PCW51 can set the pseudo-items to "N".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms