Outside Processing

This chapter explains how you can manage your outside processed resources in Work in Process.

This chapter covers the following topics:

• Overview of Outside Processing
• Outside Processing Setup and Planning
• Supplier Access to Outside Processing Purchase Orders
• Outside Processing Workflows
• Changing the Need By Date
• Printing Documents for OSP Shipment Lines

Overview of Outside Processing

Oracle Manufacturing enables you to include supplier-sourced components and resources in your manufacturing processes. You can use specialized supplier skills in your manufacturing process to help lower engineering and manufacturing costs and increase production quality; and supplier capacity to increase your overall production capacity.

Outside processing items are defined for supplier-sourced items, resources, and services included in your build process. These items can be non-stocked items which represent the actual supplier contribution in your build process or you can define the assembly itself as an outside processing item. The outside processing item is the item on your requisition or purchase order and the item you receive in your purchase order receipts. Features of outside processing include the following:

Multiple Outside Resources per Operation

Multiple outside resources can be assigned to each operation on the routings of your outside processed assemblies.

Supplier-Sourced Components

You can define supplier-sourced components by selecting the Supplier supply type on your bills of material to identify components that are provided by suppliers. Supplier components provide information on the component materials that your suppliers provide, but the supplier components need not be transacted. Supplier components are not backflushed.

Automatic Requisition Generation

An outside processing operation is an operation that contains an outside resource for a required item. Work in Process can be automatically set to generate purchase requisitions for outside processing operations. The Autocreate feature in Oracle Purchasing is used to convert these requisitions to purchase orders.

Note: The Requisition Import process automatically runs when using PO Move and PO Receipt resource types. However, only PO Move initiates the Intermediate Shipment workflow.

See: Requisitioning Outside Processing Items

Automatic Resource Charging

Purchasing automatically charges jobs or repetitive schedules for outside resources when you receive the outside processing items linked to outside resources on those jobs or repetitive schedules.

Automatic Move Transactions

When you receive outside processing items linked to PO Move resources, Purchasing automatically moves the assemblies to Queue of the next operation or to To Move of the final operation (if you are at the final operation).

If you receive more assemblies than the quantity in the Queue of the outside processing operation, WIP automatically moves a quantity up to the over-completion tolerance limit on the assembly being built. If the quantity received is greater than the acceptable over-move quantity for the job, then the transaction will error and quantity will be included on the Pending Move Transaction window.

Note: If Oracle Shop Floor Management is installed, and you are using lot based jobs with network routings, the PO Receipt transaction moves the items to the last operation-not the next operation. See:

Creating a Network Routing in the Shop Floor Management.

Automatic Assembly and Work Order Completion

If the outside processing operation is the last operation on the routing, and the resource has a charge type of PO Move, Work in Process automatically completes both full and partial outside processing assembly quantities into Inventory when they are received back from the supplier. When quantities that account for the remaining uncompleted quantity of a work order are received, the status of the work order is updated to “complete-charges allowed."

Outside Processing Business Examples

In general, you use outside processing to facilitate the purchase and costing of supplier services included in your production activities. The following are three examples of how you can use outside processing in Oracle Manufacturing.

Plating Service Example

A computer manufacturer sends frame assemblies to a supplier for plating. A primary routing is defined for assemblies that includes a supplier plating operation. There is a contract and blanket purchase agreements created based on your production capabilities and capacity planning.

To support the purchase and costing of the supplier plating service, you define an outside resource called "Plating" with a charge type of PO Move, a UOM of EA for each, and a standard cost. Then you link this resource to an outside processing item called "Plating." This is the item that you purchase and receive from your supplier.

You set the WIP parameter Requisition Creation Time to At Job/Schedule Release. When you release the job, the requisition is created. You use AutoCreate to convert the requisition to a purchase release against the blanket order for the "Plating" outside processing item and send the release to the supplier.

When your assemblies are ready for plating, you ship them to your supplier and enter a move transaction recording the move to the supplier plating operation.

You receive the plated assemblies back from the supplier. The job you use to control your production is automatically charged for the "Plating" outside resource when you receive the assemblies. The assemblies are automatically moved to the next operation for inspection to match your physical flow.

You perform inspection of the assemblies at the following operation and either move them on or return them to the supplier for rework. If you return them for rework, Oracle Manufacturing automatically reverses the charges and performs a reversing move transaction to accurately track the physical flow of your assemblies.

Plating Service Setup Charge Example

As part of your contract, your supplier charges the same setup fee for each job or repetitive schedule, regardless of the number of assemblies on the job or repetitive schedule. You have defined a primary routing for your assemblies that includes a supplier plating operation with a Lot based outside resource for plating setup.

To support the purchase and costing of this setup charge, you define an outside resource called "Plating SU" with a charge type of PO Receipt, a UOM of EA for each, and a standard cost. Then you link this resource to an outside processing item called "Plating SU." The purchase quantity is always 1 on a job or repetitive schedule, unlike the "Plating" outside processing item, which was based on the number of assemblies you shipped. You set the WIP parameter Requisition Creation Time to At Operation.

When your assemblies are ready for plating, you ship them to your supplier and enter a move transaction recording the move to the supplier plating operation. The move automatically initiates a purchase requisition for a single "Plating SU" outside processing item associated with the "Plating SU" outside resource. You use AutoCreate to convert the requisition to a purchase order and send the purchase order to the supplier.

When you receive the assemblies back from the supplier, there is a separate line item for "Plating SU." The job or repetitive schedule you use to control your production is automatically charged for the setup charge when you receive that item. The assemblies are not moved after this receipt; rather they are moved when you receive the "Plating" item since the "Plating" resource's charge type is PO Move.

Plating Service Labor Charge Example

Your supplier charges a setup fee for each job or repetitive schedule and a plating service charge for each assembly he services. In addition, the supplier has a resource at his plant to perform periodic chemical analysis relating to the assembly plating process. Although this service is not a standard part of the plating process, you still include this outside resource on your routing so you can charge it as needed.

To support the purchase and costing of this chemical analysis resource, you define an outside resource called "Analysis" with a charge type of PO Receipt, a UOM of EA for each, and a standard cost of $1. However, you do not link this resource to the "Analysis" outside processing item.

Since the "Analysis" resource is not linked to the "Analysis" outside processing item, this resource is never automatically requisitioned. However, your buyer includes this item on purchase orders as necessary to authorize this periodic chemical analysis service. The buyer includes the amount he authorizes (such as 100 EA @ $1 = $100) and the job or repetitive schedule to charge.

When you receive assemblies back from the supplier, there is a separate line item for "Analysis" charges. The job or repetitive schedule the buyer referenced on the purchase order line is automatically charged for the chemical analysis service charges when you receive that item. The assemblies are not moved after this receipt.

Outside Processing Assembly Flow

Oracle Manufacturing provides the flexibility you need to control your outside processing flows. This includes areas such as consuming material requirements, shipping assemblies to suppliers, tracking assemblies at suppliers, and inspecting outside processed assemblies.

Kitting Options

An outside operation may have material requirements in addition to labor or machine requirements. For example, you may kit and ship components to your supplier for assembly. Or, you may let your supplier provide the components.

Use the supply type on your bill to indicate who supplies components. For example, if your supplier provides components in addition to labor, you can include the components on your bill with a Supplier supply type. You can charge a job or repetitive schedule for these components by including their cost in the standard cost of the outside resource on your routing. Or, if your supplier charges you separately for these components, you can add another outside resource specifically for these costs.

If you kit components to send to a supplier for assembly, you can include these components on your bill with a Push supply type.

If you want to backflush the components at an outside operation, you can identify the components on your bill with either an Operation Pull or Assembly Pull supply type.

Shipping Options

You can use move transactions in Work in Process to record outside processing shipments to your supplier. You can include the specific costs of shipping as separate resources on your routing.

If you have sequential outside processing operations and you have worked out the physical flows between your suppliers, you can use PO Move resources to automatically move outside processed assemblies from one outside operation to the next one on your routing.

Inspection Options

Oracle Manufacturing provides you with several options for inspecting your supplier work. In general, either you or your supplier can perform inspections.

If your suppliers perform inspections, they can then ship the assemblies directly to the next operation on your routing.

If you perform the inspection internally, you can define an internal inspection resource either at the outside operation or at a separate inspection operation with an inspection resource.

You can also receive the outside processed assemblies into a receiving inspection location in Purchasing and perform your inspection activities in receiving inspection. Then, you can deliver the assemblies to the shop floor and charge the job or repetitive schedule for the outside processing services.

Outside Processing Setup and Planning

Required setup steps are completed in Oracle Applications, Inventory, Bills of material, Cost Management, and Purchasing. The following table lists the setup steps to be completed in each of these applications.

Product	Setup Functions
Oracle Applications (see: Oracle E-Business Suite Setup Guide)	Set up site level profile that enables outside processing workflows.
Inventory (see: Setting Up Inventory)	Define outside processing items, item list prices and lead times, and units of measure.
Bills of Material (see: Setting Up Bills of Material and Cost Management)	Define departments and routings. Link outside resources to operations. Include supplier-sourced components on bills of material.
Cost Management (see: Setting Up Bills of Material and Cost Management)	Define outside resources, perform cost rollup
Purchasing (see: Setting Up Purchasing)	Define supplier sourcing rules, outside processing line types, quantity received tolerances, receiving routing controls, ship to, deliver to locations, and receiving, PPV, IPV, and AP accrual accounts. Link employees to application users. Assign supplier sourcing rules.
Work in Process (see: Setting Up Work in Process)	Define WIP accounting classes, WIP parameters. Set up shop floor statuses.

Setting Up Inventory

Use the Items window to define and maintain outside processing items. These items can be non-stocked items which represent the actual supplier contribution in your build process, or you can define the assembly itself as an outside processing item. See: Defining Items, Oracle Inventory User's Guide.

Define Outside Processing Items

When you define outside processing items,, you must define certain item attributes in the Items window. See: Purchasing Attribute Group, Oracle Inventory User's Guide These attributes enable you to link outside resources to the outside processing items, and then include the items on outside processing requisition and purchase order lines. This includes:

• Outside Processing Item

  Set this attribute to Yes to link an outside processing item with an outside resource, and to include an item on an outside processing purchase order line.

• Purchasable

  Set this attribute to Yes to include an item on a purchase order line.

• Outside Processing Unit Type

  If you want to requisition one outside processing item for each assembly you ship to a supplier, set the Outside Processing Unit Type to Assembly.

  If you want to requisition the usage rate or amount of the outside resource, you should set the Outside Processing Unit Type to Resource.

Outside Processing UOM Type = Assembly	Outside Processing UOM Type = Resource
Equals the job or repetitive schedule assembly UOM.	Equals the outside resource UOM.
Equals the assembly move quantity using the outside processing item UOM.	Equals the assembly move quantity times the outside resource usage rate or amount using the outside processing item UOM.
Charge the receipt quantity times the outside resource usage rate or amount using the outside resource UOM.	Charge the receipt quantity using the outside resource UOM.

Maintain Outside Processing Items in Multiple Organizations

You must maintain each outside processing item you define across all organizations that use the item in outside processing. This includes the Purchasing inventory organization that you establish in the Financials Options window, and each work in process organization you use for building your assemblies. See: About Financials Options, Oracle Payables User's Guide

Processing Lead Time Attributes

When Work in Process requisitions an outside processing item, the start date of the operation, following the outside processing operation determines the Need By Date. If the outside processing operation is the last operation, then the Need By Date is the last unit complete date of that operation. Processing lead times are defined in Oracle Inventory Item Attributes and include:

• Preprocessing lead time specifies the number of days you must add to purchasing or manufacturing lead time to place an order.

• Processing is the days required to procure or manufacture an item. For manufactured assemblies, processing days equals manufacturing lead time.

• Post processing is the days required to receive a purchased item into inventory from the initial supplier receipt.

Note: For lot based jobs, a different logic is used to derive the need by date because network routings have changing first and last operations.

Note: For Enterprise Asset Management work orders, the need by date is the last unit completion date of the outside processing operation.

See: Lead Times Attribute Group, Oracle Inventory User's Guide.

Setting Up Bills of Material and Cost Management

Define outside resources in Cost Management and Bills of Material. You assign the outside resources to departments and shifts - and define routings that include operations with outside resources. You can also include supplier-sourced components on your bills of material.

Define Outside Resources

Define outside resources and link them to outside processing items in order to automatically generate purchase requisitions. When you assign outside resources to a routing, you also specify a usage rate or amount that determines the quantity you are requisitioning and charging to work in process jobs or schedules. See: Defining a Routing, Oracle Bills of Material User's Guide, Defining a Standard Operation, Oracle Bills of Material User's Guide, and Count Point and Autocharge Fields, Oracle Bills of Material User's Guide

Define Departments with Delivery Locations

Define departments with outside resources and valid delivery locations You cannot associate an outside resource with an operation on a routing unless the resource is assigned to the operation's department and the department has a location associated with it. See: Defining a Department, Oracle Bills of Material User's Guide

Work in Process passes the department location to Purchasing as the Deliver-To location when requisitioning outside processing items. Purchasing requires a Deliver-To location when you receive outside processing items and deliver them to the shop floor.

Define Routings

Use the Routing window in Bills of Material to associate outside resources with assemblies requiring outside processing. See: Creating a Routing, Oracle Bills of Material User's Guide.

Define Supplier-Sourced Components

You can define supplier-sourced components on bills of material by choosing a supply type of Supplier. See: Creating a Bill of Material, Oracle Bills of Material User's Guide

Cost Rollup

The cost rollup uses the outside resource's usage rate or amount, unit cost, and basis to calculate the outside processing costs for the primary routing of each assembly. Lot based resources are allocated across the assembly's standard lot size in calculating the assembly's standard cost. See: Rolling Up Assembly Costs, Oracle Bills of Material User's Guide.

Setting Up Purchasing

In conjunction with the Work in Process setup, the Purchasing setup enables you to create requisitions, send these documents through the approval process, and create purchase orders for outside processing items and resources. There are several setup steps for outside processing that you must perform in Purchasing.

Define Outside Processing Line Types

Purchasing requires you to enter a line type when you enter a requisition or purchase order line. Purchasing is installed with a predefined line type called Outside Processing, and Work in Process uses this line type when it creates pending requisitions. You can define additional line types for outside processing. See: Defining Line Types, Oracle Purchasing User's Guide.

Define Sourcing Rules

You can define rules for each outside processing item to help you determine from which supplier to source the item. When Work in Process requisitions an outside processing item, it checks for sourcing rules. See: Automatic Sourcing, Oracle Purchasing User's Guide.

Define Outside Processing Item Lead Times

When Work in Process requisitions an outside processing item, the start date of the operation following the outside processing operation determines the Need By Date. If the outside processing operation is the last operation, then the Need By Date is the last unit complete date of that operation. Lot based jobs use a different logic to derive the need by date because network routings have changing first and last operations. Enterprise Asset Manufacturing work orders calculate the need by date as the last unit completion date of the outside processing operation,

Define Over-receipt Tolerance and Control

You can specify a quantity received tolerance percent to limit the quantity you can over receive on a purchase order shipment.

You can define your receiving tolerance in the Receiving Options window in Purchasing and override it at the supplier, item, and purchase order shipment levels. See: Defining Receiving Options, Oracle Purchasing User's Guide.

Control Your Receipt Routing

You can control your receiving routing by specifying one of three options. The first option lets you receive an outside processing item directly into work in process. The second option requires you to receive to the Ship-To Location before you can deliver to work in process. The third option requires you to deliver to the Ship-To Location, inspect the outside processing items, and then deliver to work in process. See: Defining Receiving Options, Oracle Purchasing User's Guide and Profile Options in Purchasing, Oracle Purchasing User's Guide

Define Ship To and Deliver-To Locations

You must define Ship To and Deliver-To Locations to include on your requisitions and purchase orders. See: Site Locations, Oracle Human Resource Management Systems User's Guide.

• The Ship-To Location represents the delivery dock or inspection location. .

• The Deliver-To Location represents the destination location.

Setting Up Work in Process for Outside Processing

Set up the Work in Process parameters and profile options to enable the automatic creation of purchasing requisitions.

• Profile option WIP:Enable Outside Processing Workflows determines whether or not outside processing workflows are enabled and also automatically runs the Requisition Import program for purchase order move resource transactions.

• Profile option WIP:Launch Requisition Import for PO Move determines the automatic trigger of the Requisition Import program for purchase order move resource transactions and stops the workflow notifications if the WIP:Enable Outside Processing Workflows is set to No.

• Profile option WIP:Launch Requisition Import for PO Receipt determines the automatic trigger of the Requisition Import program for purchase order receipt resource transactions .

• Profile option WIP:Initiate Approval Process after Requisition Import controls whether the Requisition Import program triggers the approval process after requisition creation; or the approval process is not automatically triggered..

• Profile option WIP:Allow Cancel Jobs with Pending OSP Requisitions gives you the choice of deleting a job even when there are existing purchasing requisitions.

• Shop Floor Status for PO Move Resources parameter determines which shop floor status is assigned to the Queue intraoperation step. This enables you to assign the status to operations that have PO Move resources assigned to them. This status ensures that assembly moves from an outside processing resource operation can only be launched by the receipt of a purchase order in Oracle Purchasing.

• Requisition Creation Time parameter determines whether or not requisitions are created, and when they will be created: You can set it for:

  • At Job/Schedule Release, a purchase requisition is created when you release the job or schedule.

  • At Operation, a purchase requisition is created when you move into the Queue intraoperation step of an outside processing operation.

  • Manual: This option requires you to manually create purchase requisitions in Oracle Purchasing.

    Note: For lot based jobs in Oracle Shop Floor Management, set this is parameter to At OSP Operation. Multiple paths are available in a network routing, and the outside processing operation can change for each manufacturing run. At Job/Schedule Release At OSP Operation Manual

    Note: If you set the parameter to At Operation, and the move transaction is for a partial quantity, the requisition is created for each quantity moved. If you set the parameter to At Job/Schedule Release, the requisition is created for the entire job quantity - independent of the move transaction quantity.

• The Requisition Status at Creation sets the status for requisitions created in the outside processing step:

  • Approved: Requisitions created are set as approved, and depending on other settings, the approval process can automatically be initiated.

  • Incomplete: Requisitions are set as incomplete until approval is granted.

  This profile works in combination with the Requisition Creation Time parameter. Regardless of the value selected for this profile, if the parameter is not set to Manual, records are picked up from the Requisition Import interface. Some of the examples are as follows:

  • Example 1

    Requisition Status at Creation = Approved

    WIP:Initiate Approval Process after Requisition Import = Null or Yes

    Requisition is Approved

  • Example 2

    Requisition Status at Creation = Approved

    WIP:Initiate Approval Process after Requisition Import = No

    Requisition is Approved.

  • Example 3

    Requisition Status at Creation = Incomplete

    WIP:Initiate Approval Process after Requisition Import = Null or Yes

    The Requisition is In Process, Pre-approved, or Approved depending on the setup in Purchasing.

  • Example 4

    Requisition Status at Creation = Incomplete

    WIP:Initiate Approval Process after Requisition Import = No

    Requisition is Incomplete.

• Production Scheduler parameter defines the employee receiving outside processing workflow notifications. The production scheduler receives notifications when there are no purchase orders for outside processing items, for shipping information. See: Outside Processing Workflows.

• Shipping Manager parameter associates an employee with outside processing workflow notifications. The shipping manager receives a notification when intermediate assemblies are ready to be shipped to a supplier for outside services. See: Outside Processing Workflows

• Propagate Job Change to Purchasing controls how status and quantity changes are forwarded to purchasing documents, and whether these documents are cancelled. You can pass changes automatically through the workflow, or manually update changes directly in the purchasing documents.

• Need-By Date Tolerance values are used to initiate the workflow for automatic job date changes. These values are used by the Update OSP Need-by Date concurrent program. If the concurrent program is not submitted, these values are ignored. The concurrent program initiates the workflow for automatic job date changes when the number of days set in the Days Early field and Days Late field is exceeded.

When the purchase requisition is created, the revision of the outside processing item is determined and put on the requisition. If the outside processing item is an assembly component, the current revision of the item is used. If the outside processing item is the assembly being built, the bill of material revision on the job or schedule is used.

Note: For lot based jobs in Oracle Shop Floor Management, set this is parameter to At Operation. Multiple paths are available in a network routing, and the outside processing operation can change for each manufacturing run.

You can manually requisition and purchase outside resources that are not linked to outside processing items.

You can define a purchase order with several lines; each line can be for a different outside processing item, and each outside processing item can refer to several discrete jobs or repetitive schedules.

Job date, status, and quantity changes are passed to related purchasing documents. You can choose to have these changes fully automatic, automatic subject to approval, or manually created. This feature is applicable to discrete jobs, repetitive schedules, and maintenance work orders.

Note: Enterprise Asset Management work orders only support date changes.

See:

• Requisitioning Outside Processing Items

• WIP Parameters

• Profile Option Descriptions

Calculating Requisition Quantities for Unit Types

Calculating Requisition Quantities for Outside Processing Unit Type of Resource

When an outside processing item is requisitioned with a Outside Processing Unit Type of Resource, it uses the outside resource's usage rate or amount and basis to calculate the requisition quantity.

If the basis is Item, the usage rate or amount times the move quantity is used, or the usage rate or amount times the job quantity - depending on the WIP parameter Requisition Creation Time. For example, if you have an outside resource with a UOM of HR and a usage rate or amount of 10, and you move five assemblies into the outside operation, Work in Process requisitions 50 HR of the outside processing item linked to the outside resource.

For outside resources with a basis of Lot, Work in Process requisitions the usage rate or amount of the resource when you move the first assembly on the job or repetitive schedule into Queue of the outside operation or when you release the job, depending on your Work in Process setup.

Calculating Requisition Quantities for Outside Processing Unit Type of Assembly

When requisitioning items with an Outside Processing Unit Type of Assembly, Work in Process does not extend the assembly move quantity by the usage rate or amount.

If you set the parameter to At Operation, and the move transaction is for a partial quantity, the requisition is created for each quantity moved. If you set the parameter to At Job/Schedule Release, the requisition is created for the entire job quantity - independent of the move transaction quantity.

For outside resources with a basis of Item, when the WIP parameter Requisition Creation Time is set to At Operation, Work in Process requisitions the move quantity each time you move into Queue of the outside operation.

For outside resources with a basis of Lot, Work in Process requisitions a quantity of 1 when you move the first assembly on the job or repetitive schedule into Queue of the outside operation or when you release the job or schedule, depending on your Work in Process setup.

Move Qty.	Item Price and Unit	Required?	Transaction Quantities and Charges
50	Assembly: $1 each	Item: 10 at $1 each	50 at (50 x 10) @ $1 = $500
50	Assembly: $1 each	Lot: 10 at $1 each	1 at (1 x 10) @ $1 = $10
50	Resource: $1 per hour	Item: 10 at $1 per hour	500 hrs. at (500 HR @ $1) = $500
50	Resource: $1 per hour	Lot 10 at $1 per hour	10 hrs. at (10 HR @ $1) = $10

Work in Process Scheduling

Work in Process schedules all resources in a routing with Scheduling set to Yes and with a time based unit of measure. If you are requisitioning outside processing items for outside operations with units of measure that are not time based, you may want to add resources with time based units of measure to the routing to accurately schedule the outside processing work. You can also include time based outside resources in capacity planning. See: Overview of Work in Process Scheduling and Creating a Routing, Oracle Bills of Material User's Guide.

Planning Outside Resource Load

Capacity does not include resources with non-time based units of measure in its capacity plans. All capacity plans are displayed in hours. So, even resources which have time based units of measure other than hours must have unit of measure conversions defined for hours. For outside resources in units of measure such as EA for each, you can define another resource on your routing to use for scheduling purposes and to include in your capacity plans.

Requisitioning Outside Processing Items

You can create purchasing requisitions for outside processing items automatically or manually depending on how you set the WIP parameter Requisition Creation Time.

If you set the parameter to At Job/Schedule Release, a purchase requisition is created for all outside processing operations on a job or schedule when you release the job or schedule. If you set the parameter to At Operation, a purchase requisition is created when you move into Queue of an outside processing operation. If you set the parameter to Manual, you must create purchase requisitions manually. You also must manually create purchase requisitions for work orders with a resource charge type of PO Move or PO Receipt that are added to the work order after it is released.

The Requisition Import process automatically runs when using PO Move and PO Receipt resource types. However, only PO Move initiates the Intermediate Shipment workflow.

If Oracle Shop Floor Management is installed, and you are using lot based jobs with network routings, the PO Receipt transaction moves the items to the last operation-not the next operation. Network routings define different paths for the next operation according to the results of the last operation. The next operation cannot be determined before receiving because the routing is dynamic.

Work in Process Move Transactions

When a requisition is automatically triggered by a move transaction into an outside processing operation, Work in Process creates a pending requisition in the PO_REQUISITIONS_INTERFACE table for the outside processing item linked to the outside resource. If you define several outside resources in an operation, Work in Process creates a separate pending requisition for each outside processing item linked to each resource.

If you move into any intraoperation step other than Queue, Work in Process does not create a pending requisition. Also, if you move backwards into Queue, Work in Process does not create a pending requisition.

Submitting Requisition Import

You can submit the Requisition Import process through the Submit Requests window in Purchasing to generate approved requisitions created by Work in Process. You must specify WIP as the Import Source when you submit the process. You have several choices for grouping your requisitions including All, Buyer, Category, Item, Location, and Supplier. For example, you can group your requisitions by Item to create a separate requisition for each item. Or, you can group your requisitions by All to include multiple items on a single requisition. Purchasing creates a separate requisition line for each line in the interface table. See: Requisition Import Process, Oracle Purchasing User's Guide.

You can specify a default Group By option for Requisition Import in the Purchasing Options window. You can also automate the approval of pending requisitions by using the resubmit functionality of the Submit Requests window to automatically submit the Requisition Import process at pre-specified intervals. See: Defining Default Options, Oracle Purchasing User's Guide and Submitting a Request, Oracle E-Business Suite Setup Guide.

Creating Purchasing Requisitions

When creating approved requisitions, Purchasing automatically checks for supplier sourcing rules when it creates a requisition line for an outside processing item. If you defined a supplier sourcing rule, Purchasing defaults the primary supplier you specified. If you have a blanket purchase agreement active for the item/supplier combination in the Approved Supplier List, then Purchasing also defaults the price associated with the outside processing item on the blanket. If no price exists, then Purchasing defaults the List Price from the item master.

You can manually define a purchase requisition that includes one or more outside processing items. For each requisition line, you must specify a job or repetitive schedule to charge. You can charge any resource on a job or repetitive schedule that has a charge type of PO Move or PO Receipt. See: Entering Outside Processing Information, Oracle Purchasing User's Guide.

Creating Outside Processing Purchase Orders

You must create a purchase order line for each of the outside processing items you are buying. You can modify purchase order lines to reference jobs or schedules other than those referenced in the requisition.

Automatically Generating Purchase Orders from Requisitions

Use the AutoCreate Documents window in Purchasing to generate purchase orders from approved requisitions. See: Autocreate Purchase Order Options, Oracle Purchasing User's Guide

Manually Creating Purchase Orders and Lines

You can manually define a purchase order which includes one or more outside processing items. You can charge any resource on a job or repetitive schedule which has a charge type of PO Move or PO Receipt. You can even charge multiple jobs or repetitive schedules by including several distributions for a purchase order line. See: Entering Purchase Order Distributions, Oracle Purchasing User's Guide.

Job Changes Generated to Related Purchasing Documents

Job date, status, and quantity changes can be passed to related purchasing documents. You can choose to have these changes fully automatic, automatic subject to approval, or manually created. The Purchase Order Approval and Requisition workflows are launched to initiate these changes to Purchasing. To support quantity increase or decrease changes, the purchase order or requisition quantity is updated—instead of creating a new requisition. The purchasing documents are automatically canceled when job status changes to Complete-No-Charges, Cancelled, or Closed.

For date changes to jobs, these workflows are only initiated if preset tolerance value set in the Work in Process Parameters window, are exceeded. This feature is applicable to discrete jobs, repetitive schedules, and maintenance work orders.

Need-By Date Tolerance values are used to initiate the workflow for automatic job date changes. These values are used by the Update OSP Need-by Date concurrent program. If the concurrent program is not submitted, these values are ignored. The concurrent program initiates the workflow for automatic job date changes when the number of days set in the Days Early field and Days Late field is exceeded.

Note: Enterprise Asset Management work orders only support date changes.

Viewing Purchase Orders

You can view purchase order information including which jobs and/or repetitive schedules you are charging in the Purchase Orders window. You can view all purchase orders linked to a job or repetitive schedule by submitting the WIP Outside Processing report. See: WIP Outside Processing Report.

Receiving Outside Processing Items

You receive outside processing items using the receiving functions in Purchasing. From a physical flow point of view, you receive the outside processed assemblies and move them to the next manufacturing operation or into inventory. From a transaction point of view, you actually receive the outside processing items against purchase order lines. The receipt transaction relieves the purchase order, creates the appropriate Payables accrual, charges the job or repetitive schedule for the outside resource, and optionally moves the outside processed assembly to the next operation. See: Receiving Transactions, Oracle Purchasing User's Guide.

Direct vs Standard Receipts

When you receive outside processing items from suppliers, you can optionally receive them directly into work in process or into a receiving/inspection location before delivering them to work in process. A direct receipt also moves the assemblies to the next operation in work in process if the outside processing item you are receiving is linked to a PO Move resource.

Note: The move transactions are processed only if the Move Transaction Manager is running. .

If you enter a standard receipt, you must specify a Ship-To Location. You then use the Receiving Transactions window to deliver the outside processing items to work in process. In this case, you do not charge and move assemblies in work in process until you enter the delivery transaction in the Receiving Transactions window. See: Receiving Transactions, Oracle Purchasing User's Guide.

Receiving Partial vs. Full Quantities

When you receive outside processing items you can receive full or partial quantities against a particular purchase order shipment. For items linked to PO Move resources, the quantity of assemblies moved equals the quantity you receive.

For partial receipts of purchase order shipments linked to multiple jobs or schedules, you must specify the quantity to receive against each job or schedule. Purchasing does not automatically allocate receipt quantities for you.

Receiving Assembly vs. Resource Outside Processing Unit Type Items

The quantity of outside processing items you receive can relate to the assembly quantity on the job or repetitive schedule in several ways depending on the outside processing item's Outside Processing Unit Type and the outside resource's basis.

If the outside processing item has an Outside Processing Unit Type of Assembly and the outside resource has a basis of Item, you receive one outside processing item for each assembly you receive. If the outside resource has a basis of Lot, you receive one outside processing item for each job or repetitive schedule.

If the outside processing item has an Outside Processing Unit Type of Resource and the outside resource has a basis of Item, you receive the extended quantity (using the outside resource usage rate or amount) of the outside processing item for each assembly you receive.

Resource and Move Transactions

When you receive an outside processing item linked to a resource with a charge type of PO Move, Purchasing enters a move transaction for the assembly on the job or repetitive schedule you charge. You should use outside processing items with Assembly unit types and PO move resources with a basis of Item. Assemblies are moved to Queue of the next operation, or To Move if the resource is in the final operation. You can have only one PO Move resource per operation on a routing.

When assemblies move, the outside operation is being completed for the quantity that moves. These operation completions automatically backflush any material associated with the outside operation that has an Operation Pull supply type, and charge any WIP Move resources associated with the outside operation.

You can use outside processing operations with a serialized job only if the resource charge type is PO Receipt. This is because the serial number must be known. You cannot backflush any serial controlled components at an outside operation with a PO Move resource since the Receipts window does not enable entry of component serial numbers. You can use outside processing operations with a serialized job only if the resource charge type is PO Receipt because the serial number must be defined before moving the assembly. For lot controlled components, they can be backflushed if you set your Backflush Lot Entry setup option to one of the automatic FIFO options in the Parameters window in Work in Process. You must enter move transactions online using the Move Transactions window in Work in Process, if you want to manually record serial and lot numbers for components you backflush.

If you receive outside processing items linked to a job or repetitive schedule with an non-transactable status, such as On Hold or Cancelled, Work in Process gives these transactions an error status. You can use the Pending Move Transactions window in Work in Process to view the errors and resubmit the transactions. Processing Pending Move Transactions.

If Oracle Shop Floor Management is installed, and you are using lot based jobs with network routings, the PO Receipt transaction moves the items to the last operation-not the next operation. Network routings define different paths for the next operation according to the results of the last operation. The next operation cannot be determined before receiving because the routing is dynamic. See:

Creating a Network Routing in the Oracle Engineering User's Guide.

Autocompleting Assemblies and Work Orders

If the outside processing operation is the last operation on the routing, and the resource has a charge type of PO Move, Work in Process automatically completes both full and partial outside processing assembly quantities into Inventory when they are received back from the supplier. When quantities that account for the remaining uncompleted quantity of a work order are received, the status of the work order is updated to “complete-charges allowed."

Note: When a job or schedule with outside processing operations is changed to complete, closed, or canceled status - an informational warning message displays if open purchase orders or requisitions exist for any of the operations.

Assemblies cannot be completed from discrete jobs or repetitive schedules if the To Move intraoperation step of the outside processing operation has a status that disallows a move. If you want to disable autocomplete, however, you can assign a No Move status to the To Move intraoperation step of the outside processing operation, if it is the last operation on the routing.

Autocompletion Validation

When outside processing items are received back from the supplier, Work in Process validates the items before completing them into Inventory. If the assemblies fail validation, the quantities in Queue are moved to the To Move intraoperation step of the outside processing operation, rather than being completed into Inventory. For autocomplete to succeed, the validation process includes:

• Default subinventories and locators must be specified, if they are required by the subinventory.

• For ot number controlled assemblies. a lot number must be specified on the discrete job subinventory.

• Assemblies under serial number control must have their Serial Generation attribute in Oracle Inventory set to dynamic entry at sales order issue.

• The To Move intraoperation step of the outside processing operation cannot have any status that disallows a move, such as No Move status.

• The item revision number must be the BOM revision number.

• Quantities received must be less than or equal to the quantity in the Queue of the outside processing operation plus the user-defined over-completion allowance of the assembly being built on the job.

Consecutive Outside Processing Operations

If you have set up consecutive outside processing operations in your routing, using two different suppliers - after the first supplier has completed work, the assembly is shipped directly to the second supplier. There are two ways you can set up your routing. One method is to create a PO Move resource and a PO Receipt resource, and associate them with the same operation. In the second method, you associate outside processing resources to two consecutive operations. The method launches the workflow to notify the second supplier. When setting up the method, the following model is recommended:

• Use the Ship-To Location to specify that the supplier for the first outside processing operation, ships the completed assemblies directly to the supplier for the second outside processing operation.

• Perform a PO Move resource rather than a PO Receipt from the first outside processing operation to the second outside processing operation.

  This eliminates an unnecessary transaction since material is not actually received at your site.

  The Oracle Internet Supplier Portal application provides the framework to enable buyers and suppliers to communicate business transactions used for outside processing operations. This includes acknowledging purchase orders, rescheduling purchase orders, submitting advanced shipment notices, and notifying buyers and suppliers of shipments. See: Oracle Internet Supplier Portal Implementation Guide.

  The Notify Second Buyer and Supplier workflow is used to notify the buyer, and the next supplier, when the supplier for the first outside processing operation has completed the assemblies. See: Outside Processing Workflows

• When creating consecutive outside processing operations, define only one outside processing resource for each consecutive operation.

  When the supplier completes and submits the Advance Shipment Notice, Oracle Purchasing automatically creates a shipment in the system and sends a notification to the buyer. The Notify Second Buyer and Supplier workflow notifies the buyer and production scheduler that assemblies have been shipped to the second supplier. When the second supplier receives the assemblies from the first supplier, and responds to the workflow - this response triggers a logical receipt in the manufacturer's system. This action causes the assemblies to move into Queue of the second outside processing operation, if the first outside processing resource is PO Move.

Supplier Access to Outside Processing Purchase Orders

Oracle iSupplier Portal provides your outside processing suppliers with access to all of their current purchase orders. They can obtain detailed information on all of their purchase orders, including components, component attachments, associated operations, and operating instructions.

Oracle iSupplier Portal's Supplier Services opens a menu linking to the Orders tabbed window. From here you can query outside processing order information through the Manufacturing Orders tab. Shipment and distribution information is also displayed.

Viewing Outside Processing Orders

The information for outside processing orders displays standard and blanket outside processing purchase orders listed by purchase order number. Suppliers can view:

• Purchase order approval status

• Item number and description

• Job or schedule number

• Quantity ordered and delivered

• Date information

Access to purchase order details

Each purchase number is linked to Purchasing's Purchase Order Detail page displaying purchase order revision number, purchase order type (standard or blanket), order date, order total amount, ship-to location, carrier, currency, bill-to location, payment terms, freight terms, and status.

In addition, you can select the Invoice and Receipt buttons on the Purchase Order Detail page to see related invoices and receipt transactions.

Download Component and Operation Attachments and Instructions

If components have attachments, and if operating instructions are available, you can link to download the attachments and instructions, view them online, and print them.

Update the Promised Date

Suppliers can change the promise date through the Update Promise Date link. This automatically changes the promise date on the purchase order and notifies the buyer and production scheduler.

Download Quality Collection Plans and Collect and Submit Quality Results

You can provide your supplier with access to Quality collection plans. You must first create the collection plan in Oracle Quality and associate it with the Self-Service Quality for Outside Processing transaction. A link then is displayed in the QA Plans column. Selecting this link displays a list of the collection plans that are associated with that purchase order. You can choose to enter Quality results, to view Quality results that have been submitted, or to view attachments for any purchase order listed.

Outside Processing Workflows

To enable you to track your outside processing assemblies from the shop floor to the supplier, Work in Process provides the following four workflows, which automatically send notifications and activate processes during specific points in the outside processing process:

• Intermediate Shipment workflow tracks outside processing assemblies from the shop floor to the supplier.

• Ship and Receive Intermediates workflow notifies the shipping manager and the supplier that outside processing assemblies are ready to ship.

• Notify Second Buyer and Supplier workflow is used when you have two consecutive outside processing operations.

• Change Order Approval Workflow in Oracle Purchasing is used to change date, quantity, or status on the purchase order. If the supplier approves the change, the need by date is updated on the requisition and the purchase order—and a notification is sent to the buyer and supplier.

Outside Processing Workflow Setup

In order to use workflow functionality, you must have Oracle Workflow installed. To enable outside processing workflows, your system administrator must set up the profile option WIP:Enable Outside Processing Workflow. You also must set up the Production Scheduler and Shipping Manager parameters. See: WIP Parameters and Profile Option Summary

Note: To stop the outside processing workflow notifications and but ensure that the automatic trigger of the Requisition Import program for purchase order move transactions runs automatically, ensure the following:

• Set the WIP:Enable Outside Processing Workflows to No.

• Set the WIP:Launch Requisition Import for PO Move profile option to Yes.

Intermediate Shipment Workflow

The purpose of this workflow is to track outside processing assemblies from the shop floor to the shipping dock, and then to the supplier. The workflow is activated when you move assemblies into the Queue intraoperation step of an outside processing operation that has a PO Move resource charge type. It first imports pending requisitions, checks to see how many approved (non-cancelled) purchase orders exist for the outside processing supplier, then notifies the buyer.

Note: Only PO Move initiates the workflow.

If there are from one to three approved purchase orders for that supplier and the buyer wants to proceed with the order(s), the quantities are validated, and a second workflow, the Ship and Receive Intermediates workflow, is initiated. The second workflow notifies the shipping manager and the supplier that the outside processing items are ready to ship.

The workflow initiates the following actions, based on the number of approved purchase orders that it finds:

• If there are no approved purchase orders, the default buyer (or alternatively, the production scheduler) is notified, and the search for approved purchase orders continues. If no default buyer or production scheduler has been defined, the workflow ends.

• If there is only one approved purchase order, a notification is sent to the buyer. If the buyer decides to proceed with the order, the Ship and Receive Intermediates workflow is activated, and the first workflow ends.

• If there are one to three approved purchase orders, a notification is sent to the buyer so that the buyer can decide the quantity to be shipped to each supplier. The total allocated quantity, which must equal the move quantity, is then validated. If the quantity is valid, the Ship and Receive Intermediates workflow is activated for each purchase order.

• If there are more than three approved purchase orders for that supplier, the buyer is notified that there are multiple purchase orders, and the workflow ends.

Ship and Receive Intermediates Workflow

The purpose of this workflow is to notify the shipping manager and the supplier that assemblies are ready to ship to outside processing suppliers for further processing. The workflow is activated during the Intermediate Shipment workflow when the buyer decides to proceed with the order and selects the Proceed button on the notification window.

To enable this workflow, you must first define the Shipping Manager parameter in the WIP Parameters window, and the employee assigned to this role must have a valid user ID (this is set up by the system administrator). The workflow first searches for the shipping manager, and if found, then searches for the supplier's shipping address. It then notifies the shipping manager that the assemblies are ready to ship and relays the shipping address. If the shipping manager decides to proceed with the shipment, the system searches for the supplier contact. If a contact is found, he or she is notified that the assemblies have been shipped (if the supplier contact is not found, the buyer is then notified). The system also searches for the purchase order's Internet address or URL and includes it as a link on the notification so that the supplier has immediate access to the purchase order information. The supplier can use the same notification to send a reply stating how many assemblies were received and whether or not any assemblies were damaged.

If the shipping manager decides not to ship the assemblies, a search is conducted for the production scheduler, and if found, the production scheduler is notified that the assemblies were not shipped. The same notification is also sent to the buyer.

Notify Second Buyer and Supplier Workflow

When suppliers complete outside processing assemblies, they can notify you through Purchasing's Advance Shipment Notice. The Advance Shipment Notice is available through a link on the Supplier Management Portal Supplier Service menu. When the supplier completes the Advance Shipment Notice and submits it, Oracle Purchasing automatically creates a shipment in the system and sends a notification to the buyer.

To enable the workflow notification for this functionality, you must set up the Production Scheduler parameter, which associates an employee with the production scheduler role. The employee must have a valid user ID, which is set up by the system administrator. In addition, if you have two consecutive outside processing operations on a routing, and you want the supplier for the first operation to ship the completed assemblies directly to the supplier for the second operation, you must specify the second supplier's address in the Ship-To Location field on the purchase order.

Note: In order for the supplier's address to be available on the list of values for Purchasing's Ship-To Location field, you must first set up the supplier's address in the Shipping Network Location field on Oracle Payables' Supplier Sites Window. See: Supplier Sites window, Oracle Payables User's Guide.

When the supplier completes the Advance Shipment Notice, a receipt is automatically created and sent to the first supplier, and the Notify Second Buyer and Supplier workflow is activated to notify the second supplier that the assemblies have been shipped.

The system searches for an approved purchase order for the second outside processing supplier, and if it finds the purchase order, it then searches for the production scheduler. If the production scheduler is found, it sends the production scheduler a notification that the assemblies have been shipped from the first supplier. The same notification is also sent to the buyer, and if the buyer decides to proceed with the order, the Ship and Receive Intermediates workflow is activated to notify the shipping manager and the supplier that the assemblies have been shipped.

Change Order Approval Workflow

The Change Order Approval Workflow in Oracle Purchasing is launched for changes on purchasing documents. Changes are updated on the purchase order and then the supplier and buyer are notified.

The workflow first searches for the buyer. If the buyer decides to proceed with changes, the workflow searches for the supplier contact. If the supplier contact is found, it sends a notification. If the supplier contact accepts changes, a notification is then sent to the buyer that the changes were approved. If the new need by date is not approved, you can manually change it. See: Change Order Approval Workflow, Oracle Purchasing User's Guide

To view outside processing workflows

1. Navigate to one of the windows where you can access outside processing workflows.

   You can view the progression and status of the workflows from the Discrete Jobs, View Discrete Jobs, Repetitive Schedules, and View Repetitive schedules windows.

2. From the Tools menu, select View Workflows.

   The View Workflows window displays.

   

3. Select one of the workflows listed on this window and choose View Diagram.

   This action launches your browser and the View Diagram appears.

   This window enables you to select a view of the workflow including Active History, Status Diagram, Participant Responses, and Workflow Details.

   

   

   Caution: The Monitor Diagram may not accurately reflect the workflow status correctly if the concurrent program is processing. The workflow may display no document found when using blanket releases and the following conditions exist:

   • PO creation time is set to At Operation.

   • PO creation time is set to At Job Release and OSP is the first operation.

Changing the Need By Date

The need by date is the date on the purchase order when you expect the completed assemblies to be delivered.

• For discrete and repetitive jobs, the need by date is the first unit start date of the operation, following the outside processing operation. If the outside processing operation is the last operation, then the need by date is the last unit complete date of that operation.

• For lot based jobs, a different logic is used to derive the need by date because network routings have changing first and last operations.

• For Enterprise Asset Manufacturing work orders, the need by date is the last unit completion date of the outside processing operation.

There are several ways to update the need by date. All methods launch the Purchase Order Approval and Requisition workflows to create these changes to purchasing documents. These methods include:

• Defining Need by Date Tolerance parameters in the Work in Process Parameters window. The concurrent program uses these values for updating need by dates.

• Manually changing the date for a specific job by navigating to the Update Need By Date window to launch the workflow.

• Manually accessing the concurrent program to automatically update appropriate records when rescheduling.

Automatic Settings for Need By Date Updates

Need by Date Tolerance parameters, in the Work in Process Parameters window, are used by the concurrent program. See: Defining WIP Parameters If you have values in these Work in Process parameters, the following actions are performed:

• Early Need By Date Tolerance: The number of days prior to the Need By Date. The workflow is launched if:

  New Need By Date value, added to the Early Need By Date Tolerance value, is less than the previous Need by Date

• Late Need by Date Tolerance: The number of days after the Need By Date. The workflow is launched if:

  New Need By Date value, subtracted from the Late Need by Date Tolerance value, is greater than the previous Need By Date

• Early Need By Date Tolerance and Late Need by Date Tolerance: When you fall outside of the tolerance values, the concurrent program initiates the workflow, and the Need By Date is updated on the purchasing documents. The value in the Propagate Job Change to Purchasing is ignored.

Using the Update Need by Date Window

When the Update Need By Date window opens, it displays the Need by Date in the Current Date field for all requisitions and purchase orders associated with that operation. The check box for each operation sequence is enabled if there are existing requisitions and purchase orders with at least one day's difference between the values in the Current Date and New Date fields.

To change Need By Dates for a specific job or schedule

1. Navigate to the Update Need by Date window by selecting Update PO Need By Date in the Operations window.

   

2. To change the Need By Date, enter a value in the New Date column for all appropriate records.

3. Select the check box for the row you want to update, then choose OK.

Using the Update OSP Need-by Dates Concurrent Program

In the automatic method, you can initiate the Update OSP Need-by Dates concurrent program. If you have numerous jobs, updating the need by date manually is time consuming. The concurrent program automatically launches the workflow for Need By Date changes, associated with all appropriate work orders that are rescheduled. The concurrent program considers the tolerances set in the Work in Process Parameters window, see: Defining WIP Parameters.

To initiate the Update OSP Need-by Dates concurrent program:

1. Navigate to the Update OSP Need-by Dates concurrent program from the Discrete or Repetitive menus.

   The Parameter window displays.

2. For discrete jobs, if you are using Oracle Projects or Project Manufacturing—you can search by Project Number and appropriate Task Number.

   

3. In the Days Forward From and To fields, , enter the range of days in the future to consider changes.

   For example, if these values equal 2 days, and your program is scheduled to run daily–it will pick up requirements for jobs and schedules up to 2 days forward. Changes after two days are picked up by the concurrent program when it is scheduled to run next.

4. Choose OK to save your work and display the Request window.

5. Choose Submit to initiate the program.

Printing Documents for OSP Shipment Lines

You can create shipment lines for outside processing (OSP) work orders by running the Manage OSP Shipment Lines concurrent program. Then, when you send components to the outside processing supplier, you can print shipping documents for the shipment lines. The shipping documents help you to track the material at the supplier site.

Using the Manage OSP Shipment Lines Concurrent Program

You can use this concurrent program to generate and cancel the shipment lines for partially finished assembly material and related components for outside processing operations. You can schedule or manually run the program for outside processing operations of multiple production work orders. The program automatically considers the moved quantities and generates shipment lines for the OSP item and the components associated with the OSP operation.

Before you run the concurrent program:

• Set up the OSP item and the component items as shippable.

• Associate components with the OSP step in the routing definition.

• Perform move transactions for the OSP item to generate shipment lines.

• Perform WIP issue transactions or reservations or move order allocations for OSP operation components to generate shipment lines for lots and serial numbers.

The concurrent program creates shipment delivery lines for released and on-hold discrete work orders, which must meet the following requirements:

• Have OSP operations with a shippable OSP item

• Have the resource charge type set to PO Move and PO Receipt

To successfully generate shipment delivery lines using the concurrent program, verify that the following conditions are met:

• The partially finished assembly (PFA) is not lot, serial, or lot and serial controlled.

• Purchase orders are approved and open.

• The purchase order line is not expired.

• The purchase order line is open. The PO line must not be closed or canceled, and should have an existing open quantity.

Calculating OSP Shipment Line Quantity

To derive the quantity for the shipment lines that it will create, the Manage OSP Shipment Lines concurrent program calculates the quantity needed to create shipment lines or the quantity to be canceled for excess shipment lines, both for the partially finished assembly and for its components, and uses the Shipping API to create and cancel shipment lines.

Note the following:

• If a shipment line is not created for the partially finished assembly, then shipment lines are not created for the components.

• If a shipment line is created for the partially finished assembly, but shipment lines are not created for the components per the bill, then the transactions are rolled back and the shipment line is removed for the partially finished assembly.

• If you cancel a shipment line for a partially finished assembly, then the shipment lines for the components are also canceled.

• Even if you cannot cancel a shipment line for a partially finished assembly, you can still cancel shipment lines for the components.

Note: Ensure that you cancel the shipment lines of a partially finished assembly and its components together. In some scenarios a shipment of a partially finished assembly alone is canceled but the components are shipped. In the case where a shipment is created for the remaining partially finished assembly, the application does not support recalculation of required components based on the already shipped quantities.

Using Shipping Reports

You can create and use Oracle Shipping reports as a shipping document set and print them when you ship confirm and deliver the OSP material. These shipping documents, printed with the OSP material item code, quantity, job number, operation number, and OSP purchase order (PO) details, help you when you transport the OSP material and help the OSP vendors identify the material when they receive it.

Print the following Oracle Shipping reports that include OSP shipment line information details:

• Packing Slip Report - This report displays the OSP item, OSP PO, job number, and operation number from each shipment line.

• Bill of Lading Report - This report displays the OSP PO shipment line location as the shipping location and the OSP PO contact location as the delivery location.

• Commercial Invoice Report - This report lists details related to the OSP item, requested quantity, job number, ship-to contact, and ship-from and ship-to locations from each of the shipment lines.

• Vehicle Load Sheet Details Report - This report lists details related to the OSP item, item descriptions, and the ingredient items grouped for that delivery.

You can customize the report layouts according to your business need using the XML publisher. For more information on these reports, see Reports and Processes, Oracle Shipping Execution User's Guide.

To run the Manage OSP Shipment Lines concurrent program

1. Navigate to the Submit Request window.

2. In the Name field, select Manage OSP Shipment Lines.

3. Use the Parameters window to define the request.

   

4. Enter the organization.

5. (Optional) Enter other parameters to filter your request. Note the descriptions for the following parameters:

   • Work Order From - Enter the first work order in the range that you want to search.

   • Work Order To - Enter the last work order in the range that you want to search.

   • Assembly From - Enter the first assembly in the range that you want to search.

   • Assembly To - Enter the last assembly in the range that you want to search.

   • Lines From - Enter the first shipment line in the range that you want to search.

   • Lines To - Enter the last shipment line in the range that you want to search.

   • OSP Item From - Enter the first OSP item in the range that you want to search.

   • OSP Item To - Enter the last OSP item in the range that you want to search.

   • OSP Item Category From - Enter the first OSP item category set in the range that you want to search.

   • OSP Item Category To - Enter the last OSP item category set in the range that you want to search.

   • OSP Operation Start Date From - Enter the earliest OSP operation start date in the range that you want to search.

   • OSP Operation Start Date To - Enter the latest OSP operation start date in the range that you want to search.

6. In the Cancel OSP Shipment Lines field, select one of the following options.

   • No - Ensures that OSP shipment lines are not canceled.

   • Yes - Cancels OSP shipment lines.

     The default value is No.

7. Click OK.

8. In the Submit Request window. click Submit

9. Use the Requests window to confirm that the program runs successfully.

10. Click View Output to view the details of the OSP shipment lines that were created for the assembly and components.

    

To print documents for OSP Shipment Lines

1. Navigate to the Shipping Transactions window to query the shipment lines.

   (N) Order Management > Shipping > Transactions

2. In the Query Manager window, on the Lines tab, in the Source System field, select Outside Processing.

   

3. (Optional) Use the other available criteria in this window to filter your search. For more information about using the Query Manager, see Finding Delivery Lines, Oracle Shipping Execution User's Guide.

4. Click Find.

5. In the Shipping Transactions window, on the Lines/LPNs tab, view the details for the shipment lines that were created using the Manage OSP Shipment Lines concurrent program.

   

   Note: For more information about the Shipping Transactions window, see the following topics in the Oracle Shipping Execution User's Guide:

   • Shipping Transactions Window

   • Overview of Delivery Lines

6. To automatically create deliveries, select one or more lines, right-click, and then select Auto-create Deliveries from the list of options.

   

7. The Delivery column shows the created delivery IDs.

   

8. Click the Delivery tab. Select the line you want to ship confirm.

   Note: For more information, see the following topics in the Oracle Shipping Execution User's Guide:

   • Overview of Ship Confirm

   • Auto Ship Confirm from the Shipping Transactions Window

   

9. Click Ship Confirm.

   The Confirm Delivery window appears. The Document Set field shows Ship Confirm Documents as the documents to be printed for the OSP shipment lines.

   

10. Click OK.

11. The Messages dialog box shows that the delivery is successful. Click OK.

12. Navigate to the Requests window to view the documents.

    

13. Select the request ID for the document you want to view and click Diagnostics.

    

14. In the Request Diagnostics window, click View XML to review the report information.