What is the Meaning of "Enforce Integer Requirements'' in BOM (Doc ID 292125.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Materials Requirement Planning - Version: 11.5.9 to 12.1.3 - Release: 11.5 to 12.1
Information in this document applies to any platform.

Symptoms

In 11.5.8 and above the system added a parameter named "Enforce Intefer Req" in Bill of Material.

In the BOM screen, in component area, TAB the value of parameter 'Enforcee Integer Req'. It is set to 'up'.

Define a job by hand and check its material requirements. All components 'required' quantity still have decimal digits. According to the Users Guide, this parameter should up them to integer.

After running MRP, in Planners Workbench, find that this parameter still has no effect on the plan result.

As per the Users Guide

The Enforce Integer Requirements attribute enables you to generate demand in integer quantities and eliminate pegging partial quantities across the demand. If you pass the demand in integer values for lower level components in the BOM, you avoid passing fractional values across the BOM.
This enables pegging to reflect the true integer nature of supply and demand. You can select from one of three following values:

Up: The system rounds the gross requirements for every demand for the component to the next higher integer value. To set the value to UP, you must set the item master attribute Rounding in Oracle Inventory.

Down: The system rounds the gross requirements for every demand for the component to the next lower integer value.


The issue is that the MRP is not calculating the planned order quantity based on the UP or DOWN value of the parameter "Enforce integer req".

Cause

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