Ansicht
Dokumentation

APO-ATP-BF: Transportation and Shipping Scheduling ( RELNAPO_30A_SP1_ATP-BF1 )

TXBHW - Original Tax Base Amount in Local Currency SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.

Short text

APO-ATP-BF: Transportation and Shipping Scheduling

Use

The automatic scheduling of shipping activities and transportation is possible in APO as of Release 3.0A (First Customer Shipment and Support Package 1).

Shipping Scheduling

In shipping scheduling, the system considers those operations necessary for initiating the transportation of goods. These include the loading and the picking/packing. The availability and loading dates are determined using shipping scheduling.

Transportation Scheduling

In transportation scheduling, the system considers all dates used for preparing and carrying out the transportation. This includes the transportation lead time, transportation duration and in the event of stock transfers, the unloading or transfer of goods. The goods issue date and the planning date are determined from the requested delivery date in transportation planning. If the system carries out forward scheduling then the possible delivery date is also calculated.

The following dependencies may arise for the Supply Chain Cockpit and Transport Planning or Vehicle Scheduling when the transportation duration is determined.

If the system does not find the relevant values for determining the duration of the transportation in the conditions, it determines this using the transportation lanes and vehicles maintained in the Supply Chain Cockpit.

If a vehicle has not been maintained, the duration of the transportation is determined by standard default settings with the help of an automatic calculation:

Distance (is determined as the crow flies from the location (geographical data: latitude and longitude) of the vendor and the transportation zone (also contains a location) of the ship-to party)

Vehicle

Average speed

Vehicle-dependent surcharge on the distance (as the crow flies)

The terms used in scheduling are briefly defined below. A distinction is made between

Times (durations) which are necessary to carry out certain activities

To calculate scheduling, the system requires empirical values that you define in the form of

Planning lead time

Loading time

Pick/pack time

Transportation duration

Duration of unloading and transfer (important for stock transfers)

In-house activities such as picking/packing and loading are calculated on the basis of the shipping calendar entered in the location master.

The transportation activities are calculated on the basis of the transportation calendar that is assigned to a transportation line. If no transportation line is found the system performs without a calendar.

Consideration of goods receiving hours will not be supported until the next APO release.

Dates which are calculated on the basis of these times

Material availability date

Planning date

Loading date

Goods issue date

Delivery date

Process

In the order entry a requested delivery date can be specified for every schedule line of an item. The customer should receive the goods by this date. In order processing the system can schedule automatically when the requested shipping activities like picking, loading and transportation should begin so that the requested delivery date can be met.

Scheduling is carried out backwards, starting from the requested delivery date. For that reason it is also described as backward scheduling.

If the system determines during this scheduling that the material availability date or the planning date is in the past, it automatically carries out forward scheduling in order to determine a delivery date that can be confirmed.

Backward scheduling is carried out first starting from the requested delivery date and looks like this:

Requested delivery date transportation duration = goods issue date

Goods issue date loading time = loading date

Starting from the loading date two further dates are determined: the planning date and the material availability date

Loading date planning lead time = planning date

Loading date pick/pack time = material availability date

The transportation and shipping scheduling type is determined using the condition technique. Condition types are grouped in a scheduling procedure that is firmly fixed. The sequence of condition types within the procedure is also firmly fixed.

You create scheduling steps in the master data of the transportation and shipping scheduling, that is, maintain condition records specifically for a condition type. You can enter concrete values for the key combination through the selection of a condition type. Furthermore, you maintain the duration of the condition records. Maintain the scheduling step from SAP Easy Access via Master data

-->Master Data for Transportation and Shipment Scheduling--> Create Scheduling Step

Effects on Customizing

Condition Technique

Transportation and shipping scheduling is carried out in APO using the condition technique.

Unlike transportation and shipping scheduling in the R/3 system, you have the following advantages in APO thanks to the condition technique:

You can maintain the times flexibly

Unlike in the R/3 system you have no difficulties with different calendar types

You have less Customizing expense

Condition Types

The condition type carries out a particular aspect of transportation and shipping scheduling in APO.

The condition types are firmly coded and are delivered as follows

Condition Types Delivered

Condition Type	Description
LEAD	Planning lead time

LOAD ,, Loading time

PICK ,, Pick/pack time

TRAN ,, Transportation duration

UNLD ,, Duration of unloading and transfer

Using the condition tables you can store condition records for every condition type.

Define Condition Tables

You define condition tables individually. A condition table determines the combination of the fields (key). The combination makes up a single condition record. The system stores the specific condition data that you enter in the system in a condition record.

Example

The condition table for planning could, for example, contain the following fields:

ALAND (Delivering country)

AZONE (Delivering transportation zone)

LLAND (Destination country)

LZONE (Destination transportation zone)

VSBED (Shipping conditions)

The first four fields define a relationship between delivering and destination location. The last field defines the shipping conditions.

You create condition tables in Customizing for Global ATP via Transportation and Shipment Scheduling Define Condition Table for Scheduling.

Define Accesses

The order of the accesses controls the priority of individual condition records. The system is informed via the accesses where first and where next a valid condition record should be looked for. For every condition type for which you create condition records there is a firmly coded access sequence. You should set the exclusive indicator when defining several accesses. This controls that no more condition tables are evaluated after the first successful access.

You define the access to the condition records in Customizing for Global ATP via Transportation and Shipment Scheduling Maintain Access for Scheduling.

Define Scheduling Control

In the scheduling procedure the condition types are firmly grouped. The sequence of the condition types within the procedure is defined. Only in the control can you exclude condition types from access to the condition table via condition. Make this setting in Customizing for Global ATP via Transportation and Shipment Scheduling Maintain Control for Scheduling.

Interfaces

In order that transportation and shipping scheduling can be used as a central service in APO you have to make settings for Customizing for the interfaces. Via Customizing for the interfaces

Customizing entries of a calling system or a preceding system are assigned to the corresponding Customizing entries in APO

Customizing entries are checked for consistency, especially if these have to be available not only in APO but also in the calling system or the preceding system

You maintain the following settings in Customizing for Global ATP via Transportation and Shipment Scheduling Interfaces.

Assign Transportation Zones to Locations

Transportation and shipping scheduling generally works with locations when determining a transportation lane between the source and destination locations (for example, plant and ship-to party). In addition, distances between locations are determined via the geographical coordinates.

If a location does not have geographical coordinates (that is it has no latitude or longitude), the system attempts to derive the geographical coordinates from the attributes of a location. It is possible that transportation zones have geographical coordinates. You assign the transportation zone of the calling system or preceding system to a location.

Assign Default Vehicle Type to Shipping Conditions

When calculating transportation distances and durations, APO scheduling works on the basis of locations with distance surcharges (as the crow flies) as well as an average speed that depends on the respective vehicle type. You assign a default vehicle type to the shipping conditions here in order to make this calculation.

Carry out Consistency Check

A check is made as to whether the Customizing entries referred to in APO are also (still) available in the respective logical system.

The following particularly critical Customizing entries are checked using this report:

Shipping conditions

This is used to derive the default vehicle

Transportation zone

This is used to determine the location of a ship-to party

Carry out Field Mapping

Condition fields that are transferred in the interface table /SAPAPO/ATPFIELD can be displayed via a mapping table to a condition field of /SAPAPO/KOMGU.

Maintain Weight Groups and Volume Groups for Scheduling

You can assign a weight group (or a volume group) to the gross weight (or volume) of a document item. This is required since it is not the weight (or volume) but the weight group (or volume group) which is in /SAPAPO/KOMGU.

In order to carry out the settings for scheduling you must be assigned to the SAP_APO_SCHED_CU role.

Ansicht Dokumentation