Show TOC Start of Content Area

Function documentation Creating and Changing Sales Orders  Locate the document in its SAP Library structure

Purpose

The process is the same as the previous “Creating or Changing Sales Orders” (see also Creating Sales Orders and/or Changing Sales Orders).

When you create a sales order item, you can enter a delivering plant, or you can copy a system default value (equal value) from the master data (customer, material). There are two situations:

     Company’s own plant:

Enter a plant from the ordering system into the item. This process flow is the same as the previous procedure in which you can only enter your own plants.

     External plant:

You enter a plant from another SAP ERP System within the Business System Group. The system checks whether a CIF integration model is active for sales orders for the combination of material/plant (see also: Customizing for Cross-System Deliveries).

Features

The following steps can be compared to the conventional creation and changing of sales orders.

     The system proposes a delivering plant from the master data, or you enter a delivering plant manually.

Note

If you enter an external plant manually, the system checks whether there is an active CIF integration model for sales orders for the combination of material/plant. If there is no active CIF integration model, the system issues a warning message. If you continue to work with this entry, you cannot continue processing using APO.

Note, that the system only offers you external plants for items, if you have maintained a CIF integration model for the combination of material/plant.

     When you enter an item with an external plant, the availability check and shipment and transportation scheduling are performed in SAP APO, as for the items with your own plants, and the system writes a requirement to the SAP APO system.

     A rules-based ATP check with location determination that can determine your own, external, or your own and external plants and with product substitution, is performed in exactly the same way as for items with your own plants in APO.

     For items with your own plants, a requirement is set in the SAP ERP sales order system and a shipping due date index is written.

     For items with external plants, the system creates an unchecked delivery in the SAP ERP shipping system. In the SAP APO, this delivery then takes on the requirement from the sales order and sets a requirement in the SAP ERP shipping system.

Copying the Result into the Sales Order for Rules-Based ATP

As in the one-system case, the APO system transfers the results of the rules-based ATP check (materials/plants, quantities, deadlines, and schedule lines) to the sales order in the SAP ERP sales order system. The sales order takes on the data and generates subitems with schedule lines. The main item therefore becomes irrelevant for the requirement and the delivery. With regards to requirements, shipping index/deliveries, and/or unchecked deliveries, the sub-items are managed in the same manner as manually created items. This depends on whether the plant found is the company’s own or an external plant.

Example

Prerequisite in the example: The fixed quantity indicator is blank, and the availability check does not take a replenishment lead time into account. (This is displayed in APO as a Checking Horizon).

Enter a required quantity of 7 pc for a date1. Of this quantity, a partial quantity (4 pc) is available on the requested date (date1), and another partial quantity (2 pc) is available at a later date (date2). The remaining quantity (1 pc) will never be available.

The availability check therefore generates two schedule lines: One for date1 with a required quantity of 7 pc and a confirmed quantity of 4 pc, the other for date2 with a required quantity of 0 pc and a confirmed quantity of 2 pc.

You can set up the process in the SAP APO system in such a way that a schedule line is also generated for the remaining quantity (1 piece).

Repeat Availability Check

You repeat the ATP check for the sales order using the SAP ERP sales order system. If an item is checked again, then any corresponding, as yet undelivered sub-items are deleted internally. Afterwards, as when you created the items, the system performs an availability check for the not yet delivered quantities.

Saving the Sales Order in the APO System

When you save the sales order, the changed requirements are updated in the SAP APO system. The old unchecked deliveries are deleted in the shipping system and are replaced by new ones.

For items with external plants, the system creates an unchecked delivery in the SAP ERP shipping system. In the SAP APO, this delivery then takes on the requirement from the sales order and sets a requirement in the SAP ERP shipping system.

Note

If, during the repeat availability check, the system assigns a plant from a different delivery system to the individual items, then the old unchecked deliveries are deleted in the original delivery system and the new unchecked deliveries are created in the newly-determined delivery system.

 

 

End of Content Area