Outbound Shipping Schedule (862 / DELJIT)
Use this transaction to communicate short-term firm requirements and shipping schedules to your suppliers. Shipping schedules are usually stated in daily buckets and are used to refine planning schedules in support of a Just-in-Time planning environment.
This transaction supersedes certain shipping and delivery information transmitted in a previous planning schedule (830 transaction), but does not replace it.
This transaction may not be used to authorize labor, material, or other resources.
|Oracle Supplier Scheduling, Oracle Purchasing, Oracle Planning
|ASC X12 Transaction
Prerequisite Setup in Oracle Applications
Oracle Supplier Scheduling
Create shipping schedules manually using the Scheduler's Workbench or automatically using AutoSchedule.
Define bucket patterns, enable CUM Accounting to track quantity received by supplier site. Unlike a planning schedule (830 transaction), the concept of authorizations does not apply to shipping schedules.
Use Scheduler Workbench or enable AutoConfirm option in AutoSchedule to confirm your schedules. Only confirmed shipping schedules may be transmitted via EDI to your supplier(s).
Supplier Scheduling uses components of Oracle Purchasing to calculate and maintain schedules. Use the Approved Supplier list created in Purchasing to establish a relationship between the ship-to organization, supplier site, and item.
Information related to approved purchase requisitions, approved supply agreement releases, receipts from supplier, returns to supplier and associated adjustments are used to determine the supplier requirement.
Supplier Scheduling also uses components of Oracle Planning to calculate and maintain schedules. Use Sourcing Rules (which may be created in Purchasing, Oracle Supply Chain Planning, or Supplier Scheduling) to define how an item is replenished for a given organization. This includes the ability to identify multiple supplier sources, their percentage splits, and priority ranking.
Information related to unimplemented planned orders generated by Planning via MPS, MRP, or DRP are used to determine the supplier requirement.
Interface Table, Extension Table, and View Names
The following tables and views appear in the Interface File Definition window for this transaction. See: Changing the Data File.
Each extension table shares its name with a base interface table, except for the trailing "_X". You must define the columns for the extension tables if you choose to use them. See: Extensible EDI Gateway Architecture.
The following views appear in the Assign Categories window, under View Name, for this transaction. Columns within these views are identified as candidates for code conversion. See: Code Conversion.
Running the EDI Outbound Planning and Shipping Schedule Extract Program
Outbound Shipping Schedule Data File Organization
Outbound Planning Schedule and Shipping Schedule Data File Definition