Setting Up Supply and Demand Relationships
Access the Branch Relationship Revisions form.
- Item Number
Enter an item number to display all branch/plants that either supply or demand a certain part.
- Planning Family
Enter the planning family to display all branch/plants that either supply or demand parts that belong to a specific master planning family.
- Branch Level
Enter the level at which a component branch should be processed in multiplant processing. The lowest-level branches (which are assigned a higher numerical value) are processed first, followed by the higher-level branches (which are assigned a lower numerical value).
Note: Assign branch levels carefully so that the planning system generates all demand before allocating supply.- Branch Priority
Enter a value to determine the sequence within a level in which the branches are processed in multiplant DRP/MPS/MRP. Use this field along with the Branch Level field to check inventory availability first in one branch, and then another.
- Include/ Exclude
Enter a code that indicates whether the system includes or excludes the item/category code in the Branch Relationships Master table (F3403) when generating a multiplant schedule. If an item/category code is excluded, then that item/category code will be purchased or manufactured at the demand branch.
Some parts might come from certain branch/plants. In multifacility planning, if Exclude is selected, then the item is supplied by the demand branch only.
- Transfer Leadtime
Enter the number of days to ship items from the supply branch to the demand branch.
This lead time is set up in the Branch Relationships Master table and can vary for different category codes or even for different items.
- Effective From
Enter a date that indicates:
When a component part goes into effect on a bill of material.
When a rate schedule is in effect.
The default is the current system date.
You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in JD Edwards EnterpriseOne Product Costing from Oracle, JD Edwards EnterpriseOne Shop Floor Management, and Capacity Requirements Planning. Material Requirements Planning determines valid components by effectivity dates, not by the bill-of-material revision level. Some forms display data based on the effectivity dates that you enter.
The default date comes from the bill of material.
- Source Percent
Enter an amount as a percent. The system uses source percentage to determine what percentage of the planned order should be supplied by the source branch.
For example:
Demand Branch − ATL
Supply Branch − DEN source percentage = 40 percent, CHI source percentage = 60 percent
If ATL needs 100 parts, the system generates a message to transfer 40 parts from DEN and 60 parts from CHI.
A source percentage of 100 transfers the entire supply from that branch/plant.
- Availability Check
Specify whether the planning system checks availability of the item or family at the supply branch/plant. If you enable availability checking on the item or family that is being demanded, the available inventory at the branch/plant is committed until a zero balance results. If you disable availability checking, the inventory balance in the supplying branch/plant can be negative.
- Percent To Fill
Enter a value that is used during multiplant processing to determine what percent of an order should be filled to place a transfer order message. For example:
Percent to Fill: 75 percent
Demand: 200
If the supply branch has 150 (75 percent of 200) or more available, then the planning system places the transfer order message.
The system generates the transfer order message when the percent to fill is zero.
This amount of the source percent must be available to be filled by this branch/plant. The percent of demand should be filled to place a transfer order message. A transfer order is generated if Availability Check is on.