This chapter describes Outbound Broadcast Sequencing—a process that enables the creation of replenishment signals on a Flow line where the supplier has special requirements, preferences, or conditions.
This chapter covers the following topics:
Outbound Broadcast Sequencing is a process that enables the creation of replenishment signals to supply components for scheduled assemblies, dependent on the production sequence of the respective parent assembly. Although generally associated with supplier components, this process works with all methods of kanban supply.
Kanban signals control the replenishment of component material to a Flow line. Kanban planning has calculated container sizes, or quantity based on a predictable cycle, ensuring the availability of all necessary components. In some business processes the predictability of components is not possible, or the schedule of assemblies determines the component requirements. Outbound Broadcast Sequencing provides a method for sourcing components. For these components, the purchase requisition is generated based on firm Flow schedules. This functionality is implemented when you set up pull sequences with the Auto Request flag enabled.
A concurrent program is used to calculate kanban requirements and generate kanban cards by specifying production lines, date ranges, and other criteria. The Outbound Broadcast Sequencing process sends the appropriate date for creation of the purchase requisition for the relevant components, depending upon the Source type specified in the item's pull sequence.
Specifying a Range of Completion Dates and Build Sequences
You can specify a range of completion dates and build sequences as the Autoreplenishment Program supports selection of schedules by specifying a range of completion dates and build sequences.
The parameters From Completion Date, To Completion Date, From Build Sequence, and To Build Sequence enable you to specify the range of completion dates and build sequences.
The list of values in the From Completion Date field lists all the dates starting from the current date and the list of values in the To Completion Date field lists all dates greater than or equal to From Completion Date.
From Completion Date defaults to the current date.
To Completion Date defaults to the From Completion Date.
To Build Sequence initially defaults to From Build Sequence.
If the value of the From Build Sequence parameter is greater than To Build Sequence, then no schedule is picked.
If both the From Completion Date and From Build Sequence are null, then the From Completion Date is taken as the current date.
Note: You cannot launch multiple requests for autoreplenish concurrent program simultaneously as multiple replenishments cannot be done for the same schedule.
Related Topics
Overview of Kanban Replenishment, Oracle Inventory User's Guide.
Defining Kanban Pull Sequences, Oracle Inventory User's Guide
Setting Up Outbound Broadcast Sequencing
Outbound Broadcast Sequencing functionality is set up when you create your pull sequences.
Pull Sequence window
Enable the Auto Request box, this is used to identify this type of pull sequence replenishment.
The size and number of kanban cards are not used for kanban calculation, if the Auto Request box is enabled.
Related Topics
Overview of Kanban Replenishment, Oracle Inventory User's Guide
Defining Kanban Pull Sequences, Oracle Inventory User's Guide
The following steps are performed when Outbound Broadcast Sequencing kanbans program is initiated:
Retrieves Flow schedules in the date range specified.
Selects Flow schedules not previously processed.
Considers schedules with components flagged as Item Attribute--Release Time Fence, Kanban Item--Do Not Plan, and Supply Type—Pull.
Considers pull sequences where item and point of use matches the bill of material, component, location, and the Auto Request flag is enabled.
The basis type of the flow schedule assembly is considered.
Calculates required date of the components based on the Flow schedule completion date and the routing where the component is used. Minimum order quantity data is not used.
Creates non-replenishable kanban cards for the components using the pull sequence information.
For kanban card supply type Supplier, the purchase requisition is created with the reference to the Flow schedule information.
Related Topics
Changing and Viewing Kanban Details
Defining Kanban Cards, Oracle Inventory User's Guide
Using the Kanban Calculation Program, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide