Show TOC

 Adaptation of the Work Order

Use

Once a business partner has changed or created deliveries (transportation PIOs) in the delivery overview, the production PIOs have to be adapted to the changed deliveries and production PIOs have to be created for the new deliveries. The production PIOs also have to be adapted if the customer sends a changed purchase order with new or changed schedule lines from his or her back-end system to SAP SNC, which results in changed or new deliveries in the work order.

Example Example

If a customer changes the quantity or the date/time of a request delivery in the delivery overview, the quantities and dates/times of the request production PIOs that belong to the delivery have to be adapted.

Status changes in deliveries also have to be copied to the production PIOs. If the supplier, for example, rejects a request delivery from the customer, the associated request production PIOs have to be rejected.

End of the example.

To adapt the production PIOs to changed or new deliveries, the Adapt Work Order function is available in SAP Supply Network Collaboration (SAP SNC). You can make settings so that the system automatically executes the adaptation when a work order is saved (for example, upon receipt of a changed purchase order or after a manual change). If the system is not configured for automatic adaptation, the business partner that changed the deliveries has to call the adaptation function manually on the Web user interface (Web UI) of SAP SNC before he or she publishes the work order.

Example Example

If the customer has sent a changed purchase order to SAP SNC and automatic adaptation is not configured, the customer must call the adaptation function on the Web UI before he or she publishes the work order.

End of the example.

Prerequisites

If you want the system to automatically adapt the work order when it saves it, you have to activate the Adapt Work Order validation check ( WO_AUTO_ADAPT_CHANGES ).

Features

Adaptation of the Work Order to a New Delivery

If a business partner has created a new delivery for a primary product (depending on the business partner role, this is a request delivery or a confirmation delivery), the system creates the production PIOs that are required for the new production run, when it adapts the work order.

To determine the dates/times of the production PIOs, the system uses backward scheduling, starting with the shipping date of the delivery. To do this, the system uses the quantity-independent net phase durations and break durations from the work order phases. These durations come from the master data.

The manner in which the system determines the component quantities depends on whether the business partner created the delivery directly or with reference to another delivery, as follows:

  • Direct creation

    Direct creation is when the customer adds a new purchase order schedule line for a purchase order in the back-end system and sends the changed purchase order to SAP SNC.

    Here the system determines the component quantities using the quantity information that is defined in the master data for the production phase (master data).

  • Creation with reference to an existing delivery

    Creation with reference to an existing delivery occurs in the following situations:

    • The customer or supplier uses the negotiation function Change Date/Time and Quantity (counterproposal) or Split Delivery on the Web UI.

    • The customer changes the date/time or the quantity of a purchase order schedule line in the back-end system, and sends the changed purchase order to SAP SNC.

      Here the system uses the current quantity information from the reference for a production phase (not the quantity information from the master data).

    Example Example

    In the master data for a production phase, the production of 10 pieces of primary product is configured to require 20 pieces of an input component. During negotiation of the work order, the supplier realizes that in this production phase, a larger scrap actually occurs. The supplier therefore manually increases the input component quantity to 25 on the Instructions tab page. Thus, 25 pieces are required to produce 10 pieces of the primary product. When adapting the work order, the system uses the current quantity ratio (25 pieces for 10 pieces).

    End of the example.
Adaptation of the Production PIOs to a Quantity Change

The system proportionately adapts the current planned quantity of all production PIOs. Splitting the delivery quantity into two leads to a halving of the component quantities.

Adaptation of the Production PIOs to a Date/Time Change

To determine the dates/times of the production PIOs, the system uses backward scheduling, starting with the shipping date. To do this, the system uses the quantity-independent and phase-independent durations from the phases. If you have only changed the delivery date/time, and not the shipping date/time of a delivery, the production PIO dates/times remain unchanged during adaptation.

Adaptation of the Production PIOs to a Status Change

During adaptation, the system copies the status of the deliveries for the production PIOs that belong to the production run. Examples:

  • If the business partner has rejected a delivery directly (using the Reject function) or indirectly (by creating a counterproposal), the production PIOs also receive the status Rejected .

  • If the business partner has accepted a delivery, the system also accepts the production PIOs.

  • If a delivery is canceled, the system also cancels the production PIOs.

Adaptation of the Production PIOs in the Case of Work Orders with Co-Products

In a production run, there is a delivery for the primary product and for every co-product. The deliveries for the primary product and co-products are independent of one another. You can therefore process the deliveries separately and change the quantities, dates/times, and status independently of each other.

Note: The system only adapts the production PIOs if you have changed the quantities of the primary product delivery and associated co-product deliveries proportionately. In other words, the quantity ratio between a primary product and a co-product must stay the same. If you change quantities in such a way that the quantity ratio between primary product and co-products changes, the system does not adapt the production PIOs. You have to adapt the production PIOs for the affected production run manually on the Instructions tab page. This also applies if you change the status of the primary product PIOs and the co-product PIOs in a varied manner.

Example Example

The system only adapts the production PIOs if you halve the quantities of the primary product deliveries and of all co-product deliveries.

If you only halve the quantity of the primary product delivery, the system does not make adjustments.

If you reject a co-product delivery but not the primary product delivery, the system likewise does not make any adjustments.

End of the example.
Processing of Production PIOs Changed Locally

If a business partner has changed the quantity, the date/time, or the status of a production PIO before he or she changed the delivery, the adaptation function adapts the production PIO as follows:

  • If the shipping date/time has changed, the system adapts the date/time of the production PIO accordingly. The changed date/time of the delivery has priority.

  • If the delivery quantity has changed, the system adapts the current quantity of the production PIO proportionately.

    Note Note

    Note that the adaptation function does not adapt production PIO that have the status EFAD ( Excluded from Adaptation ). A production PIO that was created by a business partner receives the status EFAD if the other business partner creates a counterproposal for the production PIO. For more information, see Negotiation Functions .

    End of the note.

Activities

If automatic adaptation is not configured, you have to call the Adapt Work Order function on the Web UI before you publish the work order. The function is available in on the Work Order Details screen on the Tracking tab page in the delivery overview.