Select language:
Entering content frame!--a11y-->

Function documentation Determination of Dates/Times 

Use

When generating a purchase requisition or purchase order in SAP APO, the system automatically determines the dates/times.

Integration

When the purchase order or purchase requisition is transferred to the ERP system, the ERP system reschedules it.

Prerequisites

An active integration model is available for purchase orders and purchase order requisitions.

Features

Determination of Dates/Times for Stock Transport Requisitions/Stock Transport Orders in SAP APO

SAP APO calculates the following dates/times:

·  Availability date/time / end date/time (corresponds to end of goods receipt)

·  Start of goods receipt

·  End of transportation

·  Start of transportation

·  End of goods issue

·  Start of goods issue (corresponds to requirement date/time / start date/time)

·  Opening date/time

The delivery date/time (end of transportation) is transferred via APO Core Interface (CIF) to the target location. The objects are rescheduled in the ERP system.

Note

In the case of stock transport orders that were created in SAP APO, you can suppress rescheduling in the ERP system by using an indicator in Customizing. As a prerequisite, shipment scheduling must be active. To activate shipment scheduling, set the Sh. Schd. indicator in the ERP system in Customizing for purchasing under Purchase Order  ® Set Up Stock Transport Order  ® Assign Delivery Type and Checking Rule.
To suppress rescheduling, in SAP APO in the Implementation Guide (IMG) for CIF, choose Application-Specific Settings and Enhancements 
® Settings and Enhancements for External Procurement  ® Purchase Orders, Purchase Requisitions, Schedule Lines, Shipping Not.  ®  Outbound Processing ® Suppress Rescheduling of Stock Transport Orders in Target System.

 

Determination of Dates/Times for Standard Purchase Requisitions and Purchase Orders in the ERP System

The ERP system calculates the following dates/times based on the delivery date/time:

·  Availability date/time / planned date/time

Calculated from the delivery date using the goods receipt processing time, taking the plant calendar into account.

·  Release date/time

If you do not take any resources into account for goods receipt, and if the goods receipt at the destination location is the same in both SAP APO and in the ERP system, and their respective calendars are also the same, the availability date/time is identical in both systems. If resources are taken into account for goods receipt, this can lead to different availability dates/times in SAP APO and in the ERP system. This is due either to the calendar of the resource or to finite scheduling of the goods receipt activity. For more information, see SAP Note 333386.

The opening date/time is not relevant in SNP. Instead, there is a stock transfer horizon in SNP that is used to model a scheduling lead time.

The opening date/time is transferred from SAP APO to the ERP system. Even if the release date/time is in the past, as calculated in SAP APO, it is still transferred to the ERP system. However, if the release date/time is changed manually in the ERP system, it is not integrated back into SAP APO.

Determination of Dates/Times for Stock Transport Requisitions in the ERP System

The following dates/times are calculated in the ERP system based on the delivery date/time:

·  Availability date/time / planned date/time

Calculated from the delivery date using the goods receipt processing time, taking the plant calendar into account.

·  Material availability date

For more information, see the SAP Notes 361308 and 441622.

·  Release date/time

Is copied from SAP APO.

If you do not take any resources into account for goods receipt, and if the goods receipt at the destination location is the same in both SAP APO and in the ERP system, and their respective calendars are also the same, the availability date/time is identical in both systems. If resources are taken into account for goods receipt, this can lead to different availability dates/times in SAP APO and in the ERP system. This is due either to the calendar of the resource or to finite scheduling of the goods receipt activity. For more information, see SAP Note 333386.

The opening date/time is not relevant in SNP. Instead, there is a stock transfer horizon in SNP that is used to model a scheduling lead time.

The opening date/time is also transferred from SAP APO to the ERP system. Even if the release date/time is in the past, as calculated in SAP APO, it is still transferred to the ERP system. However, if the release date/time is changed manually in the ERP system, it is not integrated back into SAP APO.

Determination of Dates/Times for Stock Transport Orders in the ERP System

The ERP system calculates the following dates/times based on the delivery date/time, depending on the alternative:

  1.  Scheduling using planned delivery time

For this, see the section Determination of Dates/Times for Stock Transport Requisitions in the ERP System.

  2.  Scheduling using transportation and shipment scheduling in the ERP system

¡  Availability date/time / planned date/time

Calculated from the delivery date using the goods receipt processing time, taking the plant calendar into account.

¡  Goods issue

Calculated from the delivery date using the transit time, dependent on the route.

¡  Loading date

Calculated from goods issue using the loading time, depending on the shipping point and taking into account the calendar of the shipping point.

¡  Material availability date

Calculated from the loading data using the pick/pack time, depending on the shipping point and taking into account the calendar of the shipping point.

¡  Transportation planning date

Calculated from the loading date using the transportation planning time and depending on the route.

If you do not take any resources into account for goods receipt, and if the goods receipt at the destination location is the same in both SAP APO and in the ERP system, and their respective calendars are also the same, the availability date/time is identical in both systems. If resources are taken into account for goods receipt, this can lead to different availability dates/times in SAP APO and in the ERP system. This is due either to the calendar of the resource or to finite scheduling of the goods receipt activity. For more information, see SAP Note 333386.

If the sum of the transit time, loading time, and pick/pack time in the ERP system does not equal the goods issue and transportation in SAP APO, this leads to different dates/times relevant to MRP at the source location in the ERP system and in SAP APO.

If either the material staging date or the transportation scheduling date is in the past, the date can be rescheduled (forward scheduling) in the ERP system. This also results in a new delivery date.

  3.  Scheduling using transportation and shipment scheduling in SAP APO via RFC

¡  Availability date/time / planned date/time

Calculated from the delivery date using the goods issue processing time, taking into account the plant calendar (here scheduling is still in the ERP system).

¡  Goods issue

Calculated from the delivery date using the transit duration in accordance with the following prioritization:

  i.  If the system finds a transportation lane with a transportation duration > 0, it uses this while taking into account the relevant transportation calendar.

  ii.  Then the system uses conditions to try to determine a transit duration > 0. A customer exit is available for cases where a transportation calendar is to be taken into account. For more information, see SAP Note 376932.

  iii.  Then the system uses the geocoordinates of the locations and the average speed of the means of transport to try to determine a transit duration. A customer exit is available for cases where a transportation calendar is to be taken into account. For more information, see SAP Note 376932.

¡  Loading date

Calculated from goods issue using the loading time dependent on condition maintenance in SAP APO, taking into account the shipping calendar at the location in SAP APO.

¡  Material availability date

Calculated from the loading date using the pick/pack time dependent on condition maintenance in SAP APO, taking into account the shipping calendar at the location in SAP APO.

¡  Transportation planning date

Calculated from the loading date using the MRP lead time dependent on condition maintenance in SAP APO, taking into account the shipping calendar at the location in SAP APO.

If you do not take any resources into account for goods receipt, and if the goods receipt at the destination location is the same in both SAP APO and in the ERP system, and their respective calendars are also the same, the availability date/time is identical in both systems. If resources are taken into account for goods receipt, this can lead to different availability dates/times in SAP APO and in the ERP system. This is due either to the calendar of the resource or to finite scheduling of the goods receipt activity. For more information, see SAP Note 333386.

If the sum of the transit time, loading time, and pick/pack time does not equal the sum of goods issue, transportation, and goods receipt in SAP APO, this leads to different dates/times relevant to MRP at the source location in the ERP system and in SAP APO.

If either the material staging date or the transportation scheduling date is in the past, the date can be rescheduled (forward scheduling) in the ERP system. This also results in a new delivery date.

Note

In the case of stock transport orders that were created in the ERP system, you can suppress rescheduling in SAP APO by using an indicator in Customizing for ERP.

To suppress rescheduling, in Customizing for ERP, choose Integration with SAP Components  ® Advanced Planning and Optimization  ®Application-Specific Settings and Enhancements  ® Settings and Enhancements for External Procurement  ® Outbound Processing of Purchasing Data  ® Suppress Rescheduling of Stock Transport Orders in Target System.

 

 

Leaving content frame