Why Does Demand In Table MRP_GROSS_REQUIREMENTS Change From Planned Order To Discrete Job Demand?
Last updated on JUNE 28, 2017
Applies to:Oracle Materials Requirement Planning - Version 188.8.131.52 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Form:MRPSCPWB.FMB - Supply Chain Planner Workbench
The MRP_GROSS_REQUIRMENTS table is populated via the Memory Based Planner (MRCNEW). However users are unsure on what is the determining factor for Assembly's components being inserted into this table where the Origination Type is Discrete Job (origination_type = 3) versus an Assembly Component being inserted into this table where the Origination Type is Planned Order (orgination_type = 1). Why does this occur?
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