A sales order can be created

• by transfer from SAP R/3
• by creating a VMI sales order in SAP APO

If data is taken from a preceding document (quotation, bid, sales order, delivery), this results in an update of requirements records in SAP APO.

Restriction:
If rules based ATP is activated, data will not be consistently transferred from a quotation to a sales order as this function is not implemented in SAP R/3.
Rules based ATP may therefore not be carried out on the quotation.

The customer scheduling agreement is a customer outline agreement in which the delivery quantities and delivery dates are agreed upon and fixed. The delivery quantities and delivery dates are given in the form of a delivery schedule. The ATP check takes place at the item level analogous to the sales order. Due to delivery scheduling it may be possible that the system can only confirm the quantity at a later date. In this case, the SAP R/3 system generates a second delivery schedule with the confirmed quantity for the date determined.
The scheduling agreement using the basic method for ATP check is supported.

In quotations, the delivery time is used to agree a guaranteed maximum delivery time as of the placement of an order. If you create an order with reference to a quotation or a contract in which a delivery time has been agreed the system uses this value in the order item. You can specify delivery times at the header and item level. The delivery time at the header level influences the delivery times of all quotation and contract items. However, for each individual item you can specify a delivery time that deviates from the delivery time given at the header level.

Every process that runs in SAP R/3 for the availability check also runs for the basic method of the SAP APO ATP check, but without rules-based ATP.

Using the sales document type in SAP R/3 you can control which of the following are taken into account: the customer material info record, the order probability, credit limits, the scope of the incompleteness log, the roles of partners, shipping and transportation scheduling, delivery blocks, and shipping conditions (for ATP check and delivery scheduling). Using SAP APO does not alter this procedure.

SAP R/3 provides all the necessary sales order data for the ATP check to SAP APO.

Price determination, text determination, completion rules, the scope of the incompleteness log, the roles/determination of partners, delivery relevance and the determination of weight and volume (for the delivery schedule) are all carried out in SAP R/3. Using SAP APO does not alter this procedure.

Additional Information:
When using different rule controls (for example, rules-based ATP check) for sales document types, it is recommended to create your own sales document types in SAP R/3. A mixture of item types, for example free-of-charge delivery and discount-in-kind item, is not possible with the rules-based ATP check in SAP APO.

Restriction:
For a free-of-charge delivery item, price determination is carried out because the item type is changed to TAN. A mixture of item types is not supported.

If you create a free-of-charge delivery manually, the item type is retained with the basic method of the ATP check, for example item types KL, NORM, KLN.

If the customer wishes to return damaged or sample goods, you can enter these as returns in the system. The goods are booked into stock (for example, blocked stock returns). Returns are a sales document (order type RE), and trigger a delivery (returns delivery). After approval of the returns you can create a credit entry with reference to the returns. If the customer wants a replacement material you can generate a free-of-charge delivery with reference to the returns. Returns can lead to an increase of stock in SAP APO after the quality control.

The credit limit and the delivery block are taken into account independently of SAP R/3 Customizing (requirements relevance/no requirements relevance) when saving the sales order. Depending on the settings chosen, when saving the sales order a message is generated, the delivery is blocked or no confirmed quantities are written to SAP APO.

Service items (item type TAX) in the sales order are not relevant to SAP APO.

An availability check also takes place in SAP APO at the plant level or storage location level. Restriction:
Only material with availability 02 (individual requirements) is transferred to SAP APO via the integration model (CIF). There is no transfer of materials with MRP total requirements and the system does not give any warning of this.

Changes that are relevant for requirements are transferred to SAP APO. The following fields are relevant for requirements and always trigger an ATP check:

• Plant
• Requirements type
• Date
• Order quantity (-> change in weight)
• Material number
• Batch
• Valuation type
• Conversion factor for quantities
• Shipping point
• Route
• Reason for rejection
• Quantity fixed indicator
• Order probability
• Project number

Three cases for transfers of data changes that are not relevant to requirements are implemented as standard:

• Delivery priority
• Goods recipient
• Change of configuration

The replacement of the material number in a customer order results in a restriction of SAP APO functions if this material is known in SAP APO.