/SAPAPO/SCHED_TEST - Simulation of Transportation and Shipment SchedulingCL_GUI_FRONTEND_SERVICES - Frontend Services CPI1466 during Backup
This documentation is copyright by SAP AG.
You use this report to simulate Transportation and Shipment Scheduling. The simulation is suitable for the following applications:
- Testing the usage of scheduling data (master data and Customizing)
- Parallel to master data and Customizing maintenance, you can test the effect of these changes on scheduling, without having to execute the transactions (such as sales order processing) that use scheduling. You should be aware that scheduling temporarily stores specific data once for performance reasons. If changes to the master data or Customizing have no effect on the scheduling results, you can initialize the buffer used by scheduling with the report /SAPAPO/SCHED_BUFFER_RESET.
- Analysis of the scheduling of application documents that can determine the field catalog necessary for scheduling from the data that exists in SAP APO.
- This applies to SD documents in SAP R/3 (for example, sales orders) and, as of SAP CRM 3.0, to sales orders in SAP CRM.
Scheduling is used within Global Available-to-Promise (Global ATP). Scheduling is also used outside Global ATP; for example, to schedule SD documents, deliveries, and stock transport orders in SAP R/3, and VMI orders in SAP APO.
You make the following settings on the initial screen of the report:
- On the Scope of Input tab page, you can choose between the options Enter Attributes and Read Attributes from Database.
- If you have chosen Enter Attributes, scheduling takes account of all the data you entered on the other tab pages. You need to enter data on at least one of the following tab pages: Condition Fields, Prestep Fields, or Additional Fields.
- If you have chosen Read Attributes from Database, you enter the Item GUID in the Standard Value for Existing Item screen area or you fill the External Logical System, External Order, and Order Item fields. Enter a ten-digit value in the External Order field. Fill it up with leading zeros, if necessary. The data on the Condition Fields, Prestep Fields, and Additional Fields tab pages is not taken into account.
- You enter the following data on the General Fields tab page:
- The entry point date. This indicates which date type and which time are used to start scheduling.
- The entry point date is required for scheduling so you must specify it.
- An additional entry point date, because scheduling is not reversible, in general.
- If you do not specify an additional entry point date and start scheduling from a delivery date to calculate a material availability date, and then start scheduling anew from this material availability date, the newly calculated delivery date generally differs from the original delivery date. This is due to the different working times.
- If you specify an additional entry point date, scheduling starts from this date. If the result of this scheduling is the entry point date, among other things, the result is adopted; otherwise, scheduling is started anew from the entry point date.
- You can enter the material availability date as the entry point date and the delivery date as the additional entry point date, for example. In this case, the system performs backward scheduling starting from the delivery date. If the material availability date entered cannot be adhered to within this scheduling, the system performs forward scheduling anew, starting from the material availability date.
- The earliest permissible date
- The earliest permissible date is used as the lower date limit. If a date results from the scheduling calculation that is before the earliest permissible date, the earliest date of all those calculated is set to the earliest permissible date and forward scheduling is performed starting from there.
- If you do not specify a date limit, the scheduling results might include dates in the past.
- For example, you have set the earliest permissible date to the current time and entered a delivery date as the entry point date. If, within backward scheduling starting from this delivery date, the system determines a material availability date in the past, the material availability date is set to the current time and forward scheduling is performed from there.
- The predefined rule strategy
- You should not change this.
- You enter the data for scheduling in the SAP standard condition fields on the Condition Fields tab page.
- On the Prestep Fields tab page, you enter the attributes required for determining the scheduling master data if master data keys are given from external OLTP systems (such as SAP R/3 and SAP CRM). A master data key might be the unloading point for a ship-to party. The goods receiving hours can be determined from this.
- On the Additional Fields tab page, you can enter any additional data that is transferred to scheduling using the field catalog.
- On the Analysis tab page, you define the following:
- Whether the results and log display should be displayed after scheduling
- How often scheduling should be called using the specified data
- This field is only taken into consideration if you have set the Without Output indicator. If you call scheduling more than once, you can analyze how program changes in customer exits for scheduling affect performance (transaction SE30).
Results and log display for Transportation and Shipment Scheduling
TXBHW - Original Tax Base Amount in Local Currency General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 7750 Date: 20200225 Time: 065227 sap01-206 ( 47 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.