multiple delivery

26.01.2010 of 11

SAP Note 362445 - Effects of doc changes in R/3 on APOshipments

Note Language: English Version: 8 Validity: Valid Since 31.08.2006

Summary

SymptomThe status of a shipment in Advanced Planning and Optimization (APO)changes when you change R/3 documentsthat are contained in a planned shipment.

More TermsTransportation, transportation scheduling

Cause and PrerequisitesShipments depend directly on the documents.

Solution________________________________________________________________________

This is the standard system behavior when you change the

planning objects in the OLTP system.

Process list

________________________________________________________________________

OLTP object: Sales OrderApplication components: APO-INT-SLS, APO-INT-LE________________________________________________________________________

o No.1:OLTP object: Sales OrderChange transaction (OLTP): 'Create'.R/3 status: -APO status: -Behavior (APO): Create sales order

o No.2:OLTP object: Sales OrderChange transaction (OLTP): DeleteR/3 status: -APO status: Sales order not in planned shipmentBehavior (APO): Delete sales order

o No.3:OLTP object: Sales OrderChange transaction (OLTP): DeleteR/3 status: -APO status: Sales order in planned shipmentBehavior (APO): Sales order is deleted

- If the shipment is empty:Deletes shipment

- Otherwise:

26.01.2010 of 11


Status "Shipment modified" (publishing not allowed)

o No.4:OLTP object: Sales OrderChange transaction (OLTP): DeleteR/3 status: -APO status: Sales order in published shipmentBehavior (APO): Sales order is deleted

- If the shipment is empty:Deletes shipment

- Otherwise:Undo shipment release (unpublish)Status "Shipment modified" (publishing not allowed)Alert generates "published shipment has been modified"

o No.5:OLTP object: Sales OrderChange transaction (OLTP): DeleteR/3 status: -APO status: Sales order in published shipment Deliveries createdBehavior (APO): Not possible in R/3 system

o No.6:OLTP object: Sales OrderChange transaction (OLTP): Change (everything)R/3 status: -APO status: Sales order not in planned shipmentBehavior (APO): Change sales order

o No.7:OLTP object: Sales OrderChange transaction (OLTP): Change / not relevant for planningR/3 status: -APO status: Sales order in planned shipmentBehavior (APO): No change

o No.8:OLTP object: Sales OrderChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: -APO status: Sales order in planned shipmentBehavior (APO): As No.3

o No.9:OLTP object: Sales OrderChange transaction (OLTP): Change / not relevant for planningR/3 status: -APO status: Sales order in published shipmentBehavior (APO): As No.7

o No.10:OLTP object: Sales OrderChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: -APO status: Sales order in published shipment

26.01.2010 of 11


Behavior (APO): As No.4

o No.11:OLTP object: Sales OrderChange transaction (OLTP): Change / not relevant for planningR/3 status: -APO status: Sales order in published shipment Deliveries createdBehavior (APO): As No.7

o No.12:OLTP object: Sales OrderChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: -APO status: Sales order in published shipment Deliveries createdBehavior (APO): Not allowed in R/3

o No.12b:OLTP object: Sales OrderChange transaction (OLTP): New item / schedule lineR/3 status: -APO status: Sales order in published shipment Deliveries createdBehavior (APO): New shipment requirement Old shipment unchanged

________________________________________________________________________

OLTP object: DeliveryApplication components: APO-INT-SLS, APO-INT-LE________________________________________________________________________

o No.13:OLTP object: DeliveryChange transaction (OLTP): Create (category without precedingdocument LO)R/3 status: No shipmentAPO status: -Behavior (APO): Create delivery

o No.14:OLTP object: DeliveryChange transaction (OLTP): Create (category with precedingdocument)R/3 status: No shipmentAPO status: Preceding document not in planned shipmentBehavior (APO): Create delivery Reduces preceding document

o No.15:OLTP object: DeliveryChange transaction (OLTP): Create (category with precedingdocument)R/3 status: No shipmentAPO status: Preceding document in planned shipment

26.01.2010 of 11


Behavior (APO): Two cases:

- A) If the delivery quantity is the same as the order quantity,the system creates a delivery from the preceding document andassigns it to planned shipment.

- B) If the delivery quantity is lower than the order quantity,the system creates a delivery with the confirmed quantity andstores it for new planning in the planning pool. The existingsales order is reduced by the confirmed quantity (see a) andalso stored in the planning pool.

The planned shipment is invalidated.

o No.16: (TP/VS delivery allocation)OLTP object: DeliveryChange transaction (OLTP): Create (category with precedingdocument)R/3 status: No shipmentAPO status: Preceding document in published shipmentBehavior (APO): Two cases:

- A) If the delivery quantity is the same as the order quantity,the system creates a delivery from the preceding document andassigns it to the published shipment.

- B) If the delivery quantity is lower than the order quantity,the system creates a delivery with the confirmed quantity andstores it for new planning in the planning pool. The existingsales order is reduced by the confirmed quantity (see A) andalso stored in the planning pool.

The published shipment is invalidated.

o No.17:OLTP object: DeliveryChange transaction (OLTP): Create (category with precedingdocument)R/3 status: Shipment createdAPO status: Preceding document not in planned shipmentBehavior (APO): Not allowed in R/3

o No.18:OLTP object: DeliveryChange transaction (OLTP): Create (category with precedingdocument)R/3 status: Shipment createdAPO status: Preceding document in planned shipmentBehavior (APO): Not allowed in R/3

o No.19:OLTP object: DeliveryChange transaction (OLTP): Create (category with precedingdocument)R/3 status: Shipment createdAPO status: Preceding document in published shipment

26.01.2010 of 11


Deliveries createdBehavior (APO): Not allowed in R/3

o No.20:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: No shipmentAPO status: Delivery not in planned shipmentBehavior (APO): Deletes delivery

o No.21:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: No shipmentAPO status: Delivery in planned shipmentBehavior (APO): As No.3 Deletes delivery

o No.22:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: No shipmentAPO status: Delivery in published shipmentBehavior (APO): As No.4 Deletes delivery

o No.23:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: No shipmentAPO status: Delivery in published shipment Deliveries createdBehavior (APO): As No.4 Deletes delivery

o No.24:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: Shipment createdAPO status: Delivery not in planned shipmentBehavior (APO): Not allowed in R/3

o No.25:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: Shipment createdAPO status: Delivery in planned shipmentBehavior (APO): Not allowed in R/3

o No.26:OLTP object: DeliveryChange transaction (OLTP): DeleteR/3 status: Shipment createdAPO status: Delivery in published shipmentBehavior (APO): Not allowed in R/3

o No.27:OLTP object: Delivery

26.01.2010 of 11


Change transaction (OLTP): DeleteR/3 status: Shipment createdAPO status: Delivery in published shipment Deliveries createdBehavior (APO): Not allowed in R/3

o No.28:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: No shipmentAPO status: Delivery not in planned shipmentBehavior (APO): Change delivery

o No.29:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: No shipmentAPO status: Delivery not in planned shipmentBehavior (APO): Change delivery

o No.30:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: No shipmentAPO status: Delivery in planned shipmentBehavior (APO): As No.7

o No.31:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: No shipmentAPO status: Delivery in planned shipmentBehavior (APO): As No.3

o No.32:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: No shipmentAPO status: Delivery in published shipmentBehavior (APO): As No.7

o No.33:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: No shipmentAPO status: Delivery in published shipmentBehavior (APO): As No.4 Deallocates delivery from shipment

o No.34:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: No shipmentAPO status: Delivery in published shipment Deliveries createdBehavior (APO): As No.7

o No.35:

26.01.2010 of 11


OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: No shipmentAPO status: Delivery in published shipment Deliveries createdBehavior (APO): As No.4 Deallocates delivery from shipment

o No.36:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: Shipment createdAPO status: Delivery not in planned shipmentBehavior (APO): As No.7

o No.37:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: Shipment createdAPO status: Delivery not in planned shipmentBehavior (APO): As No.7

o No.38:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: Shipment createdAPO status: Delivery in planned shipmentBehavior (APO): Not relevant / integration model error

o No.39:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: Shipment createdAPO status: Delivery in planned shipmentBehavior (APO): Not relevant / integration model error

o No.40:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: Shipment createdAPO status: Delivery in published shipmentBehavior (APO): Not relevant / integration model error

o No.41:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / schedule linesR/3 status: Shipment createdAPO status: Delivery in published shipmentBehavior (APO): Not relevant / integration model error

o No.42:OLTP object: DeliveryChange transaction (OLTP): Change / not relevant for planningR/3 status: Shipment createdAPO status: Delivery in published shipment Deliveries createdBehavior (APO): As No.7

26.01.2010 of 11


o No.43:OLTP object: DeliveryChange transaction (OLTP): Change quantity / dates / itemsR/3 status: Shipment createdAPO status: Delivery in published shipment Deliveries createdBehavior (APO): No change allowed

o Nr.43a:OLTP object: DeliveryChange transaction (OLTP): Post goods issueR/3 status: -APO status: Delivery not in shipmentBehavior (APO): Deletes delivery

o No.43b:OLTP object: DeliveryChange transaction (OLTP): Post goods issueR/3 status: -APO status: Delivery in shipmentBehavior (APO): Sets delivery to quantity 0

________________________________________________________________________

OLTP object: ShipmentApplication components: APO-INT-LE________________________________________________________________________Basic change of behavior with Note 958175:Up to now, you created an R/3 shipment in APO using theassigned packaging material and its reference to an APO meansof transport. However, since many resources of the means oftransport type exist, the first of the existing resources wasselected. This inaccuracy caused problems in many scenarios.

o No.44:OLTP object: ShipmentChange transaction (OLTP): Choose 'Create'.R/3 status: -APO status: Deliveries not in planned shipmentBehavior (APO): Shipment is simplified

o No.45:OLTP object: ShipmentChange transaction (OLTP): Choose 'Create'.R/3 status: -APO status: Deliveries in planned shipmentBehavior (APO): As No.3 Shipment is simplified

o No.46:OLTP object: ShipmentChange transaction (OLTP): Choose 'Create'.R/3 status: -APO status: Delivery in published shipment Deliveries createdBehavior (APO): As No.4

26.01.2010 of 11


Shipment is simplified

o No.47:OLTP object: ShipmentChange transaction (OLTP): DeleteR/3 status: -APO status: Deliveries not in planned shipmentBehavior (APO): No action

o No.48:OLTP object: ShipmentChange transaction (OLTP): DeleteR/3 status: -APO status: Deliveries in planned shipmentBehavior (APO): No action Status not possible in APO

o No.49:OLTP object: ShipmentChange transaction (OLTP): DeleteR/3 status: -APO status: Delivery in published shipment Deliveries createdBehavior (APO): Deletes shipment

o No.50:OLTP object: ShipmentChange transaction (OLTP): ChangeR/3 status: -APO status: Deliveries not in planned shipmentBehavior (APO): creating shipment

o No.51:OLTP object: ShipmentChange transaction (OLTP): ChangeR/3 status: -APO status: Deliveries in planned shipmentBehavior (APO): As No.50

o No.52:OLTP object: ShipmentChange transaction (OLTP): ChangeR/3 status: -APO status: Delivery in published shipment Deliveries createdBehavior (APO): Planned shipment-relevant changes made Creates shipment again

o No.53:OLTP object: ShipmentChange transaction (OLTP): Set shipment endR/3 status: -APO status: Delivery in published shipment

o Deliveries createdBehavior (APO):

- Deletes shipment

26.01.2010 of 11


- Deletes delivery, unless GI posted

________________________________________________________________________

OLTP object: Purchase order / stock transfer order / inbounddeliveryApplication components: APO-INT-PUR, APO-INT-SLS, APO-INT-LE________________________________________________________________________

o No.70:OLTP object: Purchase order / stock transfer order / inbounddeliveryChange transaction (OLTP): All processing typesR/3 status: All statusesAPO status: All statusesBehavior (APO): Similar to behavior in OLTP object sales order or delivery:

Exception: When you create an outbound delivery for a stock transfer order,the shipment is not validated if the quantity deviates.

________________________________________________________________________

OLTP object: Delivery schedule lines / shipping notificationApplication components: APO-INT-PUR, APO-INT-SLS, APO-INT-LE________________________________________________________________________

o No.90OLTP object: Delivery schedule lines / shipping notificationChange transaction (OLTP): All processing typesR/3 status: All statusesAPO status: All statusesBehavior (APO): Similar to behavior in OLTP object sales order or delivery:

Header Data

Release Status: Released for CustomerReleased on: 01.09.2006 07:48:12Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component SCM-APO-VS Vehicle Scheduling

Valid Releases

26.01.2010 of 11


Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 46C 46C 46C

SAP_APPL 470 470 470

SAP_APPL 500 500 500

SAP_APO 30 30A 30A

SAP_APO 310 310 310

SCM 400 400 400

SCM 410 410 410

Related Notes

Number Short Text

566319 Composite SAP consulting note APO TP/VS

multiple delivery

Documents