SAP TM 8.0 IMG Help

SAP System
______________________________________________________________
6.1 Transportation Management
6.1.1 Master Data
______________________________________________________________
SAP AG 1
SAP System
______________________________________________________________
6.1.1.1 General Settings
______________________________________________________________
SAP AG 2
SAP System
______________________________________________________________
6.1.1.1.1 Define Equipment Groups and Equipment Types
Use
In this IMG activity, you can define equipment groups and equipment types.
You can use equipment types in the following areas:
- in the definition of the carrier profile to describe the kind of equipment that is owned by
the carrier
- In the definition of forwarding order or forwarding quotation items of the type Container
After you have entered the equipment group, the equipment type, and the number of
containers (pieces) on the forwarding order user interface, the system calculates the tare
weight and capacity in TEU based on the data you have defined in this Customizing
activity.
- in the definition of freight unit building rules
In this case, the system uses the physical properties of the equipment type and group that
you define in this Customizing activity instead of the planning-relevant quantities.
You can use equipment groups to group equipment types into categories.
Requirements
You have activated business function Foundation for External Transportation Management System
(SCM_SCMB_TM_FND1).
Standard settings
We deliver the CN equipment group with 32 default container types.
Activities
Define equipment groups and assign equipment types to them.
Example
You want to classify the containers that your company owns. You define an equipment group
CN for containers. There are, for example, 10-foot and 20-foot containers. For the equipment
group CN you define the equipment types 22G0 and 22R1 with physical properties, capacities,
and temperature settings for your containers.
______________________________________________________________
SAP AG 3
SAP System
______________________________________________________________
6.1.1.1.2 Define Number Range Intervals for One-time Locations
Use
In this IMG activity, you can define the number range intervals for one-time locations.
The system uses number range intervals of the type "internal" to automatically assign a number
of the number range interval to one-time locations. Therefore, you must define at least one
number range interval of the type "internal".
The system does not make explicit use of number range intervals of the type "external" in this
context. However, for documentation purposes, it may make sense to define such intervals to
make clear that these numbers are reserved for manually created locations or for locations that
have been transferred to SAP Transportation Management (SAP TM) via the Core Interface
(CIF). Therefore, the definition of number range intervals of the type "external" is optional.
Activities
- You must define a number range interval of the type "internal".

This number range interval must only contain numeric strings.
- You can define one or more number range intervals of the type "external".
This number range interval can contain alphanumeric strings.
Note: You must ensure that the individual number range intervals do not overlap.
Example
Possible definitions of number range intervals can be:

No From Number To Number Current No. Ext
01 00000000000000000000 00000000009999999999 0 (automatically assigned) not
set (internal)
02 A0000000000000000000 ZZZZZZZZZZZZZZZZZZZZ 0 (automatically assigned)
set (external)
Note
In the standard system, all roles have been configured so that users assigned to them can read
the details of locations as well as one-time locations. If this does not meet your requirements,
you can reconfigure the roles.
If you reconfigure the roles, you should ensure that all roles are configured so that users
assigned to them can at least display the details of one-time locations.
For example, if you want to define a role that is used to display all locations starting with the
characters A through to K and you have defined the number range interval for one-time
locations as shown in the example above, you should configure the APO Authorization
______________________________________________________________
SAP AG 4
SAP System
______________________________________________________________
Object: Master Data, Locations (C_APO_LOC) authorization object as follows:

- Under Activity select at least the Display indicator
- Under Location enter the intervals for the locations that can be displayed for this role.
For example, enter the following:
From To
00000000000000000000 00000000009999999999
A K
6.1.1.2 Organizational Management
6.1.1.2.1 Organizational Model
6.1.1.2.1.1 Create Organizational Model
Use
In this IMG activity, you can create the organizational model of your organization. The
organizational model is based on individual organizational units, which can be defined in detail
in this IMG activity.
On the Description tab you can specify the organizational unit function and role to define the
organizational unit in more detail. For example, you can specify Sales as the organizational unit
function and Organization as the organizational unit role. The organizational unit that you
created in this case is a sales organization.
Activities
- You define the validity period for the organizational unit.

- You create the organizational unit.
- You specify the organizational unit function and role.
- You create other organizational units and assign them to your organizational unit.
- You create jobs and positions to which you assign staff to.
- You assign staff to organizational units.
______________________________________________________________
SAP AG 5
SAP System
______________________________________________________________
6.1.1.2.1.2 Change Organizational Model
Use
In this IMG activity, you can change the organizational model of your organization.
Requirements
In the IMG activity Create Organizational Model, you have created an organizational model.
Example
Examples of possible changes are:

- Changes to the organizational unit function and roles
- Changes to the organizational structure
- Changes to staffing assigned to organizational units
6.1.1.2.1.3 Create and Merge Organizational Hierarchy
Use
In this Customizing activity, you can upload definitions of organizational hierarchies from SAP
ERP or SAP Supply Chain Management (SAP SCM) systems into SAP Transportation
Management (SAP TM). For more information, see the Create and Merge Organizational
Hierarchy from SAP ERP or SAP SCM.
6.1.1.3 Transportation Network
6.1.1.3.1 Location
______________________________________________________________
SAP AG 6
SAP System
______________________________________________________________
6.1.1.3.1.1 Activate Change Documents
Use
In this IMG activity, you activate change documents for locations.

When you set the corresponding indicator, the system creates a change document for every
change in the master data fields that can be changed by the user. The change document also
logs the value of the field before a change is made. This allows you to trace the way in which
the field was changed at a certain time.
If there is a high volume of data, change logging using change documents can affect
performance.
Standard settings
In the standard system, the logging of changes with change documents is not active for
locations.
6.1.1.3.1.2 Configuration for Alternative Location Identifiers
Use
In this Customizing activity, you can make configurations for alternative location identifiers. You
can configure the following:
- Define location scheme agencies
This configuration is optional. The agencies that you define must represent organizations
that maintain standardized identification schemes for locations. For more information, see
the 'Requirements' section.
- Define alternative location identifier types (ALI types)
ALI types distinguish between several identification schemes that can be used to identify
locations and can therefore be used to assign alternative location identifiers to locations.
- Define code lists for specific ALI types
For each ALI type, you can create a code list. Code lists are useful for project-specific
identification schemes or if you intend to restrict the identifiers to a subset of a
standardized identification scheme.
If you define a code list, you have to select the identifiers that refer to the ALI type from
the code list. If you do not define a code list, you can freely choose the identifiers.
______________________________________________________________
SAP AG 7
SAP System
______________________________________________________________
Requirements
If you intend to assign alternative location identifiers that refer to standardized identification
schemes, you must define the location scheme agency IDs in this Customizing activity under
Define Location Scheme Agencies.
You define an agency by specifying a 3-digit code and a description. The 3-digit code must
correspond to an entry of the United Nations EDIFACT data element 3055 (DE 3055).
Activities
- To define ALI types, you must carry out the following activities:
1. Under Define Types of Alternative Location Identifiers, enter a 6-digit alphanumerical
code and a description.
2. Assign a location scheme agency ID (optional step).
Note that if you want to refer to location scheme agency IDs, you must have defined these
first. For more information, see the 'Requirements 'section.
3. Assign a number to the ALI type (optional step).
4. Save your entries.
The system displays the ALI type in the location master on the Alt. Identifiers tab page.
- To define code lists for specific ALI Types, you must carry out the following activities:
1. Under Define Types of Alternative Location Identifiers, select the row of the ALI type
for which you want to define a code list.
2. In the navigation area on the left side, double-click the activity Define Code Lists for
Specific ALI Types.
3. Enter the identifiers that you want to use with the ALI type.
4. Enter a description for the identifiers.
The system accepts these identifiers in combination with the chosen ALI type, when you
enter them in the location master on the Alt. Identifiers tab page. In addition, you can
select the identifiers from the code list when using search help.
6.1.1.3.2 Transportation Lane
______________________________________________________________
SAP AG 8
SAP System
______________________________________________________________
Use
In this IMG activity, you activate change documents for transportation lanes.
performance.
Standard settings
transportation lanes.
6.1.1.3.2.2 Define Transportation Mode
Use
In this Customizing activity, you can define transportation modes.
Example
Transportation modes can be road, rail, air, or sea.
6.1.1.3.3 General Settings for Transportation Network Determination
Use
In this IMG activity, you can do the following settings:

- Transportation lane determination
Here you define what hierarchy the lane determination prioritizes when searching for
______________________________________________________________
SAP AG 9
SAP System
______________________________________________________________
You can set the Consider Hierarchical Relationships Between MTrs First indicator to
control that the lane determination considers the means of transport hierarchy first before
considering the hierarchies of the source and destination locations or zones.
In addition, you can control the order in which the lane determination considers the source
and destination locations or zones by setting the Consider Source Hierarchy First indicator.
- Transshipment location determination
If you set the Consider Directly Connected Transshipment Locations Only indicator, the
system only takes into account direct connections between transshipment locations during
transportation network determination. This indicator does not influence the assignment of
source locations and destination locations to transshipment locations. The system assigns
source locations and destination locations to transshipment locations via transportation zones
taking into account indirectly connected transshipment Locations.
Requirements
You have defined the following objects for the transportation lane determination:
- Transportation lanes
- Hierarchies for:
- the means of transport
- the source locations or zones
- the destination locations or zones
Standard settings
In the standard system, the Consider Hierarchical Relationships Between MTrs First indicator is
set.
Example
The following examples show how the two indicators for the transportation lane determination
relate to each other:
If you set the Consider Hierarchical Relationships Between MTrs First indicator and do not set
the Consider Source Hierarchy First indicator, the lane determination considers the objects and
hierarchies in the following order:
1. Means of transport
2. Destination location or zone
3. Source location or zone
You can choose this setting, for example, if the transportation lane leaving the warehouse is
more important than the customer. The means of transport has the lowest priority.
If you set the Consider Source Hierarchy First indicator and do not set the Consider
Hierarchical Relationships Between MTrs First indicator, the lane determination considers the
objects and hierarchies in the following order:
______________________________________________________________
SAP AG 10
SAP System
______________________________________________________________

You can choose this setting, for example, if the transportation lane for a specific means of
transport has the highest priority and the customer as destination location is more important than
the warehouse.
If you set both indicators, the lane determination considers the following objects and hierarchies
in the order they are presented:
You can choose this setting, for example, if a transportation lane to a certain customer is more
important than the transportation lane to your specific warehouse from which you deliver the
goods. The means of transport has the lowest priority.
If you do not set any indicator, the lane determination considers the following objects and
hierarchies in the order they are presented:
transport has the highest priority and a specific warehouse as source location is more important
than the customer.
6.1.1.4 Resources
6.1.1.4.1 Define Means of Transport
Use
In this IMG activity, you define means of transport.
______________________________________________________________
SAP AG 11
SAP System
______________________________________________________________
Example
- Airplane
- Train
- EuroTrucking
- ABC shipping
6.1.1.4.2 Define Compartment Type
Use
In this IMG activity you define compartment types.
Activities
1. Define a compartment type and, if necessary, determine capcities and capacity consumption
levels.
2. Define a compartment type profile.
3. Assign the compartment type profile to a means of transport.
6.1.1.4.3 Define Means-of-Transport Combination
Use
In this IMG activity you define means of transport combinations. You use means of transport
combinations to model vehicle-resource combinations. A means of transport combination must
consist of one means of transport that is capable of moving independently and at least one
passive means of transport.
Requirements
You have set the passive indicator for the corresponding means of transport for each trailer.
For more information, see the Implementation Guide (IMG) under Maintain Means of Transport.
______________________________________________________________
SAP AG 12
SAP System
______________________________________________________________
6.1.1.4.4 Define Attributes of MTr Combination/Compartment
Use
In this IMG activity, you define the attributes of means of transport combinations and
compartments.
Transportation Planning/Vehicle Scheduling (TP/VS):
The system uses these attributes if no reference to a database table exists in the definition of
the field in the field catalog.
6.1.1.4.5 Define Coupling/Uncoupling Duration
Use
In this IMG activity you define the length of time you require to couple a trailer to a vehicle
or to uncouple a trailer from a vehicle.
6.1.1.4.6 Maintain Registration Number Patterns
Use
In this IMG activity, you specify registration numbers patterns for resources.
Registration number patterns represent naming conventions for registration numbers.
______________________________________________________________
SAP AG 13
SAP System
______________________________________________________________
Standard settings
No registration number patterns are delivered.
Activities
1. Choose the resource type.

The registration number pattern is valid for resources of these types.
2. Choose the country key of the registration number.
The registration number pattern is valid for resources having these registration number
country keys.
3. Choose the means of transport.
The registration number pattern is valid for resources having these means of transport.
4. Enter the registration number pattern.
When entering new registration numbers for resources in the resource master, the system checks
for correctness of the numbers.
Note
If you do not specify registration number patterns, the system does not check for correctness of
registration numbers when it enters them in the resource master.
6.1.1.4.7 Specify Resource Template Types
Use
In this IMG activity, you specify a resource template type for handling resources.
You use resource template types to mark a handling resource as a handling resource template.
You can use this template for new handling resources.
______________________________________________________________
SAP AG 14
SAP System
______________________________________________________________
6.1.1.4.8 Specify Categories of Alternative Names
Use
In this IMG activity, you specify categories for alternative names of resources.
You have to specify alternative name categories before you can specify alternative names in the
resource master.
6.1.1.4.9 Maintain Settings for Qualifications
Use
In this IMG acitivity, you can specify qualifications.

Note
The system does not check the consistency of required or offered qualifications. If you want to
check the consistency, use the incompatibility framework of SAP Transportation Management
(SAP TM).
Example
You have maintained the qualification type Driving License with qualification A (Heavy
Vehicle).
- If you assign qualification A of category Driving License to a vehicle resource, this
means that this resource can only be operated with such a driving license.
- If you assign qualification A of category Driving License to a driver, this means that this
employee is allowed to operate heavy vehicles.
6.1.1.4.10 Maintain Settings for Grouping Attributes
Use
In this IMG activity, you can specify grouping attribute categories and grouping attributes for
resources.
______________________________________________________________
SAP AG 15
SAP System
______________________________________________________________
After you have specified grouping attributes and grouping attribute categories, you can assign
resources in the resources master to them.
Activities
1. Specify grouping attribute categories.

2. Specify grouping attributes for grouping attribute categories.
Example
You have specified the following:

- Grouping attribute category Truck with the grouping attributes A, B, and C
- Grouping attribute category Container with the grouping attributes C, CC, and CCC
Now you can group resources into trucks and containers. The attributes can be used for
resource selection.
6.1.1.4.11 Maintain Settings for Attached Equipment
Use
In this IMG activity, you specify categories of attached equipment.

You must specify categories of attached equipment before you can assign attached equipment to
these categories in the resource master.
6.1.1.4.12 Maintain Settings for Aggregated Capacity Requirements
Use
In this IMG activity, you specify that the system should write capacity requirements for
handling resources to the database during planning.
When you create a planned transportation activity that is linked to a handling resource, the
system aggregates the new capacity requirements of this planned transportation activity directly
on the database for the involved handling resource. This leads to a better capacity check
performance.
______________________________________________________________
SAP AG 16
SAP System
______________________________________________________________
Activities
1. Enter the name of a handling resource.

2. Set the Use DB indicator.
6.1.1.4.13 Specify Capacity Variants
Use
In this IMG activity, you can specify variants for the available capacity of resources. Capacity
variants describe, for example, the minimum and maximum capacity of the resource.
You use capacity variants, for example, if you are working with multiple-shift operations.
The system takes a capacity variant into account only if you have defined it as anactive variant
in the resource master data.
Activities
1. Specify a number for the capacity variant.

2. Specify the status of the capacity variant.
The status for SAP Transportation Management is always Normal Capacity.
3. Enter a short description for the capacity variant.
6.1.1.4.14 Assign Standard Equipment Type
Use
In this IMG activity, you specify the standard equipment type for a combination of equipment
group and equipment type.
You can use this combination to identify a transportation unit (TU) resource as a container or
as non-container equipment. This is necessary, for example, for printing or planning.
You can assign a means of transport or packaging material to this combination. The system
automatically includes these values in the TU resource information in the resource master when
it enters the combination of equipment group and equipment type there. Thus you can ensure
that TU resources are assigned to the correct means of transport and packaging materials. The
______________________________________________________________
SAP AG 17
SAP System
______________________________________________________________
system does not overwrite means of transport or packaging materials that you have already
specified.
6.1.1.5 Agreements
6.1.1.5.1 Define Freight Agreement Types
Use
In this Customizing activity, you can do the following:

- Define a freight agreement (FA) type
- Define the number range generating the ID for newly created FAs
- Specify the text schema
- Switch on and off the change value function
- Specify the retention time for archiving
6.1.1.5.2 Define Forwarding Agreement Types
Use

- Define a forwarding agreement (FWA) type
- Define the number range generating the ID for newly created FWAs
- Maintain a short description for the FWA type
______________________________________________________________
SAP AG 18
SAP System
______________________________________________________________
6.1.1.5.3 Define Deactivation Reasons
Use
In this Customizing activity, you can define the reasons why an agreement is deactivated.
6.1.1.5.4 Define Number Range Intervals for Agreements
Use
In this Customizing activity, you define number range intervals for agreements.
Activities
To define a number range, you must add a new number interval:

1. Enter a (maximum) two-character alphanumeric key.
2. Enter the limits for the number interval.
The individual number intervals must not overlap. Each number must appear once.
Note
Do not use the Ext. flag; external number ranges are not supported.
______________________________________________________________
SAP AG 19
SAP System
______________________________________________________________
6.1.2 Basic Functions
6.1.2.1 User Interface
6.1.2.1.1 Define Message Settings
Use
In this Customizing activity, you define the following message settings for a message type and
either a user or a role:
- Filtering by severity
- Filtering by detail level
- Filtering by problem class
- Maximum number of messages for application log
Requirements
- For user-specific message settings, the user must exist in the system.
- For role-specific message settings, the role must exist in the system.
Activities
1. Specify either a user or a role and a message type.

If you do not specify a user or a role, the system applies the message settings to all
users.
The system considers user-specific and role-specific message settings in the following way:
- User-specific message settings overrule role-specific message settings. Therefore, it
does not make sense to specify both a user and a role.
- If you specify different message settings for a role, the system considers the settings
with the highest granularity of information.
For example, you have specified the following settings: one with a detail level of 2
and another with a detail level of 7. In this case, the system applies the message
settings with the detail level of 7.
2. Make the message settings specified above.
______________________________________________________________
SAP AG 20
SAP System
______________________________________________________________
6.1.2.2 Create Active Version and Model
Use
In this IMG activity, you create an active version and a model.

In SAP Transportation Management (TM) you must assign specific master data objects to an
active version and a model for transportation planning purposes. You must assign the following
objects:
- Locations
The system creates the active version and the model exactly once.
Note
The active version and the model do not need to be and cannot be created more than once.
The system displays an error message if an active version and a model exist and you try to
create a new one.
Activities
Execute the IMG activity.
6.1.2.3 Define General Settings for SAP TM
Use
In this IMG activity, you can define general settings for SAP TM.
______________________________________________________________
SAP AG 21
SAP System
______________________________________________________________
6.1.2.4 Define SLD Data of Business Systems
Use
In this Customizing activity, you define the system landscape directory data of your business
systems.
You have to define the ERP systems (business system and logical system). Moreover, you need
to select the Manual Maint. checkbox.
6.1.2.5 Charge Calculation
6.1.2.5.1 Basic Settings for Charge Calculation
6.1.2.5.1.1 Define General Settings
Use
In this Customizing activity, you define the organizational unit settings for transportation charge
calculation. This consists of the following settings:
- Default purchasing organization and carrier
The default purchasing organization and carrier for which the rates are maintained so that a
price proposal can be determined for tendering purposes.
- Agreement determination rule
The BRFplus condition used to determine the agreement during charge calculation.
- Calculation sheet determination rule
The BRFplus condition used to determine the calculation sheet during charge calculation.
- Default settlement profile
The settlement profile to be applied for the organizational unit.
- Condition for determination of settlement profile
The BRFplus condition used to determine the settlement profile for charge calculation and
settlement purposes.
- Default dimensional weight profile
The default dimensional weight profile to be applied for the organizational unit.
- Condition for determination of dimensional weight profile
______________________________________________________________
SAP AG 22
SAP System
______________________________________________________________
The BRFplus condition used to determine the dimensional weight profile for charge
calculation and settlement purposes.
You can specify the organizational unit or enter *.
6.1.2.5.1.2 Define Rate Templates
Use
In this Customizing activity, you define rate templates to transport across different systems and
use as templates for creating rate tables.
Note that the system automatically enters the current date as the start date of validity and
12/31/9999 as the end date of validity. You can change these dates after you create a rate
table.
Activities
1. Create a rate template with the following required information:

- Rate template
- Charge type
- Charge usage
- Currency
2. Create rate template scales with the following required information:
- Dimension number (indicates the order of the input scales)
- Scale template
- Calculation base code
3. Create rate calculation base rules with the following required information (optional - used
in validity node):
- Calculation base
- Unit of measure
- Quantity
______________________________________________________________
SAP AG 23
SAP System
______________________________________________________________
6.1.2.5.1.3 Define Scale Templates
Use
In this Customizing activity, you define scale templates to transport across different systems and
use as templates for creating scales.
Activities
1. Create a scale template that includes the following information:

- Scale template
- Scale type
- Scale base
2. Create scale template items (optional)
This is relevant when the scale type is Base Scale (>=) or To Scale (<=) and the
scale items are numeric, for example, weight or distance.
Scale template items are not relevant when the scale items come from master data, for
example, location.
6.1.2.5.1.4 Define Calculation Sheet Templates
Use
In this Customizing activity, you define calculation sheet templates to transport across different
systems and use as templates for creating calculation sheets. The system validates the calculation
sheet templates after you create them.
Note
A calculation sheet template is a flat structure that the system formats into a hierarchical
structure based on the reference lines in the template. Therefore it is recommended that you
adhere to calculation sheet guidelines when creating a calculation sheet template, for example:
- Line numbers must be greater than 10 because the system generates the first sum line as
10
- The sum line must have reference lines greater than itself
- A subtotal line must have reference lines less than itself
- A subtotal line inherits the resolution base from the sum parent line
- If you require a nested sum line, decide on the reference line numbers accordingly
______________________________________________________________
SAP AG 24
SAP System
______________________________________________________________
Activities
1. Create a calculation sheet template with the following required information:

- Template name
- Charge usage
2. Create calculation sheet template items with the following required information:
- Line number (greater than 10 and in an ascending sequence)
- Rate template (only needed if you do not enter the amount)
- Charge type
- Instruction type
- Amount (only needed if you do not enter the rate template)
- Currency (use % for percentage charges)
- Calculation resolution base
- Operation code (compare the high and low values)
- Line to reference from (sum, subtotal, compare the high and low values, percentage)
- Line to reference to (sum, subtotal, compare the high and low values, percentage)
6.1.2.5.1.5 Define Charge Category Codes
Use
In this Customizing activity, you define charge category codes for charge types. You can use
the charge category codes to group and categorize charge types.
Example
A useful code list could be the UN/EDIFACT Codelist 5237.
______________________________________________________________
SAP AG 25
SAP System
______________________________________________________________
6.1.2.5.1.6 Define Charge Subcategory Codes
Use
In this Customizing activity, you define charge subcategory codes. You can use the charge
subcategory codes of charge types to group and categorize charge types in a more granular way
than charge category codes.
Example
A suitable example could be the code list resulting out of UN/EDIFACT Recommendation 23:
"FREIGHT COST CODE # FCC Harmonization of the Description of Freight Costs and Other
Charges".
6.1.2.5.1.7 Define Charge Type Codes
Use
In this Customizing activity, you can define charge type codes.

A charge type code describes a charge type. The charge type code defines if the charge item
results in a positive or negative value and if the value is an actual amount or a percentage
value. This value is used for other transportation charges.
We recommend to group and categorize charge type codes by use of charge type subcategory
codes and/or charge type category codes.
6.1.2.5.1.8 Define Charge Calculation Related Number Ranges
Use
In this Customizing activity, you define number ranges for the master data business objects that
are relevant for charge calculation.
______________________________________________________________
SAP AG 26
SAP System
______________________________________________________________
The system uses number range intervals of type internal to automatically assign a number of the
number range interval to the charge management objects. Therefore, you must define at least
one number range interval of the type Internal.
6.1.2.5.1.9 Define Number Range Intervals for Scales
Use
In this Customizing activity, you define number range intervals for scales.
Activities

Note
6.1.2.5.1.10 Define Number Range Intervals for Rates
Use
In this Customizing activity, you define number range intervals for rates.
______________________________________________________________
SAP AG 27
SAP System
______________________________________________________________
Activities

Note
6.1.2.5.1.11 Define Number Range Intervals for Calculation Sheets
Use
In this Customizing activity, you define number range intervals for calculation sheets.
Activities

Note
______________________________________________________________
SAP AG 28
SAP System
______________________________________________________________
6.1.2.5.2 Data Source Binding for Charge Calculation
6.1.2.5.2.1 Define Scale Bases
Use
In this Customizing activity, you define a scale base that forms one of the parameters on which
the cost to be calculated depends.
Activities
You define a scale base as a one-time setup activity. You maintain the scale base in tables of
delivery type S, meaning creating a new scale base is an enhancement activity.
Example
The cost of a shipment depends upon the weight of the goods and the distance traveled.
Therefore the weight and distance form the scale base. To define a scale base for weight, you
maintain it in Customizing in the following way:
Scale Base WEIGHT
Scale Base Desc. Weight
Field Assgmt (Scale Base Field Assignment) SCAVAL_WT
Usage Base for Scales
UoM Relevant X
Dimension Mass
Rounding Rule X
Numeric X
6.1.2.5.2.2 Define Calculation Bases
Use
In this Customizing activity, you define a calculation base for a scale base. The calculation base
indicates on what base the charge calculation is executed for a corresponding scale.
______________________________________________________________
SAP AG 29
SAP System
______________________________________________________________
Example
You define the calculation base SOURCELOC as Source (Ship from) Location and
DESTLOC as Destination (Ship to) Location for scale base LOC (Location) as follows:
Calc. Base SOURCELOC
Scale Base LOC
Description Source (Ship from) Location
Field Assgmt (Field Assignment) SOURCELOC_UUID (assignment to a field in the
communication structure)
Helper Assgmt (Helper Assignment) /SCMTMS/CL_TCC_CB_LOCATION_ID
Calc. Base DESTLOC

Scale Base LOC
Description Destination (Ship from) Location
Field Assgmt (Field Assignment) DESTLOC_UUID (assignment to a field in the
6.1.2.5.2.3 Define Dimensional Weight Profile
Use
In this Customizing activity, you calculate the dimensional weight by converting the volume to
the appropriate unit of measure and then dividing it by the dimensional weight factor. The
result is the weight in the target unit of measure. The dimensional weight is then used in the
charge calculation using the corresponding calculation base.
In general, the dimensional weight calculation depends on two input variables: the dimensional
weight factor (or ratio) and the system of used unit of measures. These variables are
country-specific and carrier-specific.
Common dimensional weight factors for metric units of measure are 5000 (cm3/kg) and 6000
(cm3/kg).
Common dimensional weight factors for imperial units of measure are 166 (in3/lb) and 194
(in3/lb).
Activities
Assign the dimensional weight profile directly to an organizational unit in the freight agreement
settings or determine the dimensional weight profile using a condition.
______________________________________________________________
SAP AG 30
SAP System
______________________________________________________________
Example
You want to configure the dimensional weight profile for imperial factor 166. You enter the
following data:
- Name I166
- Volume unit of measure in3
- Weight unit of measure lb
6.1.2.5.3 Rules and Conditions for Charge Calculation
6.1.2.5.3.1 Define Rounding Rules
Use
In this Customizing activity, you define rounding profiles. You use the rounding profile to
round the data according to its definition.
Each rounding profile points to a rounding rule at a particular index. This rounding rule
consists of the applicability of the rule that defines the value range index, the sign of range
limit included or range limit excluded, the option (for exmaple, equal to, less than, and greater
that), and low and high.
Based upon all the above mentioned factors, the value is rounded accordingly.
Activities
1. To define a rounding profile, maintain the following fields:

- Rnd. Prof. (Rounding Profile)
- Rounding Prof. Desc. (Rounding Profile Description)
2. To define the rounding rule for the above defined rounding profile, maintain the following
fields:
- Rule Index
- Rounding Profile
- Description
3. Each rounding rule in turn consists of applicability that you define with the following
attributes:
______________________________________________________________
SAP AG 31
SAP System
______________________________________________________________
- ValRngIndx (Value Range Index)

- Sign
You can select between the following: Range Limit Excluded or Range Limit
Included.
- Option
- Low Value
- High Value
Example
You define a rounding profile to round up or down to an integer of 0005, that is, it consists
of rounding rule 0005. This rounding profile, when applied to a value, rounds the value to the
nearest integer.
When rounding profile 0005 is applied to a value of 22.8, is it rounded to 23.
6.1.2.5.4 Enhancements of Charge Calculation Engine
6.1.2.5.4.1 Define Calculation Methods
Use
In this Customizing activity, you define the calculation methods used in charge calculation.
6.1.2.6 Dangerous Goods
6.1.2.6.1 Define Common Settings for Dangerous Goods Processing
Use
In this Customizing activity, you can define general settings for the dangerous goods processing
in SAP Transportation Management (TM).
______________________________________________________________
SAP AG 32
SAP System
______________________________________________________________
Standard settings
For the standard processing of dangerous goods with SAP Environment, Health and Safety
(EH&S), select the strategies DG_EHS_CHK and DG_EHS_PRT.
6.1.2.6.2 Define Dangerous Goods Profile
Use
In this Customizing activity, you define profiles for the processing of dangerous goods. The
following profiles are delivered: Only Errors Road and All Messages Road. You
define general conditions for the processing of dangerous goods, for instance what messages are
allowed to process certain dangerous goods or if you are allowed to define goods manually as
dangerous or not.
You assign the profile when defining order types for freight units or freight orders.
You can also specify default mode of transports that have to be used for the dangerous goods
check in case the information is not yet available on the business document.
Activities
You can change the profile or you can define a new one.
6.1.2.7 Type Codes and Role Codes
6.1.2.7.1 Master-Data-Related Type Codes and Role Codes
6.1.2.7.1.1 Define Party Roles
Use
In this IMG activity, you can define roles for the parties involved in the transportation process.
______________________________________________________________
SAP AG 33
SAP System
______________________________________________________________
6.1.2.7.1.2 Define Package Type Codes
Use
In this IMG activity, you define package type codes.
6.1.2.7.1.3 Define Transportation Goods Identifier Type Codes
Use
In this IMG activity, you define transportation goods identifier type codes.
6.1.2.7.2 General Type Codes and Role Codes
6.1.2.7.2.1 Define Business Transaction Document Type Codes
Use
In this IMG activity, you can define the document type codes for a business transaction.
______________________________________________________________
SAP AG 34
SAP System
______________________________________________________________
6.1.2.7.2.2 Define Business Transaction Document Item Type Codes
Use
In this IMG activity, you define business transaction document item type codes.
6.1.2.7.2.3 Define Block Reason Codes
Use
In this Customizing activity, you define block reason codes and assign them to processes. These
processes are then blocked in SAP Transportation Management (SAP TM).
You can use manual block reasons to block processes in SAP TM for many types of objects.
For example, you can block a forwarding order for planning. SAP TM also has block reasons
that are set automatically by the system. The approval workflow is an example of such a block
reason.
6.1.2.8 Text Collection
6.1.2.8.1 Define Settings for Text Collection
Use
You can use the following Customizing activity to define the settings for text collection:
Maintain Text Schema
______________________________________________________________
SAP AG 35
SAP System
______________________________________________________________
For more information, see Cross-Application Components -> Processes and Tools for Enterprise
Applications -> Reusable Objects and Functions for BOPF Environment -> Dependent Object
Text Collection -> Maintain Text Schema.
6.1.2.9 Conditions
6.1.2.9.1 Data Access Definition
Use
In this IMG activity, you define the data access definition.
6.1.2.9.2 Define Text for Data Access Definition
Use
In this IMG activity, you define text for your data access definition.
6.1.2.9.3 Define Condition Types
Use
______________________________________________________________
SAP AG 36
SAP System
______________________________________________________________
In this Customizing activity, you can define condition types.
6.1.2.9.4 Assign Condition Type to Data Access Definition
Use
In this IMG activity, you assign condition types to data access definitions.
6.1.2.10 Geographical Map
6.1.2.10.1 Define Settings for Geographical Map
Use
In this Customizing activity, you can activate the geographical map display and define settings
for the geographical map.
6.1.2.11 Printing
6.1.2.11.1 Assign Text Types to Print Document Text Fields
______________________________________________________________
SAP AG 37
SAP System
______________________________________________________________
Use
In this Customizing activity, you define which text types are to be printed in which text fields
in a print document. For example, you define that handling instructions for a house air waybill
are to be printed in the HAWB (House Air Waybill): Handling Instructions (HAWB_HDINS) text
field in the corresponding print document.
Requirements
You have defined text types and assigned them to text schemas.
For more information, see Customizing for Cross-Application Components under Processes
and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF
Environment -> Dependent Object Text Collection -> Maintain Text Schema.
6.1.3 Forwarding Order Management
6.1.3.1 Define Number Range Intervals for Forwarding Order Management
Use
In this Customizing activity, you define the number range intervals for the following business
documents:
- Forwarding Order
- Forwarding Quotation
- Order-Based Transportation Requirement
- Delivery-Based Transportation Requirement
When you create one of the above business documents, the system assigns a unique number that
identifies the business document. The number is determined from the number range interval that
is assigned to the business document type in Customizing.
Only internal number assignment is supported, therefore do not use the External Number
Range checkbox.
______________________________________________________________
SAP AG 38
SAP System
______________________________________________________________
Activities
1. To define a number range interval, specify the following:

- Alphanumeric key with up to two characters
- Boundaries of the number range interval. The individual number range intervals must
not overlap. Thus, every number can only occur once.
2. Afterwards, specify the key of the number range interval for the business document type.
For an example, seeDefine Forwarding Order Types.
6.1.3.2 Forwarding Order
6.1.3.2.1 Define Forwarding Order Types
Use
In this Customizing activity, you specify types of forwarding orders. You can use this type to
define certain parameters of the forwarding order that influence how the system processes this
business document.
For example, the forwarding order type determines the number range interval that is used to
generate a number of the forwarding order, or it defines whether freight units are created
automatically when you save the forwarding order. Furthermore, you can assign profiles, for
example planning profile and dangerous goods profile, that determine how follow-up steps such
as planning and dangerous goods checks are performed.
You can select and assign the types that you have defined in this Customizing activity on the
user interface of the forwarding order in SAP NetWeaver Business Client. You can also specify
a default forwarding order type that is used when the forwarding order is created automatically
based on electronic data interchange (EDI).
In the Organizational Unit Determination screen area, you define how the system determines
the sales organization.
The system first checks the Condition for Default Sales Organization. If no sales organization
condition is maintained or if the condition does not find a sales organization, the system checks
if the Consider User Assignment for Org. Unit Determination checkbox is selected, and if the
user is assigned to a sales organization. If the system does not find anything, it uses the sales
organization that is maintained in the Sales Organization field.
______________________________________________________________
SAP AG 39
SAP System
______________________________________________________________
6.1.3.3 Forwarding Quotation
6.1.3.3.1 Define Forwarding Quotation Types
Use
In this Customizing activity, you specify types of forwarding quotations. You can use this type
to define certain parameters of the forwarding quotation that influence how the system processes
this business document.
For example, the forwarding quotation type determines the number range interval that is used to
generate a number of the forwarding quotation, or it defines whether an approval workflow is
activated.
user interface of the forwarding quotation in SAP NetWeaver Business Client. You can also
specify a default forwarding quotation type that is used when the forwarding quotation is created
automatically based on electronic data interchange (EDI).
6.1.4 Freight Order Management
6.1.4.1 Define Number Range Intervals for Freight Order Management
______________________________________________________________
SAP AG 40
SAP System
______________________________________________________________
Use
documents
- Freight order
- Freight unit
- Freight booking
- Transportation unit
When creating one of the above business documents, a unique number is assigned which
Only internal number assignment is supported, do not use the check box External Number
Range.
Activities

- Alphanumeric key with up to two characters.
- Boundaries of the number range interval. The individual number range intervals may
For an example, see Define Freight Order Types.
6.1.4.2 Freight Order
6.1.4.2.1 Define Freight Order Types
Use
In this Customizing activity, you can define freight order types.
______________________________________________________________
SAP AG 41
SAP System
______________________________________________________________
6.1.4.3 Tendering
6.1.4.3.1 Define Settings for Tendering by E-mail
Use
In this Customizing activity, you can select and change the settings the system uses to manage
incoming e-mails that contain freight quotations (FQs) from carriers.
General Settings View
In the General Settings view, the character you enter in the Keyword Marker field marks
the beginning of a keyword in an e-mail text.
The system stops any further parsing of an e-mail text after the first occurrence of the
character you enter in the Parser End Marker field. You can place explanatory text that you
do not want the parser to process after the parser end marker in an e-mail.
Keywords View
In the Keywords view, you can assign keywords to enable the parser to relate a piece of text
in an e-mail to a business meaning. In an e-mail text, a keyword must start with the keyword
marker that you defined in the General Settings view.
For example, you define a keyword marker of "&". You assign the keyword "RFQ" to the
"Freight Request for Quotation Number" business meaning. Your e-mail text reads as follows:
"Hello, this is a freight quotation for &RFQ 12345".
In this example, the parser extracts the "Freight Request for Quotation Number" from the
e-mail text by searching for the keyword "RFQ". This keyword is preceded by the keyword
marker "&". The "Freight Request for Quotation Number" 12345 follows the keyword "RFQ".
Keywords are not case sensitive. If you define a keyword "RFQ", carriers can write "&RFQ",
"&rfq", or "&rFq" in e-mails.
You can select Determines Application for exactly one keyword in each application. The
occurrence of this specific keyword in an e-mail text determines the application. For example, if
you select the Determines Application checkbox for the keyword "RFQ" and the application
/SCMTMS/TENDERING, the occurrence of "&RFQ" in an e-mail text tells the system the
e-mail is related to a tendering process.
Keyword Values View
In the Keyword Values view, you can define how carriers write "Yes" and "No" in an e-mail
text. You must define "Yes" and "No" values for the keyword that has the "Acceptance Code"
meaning.
______________________________________________________________
SAP AG 42
SAP System
______________________________________________________________
For example, in the Keywords view, you assign the keyword "ACCEPT" to the meaning
"Acceptance Code". In the Keyword Values view, you assign keyword value "Y" to meaning
"Yes" and keyword value "N" to meaning "No". To accept a freight request for quotation
(freight RFQ) by e-mail, a carrier writes "&ACCEPT y". To reject, a carrier writes
"&ACCEPT n".
Keywords values are not case sensitive. If you define a keyword "ACCEPT" and a keyword
value "Y", a carrier can write "&ACCEPT Y", "&accept y", or "&aCCepT Y" in e-mails.
6.1.4.3.2 Define General Settings for Tendering
Use
In this Customizing activity, you can specify the standard settings for tendering. You can also
specify the tendering communication and process settings that you can use in the Define Freight
Order Types Customizing activity.
In the 01 - Visibility Settings view, you can select the settings that determine the visibility
level of a price limit, submitted price, and stop dates in a tendering process.
In the 02 - Rejection Reason Codes view, you can define reason code identifiers (IDs) and
descriptions to classify your reasons for rejecting freight request for quotations (freight RFQs).
In the 03 - E-mail and SMS Content view, you can define the following settings:
- Documents for Notifications
You can specify the names of the documents that the system uses to create e-mails. You
can specify separate documents for the e-mail subject field, the e-mail body text, and SMS
text content. You can also specify additional information that the system adds to other
e-mail body text or SMS text. The system uses the e-mail or SMS type to determine
where it adds the additional text.
You must define the documents that you use in this view as General text documents in
transaction SE61.
- Triggering Notifications at Process Events
You can specify that the system sends an e-mail or an SMS message to a carrier when an
event occurs in the tendering process. Events include sending a freight RFQ to a carrier
and awarding a freight quotation (FQ).
- Bundling Notifications
You can schedule the sending of e-mails and SMS messages in a batch report. With this,
the contact person for the carrier receives e-mails or SMS messages only when the batch
report runs in your system.
The e-mails or SMS messages contain information about all the new events that have taken
______________________________________________________________
SAP AG 43
SAP System
______________________________________________________________
place since the last bundle of e-mails or SMS messages were sent. This means the carrier
does not receive 10 separate e-mails for new freight RFQs, but one e-mail containing the
information on all 10 new freight RFQs.
- General Settings
You can specify general settings for processing e-mails. You can specify the default
communication language and time zone, and the e-mail address the system uses for inbound
e-mails. You can also specify that the system sends you an automatic status confirmation
by e-mail.
- E-mail Security Settings
You must enable secure e-mail management in your system. For more information see SAP
NetWeaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key
Capability -> Platform-Wide Services -> Connectivity -> Communication Interfaces for
Mail and Telefony -> SAP Connect (BC-SRV-COM) -> Administration -> Secure E-Mail.
In the 04 - Process Settings view, you can specify the following process settings for
tendering:
- Default tendering manager
- Visibility settings
- Tendering profile
- Carrier selection settings
- Maximum response duration
- Considering the calling hours of a business partner
You can use the process and communication settings that you define here in the Define Freight
Order Types Customizing activity to specify the tendering settings for each freight order type.
The following are the settings in the freight order type that the system uses to determine the
Customizing settings for tendering:
- Default, where the system uses the system default settings
- Freight order type, where the system uses the type of freight order
- Conditions, where the system uses the runtime characteristics of a freight order
In the 05 - Communication Settings view, you can specify the following communication
settings for tendering:
- Send alerts to tendering managers whether or not the managers have subscribed to a
tendering alert category
- Use EDI messages to communicate with carriers
- Send particular types of e-mails to carriers
Types include e-mails for freight RFQs, FQ cancellations, and FQ awards.
- Send freight RFQs as e-mails or SMS messages
In the 06 - Carrier -Specific Communication Settings view, you can define communication
settings for a particular carrier that are different from the general communication settings
defined in the 05 - Communication Settings view. This includes the following settings:
- Send EDI messages to this carrier and not to other carriers
______________________________________________________________
SAP AG 44
SAP System
______________________________________________________________
- Send particular types of e-mails and SMS messages to this carrier and not to other carriers
In the 07 - Default Settings view, you must specify one default set of process settings and
one default set of communication settings for your tendering processes.
The system uses these settings if it cannot determine a freight order type. You can also enable
the system to create change documents to record the changes you make to the tendering profiles
that you edit.
6.1.4.4 Freight Booking
6.1.4.4.1 Define Freight Booking Types
Use
In this Customizing activity, you can define freight booking types.
6.1.5 Planning
6.1.5.1.1 Define Profiles and Settings
Use
To execute planning, you have to define profiles and settings and transport them into your
production system. You can define profiles and settings in SAP NetWeaver Business Client by
choosing Application Administration -> Planning.
For more information about profiles and settings, see SAP library for Transportation
Management under Profiles and Settings.
______________________________________________________________
SAP AG 45
SAP System
______________________________________________________________
6.1.5.1.2 Configure Process Controller for Planning
Use
This Customizing activity contains general information about setting up the process controller for
use with planning.
The process controller is a framework that allows you to define your own services, strategies,
and methods for a specific application process.
Activities
You can make settings for the process controller in the following Customizing activities:
- Define Service
- Define Strategy
- Define Methods
- Assign Methods to a Strategy
With the other Customizing activities under the node Process Controller you can define
parameters in order to further adapt your strategy.
See also
For more information, see the SAP Library for SAP Transportation Management on SAP Help
Portal at http://help.sap.com under Basic Functions -> Process Controller.
6.1.5.1.3 Define Transportation Allocation Settings
Use
In this IMG activity, you maintain transportation allocation settings.
______________________________________________________________
SAP AG 46
SAP System
______________________________________________________________
6.1.5.1.4 Define Customer-Specific Functions for Planning
Use
In this Customizing activity, you can define your own functions for the planning area and
assign your own strategies to them. The functions that you define here are automatically
available for selection on the transportation planning user interface.
Requirements
You have defined at least one strategy and at least one method. Moreover, you have assigned
this method to your strategy. For more information, see Configure Process Controller for
Planning.
6.1.5.1.5 Define Scheduling Constraints
Use
In this Customizing activity, you can define scheduling constraints. A transportation planner can
use this Customizing activity to define time-based constraints for trucks coming from or going
to a certain transshipment location.
VSR optimization and scheduling (manual planning) take these scheduling constraints into
account.
You can use scheduling constraints, for example, to approximate legal requirements regarding
driving times in planning.
For more information, see SAP Library for SAP Transportation Management under Planning ->
Interactive Planning -> VSR Optimization.
Requirements
To be able to assign a constraint set, you need to have defined means of transport. For more
information, see Define Means of Transport.
______________________________________________________________
SAP AG 47
SAP System
______________________________________________________________
Activities
1. Define an activity group, for example "Working time".

2. Assign activity types to your activity group. For example, you can assign activity types
"Transportation", "Coupling", and "Uncoupling" to your activity group "Working time".
This means that the driver of the truck will drive the truck and do all coupling and
uncoupling activities.
3. Define time constraints and assign an activity group to each time constraint.
4. Define a constraint set. A constraint set contains several time constraints and indicates the
areas or countries for which the time constraints apply. You can re-use time constraints in
other constraint sets.
5. Define means-of-transport constraints by assigning your constraint set to a means of
transport. A means of transport can only have one constraint set assigned to it. However,
you can assign a constraint set to several means of transport.
See also:
For more information, see SAP Library for Transportation Management under VSR Optimization.
6.1.5.2 Freight Unit
6.1.5.2.1 Define Freight Unit Types
Use
In this Customizing activity, you can define freight unit types.
6.1.6 Settlement
6.1.6.1 Configure Process Controller for Settlement
______________________________________________________________
SAP AG 48
SAP System
______________________________________________________________
Use
use with settlement documents.
and methods for a specific application process. For example, if you want to use
split/consolidation strategy to create settlement documents differently to the standard way, you
can define your own strategy using the process controller and assign it to the TM_INVOICE
service.
Activities
Make settings for the process controller in the following Customizing activities:
- Define Service
- Define Strategy
- Define Methods
More Information
For more information about the process controller for SAP Transportation Management, see SAP
Help Portal at http://help.sap.com under SAP Transportation Management -> Basic
Functions -> Process Controller.
6.1.6.2 Define Settlement Profile
Use
In this Customizing activity, you can define the profile for creating settlement documents. The
settlement profile consists of a set of parameters with which you can control how the system
creates settlement documents.
You can assign the defined settlement profile to an organizational unit using transaction
/SCMTMS/TCM_FASET.
If you do not specify a settlement profile, the system uses standard default settings to create
settlement documents.
Activities
Specify the following activities:
______________________________________________________________
SAP AG 49
SAP System
______________________________________________________________
- Data source to determine the type of data that the system uses when creating a settlement
document. You can specify planned, confirmed, or execution data from forwarding orders
or freight orders.
- Charge item level to determine the level in the forwarding order or freight order at which
the system calculates charges. You can select the header or item level.
- Split/consolidation strategy profile to split or consolidate settlement documents
- Invoicing level to determine one of the following settings when the system creates a
settlement document:
- Consolidate data from more than one forwarding order or freight order
- Create one settlement document for each order
- Create a settlement document for each main item in an order
- Calculation option to determine one of the following settings when the system creates a
- Copy all charges from the forwarding order or freight order
- Copy only the charges that are fixed and calculate all other charges again
6.1.6.3 Forwarding Settlement
6.1.6.3.1 Define Forwarding Settlement Document Types
Use
In this Customizing activity, you define types of forwarding settlement documents (FWSDs).
You can use these types to specify certain parameters for certain types of FWSDs. The
following includes some of the parameters you can specify:
- Number ranges of FWSDs
- FWSD categories
- Tracking of changes
- BW relevance
- Default UoMs
- Retention period for archiving
- Output profile for printing and transferring to ERP
______________________________________________________________
SAP AG 50
SAP System
______________________________________________________________
6.1.6.3.2 Define Number Range Intervals for Forwarding SDs
Use
In this Customizing activity, you define number range intervals for forwarding settlement
documents (FWSDs).
Activities

Note
6.1.6.4 Freight Settlement
6.1.6.4.1 Define Freight Settlement Document Types
Use
In this Customizing activity, you define types of freight settlement documents (FSDs). You can
use these types to specify certain parameters for certain types of FSDs. The following includes
some of the parameters you can specify:
- Number ranges of FSDs
- FSD categories
- BW relevance
- Default UoMs
______________________________________________________________
SAP AG 51
SAP System
______________________________________________________________
6.1.6.4.2 Define Number Range Intervals for Freight SDs
Use
In this Customizing activity, you define number range intervals for freight settlement documents
(FSDs).
Activities

Note
6.1.7 Global Trade
6.1.7.1 Define Customs Profile
Use
In this Customizing activity, you create customs profiles and define general terms for processing
information concerning customs. You can define, for example, whether the system checks if the
transport is relevant for customs and if a declaration is necessary.
Requirements
You have defined the customs relevance check in the Customizing activity Define Customs
Relevance Check.
______________________________________________________________
SAP AG 52
SAP System
______________________________________________________________
Activities
Create a profile and assign the settings. You can also change existing profiles.
6.1.7.2 Define Customs Relevance Check
Use
In this Customizing activity, you define a customs relevance check. The system checks if the
freight order is relevant for customs and if a declaration is necessary for the transportation. The
following check is available:
- Export Check
Checks if the customs union of the source location and the destination location are
different.
Requirements
They depend on the settings you make in the customs profile. For more information, see the
Customizing activity Define Customs Profile.
Standard settings
- Standard interface
/SCMTMS/IF_GT_RELEVANCE_CHECK
- Methods
CHECK_RELEVANCE_EXPORT
- Standard implementation class
/SCMTMS/CL_GT_RELEVANCE_CHECK
Activities
Select the relevant class for the relevance check that implements the above standard interface,
and select the method for the relevance check.
You can define your own customs relevance activities.
6.1.8 Integration
6.1.8.1 ERP Logistics Integration
______________________________________________________________
SAP AG 53
SAP System
______________________________________________________________
6.1.8.1.1 Order-Based Transportation Requirement
6.1.8.1.1.1 Define Order-Based Transportation Requirement Types
Use
In this Customizing activity, you specify types of order-based transportation requirements (OTR).
You can use this type to define certain parameters of the OTR that influence how the system
processes this business document.
For example, the OTR type defines the number range interval that is used to generate a number
of the OTR, or it defines whether freight units are created automatically.
You can also specify a default type that is used when the OTR is created automatically based
on data transferred from an ERP system.
6.1.8.1.1.2 Assign ERP Text Types to TM Text Types for OTR
Use
In this Customizing activity, you define that texts entered in an SAP ERP document are
displayed on the Notes tab page of the corresponding order-based transportation requirement
(OTR) in SAP TM. You do this by mapping the text type in SAP ERP to the relevant text
type in SAP TM.
Requirements
- You have defined text types in SAP ERP. For more information, see the following:
- For sales documents, see Customizing for Logistics Execution under Shipping ->
Basic Shipping Functions -> Text Control.
- For purchase orders, see Customizing for Materials Management under Purchasing
-> Purchase Order -> Texts for Purchase Orders.
- You have defined text types in SAP TM.
For more information, see Customizing for Cross-Application Components under

Processes and Tools for Enterprise Applications -> Reusable Objects and
Functions for BOPF Environment -> Dependent Object Text Collection ->
Maintain Text Schema.
______________________________________________________________
SAP AG 54
SAP System
______________________________________________________________
6.1.8.1.2 Delivery-Based Transportation Requirement
6.1.8.1.2.1 Define Delivery-Based Transportation Requirement Types
Use
In this Customizing activity, you specify types of delivery-based transportation requirements

(DTR). You can use this type to define certain parameters of the DTR that influence how the
system processes this business document.
For example, the DTR type defines the number range interval that is used to generate a number
of the DTR, or it defines whether freight units are created automatically.
You can also specify a default type that is used when the DTR is created automatically based
6.1.8.1.2.2 Assign ERP Text Types to TM Text Types for DTR
Use
displayed on the Notes tab page of the corresponding delivery-based transportation requirement
(DTR) in SAP TM. You do this by mapping the text type in SAP ERP to the relevant text
type in SAP TM.
Requirements
______________________________________________________________
SAP AG 55
SAP System
______________________________________________________________

6.1.8.1.3 Order Scheduling
6.1.8.1.3.1 Make Settings for Sales Order Scheduling
Use
During sales order processing in SAP ERP, the dates in the SAP ERP sales order schedule
lines are determined by SAP Transportation Management (SAP TM).
Requirements
To use the synchronous scheduling of SAP ERP sales orders in SAP TM, you must set up the
following as a prerequisite:
- Asynchronous integration of SAP ERP sales orders with SAP TM order-based transportation
requirements
- Customizing-based or condition-based determination of transportation requirement types,
freight unit building rules, and planning profiles for synchronously-created transportation
requirements
In your SAP ERP system, you have assigned a Control Key for Document Transfer to
External TMS to sales orders specified by sales document type, sales area, and shipping
conditions. You have selected the Sales Order Scheduling in External TMS checkbox in this
control key.
For more information, see SAP Library for SAP Transportation Management under ERP
Logistics Integration -> Scheduling of SAP ERP Sales Orders in SAP TM.
6.1.8.2 Integration to SAP NetWeaver Business Warehouse
6.1.8.2.1 Specify Settings for BW Relevance and Data Transfer
______________________________________________________________
SAP AG 56
SAP System
______________________________________________________________
Use
You can use this activity for the following purposes:

- To access Customizing activities required for transferring data to SAP NetWeaver BW
- For more information about the activity to enable delta extraction (you determine
whether or not the system transfers data to SAP NetWeaver BW), see Customizing
for Cross-Application Components -> Processes and Tools for Enterprise
Applications -> Reusable Objects and Functions for BOPF Environment ->
PPF Adapter for Output Management -> Maintain Output Management Adapter
Settings.
- For more information about activities where you determine how the system transfers
data to SAP NetWeaver BW, see Customizing for Integration with Other
mySAP.com Components -> Data Transfer to the SAP Business Information
Warehouse.
- To access Customizing activities required for specifying the BW relevance of the following
object types:
- Define Forwarding Order Types
- Define Forwarding Quotation Types
- Define Freight Order Types
- Define Freight Booking Types
- Define Freight Unit Types
- Define Forwarding Settlement Document Types
- Define Freight Settlement Document Types
- Order-Based Transportation Requirement Types
- Delivery-Based Transportation Requirement Types
6.1.8.3 Tracking and Tracing of Processes and Documents
6.1.8.3.1 Prerequisites for Tracking and Tracing
______________________________________________________________
SAP AG 57
SAP System
______________________________________________________________
Use
To use tracking and tracing, you have executed the following Customizing activities for SAP
Transportation Management:
- You have defined the following:
- Freight order types (see Define Freight Order Types)
- Freight booking types (see Define Freight Booking Types)
- Freight unit types (see Define Freight Unit Types)
- Transportation unit types (see Define Transportation Unit Types).
In these Customizing activities make sure that you have chosen an execution tracking
relevance.
- If you want to use an event management system or SAP Event Management to track and
trace the execution of transportation activities, for example, the loading, transportation, and
unloading of freight units, you have defined the system configuration. For more information
about the system configuration for SAP Event Management, see Customizing for SAP
Transportation Management under Integration with Other mySAP.com Components -> Event
Management Interface -> Define System Configuration.
- If you want to use SAP Event Management to track and trace the execution of
transportation activities, you have activated business function SCM_EM_TMCONTENT01
EM, Visibility Proc. for External Transportation Mgmt System in SAP Event Management.
If you want to enhance the standard Customizing, you can define own events and the processing
of these events:
- Define own transportation activities and events in SAP Transportation Management. For
more information, see Define Transportation Activities for Tracking and Tracing.
- Define these events also in the external event management system. For more information
about the event definition in SAP Event Management see Event Management -> Event
Handlers and Event Handler Data -> Codes -> Event Codes -> Define Internal Event
Codes and Internal Event Code Groups.
- To enable the processing of your own events, use BAdI: Providing Execution Data for
Transportation Activities.
6.1.8.3.2 Define Transportation Activities for Tracking and Tracing
Use
______________________________________________________________
SAP AG 58
SAP System
______________________________________________________________
In this Customizing activity you define transportation activities for tracking and tracing.
You also define events.
6.1.9 Business Add-Ins (BAdIs) for Transportation Management
6.1.9.1 Master Data
6.1.9.1.1 General Settings
6.1.9.1.1.1 One-Time Locations
6.1.9.1.1.1.1 Notes on Implementation
Use
All Business Add-Ins (BAdIs) that are grouped under this structure node belong to the
enhancement spot /SCMTMS/ES_OTA_LOCATION.
Requirements
Before implementing the enhancement implementation for the enhancement spot

/SCMTMS/ES_OTA_LOCATION, ensure that you have made the following Customizing settings:
- In the IMG activity Define Number Range Intervals for One-time Locations, you have
defined a number range interval of the type "internal".
If you intend to implement the Customer-Specific Search Logic for One-Time Locations BAdI,
you must set the Addr. Search indicator in the IMG activity Define General Settings for SAP
TM in addition to defining the number range intervals for one-time locations.
6.1.9.1.1.1.2 BAdI: Adjustment of Location Data Created for One-Time
______________________________________________________________
SAP AG 59
SAP System
______________________________________________________________
Locations
Use
This Business Add-In (BAdI) is used in the following components:

- Forwarding Order Management (TM-FWM)
- Planning (TM-PLN)
You can use this BAdI to adjust the location data whenever a one-time location is created. This
BAdI takes control, for example, when a forwarding order or a transportation requirement is
created that has the following qualities:
- It contains address data specifying the source or destination locations but does not specify
an internal ID or a standard ID, such as DUNS or GLN, for the locations.
- The address data of the location does not match any of the locations already existing in
the system.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enh.
Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
Information about the implementation of BAdIs in the context of the enhancement concept is
available in the SAP Library for SAP NetWeaver under BAdIs - Embedding in the
Enhancement Framework.
See also:
Method:
Adjust Location Data for One-Time Locations
This BAdI uses the interface /SCMTMS/IF_OTA_LOCATION_DATA. For more information,

display the interface in the Class Builder.
6.1.9.1.1.1.3 BAdI: Customer-Specific Search Logic for Locations Based on
______________________________________________________________
SAP AG 60
SAP System
______________________________________________________________
Address Data
Use

- Planning (TM-PLN)
You can use this BAdI to implement a customer-specific location determination by using the
transferred address data. If you implement the BAdI, the determination takes control whenever a
transportation document is created, such as a forwarding order or a transportation requirement,
that contains address data specifying the source or the destination locations but does not specify
If a location is transferred in export structure ES_LOC_FOUND, the default address search is
suppressed automatically. A reference to this location is then inserted into the document being
created, for example to the forwarding order or to the transportation requirement, as the source
or destination location. In addition, you can explicitly suppress the default address search by
setting export parameter EV_SKIP_STANDARD.
Standard settings
Activities
See also:
Method:
Customer-Specific Location Search Based on Address Data
This BAdI uses the interface /SCMTMS/IF_OTA_LOCATION_SEARCH. For more information,
______________________________________________________________
SAP AG 61
SAP System
______________________________________________________________
6.1.9.1.1.2 Equipment Types and Equipment Groups
Use
All Business Add-Ins (BAdI) that are grouped under this structure node belong to the
enhancement spot /SCMB/MD_EQUIPMENT.
6.1.9.1.1.2.2 BAdI: Consistency Check for Equipment Types
Use
This Business Add-In (BAdI) is used in the component Transportation Management (SCM-TM).
You can use this BAdI to implement a consistency check for the entry of equipment types.
When an equipment type is created, the system checks whether it has already been entered and
assigned to another equipment group.
Requirements
You have defined equipment types and groups in Customizing for SAP Transportation
Management (SAP TM).
For more information, refer to the Implementation Guide (IMG) for SAP TM under
Transportation Management -> Master Data -> General Settings -> Define Equipment Types
and Equipment Groups.
Standard settings
In the standard system, the BAdI implementation Z_IMPL_EQUI_CONS_EXAMP is activated.

The default code is executed automatically.
The BAdI is not intended for multiple use.
The BAdI is not filter-dependent.
Activities
______________________________________________________________
SAP AG 62
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface /SCMB/IF_EQUI_TYPE_CONS. For more information,
6.1.9.1.2 Organizational Management
6.1.9.1.2.1 Enhancement of SAP NetWeaver Identity Management

Integration
Use
enhancement spot /SCMTMS/IDM_TM_CUST.
6.1.9.1.2.1.2 BAdI: User Exit for SAP NetWeaver Identity Management

Integration
Use
You use this Business Add-In (BAdI) to change or enhance the integration process between SAP
NetWeaver Identity Management and SAP Transportation Management (SAP TM).
Requirements
You are using the SAP NetWeaver Identity Management 7.1 product under license.
______________________________________________________________
SAP AG 63
SAP System
______________________________________________________________
Standard settings
In the standard system, there is no activated BAdI implementation.

The BAdI is designed for multiple use. All activated implementations are called and executed.
Activities
Example
See also:
This BAdI uses the interface /SCMTMS/IF_IDM_TM_CUST. For more information, display the
interface in the Class Builder.
6.1.9.1.2.2 Organizational Unit Integration
Use
enhancement spot /SCMTMS/ORG_UNIT_INT.
6.1.9.1.2.2.2 BAdI: Creation of Organizational Units
Use
This Business Add-In (BAdI) is used in the Organization (TM-MD-ORG) component. You can
use this BAdI to influence the creation of organizational units before saving them in the SAP
______________________________________________________________
SAP AG 64
SAP System
______________________________________________________________
Transportation Management (SAP TM) system from a connected ERP system.
Standard settings
Activities
See also
BAdI method documentation:

- MODIFY_INF
- MODIFY_REL
6.1.9.1.3 Transportation Network
6.1.9.1.3.1 Location
6.1.9.1.3.1.1 Enhancement of Validation Logic for Alternative Location

Identifiers
6.1.9.1.3.1.1.1 Notes on Implementation
Use
enhancement spot /SAPAPO/ENH_LOC_ALI_VALIDATION.
______________________________________________________________
SAP AG 65
SAP System
______________________________________________________________
6.1.9.1.3.1.1.2 BAdI: Validation of Alternative Location Identifiers
Use
This Business Add-In (BAdI) is used in the SCM Basis (SCMB) component. You can use this
BAdI to add customer-specific validation to the standard validation of alternative location IDs.
Standard settings

The BAdI is designed for single use.
Activities
6.1.9.1.3.2 Reuse Component
6.1.9.1.3.2.1 Enhancement of Distance and Duration Determination
Use
enhancement spot /SCMB/ES_LDDD_DDD.
______________________________________________________________
SAP AG 66
SAP System
______________________________________________________________
6.1.9.1.3.2.1.2 BAdI: RC LDDD - Distance and Duration Determination
Use
This Business Add-In (BAdI) is used in the component Transportation Network

(SCM-TM-MD-TN).
You can use this BAdI to influence the behavior of the function for the determination of
distance and duration on the basis of:
- GIS queries
- Calculations from coordinates
- Determinations via transportation lanes
The BAdI allows the following:
- Manipulation of input data passed on
- Use of own determinations
- Manipulation of output data of the standard determinations
The unit for the distance determined is kilometer (km).
Requirements
The system contains locations and means of transport.
Standard settings
No BAdI implementation is activated in the standard system.

Activities
See also:
This BAdI definition uses the interface /SCMB/IF_EX_LDDD_DDD. To obtain further

information, display this interface in the Class Builder.
______________________________________________________________
SAP AG 67
SAP System
______________________________________________________________
6.1.9.1.3.2.2 Enhancement of Basic Distance and Duration Determination
Use
enhancement spot /SCMB/ES_DDD.
6.1.9.1.3.2.2.2 BAdI: RC LDDD - Basic Distance and Duration Determination
Use

(SCM-TM-MD-TN).
- GIS queries
- Manipulation of output data of standard determinations
Requirements
Standard settings

______________________________________________________________
SAP AG 68
SAP System
______________________________________________________________
Activities
See also:
This BAdI definition uses the interface /SCMB/IF_EX_DDD. To obtain further information,
display this interface in the Class Builder.
6.1.9.1.4 Resources
6.1.9.1.4.1 Enhancement of Check for Registration Numbers
Use
enhancement spot /SCMB/RESTMS_REGNR_CHECK.
6.1.9.1.4.1.2 BAdI: Extend Check for Registration Numbers of Resources
Use
This Business Add-In (BAdI) is used in the Resource (TM-MD-RES) component.

You can use this BAdI to implement additional checks for the registration numbers of resources.
______________________________________________________________
SAP AG 69
SAP System
______________________________________________________________
Standard settings

The BAdI is designed for multiple use.
Activities
Example
This BAdI uses the /SCMB/IF_BADI_TMRES_REGNR_CHK interface. For more information,

display the interface and the class in the Class Builder.
6.1.9.1.5 Agreements
6.1.9.1.5.1 BAdI: Independent Agreement and Calculation Sheet

Determination
Use
This Business Add-In (BAdI) is used in the Charge Management (TM-MD-CM) component.
You can use this BAdI to determine the agreement between the contractor and the contracting
partner without going through the standard agreement determination process.
If an agreement is not determined for one or more settlement documents using this BAdI and
the standard agreement determination process is required, the Continue with Standard
Determination flag can be set. If this flag is not set in this situation, charges will not be
calculated for those settlement documents.
Standard settings
Activities
______________________________________________________________
SAP AG 70
SAP System
______________________________________________________________
More Information

- FA_TARIFF_TCCS_DET
6.1.9.1.5.2 BAdI: Agreement and Calculation Sheet Filter
Use
You can use this BAdI to execute the best logic when there are one or more valid agreements
for a given contractor and contracting partner. When this is the case, the best logic is executed
in the BAdI instead of in the standard implementation. The BAdI logic filters exactly one
agreement for every settlement document. This data is then used for subsequent charge
processing.
Standard settings
Activities
More Information

- FA_TARIFF_TCCS_FILTER
______________________________________________________________
SAP AG 71
SAP System
______________________________________________________________
6.1.9.1.5.3 BAdI: Condition for Agreement Determination
Use
This Business Add-In (BADI) is used in the Charge Management (TM-MD-CM) component.
You can use this BAdI to define your conditions for the agreement header determination. This
BAdI determines if the current agreement is to be used for the given business document.
The return value for EV_EXCLUDE_FA is true if the current agreement is not correct and is
to be skipped. The return value is false if the agreement is to be considered for standard
processing.
The BAdI method for this BAdI is CHECK_CUSTOM_CONDITION and it checks the custom
condition on the agreement header.
Standard settings
Activities
6.1.9.2 Basic Functions
6.1.9.2.1 Charge Calculation
6.1.9.2.1.1 BAdI: Profitability Calculation
Use
You can use this BAdI to allocate cost in the profitability calculation process. The cost
allocation process is based on volume or weight, according to your configuration. This BAdI
allows you to define alternative ways to allocate cost.
______________________________________________________________
SAP AG 72
SAP System
______________________________________________________________
Standard settings
Activities
More Information

- ALLOCATE_COSTS
6.1.9.2.1.2 BAdI: Calculation Sheet Resolution
Use
You can use this BAdI in the calculation sheet resolution process to determine which calculation
sheet should be processed.
Standard settings
Activities
More Information
______________________________________________________________
SAP AG 73
SAP System
______________________________________________________________
- CHECK_TCCS_RESOL_RESTRICTION
- CHECK_APPLICABILITY_RULE
6.1.9.2.1.3 BAdI: Calculation Sheet Process
Use
You can use this BAdI to manipulate automatic charge calculation.
Standard settings
Activities
More Information

- GET_AMOUNT_FOR_TCE_RULE153
- APPLY_RATE_REF_ACCESS_RULE099
- GET_ADJUSTMENT_LOGIC_CLASS_NM
- GET_CALCULATION_LOGIC_CLASS_NM
- APPLY_EXCL_LOGIC
6.1.9.2.1.4 BAdI: Charge Calculation Data Access for Business Objects
Use
______________________________________________________________
SAP AG 74
SAP System
______________________________________________________________
You can use this BAdI to extend the functionality of the data access object for business objects.
You need to implement this BAdI if you have added custom resolution bases or calculation
bases. You would also need to implement this BAdI to override standard resolution or
calculation base implementations.
Requirements
You must make the following Customizing settings:

- In the Customizing activity Define Calculation Bases, you must define calculation bases for
scale bases.
- In the Customizing activity Define Resolution Bases, you must define the calculation
resolution bases.
Standard settings
Activities
More Information

- GET_RES_BASE_KEYS
- GET_CALC_BASE_VALUES
- GET_CALC_BASE_COMM
6.1.9.2.1.5 BAdI: Charge Calculation Rules
Use
You can use this BAdI to apply different techniques to calculate charges in the following areas:
- Freight agreement
- Forwarding agreement
______________________________________________________________
SAP AG 75
SAP System
______________________________________________________________
- Calculation sheet
- Rate table
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the
Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
More Information

- AGREEMENT_EXCLUSION
- CALC_SHEET_PRECONDITION
- CALC_SHEET_ITEM_PRECONDITION
- RATE_TABLE_DETERMINATION
- CHARGE_CALC_THROUGH_FORMULA
6.1.9.2.1.6 BAdI: Charge Calculation Engine
Use
You can use this BAdI to enhance any of the main steps in the charge calculation engine. This
includes the following:
- Agreement and calculation sheet determination
- Calculation sheet resolution
- Calculation sheet processing
The BAdI methods are called after each step is executed to allow the modification of the step
results.
______________________________________________________________
SAP AG 76
SAP System
______________________________________________________________
Note
All methods are mass enabled, therefore multiple requests can be processed within one call. In
general, a request key is used to uniquely identify requests in the input and output data. All
methods have an import parameter, called IS_REQUEST, that contains all necessary request
data. Component BUS_DATA_ACCESS is a reference to the business data access object, which
provides access to the logistical data of the underlying request. Component T_REQUEST_DATA
is a nested table that contains the request keys for the call.
Standard settings
Activities
See Also

- DETERMINE_CALCULATION_SHEETS
- RESOLVE_CALCULATION_SHEETS
- PROCESS_CALCULATION_SHEETS
6.1.9.2.2 Dangerous Goods
6.1.9.2.2.1 Notes on Implementation
Use
enhancement spot /SCMTMS/ES_EHS_DG.
______________________________________________________________
SAP AG 77
SAP System
______________________________________________________________
6.1.9.2.2.2 BAdI: Definition of Data for Printing and Checking for Dangerous
Goods
Use
This Business Add-in (BAdI) is used in the Integration with SAP Environment, Health and
Safety Management (TM-DG-EHS) component. You can use this BAdI to change, delete, or
extend the input data for the dangerous goods check and the printing data for dangerous goods.
The BAdI is called before the system performs the dangerous goods check.
The BAdI contains the following methods:
- CHECK_DG_BC
Change Dangerous Goods Check Data.
- PRINTING_DATA_CHANGE
Change Dangerous Goods Printing Data.
When you implement this BAdI, the system might override the Customizing settings under SAP
Transportation Management -> SCM Basis -> EH&S Services -> Dangerous Goods
Management -> Dangerous Goods Checks and Dangerous Goods Management -> Dangerous
Goods Checks -> Specify Dangerous Goods Check Methods.
This BAdI provides defined interfaces, but no implementation.
Standard settings
Activities
Example
You can find example implementations in the BAdI Builder on the Enhancement Spot
Element Definitions tab in the Implementation Example Classes section.
The following example implementation is available:
- /SCMTMS/CL_EX_BADI_EHS_DG
Manipulation of the dangerous goods check. The check of definite item data is eliminated.
______________________________________________________________
SAP AG 78
SAP System
______________________________________________________________
6.1.9.2.3 Type Codes and Role Codes
Use
enhancement spot /SCMTMS/QTY_TYPE_CODE_DET.
6.1.9.2.3.2 BAdI: Quantity Type Code Determination
Use
This Business Add-In (BAdI) is used in the Transportation Management (SCM-TM) component.
You can use this BAdI to adapt the quantity type code determination in the inbound message
processing.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCMTMS/IF_QTY_TYPE_CODE_DET. For more
______________________________________________________________
SAP AG 79
SAP System
______________________________________________________________
information, display the interface in the Class Builder.
6.1.9.2.4 Change Controller
Use
enhancement spot /SCMTMS/TOR_CHACO.
6.1.9.2.4.2 BAdI: Determination of Changes for Change Controller
Use
This Business Add-In (BAdI) is used in the Basic Functions (TM-BF) component. You can use
this BAdI to enhance the standard logic of the change controller for determining changes to one
of the following business documents:
- Freight order
- Freight booking
- Freight unit
You can also use this BAdI to replace the standard logic with your own logic.
Standard settings
Activities
______________________________________________________________
SAP AG 80
SAP System
______________________________________________________________
See also

- SET_BADI_WORK_MODE
- DET_DATE_AND_LOC_CHANGES
- DET_QUANTITY_CHANGES
- DET_CUSTOM_CHANGES
6.1.9.2.5 Business Warehouse
Use
enhancement spot /SCMTMS/BW_EXTRACTION.
6.1.9.2.5.2 BAdI: Condition for Extraction
Use
This Business Add-In (BAdI) is used in the Integration with SAP NetWeaver Business
Warehouse (TM-BW) component. You can use this BAdI to change the condition for
extracting business document information from the SAP Transportation Management (SAP TM)
system to the SAP NetWeaver Business Warehouse (SAP NetWeaver BW) system.
The system extracts data for the initial upload (with data) and the delta upload. The system
extracts data only for the business document types for which you have selected the BW
Relevance checkbox; you cannot use this BAdI to change the BW Relevance setting.
The standard condition uses the life-cycle status to determine whether data is to be extracted.
For the initial upload, only completed business documents are extracted (that is, their life-cycle
status has the value Completed). For the delta upload, business documents with the following
life-cycle status values are also extracted:
______________________________________________________________
SAP AG 81
SAP System
______________________________________________________________
- Business documents whose life-cycle status has the value Canceled.

- Business documents whose life-cycle status was changed from Completed to another value
(such as In Process).
Canceled business documents and those changed from Completed to another value are extracted
to the SAP NetWeaver BW system in order to be deleted.
You can use the following BAdI methods for the initial upload:
- TOR_BW_CONDITION_INIT
- TRQ_BW_CONDITION_INIT
- SFIR_BW_CONDITION_INIT
- CFIR_BW_CONDITION_INIT
You can use the following BAdI methods for the delta upload:
- TOR_BW_CONDITION_DELTA
- TRQ_BW_CONDITION_DELTA
- SFIR_BW_CONDITION_DELTA
- CFIR_BW_CONDITION_DELTA
Requirements
You have specified that the business document type is BW-relevant in one of the following
Customizing activities:
Standard settings
Activities
______________________________________________________________
SAP AG 82
SAP System
______________________________________________________________
6.1.9.2.5.3 BAdI: Fill Extraction Structures
Use
Warehouse (TM-BW) component. You can use this BAdI to enhance the extraction structures
for the extraction of business document information from the SAP Transportation Management
(SAP TM) system to the SAP NetWeaver Business Warehouse (SAP NetWeaver BW) system.
You can create an append for an extraction structure of a business document. This BAdI fills
the fields in the append with values from the business document.
Standard settings
Activities
6.1.9.2.6 Geographical Map
6.1.9.2.6.1 Enhancement to Adapt Displayed Objects
Use
All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
//SCMTMS/ES_MAP_ADAPT_SCENE.
______________________________________________________________
SAP AG 83
SAP System
______________________________________________________________
6.1.9.2.6.1.2 BAdI: Enhancement to Adapt Displayed Objects
Use
This Business Add-In (BAdI) is used in the Map Display (TM-BF-MAP) component. You can
use this BAdI to influence the objects currently displayed on the geographical map.
Requirements
You have installed the geographical map for your SAP TM system.
Standard settings
Spot Element Definitions tab in the BAdI Builder (transaction SE18)
Activities
Example
Objects to be displayed on the geographical map are passed in the following format:
Changeable fields:
MO_ID - Readable identifier of map object
MO_ROLES - Role of map object
MO_DESCRIPTION - Description fields
MO_POSITION - Geographical position of spot
MO_START_POSITION - Geographical position of link start
MO_DEST_POSITION - Geographical position of link destination
FIXED - Map object is fixed for currently displayed objects
ACTION_REQUIRED - For map object action is required
ROUTE_POINTS - Waypoints of route
VISIBLE - Map object visibility status
______________________________________________________________
SAP AG 84
SAP System
______________________________________________________________
SELECTED - Map object selection status

HIGHLIGHTED - Map object highlight status
Fixed fields (if you change the content of the following field, the consistency of the displayed
objects cannot be guaranteed):
MO_GUID - Unique technical identifier of map object
MO_START_GUID - Unique identifier of link start
MO_DEST_GUID - Unique identifier of link destination
MO_TYPE - Map object type
MO_MULTI_GUID - Superior map object
MO_COUNT - Number of grouped map objects
See also
This BAdI definition uses the interface /SCMTMS/IF_EX_MAP_ADAPT_SCENE. For more

6.1.9.2.7 Authorizations
6.1.9.2.7.1 Authorization Check
Use
enhancement spot /SCMTMS/AC_BADI.
______________________________________________________________
SAP AG 85
SAP System
______________________________________________________________
6.1.9.2.7.1.2 BAdI: Authorization Check
Use
This Business Add-In (BAdI) is used in the Authorization Check (TM-BF-AUT) component.
You can use this BAdI to change the standard authorization check for business document types
before or after the system performs the standard authorization check.
Standard settings
Activities
See also

- BEFORE_AUTHCHK
- AFTER_AUTHCHK
- FILTER_DATA
6.1.9.2.7.2 Output Management
Use
enhancement spot /SCMTMS/AC_PPF.
______________________________________________________________
SAP AG 86
SAP System
______________________________________________________________
6.1.9.2.7.2.2 BAdI: Register Additional BOs for TM Authorization Check
Use
This Business Add-In (BAdI) is used in the Transportation Management component. You can
use this BAdI to define authority checks that are carried out before Post Processing Framework
(PPF) actions are executed using business object /BOFU/PPF_OUPUT_CONTENT.
The BAdI is called before the PPF action is triggered and an authority check needs to be
performed.
Requirements
You have registered business objects in the PPF authorization check class.
Standard settings
In the standard settings, actions PRINT of business object /SCMTMS/TRQ and

IMMEDIATE_PRINT of business object /SCMTMS/TOR are registered for authorization checks.
Activities
To register further business object actions, implement method ADAPT_PPF_BO_REGISTRATION

and add the BO key and the action key to changing table CT_REGISTRY.
Specify further authorization checks within method BEFORE_AUTHCHK of BAdI: Authorization
Check.
6.1.9.2.7.3 Data Retrieval Before Authorization Check
______________________________________________________________
SAP AG 87
SAP System
______________________________________________________________
Use
enhancement spot /SCMTMS/AC_DATA_BADI.
6.1.9.2.7.3.2 BAdI: Data Retrieval Before Authorization Check
Use
You can use this BAdI to change or extend the default data retrieval for authorization checks
before they are performed.
Standard settings
Activities
See also

- GET_DATA
- FILTER_DATA
______________________________________________________________
SAP AG 88
SAP System
______________________________________________________________
6.1.9.2.8 Query Extensions
Use
enhancement spot /SCMTMS/FRW_QUERY.
6.1.9.2.8.2 BAdI: Query Extensions
Use
this BAdI to extend queries for business documents.
Requirements
- If you want to extend the selection parameters of the query, you must first extend the
query structure by adding these parameters.
- If you want to extend the result structure of the query, you must first extend it by adding
the additional attributes.
Standard settings
Activities
See also
______________________________________________________________
SAP AG 89
SAP System
______________________________________________________________
- QUERY
6.1.9.3 Forwarding Order Management
6.1.9.3.1 Approval Workflow
Use
enhancement spot /SCMTMS/TRQ_APPR_CHECK_BO.
6.1.9.3.1.2 BAdI: Specific Checks for Approval Workflow in FWO

Management
Use
This Business Add-In (BAdI) is used in the Forwarding Order Management (TM-FWM)
component.
You can use this BAdI to check mandatory fields in the business documents of forwarding
order management (business object: transportation request, TR) before proceeding with the
approval workflow. You can use the BAdI method CHECK_BO.
Requirements
In the standard system, there is an activated BAdI implementation.
Standard settings
For more information about the standard settings (filters and single or multiple uses), see the
Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).
______________________________________________________________
SAP AG 90
SAP System
______________________________________________________________
Activities
Example
This BAdI uses the interface /SCMTMS/IF_TRQ_APPR_CHECK_BO and the standard

implementation /SCMTMS/IMP_TRQ_APPR_CHECK_BO. For more information, display the
interface and the class in the Class Builder.
6.1.9.3.2 Registry Extensions
Use
enhancement spot /SCMTMS/FIELD_REGISTRY.
6.1.9.3.2.2 BAdI: Extensions of Field Registry
Use
This Business Add-In (BAdI) is used in the Forwarding Order Management component. You can
use this BAdI to check the relevance of node attributes, and it is called by the constructor of
the field registry super class.
Standard settings
The list of relevant fields is defined in the constructor of a class inherited from the field
registry super class /SCMTMS/CL_FIELD_REGISTRY. Sub classes must always be created with
private instantiation and public static method GET_INSTANCE (singleton pattern), which creates
______________________________________________________________
SAP AG 91
SAP System
______________________________________________________________
one instance of the sub class once for each transaction.

Activities
Method MODIFY_REGISTRY can be used to specify lists of node attributes that are to be
added to or removed from the field registry. This enables you to change the list of relevant
fields.
6.1.9.4 Freight Order Management
6.1.9.4.1 Tendering
Use
enhancement spot /SCMTMS/TEND.
6.1.9.4.1.2 BAdI: Creation of Proposals for Tendering Plan
Use
This Business Add-In (BAdI) is used in the Freight Tendering (TM-FRM-FRT) component. You
can use this BAdI to propose carriers and price limits in a tendering plan.
______________________________________________________________
SAP AG 92
SAP System
______________________________________________________________
Standard settings
We do not provide a standard BAdI implementation. However, you do not need to implement
this BAdI to use the standard logic. The standard logic is implemented in methods
ADD_PREF_TSP and PROPOSE_PRICE_LIMIT of class
/SCMTMS/CL_TEND_A_CRT_PROPOSAL, and can be overwritten or enhanced by your BAdI
implementation.
Activities
More Information

FILL_ADDITIONAL_NODE_DATA
Set the Work Mode of the BAdI
Add Preferred Carrier to Tendering Configuration
Propose Price Limit
6.1.9.4.1.3 BAdI: Evaluation of Quotations
Use
can use this BAdI to evaluate your freight requests for quotation by defining codes that rate a
quotation as one of the following:
- Quotation acceptable (ACC)
- Quotation review required (REV)
- Quotation not acceptable (NAC)
- Freight request for quotation rejected by carrier (REJ)
- Quotation received after response time (2L8)
- Quotation contains errors (ERR)
______________________________________________________________
SAP AG 93
SAP System
______________________________________________________________
In addition, you can modify the currency conversion for an incoming quotation.
Requirements
You need to create your BAdI implementation to overrule or modify the standard logic in
regards to evaluating freight requests for quotation.
Standard settings
There is no standard BAdI implementation provided by SAP. However, you do not need to
implement this BAdI to use the standard logic. The standard logic is implemented in class
/SCMTMS/CL_TEND_A_EVAL_RESP and can be overruled or enhanced by your own BAdI
implementation.
Activities
More Information

Set Evaluation Result for Tendering Responses
6.1.9.4.1.4 BAdI: Determination of Addresses and Contact Persons for

Tendering
Use
can use this BAdI to retrieve address information of carrier contacts, tendering managers, and
other parties specified in the freight order. You need this data for sending out freight requests
______________________________________________________________
SAP AG 94
SAP System
______________________________________________________________
for quotation and receiving responses afterwards.
Requirements
You need to create your BAdI implementation in order to overrule or modify the standard logic
in regards to address determination.
Standard settings
/SCMTMS/CL_TEND_BUPA_TOOLS and can be overruled or enhanced by your own BAdI
implementation.
Activities
More Information

Get Carrier Contact Information with Addresses
Get Tendering Manager Information
Get Party Information
6.1.9.4.1.5 BAdI: Preselection of Freight Requests for Quotation
Use
can use this BAdI to preselect freight requests for quotation (RFQs).
When a tendering process is finished, the system preselects the most favorable freight RFQ. In
the case of a manual tendering, the tendering manager can then accept or reject the preselected
freight RFQ or can preselect or accept a different RFQ. In the case of an automatic tendering,
______________________________________________________________
SAP AG 95
SAP System
______________________________________________________________
the system automatically accepts the preselected RFQ and sends the updated freight order to the
carrier that provided the preselected freight RFQ.
Requirements
regards to the pre-selection of freight RFQs.
Standard settings
implement this BAdI to use the standard logic. The standard logic is implemented in method
PRESELECT_RESPONSE of class /SCMTMS/CL_TEND_A_PROC_CONTROL and can be
overruled or enhanced by your own BAdI implementation.
Activities
More Information

Preselect Freight Request for Quoatation (RFQ)
6.1.9.4.1.6 BAdI: Filling of Result Structure for Forwarding and Freight RFQs
Use
This Business Add-In (BAdI) is used in the Freight Tendering (TM-FRM-FRT) component. The
BAdI can be used in the environment of queries for freight request for quotations (freight
RFQs) and forwarding request for quotations (forwarding RFQs), in particular for the tendering
manager and external carriers. You can use this BAdI to fill or change the result structure of
queries that are based on the query class /SCMTMS/CL_TEND_Q_REQ_RESP.
This applies to the following queries of the business object /SCMTMS/TOR:
______________________________________________________________
SAP AG 96
SAP System
______________________________________________________________
Node Name Query Name

TENDERINGREQUEST QDB_TENDERINGREQUEST_BY_ELEMEN
TENDERINGREQUEST QDB_TEND_REQUEST_BY_WEB_USER
TENDERINGREQUEST QDB_TENDERINGREQ_BY_ELEME_EXT
TENDERINGRESPONSE QDB_TENDERINGRESP_BY_ELEMENTS
TENDERINGRESPONSE QDB_TEND_RESPONSE_BY_WEB_USER
TENDERINGRESPONSE QDB_TENDERINGRESP_BY_ELEME_EXT
TENDERINGRESPONSE QDB_TENDERINGRESP_MANUAL_ACT
Requirements
You need to create a BAdI implementation to overwrite or change the standard logic in the
result structure of the above queries.
Standard settings
this BAdI to use the standard logic. The standard logic is implemented in method
FILL_RESULT_STRUCTURE of class /SCMTMS/CL_TEND_Q_REQ_RESP and can be
overwritten or enhanced by your BAdI implementation.
Activities
More Information

Fill Result Structure
______________________________________________________________
SAP AG 97
SAP System
______________________________________________________________
6.1.9.4.1.7 BAdI: Filling of Result Structure for Tendering Query
Use
can use the BAdI in the environment of queries for freight orders and tenderings. You can use
this BAdI to fill or modify the result structure of queries that are based on the query class
/SCMTMS/CL_TEND_Q_SUBCON_TEND. This applies to the following queries of the business
object /SCMTMS/TOR:
SUBCONTRACTING QDB_SUBCONTRACTING_BY_ELEMENTS
TENDERING QDB_TENDERING_BY_ELEMENTS
Requirements
regards to the result structure of the above-mentioned queries.
Standard settings
FILL_RESULT_STRUCTURE of class /SCMTMS/CL_TEND_Q_SUBCON_TEND and can be
Activities
More Information

______________________________________________________________
SAP AG 98
SAP System
______________________________________________________________
6.1.9.4.1.8 BAdI: Sending of Tendering E-Mails
Use
can use this BAdI to send e-mail or SMS messages for notifications or freight request for
quotations (freight RFQs) to the contact person of a carrier for specific events in the tendering
process.
The system can send different e-mail or SMS message types. For example, the system can send
a message informing a contact person that a tendering process has been canceled. The system
can send a message for each individual event. It can also collect the messages for a particular
period of time, and send a single message containing all the information about each single
event.
Requirements
You need to create a BAdI implementation if you want to change the standard system logic for
sending tendering e-mails or SMS messages.
Standard settings
There are four different e-mail types in the standard logic for e-mails. In these, we implement
the logic for sender determination, recipient determination, text determination, and trigger
creation and validation. These e-mail types are for the following events:
- Canceled tendering processes
- Sent freight RFQs
- Awarded freight quotations (FQs)
- Rejected FQs
this BAdI if you want to use the standard logic. We implement the standard logic in the
following methods and report:
- Method SEND_NOTIFICATION_MAIL of classes /SCMTMS/CL_TEND_D_TENDREQ_AC
and /SCMTMS/CL_TEND_D_TENDRESP_AC
- Methods of class /SCMTMS/CL_TEND_CS_HELPER
- Report /SCMTMS/TEND_NOTIFICATION_MAIL
You can overwrite or enhance the standard logic with your own BAdI implementation.
______________________________________________________________
SAP AG 99
SAP System
______________________________________________________________
Activities
- Set the Work Mode of the BAdI
- DETERMINE_RECIPIENT
- DETERMINE_SENDER
- GET_TEXT
- CREATE_TRIGGER_AFTER_COMMIT
- VALIDATE_TRIGGERS
6.1.9.4.1.9 BAdI: Triggering of Alerts
Use
can use this BAdI to trigger the creation of additional alerts for the tendering process. You can
also create and use your own alert categories in this BAdI. You can decide whether the alerts
are to be created in addition to or instead of the standard tendering alerts.
Requirements
Alert categories need to be maintained in transaction ALRTCATDEF to be able to create alerts

of those categories later on. If dynamic alert texts are to be set by the BAdI, you must
maintain containers and the message short and long texts accordingly.
Standard settings
TRIGGER_ALERT of class /SCMTMS/CL_TEND_D_TENDERING_AC and can be overruled or
enhanced by your own BAdI implementation.
______________________________________________________________
SAP AG 100
SAP System
______________________________________________________________
Activities
More Information

Trigger Tendering Alerts
6.1.9.4.1.10 BAdI: Update of Freight Order (FO) After Successful Tendering
Use
can use this BAdI to update those fields of the freight order after a successful completion of a
tendering process that you determined with this BAdI.
Standard settings
There is no standard BAdI implementation provided by SAP. However, there is no need to
/BOBF/IF_FRW_ACTION~EXECUTE of class /SCMTMS/CL_TEND_A_UPDATE_TOR and
can be overruled or enhanced by your own BAdI implementation.
Activities
______________________________________________________________
SAP AG 101
SAP System
______________________________________________________________
More Information

Update Freight Order Data after Successful Tendering
6.1.9.4.1.11 BAdI: Restart of Tendering Upon Confirmation Rejection by

Assigned Carrier
Use
can use this BAdI to implement your own logic in regards to restarting a tendering process in
case an already assigned carrier, which has been determined by tendering previously, rejects his
or her confirmation. Thus a new carrier has to be determined.
Even if a carrier has already been assigned to a freight order, the carrier has still the
possibility of rejecting the freight order by sending a respective rejecting confirmation. By doing
so, a new carrier needs to be determined for this freight order. In case this carrier has been
determined earlier as the result of a tendering process, tendering can be used again for carrier
determination. This depends on whether or not this option has been selected in the
corresponding tendering process settings in Customizing, and thus a new tendering needs to be
started.
Requirements
in regards to restarting the tendering process.
Standard settings
/BOBF/IF_FRW_ACTION~EXECUTE of class /SCMTMS/CL_TEND_A_CHACO_RESTRT and
The standard logic starts a new tendering with basically the same tendering plan as the previous
tendering, which had determined the carrier that has now rejected the tendered freight order.
Since this carrier has already rejected the freight order, there is no need for him or her to
participate again in this new tendering - thus, this carrier is removed from the new tendering
______________________________________________________________
SAP AG 102
SAP System
______________________________________________________________
plan.
Activities
More Information
Modify Tendering Plan to Be Used After Restart
6.1.9.5 Planning
6.1.9.5.1 BAdI: Determination of Subcontracting-Relevant Quantity
Use
This Business Add-In (BAdI) is used in the Carrier Selection (TM-PLN-CS) component.
You can use this BAdI to implement your own logic (GET_TOR_QUANTITY) for influencing
or replacing the logic used for calculating the overall quantity of a business document that can
be subcontracted (for example, a freight unit or freight order). The system takes this quantity
into account as the overall quantity in the subcontracting area when it calculates costs or loads
specific transportation allocations.
Note:
This logic influences the quantity assigned to a business document in the complete
subcontracting area. The result of this logic might be an input of the transportation allocation
specific quantity determination which influences only the loading quantity of a specific bucket.
Requirements
You need to create your BAdI implementation to overrule or modify the standard logic that
determined the overall loading quantity.
Standard settings
______________________________________________________________
SAP AG 103
SAP System
______________________________________________________________
implement this BAdI to use the standard logic
Activities
6.1.9.5.2 BAdI: Calculation of TAL Relevant Quantity
Use
This Business Add-In (BAdI) is used in the Transportation Allocation (TM-PLN-TAL)

component.
You can use this BAdI to implement your own logic (GET_LOADING_QUANTITY) for
influencing the loading quantity. The free capacity of the relevant buckets will be decreased by
the determined value in the case of loading a transportation allocation and will be increased by
this value in case of unloading respectively.
Requirements
Standard settings
implement this BAdI to use the standard logic.
Activities
______________________________________________________________
SAP AG 104
SAP System
______________________________________________________________
6.1.9.5.3 Additional Dimensions
Use
/SCMTMS/ADD_DIMENSIONS.
6.1.9.5.3.2 BAdI: Additional Dimensions
Use
This Business Add-In (BAdI) is used in the Planning (TM-PLN) component. You can use this
BAdI to add additional dimensions during processing.
In the standard system, the quantity structure /SCMTMS/S_QUANTITIES from the item of the
BO transportation order includes the following dimensions:
- Mass
- Volume
- No dimensions (for example, pieces)
By enhancing this structure, you can add additional dimensions.
To guarantee that these new dimensions are taken into account, you must implement this BAdI
and fill table CT_DIMENSIONS with the dimensions you want to be handled during processing
of the BO transportation order.
Standard settings
______________________________________________________________
SAP AG 105
SAP System
______________________________________________________________
Activities
Example
You want to make sure that dimension LENGTH is processed in the capacity check.
6.1.9.5.4 VSR Optimizer
6.1.9.5.4.1 VSR Optimizer Preprocessing and Postprocessing
Use
enhancement spot /SCMTMS/PLN_OPT.
6.1.9.5.4.1.2 BAdI: VSR Optimizer Preprocessing
Use
This Business Add-In (BAdI) is used in the VSR Optimizer Preprocessing/Postprocessing

(TM-PLN-VSR-OPP) component.
You can use this BAdI to change input data for VSR optimization.
Standard settings
______________________________________________________________
SAP AG 106
SAP System
______________________________________________________________
Activities
6.1.9.5.4.1.3 BAdI: VSR Optimizer Postprocessing
Use

You can use this BAdI to change VSR optimizer results.
Standard settings
Activities
6.1.9.5.4.2 Explanation Tool: Customer Function
______________________________________________________________
SAP AG 107
SAP System
______________________________________________________________
Use
enhancement spot /SCMTMS/PLN_EXP.
6.1.9.5.4.2.2 BAdI: Customer Function for Explanation Tool
Use
This Business Add-In (BAdI) is used in the Planning (TM-PLN) component.

You can use this BAdI to implement customer functions within the explanation tool of the
optimizer. Within the explanation tool, a pushbutton is provided with which you can call this
BAdI.
Method:
- CUST_FUNC
Parameters:
- IV_PLN_EXP_BO_KEY: Persistent key of the business object of type
/SCMTSM/PLN_EXPL.
- IT_SELECTED_NODES: Business object nodes and keys of the objects that were selected
on the UI.
- CT_MSG: Can be filled with messages that are shown on the UI after the BAdI was
called.
Standard settings
Activities
______________________________________________________________
SAP AG 108
SAP System
______________________________________________________________
6.1.9.6 Global Trade
6.1.9.6.1 Notes on Implementation
Use
enhancement spot /SCMTMS/GT_ACTIVITIES.
6.1.9.6.2 BAdI: Change Result of Customs Relevance Check
Use
This Business Add-In (BAdI) is used in the Transportation Management (TM) component.
You can use this BAdI to change or extend data transferred through the interface
/SCMTMS/IF_GT_REL_ACTIVITY to modify the customs relevance check.
The interface is part of the customs solution of the freight order.
Requirements
You have activated the customs relevance check in Customizing for SAP Transportation
Management (TM) under Define Customs Relevance Check.
Standard settings
Activities
______________________________________________________________
SAP AG 109
SAP System
______________________________________________________________
Example
If you never use a certain freight order type, for example, ZZDE, you can exclude it from the
settings of the customs relevance check.
6.1.9.7 Integration
6.1.9.7.1 Tracking and Tracing of Processes and Documents
6.1.9.7.1.1 BAdI: Providing Execution Data for Transportation Activities
Use
This Business Add-In (BAdI) is used in the Integration with SAP Event Management
(TM-EM) component.
You can use this BAdI to process your own events for tracking the execution of physical
transports in SAP Transportation Management in a specific way.
If you define your own transportation activities and events for tracking and tracing (see Define
Transportation Activities for Tracking and Tracing), you can use this BAdI to react on those
specific events. We recommend that you use this BAdI especially in combination with an
enhancement of the extension structure /SCMTMS/INCL_EEW_TOR_EXEC, which is assigned
to the EXECUTIONINFORMATION node of business object /SCMTMS/TOR (see transaction
/BOBF/CONF_UI). The BAdI is called when an incoming event is processed.
Standard settings
Activities
Based on the importing structures and tables, the changing parameter table CT_MODIFY has to
be filled according to the method PROVIDE_CR_UPD_EXECINF of class
/SCMTMS/CL_TOR_EXEC_PROCESS.
This table is used to create or update nodes of the current processed document, for example,
freight unit. We recommend that you mainly update the execution data of the processed
document.
______________________________________________________________
SAP AG 110
SAP System
______________________________________________________________
More Information

- PROCESS_EVENT
6.1.9.7.2 Enterprise Services
6.1.9.7.2.1 Forwarding Order Management
6.1.9.7.2.1.1 Transportation Request
Use
All Business Add-Ins (BAdIs) that are grouped under this structure node belong to enhancement
spot /SCMTMS/TRQ_SE_SPOT_TRQ.
6.1.9.7.2.1.1.2 BAdI for TransportationRequestRequest_In
Use
This Business Add-in (BAdI) is used in the Transportation Management (TM) component. You
can use this BAdI to change or extend the data transferred through the service interface
TransportationRequestRequest_In, which is part of the Transportation Request Processing process
component.
______________________________________________________________
SAP AG 111
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.1.1.3 BAdI for TransportationRequestCancellationRequest_In
Use
TransportationRequestCancellationRequest_In, which is part of the Transportation Request
Processing process component.
Standard settings
Activities
6.1.9.7.2.1.1.4 BAdI for TransportationRequestConfirmation_Out
Use
TransportationRequestConfirmation_Out, which is part of the Transportation Request Processing
______________________________________________________________
SAP AG 112
SAP System
______________________________________________________________
process component.
Standard settings
Activities
6.1.9.7.2.2 Freight Order Management
6.1.9.7.2.2.1 Transportation Order
Use
spot /SCMTMS/TOR_SE_SPOT_TOR.
6.1.9.7.2.2.1.2 BAdI for TransportationOrderRequest_Out
Use
TransportationOrderRequest_Out, which is part of the Transportation Order Processing process
component
______________________________________________________________
SAP AG 113
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.2.1.3 BAdI for TransportationOrderCancellationRequest_Out
Use
TransportationOrderCancellationRequest_Out, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.1.4 BAdI for TransportationOrderConfirmation_In
Use
______________________________________________________________
SAP AG 114
SAP System
______________________________________________________________
TransportationOrderConfirmation_In, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
6.1.9.7.2.2.2 Tendering
6.1.9.7.2.2.2.1 Transportation Request
6.1.9.7.2.2.2.1.1 Notes on Implementation
Use
6.1.9.7.2.2.2.1.2 BAdI for TransportationRequestQuotationCreateRequest_In
Use
______________________________________________________________
SAP AG 115
SAP System
______________________________________________________________
TransportationRequestQuotationCreateRequest_In, which is part of the Transportation Request

Standard settings
Activities
6.1.9.7.2.2.2.1.3 BAdI for TransportationRequestQuotationCancellationReq_In
Use
TransportationRequestQuotationCancellationRequest_In, which is part of the Transportation
Request Processing process component.
Standard settings
Activities
______________________________________________________________
SAP AG 116
SAP System
______________________________________________________________
6.1.9.7.2.2.2.1.4 BAdI for TransportationRequestQuotationConfirmation_Out
Use
TransportationRequestQuotationConfirmation_Out, which is part of the Transportation Request
Standard settings
Activities
6.1.9.7.2.2.2.2 Transportation Order
Use
6.1.9.7.2.2.2.2.2 BAdI for TransportationOrderQuotationCreateRequest_Out
Use
______________________________________________________________
SAP AG 117
SAP System
______________________________________________________________
TransportationOrderQuotationCreateRequest_Out, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.2.2.3 BAdI for

TransportationOrderQuotationCancellationRequest_Out
Use
TransportationOrderQuotationCancellationRequest_Out, which is part of the Transportation Order
Standard settings
Activities
______________________________________________________________
SAP AG 118
SAP System
______________________________________________________________
6.1.9.7.2.2.2.2.4 BAdI for TransportationOrderQuotationConfirmation_In
Use
TransportationOrderQuotationConfirmation_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.3 Booking
Use
______________________________________________________________
SAP AG 119
SAP System
______________________________________________________________
6.1.9.7.2.2.3.1.2 BAdI for TransportationOrderBookingRequest_Out
Use
TransportationOrderBookingRequest_Out, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
6.1.9.7.2.2.3.1.3 BAdI for

TransportationOrderBookingCancellationRequest_Out
Use
TransportationOrderBookingCancellationRequest_Out, which is part of the Transportation Order
Standard settings
______________________________________________________________
SAP AG 120
SAP System
______________________________________________________________
Activities
6.1.9.7.2.2.3.1.4 BAdI for TransportationOrderBookingConfirmation_In
Use
TransportationOrderBookingConfirmation_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.3.1.5 BAdI for TransportationOrderBookingWaybillNotification_Out
Use
TransportationOrderBookingWaybillNotification_Out, which is part of the Transportation Order
______________________________________________________________
SAP AG 121
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.3 Global Trade
6.1.9.7.2.3.1 Request for Export Declaration
Use
spot /SCMTMS/ECA_SE_SPOT_TOR.
6.1.9.7.2.3.1.2 BAdI for ExportDeclarationSUITERequest_Out
Use
ExportDeclarationSUITERequest_Out, which is part of the Transportation Order Processing
process component.
______________________________________________________________
SAP AG 122
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.3.2 Cancellation Request for Export Declaration
Use
spot /SCMTMS/EXP_SE_SPOT_TOR.
6.1.9.7.2.3.2.2 BAdI for ExportDeclarationSUITECancellationRequest_Out
Use
ExportDeclarationSUITECancellationRequest_Out, which is part of the Transportation Order
Standard settings
______________________________________________________________
SAP AG 123
SAP System
______________________________________________________________
Activities
6.1.9.7.2.3.3 Confirmation of Export Declaration
Use
spot /SCMTMS/EIN_SE_SPOT_TOR.
6.1.9.7.2.3.3.2 BAdI for ExportDeclarationSUITEConfirmation_In
Use
ExportDeclarationSUITEConfirmation_In, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
______________________________________________________________
SAP AG 124
SAP System
______________________________________________________________
6.1.9.7.2.4 Settlement
6.1.9.7.2.4.1 Forwarding Settlement
Use
spot /SCMTMS/CFI_SE_SPOT_CFIR.
6.1.9.7.2.4.1.2 BAdI for CustomerFreightInvoiceRequestSUITERequest_Out_V1
Use
CustomerFreightInvoiceRequestSUITERequest_Out_V1, which is part of the Customer Freight
Invoice Request Processing process component.
Standard settings
Activities
______________________________________________________________
SAP AG 125
SAP System
______________________________________________________________
6.1.9.7.2.4.1.3 BAdI for CustFreightInvoiceReqSUITECancellationReq_Out_V1
Use
CustomerFreightInvoiceRequestSUITECancellationRequest_Out_V1, which is part of the Customer
Freight Invoice Request Processing process component.
Standard settings
Activities
6.1.9.7.2.4.1.4 BAdI for CustFreightInvoiceRequestSUITEConfirmation_In_V1
Use
CustomerFreightInvoiceRequestSUITEConfirmation_In_V1, which is part of the Customer Freight
Standard settings
Activities
______________________________________________________________
SAP AG 126
SAP System
______________________________________________________________
6.1.9.7.2.4.2 Freight Settlement
Use
spot /SCMTMS/SFI_SE_SPOT_SFIR.
6.1.9.7.2.4.2.2 BAdI for TranspOrderSUITEInvoicingPreparationRequest_Out
Use
TransportationOrderSUITEInvoicingPreparationRequest_Out, which is part of the Transportation
Order Processing process component.
Standard settings
Activities
______________________________________________________________
SAP AG 127
SAP System
______________________________________________________________
6.1.9.7.2.4.2.3 BAdI for TranspOrderSUITEInvoicingPreparationCancellatn_Out
Use
TransportationOrderSUITEInvoicingPreparationCancellation_Out, which is part of the
Transportation Order Processing process component.
Standard settings
Activities
6.1.9.7.2.4.2.4 BAdI for TranspOrderSUITEInvoicingPreparationConfirmation_In
Use
TransportationOrderSUITEInvoicingPreparationConfirmation_In, which is part of the
Standard settings
Activities
______________________________________________________________
SAP AG 128
SAP System
______________________________________________________________
6.1.9.7.2.5 ERP Logistics Integration
Use
6.1.9.7.2.5.1.2 BAdI for IntracompanyTransportationRequestRequest_In
Use
IntracompanyTransportationRequestRequest_In, which is part of the Transportation Request
Standard settings
Activities
______________________________________________________________
SAP AG 129
SAP System
______________________________________________________________
6.1.9.7.2.5.1.3 BAdI for IntracompanyTranspRequestCancellationRequest_In
Use
IntracompanyTransportationRequestCancellationRequest_In, which is part of the Transportation
Standard settings
Activities
6.1.9.7.2.5.1.4 BAdI for

IntracompanyTranspRequestSimulateReqConfirmation_In
Use
This Business Add-in (BAdI) is used in the Order Scheduling (TM-ERP-OS) component. You
IntracompanyTransportationRequestSimulateRequestConfirmation_In, which is part of the
Transportation Request Processing process component.
Standard settings
Activities
______________________________________________________________
SAP AG 130
SAP System
______________________________________________________________
6.1.9.7.2.5.2 Outbound Processing of Delivery Proposals
Use
spot /SCMTMS/DLVP_SPOT_SE_OUT.
6.1.9.7.2.5.2.2 BAdI for InboundDeliveryCreateRequest_Out
Use
This Business Add-in (BAdI) is used in the Delivery Creation (TM-ERP-TR-DLV) component.
You can use this BAdI to change or extend the data transferred through the service interface
InboundDeliveryCreateRequest_Out, which is part of the Transportation Order Processing process
component.
Standard settings
You can find the standard coding to fill the enterprise service interface structure in class
/SCMTMS/CL_DLVP_SEND. This might give you useful hints about how to access the data
related to the delivery proposal and how to fill the fields of the enterprise service interface
structure.
Activities
______________________________________________________________
SAP AG 131
SAP System
______________________________________________________________
6.1.9.7.2.5.2.3 BAdI for OutboundDeliveryBulkCreateRequest_Out
Use
OutboundDeliveryBulkCreateRequest_Out, which is part of the Transportation Order Processing
process component.
Standard settings
related to the delivery proposals and how to fill the fields of the enterprise service interface
structure.
Activities
6.1.9.7.2.5.3 Outbound Delivery Confirmation
Use
spot /SCMTMS/CPX_SE_SPOT_ODLV.
______________________________________________________________
SAP AG 132
SAP System
______________________________________________________________
6.1.9.7.2.5.3.2 BAdI for OutboundDeliveryBulkConfirmation_In
Use
OutboundDeliveryBulkConfirmation_In, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
6.1.9.7.2.5.4 Inbound Delivery Confirmation
Use
spot /SCMTMS/CPX_SE_SPOT_IDLV1.
______________________________________________________________
SAP AG 133
SAP System
______________________________________________________________
6.1.9.7.2.5.4.2 BAdI for InboundDeliveryConfirmation_In_V1
Use
InboundDeliveryConfirmation_In_V1, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
Use
______________________________________________________________
SAP AG 134
SAP System
______________________________________________________________
6.1.9.7.2.5.5.2 Outbound Shipment Integration
6.1.9.7.2.5.5.2.1 BAdI for TransportationOrderSCMExecutionRequest_Out
Use
TransportationOrderSCMExecutionRequest_Out, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.5.5.2.2 BAdI for

TransportationOrderSCMExecutionCancellationReq_Out
Use
TransportationOrderSCMExecutionCancellationRequest_Out, which is part of the Transportation
Standard settings
______________________________________________________________
SAP AG 135
SAP System
______________________________________________________________
Activities
6.1.9.7.2.5.5.2.3 BAdI for TransportationOrderSCMExecutionConfirmation_In
Use
TransportationOrderSCMExecutionConfirmation_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.5.5.3 Inbound Shipment Integration
6.1.9.7.2.5.5.3.1 BAdI for TransportationOrderSCMRequest_In
Use
TransportationOrderSCMRequest_In, which is part of the Transportation Order Processing
______________________________________________________________
SAP AG 136
SAP System
______________________________________________________________
process component.
Standard settings
Activities
6.1.9.7.2.5.5.3.2 BAdI for TransportationOrderSCMCancellationRequest_In
Use
TransportationOrderSCMCancellationRequest_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.5.5.3.3 BAdI for TranspOrderSCMTenderingResultNotification_Out
Use
______________________________________________________________
SAP AG 137
SAP System
______________________________________________________________
TransportationOrderSCMTenderingResultNotification_Out, which is part of the Transportation
Standard settings
Activities
6.1.9.7.3 Other Web Services
6.1.9.7.3.1 Generation of a URI to Display a Transportation Document
Use
spot /SCMTMS/TDO_SE_SPOT_URI.
6.1.9.7.3.1.2 BAdI for GetTransportationDocumentURI
Use
This Business Add-in (BAdI) is used in the Transportation Charge Calculation (TM-TCC)
component. You can use this BAdI to change or extend the data transferred through the service
interface GetTransportationDocumentURI.
______________________________________________________________
SAP AG 138
SAP System
______________________________________________________________
With this BAdI, you can change the URI (uniform resource identifier) that is generated to
display a transportation document in an independent browser window. This display might be
triggered from an application outside of SAP Transportation Management (SAP TM).
Standard settings
Activities
______________________________________________________________
SAP AG 139
Transportation Management
______________________________________________________________
Copyright
Copyright(c) 2012 SAP AG. All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form
or by any means or translated into another language, without the prior consent of
SAP AG. The information contained in this document is subject to change without
notice.
SAP is a registered trademark of SAP AG.
All other products which are mentioned in this documentation are registered or not
registered trademarks of their respective companies.
Release Notes Table of Contents SAP AG
______________________________________________________________
6.1 Transportation Management 1

6.1.1 Master Data 1
6.1.1.1 General Settings 2
6.1.1.1.1 Define Equipment Groups and Equipment Types 3
6.1.1.1.2 Define Number Range Intervals for One-time Locations 4
6.1.1.2 Organizational Management 5
6.1.1.2.1 Organizational Model 5
6.1.1.2.1.1 Create Organizational Model 5
6.1.1.2.1.2 Change Organizational Model 5
6.1.1.2.1.3 Create and Merge Organizational Hierarchy 6
6.1.1.3 Transportation Network 6
6.1.1.3.1 Location 6
6.1.1.3.1.1 Activate Change Documents 6
6.1.1.3.1.2 Configuration for Alternative Location Identifiers 7
6.1.1.3.2 Transportation Lane 8
6.1.1.3.2.2 Define Transportation Mode 9
6.1.1.3.3 General Settings for Transportation Network Determination 9
6.1.1.4 Resources 11
6.1.1.4.1 Define Means of Transport 11
6.1.1.4.2 Define Compartment Type 12
6.1.1.4.3 Define Means-of-Transport Combination 12
6.1.1.4.4 Define Attributes of MTr Combination/Compartment 13
6.1.1.4.5 Define Coupling/Uncoupling Duration 13
6.1.1.4.6 Maintain Registration Number Patterns 13
6.1.1.4.7 Specify Resource Template Types 14
6.1.1.4.8 Specify Categories of Alternative Names 14
6.1.1.4.9 Maintain Settings for Qualifications 15
6.1.1.4.10 Maintain Settings for Grouping Attributes 15
6.1.1.4.11 Maintain Settings for Attached Equipment 16
6.1.1.4.12 Maintain Settings for Aggregated Capacity Requirements 16
6.1.1.4.13 Specify Capacity Variants 17
6.1.1.4.14 Assign Standard Equipment Type 17
6.1.1.5 Agreements 18
6.1.1.5.1 Define Freight Agreement Types 18
6.1.1.5.2 Define Forwarding Agreement Types 18
6.1.1.5.3 Define Deactivation Reasons 19
6.1.1.5.4 Define Number Range Intervals for Agreements 19
6.1.2 Basic Functions 20
6.1.2.1 User Interface 20
6.1.2.1.1 Define Message Settings 20
6.1.2.2 Create Active Version and Model 20
______________________________________________________________
SAP AG iii
______________________________________________________________
6.1.2.3 Define General Settings for SAP TM 21

6.1.2.4 Define SLD Data of Business Systems 21
6.1.2.5 Charge Calculation 22
6.1.2.5.1 Basic Settings for Charge Calculation 22
6.1.2.5.1.1 Define General Settings 22
6.1.2.5.1.2 Define Rate Templates 23
6.1.2.5.1.3 Define Scale Templates 23
6.1.2.5.1.4 Define Calculation Sheet Templates 24
6.1.2.5.1.5 Define Charge Category Codes 25
6.1.2.5.1.6 Define Charge Subcategory Codes 25
6.1.2.5.1.7 Define Charge Type Codes 26
6.1.2.5.1.8 Define Charge Calculation Related Number Ranges 26
6.1.2.5.1.9 Define Number Range Intervals for Scales 27
6.1.2.5.1.10 Define Number Range Intervals for Rates 27
6.1.2.5.1.11 Define Number Range Intervals for Calculation Sheets 28
6.1.2.5.2 Data Source Binding for Charge Calculation 28
6.1.2.5.2.1 Define Scale Bases 29
6.1.2.5.2.2 Define Calculation Bases 29
6.1.2.5.2.3 Define Dimensional Weight Profile 30
6.1.2.5.3 Rules and Conditions for Charge Calculation 31
6.1.2.5.3.1 Define Rounding Rules 31
6.1.2.5.4 Enhancements of Charge Calculation Engine 32
6.1.2.5.4.1 Define Calculation Methods 32
6.1.2.6 Dangerous Goods 32
6.1.2.6.1 Define Common Settings for Dangerous Goods Processing 32
6.1.2.6.2 Define Dangerous Goods Profile 33
6.1.2.7 Type Codes and Role Codes 33
6.1.2.7.1 Master-Data-Related Type Codes and Role Codes 33
6.1.2.7.1.1 Define Party Roles 33
6.1.2.7.1.2 Define Package Type Codes 34
6.1.2.7.1.3 Define Transportation Goods Identifier Type Codes 34
6.1.2.7.2 General Type Codes and Role Codes 34
6.1.2.7.2.1 Define Business Transaction Document Type Codes 34
6.1.2.7.2.2 Define Business Transaction Document Item Type Codes 35
6.1.2.7.2.3 Define Block Reason Codes 35
6.1.2.8 Text Collection 35
6.1.2.8.1 Define Settings for Text Collection 35
6.1.2.9 Conditions 36
6.1.2.9.1 Data Access Definition 36
6.1.2.9.2 Define Text for Data Access Definition 36
6.1.2.9.3 Define Condition Types 36
______________________________________________________________
SAP AG iv
______________________________________________________________
6.1.2.9.4 Assign Condition Type to Data Access Definition 37

6.1.2.10 Geographical Map 37
6.1.2.10.1 Define Settings for Geographical Map 37
6.1.2.11 Printing 37
6.1.2.11.1 Assign Text Types to Print Document Text Fields 37
6.1.3 Forwarding Order Management 38
6.1.3.1 Define Number Range Intervals for Forwarding Order
Management 38
6.1.3.2 Forwarding Order 39
6.1.3.2.1 Define Forwarding Order Types 39
6.1.3.3 Forwarding Quotation 40
6.1.3.3.1 Define Forwarding Quotation Types 40
6.1.4 Freight Order Management 40
6.1.4.1 Define Number Range Intervals for Freight Order Management 40
6.1.4.2 Freight Order 41
6.1.4.2.1 Define Freight Order Types 41
6.1.4.3 Tendering 42
6.1.4.3.1 Define Settings for Tendering by E-mail 42
6.1.4.3.2 Define General Settings for Tendering 43
6.1.4.4 Freight Booking 45
6.1.4.4.1 Define Freight Booking Types 45
6.1.5 Planning 45
6.1.5.1.1 Define Profiles and Settings 45
6.1.5.1.2 Configure Process Controller for Planning 46
6.1.5.1.3 Define Transportation Allocation Settings 46
6.1.5.1.4 Define Customer-Specific Functions for Planning 47
6.1.5.1.5 Define Scheduling Constraints 47
6.1.5.2 Freight Unit 48
6.1.5.2.1 Define Freight Unit Types 48
6.1.6 Settlement 48
6.1.6.1 Configure Process Controller for Settlement 48
6.1.6.2 Define Settlement Profile 49
6.1.6.3 Forwarding Settlement 50
6.1.6.3.1 Define Forwarding Settlement Document Types 50
6.1.6.3.2 Define Number Range Intervals for Forwarding SDs 51
6.1.6.4 Freight Settlement 51
6.1.6.4.1 Define Freight Settlement Document Types 51
6.1.6.4.2 Define Number Range Intervals for Freight SDs 52
6.1.7 Global Trade 52
6.1.7.1 Define Customs Profile 52
6.1.7.2 Define Customs Relevance Check 53
______________________________________________________________
SAP AG v
______________________________________________________________
6.1.8 Integration 53
6.1.8.1 ERP Logistics Integration 53
6.1.8.1.1 Order-Based Transportation Requirement 53
6.1.8.1.1.1 Define Order-Based Transportation Requirement Types 54
6.1.8.1.1.2 Assign ERP Text Types to TM Text Types for OTR 54
6.1.8.1.2 Delivery-Based Transportation Requirement 55
6.1.8.1.2.1 Define Delivery-Based Transportation Requirement Types 55
6.1.8.1.2.2 Assign ERP Text Types to TM Text Types for DTR 55
6.1.8.1.3 Order Scheduling 56
6.1.8.1.3.1 Make Settings for Sales Order Scheduling 56
6.1.8.2 Integration to SAP NetWeaver Business Warehouse 56
6.1.8.2.1 Specify Settings for BW Relevance and Data Transfer 56
6.1.8.3 Tracking and Tracing of Processes and Documents 57
6.1.8.3.1 Prerequisites for Tracking and Tracing 57
6.1.8.3.2 Define Transportation Activities for Tracking and Tracing 58
6.1.9 Business Add-Ins (BAdIs) for Transportation Management 59
6.1.9.1 Master Data 59
6.1.9.1.1 General Settings 59
6.1.9.1.1.1 One-Time Locations 59
6.1.9.1.1.1.1 Notes on Implementation 59
Locations 59
Address Data 60
6.1.9.1.1.2 Equipment Types and Equipment Groups 61
6.1.9.1.1.2.2 BAdI: Consistency Check for Equipment Types 62
6.1.9.1.2 Organizational Management 63
6.1.9.1.2.1 Enhancement of SAP NetWeaver Identity Management Integration
63
Integration 63
6.1.9.1.2.2 Organizational Unit Integration 64
6.1.9.1.2.2.2 BAdI: Creation of Organizational Units 64
6.1.9.1.3 Transportation Network 65
6.1.9.1.3.1 Location 65
Identifiers 65
6.1.9.1.3.1.1.1 Notes on Implementation 65
6.1.9.1.3.1.1.2 BAdI: Validation of Alternative Location Identifiers 66
______________________________________________________________
SAP AG vi
______________________________________________________________
6.1.9.1.3.2 Reuse Component 66

6.1.9.1.3.2.1 Enhancement of Distance and Duration Determination 66
6.1.9.1.3.2.1.2 BAdI: RC LDDD - Distance and Duration Determination 66
6.1.9.1.3.2.2 Enhancement of Basic Distance and Duration Determination 68
68
6.1.9.1.4 Resources 69
6.1.9.1.4.1 Enhancement of Check for Registration Numbers 69
6.1.9.1.4.1.2 BAdI: Extend Check for Registration Numbers of Resources 69
6.1.9.1.5 Agreements 70
Determination 70
6.1.9.1.5.2 BAdI: Agreement and Calculation Sheet Filter 71
6.1.9.1.5.3 BAdI: Condition for Agreement Determination 71
6.1.9.2 Basic Functions 72
6.1.9.2.1 Charge Calculation 72
6.1.9.2.1.1 BAdI: Profitability Calculation 72
6.1.9.2.1.2 BAdI: Calculation Sheet Resolution 73
6.1.9.2.1.3 BAdI: Calculation Sheet Process 74
6.1.9.2.1.4 BAdI: Charge Calculation Data Access for Business Objects 74
6.1.9.2.1.5 BAdI: Charge Calculation Rules 75
6.1.9.2.1.6 BAdI: Charge Calculation Engine 76
6.1.9.2.2 Dangerous Goods 77
6.1.9.2.2.1 Notes on Implementation 77
6.1.9.2.2.2 BAdI: Definition of Data for Printing and Checking for
Dangerous Goods 78
6.1.9.2.3 Type Codes and Role Codes 79
6.1.9.2.3.2 BAdI: Quantity Type Code Determination 79
6.1.9.2.4 Change Controller 80
6.1.9.2.4.2 BAdI: Determination of Changes for Change Controller 80
6.1.9.2.5 Business Warehouse 81
6.1.9.2.5.2 BAdI: Condition for Extraction 81
6.1.9.2.5.3 BAdI: Fill Extraction Structures 83
6.1.9.2.6 Geographical Map 83
6.1.9.2.6.1 Enhancement to Adapt Displayed Objects 83
6.1.9.2.6.1.2 BAdI: Enhancement to Adapt Displayed Objects 84
______________________________________________________________
SAP AG vii
______________________________________________________________
6.1.9.2.7 Authorizations 85
6.1.9.2.7.1 Authorization Check 85
6.1.9.2.7.1.2 BAdI: Authorization Check 85
6.1.9.2.7.2 Output Management 86
6.1.9.2.7.2.2 BAdI: Register Additional BOs for TM Authorization Check 87
6.1.9.2.7.3 Data Retrieval Before Authorization Check 87
6.1.9.2.7.3.2 BAdI: Data Retrieval Before Authorization Check 88
6.1.9.2.8 Query Extensions 88
6.1.9.2.8.2 BAdI: Query Extensions 89
6.1.9.3 Forwarding Order Management 90
6.1.9.3.1 Approval Workflow 90
Management 90
6.1.9.3.2 Registry Extensions 91
6.1.9.3.2.2 BAdI: Extensions of Field Registry 91
6.1.9.4 Freight Order Management 92
6.1.9.4.1 Tendering 92
6.1.9.4.1.2 BAdI: Creation of Proposals for Tendering Plan 92
6.1.9.4.1.3 BAdI: Evaluation of Quotations 93
Tendering 94
6.1.9.4.1.5 BAdI: Preselection of Freight Requests for Quotation 95
6.1.9.4.1.6 BAdI: Filling of Result Structure for Forwarding and Freight
RFQs 96
6.1.9.4.1.7 BAdI: Filling of Result Structure for Tendering Query 97
6.1.9.4.1.8 BAdI: Sending of Tendering E-Mails 99
6.1.9.4.1.9 BAdI: Triggering of Alerts 100
6.1.9.4.1.10 BAdI: Update of Freight Order (FO) After Successful
Tendering 101
Assigned Carrier 102
6.1.9.5 Planning 103
6.1.9.5.1 BAdI: Determination of Subcontracting-Relevant Quantity 103
6.1.9.5.2 BAdI: Calculation of TAL Relevant Quantity 104
______________________________________________________________
SAP AG viii
______________________________________________________________
6.1.9.5.3 Additional Dimensions 105

6.1.9.5.3.2 BAdI: Additional Dimensions 105
6.1.9.5.4 VSR Optimizer 106
6.1.9.5.4.1 VSR Optimizer Preprocessing and Postprocessing 106
6.1.9.5.4.1.2 BAdI: VSR Optimizer Preprocessing 106
6.1.9.5.4.1.3 BAdI: VSR Optimizer Postprocessing 107
6.1.9.5.4.2 Explanation Tool: Customer Function 107
6.1.9.5.4.2.2 BAdI: Customer Function for Explanation Tool 108
6.1.9.6 Global Trade 109
6.1.9.6.1 Notes on Implementation 109
6.1.9.6.2 BAdI: Change Result of Customs Relevance Check 109
6.1.9.7 Integration 110
6.1.9.7.1 Tracking and Tracing of Processes and Documents 110
6.1.9.7.1.1 BAdI: Providing Execution Data for Transportation Activities 110
6.1.9.7.2 Enterprise Services 111
6.1.9.7.2.1 Forwarding Order Management 111
6.1.9.7.2.1.1 Transportation Request 111
6.1.9.7.2.1.1.2 BAdI for TransportationRequestRequest_In 111
6.1.9.7.2.1.1.3 BAdI for TransportationRequestCancellationRequest_In 112
6.1.9.7.2.1.1.4 BAdI for TransportationRequestConfirmation_Out 112
6.1.9.7.2.2 Freight Order Management 113
6.1.9.7.2.2.1 Transportation Order 113
6.1.9.7.2.2.1.2 BAdI for TransportationOrderRequest_Out 113
6.1.9.7.2.2.1.3 BAdI for TransportationOrderCancellationRequest_Out 114
6.1.9.7.2.2.1.4 BAdI for TransportationOrderConfirmation_In 114
6.1.9.7.2.2.2 Tendering 115
6.1.9.7.2.2.2.1 Transportation Request 115
6.1.9.7.2.2.2.1.1 Notes on Implementation 115
115
116
116
6.1.9.7.2.2.2.2 Transportation Order 117
6.1.9.7.2.2.2.2.2 BAdI for TransportationOrderQuotationCreateRequest_Out 117
______________________________________________________________
SAP AG ix
______________________________________________________________
6.1.9.7.2.2.2.2.3 BAdI for TransportationOrderQuotationCancellationRequest_Out

118
6.1.9.7.2.2.2.2.4 BAdI for TransportationOrderQuotationConfirmation_In 119
6.1.9.7.2.2.3 Booking 119
6.1.9.7.2.2.3.1.2 BAdI for TransportationOrderBookingRequest_Out 120
6.1.9.7.2.2.3.1.3 BAdI for TransportationOrderBookingCancellationRequest_Out
120
6.1.9.7.2.2.3.1.4 BAdI for TransportationOrderBookingConfirmation_In 121
121
6.1.9.7.2.3 Global Trade 122
6.1.9.7.2.3.1 Request for Export Declaration 122
6.1.9.7.2.3.1.2 BAdI for ExportDeclarationSUITERequest_Out 122
6.1.9.7.2.3.2 Cancellation Request for Export Declaration 123
6.1.9.7.2.3.2.2 BAdI for ExportDeclarationSUITECancellationRequest_Out 123
6.1.9.7.2.3.3 Confirmation of Export Declaration 124
6.1.9.7.2.3.3.2 BAdI for ExportDeclarationSUITEConfirmation_In 124
6.1.9.7.2.4 Settlement 125
6.1.9.7.2.4.1 Forwarding Settlement 125
125
125
126
6.1.9.7.2.4.2 Freight Settlement 127
127
127
128
6.1.9.7.2.5 ERP Logistics Integration 129
6.1.9.7.2.5.1.2 BAdI for IntracompanyTransportationRequestRequest_In 129
______________________________________________________________
SAP AG x
______________________________________________________________

129
6.1.9.7.2.5.1.4 BAdI for
IntracompanyTranspRequestSimulateReqConfirmation_In 130
6.1.9.7.2.5.2 Outbound Processing of Delivery Proposals 131
6.1.9.7.2.5.2.2 BAdI for InboundDeliveryCreateRequest_Out 131
6.1.9.7.2.5.2.3 BAdI for OutboundDeliveryBulkCreateRequest_Out 132
6.1.9.7.2.5.3 Outbound Delivery Confirmation 132
6.1.9.7.2.5.3.2 BAdI for OutboundDeliveryBulkConfirmation_In 133
6.1.9.7.2.5.4 Inbound Delivery Confirmation 133
6.1.9.7.2.5.4.2 BAdI for InboundDeliveryConfirmation_In_V1 134
6.1.9.7.2.5.5.2 Outbound Shipment Integration 134
6.1.9.7.2.5.5.2.1 BAdI for TransportationOrderSCMExecutionRequest_Out 134
6.1.9.7.2.5.5.2.2 BAdI for
TransportationOrderSCMExecutionCancellationReq_Out 135
136
6.1.9.7.2.5.5.3 Inbound Shipment Integration 136
6.1.9.7.2.5.5.3.1 BAdI for TransportationOrderSCMRequest_In 136
6.1.9.7.2.5.5.3.2 BAdI for TransportationOrderSCMCancellationRequest_In 137
6.1.9.7.2.5.5.3.3 BAdI for TranspOrderSCMTenderingResultNotification_Out 137
6.1.9.7.3 Other Web Services 138
6.1.9.7.3.1 Generation of a URI to Display a Transportation Document 138
6.1.9.7.3.1.2 BAdI for GetTransportationDocumentURI 138
______________________________________________________________
SAP AG xi
SAP System
______________________________________________________________
6 SAP Transportation Management
6.1 Transportation Management
______________________________________________________________
SAP AG 1
SAP System
______________________________________________________________
6.1.1 Master Data
______________________________________________________________
SAP AG 2
SAP System
______________________________________________________________
______________________________________________________________
SAP AG 3
SAP System
______________________________________________________________
6.1.1.1.1 Define Equipment Groups and Equipment Types
Use
In this IMG activity, you can define equipment groups and equipment types.
You can use equipment types in the following areas:
- in the definition of the carrier profile to describe the kind of equipment that is owned by
the carrier
- In the definition of forwarding order or forwarding quotation items of the type Container
After you have entered the equipment group, the equipment type, and the number of
containers (pieces) on the forwarding order user interface, the system calculates the tare
weight and capacity in TEU based on the data you have defined in this Customizing
activity.
- in the definition of freight unit building rules
In this case, the system uses the physical properties of the equipment type and group that
you define in this Customizing activity instead of the planning-relevant quantities.
You can use equipment groups to group equipment types into categories.
Requirements
You have activated business function Foundation for External Transportation Management System
(SCM_SCMB_TM_FND1).
Standard settings
We deliver the CN equipment group with 32 default container types.
Activities
Define equipment groups and assign equipment types to them.
Example
You want to classify the containers that your company owns. You define an equipment group
CN for containers. There are, for example, 10-foot and 20-foot containers. For the equipment
group CN you define the equipment types 22G0 and 22R1 with physical properties, capacities,
and temperature settings for your containers.
______________________________________________________________
SAP AG 4
SAP System
______________________________________________________________
6.1.1.1.2 Define Number Range Intervals for One-time Locations
Use
In this IMG activity, you can define the number range intervals for one-time locations.
The system uses number range intervals of the type "internal" to automatically assign a number
of the number range interval to one-time locations. Therefore, you must define at least one
number range interval of the type "internal".
The system does not make explicit use of number range intervals of the type "external" in this
context. However, for documentation purposes, it may make sense to define such intervals to
make clear that these numbers are reserved for manually created locations or for locations that
have been transferred to SAP Transportation Management (SAP TM) via the Core Interface
(CIF). Therefore, the definition of number range intervals of the type "external" is optional.
Activities
- You must define a number range interval of the type "internal".

This number range interval must only contain numeric strings.
- You can define one or more number range intervals of the type "external".
This number range interval can contain alphanumeric strings.
Note: You must ensure that the individual number range intervals do not overlap.
Example
Possible definitions of number range intervals can be:

No From Number To Number Current No. Ext
01 00000000000000000000 00000000009999999999 0 (automatically assigned) not
set (internal)
02 A0000000000000000000 ZZZZZZZZZZZZZZZZZZZZ 0 (automatically assigned)
set (external)
Note
In the standard system, all roles have been configured so that users assigned to them can read
the details of locations as well as one-time locations. If this does not meet your requirements,
you can reconfigure the roles.
If you reconfigure the roles, you should ensure that all roles are configured so that users
assigned to them can at least display the details of one-time locations.
For example, if you want to define a role that is used to display all locations starting with the
characters A through to K and you have defined the number range interval for one-time
locations as shown in the example above, you should configure the APO Authorization
______________________________________________________________
SAP AG 5
SAP System
______________________________________________________________
Object: Master Data, Locations (C_APO_LOC) authorization object as follows:

- Under Activity select at least the Display indicator
- Under Location enter the intervals for the locations that can be displayed for this role.
For example, enter the following:
From To
00000000000000000000 00000000009999999999
A K
6.1.1.2 Organizational Management
6.1.1.2.1 Organizational Model
6.1.1.2.1.1 Create Organizational Model
Use
In this IMG activity, you can create the organizational model of your organization. The
organizational model is based on individual organizational units, which can be defined in detail
in this IMG activity.
On the Description tab you can specify the organizational unit function and role to define the
organizational unit in more detail. For example, you can specify Sales as the organizational unit
function and Organization as the organizational unit role. The organizational unit that you
created in this case is a sales organization.
Activities
- You define the validity period for the organizational unit.

- You create the organizational unit.
- You specify the organizational unit function and role.
- You create other organizational units and assign them to your organizational unit.
- You create jobs and positions to which you assign staff to.
- You assign staff to organizational units.
______________________________________________________________
SAP AG 6
SAP System
______________________________________________________________
6.1.1.2.1.2 Change Organizational Model
Use
In this IMG activity, you can change the organizational model of your organization.
Requirements
In the IMG activity Create Organizational Model, you have created an organizational model.
Example
Examples of possible changes are:

- Changes to the organizational unit function and roles
- Changes to the organizational structure
- Changes to staffing assigned to organizational units
6.1.1.2.1.3 Create and Merge Organizational Hierarchy
Use
In this Customizing activity, you can upload definitions of organizational hierarchies from SAP
ERP or SAP Supply Chain Management (SAP SCM) systems into SAP Transportation
Management (SAP TM). For more information, see the Create and Merge Organizational
Hierarchy from SAP ERP or SAP SCM.
6.1.1.3 Transportation Network
6.1.1.3.1 Location
______________________________________________________________
SAP AG 7
SAP System
______________________________________________________________
Use
In this IMG activity, you activate change documents for locations.

performance.
Standard settings
locations.
6.1.1.3.1.2 Configuration for Alternative Location Identifiers
Use
______________________________________________________________
SAP AG 8
SAP System
______________________________________________________________
Requirements
Activities
Specific ALI Types.
6.1.1.3.2 Transportation Lane
______________________________________________________________
SAP AG 9
SAP System
______________________________________________________________
Use
In this IMG activity, you activate change documents for transportation lanes.
performance.
Standard settings
6.1.1.3.2.2 Define Transportation Mode
Use
In this Customizing activity, you can define transportation modes.
Example
Transportation modes can be road, rail, air, or sea.
6.1.1.3.3 General Settings for Transportation Network Determination
Use
In this IMG activity, you can do the following settings:

- Transportation lane determination
Here you define what hierarchy the lane determination prioritizes when searching for
______________________________________________________________
SAP AG 10
SAP System
______________________________________________________________
You can set the Consider Hierarchical Relationships Between MTrs First indicator to
control that the lane determination considers the means of transport hierarchy first before
considering the hierarchies of the source and destination locations or zones.
In addition, you can control the order in which the lane determination considers the source
and destination locations or zones by setting the Consider Source Hierarchy First indicator.
- Transshipment location determination
If you set the Consider Directly Connected Transshipment Locations Only indicator, the
system only takes into account direct connections between transshipment locations during
transportation network determination. This indicator does not influence the assignment of
source locations and destination locations to transshipment locations. The system assigns
source locations and destination locations to transshipment locations via transportation zones
taking into account indirectly connected transshipment Locations.
Requirements
You have defined the following objects for the transportation lane determination:
- Hierarchies for:
- the means of transport
- the source locations or zones
- the destination locations or zones
Standard settings
In the standard system, the Consider Hierarchical Relationships Between MTrs First indicator is
set.
Example
The following examples show how the two indicators for the transportation lane determination
relate to each other:
If you set the Consider Hierarchical Relationships Between MTrs First indicator and do not set
the Consider Source Hierarchy First indicator, the lane determination considers the objects and
hierarchies in the following order:
You can choose this setting, for example, if the transportation lane leaving the warehouse is
more important than the customer. The means of transport has the lowest priority.
If you set the Consider Source Hierarchy First indicator and do not set the Consider
Hierarchical Relationships Between MTrs First indicator, the lane determination considers the
objects and hierarchies in the following order:
______________________________________________________________
SAP AG 11
SAP System
______________________________________________________________

transport has the highest priority and the customer as destination location is more important than
the warehouse.
If you set both indicators, the lane determination considers the following objects and hierarchies
in the order they are presented:
You can choose this setting, for example, if a transportation lane to a certain customer is more
important than the transportation lane to your specific warehouse from which you deliver the
goods. The means of transport has the lowest priority.
If you do not set any indicator, the lane determination considers the following objects and
hierarchies in the order they are presented:
transport has the highest priority and a specific warehouse as source location is more important
than the customer.
6.1.1.4 Resources
6.1.1.4.1 Define Means of Transport
Use
In this IMG activity, you define means of transport.
______________________________________________________________
SAP AG 12
SAP System
______________________________________________________________
Example
- Airplane
- Train
- EuroTrucking
- ABC shipping
Use
Activities
levels.
Use
Requirements
______________________________________________________________
SAP AG 13
SAP System
______________________________________________________________
Use
compartments.
Use
6.1.1.4.6 Maintain Registration Number Patterns
Use
In this IMG activity, you specify registration numbers patterns for resources.
Registration number patterns represent naming conventions for registration numbers.
______________________________________________________________
SAP AG 14
SAP System
______________________________________________________________
Standard settings
No registration number patterns are delivered.
Activities
1. Choose the resource type.

The registration number pattern is valid for resources of these types.
2. Choose the country key of the registration number.
The registration number pattern is valid for resources having these registration number
country keys.
3. Choose the means of transport.
The registration number pattern is valid for resources having these means of transport.
4. Enter the registration number pattern.
When entering new registration numbers for resources in the resource master, the system checks
for correctness of the numbers.
Note
If you do not specify registration number patterns, the system does not check for correctness of
registration numbers when it enters them in the resource master.
6.1.1.4.7 Specify Resource Template Types
Use
In this IMG activity, you specify a resource template type for handling resources.
You use resource template types to mark a handling resource as a handling resource template.
You can use this template for new handling resources.
______________________________________________________________
SAP AG 15
SAP System
______________________________________________________________
6.1.1.4.8 Specify Categories of Alternative Names
Use
In this IMG activity, you specify categories for alternative names of resources.
You have to specify alternative name categories before you can specify alternative names in the
resource master.
6.1.1.4.9 Maintain Settings for Qualifications
Use
In this IMG acitivity, you can specify qualifications.

Note
The system does not check the consistency of required or offered qualifications. If you want to
check the consistency, use the incompatibility framework of SAP Transportation Management
(SAP TM).
Example
You have maintained the qualification type Driving License with qualification A (Heavy
Vehicle).
- If you assign qualification A of category Driving License to a vehicle resource, this
means that this resource can only be operated with such a driving license.
- If you assign qualification A of category Driving License to a driver, this means that this
employee is allowed to operate heavy vehicles.
6.1.1.4.10 Maintain Settings for Grouping Attributes
Use
In this IMG activity, you can specify grouping attribute categories and grouping attributes for
resources.
______________________________________________________________
SAP AG 16
SAP System
______________________________________________________________
After you have specified grouping attributes and grouping attribute categories, you can assign
resources in the resources master to them.
Activities
1. Specify grouping attribute categories.

2. Specify grouping attributes for grouping attribute categories.
Example
You have specified the following:

- Grouping attribute category Truck with the grouping attributes A, B, and C
- Grouping attribute category Container with the grouping attributes C, CC, and CCC
Now you can group resources into trucks and containers. The attributes can be used for
resource selection.
6.1.1.4.11 Maintain Settings for Attached Equipment
Use
In this IMG activity, you specify categories of attached equipment.

You must specify categories of attached equipment before you can assign attached equipment to
these categories in the resource master.
6.1.1.4.12 Maintain Settings for Aggregated Capacity Requirements
Use
In this IMG activity, you specify that the system should write capacity requirements for
handling resources to the database during planning.
When you create a planned transportation activity that is linked to a handling resource, the
system aggregates the new capacity requirements of this planned transportation activity directly
on the database for the involved handling resource. This leads to a better capacity check
performance.
______________________________________________________________
SAP AG 17
SAP System
______________________________________________________________
Activities
1. Enter the name of a handling resource.

2. Set the Use DB indicator.
Use
Activities

6.1.1.4.14 Assign Standard Equipment Type
Use
In this IMG activity, you specify the standard equipment type for a combination of equipment
group and equipment type.
You can use this combination to identify a transportation unit (TU) resource as a container or
as non-container equipment. This is necessary, for example, for printing or planning.
You can assign a means of transport or packaging material to this combination. The system
automatically includes these values in the TU resource information in the resource master when
it enters the combination of equipment group and equipment type there. Thus you can ensure
that TU resources are assigned to the correct means of transport and packaging materials. The
______________________________________________________________
SAP AG 18
SAP System
______________________________________________________________
system does not overwrite means of transport or packaging materials that you have already
specified.
6.1.1.5 Agreements
6.1.1.5.1 Define Freight Agreement Types
Use

- Define a freight agreement (FA) type
- Define the number range generating the ID for newly created FAs
- Specify the retention time for archiving
6.1.1.5.2 Define Forwarding Agreement Types
Use

- Define a forwarding agreement (FWA) type
- Define the number range generating the ID for newly created FWAs
- Maintain a short description for the FWA type
______________________________________________________________
SAP AG 19
SAP System
______________________________________________________________
6.1.1.5.3 Define Deactivation Reasons
Use
In this Customizing activity, you can define the reasons why an agreement is deactivated.
6.1.1.5.4 Define Number Range Intervals for Agreements
Use
In this Customizing activity, you define number range intervals for agreements.
Activities

Note
______________________________________________________________
SAP AG 20
SAP System
______________________________________________________________
6.1.2 Basic Functions
6.1.2.1 User Interface
6.1.2.1.1 Define Message Settings
Use
In this Customizing activity, you define the following message settings for a message type and
either a user or a role:
- Filtering by severity
- Filtering by detail level
- Filtering by problem class
- Maximum number of messages for application log
Requirements
- For user-specific message settings, the user must exist in the system.
- For role-specific message settings, the role must exist in the system.
Activities
1. Specify either a user or a role and a message type.

If you do not specify a user or a role, the system applies the message settings to all
users.
The system considers user-specific and role-specific message settings in the following way:
- User-specific message settings overrule role-specific message settings. Therefore, it
does not make sense to specify both a user and a role.
- If you specify different message settings for a role, the system considers the settings
with the highest granularity of information.
For example, you have specified the following settings: one with a detail level of 2
and another with a detail level of 7. In this case, the system applies the message
settings with the detail level of 7.
2. Make the message settings specified above.
______________________________________________________________
SAP AG 21
SAP System
______________________________________________________________
6.1.2.2 Create Active Version and Model
Use
In this IMG activity, you create an active version and a model.

In SAP Transportation Management (TM) you must assign specific master data objects to an
active version and a model for transportation planning purposes. You must assign the following
objects:
- Locations
The system creates the active version and the model exactly once.
Note
The active version and the model do not need to be and cannot be created more than once.
The system displays an error message if an active version and a model exist and you try to
create a new one.
Activities
Execute the IMG activity.
6.1.2.3 Define General Settings for SAP TM
Use
In this IMG activity, you can define general settings for SAP TM.
______________________________________________________________
SAP AG 22
SAP System
______________________________________________________________
6.1.2.4 Define SLD Data of Business Systems
Use
In this Customizing activity, you define the system landscape directory data of your business
systems.
You have to define the ERP systems (business system and logical system). Moreover, you need
to select the Manual Maint. checkbox.
6.1.2.5 Charge Calculation
6.1.2.5.1 Basic Settings for Charge Calculation
6.1.2.5.1.1 Define General Settings
Use
In this Customizing activity, you define the organizational unit settings for transportation charge
calculation. This consists of the following settings:
- Default purchasing organization and carrier
The default purchasing organization and carrier for which the rates are maintained so that a
price proposal can be determined for tendering purposes.
- Agreement determination rule
The BRFplus condition used to determine the agreement during charge calculation.
- Calculation sheet determination rule
The BRFplus condition used to determine the calculation sheet during charge calculation.
- Default settlement profile
The settlement profile to be applied for the organizational unit.
- Condition for determination of settlement profile
The BRFplus condition used to determine the settlement profile for charge calculation and
settlement purposes.
- Default dimensional weight profile
The default dimensional weight profile to be applied for the organizational unit.
- Condition for determination of dimensional weight profile
______________________________________________________________
SAP AG 23
SAP System
______________________________________________________________
The BRFplus condition used to determine the dimensional weight profile for charge
calculation and settlement purposes.
You can specify the organizational unit or enter *.
6.1.2.5.1.2 Define Rate Templates
Use
In this Customizing activity, you define rate templates to transport across different systems and
use as templates for creating rate tables.
Note that the system automatically enters the current date as the start date of validity and
12/31/9999 as the end date of validity. You can change these dates after you create a rate
table.
Activities
1. Create a rate template with the following required information:

- Rate template
- Charge type
- Charge usage
- Currency
2. Create rate template scales with the following required information:
- Dimension number (indicates the order of the input scales)
- Scale template
- Calculation base code
3. Create rate calculation base rules with the following required information (optional - used
in validity node):
- Calculation base
- Unit of measure
- Quantity
______________________________________________________________
SAP AG 24
SAP System
______________________________________________________________
6.1.2.5.1.3 Define Scale Templates
Use
In this Customizing activity, you define scale templates to transport across different systems and
use as templates for creating scales.
Activities
1. Create a scale template that includes the following information:

- Scale template
- Scale type
- Scale base
2. Create scale template items (optional)
This is relevant when the scale type is Base Scale (>=) or To Scale (<=) and the
scale items are numeric, for example, weight or distance.
Scale template items are not relevant when the scale items come from master data, for
example, location.
6.1.2.5.1.4 Define Calculation Sheet Templates
Use
In this Customizing activity, you define calculation sheet templates to transport across different
systems and use as templates for creating calculation sheets. The system validates the calculation
sheet templates after you create them.
Note
A calculation sheet template is a flat structure that the system formats into a hierarchical
structure based on the reference lines in the template. Therefore it is recommended that you
adhere to calculation sheet guidelines when creating a calculation sheet template, for example:
- Line numbers must be greater than 10 because the system generates the first sum line as
10
- The sum line must have reference lines greater than itself
- A subtotal line must have reference lines less than itself
- A subtotal line inherits the resolution base from the sum parent line
- If you require a nested sum line, decide on the reference line numbers accordingly
______________________________________________________________
SAP AG 25
SAP System
______________________________________________________________
Activities
1. Create a calculation sheet template with the following required information:

- Template name
- Charge usage
2. Create calculation sheet template items with the following required information:
- Line number (greater than 10 and in an ascending sequence)
- Rate template (only needed if you do not enter the amount)
- Charge type
- Instruction type
- Amount (only needed if you do not enter the rate template)
- Currency (use % for percentage charges)
- Calculation resolution base
- Operation code (compare the high and low values)
- Line to reference from (sum, subtotal, compare the high and low values, percentage)
- Line to reference to (sum, subtotal, compare the high and low values, percentage)
6.1.2.5.1.5 Define Charge Category Codes
Use
In this Customizing activity, you define charge category codes for charge types. You can use
the charge category codes to group and categorize charge types.
Example
A useful code list could be the UN/EDIFACT Codelist 5237.
______________________________________________________________
SAP AG 26
SAP System
______________________________________________________________
6.1.2.5.1.6 Define Charge Subcategory Codes
Use
In this Customizing activity, you define charge subcategory codes. You can use the charge
subcategory codes of charge types to group and categorize charge types in a more granular way
than charge category codes.
Example
A suitable example could be the code list resulting out of UN/EDIFACT Recommendation 23:
"FREIGHT COST CODE # FCC Harmonization of the Description of Freight Costs and Other
Charges".
6.1.2.5.1.7 Define Charge Type Codes
Use
In this Customizing activity, you can define charge type codes.

A charge type code describes a charge type. The charge type code defines if the charge item
results in a positive or negative value and if the value is an actual amount or a percentage
value. This value is used for other transportation charges.
We recommend to group and categorize charge type codes by use of charge type subcategory
codes and/or charge type category codes.
6.1.2.5.1.8 Define Charge Calculation Related Number Ranges
Use
In this Customizing activity, you define number ranges for the master data business objects that
are relevant for charge calculation.
______________________________________________________________
SAP AG 27
SAP System
______________________________________________________________
The system uses number range intervals of type internal to automatically assign a number of the
number range interval to the charge management objects. Therefore, you must define at least
one number range interval of the type Internal.
6.1.2.5.1.9 Define Number Range Intervals for Scales
Use
In this Customizing activity, you define number range intervals for scales.
Activities

Note
6.1.2.5.1.10 Define Number Range Intervals for Rates
Use
In this Customizing activity, you define number range intervals for rates.
______________________________________________________________
SAP AG 28
SAP System
______________________________________________________________
Activities

Note
6.1.2.5.1.11 Define Number Range Intervals for Calculation Sheets
Use
In this Customizing activity, you define number range intervals for calculation sheets.
Activities

Note
______________________________________________________________
SAP AG 29
SAP System
______________________________________________________________
6.1.2.5.2 Data Source Binding for Charge Calculation
6.1.2.5.2.1 Define Scale Bases
Use
In this Customizing activity, you define a scale base that forms one of the parameters on which
the cost to be calculated depends.
Activities
You define a scale base as a one-time setup activity. You maintain the scale base in tables of
delivery type S, meaning creating a new scale base is an enhancement activity.
Example
The cost of a shipment depends upon the weight of the goods and the distance traveled.
Therefore the weight and distance form the scale base. To define a scale base for weight, you
maintain it in Customizing in the following way:
Scale Base WEIGHT
Scale Base Desc. Weight
Field Assgmt (Scale Base Field Assignment) SCAVAL_WT
Usage Base for Scales
UoM Relevant X
Dimension Mass
Rounding Rule X
Numeric X
6.1.2.5.2.2 Define Calculation Bases
Use
In this Customizing activity, you define a calculation base for a scale base. The calculation base
indicates on what base the charge calculation is executed for a corresponding scale.
______________________________________________________________
SAP AG 30
SAP System
______________________________________________________________
Example
You define the calculation base SOURCELOC as Source (Ship from) Location and
DESTLOC as Destination (Ship to) Location for scale base LOC (Location) as follows:
Calc. Base SOURCELOC
Scale Base LOC
Description Source (Ship from) Location
Field Assgmt (Field Assignment) SOURCELOC_UUID (assignment to a field in the
Calc. Base DESTLOC

Scale Base LOC
Description Destination (Ship from) Location
Field Assgmt (Field Assignment) DESTLOC_UUID (assignment to a field in the
6.1.2.5.2.3 Define Dimensional Weight Profile
Use
In this Customizing activity, you calculate the dimensional weight by converting the volume to
the appropriate unit of measure and then dividing it by the dimensional weight factor. The
result is the weight in the target unit of measure. The dimensional weight is then used in the
charge calculation using the corresponding calculation base.
In general, the dimensional weight calculation depends on two input variables: the dimensional
weight factor (or ratio) and the system of used unit of measures. These variables are
country-specific and carrier-specific.
Common dimensional weight factors for metric units of measure are 5000 (cm3/kg) and 6000
(cm3/kg).
Common dimensional weight factors for imperial units of measure are 166 (in3/lb) and 194
(in3/lb).
Activities
Assign the dimensional weight profile directly to an organizational unit in the freight agreement
settings or determine the dimensional weight profile using a condition.
______________________________________________________________
SAP AG 31
SAP System
______________________________________________________________
Example
You want to configure the dimensional weight profile for imperial factor 166. You enter the
following data:
- Name I166
- Volume unit of measure in3
- Weight unit of measure lb
6.1.2.5.3 Rules and Conditions for Charge Calculation
6.1.2.5.3.1 Define Rounding Rules
Use
In this Customizing activity, you define rounding profiles. You use the rounding profile to
round the data according to its definition.
Each rounding profile points to a rounding rule at a particular index. This rounding rule
consists of the applicability of the rule that defines the value range index, the sign of range
limit included or range limit excluded, the option (for exmaple, equal to, less than, and greater
that), and low and high.
Based upon all the above mentioned factors, the value is rounded accordingly.
Activities
1. To define a rounding profile, maintain the following fields:

- Rnd. Prof. (Rounding Profile)
- Rounding Prof. Desc. (Rounding Profile Description)
2. To define the rounding rule for the above defined rounding profile, maintain the following
fields:
- Rule Index
- Rounding Profile
- Description
3. Each rounding rule in turn consists of applicability that you define with the following
attributes:
______________________________________________________________
SAP AG 32
SAP System
______________________________________________________________
- ValRngIndx (Value Range Index)

- Sign
You can select between the following: Range Limit Excluded or Range Limit
Included.
- Option
- Low Value
- High Value
Example
You define a rounding profile to round up or down to an integer of 0005, that is, it consists
of rounding rule 0005. This rounding profile, when applied to a value, rounds the value to the
nearest integer.
When rounding profile 0005 is applied to a value of 22.8, is it rounded to 23.
6.1.2.5.4 Enhancements of Charge Calculation Engine
6.1.2.5.4.1 Define Calculation Methods
Use
In this Customizing activity, you define the calculation methods used in charge calculation.
6.1.2.6 Dangerous Goods
6.1.2.6.1 Define Common Settings for Dangerous Goods Processing
Use
In this Customizing activity, you can define general settings for the dangerous goods processing
in SAP Transportation Management (TM).
______________________________________________________________
SAP AG 33
SAP System
______________________________________________________________
Standard settings
For the standard processing of dangerous goods with SAP Environment, Health and Safety
(EH&S), select the strategies DG_EHS_CHK and DG_EHS_PRT.
6.1.2.6.2 Define Dangerous Goods Profile
Use
In this Customizing activity, you define profiles for the processing of dangerous goods. The
following profiles are delivered: Only Errors Road and All Messages Road. You
define general conditions for the processing of dangerous goods, for instance what messages are
allowed to process certain dangerous goods or if you are allowed to define goods manually as
dangerous or not.
You assign the profile when defining order types for freight units or freight orders.
You can also specify default mode of transports that have to be used for the dangerous goods
check in case the information is not yet available on the business document.
Activities
You can change the profile or you can define a new one.
6.1.2.7 Type Codes and Role Codes
6.1.2.7.1 Master-Data-Related Type Codes and Role Codes
6.1.2.7.1.1 Define Party Roles
Use
In this IMG activity, you can define roles for the parties involved in the transportation process.
______________________________________________________________
SAP AG 34
SAP System
______________________________________________________________
6.1.2.7.1.2 Define Package Type Codes
Use
In this IMG activity, you define package type codes.
6.1.2.7.1.3 Define Transportation Goods Identifier Type Codes
Use
In this IMG activity, you define transportation goods identifier type codes.
6.1.2.7.2 General Type Codes and Role Codes
6.1.2.7.2.1 Define Business Transaction Document Type Codes
Use
In this IMG activity, you can define the document type codes for a business transaction.
______________________________________________________________
SAP AG 35
SAP System
______________________________________________________________
6.1.2.7.2.2 Define Business Transaction Document Item Type Codes
Use
In this IMG activity, you define business transaction document item type codes.
6.1.2.7.2.3 Define Block Reason Codes
Use
In this Customizing activity, you define block reason codes and assign them to processes. These
processes are then blocked in SAP Transportation Management (SAP TM).
You can use manual block reasons to block processes in SAP TM for many types of objects.
For example, you can block a forwarding order for planning. SAP TM also has block reasons
that are set automatically by the system. The approval workflow is an example of such a block
reason.
6.1.2.8 Text Collection
6.1.2.8.1 Define Settings for Text Collection
Use
You can use the following Customizing activity to define the settings for text collection:
Maintain Text Schema
______________________________________________________________
SAP AG 36
SAP System
______________________________________________________________
For more information, see Cross-Application Components -> Processes and Tools for Enterprise
Applications -> Reusable Objects and Functions for BOPF Environment -> Dependent Object
Text Collection -> Maintain Text Schema.
6.1.2.9 Conditions
6.1.2.9.1 Data Access Definition
Use
In this IMG activity, you define the data access definition.
6.1.2.9.2 Define Text for Data Access Definition
Use
In this IMG activity, you define text for your data access definition.
Use
______________________________________________________________
SAP AG 37
SAP System
______________________________________________________________
In this Customizing activity, you can define condition types.
6.1.2.9.4 Assign Condition Type to Data Access Definition
Use
In this IMG activity, you assign condition types to data access definitions.
6.1.2.10 Geographical Map
6.1.2.10.1 Define Settings for Geographical Map
Use
In this Customizing activity, you can activate the geographical map display and define settings
for the geographical map.
6.1.2.11 Printing
6.1.2.11.1 Assign Text Types to Print Document Text Fields
______________________________________________________________
SAP AG 38
SAP System
______________________________________________________________
Use
In this Customizing activity, you define which text types are to be printed in which text fields
in a print document. For example, you define that handling instructions for a house air waybill
are to be printed in the HAWB (House Air Waybill): Handling Instructions (HAWB_HDINS) text
field in the corresponding print document.
Requirements
You have defined text types and assigned them to text schemas.
For more information, see Customizing for Cross-Application Components under Processes
and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF
Environment -> Dependent Object Text Collection -> Maintain Text Schema.
6.1.3 Forwarding Order Management
6.1.3.1 Define Number Range Intervals for Forwarding Order Management
Use
documents:
- Forwarding Order
- Forwarding Quotation
- Order-Based Transportation Requirement
- Delivery-Based Transportation Requirement
When you create one of the above business documents, the system assigns a unique number that
Only internal number assignment is supported, therefore do not use the External Number
Range checkbox.
______________________________________________________________
SAP AG 39
SAP System
______________________________________________________________
Activities

- Alphanumeric key with up to two characters
- Boundaries of the number range interval. The individual number range intervals must
For an example, seeDefine Forwarding Order Types.
6.1.3.2 Forwarding Order
6.1.3.2.1 Define Forwarding Order Types
Use
In this Customizing activity, you specify types of forwarding orders. You can use this type to
define certain parameters of the forwarding order that influence how the system processes this
business document.
For example, the forwarding order type determines the number range interval that is used to
generate a number of the forwarding order, or it defines whether freight units are created
automatically when you save the forwarding order. Furthermore, you can assign profiles, for
example planning profile and dangerous goods profile, that determine how follow-up steps such
as planning and dangerous goods checks are performed.
user interface of the forwarding order in SAP NetWeaver Business Client. You can also specify
a default forwarding order type that is used when the forwarding order is created automatically
based on electronic data interchange (EDI).
______________________________________________________________
SAP AG 40
SAP System
______________________________________________________________
6.1.3.3 Forwarding Quotation
6.1.3.3.1 Define Forwarding Quotation Types
Use
In this Customizing activity, you specify types of forwarding quotations. You can use this type
to define certain parameters of the forwarding quotation that influence how the system processes
this business document.
For example, the forwarding quotation type determines the number range interval that is used to
generate a number of the forwarding quotation, or it defines whether an approval workflow is
activated.
user interface of the forwarding quotation in SAP NetWeaver Business Client. You can also
specify a default forwarding quotation type that is used when the forwarding quotation is created
automatically based on electronic data interchange (EDI).
6.1.4 Freight Order Management
6.1.4.1 Define Number Range Intervals for Freight Order Management
______________________________________________________________
SAP AG 41
SAP System
______________________________________________________________
Use
documents
- Freight order
- Freight unit
- Freight booking
- Transportation unit
When creating one of the above business documents, a unique number is assigned which
Only internal number assignment is supported, do not use the check box External Number
Range.
Activities

- Alphanumeric key with up to two characters.
- Boundaries of the number range interval. The individual number range intervals may
For an example, see Define Freight Order Types.
6.1.4.2 Freight Order
6.1.4.2.1 Define Freight Order Types
Use
In this Customizing activity, you can define freight order types.
______________________________________________________________
SAP AG 42
SAP System
______________________________________________________________
6.1.4.3 Tendering
6.1.4.3.1 Define Settings for Tendering by E-mail
Use
In this Customizing activity, you can select and change the settings the system uses to manage
incoming e-mails that contain freight quotations (FQs) from carriers.
General Settings View
In the General Settings view, the character you enter in the Keyword Marker field marks
the beginning of a keyword in an e-mail text.
The system stops any further parsing of an e-mail text after the first occurrence of the
character you enter in the Parser End Marker field. You can place explanatory text that you
do not want the parser to process after the parser end marker in an e-mail.
Keywords View
In the Keywords view, you can assign keywords to enable the parser to relate a piece of text
in an e-mail to a business meaning. In an e-mail text, a keyword must start with the keyword
marker that you defined in the General Settings view.
For example, you define a keyword marker of "&". You assign the keyword "RFQ" to the
"Freight Request for Quotation Number" business meaning. Your e-mail text reads as follows:
"Hello, this is a freight quotation for &RFQ 12345".
In this example, the parser extracts the "Freight Request for Quotation Number" from the
e-mail text by searching for the keyword "RFQ". This keyword is preceded by the keyword
marker "&". The "Freight Request for Quotation Number" 12345 follows the keyword "RFQ".
Keywords are not case sensitive. If you define a keyword "RFQ", carriers can write "&RFQ",
"&rfq", or "&rFq" in e-mails.
You can select Determines Application for exactly one keyword in each application. The
occurrence of this specific keyword in an e-mail text determines the application. For example, if
you select the Determines Application checkbox for the keyword "RFQ" and the application
/SCMTMS/TENDERING, the occurrence of "&RFQ" in an e-mail text tells the system the
e-mail is related to a tendering process.
Keyword Values View
In the Keyword Values view, you can define how carriers write "Yes" and "No" in an e-mail
text. You must define "Yes" and "No" values for the keyword that has the "Acceptance Code"
meaning.
______________________________________________________________
SAP AG 43
SAP System
______________________________________________________________
For example, in the Keywords view, you assign the keyword "ACCEPT" to the meaning
"Acceptance Code". In the Keyword Values view, you assign keyword value "Y" to meaning
"Yes" and keyword value "N" to meaning "No". To accept a freight request for quotation
(freight RFQ) by e-mail, a carrier writes "&ACCEPT y". To reject, a carrier writes
"&ACCEPT n".
Keywords values are not case sensitive. If you define a keyword "ACCEPT" and a keyword
value "Y", a carrier can write "&ACCEPT Y", "&accept y", or "&aCCepT Y" in e-mails.
6.1.4.3.2 Define General Settings for Tendering
Use
In this Customizing activity, you can specify the standard settings for tendering. You can also
specify the tendering communication and process settings that you can use in the Define Freight
Order Types Customizing activity.
In the 01 - Visibility Settings view, you can select the settings that determine the visibility
level of a price limit, submitted price, and stop dates in a tendering process.
In the 02 - Rejection Reason Codes view, you can define reason code identifiers (IDs) and
descriptions to classify your reasons for rejecting freight request for quotations (freight RFQs).
In the 03 - E-mail and SMS Content view, you can define the following settings:
- Documents for Notifications
You can specify the names of the documents that the system uses to create e-mails. You
can specify separate documents for the e-mail subject field, the e-mail body text, and SMS
text content. You can also specify additional information that the system adds to other
e-mail body text or SMS text. The system uses the e-mail or SMS type to determine
where it adds the additional text.
You must define the documents that you use in this view as General text documents in
transaction SE61.
- Triggering Notifications at Process Events
You can specify that the system sends an e-mail or an SMS message to a carrier when an
event occurs in the tendering process. Events include sending a freight RFQ to a carrier
and awarding a freight quotation (FQ).
- Bundling Notifications
You can schedule the sending of e-mails and SMS messages in a batch report. With this,
the contact person for the carrier receives e-mails or SMS messages only when the batch
report runs in your system.
The e-mails or SMS messages contain information about all the new events that have taken
______________________________________________________________
SAP AG 44
SAP System
______________________________________________________________
place since the last bundle of e-mails or SMS messages were sent. This means the carrier
does not receive 10 separate e-mails for new freight RFQs, but one e-mail containing the
information on all 10 new freight RFQs.
- General Settings
You can specify general settings for processing e-mails. You can specify the default
communication language and time zone, and the e-mail address the system uses for inbound
e-mails. You can also specify that the system sends you an automatic status confirmation
by e-mail.
- E-mail Security Settings
You must enable secure e-mail management in your system. For more information see SAP
NetWeaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key
Capability -> Platform-Wide Services -> Connectivity -> Communication Interfaces for
Mail and Telefony -> SAP Connect (BC-SRV-COM) -> Administration -> Secure E-Mail.
In the 04 - Process Settings view, you can specify the following process settings for
tendering:
- Default tendering manager
- Visibility settings
- Tendering profile
- Carrier selection settings
- Maximum response duration
- Considering the calling hours of a business partner
You can use the process and communication settings that you define here in the Define Freight
Order Types Customizing activity to specify the tendering settings for each freight order type.
The following are the settings in the freight order type that the system uses to determine the
Customizing settings for tendering:
- Default, where the system uses the system default settings
- Freight order type, where the system uses the type of freight order
- Conditions, where the system uses the runtime characteristics of a freight order
In the 05 - Communication Settings view, you can specify the following communication
settings for tendering:
- Send alerts to tendering managers whether or not the managers have subscribed to a
tendering alert category
- Use EDI messages to communicate with carriers
- Send particular types of e-mails to carriers
Types include e-mails for freight RFQs, FQ cancellations, and FQ awards.
- Send freight RFQs as e-mails or SMS messages
In the 06 - Carrier -Specific Communication Settings view, you can define communication
settings for a particular carrier that are different from the general communication settings
defined in the 05 - Communication Settings view. This includes the following settings:
- Send EDI messages to this carrier and not to other carriers
______________________________________________________________
SAP AG 45
SAP System
______________________________________________________________
- Send particular types of e-mails and SMS messages to this carrier and not to other carriers
In the 07 - Default Settings view, you must specify one default set of process settings and
one default set of communication settings for your tendering processes.
The system uses these settings if it cannot determine a freight order type. You can also enable
the system to create change documents to record the changes you make to the tendering profiles
that you edit.
6.1.4.4 Freight Booking
6.1.4.4.1 Define Freight Booking Types
Use
In this Customizing activity, you can define freight booking types.
6.1.5 Planning
6.1.5.1.1 Define Profiles and Settings
Use
To execute planning, you have to define profiles and settings and transport them into your
production system. You can define profiles and settings in SAP NetWeaver Business Client by
choosing Application Administration -> Planning.
For more information about profiles and settings, see SAP library for Transportation
Management under Profiles and Settings.
______________________________________________________________
SAP AG 46
SAP System
______________________________________________________________
6.1.5.1.2 Configure Process Controller for Planning
Use
use with planning.
and methods for a specific application process.
Activities
You can make settings for the process controller in the following Customizing activities:
- Define Service
- Define Strategy
- Define Methods
With the other Customizing activities under the node Process Controller you can define
parameters in order to further adapt your strategy.
See also
For more information, see the SAP Library for SAP Transportation Management on SAP Help
Portal at http://help.sap.com under Basic Functions -> Process Controller.
6.1.5.1.3 Define Transportation Allocation Settings
Use
In this IMG activity, you maintain transportation allocation settings.
______________________________________________________________
SAP AG 47
SAP System
______________________________________________________________
6.1.5.1.4 Define Customer-Specific Functions for Planning
Use
In this Customizing activity, you can define your own functions for the planning area and
assign your own strategies to them. The functions that you define here are automatically
available for selection on the transportation planning user interface.
Requirements
You have defined at least one strategy and at least one method. Moreover, you have assigned
this method to your strategy. For more information, see Configure Process Controller for
Planning.
6.1.5.1.5 Define Scheduling Constraints
Use
In this Customizing activity, you can define scheduling constraints. A transportation planner can
use this Customizing activity to define time-based constraints for trucks coming from or going
to a certain transshipment location.
VSR optimization and scheduling (manual planning) take these scheduling constraints into
account.
You can use scheduling constraints, for example, to approximate legal requirements regarding
driving times in planning.
For more information, see SAP Library for SAP Transportation Management under Planning ->
Interactive Planning -> VSR Optimization.
Requirements
To be able to assign a constraint set, you need to have defined means of transport. For more
information, see Define Means of Transport.
______________________________________________________________
SAP AG 48
SAP System
______________________________________________________________
Activities
1. Define an activity group, for example "Working time".

2. Assign activity types to your activity group. For example, you can assign activity types
"Transportation", "Coupling", and "Uncoupling" to your activity group "Working time".
This means that the driver of the truck will drive the truck and do all coupling and
uncoupling activities.
3. Define time constraints and assign an activity group to each time constraint.
4. Define a constraint set. A constraint set contains several time constraints and indicates the
areas or countries for which the time constraints apply. You can re-use time constraints in
other constraint sets.
5. Define means-of-transport constraints by assigning your constraint set to a means of
transport. A means of transport can only have one constraint set assigned to it. However,
you can assign a constraint set to several means of transport.
See also:
For more information, see SAP Library for Transportation Management under VSR Optimization.
6.1.5.2 Freight Unit
6.1.5.2.1 Define Freight Unit Types
Use
In this Customizing activity, you can define freight unit types.
6.1.6 Settlement
6.1.6.1 Configure Process Controller for Settlement
______________________________________________________________
SAP AG 49
SAP System
______________________________________________________________
Use
use with settlement documents.
and methods for a specific application process. For example, if you want to use
split/consolidation strategy to create settlement documents differently to the standard way, you
can define your own strategy using the process controller and assign it to the TM_INVOICE
service.
Activities
Make settings for the process controller in the following Customizing activities:
- Define Service
- Define Strategy
- Define Methods
More Information
For more information about the process controller for SAP Transportation Management, see SAP
Help Portal at http://help.sap.com under SAP Transportation Management -> Basic
Functions -> Process Controller.
6.1.6.2 Define Settlement Profile
Use
In this Customizing activity, you can define the profile for creating settlement documents. The
settlement profile consists of a set of parameters with which you can control how the system
creates settlement documents.
You can assign the defined settlement profile to an organizational unit using transaction
/SCMTMS/TCM_FASET.
If you do not specify a settlement profile, the system uses standard default settings to create
settlement documents.
Activities
Specify the following activities:
______________________________________________________________
SAP AG 50
SAP System
______________________________________________________________
- Data source to determine the type of data that the system uses when creating a settlement
document. You can specify planned, confirmed, or execution data from forwarding orders
or freight orders.
- Charge item level to determine the level in the forwarding order or freight order at which
the system calculates charges. You can select the header or item level.
- Split/consolidation strategy profile to split or consolidate settlement documents
- Invoicing level to determine one of the following settings when the system creates a
- Consolidate data from more than one forwarding order or freight order
- Create one settlement document for each order
- Create a settlement document for each main item in an order
- Calculation option to determine one of the following settings when the system creates a
- Copy all charges from the forwarding order or freight order
- Copy only the charges that are fixed and calculate all other charges again
6.1.6.3 Forwarding Settlement
6.1.6.3.1 Define Forwarding Settlement Document Types
Use
In this Customizing activity, you define types of forwarding settlement documents (FWSDs).
You can use these types to specify certain parameters for certain types of FWSDs. The
following includes some of the parameters you can specify:
- Number ranges of FWSDs
- FWSD categories
- BW relevance
- Default UoMs
______________________________________________________________
SAP AG 51
SAP System
______________________________________________________________
6.1.6.3.2 Define Number Range Intervals for Forwarding SDs
Use
In this Customizing activity, you define number range intervals for forwarding settlement
documents (FWSDs).
Activities

Note
6.1.6.4 Freight Settlement
6.1.6.4.1 Define Freight Settlement Document Types
Use
In this Customizing activity, you define types of freight settlement documents (FSDs). You can
use these types to specify certain parameters for certain types of FSDs. The following includes
some of the parameters you can specify:
- Number ranges of FSDs
- FSD categories
- BW relevance
- Default UoMs
______________________________________________________________
SAP AG 52
SAP System
______________________________________________________________
6.1.6.4.2 Define Number Range Intervals for Freight SDs
Use
In this Customizing activity, you define number range intervals for freight settlement documents
(FSDs).
Activities

Note
6.1.7 Global Trade
6.1.7.1 Define Customs Profile
Use
In this Customizing activity, you create customs profiles and define general terms for processing
information concerning customs. You can define, for example, whether the system checks if the
transport is relevant for customs and if a declaration is necessary.
Requirements
You have defined the customs relevance check in the Customizing activity Define Customs
Relevance Check.
______________________________________________________________
SAP AG 53
SAP System
______________________________________________________________
Activities
Create a profile and assign the settings. You can also change existing profiles.
6.1.7.2 Define Customs Relevance Check
Use
In this Customizing activity, you define a customs relevance check. The system checks if the
freight order is relevant for customs and if a declaration is necessary for the transportation. The
following check is available:
- Export Check
Checks if the customs union of the source location and the destination location are
different.
Requirements
They depend on the settings you make in the customs profile. For more information, see the
Customizing activity Define Customs Profile.
Standard settings
- Standard interface
/SCMTMS/IF_GT_RELEVANCE_CHECK
- Methods
CHECK_RELEVANCE_EXPORT
- Standard implementation class
/SCMTMS/CL_GT_RELEVANCE_CHECK
Activities
Select the relevant class for the relevance check that implements the above standard interface,
and select the method for the relevance check.
You can define your own customs relevance activities.
6.1.8 Integration
6.1.8.1 ERP Logistics Integration
______________________________________________________________
SAP AG 54
SAP System
______________________________________________________________
6.1.8.1.1 Order-Based Transportation Requirement
6.1.8.1.1.1 Define Order-Based Transportation Requirement Types
Use
In this Customizing activity, you specify types of order-based transportation requirements (OTR).
You can use this type to define certain parameters of the OTR that influence how the system
processes this business document.
For example, the OTR type defines the number range interval that is used to generate a number
of the OTR, or it defines whether freight units are created automatically.
You can also specify a default type that is used when the OTR is created automatically based
6.1.8.1.1.2 Assign ERP Text Types to TM Text Types for OTR
Use
displayed on the Notes tab page of the corresponding order-based transportation requirement
(OTR) in SAP TM. You do this by mapping the text type in SAP ERP to the relevant text
type in SAP TM.
Requirements

______________________________________________________________
SAP AG 55
SAP System
______________________________________________________________
6.1.8.1.2 Delivery-Based Transportation Requirement
6.1.8.1.2.1 Define Delivery-Based Transportation Requirement Types
Use
In this Customizing activity, you specify types of delivery-based transportation requirements

(DTR). You can use this type to define certain parameters of the DTR that influence how the
system processes this business document.
For example, the DTR type defines the number range interval that is used to generate a number
of the DTR, or it defines whether freight units are created automatically.
You can also specify a default type that is used when the DTR is created automatically based
6.1.8.1.2.2 Assign ERP Text Types to TM Text Types for DTR
Use
displayed on the Notes tab page of the corresponding delivery-based transportation requirement
(DTR) in SAP TM. You do this by mapping the text type in SAP ERP to the relevant text
type in SAP TM.
Requirements
______________________________________________________________
SAP AG 56
SAP System
______________________________________________________________

6.1.8.1.3 Order Scheduling
6.1.8.1.3.1 Make Settings for Sales Order Scheduling
Use
During sales order processing in SAP ERP, the dates in the SAP ERP sales order schedule
lines are determined by SAP Transportation Management (SAP TM).
Requirements
To use the synchronous scheduling of SAP ERP sales orders in SAP TM, you must set up the
following as a prerequisite:
- Asynchronous integration of SAP ERP sales orders with SAP TM order-based transportation
requirements
- Customizing-based or condition-based determination of transportation requirement types,
freight unit building rules, and planning profiles for synchronously-created transportation
requirements
In your SAP ERP system, you have assigned a Control Key for Document Transfer to
External TMS to sales orders specified by sales document type, sales area, and shipping
conditions. You have selected the Sales Order Scheduling in External TMS checkbox in this
control key.
For more information, see SAP Library for SAP Transportation Management under ERP
Logistics Integration -> Scheduling of SAP ERP Sales Orders in SAP TM.
6.1.8.2 Integration to SAP NetWeaver Business Warehouse
6.1.8.2.1 Specify Settings for BW Relevance and Data Transfer
______________________________________________________________
SAP AG 57
SAP System
______________________________________________________________
Use
You can use this activity for the following purposes:

- To access Customizing activities required for transferring data to SAP NetWeaver BW
- For more information about the activity to enable delta extraction (you determine
whether or not the system transfers data to SAP NetWeaver BW), see Customizing
for Cross-Application Components -> Processes and Tools for Enterprise
Applications -> Reusable Objects and Functions for BOPF Environment ->
PPF Adapter for Output Management -> Maintain Output Management Adapter
Settings.
- For more information about activities where you determine how the system transfers
data to SAP NetWeaver BW, see Customizing for Integration with Other
mySAP.com Components -> Data Transfer to the SAP Business Information
Warehouse.
- To access Customizing activities required for specifying the BW relevance of the following
object types:
- Order-Based Transportation Requirement Types
- Delivery-Based Transportation Requirement Types
6.1.8.3 Tracking and Tracing of Processes and Documents
6.1.8.3.1 Prerequisites for Tracking and Tracing
______________________________________________________________
SAP AG 58
SAP System
______________________________________________________________
Use
To use tracking and tracing, you have executed the following Customizing activities for SAP
Transportation Management:
- You have defined the following:
- Freight order types (see Define Freight Order Types)
- Freight booking types (see Define Freight Booking Types)
- Freight unit types (see Define Freight Unit Types)
- Transportation unit types (see Define Transportation Unit Types).
In these Customizing activities make sure that you have chosen an execution tracking
relevance.
- If you want to use an event management system or SAP Event Management to track and
trace the execution of transportation activities, for example, the loading, transportation, and
unloading of freight units, you have defined the system configuration. For more information
about the system configuration for SAP Event Management, see Customizing for SAP
Transportation Management under Integration with Other mySAP.com Components -> Event
Management Interface -> Define System Configuration.
- If you want to use SAP Event Management to track and trace the execution of
transportation activities, you have activated business function SCM_EM_TMCONTENT01
EM, Visibility Proc. for External Transportation Mgmt System in SAP Event Management.
If you want to enhance the standard Customizing, you can define own events and the processing
of these events:
- Define own transportation activities and events in SAP Transportation Management. For
more information, see Define Transportation Activities for Tracking and Tracing.
- Define these events also in the external event management system. For more information
about the event definition in SAP Event Management see Event Management -> Event
Handlers and Event Handler Data -> Codes -> Event Codes -> Define Internal Event
Codes and Internal Event Code Groups.
- To enable the processing of your own events, use BAdI: Providing Execution Data for
Transportation Activities.
6.1.8.3.2 Define Transportation Activities for Tracking and Tracing
Use
______________________________________________________________
SAP AG 59
SAP System
______________________________________________________________
In this Customizing activity you define transportation activities for tracking and tracing.
You also define events.
6.1.9 Business Add-Ins (BAdIs) for Transportation Management
6.1.9.1 Master Data
6.1.9.1.1 General Settings
6.1.9.1.1.1 One-Time Locations
Use
enhancement spot /SCMTMS/ES_OTA_LOCATION.
Requirements
Before implementing the enhancement implementation for the enhancement spot

/SCMTMS/ES_OTA_LOCATION, ensure that you have made the following Customizing settings:
- In the IMG activity Define Number Range Intervals for One-time Locations, you have
defined a number range interval of the type "internal".
If you intend to implement the Customer-Specific Search Logic for One-Time Locations BAdI,
you must set the Addr. Search indicator in the IMG activity Define General Settings for SAP
TM in addition to defining the number range intervals for one-time locations.
______________________________________________________________
SAP AG 60
SAP System
______________________________________________________________
Locations
Use

- Planning (TM-PLN)
You can use this BAdI to adjust the location data whenever a one-time location is created. This
BAdI takes control, for example, when a forwarding order or a transportation requirement is
created that has the following qualities:
- It contains address data specifying the source or destination locations but does not specify
- The address data of the location does not match any of the locations already existing in
the system.
Standard settings
Activities
See also:
Method:
Adjust Location Data for One-Time Locations
This BAdI uses the interface /SCMTMS/IF_OTA_LOCATION_DATA. For more information,

______________________________________________________________
SAP AG 61
SAP System
______________________________________________________________
Address Data
Use

- Planning (TM-PLN)
You can use this BAdI to implement a customer-specific location determination by using the
transferred address data. If you implement the BAdI, the determination takes control whenever a
transportation document is created, such as a forwarding order or a transportation requirement,
that contains address data specifying the source or the destination locations but does not specify
If a location is transferred in export structure ES_LOC_FOUND, the default address search is
suppressed automatically. A reference to this location is then inserted into the document being
created, for example to the forwarding order or to the transportation requirement, as the source
or destination location. In addition, you can explicitly suppress the default address search by
setting export parameter EV_SKIP_STANDARD.
Standard settings
Activities
See also:
Method:
Customer-Specific Location Search Based on Address Data
This BAdI uses the interface /SCMTMS/IF_OTA_LOCATION_SEARCH. For more information,
______________________________________________________________
SAP AG 62
SAP System
______________________________________________________________
6.1.9.1.1.2 Equipment Types and Equipment Groups
Use
enhancement spot /SCMB/MD_EQUIPMENT.
6.1.9.1.1.2.2 BAdI: Consistency Check for Equipment Types
Use
This Business Add-In (BAdI) is used in the component Transportation Management (SCM-TM).
You can use this BAdI to implement a consistency check for the entry of equipment types.
When an equipment type is created, the system checks whether it has already been entered and
assigned to another equipment group.
Requirements
You have defined equipment types and groups in Customizing for SAP Transportation
Management (SAP TM).
For more information, refer to the Implementation Guide (IMG) for SAP TM under
Transportation Management -> Master Data -> General Settings -> Define Equipment Types
and Equipment Groups.
Standard settings
In the standard system, the BAdI implementation Z_IMPL_EQUI_CONS_EXAMP is activated.

Activities
______________________________________________________________
SAP AG 63
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface /SCMB/IF_EQUI_TYPE_CONS. For more information,
6.1.9.1.2.1 Enhancement of SAP NetWeaver Identity Management

Integration
Use
enhancement spot /SCMTMS/IDM_TM_CUST.

Integration
Use
You use this Business Add-In (BAdI) to change or enhance the integration process between SAP
NetWeaver Identity Management and SAP Transportation Management (SAP TM).
Requirements
You are using the SAP NetWeaver Identity Management 7.1 product under license.
______________________________________________________________
SAP AG 64
SAP System
______________________________________________________________
Standard settings

The BAdI is designed for multiple use. All activated implementations are called and executed.
Activities
Example
See also:
This BAdI uses the interface /SCMTMS/IF_IDM_TM_CUST. For more information, display the
interface in the Class Builder.
6.1.9.1.2.2 Organizational Unit Integration
Use
enhancement spot /SCMTMS/ORG_UNIT_INT.
6.1.9.1.2.2.2 BAdI: Creation of Organizational Units
Use
This Business Add-In (BAdI) is used in the Organization (TM-MD-ORG) component. You can
use this BAdI to influence the creation of organizational units before saving them in the SAP
______________________________________________________________
SAP AG 65
SAP System
______________________________________________________________
Transportation Management (SAP TM) system from a connected ERP system.
Standard settings
Activities
See also

- MODIFY_INF
- MODIFY_REL
6.1.9.1.3 Transportation Network
6.1.9.1.3.1 Location

Identifiers
Use
enhancement spot /SAPAPO/ENH_LOC_ALI_VALIDATION.
______________________________________________________________
SAP AG 66
SAP System
______________________________________________________________
6.1.9.1.3.1.1.2 BAdI: Validation of Alternative Location Identifiers
Use
Standard settings

Activities
6.1.9.1.3.2 Reuse Component
6.1.9.1.3.2.1 Enhancement of Distance and Duration Determination
Use
enhancement spot /SCMB/ES_LDDD_DDD.
______________________________________________________________
SAP AG 67
SAP System
______________________________________________________________
6.1.9.1.3.2.1.2 BAdI: RC LDDD - Distance and Duration Determination
Use

(SCM-TM-MD-TN).
- GIS queries
- Determinations via transportation lanes
- Manipulation of output data of the standard determinations
Requirements
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCMB/IF_EX_LDDD_DDD. To obtain further

______________________________________________________________
SAP AG 68
SAP System
______________________________________________________________
6.1.9.1.3.2.2 Enhancement of Basic Distance and Duration Determination
Use
enhancement spot /SCMB/ES_DDD.
Use

(SCM-TM-MD-TN).
- GIS queries
- Manipulation of output data of standard determinations
Requirements
Standard settings

______________________________________________________________
SAP AG 69
SAP System
______________________________________________________________
Activities
See also:
This BAdI definition uses the interface /SCMB/IF_EX_DDD. To obtain further information,
display this interface in the Class Builder.
6.1.9.1.4 Resources
6.1.9.1.4.1 Enhancement of Check for Registration Numbers
Use
enhancement spot /SCMB/RESTMS_REGNR_CHECK.
6.1.9.1.4.1.2 BAdI: Extend Check for Registration Numbers of Resources
Use
This Business Add-In (BAdI) is used in the Resource (TM-MD-RES) component.

You can use this BAdI to implement additional checks for the registration numbers of resources.
______________________________________________________________
SAP AG 70
SAP System
______________________________________________________________
Standard settings

Activities
Example
This BAdI uses the /SCMB/IF_BADI_TMRES_REGNR_CHK interface. For more information,

6.1.9.1.5 Agreements

Determination
Use
You can use this BAdI to determine the agreement between the contractor and the contracting
partner without going through the standard agreement determination process.
If an agreement is not determined for one or more settlement documents using this BAdI and
the standard agreement determination process is required, the Continue with Standard
Determination flag can be set. If this flag is not set in this situation, charges will not be
calculated for those settlement documents.
Standard settings
Activities
______________________________________________________________
SAP AG 71
SAP System
______________________________________________________________
More Information

- FA_TARIFF_TCCS_DET
6.1.9.1.5.2 BAdI: Agreement and Calculation Sheet Filter
Use
You can use this BAdI to execute the best logic when there are one or more valid agreements
for a given contractor and contracting partner. When this is the case, the best logic is executed
in the BAdI instead of in the standard implementation. The BAdI logic filters exactly one
agreement for every settlement document. This data is then used for subsequent charge
processing.
Standard settings
Activities
More Information

- FA_TARIFF_TCCS_FILTER
______________________________________________________________
SAP AG 72
SAP System
______________________________________________________________
6.1.9.1.5.3 BAdI: Condition for Agreement Determination
Use
This Business Add-In (BADI) is used in the Charge Management (TM-MD-CM) component.
You can use this BAdI to define your conditions for the agreement header determination. This
BAdI determines if the current agreement is to be used for the given business document.
The return value for EV_EXCLUDE_FA is true if the current agreement is not correct and is
to be skipped. The return value is false if the agreement is to be considered for standard
processing.
The BAdI method for this BAdI is CHECK_CUSTOM_CONDITION and it checks the custom
condition on the agreement header.
Standard settings
Activities
6.1.9.2 Basic Functions
6.1.9.2.1 Charge Calculation
6.1.9.2.1.1 BAdI: Profitability Calculation
Use
You can use this BAdI to allocate cost in the profitability calculation process. The cost
allocation process is based on volume or weight, according to your configuration. This BAdI
allows you to define alternative ways to allocate cost.
______________________________________________________________
SAP AG 73
SAP System
______________________________________________________________
Standard settings
Activities
More Information

- ALLOCATE_COSTS
6.1.9.2.1.2 BAdI: Calculation Sheet Resolution
Use
You can use this BAdI in the calculation sheet resolution process to determine which calculation
sheet should be processed.
Standard settings
Activities
More Information
______________________________________________________________
SAP AG 74
SAP System
______________________________________________________________
- CHECK_TCCS_RESOL_RESTRICTION
- CHECK_APPLICABILITY_RULE
6.1.9.2.1.3 BAdI: Calculation Sheet Process
Use
You can use this BAdI to manipulate automatic charge calculation.
Standard settings
Activities
More Information

- GET_AMOUNT_FOR_TCE_RULE153
- APPLY_RATE_REF_ACCESS_RULE099
- GET_ADJUSTMENT_LOGIC_CLASS_NM
- GET_CALCULATION_LOGIC_CLASS_NM
- APPLY_EXCL_LOGIC
6.1.9.2.1.4 BAdI: Charge Calculation Data Access for Business Objects
Use
______________________________________________________________
SAP AG 75
SAP System
______________________________________________________________
You can use this BAdI to extend the functionality of the data access object for business objects.
You need to implement this BAdI if you have added custom resolution bases or calculation
bases. You would also need to implement this BAdI to override standard resolution or
calculation base implementations.
Requirements
You must make the following Customizing settings:

- In the Customizing activity Define Calculation Bases, you must define calculation bases for
scale bases.
- In the Customizing activity Define Resolution Bases, you must define the calculation
resolution bases.
Standard settings
Activities
More Information

- GET_RES_BASE_KEYS
- GET_CALC_BASE_VALUES
- GET_CALC_BASE_COMM
6.1.9.2.1.5 BAdI: Charge Calculation Rules
Use
You can use this BAdI to apply different techniques to calculate charges in the following areas:
- Freight agreement
- Forwarding agreement
______________________________________________________________
SAP AG 76
SAP System
______________________________________________________________
- Calculation sheet
- Rate table
Standard settings
Activities
More Information

- AGREEMENT_EXCLUSION
- CALC_SHEET_PRECONDITION
- CALC_SHEET_ITEM_PRECONDITION
- RATE_TABLE_DETERMINATION
- CHARGE_CALC_THROUGH_FORMULA
6.1.9.2.1.6 BAdI: Charge Calculation Engine
Use
You can use this BAdI to enhance any of the main steps in the charge calculation engine. This
includes the following:
- Agreement and calculation sheet determination
- Calculation sheet resolution
- Calculation sheet processing
The BAdI methods are called after each step is executed to allow the modification of the step
results.
______________________________________________________________
SAP AG 77
SAP System
______________________________________________________________
Note
All methods are mass enabled, therefore multiple requests can be processed within one call. In
general, a request key is used to uniquely identify requests in the input and output data. All
methods have an import parameter, called IS_REQUEST, that contains all necessary request
data. Component BUS_DATA_ACCESS is a reference to the business data access object, which
provides access to the logistical data of the underlying request. Component T_REQUEST_DATA
is a nested table that contains the request keys for the call.
Standard settings
Activities
See Also

- DETERMINE_CALCULATION_SHEETS
- RESOLVE_CALCULATION_SHEETS
- PROCESS_CALCULATION_SHEETS
6.1.9.2.2 Dangerous Goods
Use
enhancement spot /SCMTMS/ES_EHS_DG.
______________________________________________________________
SAP AG 78
SAP System
______________________________________________________________
6.1.9.2.2.2 BAdI: Definition of Data for Printing and Checking for Dangerous
Goods
Use
This Business Add-in (BAdI) is used in the Integration with SAP Environment, Health and
Safety Management (TM-DG-EHS) component. You can use this BAdI to change, delete, or
extend the input data for the dangerous goods check and the printing data for dangerous goods.
The BAdI is called before the system performs the dangerous goods check.
The BAdI contains the following methods:
- CHECK_DG_BC
Change Dangerous Goods Check Data.
- PRINTING_DATA_CHANGE
Change Dangerous Goods Printing Data.
When you implement this BAdI, the system might override the Customizing settings under SAP
Transportation Management -> SCM Basis -> EH&S Services -> Dangerous Goods
Management -> Dangerous Goods Checks and Dangerous Goods Management -> Dangerous
Goods Checks -> Specify Dangerous Goods Check Methods.
This BAdI provides defined interfaces, but no implementation.
Standard settings
Activities
Example
You can find example implementations in the BAdI Builder on the Enhancement Spot
Element Definitions tab in the Implementation Example Classes section.
The following example implementation is available:
- /SCMTMS/CL_EX_BADI_EHS_DG
Manipulation of the dangerous goods check. The check of definite item data is eliminated.
______________________________________________________________
SAP AG 79
SAP System
______________________________________________________________
6.1.9.2.3 Type Codes and Role Codes
Use
enhancement spot /SCMTMS/QTY_TYPE_CODE_DET.
6.1.9.2.3.2 BAdI: Quantity Type Code Determination
Use
This Business Add-In (BAdI) is used in the Transportation Management (SCM-TM) component.
You can use this BAdI to adapt the quantity type code determination in the inbound message
processing.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCMTMS/IF_QTY_TYPE_CODE_DET. For more
______________________________________________________________
SAP AG 80
SAP System
______________________________________________________________
information, display the interface in the Class Builder.
6.1.9.2.4 Change Controller
Use
enhancement spot /SCMTMS/TOR_CHACO.
6.1.9.2.4.2 BAdI: Determination of Changes for Change Controller
Use
this BAdI to enhance the standard logic of the change controller for determining changes to one
of the following business documents:
- Freight order
- Freight booking
- Freight unit
You can also use this BAdI to replace the standard logic with your own logic.
Standard settings
Activities
______________________________________________________________
SAP AG 81
SAP System
______________________________________________________________
See also

- DET_DATE_AND_LOC_CHANGES
- DET_QUANTITY_CHANGES
- DET_CUSTOM_CHANGES
6.1.9.2.5 Business Warehouse
Use
enhancement spot /SCMTMS/BW_EXTRACTION.
6.1.9.2.5.2 BAdI: Condition for Extraction
Use
Warehouse (TM-BW) component. You can use this BAdI to change the condition for
extracting business document information from the SAP Transportation Management (SAP TM)
system to the SAP NetWeaver Business Warehouse (SAP NetWeaver BW) system.
The system extracts data for the initial upload (with data) and the delta upload. The system
extracts data only for the business document types for which you have selected the BW
Relevance checkbox; you cannot use this BAdI to change the BW Relevance setting.
The standard condition uses the life-cycle status to determine whether data is to be extracted.
For the initial upload, only completed business documents are extracted (that is, their life-cycle
status has the value Completed). For the delta upload, business documents with the following
life-cycle status values are also extracted:
______________________________________________________________
SAP AG 82
SAP System
______________________________________________________________
- Business documents whose life-cycle status has the value Canceled.

- Business documents whose life-cycle status was changed from Completed to another value
(such as In Process).
Canceled business documents and those changed from Completed to another value are extracted
to the SAP NetWeaver BW system in order to be deleted.
You can use the following BAdI methods for the initial upload:
- TOR_BW_CONDITION_INIT
- TRQ_BW_CONDITION_INIT
- SFIR_BW_CONDITION_INIT
- CFIR_BW_CONDITION_INIT
You can use the following BAdI methods for the delta upload:
- TOR_BW_CONDITION_DELTA
- TRQ_BW_CONDITION_DELTA
- SFIR_BW_CONDITION_DELTA
- CFIR_BW_CONDITION_DELTA
Requirements
You have specified that the business document type is BW-relevant in one of the following
Customizing activities:
Standard settings
Activities
______________________________________________________________
SAP AG 83
SAP System
______________________________________________________________
6.1.9.2.5.3 BAdI: Fill Extraction Structures
Use
Warehouse (TM-BW) component. You can use this BAdI to enhance the extraction structures
for the extraction of business document information from the SAP Transportation Management
(SAP TM) system to the SAP NetWeaver Business Warehouse (SAP NetWeaver BW) system.
You can create an append for an extraction structure of a business document. This BAdI fills
the fields in the append with values from the business document.
Standard settings
Activities
6.1.9.2.6 Geographical Map
6.1.9.2.6.1 Enhancement to Adapt Displayed Objects
Use
//SCMTMS/ES_MAP_ADAPT_SCENE.
______________________________________________________________
SAP AG 84
SAP System
______________________________________________________________
6.1.9.2.6.1.2 BAdI: Enhancement to Adapt Displayed Objects
Use
This Business Add-In (BAdI) is used in the Map Display (TM-BF-MAP) component. You can
use this BAdI to influence the objects currently displayed on the geographical map.
Requirements
You have installed the geographical map for your SAP TM system.
Standard settings
Spot Element Definitions tab in the BAdI Builder (transaction SE18)
Activities
Example
Objects to be displayed on the geographical map are passed in the following format:
Changeable fields:
MO_ID - Readable identifier of map object
MO_ROLES - Role of map object
MO_DESCRIPTION - Description fields
MO_POSITION - Geographical position of spot
MO_START_POSITION - Geographical position of link start
MO_DEST_POSITION - Geographical position of link destination
FIXED - Map object is fixed for currently displayed objects
ACTION_REQUIRED - For map object action is required
ROUTE_POINTS - Waypoints of route
VISIBLE - Map object visibility status
______________________________________________________________
SAP AG 85
SAP System
______________________________________________________________
SELECTED - Map object selection status

HIGHLIGHTED - Map object highlight status
Fixed fields (if you change the content of the following field, the consistency of the displayed
objects cannot be guaranteed):
MO_GUID - Unique technical identifier of map object
MO_START_GUID - Unique identifier of link start
MO_DEST_GUID - Unique identifier of link destination
MO_TYPE - Map object type
MO_MULTI_GUID - Superior map object
MO_COUNT - Number of grouped map objects
See also
This BAdI definition uses the interface /SCMTMS/IF_EX_MAP_ADAPT_SCENE. For more

6.1.9.2.7 Authorizations
6.1.9.2.7.1 Authorization Check
Use
enhancement spot /SCMTMS/AC_BADI.
______________________________________________________________
SAP AG 86
SAP System
______________________________________________________________
6.1.9.2.7.1.2 BAdI: Authorization Check
Use
You can use this BAdI to change the standard authorization check for business document types
before or after the system performs the standard authorization check.
Standard settings
Activities
See also

- BEFORE_AUTHCHK
- AFTER_AUTHCHK
- FILTER_DATA
6.1.9.2.7.2 Output Management
Use
enhancement spot /SCMTMS/AC_PPF.
______________________________________________________________
SAP AG 87
SAP System
______________________________________________________________
6.1.9.2.7.2.2 BAdI: Register Additional BOs for TM Authorization Check
Use
This Business Add-In (BAdI) is used in the Transportation Management component. You can
use this BAdI to define authority checks that are carried out before Post Processing Framework
(PPF) actions are executed using business object /BOFU/PPF_OUPUT_CONTENT.
The BAdI is called before the PPF action is triggered and an authority check needs to be
performed.
Requirements
You have registered business objects in the PPF authorization check class.
Standard settings
In the standard settings, actions PRINT of business object /SCMTMS/TRQ and

IMMEDIATE_PRINT of business object /SCMTMS/TOR are registered for authorization checks.
Activities
To register further business object actions, implement method ADAPT_PPF_BO_REGISTRATION

and add the BO key and the action key to changing table CT_REGISTRY.
Specify further authorization checks within method BEFORE_AUTHCHK of BAdI: Authorization
Check.
6.1.9.2.7.3 Data Retrieval Before Authorization Check
______________________________________________________________
SAP AG 88
SAP System
______________________________________________________________
Use
enhancement spot /SCMTMS/AC_DATA_BADI.
6.1.9.2.7.3.2 BAdI: Data Retrieval Before Authorization Check
Use
You can use this BAdI to change or extend the default data retrieval for authorization checks
before they are performed.
Standard settings
Activities
See also

- GET_DATA
- FILTER_DATA
______________________________________________________________
SAP AG 89
SAP System
______________________________________________________________
6.1.9.2.8 Query Extensions
Use
enhancement spot /SCMTMS/FRW_QUERY.
6.1.9.2.8.2 BAdI: Query Extensions
Use
this BAdI to extend queries for business documents.
Requirements
- If you want to extend the selection parameters of the query, you must first extend the
query structure by adding these parameters.
- If you want to extend the result structure of the query, you must first extend it by adding
the additional attributes.
Standard settings
Activities
See also
______________________________________________________________
SAP AG 90
SAP System
______________________________________________________________
- QUERY
6.1.9.3 Forwarding Order Management
6.1.9.3.1 Approval Workflow
Use
enhancement spot /SCMTMS/TRQ_APPR_CHECK_BO.

Management
Use
This Business Add-In (BAdI) is used in the Forwarding Order Management (TM-FWM)
component.
You can use this BAdI to check mandatory fields in the business documents of forwarding
order management (business object: transportation request, TR) before proceeding with the
approval workflow. You can use the BAdI method CHECK_BO.
Requirements
In the standard system, there is an activated BAdI implementation.
Standard settings
______________________________________________________________
SAP AG 91
SAP System
______________________________________________________________
Activities
Example
This BAdI uses the interface /SCMTMS/IF_TRQ_APPR_CHECK_BO and the standard

implementation /SCMTMS/IMP_TRQ_APPR_CHECK_BO. For more information, display the
interface and the class in the Class Builder.
6.1.9.3.2 Registry Extensions
Use
enhancement spot /SCMTMS/FIELD_REGISTRY.
6.1.9.3.2.2 BAdI: Extensions of Field Registry
Use
This Business Add-In (BAdI) is used in the Forwarding Order Management component. You can
use this BAdI to check the relevance of node attributes, and it is called by the constructor of
the field registry super class.
Standard settings
The list of relevant fields is defined in the constructor of a class inherited from the field
registry super class /SCMTMS/CL_FIELD_REGISTRY. Sub classes must always be created with
private instantiation and public static method GET_INSTANCE (singleton pattern), which creates
______________________________________________________________
SAP AG 92
SAP System
______________________________________________________________
one instance of the sub class once for each transaction.

Activities
Method MODIFY_REGISTRY can be used to specify lists of node attributes that are to be
added to or removed from the field registry. This enables you to change the list of relevant
fields.
6.1.9.4 Freight Order Management
6.1.9.4.1 Tendering
Use
enhancement spot /SCMTMS/TEND.
6.1.9.4.1.2 BAdI: Creation of Proposals for Tendering Plan
Use
can use this BAdI to propose carriers and price limits in a tendering plan.
______________________________________________________________
SAP AG 93
SAP System
______________________________________________________________
Standard settings
this BAdI to use the standard logic. The standard logic is implemented in methods
ADD_PREF_TSP and PROPOSE_PRICE_LIMIT of class
/SCMTMS/CL_TEND_A_CRT_PROPOSAL, and can be overwritten or enhanced by your BAdI
implementation.
Activities
More Information

Add Preferred Carrier to Tendering Configuration
Propose Price Limit
6.1.9.4.1.3 BAdI: Evaluation of Quotations
Use
can use this BAdI to evaluate your freight requests for quotation by defining codes that rate a
quotation as one of the following:
- Quotation acceptable (ACC)
- Quotation review required (REV)
- Quotation not acceptable (NAC)
- Freight request for quotation rejected by carrier (REJ)
- Quotation received after response time (2L8)
- Quotation contains errors (ERR)
______________________________________________________________
SAP AG 94
SAP System
______________________________________________________________
In addition, you can modify the currency conversion for an incoming quotation.
Requirements
regards to evaluating freight requests for quotation.
Standard settings
/SCMTMS/CL_TEND_A_EVAL_RESP and can be overruled or enhanced by your own BAdI
implementation.
Activities
More Information

Set Evaluation Result for Tendering Responses

Tendering
Use
can use this BAdI to retrieve address information of carrier contacts, tendering managers, and
other parties specified in the freight order. You need this data for sending out freight requests
______________________________________________________________
SAP AG 95
SAP System
______________________________________________________________
for quotation and receiving responses afterwards.
Requirements
in regards to address determination.
Standard settings
/SCMTMS/CL_TEND_BUPA_TOOLS and can be overruled or enhanced by your own BAdI
implementation.
Activities
More Information

Get Carrier Contact Information with Addresses
Get Tendering Manager Information
Get Party Information
6.1.9.4.1.5 BAdI: Preselection of Freight Requests for Quotation
Use
can use this BAdI to preselect freight requests for quotation (RFQs).
When a tendering process is finished, the system preselects the most favorable freight RFQ. In
the case of a manual tendering, the tendering manager can then accept or reject the preselected
freight RFQ or can preselect or accept a different RFQ. In the case of an automatic tendering,
______________________________________________________________
SAP AG 96
SAP System
______________________________________________________________
the system automatically accepts the preselected RFQ and sends the updated freight order to the
carrier that provided the preselected freight RFQ.
Requirements
regards to the pre-selection of freight RFQs.
Standard settings
PRESELECT_RESPONSE of class /SCMTMS/CL_TEND_A_PROC_CONTROL and can be
Activities
More Information

Preselect Freight Request for Quoatation (RFQ)
6.1.9.4.1.6 BAdI: Filling of Result Structure for Forwarding and Freight RFQs
Use
This Business Add-In (BAdI) is used in the Freight Tendering (TM-FRM-FRT) component. The
BAdI can be used in the environment of queries for freight request for quotations (freight
RFQs) and forwarding request for quotations (forwarding RFQs), in particular for the tendering
manager and external carriers. You can use this BAdI to fill or change the result structure of
queries that are based on the query class /SCMTMS/CL_TEND_Q_REQ_RESP.
This applies to the following queries of the business object /SCMTMS/TOR:
______________________________________________________________
SAP AG 97
SAP System
______________________________________________________________

TENDERINGREQUEST QDB_TENDERINGREQUEST_BY_ELEMEN
TENDERINGREQUEST QDB_TEND_REQUEST_BY_WEB_USER
TENDERINGREQUEST QDB_TENDERINGREQ_BY_ELEME_EXT
TENDERINGRESPONSE QDB_TENDERINGRESP_BY_ELEMENTS
TENDERINGRESPONSE QDB_TEND_RESPONSE_BY_WEB_USER
TENDERINGRESPONSE QDB_TENDERINGRESP_BY_ELEME_EXT
TENDERINGRESPONSE QDB_TENDERINGRESP_MANUAL_ACT
Requirements
You need to create a BAdI implementation to overwrite or change the standard logic in the
result structure of the above queries.
Standard settings
this BAdI to use the standard logic. The standard logic is implemented in method
FILL_RESULT_STRUCTURE of class /SCMTMS/CL_TEND_Q_REQ_RESP and can be
overwritten or enhanced by your BAdI implementation.
Activities
More Information

______________________________________________________________
SAP AG 98
SAP System
______________________________________________________________
6.1.9.4.1.7 BAdI: Filling of Result Structure for Tendering Query
Use
can use the BAdI in the environment of queries for freight orders and tenderings. You can use
this BAdI to fill or modify the result structure of queries that are based on the query class
/SCMTMS/CL_TEND_Q_SUBCON_TEND. This applies to the following queries of the business
object /SCMTMS/TOR:
SUBCONTRACTING QDB_SUBCONTRACTING_BY_ELEMENTS
TENDERING QDB_TENDERING_BY_ELEMENTS
Requirements
regards to the result structure of the above-mentioned queries.
Standard settings
FILL_RESULT_STRUCTURE of class /SCMTMS/CL_TEND_Q_SUBCON_TEND and can be
Activities
More Information

______________________________________________________________
SAP AG 99
SAP System
______________________________________________________________
6.1.9.4.1.8 BAdI: Sending of Tendering E-Mails
Use
can use this BAdI to send e-mail or SMS messages for notifications or freight request for
quotations (freight RFQs) to the contact person of a carrier for specific events in the tendering
process.
The system can send different e-mail or SMS message types. For example, the system can send
a message informing a contact person that a tendering process has been canceled. The system
can send a message for each individual event. It can also collect the messages for a particular
period of time, and send a single message containing all the information about each single
event.
Requirements
You need to create a BAdI implementation if you want to change the standard system logic for
sending tendering e-mails or SMS messages.
Standard settings
There are four different e-mail types in the standard logic for e-mails. In these, we implement
the logic for sender determination, recipient determination, text determination, and trigger
creation and validation. These e-mail types are for the following events:
- Canceled tendering processes
- Sent freight RFQs
- Awarded freight quotations (FQs)
- Rejected FQs
this BAdI if you want to use the standard logic. We implement the standard logic in the
following methods and report:
- Method SEND_NOTIFICATION_MAIL of classes /SCMTMS/CL_TEND_D_TENDREQ_AC
and /SCMTMS/CL_TEND_D_TENDRESP_AC
- Methods of class /SCMTMS/CL_TEND_CS_HELPER
- Report /SCMTMS/TEND_NOTIFICATION_MAIL
You can overwrite or enhance the standard logic with your own BAdI implementation.
______________________________________________________________
SAP AG 100
SAP System
______________________________________________________________
Activities
- Set the Work Mode of the BAdI
- DETERMINE_RECIPIENT
- DETERMINE_SENDER
- GET_TEXT
- CREATE_TRIGGER_AFTER_COMMIT
- VALIDATE_TRIGGERS
6.1.9.4.1.9 BAdI: Triggering of Alerts
Use
can use this BAdI to trigger the creation of additional alerts for the tendering process. You can
also create and use your own alert categories in this BAdI. You can decide whether the alerts
are to be created in addition to or instead of the standard tendering alerts.
Requirements
Alert categories need to be maintained in transaction ALRTCATDEF to be able to create alerts

of those categories later on. If dynamic alert texts are to be set by the BAdI, you must
maintain containers and the message short and long texts accordingly.
Standard settings
TRIGGER_ALERT of class /SCMTMS/CL_TEND_D_TENDERING_AC and can be overruled or
enhanced by your own BAdI implementation.
______________________________________________________________
SAP AG 101
SAP System
______________________________________________________________
Activities
More Information

Trigger Tendering Alerts
6.1.9.4.1.10 BAdI: Update of Freight Order (FO) After Successful Tendering
Use
can use this BAdI to update those fields of the freight order after a successful completion of a
tendering process that you determined with this BAdI.
Standard settings
There is no standard BAdI implementation provided by SAP. However, there is no need to
/BOBF/IF_FRW_ACTION~EXECUTE of class /SCMTMS/CL_TEND_A_UPDATE_TOR and
Activities
______________________________________________________________
SAP AG 102
SAP System
______________________________________________________________
More Information

Update Freight Order Data after Successful Tendering

Assigned Carrier
Use
can use this BAdI to implement your own logic in regards to restarting a tendering process in
case an already assigned carrier, which has been determined by tendering previously, rejects his
or her confirmation. Thus a new carrier has to be determined.
Even if a carrier has already been assigned to a freight order, the carrier has still the
possibility of rejecting the freight order by sending a respective rejecting confirmation. By doing
so, a new carrier needs to be determined for this freight order. In case this carrier has been
determined earlier as the result of a tendering process, tendering can be used again for carrier
determination. This depends on whether or not this option has been selected in the
corresponding tendering process settings in Customizing, and thus a new tendering needs to be
started.
Requirements
in regards to restarting the tendering process.
Standard settings
/BOBF/IF_FRW_ACTION~EXECUTE of class /SCMTMS/CL_TEND_A_CHACO_RESTRT and
The standard logic starts a new tendering with basically the same tendering plan as the previous
tendering, which had determined the carrier that has now rejected the tendered freight order.
Since this carrier has already rejected the freight order, there is no need for him or her to
participate again in this new tendering - thus, this carrier is removed from the new tendering
______________________________________________________________
SAP AG 103
SAP System
______________________________________________________________
plan.
Activities
More Information
Modify Tendering Plan to Be Used After Restart
6.1.9.5 Planning
6.1.9.5.1 BAdI: Determination of Subcontracting-Relevant Quantity
Use
This Business Add-In (BAdI) is used in the Carrier Selection (TM-PLN-CS) component.
You can use this BAdI to implement your own logic (GET_TOR_QUANTITY) for influencing
or replacing the logic used for calculating the overall quantity of a business document that can
be subcontracted (for example, a freight unit or freight order). The system takes this quantity
into account as the overall quantity in the subcontracting area when it calculates costs or loads
specific transportation allocations.
Note:
This logic influences the quantity assigned to a business document in the complete
subcontracting area. The result of this logic might be an input of the transportation allocation
specific quantity determination which influences only the loading quantity of a specific bucket.
Requirements
Standard settings
______________________________________________________________
SAP AG 104
SAP System
______________________________________________________________
implement this BAdI to use the standard logic
Activities
6.1.9.5.2 BAdI: Calculation of TAL Relevant Quantity
Use
This Business Add-In (BAdI) is used in the Transportation Allocation (TM-PLN-TAL)

component.
You can use this BAdI to implement your own logic (GET_LOADING_QUANTITY) for
influencing the loading quantity. The free capacity of the relevant buckets will be decreased by
the determined value in the case of loading a transportation allocation and will be increased by
this value in case of unloading respectively.
Requirements
Standard settings
implement this BAdI to use the standard logic.
Activities
______________________________________________________________
SAP AG 105
SAP System
______________________________________________________________
6.1.9.5.3 Additional Dimensions
Use
/SCMTMS/ADD_DIMENSIONS.
6.1.9.5.3.2 BAdI: Additional Dimensions
Use
This Business Add-In (BAdI) is used in the Planning (TM-PLN) component. You can use this
BAdI to add additional dimensions during processing.
In the standard system, the quantity structure /SCMTMS/S_QUANTITIES from the item of the
BO transportation order includes the following dimensions:
- Mass
- Volume
- No dimensions (for example, pieces)
By enhancing this structure, you can add additional dimensions.
To guarantee that these new dimensions are taken into account, you must implement this BAdI
and fill table CT_DIMENSIONS with the dimensions you want to be handled during processing
of the BO transportation order.
Standard settings
______________________________________________________________
SAP AG 106
SAP System
______________________________________________________________
Activities
Example
You want to make sure that dimension LENGTH is processed in the capacity check.
6.1.9.5.4 VSR Optimizer
6.1.9.5.4.1 VSR Optimizer Preprocessing and Postprocessing
Use
enhancement spot /SCMTMS/PLN_OPT.
6.1.9.5.4.1.2 BAdI: VSR Optimizer Preprocessing
Use

You can use this BAdI to change input data for VSR optimization.
Standard settings
______________________________________________________________
SAP AG 107
SAP System
______________________________________________________________
Activities
6.1.9.5.4.1.3 BAdI: VSR Optimizer Postprocessing
Use

You can use this BAdI to change VSR optimizer results.
Standard settings
Activities
6.1.9.5.4.2 Explanation Tool: Customer Function
______________________________________________________________
SAP AG 108
SAP System
______________________________________________________________
Use
enhancement spot /SCMTMS/PLN_EXP.
6.1.9.5.4.2.2 BAdI: Customer Function for Explanation Tool
Use
This Business Add-In (BAdI) is used in the Planning (TM-PLN) component.

You can use this BAdI to implement customer functions within the explanation tool of the
optimizer. Within the explanation tool, a pushbutton is provided with which you can call this
BAdI.
Method:
- CUST_FUNC
Parameters:
- IV_PLN_EXP_BO_KEY: Persistent key of the business object of type
/SCMTSM/PLN_EXPL.
- IT_SELECTED_NODES: Business object nodes and keys of the objects that were selected
on the UI.
- CT_MSG: Can be filled with messages that are shown on the UI after the BAdI was
called.
Standard settings
Activities
______________________________________________________________
SAP AG 109
SAP System
______________________________________________________________
6.1.9.6 Global Trade
6.1.9.6.1 Notes on Implementation
Use
enhancement spot /SCMTMS/GT_ACTIVITIES.
6.1.9.6.2 BAdI: Change Result of Customs Relevance Check
Use
This Business Add-In (BAdI) is used in the Transportation Management (TM) component.
You can use this BAdI to change or extend data transferred through the interface
/SCMTMS/IF_GT_REL_ACTIVITY to modify the customs relevance check.
The interface is part of the customs solution of the freight order.
Requirements
You have activated the customs relevance check in Customizing for SAP Transportation
Management (TM) under Define Customs Relevance Check.
Standard settings
Activities
______________________________________________________________
SAP AG 110
SAP System
______________________________________________________________
Example
If you never use a certain freight order type, for example, ZZDE, you can exclude it from the
settings of the customs relevance check.
6.1.9.7 Integration
6.1.9.7.1 Tracking and Tracing of Processes and Documents
6.1.9.7.1.1 BAdI: Providing Execution Data for Transportation Activities
Use
This Business Add-In (BAdI) is used in the Integration with SAP Event Management
(TM-EM) component.
You can use this BAdI to process your own events for tracking the execution of physical
transports in SAP Transportation Management in a specific way.
If you define your own transportation activities and events for tracking and tracing (see Define
Transportation Activities for Tracking and Tracing), you can use this BAdI to react on those
specific events. We recommend that you use this BAdI especially in combination with an
enhancement of the extension structure /SCMTMS/INCL_EEW_TOR_EXEC, which is assigned
to the EXECUTIONINFORMATION node of business object /SCMTMS/TOR (see transaction
/BOBF/CONF_UI). The BAdI is called when an incoming event is processed.
Standard settings
Activities
Based on the importing structures and tables, the changing parameter table CT_MODIFY has to
be filled according to the method PROVIDE_CR_UPD_EXECINF of class
/SCMTMS/CL_TOR_EXEC_PROCESS.
This table is used to create or update nodes of the current processed document, for example,
freight unit. We recommend that you mainly update the execution data of the processed
document.
______________________________________________________________
SAP AG 111
SAP System
______________________________________________________________
More Information

- PROCESS_EVENT
6.1.9.7.2 Enterprise Services
6.1.9.7.2.1 Forwarding Order Management
Use
6.1.9.7.2.1.1.2 BAdI for TransportationRequestRequest_In
Use
TransportationRequestRequest_In, which is part of the Transportation Request Processing process
component.
______________________________________________________________
SAP AG 112
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.1.1.3 BAdI for TransportationRequestCancellationRequest_In
Use
TransportationRequestCancellationRequest_In, which is part of the Transportation Request
Standard settings
Activities
6.1.9.7.2.1.1.4 BAdI for TransportationRequestConfirmation_Out
Use
TransportationRequestConfirmation_Out, which is part of the Transportation Request Processing
______________________________________________________________
SAP AG 113
SAP System
______________________________________________________________
process component.
Standard settings
Activities
6.1.9.7.2.2 Freight Order Management
Use
6.1.9.7.2.2.1.2 BAdI for TransportationOrderRequest_Out
Use
TransportationOrderRequest_Out, which is part of the Transportation Order Processing process
component
______________________________________________________________
SAP AG 114
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.2.1.3 BAdI for TransportationOrderCancellationRequest_Out
Use
TransportationOrderCancellationRequest_Out, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.1.4 BAdI for TransportationOrderConfirmation_In
Use
______________________________________________________________
SAP AG 115
SAP System
______________________________________________________________
TransportationOrderConfirmation_In, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
6.1.9.7.2.2.2 Tendering
6.1.9.7.2.2.2.1 Transportation Request
Use
Use
______________________________________________________________
SAP AG 116
SAP System
______________________________________________________________
TransportationRequestQuotationCreateRequest_In, which is part of the Transportation Request

Standard settings
Activities
Use
TransportationRequestQuotationCancellationRequest_In, which is part of the Transportation
Standard settings
Activities
______________________________________________________________
SAP AG 117
SAP System
______________________________________________________________
Use
TransportationRequestQuotationConfirmation_Out, which is part of the Transportation Request
Standard settings
Activities
Use
6.1.9.7.2.2.2.2.2 BAdI for TransportationOrderQuotationCreateRequest_Out
Use
______________________________________________________________
SAP AG 118
SAP System
______________________________________________________________
TransportationOrderQuotationCreateRequest_Out, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.2.2.3 BAdI for

TransportationOrderQuotationCancellationRequest_Out
Use
TransportationOrderQuotationCancellationRequest_Out, which is part of the Transportation Order
Standard settings
Activities
______________________________________________________________
SAP AG 119
SAP System
______________________________________________________________
6.1.9.7.2.2.2.2.4 BAdI for TransportationOrderQuotationConfirmation_In
Use
TransportationOrderQuotationConfirmation_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.2.3 Booking
Use
______________________________________________________________
SAP AG 120
SAP System
______________________________________________________________
6.1.9.7.2.2.3.1.2 BAdI for TransportationOrderBookingRequest_Out
Use
TransportationOrderBookingRequest_Out, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
6.1.9.7.2.2.3.1.3 BAdI for

TransportationOrderBookingCancellationRequest_Out
Use
TransportationOrderBookingCancellationRequest_Out, which is part of the Transportation Order
Standard settings
______________________________________________________________
SAP AG 121
SAP System
______________________________________________________________
Activities
6.1.9.7.2.2.3.1.4 BAdI for TransportationOrderBookingConfirmation_In
Use
TransportationOrderBookingConfirmation_In, which is part of the Transportation Order
Standard settings
Activities
Use
TransportationOrderBookingWaybillNotification_Out, which is part of the Transportation Order
______________________________________________________________
SAP AG 122
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.3 Global Trade
6.1.9.7.2.3.1 Request for Export Declaration
Use
spot /SCMTMS/ECA_SE_SPOT_TOR.
6.1.9.7.2.3.1.2 BAdI for ExportDeclarationSUITERequest_Out
Use
ExportDeclarationSUITERequest_Out, which is part of the Transportation Order Processing
process component.
______________________________________________________________
SAP AG 123
SAP System
______________________________________________________________
Standard settings
Activities
6.1.9.7.2.3.2 Cancellation Request for Export Declaration
Use
spot /SCMTMS/EXP_SE_SPOT_TOR.
6.1.9.7.2.3.2.2 BAdI for ExportDeclarationSUITECancellationRequest_Out
Use
ExportDeclarationSUITECancellationRequest_Out, which is part of the Transportation Order
Standard settings
______________________________________________________________
SAP AG 124
SAP System
______________________________________________________________
Activities
6.1.9.7.2.3.3 Confirmation of Export Declaration
Use
spot /SCMTMS/EIN_SE_SPOT_TOR.
6.1.9.7.2.3.3.2 BAdI for ExportDeclarationSUITEConfirmation_In
Use
ExportDeclarationSUITEConfirmation_In, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
______________________________________________________________
SAP AG 125
SAP System
______________________________________________________________
6.1.9.7.2.4 Settlement
6.1.9.7.2.4.1 Forwarding Settlement
Use
spot /SCMTMS/CFI_SE_SPOT_CFIR.
Use
CustomerFreightInvoiceRequestSUITERequest_Out_V1, which is part of the Customer Freight
Standard settings
Activities
______________________________________________________________
SAP AG 126
SAP System
______________________________________________________________
Use
CustomerFreightInvoiceRequestSUITECancellationRequest_Out_V1, which is part of the Customer
Freight Invoice Request Processing process component.
Standard settings
Activities
Use
CustomerFreightInvoiceRequestSUITEConfirmation_In_V1, which is part of the Customer Freight
Standard settings
Activities
______________________________________________________________
SAP AG 127
SAP System
______________________________________________________________
6.1.9.7.2.4.2 Freight Settlement
Use
spot /SCMTMS/SFI_SE_SPOT_SFIR.
Use
TransportationOrderSUITEInvoicingPreparationRequest_Out, which is part of the Transportation
Standard settings
Activities
______________________________________________________________
SAP AG 128
SAP System
______________________________________________________________
Use
TransportationOrderSUITEInvoicingPreparationCancellation_Out, which is part of the
Standard settings
Activities
Use
TransportationOrderSUITEInvoicingPreparationConfirmation_In, which is part of the
Standard settings
Activities
______________________________________________________________
SAP AG 129
SAP System
______________________________________________________________
6.1.9.7.2.5 ERP Logistics Integration
Use
6.1.9.7.2.5.1.2 BAdI for IntracompanyTransportationRequestRequest_In
Use
IntracompanyTransportationRequestRequest_In, which is part of the Transportation Request
Standard settings
Activities
______________________________________________________________
SAP AG 130
SAP System
______________________________________________________________
Use
IntracompanyTransportationRequestCancellationRequest_In, which is part of the Transportation
Standard settings
Activities
6.1.9.7.2.5.1.4 BAdI for

IntracompanyTranspRequestSimulateReqConfirmation_In
Use
This Business Add-in (BAdI) is used in the Order Scheduling (TM-ERP-OS) component. You
IntracompanyTransportationRequestSimulateRequestConfirmation_In, which is part of the
Transportation Request Processing process component.
Standard settings
Activities
______________________________________________________________
SAP AG 131
SAP System
______________________________________________________________
6.1.9.7.2.5.2 Outbound Processing of Delivery Proposals
Use
spot /SCMTMS/DLVP_SPOT_SE_OUT.
6.1.9.7.2.5.2.2 BAdI for InboundDeliveryCreateRequest_Out
Use
InboundDeliveryCreateRequest_Out, which is part of the Transportation Order Processing process
component.
Standard settings
related to the delivery proposal and how to fill the fields of the enterprise service interface
structure.
Activities
______________________________________________________________
SAP AG 132
SAP System
______________________________________________________________
6.1.9.7.2.5.2.3 BAdI for OutboundDeliveryBulkCreateRequest_Out
Use
OutboundDeliveryBulkCreateRequest_Out, which is part of the Transportation Order Processing
process component.
Standard settings
related to the delivery proposals and how to fill the fields of the enterprise service interface
structure.
Activities
6.1.9.7.2.5.3 Outbound Delivery Confirmation
Use
spot /SCMTMS/CPX_SE_SPOT_ODLV.
______________________________________________________________
SAP AG 133
SAP System
______________________________________________________________
6.1.9.7.2.5.3.2 BAdI for OutboundDeliveryBulkConfirmation_In
Use
OutboundDeliveryBulkConfirmation_In, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
6.1.9.7.2.5.4 Inbound Delivery Confirmation
Use
spot /SCMTMS/CPX_SE_SPOT_IDLV1.
______________________________________________________________
SAP AG 134
SAP System
______________________________________________________________
6.1.9.7.2.5.4.2 BAdI for InboundDeliveryConfirmation_In_V1
Use
InboundDeliveryConfirmation_In_V1, which is part of the Transportation Order Processing
process component.
Standard settings
Activities
Use
______________________________________________________________
SAP AG 135
SAP System
______________________________________________________________
6.1.9.7.2.5.5.2 Outbound Shipment Integration
6.1.9.7.2.5.5.2.1 BAdI for TransportationOrderSCMExecutionRequest_Out
Use
TransportationOrderSCMExecutionRequest_Out, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.5.5.2.2 BAdI for

TransportationOrderSCMExecutionCancellationReq_Out
Use
TransportationOrderSCMExecutionCancellationRequest_Out, which is part of the Transportation
Standard settings
______________________________________________________________
SAP AG 136
SAP System
______________________________________________________________
Activities
Use
TransportationOrderSCMExecutionConfirmation_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.5.5.3 Inbound Shipment Integration
6.1.9.7.2.5.5.3.1 BAdI for TransportationOrderSCMRequest_In
Use
TransportationOrderSCMRequest_In, which is part of the Transportation Order Processing
______________________________________________________________
SAP AG 137
SAP System
______________________________________________________________
process component.
Standard settings
Activities
6.1.9.7.2.5.5.3.2 BAdI for TransportationOrderSCMCancellationRequest_In
Use
TransportationOrderSCMCancellationRequest_In, which is part of the Transportation Order
Standard settings
Activities
6.1.9.7.2.5.5.3.3 BAdI for TranspOrderSCMTenderingResultNotification_Out
Use
______________________________________________________________
SAP AG 138
SAP System
______________________________________________________________
TransportationOrderSCMTenderingResultNotification_Out, which is part of the Transportation
Standard settings
Activities
6.1.9.7.3 Other Web Services
6.1.9.7.3.1 Generation of a URI to Display a Transportation Document
Use
spot /SCMTMS/TDO_SE_SPOT_URI.
6.1.9.7.3.1.2 BAdI for GetTransportationDocumentURI
Use
This Business Add-in (BAdI) is used in the Transportation Charge Calculation (TM-TCC)
component. You can use this BAdI to change or extend the data transferred through the service
interface GetTransportationDocumentURI.
______________________________________________________________
SAP AG 139
SAP System
______________________________________________________________
With this BAdI, you can change the URI (uniform resource identifier) that is generated to
display a transportation document in an independent browser window. This display might be
triggered from an application outside of SAP Transportation Management (SAP TM).
Standard settings
Activities
6.2 SCM Basis
6.2.1 Integration
6.2.1.1 Basic Settings for Creating the System Landscape
6.2.1.1.1 Name Logical Systems
Use
In this step, you can define the logical systems in your distributed system.
Caution
Logical systems are defined cross-client.
Activities
1. To create a logical system, choose Edit -> New Entries.

2. Enter a name for the logical system that you want to create.
3. Enter a description of the logical system.
If you want to change this entry:

a) Select the appropriate line.
______________________________________________________________
SAP AG 140
SAP System
______________________________________________________________
b) Choose Edit -> Change field contents.

c) Enter the new text.
d) Choose Replace.
Further notes
To enable the transfer of data, you must name both the system you are in and the ERP system
to which you want to transfer data as logical systems.
Note that you also have to carry out these steps on the ERP side. The names of the logical
systems must mutually correspond. That is to say, the name that defines your own system in
this system must be specified as the logical target system in the ERP system and the name that
defines your own system in the ERP system must be specified as the logical target system in
that system.
6.2.1.1.2 Assign Logical Systems to a Client
Use
In this work step, you assign a client to each logical system.
Actions
1. Select one line.

2. Choose: Goto -> Details.
The 'Client Details' screen appears.
3. In the field Logical system, enter the name of the logical system to which you want to
assign the selected client.
______________________________________________________________
SAP AG 141
SAP System
______________________________________________________________
Notes on the transport
These settings cannot be transported. When a new system is being set up, these settings must
be made after the system installation has been completed.
Note that you also have to carry out these steps in ERP. The names of the logical systems
must mutually correspond. That is to say, the name that defines your own system in this
system must be specified as the logical target system in the ERP system and the name that
defines your own system in the ERP system must be specified as the logical target system in
that system.
6.2.1.1.3 Set Up RFC Destination
Use
In this IMG activity, you create the connection to the target system. The name of the RFC
destination has to match exactly the name of the previously-named logical target system.
Requirements
The target system must have been defined under Name Logical Systems.
Activities
1. Open the ABAP Connections node.

2. Choose Create. The RFC Destination screen is displayed.
3. Enter the required data as follows:
- RFC Destination: Enter the name of the logical target system specified in the IMG
activity Name Logical Systems.
- Connection Type: Use the input help to choose the relevant connection type.
4. Under Technical Settings enter the required data as follows:
- Load Distribution: Choose the required setting.
- Target Machine: You can determine the destination of the target machine as follows:
Call SAPlogon from the start menu.
Choose Server.
Copy the server ID from the Message Server input field.
______________________________________________________________
SAP AG 142
SAP System
______________________________________________________________
- System Number: You can determine the system number of your target system as
follows:
Call SAPlogon from the start menu.
Select your target system.
Choose Properties. You see a dialog screen in which the system number is specified.
- Gateway Host: Optional
- Gateway Service: Optional
5. Under Logon/Security and under Special Options enter the required data using the input
help.
- The client depends on the user's current authorization profile (Customizing).
- The user must also be created in the target system (SAP R/3) with a corresponding
authorization profile. If you want to carry out cross-system debugging, the user also
has to be created in the target system as a dialog user with debugging authorization.
6. Choose Destination and then TRFC Options. Under Connection Attempts Until Stop,
enter a value smaller than or equal to 10. In the field Time Between 2 Attempts
[Min], enter the value 2. Confirm the entry with Continue.
7. The connection test is optional.
Further notes
6.2.1.1.4 Assign RFC Destinations to Various Application Cases
Use
The integration via Core Interface (CIF) mainly consists of of data transfers between the
systems that run in the background and without user interaction. However, in some application
cases (for example, availability check) it may be necessary for the user to access data in the
relevant target system using a synchonous Remote Function Call (RFC). In these application
cases, it makes sense to use different RFC destinations with different user authorizations. In this
way, you can limit user authorizations for executing certain actions in the relevant logical target
system to particular application cases.
In this IMG activity you can assign the application cases.
Requirements
The target system must be defined under Name Logical Systems.

The RFC destination must be created under Set Up RFC Destination.
______________________________________________________________
SAP AG 143
SAP System
______________________________________________________________
Activities
- Use the input help for the logical system specified to choose an application case.
- Assign the required RFC destination to this application case.
6.2.1.1.5 Maintain Business System Group
Use
In this IMG activity, you determine the assignment to a business system group of this system
and the ERP systems that are to be connected. By doing this, you create areas with the same
naming conventions. These guarantee that the same names are used for master data and also
their synchronization in distributed system landscapes.
Requirements
In addition to the ERP systems, this system too must be assigned to a business system group
(BSG) as an independent logical system.
Activities
- Choose New Entries.

- On the New Entries: Overview screen, specify the following information for the business
system group:
- An alphanumerical key (maximum of 10 characters).
- A description of your choice
- Save your entries.
Example 1
An SCM System is to be connected with the two ERP systems A and B in which two different
materials (for example a hammer and a screw), have the same material number (100). The two
materials are to be represented as two different products in the SCM system.
Assign The two ERP systems to different BSGs. Assign the SCM system to one of the two
BSGs.
- ERP system A (material number 100 = hammer) -> BSG A
- ERP system A (material number 100 = screw) -> BSG B
- SCM system -> BSG A
______________________________________________________________
SAP AG 144
SAP System
______________________________________________________________
In order to avoid having two identical names and to be able to uniquely assign the material
numbers, you also need the Business Add-In (BAdI) SMOD_APOCF005 for the inbound
processing of the product (transaction SE18),
Material number 100 from BSG A is assigned product number 100 in the SCM system, for
example, whereas material number 100 from BSG B gets product number 100_B. In other
words, the materials are uniquely assigned.
For master data, the following SAP enhancements are available as BAdIs for inbound processing
in the SCM system:
- Inbound processing of location: BAdI definition SMOD_APOCF001, method
EXIT_/SAPAPO/SAPLCIF_LOC_001
- Inbound processing of product: BAdI definition SMOD_APOCF005, method
EXIT_/SAPAPO/SAPLCIF_PROD_001
- For SAP APO only, the following customer exits are available (transaction SMOD or
CMOD):
- Inbound processing of resource: APOCF008
- Inbound processing of production process model: APOCF012
Example 2
An SCM System is to be connected with the ERP systems A and B. In the ERP system A, a
certain screw has the material number 110. In the ERP system B, however, it has the material
number 120. Both material numbers are to be mapped in the SCM system to a product with
the product number 110.
Assign the two ERP systems to different BSGs. If possible, assign the SCM system to the BSG
whose data does not have to be renamed.
- ERP system A (material number 110 = screw) -> BSG A
- ERP system B (material number 120 = screw) -> BSG B
- SCM system (product number 110 = screw) -> BSG A
You use the SAP enhancement SMOD_APOCF005 to map the local ERP material number 120
to the SCM product number 110 in the SCM system.
Note
For the time being, this second scenario is only supported for material masters and product
masters. If, for example, the same customer is used with different BSGs in ERP systems A &
B, you must create two separate customer locations in the SCM system. This also applies to the
vendor, plant, and other master data.
For more information, refer to the SCM Master Data section of the SAP Library.
______________________________________________________________
SAP AG 145
SAP System
______________________________________________________________
6.2.1.1.6 Assign Logical System and Queue Type
In this IMG activity, you assign a logical system to a business system group (BSG).
Additionally, you assign a queue type (inbound queue or outbound queue) to the BSG.
In the Error Handling column, you can set the type of error handling for the logical system
concerned. You use the Postprocessing for Errors, No Splitting of LUWs setting to activate
CIF error handling.
Requirements
To enable error-free communication, every source system (ERP system) must be assigned to a
BSG. A BSG can consist of one or more source systems.
Recommendation
To choose the queue type:
If you are transferring a large amount of data to the ERP system and you want to ensure an
even load on the ERP system, choose Inbound Queues.
If you choose Inbound Queues on the SCM side, you must make the necessary settings for
the Queue-In (QIN) Scheduler in the qRFC monitor on the ERP side. Queues that the ERP
system is to process automatically must be registered in the QIN Scheduler.
- Call up the QIN Scheduler in the ERP system using the transaction SMQR.
- To select all CIF queues, enter CF* in the Queue Name field.
- Choose Register. You see the Queue Registration dialog box. We recommend the
following entries:
- Queue Name: CF*
- EXEMODE: D (Dialog processing) or B (Background processing)
- MAXTIME: 10 (maximum processing time)
- NRETRY: 30 (number of repeated attempts if queue is blocked)
- TDELAY: 300 (time between two repeated attempts)
Activities
Choose the relevant BSG using the input help and choose Adopt.
The View - Change Assignment of System/Client to RFC Destination+/> screen
appears.
Proceed as follows:
- Field BusSystGrp: Enter the name of a valid business system group.
______________________________________________________________
SAP AG 146
SAP System
______________________________________________________________
- Field LogSystem: Enter the name of the logical system that has been maintained for the
current client (source system ERP system).
- Description field: The system automatically copies the name of the BSG.
- Field SAP sys.: Set an indicator to define the ERP system as the source system.
- Field SAP Rel: Specify your valid ERP Release.
- Field Queue Type: Choose between outbound and inbound queues.
6.2.1.1.7 Settings for qRFC Communication
6.2.1.1.7.1 Configure qRFC Communication
Use
You can use the scheduler settings for inbound and outbound queues to configure communication
using queued Remote Function Call (qRFC) and therefore control the management and
monitored processing of qRFCs.
qRFC communication allows asynchronous communication with transactional security and a
serialization of calls. qRFC communication is used intensively in the Core Interface to transfer
logistical data between the systems online and thus retain the transactionality and sequence. If
the qRFC communication is not correctly configured, no further processing is carried out. In
this case, no exchange of planning data can take place and consistent planning is no longer
possible.
Inbound qRFCs are processed using the QIN scheduler, outbound ones by the QOUT scheduler.
Requirements
To avoid problem situations, we recommend that you use the current qRFC version. For more
information, see SAP Note 438015.
The qRFC is delivered as part of SAP Basis or implemented in Support Packages. An update is
also possible using a special transport. For more information, see SAP Notes 481278 and
438015.
Activities
You complete the following steps in the relevant client in the production system.
You configure the required profile parameters using transaction RZ12.
- Call transaction RZ12.
- Double-click on a server group. A dialog window is displayed in which you can set the
following parameters:
______________________________________________________________
SAP AG 147
SAP System
______________________________________________________________
- Activated (0 or 1): 1
- Max. requests in queue: 5
- Max. number of logons: 90
- Max. number of own logons: 25
- Max. number of WPs (work processes) used: 75
- Min. number of free WPs: 1
- Max. number of comm. entries: 90
- Max. wait time : 10
Use SAP Note 74141 to fill the parameters for the system concerned. Note that all entries
apart from Activated and Min. number of free WPs must be in percent.
The number of work processes (WPs) that may be used by qRFC is determined using the
following formula: (Number of all dialog WPs - minimum number of free WPs) x
maximum number of WPs used / 100. If this figure is too small, it is not possible to use
communication via qRFC.
Example 1:
There are a total of 7 dialog WPs in a system, the minimum number of free WPs
is 2, and the maximum number of WPs used is 6. The number of WPs that can
be used is calculated as follows: (7-2) x 6/100 = 0.3. In this case communication
using qRFC is not possible.
Example 2:
There are a total of 10 dialog WPs in a system, the minimum number of free WPs
is 2, and the maximum number of WPs used is 75. The number of WPs that can
be used is calculated as follows: (10-2) x 75/100 = 6. In this case, communication
using qRFC is possible.
Other profile parameters
Note that qRFC calls are processed in work processes of the type DIALOG (exception: inbound
queues). As a result, the DIALOG restriction for processing a dialog step (standard 300
seconds, system profile parameter rdisp/max_wprun_time) also applies to these RFC calls. On
every server that is available for processing parallel RFCs, more dialog work processes must be
configured than non-dialog work processes. For more information, see SAP Note 74141.
6.2.1.1.7.2 Set Up QOUT Scheduler
Use
The data transfer via Core Interface (CIF) is carried out via queued Remote Function Call
(qRFC). Outgoing qRFCs (outbound queue) are processed by the QOUT scheduler.
You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound
qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done
automatically.
______________________________________________________________
SAP AG 148
SAP System
______________________________________________________________
The following options exist for a registered destination:

- Type
- R: The destination is registered, that is, it is started using the QOUT scheduler.
- U: The destination is not registered, that is, it is not processed.
- N: The destination is not processed using the QOUT scheduler, but is sent at the time
of the COMMIT WORK.
- Max. Connections: Number of connections that are used to send the qRFCs. The default
value is 10 for ERP connections and 1 for TCP/IP connections.
- Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default
value is 60 seconds.
- The destination NONE means that the qRFCs are processed in the local system and should
not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9,
NONE can be registered and the without tRFC option set.
Requirements
The qRFC configuration must be configured. For more information, see

Configure qRFC Communication.
6.2.1.1.7.3 Set Up QIN Scheduler
Use
The data transfer via Core Interface (CIF) is carried out via queued Remote Function Call
(qRFC). If you are working with inbound queues, incoming qRFCs are processed by the QIN
scheduler.
The QIN scheduler is called using transaction SMQR. In contrast to the QOUT scheduler, only
queue names are registered in the QIN scheduler, not destinations. The registration is not made
automatically; you have to do this yourself. If a queue is not registered, it is not processed
(that is, there is no transfer).
Requirements
qRFC communication has to be configured. For more information, see Configure qRFC
______________________________________________________________
SAP AG 149
SAP System
______________________________________________________________
Communication.
Activities
- Call transaction SMQR and choose Registration.

- Enter the queue name CF* and make the required settings.
- EXEMODE: Execution mode (D - Dialog work process; B - Batch work process)
- MAXTIME: Maximum runtime that the QIN scheduler uses for activating a destination;
default value: 60 seconds
- USERDEST: RFC destination with LOGON data. Specification of a logical destination with
its own language on the local system. This means that the burden of integration can be
distributed to a server group.
- NRETRY: Number of repetitions for failed calls, default value: 30
- RDELAY: Wait time between individual calls, default value: 300
6.2.1.1.7.4 Set Up qRFC Administration for CIF Queue Display
Use
If faulty queue entries occur in the data transfer between SAP APO and SAP R/3, you can use
CIF queue display to view the contents of the queues and carry out follow-up processing for
the objects affected.
In this IMG activity, you set up qRFC administration in such a way that you can call CIF
queue display from the qRFC monitors. To do this, you have to register the program
/SAPAPO/CIF_QUEUE_EVENT2 as the display program for CF* queues.
Requirements
If you are working with outbound queues and want to navigate from the queue contents display
to the relevant application log entries in the target system, you need to enter a dialog user in
the RFC destination in user maintenance (transaction SU01) or you can use a flexible RFC
destination with a dialog user. For more information, see Assign RFC Destinations to Various
Application Cases.
Activities
- Call transaction SMQE.

- Choose Edit and Register Display Program.
______________________________________________________________
SAP AG 150
SAP System
______________________________________________________________
- Enter CF* as the queue name and /SAPAPO/CIF_QUEUE_EVENT2 as the program

name.
6.2.1.1.8 Activate / Deactivate Background RFC (bgRFC)
Use
In this IMG activity, you can activate or deactivate the background RFC (bgRFC) for the Core
Interface (CIF).
Standard settings
In the standard system, the bgRFC is not activated for the data transfer via CIF.
Activities
Call the report /SAPAPO/CIF_NEW_QRFC_CUST and acitvate the bgRFC for the required
target system.
6.2.1.2 Basic Settings for Data Transfer
6.2.1.2.1 Activate Incremental Data Transfer
Use
In this Customizing activity, you can activate the incremental data transfer for a logical system.
You can use the incremental data transfer during the initial data transfer of master data objects
from an ERP system to an SCM system via Core Interface (CIF). The incremental data transfer
is valid for the following master data objects:
- Product master data
- Location product master data
- Production data structure (PDS) (in SAP APO only)
If you do not activate the incremental data transfer, the initial data transfer via CIF stops in the
event of an error during the processing of a queue even if the error only affects one of the
objects in the queue. If the data transfer is scheduled in a background job, then the background
job is canceled. You must correct the error and start the transfer of all objects again.
______________________________________________________________
SAP AG 151
SAP System
______________________________________________________________
If you activate the incremental data transfer, the system transfers all blocks of correct master
data objects in a CIF queue so that you only have to retransfer blocks with errors. Due to the
lower volume of objects to be processed again, the retransfer becomes more effective.
Requirements
You have activated the Enhanced Initial Data Transfer (CA_CIF_INILOAD_01) business
function. This business function is available as of SAP ECC 6.0 Enhancement Package 4.
Standard settings
In the standard system, the Increm. DT (Incremental Data Transfer via CIF) checkbox is not
selected.
Activities
You can activate the incremental data transfer by selecting the Increm. DT (Incremental Data
Transfer via CIF) checkbox.
6.2.1.2.2 Set User Parameters
Use
In this IMG activity, you can make user-specific entries for the following parameters:
- Logging (configure application log on a user-specific basis)
- Debugging (activate/deactivate debugging on a user-specific basis)
- Recording (control event recording, that is, the publication of planning results)
Requirements
The settings for setting up the system landscape must already have been made.
Activities
1. Enter the user name as specified in the user master.

2. Use the field and input help to make the relevant settings for this user.
______________________________________________________________
SAP AG 152
SAP System
______________________________________________________________
6.2.1.3 BAdIs for Specific Applications
6.2.1.3.1 Location and Business Partner
6.2.1.3.1.1 BAdI: Inbound Processing for Location
Use
This Business Add-In (BAdI) is used in the SCM Basis (SCM-BAS) component.
This BAdI enables you to edit location master data that was transferred via Core Interface (CIF)
from SAP ERP when it enters SAP SCM before further processing takes place.
Standard settings
In the standard system, the Business Add-In is not activated.

The Business Add-In is not reusable.
The Business Add-In is not filter-dependent.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for
the implementation.
If implementations of this Business Add-In have already been created, the system displays them
in a dialog box. You then choose one of them by choosing Create, and continue as follows:
1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations.
2. On this screen, enter a short description for you implementation in the Implementation
Short Text field.
3. If you choose the Interface tab, you will notice that the system has filled in the Name of
the Implementing Class field automatically, by assigning a class name based on the name
of your implementation.
4. Save your entries and assign the Add-In to a package.
5. To edit a method, double-click its name.
6. Enter your implementation code between the method <Interface Name>~<Name of
Method>. and endmethod. statements.
7. Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later.
If you want to do this, do not carry out the following step:
______________________________________________________________
SAP AG 153
SAP System
______________________________________________________________
8. Choose Activate.
When the application program is executed, the system carries out the code in the method
you wrote.
Example
To display the sample code, choose Goto -> Default Code -> Display.
6.2.1.3.1.2 BAdI: Inbound Processing for Business Partner
Use
This BAdI enables you to edit business partner data that was transferred via Core Interface
(CIF) from SAP ERP when it enters SAP Supply Chain Management (SAP SCM) before further
processing takes place.
Standard settings

The Business Add-In ist not reusable.
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 154
SAP System
______________________________________________________________

8. Choose Activate.
you wrote.
6.2.1.3.1.3 BAdI: Change of Business Partner Attributes
Use
This Business Add-In (BAdI) is used in SCM Basis. You can use this BAdI to change the
attributes of business partners.
Standard settings
Activities
6.2.1.3.1.4 BAdI: Maintain and Save Business Partner Attributes
Use
This Business Add-In (BAdI) is used in SCM Basis (SCM_BASIS). In SCM Basis, you can
create a business partner manually or by transferring data such as customer and vendor data
from an ERP system using the core interface. The system calls this BAdI after creating and
saving the business partner. You can use the BAdI to maintain attributes of the business partner
______________________________________________________________
SAP AG 155
SAP System
______________________________________________________________
after the system saves the business partner.
Standard settings
Activities
6.2.1.3.2 Product
6.2.1.3.2.1 BAdI: Inbound Processing for Product
Use
This Business Add-In is used in the SCM Basis (SCM-BAS) component.

This BAdI enables you to edit product master data that was transferred via Core Interface (CIF)
from SAP ERP when it enters SCM before further processing takes place.
Standard settings

Activities
the implementation.
______________________________________________________________
SAP AG 156
SAP System
______________________________________________________________
Short Text field.
8. Choose Activate.
you wrote.
Example
To display the sample code, choose Goto -> Sample Code -> Display.
6.2.1.3.2.2 BAdI: Master Data Hierarchy for Product
Use
You can use this BAdI to process master data hierarchy data for products when it arrives in
SCM, having been transferred from SAP ERP via Core Interface (CIF), before it is processed
further.
Standard settings

The BAdI is designed for multiple uses.
______________________________________________________________
SAP AG 157
SAP System
______________________________________________________________
Activities
See also:
This BAdI uses the interface /SAPAPO/IF_CIF_ENH_MDHIER_PR.

For more information, display the interface in the BAdI Builder.
6.2.1.3.2.3 BAdI: Master Data Hierarchy for Location Product
Use
You can use this BAdI to edit master data hierarchy data for location products when it arrives
in SCM, having been transferred from SAP ERP via Core Interface (CIF), before it is
processed further.
Standard settings

Activities
See also:
This BAdI uses the interface /SAPAPO/IF_CIF_ENH_MDHIER_LP.
______________________________________________________________
SAP AG 158
SAP System
______________________________________________________________
6.2.1.3.3 Classes, Characteristics, and Classifications
6.2.1.3.3.1 BAdI: Inbound Processing for Classification
Use
This Business Add-In (BAdI) is used in the SCM Basis (SCM-BAS) application component.
You can use this BAdI to process classification data when it arrives in SCM, having been
transferred from SAP ERP via Core Interface (CIF), before it is processed further.
Standard settings

The BAdI is not designed for multiple uses.
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 159
SAP System
______________________________________________________________
8. Choose Activate.
you wrote.
6.2.1.3.3.2 BAdI: Inbound Processing for Characteristics
Use
You can use this BAdI to process characteristics data when it arrives in SCM, having been
Standard settings

Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 160
SAP System
______________________________________________________________
8. Choose Activate.
you wrote.
6.2.1.3.3.3 BAdI: Inbound Processing for Class Hierarchies
Use
You can use this BAdI to process class hierarchy data when it arrives in SCM, having been
Standard settings

Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 161
SAP System
______________________________________________________________

8. Choose Activate.
you wrote.
6.2.1.3.3.4 BAdI: Inbound Processing for Classes
Use
You can use this BAdI to process class data when it arrives in SCM, having been transferred
from SAP ERP via Core Interface (CIF), before it is processed further.
Standard settings

Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 162
SAP System
______________________________________________________________

8. Choose Activate.
you wrote.
6.2.1.3.4 Sources of Supply
6.2.1.3.4.1 BAdI: Inbound Processing for Sources of Supply
Use
You can use this BAdI to process source of supply data when it arrives in SCM, having been
Standard settings

Activities
the implementation.
______________________________________________________________
SAP AG 163
SAP System
______________________________________________________________
Short Text field.
8. Choose Activate.
you wrote.
Example
To display the sample code, choose Goto -> Sample Code -> Display in the BAdI Builder.
6.2.1.3.4.2 BAdI: Change of Sources of Supply
Use
This Business Add In (BAdI) is used in the SCM Basis (SCM-BAS) component. You can use
this BAdI to change the date of the sources of supply.
You can do the following:
- You can change the data transferred from your OLTP system to your SCM system. This
data can then be stored in your own tables.
Note: You can only select data that has been changed or created in your OLTP system.
- You can process the data marked as inactive in your OLTP system.
Note: You can only select from data that has either an "inward delivery completed"
indicator or a deletion flag in the OLTP system.
Standard settings
______________________________________________________________
SAP AG 164
SAP System
______________________________________________________________
Activities
6.2.1.3.5 Transportation Lanes
6.2.1.3.5.1 BAdI: Transportation Lanes
Use
This Business Add-In (BAdI) is used in the application component SCM Basis (SCM-BAS).
You can use this BAdI to edit transportation lane data when it arrives in SCM, having been
transferred via Core Interface (CIF) from SAP ERP, before it is processed further.
Standard settings

Activities
See also:
This BAdI uses the interface /SAPAPO/IF_CIF_ENH_TLANE.
______________________________________________________________
SAP AG 165
SAP System
______________________________________________________________
6.2.1.3.6 Batches
6.2.1.3.6.1 BAdI: CIF Inbound Processing for Batches
Use
This Business Add-In is used in the SCM Basis (SCM-BAS) component.

This BAdI enables you to edit batch master data that was transferred via Core Interface (CIF)
from SAP ERP when it enters SAP SCM before further processing takes place.
Standard settings
This Business Add-In is reusable.

Activities
See also:
This BAdI uses the interface /SAPAPO/IF_CIF_ENH_BATCH. For more information, display
the interface in the Class Builder.
6.2.1.3.7 CIF Core
6.2.1.3.7.1 BAdI: Inbound Processing for CIF Error Handling
Use
This BAdI enables you to extend the standard CIF error handling in SCM. The BAdI can be
used to write additional data into customer tables, to start customer-specific work flows or an
______________________________________________________________
SAP AG 166
SAP System
______________________________________________________________
analysis etc.
Standard settings

The Business Add-In is reusable.
Activities
See also
This BAdI uses the interface /SAPAPO/IF_CIF_ENHANCE_ERRHDL. For more information,

6.2.1.3.7.2 BAdI: Inbound Processing for Master Data Hierarchy PDS
Use
You can use the BAdI /SAPAPO/CIF_ENHANCE_MDHIER_PDS to influence master data

hierarchy data for product data structures, when it arrives in SCM, having been transferred via
Core Interface (CIF) from SAP ERP, before it is processed further.
Method INBOUND_MDHIER_PDS of this BAdI is processed when it arrives in SCM before
data is processed and updated in SCM. It can be used to change data from an SAP ERP
system in various ways during SCM inbound processing (add, change, or delete data).
Standard settings
- In the standard system, there is no activated BAdI implementation.

- The BAdI is not filter-dependent.
- The BAdI is designed for multiple uses.
Activities
______________________________________________________________
SAP AG 167
SAP System
______________________________________________________________
Example
This BAdI uses the interface /SAPAPO/IF_CIF_ENH_MDHIER_PDS. For more information,

display the interface in the BAdI Builder.
6.2.2 Master Data
6.2.2.1 Change Notification Agent
6.2.2.1.1 Maintain Change Notification Agent
Use
You can use this Customizing activity to make settings for the change notification agent (CNA).
6.2.2.2 Define Parameters for Master Data Locking Concept
Use
In this IMG activity, you can influence the performance of the master data locking concept for
each lock object, by changing the following parameters:
- Block Size in Mass Maintenance and Data Transfer
- Number of Parallel Work Processes
- Blocks per Parallel Work Process
For each lock object, you can also exclude one or more of the following maintenance types
from the master data locking concept:
- Mass Maintenance
- Transfer via Business Application Programming Interface (BAPI)
- Transfer via Core Interface (CIF)
______________________________________________________________
SAP AG 168
SAP System
______________________________________________________________
Standard settings
By default, the master data locking concept is set up for all of the maintenance types named
above.
Activities
To optimize the processing and thus performance of the lock requests, you change the
parameters named above. The effects of these settings strongly depend on each individual
situation. SAP recommends that you test different settings to achieve an optimal result for your
concrete situation.
To exclude a maintenance type from the master data locking concept, you reset the
corresponding indicator. The system no longer sets a lock if you change the master data objects
via this maintenance type. This can make sense if master data objects that lock each other
affect the performance.
For more information about the master data locking concept, see the online documentation of
SCM Basis under Master Data -> General Master Data Functions -> Master Data Locking
Concept.
6.2.2.3 Maintain Freely-Definable Attributes
In this IMG activity, you release those fields in the product or location master in which product
or location attributes can be maintained. These fields are not available by default as they are
for additional information that is not required as a general rule.
Product master: The fields for global product master data can be found on the tab Properties.
Attribute fields for location-specific product master data can be found on the tab Extras, which
is only available if at least one of these fields is released.
Location master: Attributes for location mster data can also be found on the tab Extras, the
existence of which requires that such a field be released.
- An attribute is defined by its field and table name. A field name must be maintained for
this attribute in order for you to open a field in the product master. The definition of the
field name can be language-dependent.
- An attribute is activated when the language of the field name and the language in which
you have logged onto the system are identical, or when the field name was maintained
independent of a language.
Activities
1. Enter a field name and a table name as follows:

- Global product master data:
Field name: ATTnn with 'nn' from '01' to '05',
______________________________________________________________
SAP AG 169
SAP System
______________________________________________________________
Table name: /SAPAPO/MATKEY.

There are five attributes.
- Location-specific product master data:
Field name: ATnnn with 'nnn' from '101' to '105',
Table name: /SAPAPO/MATLOC.
- Location master data:
Field name: ATTLOnn with 'nn' from '01' to '05',
Table name: /SAPAPO/LOC.
2. Specify a language.
3. Enter a field name. This name is used on the aforementioned tabs as a description of each
attribute field.
6.2.2.4 Calendar
You perform the system settings for the different calendar types in the following steps.
6.2.2.4.1 Maintain Factory Calendar
The public holiday and factory calendar is a central module in the SAP System. It is used in
many areas (for example, in Logistics and in Human Resources) in the standard version.
You can use the calendar to maintain and display the components of the calendar system. The
public holiday and factory calendar data calculated from calendar maintenance is directly
available to the system.
A factory calendar is allocated to your plant via the definition of plants.
The calendar system consists of the following components:
- Public holidays
Definitions for public holidays: Calculation rule for the date, religious denomination, and so
on.
- Public holiday calendar
Any composition of public holiday rules.
- Factory calendar
Definition of workdays including special regulations, under the assignment of a particular
public holiday calendar.
Standard settings
The system delivers definitions of all common public holidays and public holiday rules, as well
______________________________________________________________
SAP AG 170
SAP System
______________________________________________________________
as a standard factory calendar.

A main memory area of 400000 Bytes is reserved for calendar data in the standard version.
This is the mimimum buffer size, which you should not go under.
Activities
Check whether all the definitions for public holidays and public holiday rules that you need are
available in the sytem. If necessary, maintain the public holiday definitions and copy them to
new or existing public holiday rules.
Create factory calendars if necessary.
Public Holidays
Check that existing public holidays are complete, and create new definitions if required:
1. Double-click with the mouse on the Execute symbol, select the option Public holidays and
choose the function Display. You receive a list of the defined public holidays.
2. Check whether the list of public holidays displayed contains all the public holidays that you
need. If you want to see detailed information on any public holiday, choose the function
Display def.
3. If you need other public holidays, return to the initial screen of the maintenance
transaction, and choose the function Change. You again receive a list of the defined
public holidays.
4. Choose the function Insert. A screen appears for the selection of the type of public
holiday.
5. Select the desired type of public holiday and choose Insert. A screen appears in which
you can determine public holidays and maintain their characteristics.
6. Enter the following data:
- Date or calculation rule
- If necessary, public holiday guarantee (for fixed and irregular public holidays
- Public holiday text (short and long)
- If required: Sort criterion, religious denomination or public holiday class
(For notes on this, see the F1 Help).
Save the definition.
Public holiday calendar
Combine the public holidays you require in a public holiday rule in the public holiday calendar:
1. Double-click with the mouse on "Execute function", select the option Public holiday
calendar and choose the function Display.
2. Check whether all the public holiday rules that your require are available. To get the
definitions for a public holiday calendar, position the cursor on it and choose the function
Display def..
______________________________________________________________
SAP AG 171
SAP System
______________________________________________________________
3. If you need other public holiday calendars or would like to change existing ones, return to
the initial screen of the maintenance transaction and choose the function Change.
4. To create a public holiday calendar, choose the function Insert (to change a public holiday
calendar, position the cursor on it and choose Change), and make the following entries:
- Calendar ID and a descriptive short text
- Period of validity (From year, To year)
5. Using the function Assign public holidays, generate a complete list of defined public
holidays.
6. Select the public holidays you need, and choose Assign public holidays.
Factory calendar
Define a factory calendar including the relevant public holiday calendar:

2. In calendar maintenance, select the option "Factory calendar", and choose the function
Change.
3. Choose the function Insert and make the following entries: Factory calendar ID and a
descriptive short text
- Public holiday calendar ID
- Start no. factory date
Number from which the factory date is incremented for each workday. If you do not
make an entry, the default value is "0".
4. Decide which days of the week are meant to be workdays.
5. Define special rules if necessary (e.g. plant holidays).
Further notes
- Calendar buffer
If you want to increase the size of the calendar buffer, maintain the parameter
zcsa/calendar_area with the maintenance transaction for system profiles. Restart the system
for the value to take effect.
- Transport
Changes to calendar data are not automatically included in a correction request. For the
calendar data to be utilizable in another system, use the function Transport in the initial
screen of the maintenance transaction. Note that you cannot transport individual public
holidays or calendars. You can only transport calendar data in its entirety. When you do
this, all public holidays, public holiday and factory calendars existing in the target system
are deleted.
______________________________________________________________
SAP AG 172
SAP System
______________________________________________________________
6.2.2.4.2 Maintain Planning Calendar (Time Stream)
In this step you create a time stream, or calendar, that serves as the basis for planning. The
time stream can be set up in weekly or monthly periods.
Activities
1. Enter a unique name for the time stream (calendar), and choose Create. The Change
Planning Calendar screen appears.
2. Enter a short description for the time stream.
3. Enter how many years into the past the calendar is to extend. This setting is optional.
4. Enter how many years into the future the calendar is to extend.
Note
If you do not make an entry in this field, the system considers the current year only.
5. Use the input help to select the time zone for the location to which this calendar is
assigned.
6. Select one of the following calendar options, depending on the location or transportation
lane associated with this calendar:
- Factory calendar (with gaps)
- Period calendar (without gaps)
7. Use the input help to select a pre-defined calendar.
8. Choose Periods to define the periods for this calendar.
9. Select the required time interval (week or month). The interval is displayed in weeks or
months accordingly.
10. The information you enter in this step depends on whether you selected week or month
for the time interval:
- If you selected week, assign numbers 1 - 7 (1 for Monday, 2 for Tuesday, and so
on) to the periods and enter the required times.
- If you selected month, assign numbers 1 - 5 in the first column for the weeks in a
month, and number 1 - 7 in the second column for the days of the week. Enter the
required times.
11. Choose Periods to generate the periods. You always have to generate the periods again
when you have changed the calculation rules.
12. Choose Save.
Example 1
To set up a simple, weekly planning calendar that goes from Mondays to Fridays, from 08:00
to 17:00 every day, for one year without including weekends, enter the general data and
choose:
______________________________________________________________
SAP AG 173
SAP System
______________________________________________________________
- Factory calendar (with gaps)

- Calculation rule: weeks
Set up the calculation rule as follows:
1 (Mon.) from 8:00:00 to 17:00:00
2 (Tues.) from 8:00:00 to 17:00:00
3 (Wed.) from 8:00:00 to 17:00:00
4 (Thurs.) from 8:00:00 to 17:00:00
5 (Fri.) from 8:00:00 to 17:00:00
Choose the Periods tab page to view the calendar periods.
Example 2
To set up monthly planning periods that run daily around the clock with no breaks, beginning
at 08:00 every 2nd and 4th Friday of the month for one year, enter the general data and
choose:
- Period calendar (without gaps)
- Calculation rule: months
Define the time interval as foolows:
(Week) 2 5 (Friday) from 8:00:00 to '
'
(Week) 4 5 (Friday) from 8:00:00 to '
'
Choose the Periods tab page to view the calendar periods.

Note
End the periods of a period calendar with the start of the next periods.
In the above example, one period stretches from 8:00:00 on the 2nd Friday in a month to
07:59:59 on the 4th Friday.
6.2.2.5 Location
6.2.2.5.1 Activate Change Documents
Use
In this IMG activity, you can specify whether or not the System is to log changes to location
master data.
______________________________________________________________
SAP AG 174
SAP System
______________________________________________________________
performance.
You can display the change documents for a location via the SCM Basis menu under Master
Data -> Location -> Display Change Documents or via transaction
/SAPAPO/LOC_CD_READ.
Standard settings
In the standard system, change logging via change documents is not active for locations.
6.2.2.5.2 Configuration for Alternative Location Identifiers
Use
Requirements
______________________________________________________________
SAP AG 175
SAP System
______________________________________________________________
Activities
Specific ALI Types.
6.2.2.5.3 BAdI: Validation of Alternative Location Identifiers
Use
Standard settings

______________________________________________________________
SAP AG 176
SAP System
______________________________________________________________
Activities
6.2.2.6 Business Partner
6.2.2.6.1 Define Transportation Service Level Codes
Use
In this Customizing activity, you define transportation service level codes for the customer and
the vendor.
Activities
You specify transportation service levels for the customer and the vendor in the business partner
master (transaction BP) on the Customer Org. Data or Vendor Org. Data tab page under
Shipping.
Note: The Customer Org. Data or Vendor Org. Data tab pages are only available using the
business partner roles Sold-to-Party (CRM000) and Ship-To-Party (CRM002) for the customer
tab pages and Vendor (BBP000) and Carrier (CRM010) for the vendor tab pages.
6.2.2.6.2 Map ERP Shipping Conditions to Transp. Serv. Level Codes
Use
In this Customizing activity, you map shipping conditions from the ERP system to transportation
______________________________________________________________
SAP AG 177
SAP System
______________________________________________________________
service level codes in SCM Basis.
Requirements
You have defined transportation service level codes in the Define Transportation Service Level
Codes Customizing activity.
6.2.2.6.3 Define Industry Keys
Use
In this Customizing activity, you define industry keys. You can group together your vendors or
customers by industry.
Activities
You define which industry the vendor or customer belongs to in the business partner master
(transaction BP) on the Customer Data or Vendor Data tab page under General Data.
Note: The Customer Data or Vendor Data tab pages are only available using the business
partner roles Sold-to-Party (CRM000) and Ship-To-Party (CRM002) for the customer tab pages
and Vendor (BBP000) and Carrier (CRM010) for the vendor tab pages.
6.2.2.6.4 Define Terms of Payment
Use
In this Customizing activity, you define the terms of payment. You define cash discount
percentages and the periods allowed for payment (discount-qualifying periods).
______________________________________________________________
SAP AG 178
SAP System
______________________________________________________________
Activities
You define the terms of payment for the vendor or customer in the business partner master
(transaction BP) on the Customer Company Org. Data or Vendor Company Org. Data tab
page under Additional Settings.
Note: The Customer Company Org. Data or Vendor Company Org. Data tab pages are
only available using the business partner roles Sold-to-Party (CRM000) and Ship-To-Party
(CRM002) for the customer tab pages and Vendor (BBP000) and Carrier (CRM010) for the
vendor tab pages.
6.2.2.6.5 Define Customer Account Groups
Use
In this Customizing activity, you define customer account groups.
Activities
You define a customer account group for the customer in the business partner master
(transaction BP) on the Customer Data tab page under Accounting.
Note: The Customer Data tab page is only available using the business partner roles
Sold-to-Party (CRM000) and Ship-To-Party (CRM002).
6.2.2.6.6 Define Vendor Account Groups
Use
In this Customizing activity, you define vendor account groups.
Activities
You specify a vendor account group for the vendor in the business partner master (transaction
______________________________________________________________
SAP AG 179
SAP System
______________________________________________________________
BP) on the Vendor Data tab page under Accounting.

Note: The Vendor Data tab page is only available using the business partner roles Vendor
(BBP000) and Carrier (CRM010).
6.2.2.6.7 Define Business Partner Functions
Use
In this Customizing activity, you define the functions that exist for the business partners, for
example for the sold-to-party, the ship-to-party, the vendor, and the carrier.
Activities
You specify the function of the vendor or customer in the business partner master (transaction
BP) on the Vendor Partner Functions or Customer Partner Functions tab pages.
Note: The Vendor Partner Functions and Customer Partner Functions tab pages are only
available using the business partner roles Sold-to-Party (CRM000) and Ship-To-Party
(CRM002) for the customer tab pages and Vendor (BBP000) and Carrier (CRM010) for the
vendor tab pages.
6.2.2.6.8 Define Delivery Priorities
Use
In this Customizing activity, you define delivery priorities.
Activities
You specify a delivery priority for the customer in the business partner master (transaction BP)
on the Customer Org. Data tab page under Shipping.
Note: The Customer Org. Data tab page is only available using the business partner roles
Sold-to-Party (CRM000) and Ship-To-Party (CRM002).
______________________________________________________________
SAP AG 180
SAP System
______________________________________________________________
6.2.2.6.9.1 Organizational Model
6.2.2.6.9.1.1 Create Organizational Model
______________________________________________________________
SAP AG 181
SAP System
______________________________________________________________
6.2.2.6.9.1.2 Change Organizational Model
Use
In this Customizing activity, you can change the organizational model of your organization. You
can change settings such as the organizational unit function and roles, the organizational
structure or staffing assigned to organizational units.
Requirements
In the Customizing activity Create Organizational Model, you have created an organizational
model.
______________________________________________________________
SAP AG 182
SAP System
______________________________________________________________
6.2.2.7 Product
In the following steps, you perform the ncessary system settings for the product master.
6.2.2.7.1 Maintain Product-Relevant Hierarchies and Hierarchy Structures
Use
In this IMG activity, you specify that certain already created hierarchies or hierarchy structures
are to have a specific product-relevant meaning.
You can define the following:
- Hierarchy for planning products
- Hierarchy structure for bills of distribution (BODs)
- Hierarchy structure for transportation lanes
- Product hierarchy for AFS planning
- Location product hierarchy for AFS planning
- Production data structure hierarchy for AFS planning
Requirements
The selected hierarchies / hierarchy structures must already be created. For more information,
see the input help for the respective fields.
Activities
Select the hierarchies / hierarchy structures you want.
6.2.2.7.2 Specify Output Format of Product Number
In this work step, you determine the following:

- Maximum input and output length of the product number
The length can be up to a maximum of 40 places.
- Template for displaying the product number (on-line or printing)
You must type an underscore at every place in the product number that
should not contain template characters.
- Display with or without leading zeros
- Storage type of the product number
______________________________________________________________
SAP AG 183
SAP System
______________________________________________________________
You can make these product number settings for the entire system.
Activities
1. Determine the maximum length of the product number.

2. Determine a product number template.
3. Determine if the product number should be displayed with or without leading zeros.
4. Determine the storage type of the product number.
Dependencies
Effects on ERP systems via Core Interface (CIF):

The settings made here are independent of the ERP system and only influence the conversion of
the internal SAP APO display to external SAP APO display.
As with conversion of SAP APO data, there is also a similar conversion of the internal SCM
display to external SCM display. So that the numbers also appear immediately on the interface,
it is recommended that you use a corresponding conversion in SCM and in ERP.
If SCM is planning for several ERP systems, it may be necessary to make the identical
numbers from different ERP systems unique in SCM. It is usual to use a prefix or suffix to do
this. In this case, the internal ERP display and the internal SCM display are different. The
conversion between the internal and external SCM display thus also differs from the conversion
in ERP.
6.2.2.7.3 Configure Time Base of Fields
In this work step you can change the time base of a field. A change to the time base is only
possible for the field product dependent storage costs. A change makes sense if the
number of decimal places is not enough to represent the storage costs per day.
Example
The product dependent storage costs field in the location-specific product master usually
uses the time base day; in other words, normally refers to a base unit of measure per day. In
this work step you can set the time base to year, for example.
Recommendation
Only change the time base for the field product dependent storage costs if no storage costs
have been maintained yet. A change to the time base changes the way in which the values that
have already been stored are interpreted and should be regarded as critical. If values already
exist, these are wrongly evaluated after a change.
______________________________________________________________
SAP AG 184
SAP System
______________________________________________________________
The field product dependent storage costs is used by PP/DS and SNP.
6.2.2.7.4 Maintain Rounding Profiles
Use
In this IMG activity, you define rounding profiles. Using rounding, the system can adapt the
quantity of a product to packing, handling, delivery, or transport units. You assign a rounding
profile to a product, if the rounding value that the system is to consider during rounding is to
depend on the product quantity to be rounded.
Elements of a Rounding Profile
A rounding profile is made up of one or more levels in ascending order. You can assign a
threshold value and a rounding value to each level. If the quantity to be rounded reaches a
threshold value, the system takes into account the rounding value that is assigned to this level.
When the quantity reaches the next threshold, the system takes into account the rounding value
that is assigned to the corresponding level. You have to enter the levels, threshold values, and
rounding values in ascending order. During rounding later on, however, the system evaluates the
levels in a descending order starting from the highest level that applies to the quantity to be
rounded.
Use of Rounding Profiles in Different Applications

Note that different applications use the levels, thresholds, and rounding values of a rounding
profile differently, as follows:
- SAP APO applications
In SAP Advanced Planning and Optimization (SAP APO), rounding profiles are relevant for
materials requirements planning in Production Planning and Detailed Scheduling (PP/DS)
and for the heuristic in Supply Network Planning (SNP). During rounding, the system
always uses the highest level rounding value that is applicable to round up the quantity to
the next whole-numbered multiple of this rounding value. If the quantity is below the first
threshold, no rounding takes place.
- SAP SNC applications
In SAP Supply Network Planning (SAP SNC), rounding profiles are relevant for the
replenishment service. Using a rounding profile, the replenishment service can perform a
two-level rounding for the product. For two-level rounding, you assign the product a
rounding profile that is made up of two levels only. During rounding, the system first
divides the quantity to be rounded by the greater second-level rounding value. (This
corresponds to building as many as possible larger packing units.) Using the first-level
rounding value, the system then rounds the remaining quantity up to the next
whole-numbered multiple of the first-level rounding value. (This corresponds to filling as
many as possible small packing units completely.) If the rounded remaining quantity
______________________________________________________________
SAP AG 185
SAP System
______________________________________________________________
reaches or exceeds the second-level threshold, the remaining quantity is rounded up to the
second-level rounding value. (This corresponds to using only the large packing units.) For
the first level, you do not specify a threshold value.
Activities
1. If the system is to use a rounding profile for rounding the quantities of a particular
product, define a rounding profile. You enter the threshold value and the rounding value
with respect to the product's base unit of measure.
2. Assign the rounding profile to the product in the location product master.
Example
SAP APO PP/DS: Rounding in Materials Requirements Planning

A product has the base unit of measure of 1 unit. A purchase order is tobe in layers or in
pallets. 1 layer equals 5 units. 1 pallet equals 40 units. From a requirement of 2 units, the
system is to round up to 5 units. From a requirement of 32 units, the system is to round up to
40 units. You define the profile PPS_ROUND as follows:
- For the first level, you enter the following data:
- Profile: PPS_ROUND
- Level: 1
- Threshold Value: 1
- Rounding Value: 5
- For the second level, you enter the following data:
- Profile: PPS_ROUND
- Level: 2
- Threshold Value: 32
- Rounding Value: 40
Using these settings, the system rounds a requirement quantity as follows during materials
requirements planning (requirement value -> rounded value):
1 -> 1
2 -> 5
6 -> 10
7 -> 10
31 -> 35
32 -> 40
41 -> 45
SAP SNC: Two-Level Rounding (Replenishment Service)
______________________________________________________________
SAP AG 186
SAP System
______________________________________________________________
See SAP Library for SAP Supply Network Collaboration on SAP Help Portal at
http://help.sap.com -> Replenishment -> Replenishment Planning -> Replenishment
Service -> Rounding -> Two-Level Rounding.
Use
In this IMG activity, you can specify whether or not changes made to product master data are
to be logged.
performance.
You can display the the change documents for a product via the SCM Basis menu under
Master Data -> Product -> Display Change Documents or using transaction
/SAPAPO/PROD_CD_READ.
Standard settings
Im the standard system, the logging of changes with change documents is not active for
products.
6.2.2.7.6 Product Groups
6.2.2.7.6.1 Define Product Group Types
Use
In this IMG activity, you define product group types. You can then assign values to these
under Define Product Groups.
Product group types and product groups serve to group products of the same kind. You define
______________________________________________________________
SAP AG 187
SAP System
______________________________________________________________
a product group type for the criterion with which the product groups are to be formed.
You can assign product group types, which you have defined here, to a product in the product
master on the Properties 2 tab page.
You can also set the following indicators for a product group type:
- Relevant for Transportation Lanes
- External Material Group
Activities
1. Enter a two-character code and a description for the product group type.
2. Assign a number to the product group type.
3. Save your input.
Example
You want to group products according to the criterion size. You define a product group type
size for this product. You then assign the values small, medium, and large to this product
group type.
6.2.2.7.6.2 Define Product Groups
Use
In this IMG activity, you define the possible product groups for a product group type.
Definition of product groups is a prerequisite for Service Parts Planning (SPP) processes.
Requirements
You have already created product group types in Define Product Group Types.
Activities
1. Enter an existing product group type.

2. Assign one or more values to the product group type.
Example
You have defined a size product group type. You assign the values small, medium and large
______________________________________________________________
SAP AG 188
SAP System
______________________________________________________________
to the size product group type.
6.2.2.7.7 Maintain Type of Alternative Product Number
Use
In this IMG activity you define the types of alternative product numbers (APN types). You
need APN types to assign one or more alternative product numbers to a product in the product
master.
Activities
1. Enter a two-digit code and a description.

2. Assign a number to the APN type.
4. The system displays the APN type in the product master on the Properties 2 tab page.
6.2.2.7.8 Define Replenishment Indicator
Use
In this IMG activity, you define replenishment indicators.

In the Service Parts Planning (SPP) processes, the replenishment indicator controls how
replenishment is managed. You can select the replenishment indicators defined here in the
product master on the SPP Requirements Planning tab page for a location product.
Certain replenishment indicators are predefined by SAP and are delivered as standard.
Activities
1. Enter a two-digit code and a description of the replenishment indicator.

2. Set the relevant indicators.
______________________________________________________________
SAP AG 189
SAP System
______________________________________________________________
6.2.2.7.9 Define ABC Indicators
Use
In this IMG activity, you specify the values for the ABC indicator for a product.
Activities
Define the values for the ABC indicator for a product. The system checks the values in the
ABC Indicator field if you are working with mass maintenance for location products, for
example.
Example
You assign the ABC indicator for products in order to classify them according characteristics
such as the following:
- A: Important
- B: Less important
- C: Relatively unimportant
A products are then products that are of the greatest importance for a firm's production, for
instance.
6.2.2.7.10 Maintain Transportation Group
Use
In this IMG activity, you maintain Transportation Groups.
______________________________________________________________
SAP AG 190
SAP System
______________________________________________________________
6.2.2.7.11 Define Packaging Material Types
Use
In this IMG activity, you define the packaging material types that you need for packing. The
packaging material type summarizes packaging materials into groups, and contains the essential
control characteristics that are valid for the relevant packaging materials.
Activities
Create the required packaging material types and use the following indicators or fields to
determine how this packaging material is to be used:
- Packaging material category
The packaging material category specifies the type of packaging material contained in this
packaging material type.
- Variable tare weight
Specifies the tare weight of a packaging material in this packaging material type as
variable. This causes the system to adjust the tare weight when the total weight of a
handling unit changes.
- Closed
Indicates whether the packaging material is closed packaging.
- Status profile
Assigns the user status profile maintained here to the handling units that you generate with
the packaging material of this packaging material type.
- Capacity check method
Determines how the capacity check method is to be performed.
- Delete
Indicates how the system is to manage handling units that become empty.
6.2.2.8 Partner-Dependent Data
6.2.2.8.1 Activate Change Documents for Partner-Dependent Locations
Use
In this IMG activity, you activate the change documents for the partner location.
______________________________________________________________
SAP AG 191
SAP System
______________________________________________________________
6.2.2.8.2 Activate Change Documents for Partner-Dependent Product Data
Use
In this IMG activity, you activate the change documents for the partner product.
6.2.2.9 Resource
6.2.2.9.1 Processor
6.2.2.9.1.1 Make Settings for the HR System
Use
You use this IMG activity to define the HR systems that are relevant for the employee or
processor.
Here you can also define whether an HR system is to always be displayed as a proposal when
creating new processors, to simplify the process for maintaining master data for a processor
(business partner with role type Processor).
The HR system is used when HR-specific data is to be communicated between the SCM system
and the corresponding HR system. The number range interval for performance documents is
assigned to the HR system.
If you are not using an HR system but want to use performance documents, you have to define
a dummy HR system and specify a number range interval for the performance document.
______________________________________________________________
SAP AG 192
SAP System
______________________________________________________________
Activities
1. Define the HR systems.

2. Define a number range interval in the EWM system, and specify this in the HR system.
3. For every connected HR system, define the origin, wage types, and currency.
Use
Activities

6.2.2.10 Transportation Lane
6.2.2.10.1 Maintain Transportation Mode
In this step you maintain the transportation mode.
Example
A transportation mode can be:

- Road
______________________________________________________________
SAP AG 193
SAP System
______________________________________________________________
- Rail
- Air
- Sea
Activities
1. Select the New Entries key in the Change View "Transportation Mode": Overview
screen.
2. Enter a description for a transportation mode and choose Save.
3. Leave the screen using the Back key.
6.2.2.10.2 Maintain Means of Transport
You use this IMG activity to maintain the means of transport.
Example
Means of transport include:

- Airplane
- Train
- EuroTrucking
- ABC shipping
Activities
1. Choose new entries.

2. Enter an ID and description for each means of transport.
3. Save.
Duration and distance
If you want to calculate means of transport-dependent duration times and distances within
transportation lanes for exact streets, for instance by connecting the Geo Information Tool (GIS)
to the Internet Graphic Server (IGS), make the following settings for the relevant means of
transport:
______________________________________________________________
SAP AG 194
SAP System
______________________________________________________________
- Set the Distance and Duration Time Calculation in IGS Quality indicator.
- Enter a low speed.
- Enter a medium speed.
- Enter a high speed.
6.2.2.10.3 Set Usage of GIS Tool
Use
Within the transportation lane, you have the option of determining distances and durations for a
means of transport using a geographical information system (GIS).
When you have installed a GIS and connected via the Internet Graphics Server (IGS), you can
specify in this work step for each client whether the system is to use this tool.
You can also change the standard RFC destination for the IGS. This is not usually necessary,
and you should only use this for a temporary installation of a second GIS or IGS.
Requirements
Use
In this IMG activity, you can specify whether or not changes made to transportation lanes are
to be logged.
performance.
You can display the the change documents for a transportation lane via the menu under Master
Data -> Transportation Lane -> Display Change Documents or using transaction
/SAPAPO/TR_CD_TLANE.
______________________________________________________________
SAP AG 195
SAP System
______________________________________________________________
Standard settings
Im the standard system, the logging of changes with change documents is not active for
6.2.2.10.5 Transportation Service Provider Profile
6.2.2.10.5.1 Define Freight Code Sets, Freight Codes, and Determination
Use
In this IMG activity, you define freight code sets, freight codes, and and freight code
determination.
Freight codes are used together with freight code sets of freight forwarders and rail carriers to
classify the goods that are to be transported. Freight codes are used for communication with
freight forwarders and are specified in the shipping papers.
Some freight codes are issued by freight forwarders and rail carriers and are used specifically
for transportation by rail or road.
The determination of freight codes is carried out in two steps:
- Automatic determination of freight code sets on the basis of the following criteria:
- Transportation service provider
- Forwarding country
- Means of transport
- Automatic freight code determination on the basis of the following criteria:
- Product freight group
- Freight code set
Activities
1. Define freight code sets.

Freight code sets are used for freight code determination.
2. Define freight codes.
Each freight code is defined for a specific freight code set.
______________________________________________________________
SAP AG 196
SAP System
______________________________________________________________
3. Configure the freight code determination process.

To guarantee automatic freight code determination, enter a freight code for a combination
of product freight code and freight code set. You can only specify one freight code that
you have defined for the associated freight code set.
6.2.2.10.5.2 Define Product Freight Groups
Use
In this IMG activity, you define product freight groups.

You assign a transportation service provider to product freight groups in the transportation
service provider profile for the routing guide. You also need product freight groups for EDI
communication.
6.2.2.11 Trailers and Compartments
Use
Activities
levels.
______________________________________________________________
SAP AG 197
SAP System
______________________________________________________________
Use
Requirements
Use
compartments.
Use
______________________________________________________________
SAP AG 198
SAP System
______________________________________________________________
6.2.2.12 Quota Arrangement
Use
In this IMG activity, you can specify whether or not changes made to quota arrangements are
to be logged.
performance.
You can display the the change documents for a quota arrangement via the SAP APO menu
under Master Data -> Quota Arrangement -> Display Change Documents or using
transaction /SAPAPO/TR_CD_QUOTA.
Standard settings
Im the standard system, the logging of changes with change documents is not active for quota
arrangements.
6.2.2.13 Business Add-In (BAdI) for Source Determination
6.2.2.13.1 BAdI: Source Determination
______________________________________________________________
SAP AG 199
SAP System
______________________________________________________________
Title
BAdI: Change Source Determination
Use
This Business Add-In (BAdI) is used in the component Sources of Supply.

It enables you to do the following for the "valid sources of supply" determined by the system:
- Change the sorting
- Change the data for a source
Example
The system is to take the valid sources into account as follows:

- When a procurement order is created in the background, sources with the procurement
priority 3 are not to be taken into account.
- When a procurement order is created in dialog mode, sources with the procurement
priority 3 are to be displayed as additional procurement alternatives.
To achieve this result, proceed as follows:
In mode P (planning in the background), filter out the sources with the procurement priority 3
by deleting such sources from the table CT_SOURCES_EXTEND.
The parameter IV_LOW_LEVEL_CODE within the method PWB_USEX_SOS indicates whether
the BAdI has been called up within the determination of the low-level code. If so, the
parameters IV_MINLS and IV_MAXLS are not filled.
Standard settings
This BAdI is not active in the standard system supplied.

This BAdI can be used multiple times.
Activities
INCLUDE BADI_IMPLEMENTATION OBJECT DOKU ID TX LANGUAGE EN
See also
Methods
Sorting and/or Restriction of Source Selection(PWB_USEX_SOS)
Reading of Source (PWB_USEX_SOS_ORDER_TRPID)
______________________________________________________________
SAP AG 200
SAP System
______________________________________________________________
Interface
/SAPAPO/IF_EX_PWB_SOS
6.2.2.14 Product and Location Interchangeability
6.2.2.14.1 Application Settings
6.2.2.14.1.1 General Settings
Use
In this IMG activity you can activate and deactivate the creation of workflow events and change
documents for the product and location interchangeability master data. Do not change these
settings during operation.
6.2.2.14.1.2 Maintain Attribute Properties for Supersession Chains
Use
In this IMG activity, you define the attributes for a supersession chain on client level. Each
attribute can be maintained for particular applications. This means that you can configure the
same attribute in different ways.
In the view SAP Menu -> Master Data -> Product and Location Interchangeability ->
Interchangeability Group, only active attributes are displayed.
Standard settings
The following attributes are defined in the standard system:
Activities
1. Choose an attribute. Note the application for which this attribute is to be used.
2. If the chosen attribute is necessary for the supersession chain, set the Required indicator.
______________________________________________________________
SAP AG 201
SAP System
______________________________________________________________
3. If the chosen attribute only needs to be displayed, set the Display Only indicator.
4. Choose the corresponding location dependency.
5. If you want to activate the chosen attribute on client level, set the Active indicator.
6.2.2.14.1.3 Maintain Member Types
Use
In this IMG activity you can maintain member types on client level.
The member type is part of the replacement type and determines the objects that an
interchangeability relationship contains. You can also define your own member types based on
the basic types that are supplied.
Standard settings
In the standard system, the following member types are defined:

- Member type 1 = Assembly (Basic type = Assembly)
You can only use this member type for supersession chains.
If you want to assign an Assembly to a supersession chain, the replacement type that you
use must also contain an assembly type object.
- Member type ZK>2 = Group (Basic type = Group)
You can only use this member type for restricted interchangeability for FFF-classes,
product substitution procedures, location product substitution procedures, and location
determination procedures.
If you create an interchangeability group (for example, product substitution procedure), to
which you want to assign other interchangeability groups (for example, supersession
chains), the replacement type that you use must contain a Group type object.
- Member type 3 = Location (Basic type = Location)
You can only use this member type for location substitution chains .
If you want to create a location substitution chain, the replacement type that you use must
also contain a Location type object.
- Member type 4 = Location Product (basic type = Location Product)
You can only use this member type forLocation product substitution chains.
If you want to create a location product substitution chain, the replacement type that you
use must contain a location product type object.
- Member type 5 = Product (basic type = Product)
You can only use this member type for supersession chains, location product substitution
chains, FFF-Classes, and restricted interchangeability for FFF-classes.
If you want to assign a
______________________________________________________________
SAP AG 202
SAP System
______________________________________________________________
productto an interchangeability group, the replacement type that you use must also contain
a Product type object.
- Member type 6 = no member type (Basic type = no Basic Type)
You use this member type if you create a 0:1 or a 1:0 substitution.
Activities
1. Enter the name of the new member type.

2. Assign a suitable basic type to the member type.
3. Enter a description for the newly defined member type.
4. Assign the member type to a replacement type.
Example
You can create the member typeoverhauled product based on the basic type product. You
use this member type to distinguish revised or modified products (which can also be members
of product replacement) from newly manufactured products.
6.2.2.14.1.4 Maintain Replacement Types
Use
In this IMG activity you can maintain replacement types on client level.
The replacement type determines which objects (member types) are used in product or location
substitution and which cardinality exists between the objects.
In addition to the existing replacement types, you can also define your own replacement types.
Requirements
You have defined member types.
Standard settings
The following replacement types are defined in the standard system:

- S_0L1L: 0:1 - Location Substitution
Use this replacement type if a validity date is to be maintained for the predecessor location
in a location substitution chain .
- S_0LP1LP: 0:1 - Location Product Substitution
Use this replacement type if a validity date for thepredecessor location product is to be
maintained in the location product substitution chain.
______________________________________________________________
SAP AG 203
SAP System
______________________________________________________________
- S_1A0A: 1:0 - Assembly Replacement

Use this replacement type if an assembly is discontinued and is not replace by another
assembly (supersession chain).
- S_1A1A: Assembly - Assembly
Use this replacement type if you want to replace one assembly with another (supersession
chain).
- S_1A1P: Assembly - Product
Use this replacement type if you want to replace an assembly with a Product (supersession
chain).
- S_1G1G: Group - Group
Use this replacement type if you want to replace an FFF-Class with another FFF-class
(restricted interchangeability for FFF-classes).
- S_1G1P: Group - Product
Use this replacement type if you want to replace an FFF-class with a product (restricted
interchangeability for FFF-classes).
- S_1L1L: Location - Location
Use this replacement type if you want to replace a location with another location (location
substitution chain).
- S_1LP1LP: Location Product - Location Product
Use this replacement type if you want to replace a location product with another location
product (location product substitution chain).
- S_1P0P: 1:0 - Product Substitution
Use this replacement type when a product is discontinued and will not be replaced by
another product (supersession chain).
- S_1P1A: Product - Assembly
Use this replacement type if you want to replace a product with an assembly (supersession
chain).
- S_1P1G: Product - Group
Use this replacement type if you want to replace a product with an FFF-class (restricted
interchangeability for FFF-classes).
- S_1P1P: Product - Product
Use this replacement type if you want to replace a product with another product
(supersession chain).
- S_1PNP: 1:n - Product Substitution
Use this replacement type if you want to replace a product with a number of other
products (supersession chain).
- S_FFF: FFF-Class with Products
Use this replacement type if you want to create an FFF-class.
- S_LOCLST: Location List
Use this replacement type if you want to create a list of locations.
- S_NP1P: n:1 - Product Substitution
Use this replacement type if you want to replace a number of products with one product
______________________________________________________________
SAP AG 204
SAP System
______________________________________________________________
(supersession chain).
- S_NPNP: n:m - Product Substitution
Use this replacement type if you want to replace a number of products with a number of
other products (supersession chain).
- S_PSP: Substitution Procedure
Use this replacement type if you want to create a product substitution procedure,a location
product substitution procedure or a location determination procedure.
Activities
1. Enter the name, counter, and description of the new replacement type.
2. Select the corresponding relationship type.
3. Define the member types and their cardinalities.
4. If you want to activate the replacement type, set the indicator Active.
5. Assign the replacement type to an interchangeability group.
6.2.2.14.1.5 Maintain Interchangeability Group Types and Assign

Replacement Types
Use
In this IMG activity, you define the properties of the interchangeability group types on client
level. A number of replacement types can be assigned to each interchangeability group type. In
the view SAP Menu -> Master Data -> Product and Location Interchangeability ->
Interchangeability Group, only active interchangeability group types are shown.
Requirements
You can only assign the replacement types that you have defined in the IMG activity Maintain
Replacement Types.
Activities
1. Choose an interchangeability group type.

2. If you want to activate the interchangeability groups type, set the Active indicator.
3. If you want the interchangeability group type to appear as a proposal, set the Proposal
indicator.
4. Assign the corresponding replacement type to the interchangeability group type.
______________________________________________________________
SAP AG 205
SAP System
______________________________________________________________
6.2.2.14.1.6 Maintain Graphic Profile
Use
In this IMG activity, you can activate a graphics profile on client level and then use it in the
view SAP Menu -> Master Data -> Product and Location Interchangeability ->
Interchangeability Group.
Requirements
You have already defined a graphic profile .
6.2.2.14.2 Maintain Number Range for Groups
Use
In this IMG activity you define the type of number assignment and the number range interval
for interchangeability groups. When creating an interchangeability group, you must assign it a
unique number. The following options are available for this:
- internal number assignment
The SAP system assigns a number that lies within the allowed number range interval to the
group.
- external number assignment
You assign a number that lies within the allowed number range interval to the group. In
external number assignment, you can define numeric and alphanumeric intervals.
After you have defined a number range interval for a group, you assign an interchangeability
group type to it.
If you only assign one interchangeability group type to a group, then for this group type you
can define both an internal and an external number range interval.
You can however also combine a number of group types and define internal and external
number range intervals for the groups, if you want many interchangeability group types to have
the same number range intervals.
______________________________________________________________
SAP AG 206
SAP System
______________________________________________________________
Activities
1. Assign an interchangeability group type to each group. The following interchangeability

group types are available:
a) 1: Supersession Chain
b) 2: FFF-Class
c) 3: Restricted Interchangeability for FFF-Classes
d) 4: FFF-Subset
e) 5: Product Substitution Procedure
f) 6: Location Substitution Chain
g) 7: Location List
h) 8: Location Product Substitution Chain
i) 9: Location Determination Procedure
j) 10: Location Product Substitution Procedure
2. Define the number range interval for all groups.
Example
Group: Interchangeability subset

Group type: FFF-Subset
Number range 01, Number range interval 100.000-999.999, internal assignment
6.2.2.14.3 Maintain Reason Code
Use
In this IMG activity you define the reason code that states why products are replaced.
You can only use the reason codes with supersession chains, location product substitution chains
and with restricted interchangeability for FFF-Classes.
Activities
- Select a group type.

- Enter a reason code.
______________________________________________________________
SAP AG 207
SAP System
______________________________________________________________
For supersession chains and location product substitution chains the reason code must be no
longer than four characters. For restricted interchangeability for FFF-classes the reason
code must be no longer than two characters.
- Enter a description that explains why this product replacement has occurred.
6.2.2.14.4 Consistency Checks
6.2.2.14.4.1 Maintain Field Catalog
Use
In this Customizing activity, you maintain field catalog entries The field catalog includes the
fields that can be chosen for comparison during the execution of consistency checks. A few
properties of products might be required to be equal, so that they can belong to a same
interchangeability group. You add the relevant fields to compare in the field catalog. As part
of the consistency check, the system makes sure that all the products in the interchangeability
group have the same value for the fields that have been included in the field catalog.
Examples for such properties of a product could be Procurement type, Unit of Measure, Shelf
Life.
Activities
- Enter the name of the Field Catalog and Description.

- Select the field catalog that you have entered and double click on Maintain field catalog.
- In the field catalog, you can choose the fields that you want for the catalog, the list of
available fields can be seen with F4 help.
- Save your entries.
6.2.2.14.4.2 Maintain Validation
Use
______________________________________________________________
SAP AG 208
SAP System
______________________________________________________________
In this Customizing activity you maintain the validations to be carried out when you create
different types of interchangeability groups. There are some standard validations delivered with
the application. You can deactivate these validations if, you do not want them to take place.
To create new validations you must define the validation in this activity. The validation must
start with Y or Z. Ensure that it is active. In order to implement these validations you need
to use the BAdI Consistency Checks (/INCMD/CONSIST_CHK).
Standard settings
There are a few validations which are delivered with the standard application. You can specify
in customizing whether the output for these is displayed as error message or warning.
S_V1: When you create or modify an interchangeability group, the system checks the equality
of the present fields in the particular attached field catalog. It is essential to maintain a field
catalog and also attach field catalog to interchangeability group types.
S_V2: When you create or modify an interchangeability group, the system checks whether any
of the products or product combinations of that group are already contained in other
interchangeability groups of the same group type.
of the products or product combinations are already contained in that particular
interchangeability group itself.
S_V4: When you create or modify an interchangeability group, the system checks whether one
of the following combinations is already contained in other interchangeability groups of the same
group type:
- Product and location
- Product combination and location
This check is not valid for FFF classes and restricted interchangeability for FFF classes.
S_V5: When you create or modify a FFF subset for a FFF class, the system checks whether
there is another FFF subset in the same location for that FFF class.
This check is valid only for FFF subsets.
S_V6: When you create or modify a supersession chain that contains an assembly, the system
checks whether any of the components of that assembly are already contained in this
supersession chain.
This check is valid only for supersession chains.
S_V7: When you create or modify a planning-relevant interchangeability group, the system
checks whether any of the products or product combinations of that group are already contained
in other planning-relevant interchangeability groups of the same group type.
S_V8: When you create or modify an ATP-relevant interchangeability group, the system checks
whether any of the products or product combinations of that group are already contained in
other ATP-relevant interchangeability groups of the same group type.
checks whether one of the following combinations is already contained in other planning-relevant
interchangeability groups of the same group type:
______________________________________________________________
SAP AG 209
SAP System
______________________________________________________________

whether one of the following combinations is already contained in other ATP-relevant
S_V11: When you create or modify a product substitution procedure (PSP), the system checks
whether any of the associated subgroups are already contained in other interchangeability groups
of the same group type.
This check is relevant only for PSP.
S_V12: When you create or modify a planning-relevant PSP, the system checks whether any of
the associated planning-relevant subgroups are already contained in other planning-relevant
S_V13: When you create or modify an ATP-relevant PSP, the system checks whether any of
the associated ATP-relevant subgroups are already contained in other ATP-relevant
of the products or product combination components are already contained in other
checks whether any of the products or product combination components are already contained in
other planning-relevant interchangeability groups of the same group type.
whether any of the products or product combination components are already contained in other
ATP-relevant interchangeability groups of the same group type.
S_V17: When you create or modify an interchangeability group, the system checks whether one
of the following combinations is already contained in other interchangeability groups of the same
group type:
- Product combination components and location
checks whether one of the following combinations is already contained in other planning-relevant
______________________________________________________________
SAP AG 210
SAP System
______________________________________________________________

whether one of the following combinations is already contained in other ATP-relevant
S_V20: When you create or modify a supersession chain that contains a product combination,
the system checks whether the product combination is replaced by any of its own components.
This check is valid only for supersession chains.
S_V21: When you create or modify an interchangeability group that contains subgroups, the
system checks whether any product or product combination of a subgroup is already contained
in another subgroup of the same main group.
This check is valid only for PSP and restricted interchangeability for FFF classes.
S_V22: When you create a supersession chain, the system checks if the products used are
already part of an FFF class. If yes, the system will not allow you to create the supersession
chain.
Similarly, when you create an FFF class, the system checks if the products used are already
part of a supersession chain. If yes, the system will not allow you to create the FFF class.
S_V23: When you create or modify an FFF subset for an FFF class, the system checks
whether the leading product is the same as the leading products of the other subsets.
This check is valid only for FFF subsets.
checks whether any of the products of that group is creating a loop with other released
planning-relevant interchangeability groups of the same group type (supersession chain).
In the following example, the chains 1, 2, and 3 form the chain A->B->C->A, where
product A creates a loop by being its own predecessor and successor at the same time.
Predecessor Successor
Chain 1 Product A Product B
Chain 2 Product B Product C
Chain 3 Product C Product A
Activities
- To make any validations active select the checkbox with active status.
- To deactivate the validation uncheck the active status checkbox.
- Save the changes
______________________________________________________________
SAP AG 211
SAP System
______________________________________________________________
6.2.2.14.4.3 Maintain Consistency Profiles and Assign Validation
Use
In this activity you maintain the consistency profiles and assign validations to them. Consistency
profiles make sure that the data entered while creating an interchangeability group is consistent.
When you create a profile you can specify which validations failure is classified as error or
warning
Requirements
Activities
- Enter the name for your consistency profile and a brief description
- Select the consistency profile that you have entered and choose the subfolder Maintain
Validations for Consistency Profile
- View and select the validations you would like for the consistency profile using F4 help
and classify it as an error or warning
- Save your changes
Example
Consistency Profile S1: Profile for chains
S_V1 (validation for Field Checks) and S_V2 (Product in Multiple Groups) for example are the
validations assigned to the profile. You can categorize, in case of consistency profile S1, that
S_V1 is an error and S_V2 is a warning.
6.2.2.14.4.4 Assign Consistency Profiles and Field Catalog to Group Type
Use
For each group type you can specify which set of validations will be carried out and which
fields will be compared during the execution of the consistency check.
______________________________________________________________
SAP AG 212
SAP System
______________________________________________________________
Activities
- Enter the group type (Interchangeability type)

- Assign the consistency profile that you have created for this group type
- Using F4 help, select the field catalog for the group type
- Save the changes
6.2.2.14.5 Business Add-Ins (BAdIs) for Product and Location

Interchangeability
6.2.2.14.5.1 BAdI: Consistency Checks
Use
You use this BAdI for the following Scenarios:

1. You are in need of additional consistency checks apart from those delivered by SAP
2. You need to override the delivered checks.
You can use the GROUP_CONSISTENCY_CHECK method to add optional or Customizing
checks and to change these checks.
You can use the GROUP_MANDATORY_CHECK method to carry out the mandatory checks
that need to be done for creating any interchangeability group. You can create an
interchangeability group only if these checks are successful.
For example, a check would make it mandatory for you to specify the description of that
group in order to create the interchangeability group.
Another example of mandatory check is while creating a supersession chain, if you assign a
location to the chain then all the members of the chain should be assigned to that particular
location.
Standard settings
- This BAdI is not active in the standard system.

- This BAdI is not filter-dependent.
- This BAdI cannot be used more than once.
______________________________________________________________
SAP AG 213
SAP System
______________________________________________________________
Further notes
Documentation on GROUP_CONSISTENCY Method
You can also call the documentation on BAdI methods from the menu. Take the following
steps:
3. Choose tab page Interface.
4. Double-click on the corresponding method.
5. Click the right-hand mouse button and choose Documentation on component.
6.2.2.14.5.2 BAdI: Interface Enhancements
Use
You use this BAdI to add additional fields to the maintenance screen for interchangeability
groups.
The following methods are available:
- EXTEND_CHAIN_ITEM_ALV
Use this method to extend the Group Details screen section for supersession chains.
- EXTEND_CHAIN_LOC_ALV
Use this method to extend the Location tab page for supersssion chains.
- EXTEND_RESFFF_ALV
Use this method to extend the Group Details screen section for interchangeability group
type restricted interchangeability for FFF classes.
- EXTEND_FFF_ALV
Use this method to extend the Group Details screen section for FFF classes.
- EXTEND_FFFS_ALV
Use this method to extend the FFF Subset Members tab page.
- EXTEND_FFFSL_ALV
Use this method to extend the FFF Subset List Screen.
- EXTEND_PSP_ITEM_ALV
type product substitution procedure.
______________________________________________________________
SAP AG 214
SAP System
______________________________________________________________
- EXTEND_LOC_CHAIN_ITEM_ALV
type location substitution chain.
- EXTEND_LP_CHAIN_ITEM_ALV
type location product substitution chain.
- EXTEND_LOC_LIST_ITEM_ALV
type location list.
- EXTEND_LDP_ITEM_ALV
type location determination procedure.
- EXTEND_LPSP_ITEM_ALV
type location product substitution procedure.
6.2.2.14.5.3 BAdI: Master Data Maintenance for Product and Location

Interchangeability
Use
You use this BAdI to maintain interchangeability master data related details in your own
customer tables.
- MAINT_FCODE_HANDLE
Use this method to add more pushbuttons with function codes to the GUI status. Eight
function codes are available for customer enhancements to GUI Status.
- MAINT_GROUP_CREATE
Use this method to create further data when creating an interchangeability group.
- MAINT_GROUP_DELETE
This method is used in conjunction with the previous method. You use it to delete other
data when deleting an interchangeability group.
- MAINT_INTIAL_PREPARE
______________________________________________________________
SAP AG 215
SAP System
______________________________________________________________
Use this method to back up data of customer-related tables. This method is called initially
to back up these tables for future restoration in case of errors.
- MAINT_CLEANUP_ON_ERROR
Use this method to restore data in case of error. This method should be used in
conjunction with the MAINT_INITIAL_PREPARE method to ensure data consistency should
errors occur. The method is called if an error occurs when changing interchangeability
master data.
6.2.2.14.5.4 BAdI: Rule Resolution
Use
Conditional interchangeability between members of an interchangeabilty group requires that a

condition be satisfied/fulfilled for interchangeability to take place.
For example, product A can be replaced with product B if condition 1 is satisfied.
Product A can be replaced with product C, if condition 2 is satisfied.
- Condition 1 # Operating temperature > 100 degree Celsius.
- Condition 2 # Operating temperature < 100 degree Celsius.
When you have a condition like this, you need to evaluate it and thus decide which product
should be used.
You use this BAdI to program the logic, which you would like to use for resolving the rules.
Based upon this logic, the system decides which successor product should be used.
This is relevant for group types supersession chain and restricted interchangeability for FFF
classes.
The methods are:
- INC_RULE_RESOLVE
Resolves rules that may be attached at the relation level between the products of an
interchangeability group.
- INC_GROUP_RULES_RESOLVE
Used to resolve the group after evaluating the rules at the relation level. This method
decides which interchangeability group should be used after the conditions/rules are
evaluated at the relation level.
The sample code is delivered by SAP for this method.
______________________________________________________________
SAP AG 216
SAP System
______________________________________________________________
6.2.2.14.5.5 BAdI: Group Filter
Use
You use this BAdI to filter interchangeability groups based on specific filtering criteria. This is
used in the external services query where the filtering criteria of the output is passed as a
parameter.
You can define such filters and specify the logic programmatically so that you filter out the
results based on the parameter specified.
The following method is available:
MAINT_GROUP_FILTER
6.2.2.14.5.6 BAdI: XML Upload of Interchangeability Groups
Use
You use this BAdI to change the data in the interchangeability data structures before it is
transferred to the interchangeability master data services.
The following method is available:
CHANGE_UPLOAD_DATA
This method contains tables with interchangeability header data, header text data, item data,
additional information data, product combination data, location data, model assignment data and
the XML data in raw format as changing parameters. Customer can change the data for
further manipulation before transferring the data to the interchangeability master data services.
______________________________________________________________
SAP AG 217
SAP System
______________________________________________________________
Requirements
You can use this BAdI only when the data has been uploaded in XML format, either using an
online or batch program. The XML data must be correctly formatted and must adhere to the
standard schema that is shipped along with the interchangeability services.
6.2.2.14.5.7 BAdI: External Customer Enhancements
Use
You use this BAdI to maintain the data in the interchangeability data structures before it is
transferred to the interchangeability master data services.
- BAPI_GROUP_MAINT_EXT
This method imports BAPI parameter, change parameter and the internal parameter as
changing parameters. All data from the BAPI structures and tables is mapped to the
corresponding fields in the internal structures and tables. Before transferring the internal
parameters to the interchangeability master data services the customer can change the data
in the internal parameters by using the EXTENSION_IN parameter, theEXTENSION_OUT
parameter and change parameters for further manipulation.
- BAPI_GROUP_READ_EXTIN
This method imports selection tables and extension parameters as changing parameters.
The customer can change the selection criteria by using the EXTENSION_IN parameter to
get the groups that satisfy the given criteria.
- BAPI_GROUP_READ_EXTOUT
This method imports BAPI parameter and the internal parameter as changing parameters.
All data from the internal structures and tables is mapped to the corresponding fields in the
BAPI structures and tables. Before transferring the BAPI parameters to the called services
the customer can change the data in the BAPI parameters by using the EXTENSION_IN
and the EXTENSION_OUT parameter for further manipulation.
- BAPI_GROUP_DELETE_EXT
Use this method only if you want to perform some actions before deleting the
interchangeability group. This method contains GROUP_NUMBER tables, the
EXTENSION_IN and the EXTENSION_OUT parameter as changing parameters. Customer
can perform checks by using the EXTENSION_IN parameter before deleting the
interchangeability group.
Note:
The logical system identifies the sending system (client), from which the request originates. It is
______________________________________________________________
SAP AG 218
SAP System
______________________________________________________________
a logical system for Application Link Enabling (ALE). You can maintain the logical system in
Customizing for ALE.
6.2.2.15 Hierarchy
6.2.2.15.1 Define Hierarchy Structure
In this step , you define hierarchy structures. You can define hierarchy structures, extended
hierarchy structures, generated hierarchy structures, and schema hierarchy structures.
Hierarchy structures, extended hierarchy structures, and schema hierarchy structures are
independent, whereas generated hierarchy structures are based on other hierarchy structures
(generated or independent).
In principle, hierarchy structures, extended hierarchy structures, and schema hierarchy structures
are similar, but they are maintained differently. Hierarchy structures are independent, schema
hierarchy structures are maintained with reference to an object, and generated hierarchy
structures are based on a hierarchy or schema hierarchy structure.
Hierarchy structures are a prerequisite for defining hierarchies in the Master Data menu.
Standard settings
Values available for the definition of a hierarchy structure:
- Object type: Product, location, location product, resource, production process model.
- Hierarchy structure category: Hierarchy, extended hierarchy, generated hierarchy, schema
hierarchy.
- Table:
- /SAPAPO/RELDHBOD (Edges in Location Hierarchies for BODs)
- /SAPAPO/RELDHLOC (Edges in Location Hierarchies)
- /SAPAPO/RELDHMAT (Edges in Product Hierarchies)
- /SAPAPO/RELDHMKA (Edges in Product Hierarchies for Aggr. Planning)
- /SAPAPO/RELDHML (Edges in Location Product Hierarchy)
- /SAPAPO/RELDHMLA (Edges in Location Product Hierarchy for Aggr. Planning)
- /SAPAPO/RELDHPDS (Edges in PDS Hierarchies)
- /SAPAPO/RELDHPPM (Edges in PPM Hierachies)
- /SAPAPO/RELDHRES (Edges in Resource Hierarchies)
______________________________________________________________
SAP AG 219
SAP System
______________________________________________________________
- /SAPAPO/RELDHRGP (Edges in Location Hierarchies)

- /SAPAPO/RELDHZON (Edges in transportation zone hierarchies)
- /SAPAPO/RELEHLOC (Edges in Extended Location Hierarchies)
- /SAPAPO/RELEHMAT (Edges in Extended Product Hierarchies)
- /SAPAPO/RELEHML (Edges in Extended Location Product Hierarchies)
- /SAPAPO/RELEHPDS (Edges in Extended PDS Hierarchies)
- /SAPAPO/RELEHPPM (Edges in Extended PPM Hierarchies)
- /SAPAPO/RELEHRES (Edges in Extended Resource Hierarchies)
- /SAPAPO/RELEHZON (Edges in extended transportation hierarchies)
- /SAPAPO/RELGHML (Edges in Generated Location Product Hierarchy)
Activities
The initial screen for maintaining hierarchy structures is divided into two areas. The area on the
left shows a tree structure in which you select the part of the structure you wish to maintain,
while the area on the right consists of a table containing all the structures you have maintained,
and in which each line represents a structure. You can change existing structures in or add new
ones to this table.
Definition of Hierarchy Structures and Extended Hierarchy Structures:
- Define the object and hierarchy structure category and the name of the table for the node
relationships of the hierarchy structure. Select the initial node Hierarchy Structures in the
tree structure and choose New Entries to define a new structure. The New Entries:
Details of Added Entries screen appears.
- Maintain an ID, a text, and a name for this structure. You then see the maintained
texts in the overview of hierarchy structures
- Choose the object type and the hierarchy structure category using the input help.
- Enter an edge table name as described above under Standard Settings. You can
also assign your own names.
- Define the levels of the hierarchy structure. Select the structure in the right-hand area of
the screen and select Hierarchy Structure Level Definition in the tree structure. Choose
New Entries to maintain a level ID.
- Choose a hierarchy structure ID for which you want to maintain the level using the
input help
- Maintain a numeric level ID
- Maintain a level number to define the sequence of levels in the hierarchy
Via Change, you can maintain the structure subsequently. The ID of the hierarchy structure is
retained as a unique key.
Definition of Generated Hierarchy Structures:
To define these structures, follow the same procedure as for hierarchy structures. Perform the
______________________________________________________________
SAP AG 220
SAP System
______________________________________________________________
following additional steps:

- Define the hierarchies on which the structure is to be based. Select the structure in the
table in the right-hand area of the screen and choose Definition for Generated Hierarchy
Structure in the tree structure. Choose New Entries to maintain the underlying
hierarchies and define the position of the hierarchies.
- Assign the levels of the hierarchies involved to the levels of the generated hierarchy
structure. Choose Level Assignment for Generated Hierarchy Structure and then New
Entries. The following rules apply:
- A generated hierarchy structure must use one level from each hierarchy structure
involved (combination of levels).
- A combination of levels must not be duplicated.
- A combination must not contain a level that represents an overlap in comparison with
another combination. Relationships must only run in one direction.
Example:
Generated hierarchy structure for location products. A product hierarchy is combined with a
location hierarchy in each case.
Product hierarchy: Product group (A); product (B)

Location hierarchy: Country (1); region (2); city (3)
Possible correct definitions:

A/1(I); B/2(II); B/3(III) or
A/1(I); A/2(II); A/3(III); B/3(IV).
Incorrect definitions:
A/3(I); B/2(II) or
B/2(I); A/3(II) or
B/2(I); A/1(II); B/3(III).
Definition of Schema Hierarchies:
Proceed in the same way as for defining hierarchy structures and perform the following
additional steps:
- Select a schema hierarchy structure in the hierarchy structure overview and choose
Definition for Schema Hierarchy Structures from the tree structure. The Change View
"Definition for Schema Hierarchy": Overview screen appears.
- Choose New Entries, and enter the ID of the hierarchy structure in the table on the right
of the screen.
- In the Code Field column, enter the basis of the hierarchy schema (for example, the field
names of the freely definable master data attributes). If the hierarchy is intended to be
used in this way, you should create a unique index. This not only assigns a unique name
to the field, but also enables you to find data more quickly.
Hierarchy Structures - Schema Hierarchy Structures:
You should note the difference between these two structure types when assigning level numbers.
______________________________________________________________
SAP AG 221
SAP System
______________________________________________________________
Level number for hierarchy structures: The levels are called up in numerical order. The
number itself has an order function.
Level number for schema hierarchy structures: The level number likewise reflects the order.
The number additionally stands for the number of characters defining the object of the level:
Level number No. of characters Object
Level 1: 3 3 characters AAA
Level 2: 5 5 characters AAA BB
Level 3: 9 9 characters AAA BB CCCC
Note that the characters of the object of the upper level must be repeated at a subordinate
level, so that the assignment can be recognized. If the designation for objects of level 2 were
AA1 BB, assignment to a superordinate level could not take place here.
In contrast to the hierarchy structure, the number here is not just an element of order but a
meaning carrier.
6.2.2.15.2 BAdI: BOD Product Assignment
Use
This Business Add-In (BAdI) is used in the SCM Basis (SCM-BAS) component. You use this
Business Add-In (BAdI) to manipulate the assignment of products to bills of distribution
(BODs).
Standard settings
Activities
______________________________________________________________
SAP AG 222
SAP System
______________________________________________________________
6.2.2.16 Specify Person Responsible (Planner)
In this step you assign planning priveleges to planners. You must select each application for
which each planner is responsible.
Activities
1. Choose New Entries.

2. Enter an identifier and description for each planner.
3. Select each area for which you want the planner to have priveleges.
4. Choose Save.
6.2.2.17 Define Incoterms
Use
In this IMG activity, you define Incoterms.
Activities
1. Specify an alphanumeric key of up to 3 figures and a description for the incoterms.

2. If entering a location in the master data is to be compulsory, you must set the
corresponding indicator and also enter the incoterm location during master data
maintenance.
6.2.2.18 Enterprise Services
6.2.2.18.1 Assign Code to Planner
Use
In this IMG activity, you assign a code to a planner. The code is used to identify the planner
in the Global Data Type (GDT) DemandPlannerGroupCode for SAP SCM Enterprise Services.
______________________________________________________________
SAP AG 223
SAP System
______________________________________________________________
Requirements
You have already set up planners in Customizing, by choosing SCM Basis -> Master Data
-> Specify Person Responsible (Planner).
Activities
Enter an existing planner and assign a code. You have to use a different code for each planner.
6.2.2.18.2 Assign Code to Product Group
Use
In this IMG activity, you assign a code to a product group. The code is used to identify the
product group in the Global Data Type (GDT) ServicePartPlanningProductGroupCode for
SAP SCM Enterprise Services.
Requirements
You have already set up product groups in Customizing, by choosing SCM Basis -> Master
Data -> Product -> Product Groups -> Define Product Groups.
Activities
Enter an existing product group and assign a code. You have to use a different code for each
product group.
6.2.2.18.3 Business Add-Ins (BAdIs)
6.2.2.18.3.1 Location Data Management
6.2.2.18.3.1.1 Location and Bill of Distribution
6.2.2.18.3.1.1.1 Note on Implementation
______________________________________________________________
SAP AG 224
SAP System
______________________________________________________________
Use
spot /SCMB/BIF_LDM_LOC.
6.2.2.18.3.1.1.2 BAdI for

LocationSimpleByIDAndTypeCodeAndDescriptionQueryResponse
Use
This Business Add-In (BAdI) is used in the SCM-APO-MD component. You can use this BAdI
to change or extend the data transferred through the message interface
LocationSimpleByIDAndTypeCodeAndDescriptionQueryResponse_In that is part of the
process component Location Data Management.
Requirements

Standard settings
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_LOC002QR interface. For more

information, see the Enterprise Service Workplace in the SAP Developer's Network (SDN) at
sdn.sap.com -> Enterprise SOA -> ES Workplace -> Browse service definitions ->
Enterprise Services Index
______________________________________________________________
SAP AG 225
SAP System
______________________________________________________________
6.2.2.18.3.1.1.3 BAdI for LocationCreateRequestConfirmation
Use
LocationCreateRequestConfirmation_In that is part of the process component Location Data
Management.
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_LOCCRTRC interface. For more

Enterprise Services Index.
6.2.2.18.3.1.1.4 BAdI for LocationChangeRequestConfirmation
Use
LocationChangeRequestConfirmation_In that is part of the process component Location Data
Management.
______________________________________________________________
SAP AG 226
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_LOCCHGRC interface. For more

6.2.2.18.3.1.1.5 BAdI for LocationByIDQueryResponse
Use
LocationByIDQueryResponse_In that is part of the process component Location Data
Management.
Standard settings

Activities
______________________________________________________________
SAP AG 227
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_LOC001QR interface. For more

6.2.2.18.3.1.1.6 BAdI for LocationDeactivateRequestConfirmation
Use
LocationDeactivateRequestConfirmation_In that is part of the process component Location
Data Management.
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_LOCCNCRC interface. For more

______________________________________________________________
SAP AG 228
SAP System
______________________________________________________________
6.2.2.18.3.1.1.7 BAdI for LocationByIDAndTypeCodeQuery
Use
This Business Add-in (BAdI) is used in the Master Data (SCM-APO-MD) component. You can
use this BAdI to change or extend the data transferred through the message interface
LocationByIDAndTypeCodeAndDescriptionQuery_In.
Standard settings

Activities
See Also
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_LOC003QU interface. For more

information, see the Enterprise Services Workplace in the SAP Developer's Network (SDN) at
sdn.sap.com -> Enterprise SOA.
6.2.2.18.3.1.1.8 BAdI for BillOfDistributionByIDQueryResponse
Use
BillOfDistributionByIDQueryResponse_In that is part of the process component Location Data
Management.
______________________________________________________________
SAP AG 229
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_BOD001QR interface. For more

6.2.2.18.3.1.1.9 BAdI for LocationSimpleByIDAndRadiusQueryResponse
Use
LocationSCMSimpleByIDAndRadiusQueryResponse_In that is part of the process component
Location Data Management.
Standard settings

Activities
______________________________________________________________
SAP AG 230
SAP System
______________________________________________________________
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_LDM_LOC004QR. For more

6.2.2.18.3.1.1.10 BAdI for

LocationSCMSimpleByIdentifyingElementsQueryResponse
Use
This Business Add-In (BAdI) is used in the Master Data (SCM-BAS-MD) component. You can
LocationSCMSimpleByIdentifyingElementsQueryResponse.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCMB/IF_EX_BIF_LDM_LOC005QR. For more
______________________________________________________________
SAP AG 231
SAP System
______________________________________________________________
6.2.2.18.3.1.2 Supply Planning Area
Use
spot /SCMB/BIF_LDM_SPA.
6.2.2.18.3.1.2.2 BAdI for SupplyPlanningAreaCreateRequest/Confirmation
Use
SupplyPlanningAreaCreateRequestConfirmation_In that is part of the process component
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_SPACRTRC interface. For more
______________________________________________________________
SAP AG 232
SAP System
______________________________________________________________
6.2.2.18.3.1.2.3 BAdI for SupplyPlanningAreaChangeRequest/Confirmation
Use
SupplyPlanningAreaChangeRequestConfirmation_In that is part of the process component
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_SPACHGRC interface. For more

______________________________________________________________
SAP AG 233
SAP System
______________________________________________________________
6.2.2.18.3.1.2.4 BAdI for SupplyPlanningAreaByLocationIDQuery/Response
Use
SupplyPlanningAreaByLocationIDQueryResponse_In that is part of the process component
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_SPA001QR interface. For more

6.2.2.18.3.1.2.5 BAdI for SupplyPlanningAreaDeactivateRequest/Confirmation
Use
SupplyPlanningAreaDeactivateRequestConfirmation_In that is part of the process component
______________________________________________________________
SAP AG 234
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_SPACNCRC interface. For more

6.2.2.18.3.1.2.6 BAdI for

SupplyPlanningAreaByLocationIDAndLocationTypeCodeQuery
Use
SupplyPlanningAreaByLocationIDAndLocationTypeCodeQuery_In.
Standard settings

Activities
______________________________________________________________
SAP AG 235
SAP System
______________________________________________________________
See Also
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_SPA002QU interface. For more

6.2.2.18.3.1.2.7 BAdI for

SupplyPlanningAreaSCMSimpleByLocationQueryResponse
Use
SupplyPlanningAreaSCMSimpleByLocationQueryResponse that is part of the process component
Standard settings

Activities
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_LDM_SPA003QR. For more

sdn.sap.com -> Service-Oriented Architecture -> Explore Enterprise Services -> ES Workplace.
______________________________________________________________
SAP AG 236
SAP System
______________________________________________________________
6.2.2.18.3.1.3 Transportation Lane
Use
spot /SCMB/BIF_LDM_TRL.
6.2.2.18.3.1.3.2 BAdI for

TransportationLaneSimpleByElementsQuery/Response
Use
TransportationLaneSimpleByElementsQueryResponse_In that is part of the process
component Location Data Management.
Standard settings

Activities
______________________________________________________________
SAP AG 237
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_TRL002QR interface. For more

6.2.2.18.3.1.3.3 BAdI for

TransportationLaneByTransportationLaneQuery/Response
Use
TransportationLaneByTransportationLaneQueryResponse_In that is part of the process
Standard settings

Activities
See also:

______________________________________________________________
SAP AG 238
SAP System
______________________________________________________________
6.2.2.18.3.1.3.4 BAdI for

TransportationLaneSCMByIdentifyingElementsQueryResp
Use
TransportationLaneSCMByIdentifyingElementsQueryResponse_In that is part of the process
Standard settings

Activities
Example
See also

sdn.sap.com -> Service-Oriented Architecture -> Explore Enterprise Services -> ES Workplace
-> Open the ES Workplace -> Enterprise Services Index.
6.2.2.18.3.1.3.5 BAdI for

TransportationLaneSCMCancelRequestConfirmation_In
Use
______________________________________________________________
SAP AG 239
SAP System
______________________________________________________________
TransportationLaneSCMCreateRequest/Confirmation that is part of the process component
Standard settings

Activities
Example
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_LDM_TRL004RC. For more

6.2.2.18.3.1.3.6 BAdI for

TransportationLaneSCMChangeRequestConfirmation_In
Use
TransportationLaneSCMChangeRequestConfirmation_In that is part of the process component
Standard settings
______________________________________________________________
SAP AG 240
SAP System
______________________________________________________________

Activities
Example
See also
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_TRL008RC interface. For more

sdn.sap.com -> Service-Oriented Architecture -> Explore Enterprise Services -> ES Workplace
-> Open the ES Workplace -> Enterprise Services Index.
6.2.2.18.3.1.3.7 BAdI for

TransportationLaneSCMConsistencyCheckQueryResponse_In
Use
TransportationLaneSCMConsistencyCheckQueryResponse_In that is part of the process component
Standard settings

Activities
______________________________________________________________
SAP AG 241
SAP System
______________________________________________________________
Example
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_LDM_TRL009QR. For more

6.2.2.18.3.1.3.8 BAdI for

TransportationLaneSCMCreateCheckQueryResponse_In
Use
TransportationLaneSCMCreateCheckQueryResponse_In that is part of the process component
Standard settings

Activities
Example
See also

______________________________________________________________
SAP AG 242
SAP System
______________________________________________________________
6.2.2.18.3.1.3.9 BAdI for

TransportationLaneSCMCreateRequestConfirmation_In
Use
TransportationLaneSCMCreateRequest/Confirmation that is part of the process component
Standard settings

Activities
Example
See also

6.2.2.18.3.1.3.10 BAdI for
______________________________________________________________
SAP AG 243
SAP System
______________________________________________________________
TransportationLaneSCMValidMaterialChangeRequestConfirmation_In
Use
TransportationLaneSCMValidMaterialChangeRequestConfirmation_In that is part of the process
Standard settings

Activities
Example
See also

6.2.2.18.3.1.3.11 BAdI for

TransportationLaneSCMValidTransportMeansChangeRequestConfirmation
Use
TransportationLaneSCMValidTransportMeansChangeRequestConfirmation_In that is part of the
process component Location Data Management.
______________________________________________________________
SAP AG 244
SAP System
______________________________________________________________
Standard settings

Activities
Example
See also

6.2.2.18.3.2 Product Data Maintenance
6.2.2.18.3.2.1 Material
Use
spot /SCMB/BIF_PDM_PRD.
______________________________________________________________
SAP AG 245
SAP System
______________________________________________________________
6.2.2.18.3.2.1.2 BAdI for MaterialSimpleByIDAndDescriptionQuery/Response
Use
MaterialSimpleByIDAndDescriptionQueryResponse_In that is part of the process component
Product Data Management.
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRD002QR interface. For more

6.2.2.18.3.2.1.3 BAdI for

MaterialSCMSimpleByIdentifyingElementsQueryResponse
Use
This Business Add-In (BAdI) is used in the Master Data (SCM-APO-MD) component. You can
______________________________________________________________
SAP AG 246
SAP System
______________________________________________________________
MaterialSCMSimpleByIdentifyingElementsQueryResponse.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCMB/IF_EX_BIF_PDM_PRD007QR. For more

6.2.2.18.3.2.1.4 BAdI for MaterialBasicDataCreateRequest/Confirmation
Use
MaterialBasicDataCreateRequestConfirmation_In that is part of the process component
Standard settings

Activities
______________________________________________________________
SAP AG 247
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRDCRTRC interface. For more

6.2.2.18.3.2.1.5 BAdI for MaterialBasicDataChangeRequest/Confirmation
Use
MaterialBasicDataChangeRequestConfirmation_In that is part of the process component
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRDCHGRC interface. For more

______________________________________________________________
SAP AG 248
SAP System
______________________________________________________________
6.2.2.18.3.2.1.6 BAdI for MaterialBasicDataByIDQuery/Response
Use
MaterialBasicDataByIDQueryResponse_In that is part of the process component Product Data
Management.
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRD001QR interface. For more

6.2.2.18.3.2.1.7 BAdI for

MaterialSCMServicePartsPlanningInventoryPolicyChangeRequest_In
Use
MaterialSCMServicePartsPlanningInventoryPolicyChangeRequest_In.
______________________________________________________________
SAP AG 249
SAP System
______________________________________________________________
Standard settings

Activities
See Also
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRD004_RQ interface. For more

sdn.sap.com -> Enterprise SOA .
6.2.2.18.3.2.1.8 BAdI for

MaterialSCMServicePartsPlanningInventoryPolicyBulkChangeRequest_In
Use
MaterialSCMServicePartsPlanningInventoryPolicyBulkChangeRequest_In.
Standard settings

Activities
______________________________________________________________
SAP AG 250
SAP System
______________________________________________________________
See Also
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRD003_RQ interface. For more

6.2.2.18.3.2.1.9 BAdI for MaterialSupplyPlanningChangeRequest/Confirmation
Use
MaterialSupplyPlanningChangeRequestConfirmation_In that is part of the process component
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PSPCHGRC interface. For more
Enterprise Services Index
6.2.2.18.3.2.1.10 BAdI for MaterialSupplyPlanningByIDQuery/Response
Use
______________________________________________________________
SAP AG 251
SAP System
______________________________________________________________
MaterialSupplyPlanningByIDQueryResponse_In that is part of the process component Location
Data Management.
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PSP001QR interface. For more

6.2.2.18.3.2.1.11 BAdI for

MaterialSupplyPlanningSupplyPlanningAreaByIDAnd..Query/Response
Use
MaterialSupplyPlanningSupplyPlanningAreaByIDAndSupplyPlann
ingAreaIDQueryResponse_In that is part of the process component Location Data
Management.
Standard settings
______________________________________________________________
SAP AG 252
SAP System
______________________________________________________________

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PSP002QR interface. For more

6.2.2.18.3.2.1.12 BAdI for

MaterialServicePartsPlanningChangeRequest/Confirmation
Use
MaterialServicePartsPlanningChangeRequestConfirmation_In that is part of the process
component Product Data Management.
Standard settings

Activities
______________________________________________________________
SAP AG 253
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PSPPCHGRC interface. For more

6.2.2.18.3.2.1.13 BAdI for MaterialServicePartsPlanningByIDQuery/Response
Use
MaterialServicePartsPlanningByIDQueryResponse_In that is part of the process component
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PSPP001QR interface. For more

______________________________________________________________
SAP AG 254
SAP System
______________________________________________________________
6.2.2.18.3.2.1.14 BAdI for

MaterialServicePartsPlanningSupplyPlanningAreaByID..Query/Response
Use
MaterialServicePartsPlanningSupplyPlanningAreaByIDAndSuppl
yPlanningAreaIDQueryResponse_In that is part of the process component Product Data
Management.
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PSPP002QR interface. For more

6.2.2.18.3.2.1.15 BAdI for

MaterialServicePartsPlanningSupplyPlanningAreaByIDAndSPAID
Use
MaterialServicePartsPlanningSupplyPlanningAreaByIDAndSupplyPlanningAreaIDQuery_In.
______________________________________________________________
SAP AG 255
SAP System
______________________________________________________________
Standard settings

Activities
See Also
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRD005_QU interface. For more

6.2.2.18.3.2.1.16 BAdI for MaterialDeactivateRequest/Confirmation
Use
MaterialDeactivateRequestConfirmation_In that is part of the process component Product
Data Management.
Standard settings

Activities
______________________________________________________________
SAP AG 256
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCMB/IF_EX_BIF_PDM_PRDCNCRC interface. For more

6.2.2.18.3.2.1.17 BAdI for

MaterialLocationByIDAndLocationIDAndLocationRadiusQuery
Use
MaterialSCMLocationByIDAndLocationIDAndLocationRadiusQueryResponse_In that is part of the
process component Product Data Management.
Standard settings

Activities
See also

______________________________________________________________
SAP AG 257
SAP System
______________________________________________________________
6.2.2.18.3.2.1.18 BAdI for

MaterialSCMReplenishmentByElementsQueryResponse_In
Use
MaterialSCMReplenishmentChangeRequestConfirmation_In that is part of the process component
Product Data Maintenance.
Standard settings

Activities
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_PDM_PRD010RC. For more

6.2.2.18.3.2.1.19 BAdI for

MaterialSCMReplenishmentChangeRequestConfirmation_In
Use
______________________________________________________________
SAP AG 258
SAP System
______________________________________________________________
MaterialSCMReplenishmentChangeRequestConfirmation_In that is part of the process component

Product Data Maintenance.
Standard settings

Activities
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_PDM_PRD010RC. For more

6.2.2.18.3.2.1.20 BAdI for

MaterialSCMSimpleBySupplyPlanningAreaIDQueryResponse_In
Use
MaterialSCMSimpleBySupplyPlanningAreaIDQueryResponse_In that is part of the process
component Product Data Maintenance.
Standard settings

______________________________________________________________
SAP AG 259
SAP System
______________________________________________________________
Activities
See also

6.2.2.18.3.2.1.21 BAdI for

MaterialSCMSupplyPlanningAreaAssignmentActivateRequestConf
Use
MaterialSCMSupplyPlanningAreaAssignmentActivateRequestConfirmation_In that is part of the
process component Product Data Maintenance.
Standard settings

Activities
See also
This BAdI definition uses the interface /SCMB/IF_EX_PDM_SPA_ACTIVAT. For more

______________________________________________________________
SAP AG 260
SAP System
______________________________________________________________
6.2.2.18.3.2.1.22 BAdI for

MaterialSCMSupplyPlanningAreaAssignmentDeactivateRequestConfirm
Use
MaterialSCMSupplyPlanningAreaAssignmentDeactivateRequestConfirmation_In that is part of the
process component Product Data Maintenance.
Standard settings

Activities
See also
This BAdI definition uses the interface /SCMB/IF_EX_PDM_SPA_DEACTIVAT. For more

6.2.2.18.3.3 Source of Supply Determination
6.2.2.18.3.3.1 Source of Supply
______________________________________________________________
SAP AG 261
SAP System
______________________________________________________________
6.2.2.18.3.3.1.1 BAdI for SourceOfSupplySCMByElementsQueryIn
Use
SourceOfSupplySCMByElementsQuery_In.
Standard settings

Activities
See Also
This BAdI definition uses the /SCMB/IF_EX_BIF_LDM_SOS001QU interface. For more

6.2.2.18.3.3.1.2 BAdI for SourceOfSupplyByElemenstQueryResponse
Use
SourceOfSupplySCMByElementsQueryResponse_In that is part of the process component Source of
Supply Determination.
______________________________________________________________
SAP AG 262
SAP System
______________________________________________________________
Standard settings

Activities
See also
This BAdI definition uses the interface /SCMB/IF_EX_BIF_LDM_SOS002QR. For more

6.2.2.18.3.4 Interchangeability Group Management
6.2.2.18.3.4.1 Material and Site Interchangeability Group
6.2.2.18.3.4.1.1 BAdI for

MaterialAndSiteInterchangeabilityGroupSCMByElementsQuery
Use
This Business Add-in (BAdI) is used in the Production Planning and Detailed Scheduling
(SCM-APO-PPS) component. You can use this BAdI tochange or extend the data transferred
through the message interface MaterialAndSiteInterchangeabilityGroupSCMByElementsQuery_In.
Standard settings

______________________________________________________________
SAP AG 263
SAP System
______________________________________________________________
Activities
See Also
This BAdI definition uses the /SCMB/IF_EX_SE_IGM_MSIG_QR interface. For more

6.2.3 Master Data Layer
6.2.3.1 BAdI: Modify Generated Partner ID
Use
This Business Add-In (BAdI) is used in the Master Data Layer (MDL) component.
You can use this BAdI to change the partner ID generated by the MDL to represent a user.
The standard system tries to create a partner ID from the user name. If the system cannot use
the user name because it is already in use, an algorithm creates a new unique partner ID. The
algorithm adds a counter to the user name, which increases with each iteration. If necessary,
characters of the user name are overwritten.
The BAdI is called after the generation of the partner ID. The system uses the partner ID that
the BAdI generates in all applications.
Standard settings

The BAdI definition is not filter-dependent.
Activities
______________________________________________________________
SAP AG 264
SAP System
______________________________________________________________
6.2.4 Configure Parameters
Use
In this IMG activity, you configure the parameters for transactional data.
A parameter describes the structural attributes of a data field that you define by specifying a
data element or an InfoObject in SAP BW.
For more information, see Configure Time Series Data Management and Configure Order
Document Management.
6.2.5 Alert Monitor
In the following steps you define the system settings for the Alert Monitor, the APO tool for
management by exception.
6.2.5.1 Define Number Ranges for Alerts
Use
In this IMG activity you define number ranges for alerts.
______________________________________________________________
SAP AG 265
SAP System
______________________________________________________________
6.2.5.2 Activate/Deactivate Applications in Alert Monitor
Use
In this IMG activity you can configure the applications that are displayed or not displayed in
the Alert Monitor selection screen. In this way you can limit the number of applications
displayed, that is the tab pages displayed under Application-Specific Alert Profiles, to those
that you need. This means that the Alert Monitor selection screen is clearer and is tailored to
your needs.
For an application to be displayed, the indicator Active must be set for this application. To
ensure that certain applications are not displayed, reset this indicator for the relevant
applications.
Standard settings
By default all applications contained in the table for this IMG activity are active. This means
that the Alert Monitor selection screen displays the tab pages for all applications for which the
system determines alerts.
6.2.5.3 Maintain Prioritization of Alert Types
Alert priorities are represented by icons displayed in the monitoring slots of the Supply Chain
Cockpit control panel. In the Alert Monitor window, there are three possible priority levels:
- 1 Error
- 2 Warning
- 3 Information
In the Alert Monitor, a priority level is automatically assigned to all alert types. In this step,
you can change the priority level of an alert.
Note:
In the following cases, your specifications regarding the priority of an alert are overridden by
the system:
- A resource receives an alert due to overload. If the resource and the activities of the
resource are now displayed simultaneously (for example in the product planning table), the
resource and the activities affected by the alert situation each receive an alert due to
overload. To improve clarity for the planner, in this case the standard priority of the alerts
for the activities is overridden by the system and the alert is displayed not with the
standard priority but with the priority level Information.
______________________________________________________________
SAP AG 266
SAP System
______________________________________________________________
As soon as just the alerts for the activities of a resource are displayed, the alerts again
receive the standard priority assigned to them.
- In the case of alerts for Supply and Demand Planning, the alert macros from the planning
books generally override the standard priority.
Activities

2. Use F4 to call up the list of possible alert types.
3. Choose the alert for which you wish to change the priority level.
4. Use F4 to call up the list of priority levels.
5. Change the priority level.
6. Save.
6.2.5.4 Define Additional Status in Alert Monitor
Use
In this IMG activity, you can define your own alert statuses in addition to the predefined alert
statuses. This enables you to tailor the output of alerts found in the Alert Monitor to your own
requirements.
Activities
- Under Status, enter a two-character identifier for the status.

- Enter a description for the status.
- Under Icon, use the input help to assign an icon to the status.
- Define whether the status is to be a user-specific alert status.
- Under Days, specify the number of days after which the alert status is to be reset
automatically.
6.2.5.5 Limit Additionally Defined Status to Specific Alert Object Types
Use
In this IMG activity you can assign a status that you have defined in the IMG activity Define
______________________________________________________________
SAP AG 267
SAP System
______________________________________________________________
Additional Status to one or more alert object types. The status is then only valid for the alert
types with these alert object types. In this way you can make the display clearer and tailor it
to your own requirements.
6.2.5.6 Business Add-Ins (BAdIs) for the Alert Monitor
6.2.5.6.1 Change Prioritization of Alerts Read
Use
The Business Add-In (BAdI) /SAPAPO/AM/SET_PRIO enables you to reprioritize alerts that
have been read, depending on the alert parameters. (You can also use the BAdI
/SAPAPO/AM_ALERTLIST for this purpose).
The system transfers the following to the BAdI: the list t_alerts, containing all alert object types
(AOTs), and a table of field catalogs (T_AOT_FIELDCAT), which assigns a field catalog to the
alert object types.
Via this field catalog, the BAdI relates all alerts that have occurred to alert object types.
Activities
To activate the BAdI, you must create an active implementation. To do so, go to Customizing
for the Alert Monitor and choose Business Add-In (BAdI) for the Alert Monitor.
Example
To view the example code, choose Goto -> Sample Code -> Display.
The example code consists of three parts: the data definition part, the parameter part, and the
implementation part. For simple dependencies when setting priorities, you can copy this example
code for your own implementation. Adjust the parameters as follows:
- Specify the alert object type for which you wish to change the priority:
Alert object type
lc_alert_object_type_to_change(4);VALUE aot_lc_matorder_con,
Which AOT an alert type has can be seen from the maintenance view (sm30)
/SAPAPO/ATYPES. You will find the associated constants in the type group (DDic object)
AOT.
- Specify the name of the field via which the instance of prioritization is to be determined
(determining field):
Determining field
______________________________________________________________
SAP AG 268
SAP System
______________________________________________________________
lc_determining_field(30); VALUE 'ATPCAT'.

- Define a table containing the assignment of the determining field instance to the priority to
be assigned:
Fill table lt_assignment_of_priorities
ls_assignment_of_priorities-value = 'AC'.
ls_assignment_of_priorities-prio = lc_prio_error.
append ls_assignment_of_priorities to lt_assignment_of_priorities.
If you need more than one determining field, you must additionally extend the implementation
part.
6.2.5.6.2 Extend or Change Alert List
Use
The Business Add-In (BAdI) /SAPAPO/AM_ALERTLIST for the Alert Monitor can be used as
follows:
- With the method MODIFY_ALERTLIST, you can append additional fields to an alert type
and also change existing fields.
- If you have defined a PP/DS alert type yourself, you use the method
READ_CUSTDEF_PP_ALERTS, so that these alert types can also be displayed in the
Alert Monitor for example.
Requirements
If you wish to use this BAdI for self-defined PP/DS alert types, you must have defined your
own PP/DS alert types.
Standard settings
In the standard system, the BAdI is not active. No default code is executed automatically.
The BAdI is not filter-dependent and cannot be used multiple times.
Activities
To activate the Business Add-In, you must create an active implementation. To do so, go to
Customizing for the Alert Monitor and choose Business Add-Ins (BAdIs) for the Alert
Monitor.
&ADDITIONAL_HINTS
Documentation of the method READ_CUSTDEF_PP_ALERTS

Documentation of the method MODIFY_ALERTLIST
______________________________________________________________
SAP AG 269
SAP System
______________________________________________________________
6.2.6 Alert Notification Engine
6.2.6.1 Specify Message Channels for Alert Notification Engine
Use
Here, you specify the message channels available for all applications connected to the Alert
Notification Engine.
If you enter a partner or user, the message channel is only available for this recipient. If you
do not enter a partner or user, the message channel is available for all recipients.
6.2.6.2 Connection of the Alert Notification Engine to the Portal
Use
If you are using the Enterprise Portal and the role Production Scheduler, you can also include
alerts from SCM in the Portal in addition to the alerts from the ERP system. If you have
integrated the Alert Notification Engine, the system is able to determine the responsible person
and send them the alerts that were generated by the Alert Notification Engine into the Portal.
This IMG activity describes what you must do to enable the system to forward individual alerts
from the PP/DS area to the alert inbox of the Portal.
Requirements
You have assigned the URL of the alert inbox in Alert Management to the alert inbox in the
Portal. You can also assign more than one URL to the alert inbox in the Portal.
Activities
You must execute the following activities to be able to include the alerts in the Portal:
1. You create an alert profile in SCM. In the alert profile, you can select which alerts you
want to use for which objects.
2. You select a message profile. For the role production scheduler, message profile
______________________________________________________________
SAP AG 270
SAP System
______________________________________________________________
PRODUCTIONPLANNER is offered as an example. In this profile you can specify which

detailed information is to be displayed in the alert message, such as material name,
resource name and so on.
3. You maintain the Alert Notification Profile. You use the alert notification profile to define
the recipient of the alerts and to define which message profile is to be used. For more
information about creating an alert notification profile, see the SAP Library under Alert
Monitor -> Sending Alert Notifications -> Settings for Sending Using the Alert
Notification Engine.
4. To enable the system to send the alerts, you must schedule report /SCMB/ANOT_PULL
to run periodically.
For more information about integrating SCM alerts into the Portal, see SAP Note 948426.
6.2.6.3 Business Add-Ins (BAdIs) for the Alert Notification Engine
6.2.6.3.1 Change Structure of Messages
Use
You use the /SCMB/ANOT_MSGCREATE business add-in (BAdI) to control how the Alert
Notification Engine compiles messages for alert notification from the alert data determined in
the connected application. You can change or replace the settings already made in the message
profile.
If you have created an active implementation of this BAdI, you can do without the message
profile.
The selection of alerts for notification is not affected by this BAdI.
The BAdI is called when the messages are created.
Standard settings
The BAdI is not active as standard.

If an active implementation does not exist, method MSGCREATE of class /SCMB/ANOTEN is
executed after the BAdI is called.
The BAdI is not filter-dependent and cannot be used on multiple occasions.
Activities
To activate the BAdI, you have to create an active implementation. To do this, go to

Customizing for the Alert Notification Engine and choose Business Add-Ins (BAdI) for the
Alert Notification Engine.
For more information on the procedure, see the SAP Library under Basis Components ->
______________________________________________________________
SAP AG 271
SAP System
______________________________________________________________
ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins ->
Implementing Business Add-Ins.
Further notes
Documentation for BAdI Method MSGCREATE
6.2.6.3.2 Change URL for Calling an Alert
Use
With the Business Add-In (BAdI) /SCMB/ALERTURLADDIN, you can change the URL that
is contained in a notification sent from the Alert Notification Engine.
6.2.6.3.3 Change Attachments
Use
With the Business Add-In (BAdI) /SCMB/ANOTATTACHMENT, you can change attachments
that are attached to a notification by the Alert Notification Engine.
6.2.6.3.4 BAdI: Change Authorization Check for Location Products
Use
This Business Add-In (BAdI) is used in the Alert Notification Engine (SCM-BAS-ANO)
component. You can use this BAdI, to either change the authorization check for location
products that SCM Basis runs when they generate an alert notification message or you can use
______________________________________________________________
SAP AG 272
SAP System
______________________________________________________________
the BAdI to switch off the authorization check. SCM Basis calls this BAdI before it runs the
authorization check. This BAdI uses the BAdI method Filter Location Products Using
Authorization Check (FILTER_BY_AUTH_CHECK). The BAdI method filters all location
products on the basis of the authorization check and determines if SCM Basis needs to run
further authorization checks.
Standard settings
Activities
6.2.7 Process Controller
6.2.7.1 Define Service
Use
In this Customizing activity, you define services.
6.2.7.2 Define Strategy
Use
In this Customizing activity, you define a strategy and choose the required service. You can
then assign methods and method parameters to this strategy (see Assign Methods to a Strategy
and Assign Method Parameters to a Strategy). You can use your strategy instead of the standard
strategy delivered by SAP.
______________________________________________________________
SAP AG 273
SAP System
______________________________________________________________
6.2.7.3 Define Methods
Use
In this Customizing activity, you define methods and technical data. You need this technical
data to call the method:
- Interface component (method name)
- Class/interface (class that contains the method mentioned before)
- You then assign these methods to your strategy (see Assign Methods to a Strategy).
6.2.7.4 Assign Methods to a Strategy
Use
In this Customizing activity, you assign methods to a strategy and define the order in which the
methods in the strategy are to be called. You can assign existing methods (from the standard
strategy) or you can assign your own methods.
Requirements
You have defined a strategy and methods and have chosen the same service for each.
______________________________________________________________
SAP AG 274
SAP System
______________________________________________________________
6.2.7.5 Define Parameters
Use
In this Customizing activity, you define parameters and detailed information. You then assign
these parameters to your strategy (see Assign Method Parameters to a Strategy). There you can
also define default values for your parameters.
6.2.7.6 Assign Parameters to a Method
Use
In this Customizing activity, you can assign parameters to a method to use them in a strategy.
You can assign a parameter to more than one method. In the Customizing activity Assign
Method Parameters to a Strategy, you can assign your parameter to a strategy and define values
for it.
6.2.7.7 Assign Method Parameters to a Strategy
Use
In this Customizing activity, you can define default values for parameters of a method belonging
to a strategy. Method parameters are used when the routing guide is called, assuming that they
are not overridden.
Requirements
You have defined strategies, methods, and parameters, and have chosen the same service for
each.
______________________________________________________________
SAP AG 275
SAP System
______________________________________________________________
6.2.8 Logistics Inventory Management Engine (LIME)
6.2.8.1 Basic Settings
6.2.8.1.1 Features of Calling Application
6.2.8.1.1.1 Process Type of Calling Application
6.2.8.1.1.1.1 Determine Process Type of Calling Application
Use
In this IMG activity, you determine the process type of the calling application. The process
type of the calling application controls how LIME processes an inbound document.
In the Applications step, you determine for the particular process type whether the system:
- Calls the collector
- Creates and saves a Prima Nota document
- Uses dated stock
In the Control Collector step, you determine for each process type which subsequent
applications LIME must inform about the posting.
You cannot define new process types in the Implementation Guide (IMG), you can only do it
directly in the source text.
Note
We recommend that you only allow SAP to make this change.
You also set in the source text for the new process type whether the system:
- creates a LOG file
- in the case of error terminates posting of the complete document or simply does not post
the incorrect group
- returns the direct parent or all parents of the hierarchy during a goods movement
- explodes the stock entries during a location or HU movement
- should not execute particular functions for performance reasons.
______________________________________________________________
SAP AG 276
SAP System
______________________________________________________________
Standard settings
SAP delivers the following process types:

- Reorganization/administration (ADMI)
- External application (EXTR)
- Data transfer from SAP R/3 (MIDL)
- Goods movement from SAP R/3 (MIGO)
- SCM Goods Movement (LIMA)
- SCM Physical Inventory (LIPI)
- SCM Delivery (DELI)
- SCM Inventory Collaboration Hub (SCA)
- SCM Forecast & Replenishment (FRE)
Activities
During activation of a collection for a process type, ensure that the corresponding Business
Add-In implementation exists for the collector and is active.
6.2.8.1.1.1.2 Determine External Number Assignment for Inbound Documents
Use
In this IMG activity, you determine the number range for the assignment of external document
numbers. This ensures a unique assignment between the external document and the LIME
documents. If the calling application can already guarantee the uniqueness of the external
document number for a goods movement (for each process type), this function is not required.
The assignment of the external document number by LIME may be useful for preventing several
calling applications from having the same external document number.
Activities
To use this function, you must call function module /LIME/GET_EXT_DOC (Document
Number Assignment for LIME Call), before you call LIME, to assign the unique external
document number. This document number is then transferred to LIME in the connecting LIME
call.
______________________________________________________________
SAP AG 277
SAP System
______________________________________________________________
6.2.8.1.1.1.3 Dispatcher
6.2.8.1.1.1.3.1 Determine Control Data for Dispatcher
Use
In this IMG activity, you determine which of the following applications (collection types) are to
be called by the system for the dispatcher.
You can specify for each collection type:
- whether the dispatcher is to be called immediately
- which communication type is to be set for distributing the LIME data
- which number range group in LIME is used if no external document number exists or if a
document summarization takes place within LIME.
Standard settings
In the LIME standard settings, the dispatcher is called immediately.
Activities
If you call the dispatcher later for collection types, this is sent by the system using job
/LIME/DISPATCHER_EXEC. You can manually schedule the job periodically.
You can determine the number ranges for the groups in the IMG activity Determine Number
Assignment for Documents.
6.2.8.1.1.1.3.2 Set Filter Values for Dispatcher
Use
In this IMG activity, you set the filter values for the dispatcher.
The filter values for the Business Add-In (BAdI) /LIME/DISPATCHER (Distribution of LIME
Documents) depend on the collection type and the communication type. For each combination of
collection type and communication type you use, determine the relevant filter value.
______________________________________________________________
SAP AG 278
SAP System
______________________________________________________________
Standard settings
There is one standard implementation for both filter values BWLOC and MMIMLOC.
Activities
When using filter value LEGXI or when creating a new filter value, create and activate a BAdI
implementation in the dispatcher.
6.2.8.1.1.1.3.3 Define Filter Values for the Distribution of Documents
Use
In this IMG activity, define the filter values for the dispatcher.
Activities
After you have created a new filter value, enhance the Business Add-In (BAdI) of the
dispatcher with the implementation and activate this implementation. Assign the new filter value
to a collection type, and the corresponding communication type (also see IMG activity Set Filter
Values for Dispatcher).
6.2.8.1.1.1.3.4 Determine Number Assignment for Documents
Use
In this IMG activity, you determine the assignment of LIME-internal document numbers for the
DS:GLOS.95E9D6B493848E498970807ED381B87B>dispatcher.
This document number is used in LIME if a document number was not transferred to LIME
from an external application, or if the collector aggregates the documents and therefore deletes
the external document numbers.
With the LIME-internal number assignment, it is possible to determine for a subsequent
application, the original documents from which a collection is composed.
Determine the assignment of a collection to a number range group in the IMG activity
Determine Control Data for Dispatcher.
______________________________________________________________
SAP AG 279
SAP System
______________________________________________________________
6.2.8.1.2 Index Tables and Hierarchy
6.2.8.1.2.1 Generate LIME Source Code
Use
In this IMG activity, you generate the source text for the newly created or changed index table.
Activities
After creating a new index table, you must include this in the Customizing index table (IMG
activity Determine Index Tables) and then determine the hierarchy dependency within LIME
(IMG activity Determine Hierarchy).
6.2.8.1.2.2 Determine Index Tables
Use
In this IMG activity, you must include newly-created business keys (new location, handling unit
or stock index tables) in the index table.
The LIME-internal key for an index table is composed of the object types (L for location, H
for handling unit, and S for stock item) and a three-digit index.
For each created stock index table, you set an indicator to determine whether new entries can
be included in the index table for a goods movement or physical inventory. If you do not set
this indicator for a stock index table, you cannot create new stocks for this table. You can then
only execute goods movements for stocks that already exist in the system. In this case, you
create new stocks with the function module /LIME/STOCK_MAINTAIN
For creating a handling unit (HU) or location, use function module /LIME/HU_MAINTAIN (for
HUs) or /LIME/LOC_MAINTAIN (for locations).
Furthermore, determine for each index table (location, HU or stock) whether its entries can be
______________________________________________________________
SAP AG 280
SAP System
______________________________________________________________
deleted in the current tables. The deletion process takes place in an automatic background job:
/LIME/BACKGROUND_DELETE_EXEC.
If you set the deletion indicator, you also delete the entry in the current index table.
In a stock index table, the entries are deleted if the stock shows value 0.
At a location or HU, the entries are deleted if they no longer have children. We recommend
that you only delete entries for locations and HUs in special cases.
Activities
You schedule the automatic background job /LIME/BACKGROUND_DELETE_EXEC

periodically. You can also schedule and execute this background job if the deletion indicator is
not set for any index table. The background job ensures that the current work tables within
LIME do not contain any unnecessary entries.
6.2.8.1.2.3 Determine Hierarchy
Use
In this IMG activity, you determine the hierarchy structure within LIME for locations, handling
units, and stocks. You must display the allowed hierarchy dependencies in LIME. You can, for
example, determine for a location (parent) whether it is allowed to create a sublocation (child),
and which stock types can be stored in this location, for example, whether it is allowed to put
away a handling unit. After you have determined new hierarchy entries for the newly created
index table, you can then execute goods movements in this new index table.
Within LIME, the highest node is called ROOT. This always contains the key table entry 000.
All of your objects on the highest level (for example, location plant) must be assigned to this
highest node. Only locations are allowed as the child for the highest node.
Standard settings
The highest node Root always has key table entry 000. The system sets this value
automatically. The highest node can only be selected as the parent.
For the parent, the entries for locations and handling units can be selected according to the
index table and the highest node (Root). You cannot select stocks as the parent.
For the child, the entries for locations, handling units and stocks can be selected according to
the index table and the wildcard characters * (= all entries for locations or handling units or
stocks).
______________________________________________________________
SAP AG 281
SAP System
______________________________________________________________
Example
For the child entry, a wildcard character (*) is allowed, in other words, if you have assigned
the child Stock * to a location (as parent Location Plant + Stor.Loc.), all stock index
tables of this location can be assigned to a goods movement within LIME.
6.2.8.1.2.4 Determine Node Width
Use
In this IMG activity, you can define the width of the nodes in the LIME hierarchy.
If you do not maintain the width, LIME uses standard values for the node width.
You can maintain the width per type (location or HU), level, and index. In addition, you can
define categories for the size. When you create new locations or HUs, you can specify this size
category. LIME then uses the width defined there.
6.2.8.1.3 User-Specific Parameters
6.2.8.1.3.1 Determine Grouping Parameters
Use
In this IMG activity, you determine the grouping parameters for the physical inventory.
For incoming documents with several goods receipt lines, it may be that the following
applications require information for each incoming line and not simply for each document (such
as Financial Accounting), or that you need to execute a different quantity conversion within the
document for each incoming line. You define the grouping parameter required for this here.
Requirements
The calling application must be in a position to transfer the fields of the grouping parameter to
LIME or to the physical inventory.
______________________________________________________________
SAP AG 282
SAP System
______________________________________________________________
Standard settings
The physical inventory transfers the fields of the parameter group to LIME, but does not
execute any activities itself.
Activities
The inbound document for LIME and the physical inventory must be enhanced with the fields
that belong to this grouping parameter.
According to the use of the grouping parameter, you may have to execute or adjust an
implementation in the corresponding Business Add-Ins (BAdIs).
6.2.8.1.3.2 Determine Type of Quantity Calculation
Use
In this IMG activity, use the QCI type (type of quantity calculation) to control which specified
quantity conversion is to be executed in the Business Add-In (BAdI) /LIME/QCI for LIME.
In a first work step, you define the filter value used for LIME in BAdI /LIME/QCI.
In a second work step, you create an implementation for this filter value for LIME in BAdI
/LIME/QCI.
Standard settings
Both QCI types (= filter values) DOC and MARM are delivered:
- DOC
Quantity conversion does not take place within LIME; the correct quantities have already
been transferred by the calling instance.
- MARM
Quantity conversion takes place in LIME to calculate the stock quantity from the document
quantity. The calculation is only executed for both stock index tables 002 (location plant)
and 001 (location plant + stor.loc.). (The calculation takes place based on the quantity
conversion in the SAP R/3 standard system.)
______________________________________________________________
SAP AG 283
SAP System
______________________________________________________________
6.2.8.1.4 Application-Specific Settings
6.2.8.1.4.1 Determine Stock Type
Use
In this IMG activity, you determine the stock types.

Aside from the quantity of a stock at a particular storage bin, the status and its availability are
also important. With the stock type, you determine the status and therefore the availability of a
stock within LIME.
The stock types defined here are also used in the physical inventory
Requirements
The stock types used must be recognized by both the calling instance and the subsequent
applications.
Standard settings
The stock type is a key field for all stock index tables.
6.2.8.1.4.2 Determine Indicator for Virtual Stock
Use
In this IMG activity, you determine the indicator for the virtual stock (VSI = virtual stock
indicator). This indicator allows you to display the same physical stocks in LIME several times.
Stock without a VSI is the real stock. You can define the valid VSI values within LIME in
this IMG activity.
Standard settings
Aside from the physical stock with initial VSI values (blank), there are two VSI values, A for
book inventory, and P for planned stock. You can therefore determine whether a stock quantity
refers to the physical or virtual stock.
______________________________________________________________
SAP AG 284
SAP System
______________________________________________________________
Example
A location (such as a tank of a tank operator) stores the stocks of owners. owners. The
location stock is determined periodically, for example, by a physical inventory, and corresponds
with the physical stock, whereas the stocks of the different owners are managed as book
inventory (VSI value = A). The stocks of the individual owners lie beneath the location in the
hierarchy.
During determination of the physical stock, only the physical inventory measurement is taken
into consideration; the individual book inventories are not considered. In this way, you can
ensure that the same physical stock is not counted more than once.
During stock analyses, it is possible to evaluate stocks for each VSI.
6.2.8.1.4.3 Determine Indicator for Stock Use
Use
In this IMG activity, you determine the special stocks to be used in LIME or the physical
inventory using the stock usage indicator.
Special stocks are stocks that have to be executed separately. Examples of this include vendor
consignment stock and consignment stock at customer.
Requirements
The stock usage types used must be known by both the calling instance and the subsequent
applications.
Standard settings
The stock usage is a key field in all stock index tables.
Example
Consignment processing:
Both the stock at the custodian and stock at the customers is to be displayed with a stock usage
indicator (C) within LIME, as the owner is also a key field in the stock index table.
Regardless of who is entered as the owner, either vendor consignment (owner = partner) or
customer consignment (owner = own company) is concerned. Accordingly, in the relevant
location, the company is entered as the custodian for vendor consignment and the partner is
entered as the custodian for customer consignment.
The same goes for returnable packaging processing with the stock usage indicator E (see below)
and for subcontract procurement processing with the stock usage indicator D.
______________________________________________________________
SAP AG 285
SAP System
______________________________________________________________
Returnable packaging processing:

Returnable packaging at the vendors: Custodian = own company, owner = partner.
Returnable packaging at the customers: Custodian = partner, owner = own company.
6.2.8.1.4.4 Determine Reason for Movement
Use
In this IMG activity, you define the reason for a goods movement that is allowed in LIME. In
the calling application, for example SAP R/3, entering a reason for a return delivery to the
vendors may be obligatory. The reason for movement specified in a LIME inbound document is
checked here aginst the determined values.
Requirements
The values for the reason of the movement must be known in all systems or adjusted in the
particular interface (calling application/LIME or LIME/application to be called) according to
the values in the application called.
Standard settings
For a connection from LIME to an SAP R/3 System (process type: Goods Movement from
SAP R/3), some reasons for goods movements have already been delivered by SAP.
6.2.8.1.4.5 Define Description of Stock Change
Use
In this IMG activity, you can determine business descriptions for stock changes.
It is possible for a LIME user to set the Description of Stock Change indicator for different
business processes, in order to describe the stock changes from a business view. Because the
system copies this indicator into the LIME documents, you can differentiate between goods
movements such as scrapping or release from quality inspection stock.
Note
The purpose of this function is to determine a non-technical field in a LIME document and is
not intended for subsequent applications. For subsequent applications, you must use IMG activity
Determine Reason for Movement.
______________________________________________________________
SAP AG 286
SAP System
______________________________________________________________
6.2.8.1.4.6 Determine Global Customizing Settings for Each Client
Use
In this step, you determine client-wide whether negative stocks are to be allowed. If you need
fine-tuned control for allowing negative stocks beneath client level, you can set method
NEGATIVE_STOCK in Business Add-In (BAdI) /LIME/CUST.
Standard settings
Negative stocks are allowed in the LIME standard settings.
6.2.8.2 Business Add-Ins (BAdIs)
6.2.8.2.1 Dependencies Between BAdIs
Use
Business Add-Ins for Master Data and Quantity Conversion

After you have executed or changed an implementation in method
GET_UNITS_AND_QCI_TYPE in Business Add-In (BAdI) BAdI: Read LIME Master Data,
check that for the selected return parameter E_QCI_TYPE, a corresponding implementation
exists in the BAdI: LIME QCI Converter and check whether this needs to be changed.
Business Add-Ins for Collector and Dispatcher
After you have changed an implementation for a collection type in BAdI: Fill LIME Collections
(for example, in method ADD_FIELDS), check in the relevant dispatcher implementation in
BAdI: Distribution of LIME Documents, whether this also needs to be changed (especially in
method SET_COLLECTION).
Requirements
The required BAdIs are active in your system.
______________________________________________________________
SAP AG 287
SAP System
______________________________________________________________
Example
Create a new index table

After you have created a new index table, check whether you have to adjust your
implementations in the BAdIs:
- Are your incoming checks still correct?
(BAdI: Static Checks of Incoming Documents)
- Do you have to read master data?
(BAdI: Read LIME Master Data)
- Are quantity conversions necessary?
(BAdI: LIME QCI Converter)
- Do you need to adjust BAdIs in Customizing?
(BAdI: LIME Customizing)
- Are you using dependent rules in your data cumulation (collections) of index tables?
(BAdI: Fill LIME Collections)
- Are the distribution rules for subsequent applications still correct?
(BAdI: Distribution of LIME Documents)
6.2.8.2.2 BAdI: Static Checks of Inbound Documents
Use
This Business Add-In (BAdI) is used in component SCM-ECT-LIM.

With this BAdI, you can check the LIME inbound documents for accuracy, and terminate
processing in the event of errors.
The BAdI makes the method CHECK_DOC available, which is called in LIME prior to
execution. The interface /LIME/IF_PN is passed on to the method CHECK_DOC. This interface
facilitates access to the inbound document via appropriate GET methods.
The BAdI is called for different categories of inbound documents:
- Maintain modules (/LIME/LOC_MAINTAIN, /LIME/HU_MAINTAIN and
/LIME/STOCK_MAINTAIN)
- HU/LOC move modules (/LIME/LOC_MOVE and /LIME/HU_MOVE)
- Goods movement (/LIME/DOCUMENT_INPUT)
In accordance with the calling function module, you obtain the information on the inbound
document via the associated GET methods. In this way, for example, you get location maintain
lines via the method GET_LOC_MAINT_ITEM, goods movement lines via the method
______________________________________________________________
SAP AG 288
SAP System
______________________________________________________________
GET_ITEM, and so on.

You can interrupt the processing of the document by triggering an exception of the category
/LIME/CX_BADI. This exception is logged in LIME.
Requirements
Depending on the process type, you can deactivate the BAdI call. However, this is not a
Customizing setting - a modification of the SAP source code is necessary.
Standard settings
- In the standard system, the Business Add-In is active.

- There is no default implementation.
Activities
Customizing and choose the relevant IMG activity under Business Add-Ins (BAdIs).
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
For more information, see the SAP Library under SAP Web Application Server -> ABAP
Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins ->
______________________________________________________________
SAP AG 289
SAP System
______________________________________________________________
Example
The example implementation of the BAdI ensures that stocks are updated with VSI=A (Virtual
Stock Indicator) only via 'absolute stock postings'.
See also
You can also call the documentation for a BAdI method from the menu:
1. Select tab page Interface.
3. Click the right-hand mouse button and choose Documentation on Component.
6.2.8.2.3 BAdI: Read LIME Master Data
Use

The Business Add-In /LIME/MASTER_DATA enables you to:
- Determine the conversion type /LIME/QCI_TYPE for a movement: Type of quantity
calculation
- Compile a list of allowed units of measure for a stock posting and notify the system of it
- Read master data to check postings (creation, changing, and deletion of stocks, locations,
and HUs) in the system and carry out this check during the relevant activities
For each goods movement in the system, a conversion type /LIME/QCI_TYPE is necessary for
each item. You can define the allowed conversion types in Customizing. The conversion type is
the filter value for the Business Add-In /LIME/QCI and controls the product-dependent or
product-location-dependent type of quantity calculation that may be necessary. SAP supplies two
entries for these conversion types: DOC and MARM. The determination of these conversion
types is implemented as an example in a default implementation supplied by SAP with this
BAdI. The service class /LIME/CL_SRV_MASTER_DATA is supplied for this purpose. If you
create your own implementation that overwrites the default implementation, we recommend
creating your own service class derived from this service class.
As a rule, the default implementation of this BAdI sets the type of quantity conversion to the
type DOC. The type MARM is set if a posting with SAP R/3 materials is involved and the
master data is to be read from an SAP R/3 system and the stock index tables with the index
number 001 (location plant + storage location) or 002 (location plant) are affected. These tables
are supplied by SAP.
Type of quantity calculation: DOC
For this conversion type, there is generally no further master data access and no quantity
conversion. The list of allowed units of measure is compiled from the list of the document
______________________________________________________________
SAP AG 290
SAP System
______________________________________________________________
units of measure.
Example:
1. You post a goods movement (goods receipt) for a material A with 1000 kg. In this case,
the list of allowed units of measure will contain just one unit of measure, namely the unit
kg. This unit is flagged as inventory-managed. The stock figure for the material increases
by 1000 kg following successful posting.
2. You post a goods movement for a material B with 1000 kg and 22 pc. The list of allowed
units of measure will now contain both units, namely the units kg and pc. Both units are
flagged as inventory-managed. The stock figure for the material increases by 1000 kg and
22 pc following successful posting (parallel inventory management).
As a general rule, no units of measure are flagged as valuation-relevant for the type of quantity
calculation DOC. The service class /LIME/CL_SRV_MASTER_DATA contains a method
CHANGE_DOC_UNIT_FLAGS which can be redefined in the event that a customer service
class is derived for a customer-specific implementation of this BAdI to define units as
valuation-relevant.
Type of quantity calculation: MARM
The type MARM is set as explained above if a posting with SAP R/3 materials is involved and
the master data is to be read from an SAP R/3 system, and the stock index tables with index
number 001 or 002 are affected. The master data access is effected via the MDL (master data
layer) and the relevant functions of this component. If an SAP R/3 system holds the master
data, the list of allowed quantity units is compiled via the access from the tables MARA and
MARM and the QCI-TYPE is set to MARM. The base unit of measure is then the only unit
that is relevant with regard to both the stock update and valuation in subsequent systems.
Example:
1. You post a goods movement for a material A with 1000 kg. The accessing of the master
data in an SAP R/3 system is successful and determines L (liter), kg, and pc as allowed
units of measure. The base unit of measure is kg. The stock figure is increased by 1000
kg following successful posting. There is no conversion into the quantities L and pc, since
these are allowed for a goods movement but need not be known.
2. You post a goods movement for a material A with 1000 pc. The accessing of the master
data in an SAP R/3 system is successful and determines L (liter), kg, and pc as allowed
units of measure. The base unit of measure is kg. This makes it necessary to calculate the
quantity in the base unit kg. For this purpose, the default implementation of the Business
Add-In /LIME/QCI is run through. The stock figure is increased by 200 kg following
successful posting (assumption: 5 pc = 1 kg). Just one quantity conversion takes place:
from the quanity in pc into the quantity in kg. The quantity in L is not calculated, since
the quantity in this unit, although basically allowed for a goods movement, is not necessary
for the further process steps.
Master data check
The Business Add-In /LIME/MASTER_DATA makes available a series of callback methods,
which can be called during the processing of a LIME document. The methods enable you to
carry out additional master data checks and add further information.
______________________________________________________________
SAP AG 291
SAP System
______________________________________________________________
- ON_CREATE_*
The methods are called whenever a location, an HU, or a stock item is created. You have
the opportunity to change the attributes of the object and can assign a GUID for the object
to be created.
- ON_CHANGE_*
The methods are called if the attributes of an object are changed.
- ON_DELETE_*
The methods are called when a LIME object is deleted.
- ON_POST_GM
In the method, you have the opportunity to carry out further master data checks and
terminate the posting if necessary.
SAP does not supply a default implementation for the callback methods.
Standard settings
In the standard system supplied, the above-mentioned default implementation is run through.
Activities
the implementation.
Short Text field.
10. Choose Activate.
______________________________________________________________
SAP AG 292
SAP System
______________________________________________________________
you wrote.
Example
In addition to the already-mentioned default implementation, there is an example implementation

for the callback methods.
See also
6.2.8.2.4 BAdI: LIME QCI Converter
Use

With the filter BAdI /LIME/QCI, you can achieve the following for each filter value
/LIME/QCI_TYPE that is determined for a goods movement in the implementation of Business
Add-In /LIME/MASTER_DATA:
- Carry out a quantity conversion for missing units of measure
- Check quantities for several units for consistency and, in the case of error, reject the
posting
In the default implementation of BAdI /LIME/MASTER_DATA, the QCI-TYP (type of quantity
conversion) is set. SAP supplies entries in the relevant Customizing table for two values (DOC
and MARM). These values are used in the default implementation of the Business Add-In
/LIME/MASTER_DATA. A quantity conversion is not allowed within this BAdI for the value
DOC. In this case, the system runs through the method for checking the quantity only. For the
filter value MARM, the default implementation of this BAdI is run through and a quantity
calculation executed.
Standard settings
The default implementation for this BAdI carries out a calculation of the stock quantity from
the document quantity, if the stock quantity or quantities is/are not included in the table of the
document quantity. The calculation only takes place for movements in which the stock index
______________________________________________________________
SAP AG 293
SAP System
______________________________________________________________
tables with index 001 or 002 are involved. The calculation is based on the standard R/3
quantity conversion (table MARM). SAP uses a service class /LIME/CL_SRV_QCI for the
default implementation of this BAdI, which is also available to customers.
Important:
If the stock quantity is calculated from a document quantity, this may lead to the following
situation: A goods movement is posted for a material with 2 pc and 6 liters. The stock is to
be managed in kg. As the starting unit of measure for the calculation, there are now 2
quantities available in different units. The default implementation rejects this case with an error
message, because no general decision as to which quantity the quantity in kg is to be calculated
from can be arrived at.
Activities
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
Example
To display default code, choose Goto -> Default Code -> Display.
______________________________________________________________
SAP AG 294
SAP System
______________________________________________________________
To display example code, choose Goto -> Example Code -> Display.
See also
6.2.8.2.5 BAdI: LIME Customizing
Use

With Business Add-In /LIME/CUST, you can overwrite the Customizing settings in LIME by
defining your own logic. The particular BAdI method is called when the Customizing data is
used. This is possible for the three following methods:
- WRITE_PN You can use this method to control whether a Prima Nota document is to be
written, depending on the data in the LIME inbound document.
- GET_COMM_TYPE
This method delivers the communication type or types for a collection. The LIME standard
system only supports one communication type for each collection.
- AUTO_CREATE
With this method, you can override the Customizing setting for whether a stock index
entry is to be generated automatically.
- NEGATIVE_STOCK
With this method you can control in detail whether negative values are allowed for a
stock, for example, at material level. In LIME, you can only make this setting per client.
- ARCH_RESIDENT With this method, you can control whether the archiving and deletion
of inbound documents is to be prevented during standard archiving, before the inbound
documents are archived by the calling application. Each inbound document therefore
remains in the system until it is archived by the calling application and the
/LIME/ARCH_RESIDENT indicator in the log table for the header data of a Prima Nota
document (/LIME/LOG_HEAD) has been reset.
Standard settings
- The Business Add-In is active in the standard system. The default code is executed
automatically.
- The Business Add-In cannot be used more than once.
- The Business Add-In is not filter-dependent.
______________________________________________________________
SAP AG 295
SAP System
______________________________________________________________
Activities
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
Example
See also
Documentation on interface /LIME/IF_EX_CUST

Documentation on BAdI methods:
Are Negative Stocks Allowed?
NEGATIVE_STOCK
Automatic Creation of a Stock
______________________________________________________________
SAP AG 296
SAP System
______________________________________________________________
AUTO_CREATE
Delivers all Communication Types to Collection Type
GET_COMM_TYPE
6.2.8.2.6 BAdI: Fill LIME Collections
Use

The Business Add-In /LIME/COLLECTOR enables you to influence collections for
communication with subsequent applications. You can:
- Extend collections by adding customer-specific fields
- Flag document items as relevant/irrelevant for the collections
- Reset fields of a document item in order to aggregate collections
The Business Add-In is a filter-BAdI, so an implementation is necessary for each collection
type. The allowed values for the collection types are defined in table /LIME/CUSY_COLL. For
example, an implementation for the collection type BW (Business Warehouse) influences the
updating of the BW collections in table /LIME/COLL_BW. It is not possible to define
customer-specific collection types because this would involve program changes. The collection
type LEG (legacy) is reserved for customer developments.
In a second step, the collections are read by the LIME dispatcher and distributed to the
subsequent applications. The BAdI /LIME/DISPATCHER is available for the purpose of setting
the dispatcher functions. An implementation of the BAdI /LIME/COLLECTOR only makes sense
if a corresponding implementation of the BAdI /LIME/DISPATCHER exists.
In the standard system, collector/dispatcher functions are only provided for SAP R/3 MMIM and
for BW. SAP supplies standard implementations for the BAdI /LIME/COLLECTOR and service
classes for the BAdI /LIME/DISPATCHER for both collection types.
Only the legacy collection (LEG) is provided for the link to external systems. SAP reserves the
right to supply a standard implementation for all other collections in future releases.
The methods of the BAdI /LIME/COLLECTOR are called directly after the posting of a goods
movement, HU movement, location movement, or stock report in LIME. In LIME, the stock
has already been updated and a document generated. The BAdI is not invoked in the case of
MAINTAIN functions (function modules /LIME/STOCK_MAINTAIN, /LIME/HU_MAINTAIN,
/LIME/LOC_MAINTAIN or in the case of corresponding maintain lines in
/LIME/DOCUMENT_POST).
______________________________________________________________
SAP AG 297
SAP System
______________________________________________________________
The methods are invoked in the following order:

1. GET_PARENT
2. ADD_FIELDS
3. RELEVANCE_CHECK
4. CLEAR_FIELDS
The GET_PARENT method is first processed for all lines of the incoming documents. After
this, the methods ADD_FIELDS, RELEVANCE_CHECK, and CLEAR_FIELDS are run through
for the possible collection records.
Requirements
The collection type must have been activated for the process type in Customizing.
Standard settings
In the standard system supplied, standard implementations for the BW collection and the MMIM
collection are active. There is no default implementation.
- The Business Add-In is active in the standard system. The default code is executed
automatically.
- The Business Add-In can be used more than once. All active implementations are called
and executed.
- The Business Add-In is filter-dependent. Create an implementation for each desired filter
category.
Activities
A standard implementation exists for the standard collection types BW and MMIM. You do not
need to create an implementation for these collection types.
If you wish to connect an external system to LIME, you must create an implementation for the
filter value LEG.
the implementation.
Short Text field.
______________________________________________________________
SAP AG 298
SAP System
______________________________________________________________
8. Choose Activate.
you wrote.
Note that the Business Add-In can be used more than once, therefore all active implementations
are called and run.
Example
SAP does not supply an example implementation or a default implementation for this BAdI
because a standard implementation exists.
See also
Documentation on BAdI methods:

Population of BAdI Structures for the Collections
ADD_FIELDS
Initialize Fields for Aggregation
CLEAR_FIELDS
Current Line Relevant to Collection
RELEVANCE_CHECK
Determination of Location/HU for Follow-On Application
GET_PARENT
______________________________________________________________
SAP AG 299
SAP System
______________________________________________________________
6.2.8.2.7 BAdI: Distribution of LIME Documents
Use

With BAdI /LIME/DISPATCHER, the collections are transferred to the subsequent applications.
The communication can take place both snychronously and asynchronously with program
/LIME/DISPATCHER_EXEC. The LIME documents to be sent are first combined in BAdI
/LIME/COLLECTOR for each application.
The Business Add-In /LIME/DISPATCHER is a filter BAdI, in other words, an implementation
is necessary for each subsequent application and communication type. For each application
(collection type), the standard system only supports one communication type. The allowed filter
values are defined in table LIME/CUSY_FLTDI. The decision about which filter value will be
run by the implementation of the BAdI for a particular collection type, is made according to
the Customizing data of the IMG activity Set Filter Values for Dispatcher
(/LIME/V_CUST_FDR).
An implementation of BAdI /LIME/DISPATCHER is only useful when a corresponding
implementation of BAdI /LIME/COLLECTOR exists.
In the standard system, there are currently only collector/dispatcher functions intended for SAP
R/3 MMIM and for SAP BW. SAP delivers standard implementations for BAdI
/LIME/COLLECTOR and service classes for BAdI /LIME/DISPATCHER for both collection
types.
BAdI /LIME/COLLECTOR and therefore also BAdI /LIME/DISPATCHER is not called for
MAINTAIN functions (function modules /LIME/STOCK_MAINTAIN, /LIME/HU_MAINTAIN,
/LIME/LOC_MAINTAIN or corresponding Maintain lines in /LIME/DOCUMENT_POST).
The methods are called when posting a goods movement in the following sequence:
- SET_DISPATCH_IMMEDIATELY
- SET_COLLECTION
- TAKE_NO_FROM_NORANGE
- SET_DISPATCH_EXT_DOC
- CALL
- GET_COLL_DISPATCHED
With method SET_DISPATCH_IMMEDIATELY, the user implementing the BAdI receives the
information about whether the implementation was just called in a synchronous process or from
programm /LIME/DISPATCHER_EXEC. This information is important for a possible COMMIT
control within the BAdI implementation. In the case of a synchronous dispatcher call, a
COMMIT WORK should not be implemented within the implementation, as this can lead to
inconsistent and incomplete data. The COMMIT WORK is executed in this case by the calling
application.
The method SET_COLLECTION transfers the collections to be dispatched to the user who is
implementing the BAdI.
______________________________________________________________
SAP AG 300
SAP System
______________________________________________________________
The TAKE_NO_FROM_NORANGE and SET_DISPATCH_EXT_DOC methods provide the user

implementing the BAdI with a number range service. This is then useful when a
document-related link from the LIME inbound document to the document for the subsequent
application is required.
With method TAKE_NO_FROM_NORANGE, you can transfer the information that you want to
use this service, and with method SET_DISPATCH_EXT_DOC you will receive a number that
was determined for number range object /LIME/DIEX. This can then be transferred to the
subsequent application as an external number.
In method CALL, the call for the subsequent application or the actual sending of data to the
subsequent application is to be implemented.
The method GET_COLL_DISPATCHED is for returning the information to the calling program,
which collections could be sent successfully, and with which external document number this is
transferred to the subseqent application.
Requirements
In Customizing, the subsequent application (= collection type) must be activated for the process
type.
Standard settings
In the standard system, only one communication type is supported for each subsequent
application (collection type).
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 301
SAP System
______________________________________________________________
8. Choose Activate.
you wrote.
Example
See also
6.2.9 Physical Inventory
6.2.9.1 Basic Settings
6.2.9.1.1 Define Physical Inventory Area
Use
In this IMG activity, you make the settings for the physical inventory areas.
In the first step, physical inventory area, you define the physical inventory areas to be used
within the physical inventory. The system compares the physical inventory area specified in an
inbound document with this data.
You specify the following per physical inventory area:
- Whether a putaway physical inventory is allowed (once per PI period)
- Whether a low-stock/zero-stock physical inventory is allowed (once per PI period)
- Whether a low-stock/zero-stock check is to be carried out when the warehouse task is
confirmed
______________________________________________________________
SAP AG 302
SAP System
______________________________________________________________
- Whether the document is to be posted automatically after the count (this depends on the
user's allowed tolerance values)
- Whether the book inventory is to be proposed at the time of the count and at the time of
printout (does not apply to radio frequency environments
- Whether the product data is proposed in the case of the storage-bin- specific physical
inventory
- Whether it is allowed to count a handling unit as complete
- Whether the product data is included in printouts
- The threshold value for the low-stock physical inventory or check (in the case of the
zero-stock physical inventory or check, leave the field initial or zero)
In the second step, Permitted Document Types, you specify which physical inventory
procedures (e.g. continuous physical inventory, cycle counting) you are allowed to use per
physical inventory area.
The system compares the physical inventory procedure specified in the inbound document with
this data.
Standard settings
The permitted physical inventory procedures are fixed values.
6.2.9.2 Business Add-Ins (BAdIs)
6.2.9.2.1 Influencing Physical Inventory Processing
Use
/LIME/ES_PI_CUSTOMER.
______________________________________________________________
SAP AG 303
SAP System
______________________________________________________________
6.2.9.2.1.2 BAdI: Information About Activated Physical Inventory Document

Items
Use
This Business Add-In (BAdI) is used in the component Extended Warehouse Management
(SCM-EWM).
This BAdI informs you about successfully activated physical inventory document items. On the
basis of this information, your own data can be updated or follow-on actions started.
Standard settings
In the standard system, no BAdI implementation is activated.

The BAdI cannot be used multiple times.
Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_ACTIVA_INFO. For more information,
6.2.9.2.1.3 BAdI: Rejection of Physical Inventory Document Items to be

Activated
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the activation of physical inventory document items
on the basis of your own criteria (e.g. product or storage bin master data).
______________________________________________________________
SAP AG 304
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_ACTIVA_REJE. For more information,
6.2.9.2.1.4 BAdI: Influencing of Book Inventory Determination of a PI

Document
Use
(SCM-EWM).
With this BAdI, you can influence the determination of book inventory in the physical inventory
process. During the determination of the book inventory at the time of the physical inventory
count, an own book inventory can be set if the stock determined by the system does not agree
with the stock physically on hand.
Standard settings

Activities
______________________________________________________________
SAP AG 305
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface IF_EX_PI_CR_BOOK_QTY. For more information,
6.2.9.2.1.5 BAdI: Information About Changed Physical Inventory Document

Items
Use
(SCM-EWM).
This BAdI informs you about successfully changed physical inventory document items (change in
the count data). On the basis of this information, your own data can be updated or follow-on
actions started.
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_CHANGE_INFO. For more information,
______________________________________________________________
SAP AG 306
SAP System
______________________________________________________________

Changed
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the changing of physical inventory document items
(change in count data) on the basis of your own criteria (e.g. product or storage bin master
data).
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_CHANGE_REJEC. For more information,
6.2.9.2.1.7 BAdI: Information About Counted Physical Inventory Document

Items
Use
(SCM-EWM).
This BAdI informs you about successfully counted physical inventory document items. On the
______________________________________________________________
SAP AG 307
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_COUNT_INFO. For more information,

Counted
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the adoption of count data for individual physical
inventory document items on the basis of your own criteria (e.g. product or storage bin master
data).
Standard settings

Activities
______________________________________________________________
SAP AG 308
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface IF_EX_PI_CR_COUNT_REJECT. For more information,
6.2.9.2.1.9 BAdI: Setting the Count Date When Creating a Physical

Inventory Document
Use
(SCM-EWM).
When creating a physical inventory document, you can set or overwrite the (planned) count date
specified in the PI document on the basis of your own criteria.
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_CREATE_DATE. For more information,
6.2.9.2.1.10 BAdI: Information About Physical Inventory Document Items
______________________________________________________________
SAP AG 309
SAP System
______________________________________________________________
Created
Use
(SCM-EWM).
This BAdI informs you about successfully created physical inventory document items. On the
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_CREATE_INFO. For more information,
6.2.9.2.1.11 BAdI: Setting the Priority When Creating a Physical Inventory

Document
Use
(SCM-EWM).
When creating a physical inventory document, you can use this BAdI to change or reset the
physical inventory priority automatically determined from the reason for the physical inventory
according to your own criteria.
______________________________________________________________
SAP AG 310
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_CREATE_PRIO. For more information,

Created
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the creation of physical inventory documents on the
basis of your own criteria (e.g. product or storage bin master data).
Standard settings

Activities
______________________________________________________________
SAP AG 311
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface IF_EX_PI_CR_CREATE_REJEC. For more information,
6.2.9.2.1.13 BAdI: Information About Deleted Physical Inventory Document

Items
Use
(SCM-EWM).
This BAdI informs you about successfully deleted physical inventory document items. On the
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_DELETE_INFO. For more information,
______________________________________________________________
SAP AG 312
SAP System
______________________________________________________________
Deleted
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the deletion of physical inventory documents on the
basis of your own criteria (e.g. product or storage bin master data).
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_DELETE_REJEC. For more information,
6.2.9.2.1.15 BAdI: Information About Inventory Adjustment Postings
Use
(SCM-EWM).
This BAdI informs you about successfully activated and posted (automatically created) physical
inventory document items. On the basis of this information, your own data can be updated or
follow-on actions started.
______________________________________________________________
SAP AG 313
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_DOC_INFO. For more information,
6.2.9.2.1.16 BAdI: Rejection of Inventory Adjustment Postings
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the creation and posting of physical inventory
documents (automatic creation) on the basis of your own criteria (e.g. product or storage bin
master data).
Standard settings

Activities
______________________________________________________________
SAP AG 314
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface IF_EX_PI_CR_DOC_REJECT. For more information,
6.2.9.2.1.17 BAdI: Information About PRL Check Result
Use
(SCM-EWM).
This BAdI informs you about the result of a PRL check. Your own data can be updated or
follow-on actions started.
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_MRL_CHECK. For more information,
6.2.9.2.1.18 BAdI: Information About Posted Physical Inventory Document
______________________________________________________________
SAP AG 315
SAP System
______________________________________________________________
Items
Use
(SCM-EWM).
This BAdI informs you about successfully posted physical inventory document items. On the
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_POST_INFO. For more information,

Posted
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the posting of physical inventory document items on
the basis of your own criteria (e.g. product or storage bin master data).
______________________________________________________________
SAP AG 316
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_POST_REJECT. For more information,
6.2.9.2.1.20 BAdI: Information About Recounted Physical Inventory

Document Items
Use
(SCM-EWM).
This BAdI informs you about successfully recounted physical inventory document items. On the
Standard settings

Activities
______________________________________________________________
SAP AG 317
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface IF_EX_PI_CR_RECOUNT_INFO. For more information,

Recounted
Use
(SCM-EWM).
With this BAdI, you can prevent and reject the recounting of physical inventory document items
on the basis of your own criteria (e.g. product or storage bin master data).
Standard settings

Activities
See also:
This BAdI definition uses the interface IF_EX_PI_CR_RECOUNT_REJE. For more information,
______________________________________________________________
SAP AG 318
SAP System
______________________________________________________________
6.2.10 Configurable Process Scheduling
6.2.10.1 Scheduling Schema
6.2.10.1.1 Define Elements of Schema
Use
In this IMG activity, you can maintain the elements used to define scheduling procedures.
Standard settings
Elements are already provided by SAP in the SAP namespace. You can also use the customer
name spaces Y* and Z* for customer-specific definitions.
Activities
1. Create activity types for scheduling. Activity types are needed to model business processes
within scheduling.
For each activity type you can enter a description text and also a standard value for the
logical class that is used to delegate this activity.
2. Create date types for scheduling. Date types are used within a scheduling procedure to
model the start and end dates of activities.
3. Create activity categories for scheduling. These categories can be assigned to individual
activities within the definition of a scheduling procedure to group them logically. This
means it is possible that some services for scheduling do not run dependent on the activity
type, but rather dependent on the activity type category (for example, start date
determination).
4. Create the permitted logical classes for scheduling in which you assign an existing
ABAP-00 class to a technical (logical) class ID. You can enable each logical class for
different uses within scheduling. A logical class can only be used in scheduling procedures
if it has been enabled for this purpose.
6.2.10.1.2 Define Schema
Use
In this IMG activity, you can maintain scheduling procedures. A scheduling procedure is used
within a process definition. You use the procedure to control the behavior of scheduling. For
example, you can control the determination of master data relevant to scheduling (durations,
calendar, and time zone) for the activity types used.
______________________________________________________________
SAP AG 319
SAP System
______________________________________________________________
Requirements
A scheduling procedure uses activity types, date types, activity type categories, and logical
classes. These elements must already have been maintained.
Standard settings
SAP already provides scheduling procedures in the SAP namespace. For customer-specific
definitions you can use the following customer namespace: Y* and Z* for entities and
0*,1*,2*,3* and 4* for the access priority.
All data records provided by SAP have an access priority of greater than or equal to 50. You
can define your own data records with an access priority less than 50, which will be evaluated
before the data records provided by SAP. This enables you to override the prioritization
designed by SAP for the different determination methods.
Activities
1. Maintain the activity types that are to be used in a procedure. For each activity type, you
can assign an activity type category and the date types for the start or end date of the
activity. Note that a date type can only be used once within a procedure as the date for
an activity. This means that the date types used for these activity dates are unique within a
procedure.
For each activity type of the procedure, you can define a default value for the logical
class that is used to made a delegation for this activity. You can maintain a control
parameter for determining the logical class of the delegation for each activity type.
2. You can define a list of derived date types for each procedure. You use these derived date
types to integrate scheduling with another application purely on the basis of dates, without
the application having detailed knowledge about the activity types in the process. Note that
a date type can only be used once as a derived date type in a procedure. This means that
the derived date types are unique within a procedure. You can use the same date type both
for an activity date and for a derived date.
3. You can maintain property information for a procedure. Scheduling receives interface data
from a calling application in the form of a list of properties. A property is a data record
consisting of a property name and a property value. You can use a property transformation
to transfer the value of a property that was sent using the application interface (external) to
the value of an (internal) property with a different property name. You can also derive
internal properties from the list of all external properties by using a logical class. If you
maintain a logical class and an external property in a data record, the system uses the
logical class.
You can maintain several data records for the same internal property with different access
priorities. The system works through all data records on the basis of their access priority
until an access is successful. Any data records that might exist with a higher access
priority are not taken into account.
The system automatically converts all the (external) properties transferred using the interface
into internal properties.
You can use all internal properties in the following process steps.
4. You can assign a special property both for the start and end of the activity for each
______________________________________________________________
SAP AG 320
SAP System
______________________________________________________________
activity type. These two properties are intended to contain the keys for the location,
partner, or related entities. The value of the two properties (that is of both locations) can
also be identical.
You can maintain location determination by defining an internal property that contains the
location key as a property value. You can also maintain a logical class that takes over
location determination. If you maintain an internal property and a logical class in a data
record, the system uses the logical class.
In each case, you can maintain multiple data records with different access priorities. The
system works through all data records depending on their access priority until an access is
successful. Any data records that might exist with higher access priorities are not taken
into account.
The properties (locations) that are determined for the start and end of the activity are
available within duration, calendar, and time zone determination if this is done using a
logical class. They are also available within delegation determination.
5. You can maintain internal properties that are required for the subsequent determination of
master data. If you maintain data records for master data derivation, you can assign logical
classes that are then used to determine an internal property if it is not yet known. An
internal property is already known if it is transferred from the application using an external
property or if it was already derived using a property transformation.
In each case, you can maintain several data records with different access priorities. The
system works through all data records on the basis of their access priority until an access
is successful. Any other data records that might exist with higher access priorities are not
taken into account.
6. You can maintain duration determination for each activity type by defining an internal
property that contains the duration of the activity as a value. You have to fill the value of
this property in accordance with the /SCMB/SC_DURA_PROPVALUE structure. You can
also execute duration determination by using a logical class. If you maintain an internal
property and a logical class in a date record, the system uses the logical class.
In each case, you can maintain several data records with different access priorities. The
system works through all data records on the basis of their access priority until an access
is successful. Any other data records that might exist with higher access priorities are not
taken into account.
7. You can maintain calendar determination for each activity in the same way as for duration
determination. You have to fill the value of a property that is used for calendar
determination in accordance with the /SCMB/SC_CAL_PROPVALUE structure.
8. You can maintain time determination for each activity in the same way as for duration
determination.
9. You can maintain delegation determination in the same way as for duration determination.
Note that the system only uses this delegation determination if you have set the control
parameters for delegation determination in the activity in such a way that the system uses
dynamic determination.
10. You can maintain subnetwork determination in the same was as duration determination. A
subnetwork is a subflow modeled in a process definition that is assigned to a process
activity. Subnetwork determination controls whether the activity itself is used within
scheduling or whether it is substituted by a subflow. This enables you to model and
schedule a business process at different levels of detail.
______________________________________________________________
SAP AG 321
SAP System
______________________________________________________________
6.2.10.1.3 Assign External Date Descriptors
Use
In this IMG activity, you can assign an external date descriptor from another business system to
date types that are used within a scheduling procedure. The allows the configurable process
scheduling to be integrated with other (external) applications in a heterogeneous system
landscape. Scheduling provides an application programming interface (API) which can be used to
make these assignment relationships available to the applications. The applications are therefore
able to convert external date descriptors to date types of configurable process scheduling.
Requirements
You must already have maintained a scheduling procedure.
Activities
You can assign an external date descriptor for a business system to the start or end date of an
activity of a procedure.
6.2.10.2 Units of Time
6.2.10.2.1 Define Units
Use
In this IMG activity, you can maintain time units. This involves assigning an ABAP-OO class
to a time unit ID. This ABAP-OO class manages all time calculations that have to be executed
in this time unit.
You can assign data types to time units in process scheduling. This means that the time unit is
preset for the results date for scheduling. The system also uses time units to define the time
duration of an activity. In accordance with the time unit of the duration of an activity, the
system uses another ABAP-OO implementation for the basic date calculation. The
implementations provided by SAP differ as follows:
- For time units less than a day, the system calculates the (net) duration of the activity
along the time stream of the activity. This time stream allows you to map work definitions
of less than a day (down to the level of seconds).
______________________________________________________________
SAP AG 322
SAP System
______________________________________________________________
- For the day time unit, the system calculates the (net) duration along the factory calendar
of the activity.
- For time units greater than a day, the system does not take working time or the calendar
into account.
If you create and use your own time units, you can influence scheduling in your core functions,
particularly if you are also using your own ABAP-OO implementations.
Requirements
ABAP-OO classes that implement the IF_TIMEUNIT_CALC interface must exist.
Standard settings
SAP already provides time units in the SAP namespace. The customer namespaces X* and Y*
also exist.
Activities
1. Maintain the assignment of a time unit ID to an existing ABAP-OO class.

2. Also maintain the (language dependent) singular and plural names.
6.2.10.2.2 Assign Units
Use
In this IMG activity, you can maintain time unit assignment sets. A set consists of a number of
date types and the assignment of a time unit to each date type.
You can use a time unit assignment set within scheduling to preset the time unit for the results
dates. If a time unit is preset for a date, the system rounds the results dates to the relevant
time unit by taking into account the time zone of the activity. For example, the result of a date
type with the unit "day" is a day in the local time zone of the activity.
Requirements
If you want to use additional units to those provided by SAP, you need to maintain these
beforehand.
Standard settings
Time unit assignment sets are provided by SAP in the SAP namespace. The customer
namespaces Y* and Z* are also available.
______________________________________________________________
SAP AG 323
SAP System
______________________________________________________________
Activities
1. Create a technical key for a set and a (language-dependent) set name.

2. Assign a number of date types to the set and specify the time unit for each date type.
6.2.10.3 Process Definition
6.2.10.3.1 Simple Process Maintenance
Use
In this IMG activity, you can model a business process to be used within scheduling. A
simplified SAP workflow editor that only allows a restricted number of step types for modeling
is used to define this scheduling process model.
The scheduling process model consists of a number of activities and their chronological
relationships (predecessor/successor relationships).
The process definition refers to an existing scheduling agreement that contains all activities of
the process definition. The process definition can (optionally) refer to a time unit assignment
set.
Requirements
You must already have maintained a scheduling agreement.
Standard settings
SAP already provides process definitions in the SAP namespace that are used within SAP
applications. Customer-specific definitions can use the customer number range of the workflow
prefix numbers.
SAP provides task TS79400001 that can be used for step definition.
Activities
1. Under Basic Data -> Version-Dependent -> Properties, maintain the reference to a
scheduling procedure by creating a property with the name sap.scm.bas.sch.scheme and
entering the key of a scheduling agreement as the property value.
2. Under Basic Data -> Version-Dependent -> Properties, you can maintain the reference to
a time unit assignment set by creating a property with the name sap.scm.bas.sch.timeunitas
and entering the key of an assignment set as the key.
3. Create one or more steps of the workflow. If the workflow is only to be used for process
scheduling, it is not instanced and is not processed by the workflow engine. This means
______________________________________________________________
SAP AG 324
SAP System
______________________________________________________________
that a task to be executed is not necessary for the steps. In this case, you can assign task
TS79400001 to the workflow steps. This task is an auxiliary task without an actual
process.
If a step is relevant for scheduling, create a property with the name

sap.scm.bas.sch.actitype for this step and assign the property to the key of an activity as a
value. This makes the step into an activity of the process model used in scheduling. Note
that you have to define this activity within the process defined in the basic data. The
process definition in the workflow editor that is in the form of a network of steps is
converted into a process model within scheduling that only contains the steps (activities)
relevant to scheduling.
You can assign a workflow that has already been defined to a workflow step as a task.
This allows top down modeling of the process used for scheduling. Ensure that you have
assigned the same scheduling agreement as a property in your basic data for all
hierarchically linked workflows. Scheduling supports a deep hierarchy of subworkflows.
If a step does not have the property sap.scm.bas.sch.actitype but does have a workflow
assigned as a task, this workflow is expanded in scheduling and the steps relevant to
scheduling are used as activities in the scheduling process model.
If a step has the property sap.scm.bas.sch.actitype and also has a workflow assigned as a
task, you can use the subnetwork determination of the procedure definition to control
whether the step itself is used for scheduling or whether the subworkflow is used.
If you include a subworkflow containing steps that are not relevant to scheduling, it may
be necessary to mark up to two steps that are relevant to scheduling explicitly as inbound
or outbound activities of this subflow. You do this by maintaining the inbound/outbound
activity for the property sap.scm.bas.sch.sacti or sap.scm.bas.sch.eacti at the workflow
step. These activities are then connected to the inbound and outbound edges that the
superordinate step possesses in the superordinate workflow. In simple cases, the system can
determine the inbound and outbound activity itself. This is the case for workflows that only
consist of a linear sequence of steps. In general, however, determination by the system is
not possible. In particular, complex workflows that also contain steps that are not relevant
to scheduling may require the explicit marking of inbound and outbound activities. This
especially applies when the scheduling process model derived from the subworkflow has
several activities without an inbound edge (that is, several potential inbound activities). The
same applies for outbound activities.
Note that the resulting scheduling process model must be free of cycles. A cycle exists when
activity A1 is connected to two successor activities A2 and A3 and these are both connected to
the same successor activity A4. The workflow itself is allowed to have cycles (for example, due
to the step types "Split" and "Join"). In modeling, you can assign the property
sap.scm.bas.sch.skip to a workflow step. As a result, this step (and all its connection edges to
other steps) is ignored for the creation of the scheduling process model. You can then use it to
model cycle-free scheduling process models.
______________________________________________________________
SAP AG 325
SAP System
______________________________________________________________
6.2.10.3.2 Maintain Process
Use
In this IMG activity, you can model a business process that you want to use within scheduling.
The scheduling process model is defined here using an SAP workflow editor.
For more information, see the documentation for the IMG activity Simple Process Maintenance.
6.2.10.3.3 Define Process Alias
Use
In this IMG activity, you can define process (alias) names. Process scheduling can then use this
process name instead of using the explicit identification of a workflow.
You can add a language-dependent process ID to the process name. The process ID can be
used in the user interface (for example, in the scheduling log) to display the scheduling process
model being used.
Requirements
You must already have maintained a workflow that contains the scheduling process model.
Standard settings
SAP already provides process names in the SAP namespace. You can also maintain your own
process (alias) names in the customer namespaces Y* and Z*.
Activities
Create a data record with a (technical) alias name and assign this an identification of a
workflow that already exists. You can also maintain a (language-dependent) process ID.
______________________________________________________________
SAP AG 326
SAP System
______________________________________________________________
6.2.10.4 Calendar and Time Zones
6.2.10.4.1 Maintain Calendar
The public holiday and factory calendar is a central module in the SAP System. It is used in
many areas (e.g. in Logistics and in Human Resources) in the standard version.
You can use calendar maintenance to maintain and display the components of the calendar
system. The public holiday and factory calendar data calculated from calendar maintenance is
directly available to the system.
You can only change the holiday and factory calendar in the clients setup for them. The client
must have the "Customizing" role and the "Repository and cross-client Customizing changes
allowed" attribute. You must have maintenance authorization for the calendar.
A factory calendar is allocated to your plant via another Customizing function.
The calendar system consists of the following components:
- Public holidays
Definitions for public holidays: Calculation rule for date, religious denomination etc.
- Public holiday calendar
Any composition of public holiday rules.
- Factory calendar
Definition of workdays including special regulations, under the assignment of a particular
public holiday calendar.
Standard settings
The system delivers definitions of all common public holidays and public holiday rules, as well
as a standard factory calendar.
A main memory area of 400000 Bytes is reserved for calendar data in the standard version.
This is the mimimum buffer size, which you should not go under.
Activities
Check whether all the definitions for public holidays and public holiday rules that you need are
available in the sytem. If necessary, maintain the public holiday definitions and copy them to
new or existing public holiday rules.
Create factory calendars if necessary.
Public holidays
Check that existing public holidays are complete, and create new definitions if required:
1. Double-click with the mouse on the Execute symbol, select the option Public holidays and
choose the function Display.
2. Check whether the list of public holidays displayed contains all the public holidays that you
______________________________________________________________
SAP AG 327
SAP System
______________________________________________________________
need.
If you want to see detailed information on any public holiday, choose the function Display
def.
3. If you need other public holidays, return to the initial screen of the maintenance
transaction, and choose the function Change.
4. Choose the function Insert, and now make the following entries:
- Public holiday type
- Date or calculation rule
- Public holiday text (short and long)
- If required: Sort criterion, religious denomination or public holiday class (for notes on
this, press the F1 Help).
Save the definition.
Public holiday calendar
Combine the public holidays you require in a public holiday rule in the public holiday calendar:
2. Check whether all the public holiday rules that your require are available.
To get the definitions for a public holiday calendar, position the cursor on it and choose
the function Display def..
3. If you need other public holiday calendars or would like to change existing ones, return to
the initial screen of the maintenance transaction and choose the function Change.
4. To create a public holiday calendar, choose the function Insert (to change a public holiday
calendar, position the cursor on it and choose Change), and make the following entries:
- Calendar ID and a descriptive short text
5. Using the function Assign public holidays, generate a complete list of defined public
holidays.
6. Select the public holidays you need, and choose Assign public holidays.
Factory calendar
Define a factory calendar including the relevant public holiday calendar:

2. In calendar maintenance, select the option "Factory calendar", and choose the function
Change.
3. Choose the function Insert and make the following entries:
______________________________________________________________
SAP AG 328
SAP System
______________________________________________________________
- Factory calendar ID and a descriptive short text

- Public holiday calendar ID
- Start no. factory date
Number from which the factory date is incremented for each workday.
If you do not make an entry, the default value is "0".
4. Decide which days of the week are meant to be workdays.
5. Define special rules if necessary (e.g. plant holidays).
Further notes
- Calendar buffer
If you want to increase the size of the calendar buffer, maintain the parameter
zcsa/calendar_area with the maintenance transaction for system profiles. Restart the system
for the value to take effect.
- Transport
Changes to calendar data are not automatically included in a correction request.
For the calendar data to be utilizable in another system, use the function Transport in the
initial screen of the maintenance transaction.
Note that you cannot transport individual public holidays or calendars. You can only
transport calendar data in its entirety. When you do this, all public holidays, public holiday
and factory calendars existing in the target system are deleted.
6.2.10.4.2 Maintain Process Scheduling Calendar (Time Stream)
Use
In this IMG activity, you create a time stream that is used as a basis for process scheduling.
The time stream can be set up with weekly or monthly periods.
Activities
1. Enter a unique name for the time stream and choose Create.
2. Enter a short description for the time stream.
3. Enter the number of years into the past that the time stream should apply. This setting is
optional.
4. Enter the number of years into the future that the time stream should apply.
Note
______________________________________________________________
SAP AG 329
SAP System
______________________________________________________________
If you do not enter a value here, the system only takes the current year into account.
5. Use input help to select the time zone that is assigned to this time stream. The system
interprets all other entries that you make in this time stream maintenance together with this
time zone.
6. Select one of the following options:
- Working time calendar (with gaps)
- Working time calendar (without gaps)
7. Use input help to select a predefined calendar. Note that the system interprets this calendar
together with the time zone that you have already entered. This means that the days of
this calendar are interpreted as local days in the time zone that has been maintained.
8. Choose the calculation rule to specify the periods for this time stream.
9. Select the required time interval (week or month). A weekly or monthly interval is
displayed depending on the selection made.
10. The information that you enter in this next step depends on whether you have chosen a
weekly or monthly time interval:
If you have chosen a weekly interval, you assign the periods the numbers 1-7 (1 for
Monday, 2 for Tuesday, and so on) and enter the required times.
If you have chosen a monthly interval, assign the numbers 1-5 in the first column for the
weeks of the month and the numbers 1-7 in the second column for the days of the week.
You also enter the required times.
Note that the system interprets the (work) times together with the time zone that you have
already maintained.
11. Choose the "Periods" pushbutton to generate periods. You always have to regenerate the
periods when you change the calculation rules.
12. Choose Save.
6.2.10.4.3 Time Zones
6.2.10.4.3.1 Maintain System Settings
In this activity, you configure the following settings for the time zones:
- System time zone
- Standard time zone for users
System time zone

The system time zone is comparable to the time zone of your operating system. It applies to all
______________________________________________________________
SAP AG 330
SAP System
______________________________________________________________
clients. If you change the system time zone in one client, the new value is automatically copied
to all other clients.
If you specify the system time zone, the SAP System can calculate the local time from a UTC
time.
Standard time zone for users

Via the standard time zone, you specify the local time zone of a user in a client. This
specification is only used, however, if no personal time zone is maintained in the user defaults.
The standard time zone is not changed on a cross-client basis. It can vary from client to client.
Requirements
Befor you configure your settings in the system, you should check in the workstep Maintain
Time Zone whether the time zone you require exists. If the time zone does not exist, you
create this in the workstep Maintain Time Zones , and you pass on a customer message to
SAP.
Standard settings
If you are logging on to an SAP System for the first time, the system time zone is determined
automatically. You should check this value, howe ver, since a unique assignment is sometimes
not possible.
So that the time zone function becomes active, the system automatically sets the indicator Time
Zone Active.
The fields Change Allowed and Delete Allowed are no longer in use since Release 4.6D.
6.2.10.4.3.2 Maintain Time Zones
In this activity all the time zones that are available will be displayed . You create those time
zones that do not yet exist.
______________________________________________________________
SAP AG 331
SAP System
______________________________________________________________
Standard settings
Since the standard time zones are deliverd with the SAP System, you no longer need to
maintain these. All the time zone and daylight saving rules are included in the delivery
package.
However, you should check the time zone tables for your area in order to ensure that the
talbes do not contain errors (e.g. on the basis of changes to regional laws). If a time zone is
missing, send a customer message to SAP.
Activities
If you wish to create a new time zone, you must first determine the time zone rules and the
daylight saving rules, and then define the time zone. Proceed as follows:
1. Define the variable daylight saving time rules or the respective fixed daylight saving time
date.
2. In the overview screen Daylight saving rules, define the time shifts caused by the daylight
saving time.
3. Then, in the overview screen Zeit zone rules , define the time shifts caused by the time
zones.
4. In the overview screen Time zones define the time zone key.
5. If you have filled the individual tables, save your data.
6. Return to the activity Maintain system settings, and execute the remaining steps there.
6.2.10.4.3.3 Maintain Geographical Assignments
In this activity, the system displays all the countries that are assigned to a time zone.
Geographical assignments that do not exist can be created.
You can perform geographical assignments at
- Country level
- Regional level
- Postal code level
When assigning a country to a time zone, make sure that the country key provided by SAP is
used.
______________________________________________________________
SAP AG 332
SAP System
______________________________________________________________
Requirements
Before you create new geographical assignments, you must first define the time zone in your
system.
Standard settings
Since the geographical assignments are supplied with the SAP system, you no longer need to
maintain these assignments.
However, you should check your own geographical areas to make sure that they do not contain
any errors. If a geographical assignment is missing, enter a customer message and pass it on to
SAP.
6.2.10.5 Master Data for Activities
6.2.10.5.1 Assign Calendar
Use
In this IMG activity, you can maintain the calendar and time stream depending on the following
criteria:
- Activity type category
- Activity type (if the category is maintained as indefinite)
- Activity type category and activity type
- Activity type category, activity type, and two properties.
These two properties of an activity correspond to the properties for the start and end of
the activity that are assigned using location determination for the activity as specified in the
scheduling procedure.
SAP provides the logical class TSTR_SC as a procedure element. This enables the master data
maintained here to be accessed. If you use this class in calendar determination for a procedure,
the system uses the master data maintained here for scheduling. If you use the logical class
TSTR_SC, you can influence the master data access by also providing the value for the internal
property in the data record of calendar determination as follows:
- For a property value ACAT, the access to the stored master data is made using only the
activity type category as the key. If you are using this, you should maintain only one
master data record for each activity type category.
______________________________________________________________
SAP AG 333
SAP System
______________________________________________________________
- For a property value ACTI, the access to the stored master data is made using only the
activity type as the key. If you are using this, you should maintain only one master data
record for each activity type.
- For a property value ACAT_ACTI, the access to the stored master data is made using
only the activity type category and the activity type as the key. If you are using this, you
should maintain only one master data record for each combination of activity type category
and activity type.
- For all other property values, the access is made with the full key of activity type
category, activity type, and the two properties.
Requirements
The calendar and time streams must already have been maintained if you want to use them in
this master data maintenance.
Standard settings
No data records are provided by SAP.
Activities
Use input help on the entry screen to maintain a time stream and a calendar dependent on the
keys mentioned above. Note that you can use all time streams that are available locally in the
system and not just those that were created using time stream maintenance in process
scheduling. Other time streams that exist are defined using different maintenance dialogs in
other applications.
6.2.10.5.2 Assign Time Durations
Use
In this IMG activity you can maintain time durations in the same way as for calendar
maintenance.
In the same way as for class TSTR_SC, SAP provides the logical class DURA_SC as a
procedure element. See also the notes and details in the Maintain Calendar IMG activity.
Requirements
You must already have maintained the time units to be able to use them here.
______________________________________________________________
SAP AG 334
SAP System
______________________________________________________________
6.2.10.5.3 Assign Time Zones
Use
In this IMG activity you can maintain time zones in the same way as for calendar maintenance.
In the same way as for class TSTR_SC, SAP provides the logical class TZON_SC as a
procedure element. See also the notes and details in the Maintain Calendar IMG activity.
Requirements
You must already have maintained the time zones to be able to use them here.
6.2.10.6 Scheduling Log
6.2.10.6.1 Find, Display, and Delete Logs
Use
In this IMG activity, you can delete log data for process scheduling and display scheduling
logs.
If you save scheduling logs to the database (for example, using the scheduling test tool), you
should clean up your database on a regular basis by deleting old logs that you no longer need.
Activities
1. On the entry screen, choose one of the three options for preselecting the logs:
- Selection by entering the posting date and time of a log
- Selection by entering a value range for the posting date of the log
- Selection by entering a value range for the technical key of the log
2. Execute the program. A list of the selected logs is displayed.
3. To display a log, select a log from the list and choose "Display Log".
4. To delete a log, select a log from the list and choose "Delete Logs".
______________________________________________________________
SAP AG 335
SAP System
______________________________________________________________
6.2.10.7 Condition Technique
6.2.10.7.1 Create Field Catalog
Use
In this IMG activity, you can make settings for the field catalog.
The field catalog contains the fields permitted for the definition of condition tables.
Field catalog maintenance is organized in three screen areas:
- Field catalog area
- Detail area for field and data element (can be shown/hidden)
- Detail area for the log (can be shown/hidden)
Field Catalog Area
The field catalog area is the main component of field catalog maintenance. You can edit fields
or create new ones here.
Detail Area for Field and Data Element
You can maintain the detail area exclusively for a selected field from the field catalog area, and
for which you have selected the detail function (magnifying glass symbol).
Detail Area for the Log
In the detail area, the system displays the application log that it wrote when it last called the
transaction when saving or generating.
The standard functions of the application log are available.
The logs are saved under the following object of the application log: COND_TECHNIQUE
(subobject FIELD_CATALOGUE).
You can use transaction SLG1 (evaluate application log) to display all logs. You can use
transaction SLG2 (Application Log: Delete Expired Logs) to delete logs that are no longer
needed.
______________________________________________________________
SAP AG 336
SAP System
______________________________________________________________
6.2.10.7.2 Define Condition Tables
Use
In this IMG activity, you create condition tables. You use a condition table to define the
combination of the fields that are to make up the individual condition record. The number of
fields used for a condition table is limited to 10.
The condition table consists of a combination of search and result fields.
The system can use the search fields to search for condition records later. You can define the
search fields as you choose.
The results fields are fixed and are not displayed when a condition table is created. If
necessary, you can enhance these fixed fields with fields that you designate as non-search fields.
According to the condition table used, the condition contains the specific condition data that you
have specified.
SAP Recommendation
You should not change the condition tables that are contained in the SAP standard system.
Activities
To create a condition table, proceed as follows:

1. Before you create a condition table, you should check whether the existing field catalog
fields suffice. If you would like to use a field that is not provided in the SAP standard
system, you need to copy it into the field catalog.
2. Enter the name of the table that you would like to create. Note that the name must begin
with CUS, and that you can specify a maximum of 5 characters.
3. Select 'Change' and specify a short description for the condition table. If you do not
specify a description, a short description is generated from the field name of the table
when you save it.
4. Select the desired fields for the condition table from the list of fields that exist in the field
catalog.
5. Activate the new condition table.
6. Specify the condition tables in the access sequences. By doing so, you create a connection
between the determination procedure, the condition type, the access sequence, and the
condition record.
______________________________________________________________
SAP AG 337
SAP System
______________________________________________________________
6.2.10.7.3 Define Access Sequences
Use
In this IMG activity, you define access sequences.

Access sequences are search strategies that the SAP system uses to search for valid
determination strategies for a condition type.
Each condition table contains a certain combination of fields, for which the system is to search
in the condition records. The search sequence should proceed from special to general condition
records.
You can use the indicator exclusive condition access to specify that the system stops the access
sequence in further condition types once it has successfully accessed a valid condition record.
Evaluation of the logical conditions is executed after determination itself. For this reason, a
condition record is not always found in some processes.
Activities
1. Check the extent to which you can use the access sequences that are contained in the SAP
standard system.
2. Create new access sequences. The namespace for customer-specific entries is A* to Z* and
8*, 9*.
3. Maintain the accesses for the access sequence, by specifying the condition tables in the
desired sequence. To do this, select your new access sequence and select accesses. You
use the sequence to determine the priority of the accesses.
4. Select the new accesses consecutively and select Fields. You use the access type to
determine whether a field in the fixed or free key part is concerned. If an optional key
field is concerned (field in the free key part), you must also define the evaluation priority.
Use
In this IMG activity, you use the condition type to determine the properties, field combinations
and business meaning of condition records. You specify an access sequence in each condition
type, which you use to determine the fields the SAP system searches after a valid determination
record (condition record).
______________________________________________________________
SAP AG 338
SAP System
______________________________________________________________
You always define determination records for a condition type.
Activities
1. Check to what extent you can use the determination procedures contained in the SAP
standard system.
2. Create the new determination type. The namespace for customer-defined entries is A* to
Z*, and 8*, 9*.
3. Specify an alphanumeric key of up to four places for the determination type. Then define a
description.
4. Specify an access sequence for the determination type.
5. If necessary, specify a date proposal when creating condition records.
6.2.10.7.5 Define Determination Procedure
Use
The determination procedure defines the condition types that are to be used in the determination
process. With the aid of the sort characteristics level and counter, you define the sequence of
the condition types. Upon invocation of the determination function, the system processes the
condition types in the order of these sort characteristics.
You still have the option of linking the determination of condition types to conditions.
Activities
1. Create the new determination procedure. The namespace for customers' own entries is A*
to Z* and 8*, 9*.
2. Specify an alphanumeric key for the determination type, which can be up to 6 characters
in length. Also enter a description.
3. Maintain the search sequence for the condition types by specifying them in the desired
order. To do so, select your new determination procedure and choose Elements of
Determination Procedure. With the level number, you define the sequence of the
accesses.
______________________________________________________________
SAP AG 339
SAP System
______________________________________________________________
6.2.10.7.6 Determine Condition Maintenance Groups for Context
Use
In this activity, you determin the condition maintenance groups for a context.
6.2.10.7.7 Create Condition Maintenance Group
Use
The condition maintenance group combines condition tables and condition types for condition
maintenance.
Additional Information
Note that an enhancement to the condition maintenance groups provided by SAP constitutes a
modification.
6.2.10.7.8 Assign Schema and Activity to a Determination Schema
Use
In this IMG activity, you can define the following:

- Determination of durations, calendars, or time zones
In this IMG activity, you can assign a scheduling schema and anactivity type to a
determination schema. Via this assignment, configurable process scheduling can determine
durations, calendars, or time zones.
- Determination of a process alias (ATP-specific)
In this IMG activity, you can define that the system is to determine the process alias using
the condition technique. Determination takes place on the basis of the determination
______________________________________________________________
SAP AG 340
SAP System
______________________________________________________________
procedure for the application scheduling and the use process alias.
If the system finds a process alias using the condition technique, calculation of dates/times
does not take place via transportation and shipment scheduling, but via configurable process
scheduling. In the same way, the system does not use the results and log display of
transportation and shipment scheduling, but the log display of configurable process
scheduling.
If the system finds a process alias using the condition technique then it does not consider
the process alias that you have defined in the Customizing of Global ATP under
Assignment of Item Category to Process Alias. Determination of the process alias using the
condition technique also has a higher priority than determination of the process alias by
assigning an item category.
Note that the process alias found must conform to the scheduling schema SCHEDL.
For more information about configurable process scheduling and the process alias, see SAP
Supply Chain Management (SAP SCM) -> SCM Basis -> Configurable Process Scheduling ->
Scheduling Schema or Process Definition in the SAP Library.
For more information about scheduling using configurable process scheduling, see SAP Supply
Chain Management (SAP SCM) -> SAP Advanced Planning and Optimization (SAP APO) ->
Global Available-to-Promise (Global ATP) -> Transportation and Shipment Scheduling ->
Scheduling Using Configurable Process Scheduling in the SAP Library.
Requirements
- You have defined the following data in configurable process scheduling:

- Scheduling schema
For more information, see Define Elements of Schema, Define Schema and Assign
External Date/Time Descriptors in the Implementation Guide (IMG) of SCM Basis.
- Process alias
For more information, see Simple Process Maintenance, Maintain Process and Define
Process Alias in the IMG of SCM Basis.
You can only define one process alias and thus one scheduling schema that conforms to
the scheduling schema SCHEDL.
- You have set the following in the schema definition for the related scheduling schema and
the related activity type:
- If you would like to determine durations using the condition technique, you need to
have specified the logical class DURA_COND under Duration Determination.
- If you would like to determine calendars using the condition technique, you need to
have specified the logical class TSTR_COND under Calendar Determination.
- If you would like to determine time zones using the condition technique, you need to
have specified the logical class TZON_COND under Time Zone Determination.
For more information, see Define Schema in the IMG of SCM Basis.
- You have made the following condition technique settings:
- You have created a field catalog. (Transaction /SAPCND/CTFC)
- You have created one or more condition tables. (Transaction /SAPCND/CTCT)
- You have created one or more access sequences. (Transaction
______________________________________________________________
SAP AG 341
SAP System
______________________________________________________________
/SAPCND/CT_ACC_SEQ)
- You have created one or more condition types. (Transaction
/SAPCND/CT_COND_TYPE)
- You have created one or more determination procedures. (Transaction
/SCWM/CT_DET_PROC)
- You have registered the condition tables created under the defined condition
maintenance group. (Transaction SM34 for view cluster /SAPCND/VC_GROUP)
- You have defined a condition maintenance group for the maintenance context GCM
(Transaction SM30 for view /SAPCND/V_CNT_GR)
- You have created condition records. (Transaction /SAPCND/GCM)
Activities
Make the settings to determine a determination procedure:

1. Choose scheduling schemas.
2. Choose activity types.
3. Choose the application scheduling.
4. Choose one of the following uses: Calendars, Durations Time Zones, Process Alias.
If you choose the usage Process Alias, you must not specify a scheduling schema or a
scheduling activity.
5. Choose condition type lists.
Note (ATP-specific)
The new condition technique is used within configurable process scheduling. In this way, the
system does not consider any condition data that you have created using the old condition
technique for transportation and shipment scheduling.
6.2.10.8 Interfaces
6.2.10.8.1 Maintain Transportation Zone
In this process step you can define transportation zones corresponding to your site and country.
Transportation zones represent the regional zone of the ship-to party, who receives delivery of
goods, or the regional zone of the vendor who delivers the ordered goods.
Use
You can assign the transportation zones maintained here to locations. You carry out the
assignment in IMG activity Define Assignment of Transportation Zones to Locations.
______________________________________________________________
SAP AG 342
SAP System
______________________________________________________________
This enables scheduling to find the locations that it needs in order to determine
scheduling-relevant data, for example:
- Transportation lane between source location and target location
- Distance between source and target location
- Shipping and recipient calendar for the locations
Example
You can define the transportation zones, for example, corresponding to the postal code system
of a country.
Activities
Per country, define the transportation zones you require and enter the corresponding name.
Next, assign the transportation zones to locations.
To be able to find a transportation lane you must assign means of transport to shipping
conditions. You make this assignment in IMG activity Define Assignment of Default Means of
Transport to Shipping Conditions.
6.2.10.8.2 Define Assignment of Transportation Zones to Locations
If you want to work with a ship-to party, for example, for which a location has not been
created, you can use the transportation zones in scheduling. To do this, you assign
transportation zones and countries from the calling or predecessor system to locations in SAP
APO. This means that you can use the same location for all ship-to parties in the calling or
predecessor system.
The system finds this location automatically and uses it during scheduling to determine the
transportation lane between source and destination location and to determine the distance.
If no geographical coordinates are assigned to the location, the system tries to derive the
geographical coordinates from the additional location data by using the coordinates from the
transportation zone, for example.
______________________________________________________________
SAP AG 343
SAP System
______________________________________________________________
Activities
Assign the country and transportation zone of the calling or predecessor system to a location.
6.2.10.8.3 Define Assignment of Default Means of Transport to Shipping

Conditions
In this IMG activity, you assign default means of transport to shipping conditions.
Scheduling uses the means of transport to determine the transport duration of the transportation
lane as well as the transportation distance. The following additional factors are also relevant:
- Where the locations are situated
- Distance surcharge (as the crow flies)
- The average speed (dependent on the type of means of transport)
Requirements
The shipping conditions must be maintained uniformly in all calling or predecessor systems.
Recommendation
You should create an entry in which you specify a means of transport but no shipping
condition. The system uses this means of transport if no shipping condition has been passed on.
6.2.10.8.4 Perform Consistency Check
With this IMG activity, you can check the Customizing entries which you have entered for the
transportation and shipment scheduling interfaces.
______________________________________________________________
SAP AG 344
SAP System
______________________________________________________________
Further notes
For more information, see Report Documentation.
6.2.10.8.5 Determine Assignment of Item Category to Process Alias
Use
In this IMG activity, you assign an item category to a process alias if you want to use
configurable process scheduling within the global availability check. If the system finds a
process alias for an item category, the calculation of the dates/times is not carried out by
transportation and shipment scheduling but with the configurable process scheduling. Also, in
this case the system does not use the result and log display of transportation and shipment
scheduling but the log display of configurable process scheduling.
Note that assignment of the item category to the process alias is ignored if the system has
previously found a process alias using the condition technique. For more information, see
Assign Schema and Activity to a Condition Type List in the Implementation Guide of SAP
APO.
For more information about the process alias and configurable process scheduling, see SAP
Supply Chain Management (SAP SCM) -> SCM Basis -> Configurable Process Scheduling ->
Process Definition in the SAP Library.
For more information about scheduling using configurable process scheduling, see SAP Supply
Chain Management (SAP SCM) -> SAP Advanced Planning and Optimization (SAP APO) ->
Global Available-to-Promise (Global ATP)-> Transportation and Shipment Scheduling ->
Scheduling Using Configurable Process Scheduling in the SAP Library.
Requirements
You have defined the following data in configurable process scheduling:

- Scheduling Schema
For more information, see Define Elements of Schema, Define Schema and Assign External
Date Descriptors in the Implementation Guide (IMG) of SCM Basis .
- Process Alias
For more information, see Simple Process Maintenance, Maintain Process and Define
Process Alias in the IMG of SCM Basis.
You can only assign one process alias and thus one scheduling schema that conforms to
scheduling schema SCHEDL.
______________________________________________________________
SAP AG 345
SAP System
______________________________________________________________
6.2.10.9 Test Scheduling
Use
In this IMG activity, you can test process scheduling in simulation without integrating it with an
application. This allows you to study the behavior of process scheduling independently of the
data maintained in Customizing.
Requirements
The Customizing for process scheduling must already have been carried out. If you do not
maintain your own Customizing for process scheduling, you will only be able to test the
scenarios provided by SAP.
Activities
Maintain the start parameters for the test on the entry screen and choose Execute.
Note
For more information, see Simulation and Test of Process Scheduling.
6.2.11 Order Document Management
6.2.11.1 Configure Order Document Management
Use
In this IMG activity, you configure order document management (ODM) using metadata
maintenance. The system uses the metadata to describe the database structure in which the order
document data is managed by order document management.
Metadata also determines the structures with which the application can access the order
document data. For this, the application does not know in which tables the order document data
is stored.
This activity consists of the following main areas:
- Order component
- Order data type
- Order data area
______________________________________________________________
SAP AG 346
SAP System
______________________________________________________________
- Order document type

You can only change the inactive versions in this IMG activity. You can use the following
reports for the activities here:
- Activation report
You can use this report to pass changes from the inactive version to the active version.
- Generation report
You can use this report if the activation report does not run without errors. You have to
start the activation report again after generation.
- Control report
You can use this report to control the current active settings and generated objects.
Activities
Order components
In this area, you can maintain or display the following subareas:
- Order components
- Parameters for order components
- Indices for order components
- Generation data
Each component has a technical and a descriptive name. The technical name is used to identify
the component in the order data type and in the application. Order document management
distinguishes between core components and extensions.
- Core components
The core components form the basic framework of an order document. This consists of a
header, item, and - if necessary - a schedule line.
For a two-level order document, you use the components 1HDR (header) and 2IT2 (item).
For a three-level order document, use 1HDR (header), 2IT3 (item) and 4SDL (schedule
line).
You can identify core components using the ODM: Core Component indicator. A core
component cannot be used as an extension. If a corresponding extension is required, you
have to create this as well. The extension can use the same ABAP Dictionary structure as
the core component.
- Extensions
You can use extensions to store additional data for an order document that is not contained
in the core. The extension groups characteristics or attributes for an order document
according to their properties (for example, shipment). You assign extensions in the order
document type. The following are standard extensions for ODM:
- 7MP2 and 7MP3
Used for mapping the two and three-level document types.
______________________________________________________________
SAP AG 347
SAP System
______________________________________________________________
- 7REF
Used for references (links between order documents and parts of documents).
- 1PRT and 2PRT
Used to store partners at the header and item level.
- 1TST, 2TST, and 4TST
Used to store time stamps or time intervals. (This extension is not yet used in the
active version.)
You have to assign an ABAP Dictionary structure to a component. You use this structure to
specify which attributes the system stores for the component.
Order data type
In this area, you can maintain the following subareas:
- Order data type
- Extensions for order data type
- Generation data
An order data type consolidates several components. The order data type describes which data
you can save for an order document type and which structures are used for this.
The hierarchy category indicates whether the document is two or three-level (header and item;
or header, item and, schedule line). Generally, the header answers the question 'Who?', the
item 'What?', and the schedule line the questions 'When?' or 'How much?'. If only one
individual quantity (when, how much) is possible (for example, a delivery), you can use the
two-level hierarchy type.
You have to enter components for the header, item, and - if necessary - schedule line,
depending on the hierarchy type used for the order data type.
- If you want to store external or readable numbers for the order documents, you have to
enter the relevant mapping components (two or three-level).
- If the order data type can reference other order documents (and if these references are to
be stored in ODM), you also have to enter the reference components.
If you set the History indicator, the system can update a history for this order document type.
If you change an order data type, this change applies for all order document types used.
Order data area
- Order data area
- Tables for order data area
The order data area describes in which tables the order document data is stored.
An order data type is assigned to the order data area. An order data area is assigned to one or
more order document types. All order document types that have the same order data structure
can be stored in one order data area. For example, if the customer quotation and the sales
order have the same order data structure, you can store both of these in the same order data
area (if this also has the same order data type).
______________________________________________________________
SAP AG 348
SAP System
______________________________________________________________
Order document type

- Order document type
- Validity of the order data area
The definition of the order document type (for example, sales order, delivery, purchase order)
mainly consists of the assignment to an order data type.
The order data type determines which data you can store for an order document type.
For each order document type, you can specify whether the system should update the history.
You can only set the indicator if the history is allowed under order data type. (Updating the
history is not yet supported in the current version.)
6.2.11.2 Define Value Range
Use
In this IMG activity, you define the value range. For this, you can maintain the following
master data:
- Item category
The item category decides how an item is handled in the order document or what its
function is. The item categories are specified and interpreted by the applications.
- Schedule line category
The schedule line categories can be used to differentiate schedule lines or their quantities
(for example, requested or confirmed quantity). The schedule line categories are specified
and interpreted by the applications.
- Date type
The date type can be used to make additional specifications for date entries (goods issue or
loading date).
- Partner type
The partner role can be used to further specify partner entries (goods recipient, vendor).
The partner roles are specified and interpreted by the applications.
______________________________________________________________
SAP AG 349
SAP System
______________________________________________________________
6.2.11.3 Check Settings in Order Document Management
Use
In this IMG activity, you can check your settings for order document management.
You can make a check of all settings, or make restrictions according to the following subareas:
- Order component
- Order data type
- Order data area
You can also make additional restrictions; for example, by entering a certain order component,
you can check just the settings for this component.
You can also make the check for an inactive version.
You can output the results as either a log or a list.
6.2.11.4 Activate Settings in Order Document Management
Use
In this IMG activity, you can activate the following settings:

- Order component
- Order data area
- Order data type
For the activation, you convert the inactive settings to the active settings. Order document
management (ODM) only uses the active settings.
The system monitors the inactive settings when activation takes place and, if necessary,
generates ABAP Dictionary objects (structures and tables).
If the activation does not run without errors, you can call generation. You have to run
activation again once generation has been completed successfully.
______________________________________________________________
SAP AG 350
SAP System
______________________________________________________________
6.2.11.5 Generate Settings in Order Document Management
Use
In this IMG activity, you can generate the following ABAP Dictionary objects of inactive
versions:
- The inactive order component
- The inactive order data area
- The inactive order data type
The system only takes into account the inactive settings at generation. The ABAP Dictionary
objects of the active order component, the active order data area, and the active order data type
are not changed.
During the generation, the system monitors the inactive settings and, if necessary, generates
ABAP Dictionary objects (structures and tables).
If the activation does not run without errors, you can call generation. After successful
generation, you have to call activation again.
6.2.11.6 BAdI: Adjust Worklist of Deletion Report
Use
This Business Add-In (BAdI) is used in the Order Document Management component.
You can use this BAdI to do the following:
- Restrict the list of order documents
You can use this BAdI in the deletion report /SCMB/ODM_DATA_DELETE to restrict the
list of order documents that you have selected for deletion.
- Consider the lock categories from Forecasting and Replenishment
If you activate the enhancement implementation /FRE/ODM_DATA_DELETE of this BAdI,
the deletion report /SCMB/ODM_DATA_DELETE considers lock categories and lock
characteristics from Forecasting and Replenishment.
For more information, see the Implementation Guide (IMG) for SAP Supply Chain
______________________________________________________________
SAP AG 351
SAP System
______________________________________________________________
Management under Forecasting and Replenishment -> Order Proposal Management

-> Settings for Order Proposal Configuration -> Define Lock Categories and Lock
Characteristics.
Requirements
The BAdI is called once every time the deletion report /SCMB/ODM_DATA_DELETE is
executed.
Standard settings

Activities
See also:
This BAdI uses the /SCMB/IF_ODM_DATA_DELETE_BADI interface. For more information,

6.2.12 Time Series Data Management
6.2.12.1 Configure Time Series Data Management
Use
In this IMG activity, you define the metadata objects time profile, time series data type, time
series data area, and time series type.
- In the time profile, you define the entire validity period and the period interval of time
periods. You determine the individual time periods using the period multiplier or the
duration (period interval type duration).
To improve performance, the system groups the data records for the time series for each
parameter combination and key figure name as key figure values in adjoining table fields
of a table entry. This is a cluster. You use the cluster interval type to determine the
cluster interval that you want to use. You use the cluster multiplier to determine the
number of key figure values next to each other.
______________________________________________________________
SAP AG 352
SAP System
______________________________________________________________
To be able to use the time profile, you must activate the time profile. This also applies if
you have made changes to the time profile.
- The time series data type specifies the structural properties of a set of key figure data.
You use the mode to determine the characteristics combination of the parameter values
location, product, version, and a freely-determinable characteristic.
- You assign the appropriate time profile to determine the time properties of the set of
key figure data.
- You can also select a key figure parameter to specify the size of the database fields
for the key figure values. If you do not select anything, time series data management
(TSDM) uses the data element /SCA/TSDM_QUANTITY. You can define your own
parameters in Customizing under SCM Basis -> Configure Parameters.
- You can create a connection to the planning object structure. To do so, you use Mode
E (Characteristics: Planning Object Structure) and define suitable characteristics
parameters that are assigned to the InfoObjects in Customizing, under SAP SCM -
Implementation Guide ->SCM Basis -> Configure Parameters.
- Activate time profile, time series data type and time series data area depending on
what you want to transport and use the IMG Activity Configure Time Series Data
Administration to transport inactive and active entries.
When transporting time series data areas, you must also transport the tables. This is
not possible with the tables generated by TSDM of the namespace /1SCA/ since you
cannot use namespace /1SCA/ to transport active time series data areas.
To transport active time series data areas, you create tables with only one client field
in a package of your choice and use them in the configuration of the time series data
area. Enter all table names in the inactive version. As soon as you activate the time
series data area, TSDM adjusts these tables to its requirements.
- Time Profile:
Use transaction SM30 for the tables /SCA/TIMECLUSTER und /SCA/TIMEPERIOD
for transporting the periods and clusters of time profiles.
- Mode E:
The time series data tyep is connected to a planning object structure with the same
name.
You use the logical transport object SDPS to transport the planning object structure:
a) Use transaction SE09 to select the Transport Organizer.
b) Add the object R3TR SDPS <Time Series Data Type Name> to the transport.
c) Release the transport.
- If you want to obtain information about the key figure parameter (optional) and the
key sequence (optional), contact SAP.
To be able to use the time series data type, you must activate the time series data
type. This also applies if you have made changes to the time series data type.
- Using the time series data area, you define a group of tables to specify the storage
location for time series of a specific time series data type.
For the TSDM to assign the table names and creates related tables, you must activate the
time series data area.
______________________________________________________________
SAP AG 353
SAP System
______________________________________________________________
- The external interfaces of TSDM use the time series type to identify a group of time
series data.
To define a time series type, you specify the structure using the time series data type.
In addition, you can select one of the characteristics MATID (product), LOCID (location),
or CHOBJ (freely-determinable characteristic) to define it further in the Time Series Data
Areas for Time Series Type step.
If you activate the Change History indicator, the system records changes to key figure
values according to clusters.
In the Time Series Data Areas for Time Series Type step, you connect the external
description Time Series Type with one or more time series data areas.
To be able to save data in TSDM, you must assign at least one time series data area to a
time series type. You can use additional criteria such as version, key figure, or
characteristic value of the characteristic that you specified in the previous step to specify
that the data of a time series type should be distributed to several time series data areas.
6.2.12.2 Configure Parameters
Use
In this IMG activity, you configure the parameters for transactional data.
A parameter describes the structural attributes of a data field that you define by specifying a
data element or an InfoObject in SAP BW.
For more information, see Configure Time Series Data Management and Configure Order
Document Management.
6.2.12.3 Activate Time Profile
Use
______________________________________________________________
SAP AG 354
SAP System
______________________________________________________________
In this IMG activity, you activate an existing time profile to be able to use it in time series
data management (TSDM). On activation, the system creates an additional data record for the
activated time profile with the Active indicator.
Note: If you have changed the definition of the time profile so that the new periods have
different lengths or different start dates to the old periods, the time series data of the related
time series types becomes invalid. This also applies if you change clustering (length, cluster
type).
If you only change the validity period of the time profile, the time series data of the related
time series types remains valid.
Requirements
You have created a time profile under Configure Time Series Data Management.
6.2.12.4 Delete Time Profile
Use
In this IMG activity, you can delete the active version, the periods, or the cluster of a time
profile. If you want to delete a time profile for good, set the Delete All Versions indicator.
Note: If you delete the active version of the time profile, the time series data of the related
time series types becomes invalid. The system deletes the active version of the related data
types and the related data areas.
Requirements
To be able to delete an active time profile, you need to have activated it beforehand under
Activate Time Profile.
6.2.12.5 Activate Time Series Data Type
Use
______________________________________________________________
SAP AG 355
SAP System
______________________________________________________________
In this IMG activity, you can activate an existing time series data type to be able to use it in
time series data management (TSDM). Additionally, if the planning object structure (POS) is
deactivated, you can activate it.
Requirements
- You have created a time series data type by choosingConfigure Time Series Data
Management.
- To be able to activate the POS, you must have activated the corresponding time series data
type.
Activities
1. To activate an existing time series data type, select the Activate Times Series Data
Type radio button. Upon activation, the system creates an additional data record for the
activated time series data type with the Active indicator. If you want to set up the data
type anew, even though you have not made any changes to the settings, choose Reset. If
you also want to activate the related time profile and the time series data areas, choose
Activate Dependent.
2. To activate the planning object structure, select the Activate Planning Object Structure
radio button. The selected time series data type determines the POS to be activated.
Note: If you have changed the definition of the time profile so that the new periods have
different lengths or different start dates from the old periods, the time series data of the related
time series types becomes invalid. This also applies if you change the clustering (length, cluster
type).
6.2.12.6 Delete Time Series Data Type
Use
In this IMG activity, you can delete the active version or dependent objects of a time series
data type. If you want to delete the time series data type for good, set, in addition, the Delete
All Versions indicator.
Note: If you delete the active version or dependent objects of the time series data type, the
system also deletes all related time series data areas. This relates to the active versions or all
versions.
Requirements
To be able to delete an active data type, you have activated an existing time series data type
______________________________________________________________
SAP AG 356
SAP System
______________________________________________________________
under Activate Time Series Data Type.
6.2.12.7 Activate Time Series Data Area
Use
In this IMG activity, you activate an existing time series data area so that time series data
management (TSDM) assigns table names and creates related tables. On activation, the system
creates an additional data record for the activated time series data area with the Active
indicator.
Note: If the system regenerates tables, it deletes the time series data of each data area for
good.
Requirements
You have created a time series data area under Configure Time Series Data Management.
6.2.12.8 Delete Time Series Data Area
Use
In this IMG activity, you can delete the active version of the time series data area. If you want
to delete the time series data area for good, you also set the Delete All Versions indicator.
Note: If you delete the active version of the time series data area, applications that work with
time series data management (TSDM) can no longer access data within this time series data
area. The data is not deleted from the database but it is nevertheless no longer accessible. If
you activate the time series data area anew for an unchanged time series data type, the data is
accessible again.
Requirements
To be able to delete an active time series data area, you have activated an existing time series
data area under Activate Time Series Data Area.
______________________________________________________________
SAP AG 357
SAP System
______________________________________________________________
6.2.12.9 Copy Time Series Data Area
Use
In this IMG activity, you copy a time series data area into another time series data area. You
copy time series data areas to keep data areas to a size that the database can manage while
retaining the level of performance.
Requirements
You have created at least two time series data areas under Configure Time Series Data
Management.
6.2.12.10 Delete Time Series Data
Use
In this IMG activity, you can delete time series data that you no longer require.
- The Date From and Date To or Number of Days in Past fields indicate the time series
periods that you want to delete. In the Number of Days in Past field, the system counts
backward from today and sets the contents of the Date From and Date To fields
correspondingly.
- You can use the Delete Key Figure Data and Delete State Data indicators to control the
data that you actually want to delete.
- If you set the Test Run indicator, you see the data that would be deleted from the system,
but the system does not delete this data.
- The system writes a log with the object ICH and the subobject TSDM.
Requirements
You have created a time series type under Configure Time Series Data Management.
______________________________________________________________
SAP AG 358
SAP System
______________________________________________________________
6.2.12.11 Delete Time Series Change History
Use
Time series data management (TSDM) records changes to time series data depending on the
settings of the time series data type. This data volume can be very large.
In this IMG activity, you can delete data from the change history that you no longer require
for a specific period in the past. You define this period in the Number of Days in Past field.
- The Date From and Date To or Number of Days in Past fields indicate the time series
periods that you want to delete. In the Number of Days in Past field, the system counts
backward from today and sets the contents of the Date From and Date To fields
correspondingly.
- You can use the Delete Key Figure Data and Delete State Data indicators to control the
data that you actually want to delete.
As a result, the system deletes all recorded changes lying more than the given number of days
before the execution date of the transaction. Instead of the manual transaction, you can also
execute the related report /SCA/TSDM_TS_HIST_DELETE regularly in the background.
6.2.12.12 BAdI: Definitions for Change Period in Time Profile Activation
Use
This Business Add-In (BAdI) is used in the Time Series Data Management (SCM-BAS-TSM)
component.
This BAdI enables you to define time periods that cannot be configured with the Configure
Time Series Data Management IMG activity.
The BAdI is called when you activate a Time Series Data Management (TSDM) time profile,
before the system saves the definition of the time periods and time clusters of the time profile
to the data base.
______________________________________________________________
SAP AG 359
SAP System
______________________________________________________________
Requirements
The BAdI should be used only if you cannot make the desired settings in the Configure Time
Series Data Management IMG activity. Here you can define certain types of irregular time
periods with the Fiscal Year Variant field and you can define time periods of arbitrary length
(in hours or fractions of hours), by choosing Time duration in the Period Interval Type field.
Standard settings

If the BAdI is not activated, TSDM uses the configuration of the time profile in the Configure
Time Series Data Management IMG activity to determine the time periods and the time clusters.
The BAdI method comes after this computation, so that it can be used to modify the result of
the standard period determination or to define time periods and time clusters from scratch.
Activities
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
______________________________________________________________
SAP AG 360
SAP System
______________________________________________________________
Example
Defined time periods could be the following:

- Weeks with varying offset days, such as: week one starts on Monday, week two starts on
Tuesday, week three starts on Wednesday, week four starts on Tuesday
- Complex calendar dependencies
- Completely irregular intervals
Note
Time periods configured in the Configure Time Series Data Management IMG activity are
grouped into clusters according to the cluster settings. For irregular time periods configured
with this BAdI, we recommend that you group a fixed number of periods into one cluster. In
both cases, the begin and end times of the clusters to which the time periods belong need to be
set according to the start of the earliest time period and the end of the latest time period.
See also
Method
Set Time Period Definition
6.2.13 Pack
6.2.13.1 Packaging Specification
6.2.13.1.1 Define Number Range for Packaging Specification
Use
In this step, you define the number ranges for

- Packaging specification IDs
- Packaging work steps
- PS level element groups
The following types of number assignment are possible:
- Internal number assignment
The SAP system automatically assigns a sequential number from the defined number range.
______________________________________________________________
SAP AG 361
SAP System
______________________________________________________________
- External number assignment

You enter a number from an external number range.
When you create a number range, you specify whether it is an internal or external number
range.
Activities

2. Enter the limits for the number interval. The individual number intervals must not overlap.
Each number must only appear once.
3. Flag the number range if it should be used for external number assignment.
6.2.13.1.2 Define General Packaging Specification Parameters
Use
In this IMG activity, you specify the general packaging specification parameters.
Activities
Create one entry for each client.

- Assign the number ranges for packaging work steps and level element groups.
- Enter the form name of the form you wish to use for printing packaging specifications.
- If you want to use document management, enter the RFC destination of the SAP R/3
system, and the object type used in the SAP R/3 system.
- You also decide whether changes to packaging specifications should be documented using
change documents.
You should only activate updates of determination logs for test purposes.
______________________________________________________________
SAP AG 362
SAP System
______________________________________________________________
6.2.13.1.3 Define Packaging Specification Group
Use
In this IMG activity, you create groups for packaging specifications.

A group consists of a description, the assignment of a number range interval, and a level set
and is used in the authorization object for packaging specifications.
Furthermore, you specify whether packaging specifications of this group are to be distributed to
other SCM systems.
Activities
Create a group for packaging specifications and assign it a description, a number range for the
packaging specification ID, and a level set.
Distribution of packaging specifications:
If you have just one SCM system, choose the value 'local' for the Distribution field.
If you have several SCM systems, specify here whether packaging specifications of this group
are to be distributed from this system (option: source system).
In the other SCM systems, you then set the 'target system' option for this packaging
specification group. As a result, this PS group will not be offered for selection during the
creation of packaging specifications.
Example
Within your company, packaging specifications can be used or written by by both internal and
external employees (such as those of a vendor).
Create group 01 for external employees and group 02 for internal employees.
By including the groups in the associated role for the employees, you can ensure that external
employees can see packaging specifications but are not allowed to make any changes.
As you are working with two SCM systems, choose the 'Packagaging Spec. Source System'
option for the two groups 01 and 02 in system SCM1. In system SCM2, set 'Packaging Spec.
Target System' for the two groups.
6.2.13.1.4 Define RFC Connection for Packaging Specification Distribution
Use
______________________________________________________________
SAP AG 363
SAP System
______________________________________________________________
In this IMG activity, you specify the RFC connections via which the packaging specifications
are to be distributed to other SCM systems.
Requirements
Ensure that you have created the RFC connections that you wish to enter here. More
information is available via the SAP menu under Tools -> ALE -> ALE Administration
->Runtime Settings -> Maintain RFC Destination.
Activities
Enter the desired RFC connections via which you wish to distribute packaging specifications to
other SCM systems.
6.2.13.1.5 Maintain Master Data for Packaging Specifications
Use
In this IMG activity, you define master data for level sets.
Activities
You can specify a packaging specification as a template for each level set, so that the
corresponding condition records of this template packaging specification are copied when a new
packaging specification is created with this level set.
If you wish to adjust the copying of the condition records, implement the BAdI BAdI: Use
Condition Record Template of a Packaging Specification.
6.2.13.1.6 Maintain Structure of Packaging Specification
6.2.13.1.6.1 Define Level Type
______________________________________________________________
SAP AG 364
SAP System
______________________________________________________________
Use
In this IMG activity, you create level types.

A level type consists of a description and various default values.
A level type is a prerequisite for a level set.
Activities
Create a level type with a description.

If you wish, you can enter default values for the Target Quantity in Level and the Performing
Entity.
Specify whether a level of this type can be deleted in a packaging specification.
You can use the symbol to predefine the display for a level of this level type on the packaging
specification user interface.
Example
Create the level type 'Basic Packing'.

Since this level of packing is always performed internally in your company, you save the
default value 'Warehouse'.
If the basic packing level should be used to exactly describe how a piece of a product should
be packed, you store a target quantity of 1. Since you want each packaging specification to
contain this level, you set the 'Not Deletable' indicator.
6.2.13.1.6.2 Define Element Type
Use
In this IMG activity, you create element types.

An element type consists of a description and various default values.
An element type is a prerequisite for a level set.
______________________________________________________________
SAP AG 365
SAP System
______________________________________________________________
Activities
Create an element type with a description. If you wish, you can enter a default value for the
HU relevance.
Specify whether an element of this type can be deleted in a packaging specification.
You can use the symbol to predefine the display of an element of this type on the packaging
specification user interface.
Example
Create the element type 'Main Load Carrier'. In an element of this type, the packaging material
should always be entered, and should be the packaging material used to build HUs. Choose the
HU relevance 'Main Packaging Material (1)' as the default value.
6.2.13.1.6.3 Define Level Set
Use
In this IMG activity, you define level sets.

A level set defines the structure of a packaging specification. It consists of level types and
element types.
It enables you to predefine a uniform structure for packaging specifications in your system.
If a user creates a packaging specification with reference to this level set, the system adopts all
the default values, and the newly created packaging specification already contains empty levels
and elements.
Requirements
You have created level types and element types (see also: Define Level Type and Define
Element Type).
Activities
1. Create a level set with a description.

2. Assign one or more level types. You can also assign one or more element types to each
level type.
3. Specify the number of products that can be contained in a packaging specification.
4. If you have configured packaging specification determination, you can store a default value
for the condition type. This condition type is automatically proposed to the user when
creating a packaging specification.
______________________________________________________________
SAP AG 366
SAP System
______________________________________________________________
Example
You want each packaging specification to describe the basic packaging and the transportation
packaging for a product. Create a level set 'Warehouse' and assign the two level types 'Basic
Packing' and 'Transportation Packing'. Each of these level types should contain a main
packaging material; assign the element type 'Main Load Carrier' to each of the level types.
6.2.13.1.6.4 Define Work Step Type
Use
In this IMG activity, you define packaging work step types. The work step types ensures a
logical grouping of work steps.
You can assign a work step to one work step type. You can use the work step type to restrict
permissions of work steps for a packaging material. These permissions are ensured by assigning
work steps to packaging material types.
Activities
Create one or more work step types.
Example
You can use the work step types 'Include' and 'Seal' to ensure that when you create a packing
instruction, packaging materials such as "Plastic Bags" are not linked to work steps that belong
to "Include".
6.2.13.1.6.5 Define Packaging Material Types
Use
______________________________________________________________
SAP AG 367
SAP System
______________________________________________________________
Activities
- Closed
- Status profile
- Delete
6.2.13.1.6.6 Assign Packaging Material Type to Element Type
Use
In this IMG activity, you can assign permitted packaging material types to element types. You
can assign more than one packaging material type to an element type.
If packaging material types are assigned to an element type, then only packaging materials that
belong to these packaging material types are valid for this level element in a packing
instruction.
If no packaging material types are assigned to an element type, then all packaging materials are
valid in the level element.
Requirements
Make sure that you have defined packaging material types and element types (see also: Define
Packaging Material Types and Define Element Type).
______________________________________________________________
SAP AG 368
SAP System
______________________________________________________________
Standard settings
There are no predefined assignments of packaging material type to element type. You should
only configure these where you want the system to handle assignments of packaging material to
level element restrictively, during maintenance of a packing instruction.
Activities
Create an entry in which a specific packaging material type is assigned to a level type. This
element type takes account of this rule during maintenance of a level element. This means, that
only packaging materials belonging to this packaging material type are permitted in this level
element.
6.2.13.1.6.7 Assign Work Step Type to Packaging Material Type
Use
In this IMG activity, you can assign permitted work step types to a packaging material type.
The system takes this assignment into account during maintenance of packing instructions.
You can assign several work step types to a packaging material type.
If no work steps are assigned to a packaging material type, then all work step types are
permitted during maintenance of a level element in a packing instruction, if you are using a
packaging material from the given packaging material type.
Requirements
You have defined a packaging material type and work step types (see also: Define Packaging
Material Types and Define Work Step Type).
Standard settings
There are no predefined assignments for work step types. This means that without this setting,
all combinations of packaging material and work step are permitted in a level element.
Activities
Create a combination of an existing packaging material type and an existing work step type.
This means that during maintenance of a level element in a packing instruction, only the work
steps for the work step type are permitted, which use a packaging material from this packaging
material type.
______________________________________________________________
SAP AG 369
SAP System
______________________________________________________________
6.2.13.1.7 Determination of Packaging Specifications
6.2.13.1.7.1 Create Field Catalog
Use
In this IMG activity, you can maintain the field catalog for packaging specifications.
The field catalog contains the fields you are allowed to use for defining condition tables.
Field catalog maintenance is divided into three screen areas:
- Field catalog area
- Detail area for field and data element (can be displayed/hidden)
- Detail area for the log (can be displayed/hidden)
Field catalog area
The field catalog area is the principal part of field catalog maintenance. You can edit fields, or
create new ones. In change mode, you can maintain the following fields:
- Category of Subcommunication Structure
(This field is only ready for input for the selection All Fields, as otherwise a specific
category is defined as a default):
- Header
Fields that are only used in the document header.
- Item
Fields that are only used in the document item.
- Header/item
Fields that are used in the document item, but that are usually identical in all items.
These fields become header fields at the condition access, which inproves performance.
- Fields not contained
Fields that can be contained in the condition tables, but that are not contained in the
communication structure. Fields of this type can be populated, for example, from
other fields.
- All fields
Overview of all existing subgroupings.
- Field
Enter a field name. Note, that the namespace Y* and Z* is reserved as a customer
namespace. The remaining namespace is reserved for SAP.
- Virtual
The attribute 'Virtual' for a field defines the appearance of the field. Currently, the
following attributes are permitted:
- A = internal only, never appears on the user interface
______________________________________________________________
SAP AG 370
SAP System
______________________________________________________________
- B = external only, never appears in a condition record

- C = internal and external use
- D = access field only. This means that is does not appear on the user interface or in
condition records
- E = internal and external use, but not visible on the user interface
Fields of type A represent an internal display (such as a product GUID). Fields of type B
represent an external display (such as a product number). If the internal and external
displays for a field are identical, then the field is of type C or E.
Fields of type A, B, C, and E can always be contained in condition tables, whilst fields
of type D are only used in the communication structure for acccesses (during access, a
field of type D is assigned to a field in the condition table, for example, the local
currency field is assigned to a currency field).
- Selection type
This attribute specifies the type of condition record selection during general condition
maintenance. Currently, the following attributes are permitted:
- A = Any selection possible
- B = Single values possible
- C = One single value possible
- D = Not used for selection
- Data element
The data element specifies the business meaning as well as the data type of the field. In
principal, you can select all of the data elements that exist in the system.
After you enter a data element, the system displays the description, the data type and the
field length in the other non-input-ready columns of the table control.
Caution: A data element can only exist once in the field catalog.
The following special functions are available in the field catalog area:
- Select
- Select Block
- Deselect
- Position
Details: Relationships and dependencies for the field or data element are shown in the detail
area for the field or data element, where this area is displayed.
Detail area for field and data element
You can only maintain the detail area for a selected field from the field catalog, for which you
have selected the "Detail" function (Symbol: magnifying glass).
- Relationships
In this area, you can maintain relationships to other fields for the field you selected.
Relationships are useful if the internal and external use of a field are different.
Example:
______________________________________________________________
SAP AG 371
SAP System
______________________________________________________________
The STOCK_GUID field is only used internally. Its external display is a combination of
the fields PAK_MATID (product), Owner (owner), Entitled (party entitled to dispose), and
Category (stock type). For the STOCK_GUID field, you therefore need to enter the above
four fields into the relationships.
The selected field should always be a field with internal use (the 'Virtual' column in the
field catalog area). You can then maintain relationships to fields with external use. If the
uses of the fields do not match up, the system issues a relevant error message.
You can only maintain relationships to fields from the global field catalog (table
/SAPCND/T681FF).
- Dependencies
In this area, you can maintain dependencies to other data elements for the data element of
a selected field. These dependencies are checked during processing of condition records.
Example:
Before checking the STOCK_GUID field with data element /LIMEB/GUID_STOCK the
system should first check the product and the location. You therefore need to maintain the
dependencies in the following order:
- PAK_MATID (product)
- PAK_LOCID (location GUID)
In the dependencies, you can only select data elements from the global field catalog.
Detail area for the log
In the area for the log, you can see the last application log written during the last transaction
call at 'Save' or 'Generate'.
The standard functions of the application log are available.
The logs are saved under the following object for the application log: COND_TECHNIQUE
(subobject FIELD_CATALOGUE).
You can use transaction SLG1 (Evaluate Application Log) to display all the logs. Any logs that
are no longer required can be deleted using transaction SLG2 (Application Log -> Delete
Outdated Logs).
Functions
The following functions are globally available for all screen areas.
- Save
When you save the field catalog, the entries in tables /SAPCND/T681FA,
/SAPCND/T681FF, and /SAPCND/T681F are updated or deleted..
When you maintain relationships, this causes a database change in table /SAPCND/T681FR.
When you maintain dependencies, this causes a database change in table
/SAPCND/T681FD.
- Delete
The selected lines are deleted from the field catalog area, relationship area, or dependency
area.
When you delete fields, the dependencies are automatically deleted. Dependencies of the
relevant data element are only deleted if they do not have a dependency to another data
element.
______________________________________________________________
SAP AG 372
SAP System
______________________________________________________________
If fields are already used in condition tables or accesses, then the system issues a warning.
You should only delete the field if the tables and accesses are not used in a productive
system.
- Generate
When you execute the 'Generate' function, the system generates the communication
structures that are dependent on the field catalog. The communication structures are as
follows:
/SCWM/PAK_COM_H (header fields)
/SCWM/PAK_COM_M (item fields that are normally the same for all items)
/SCWM/PAK_COM_I (item fields that are normally different for all items)
- Transport
Changes to the field catalog are transported using a transport object (name
/SAPCND/CUSTOMIZING, transaction SOBJ) of type #T (individual transaction object).
When you save the data, the systems asks for a transport request to record the changes.
The system always transports a complete, internally consistent logical object. This means
that for a field, the system always transports the relationships and dependencies, where
present. The consistency check for the transport order is performed using the transport
methods assigned to the transport object:
BEFORE_EXPORT: Method for checking the consistency of the transported table entreis
before they leave the source system.
AFTER_IMPORT: Method for generating the dependent objects in the destination system.
You can also trigger a manual transport of the entire field catalog for an application.
6.2.13.1.7.2 Define Condition Tables
Use
In this IMG activity, you define packaging specification dependencies. For example, you can
make packaging specifications dependent on the material to be packed and the goods recipient.
In this case, the system finds a particular packaging specification according to the product and
goods recipient specified.
You define these dependencies using the condition tables. You define the combination of fields
in a condition table (for example, product and goods recipient) on which you want to make the
packaging specification determination dependent. Later on, you fill this condition table with
content, that is, with concrete information, using the condition records.
SAP Recommendation
You should not change the condition tables contained in the SAP standard version.
______________________________________________________________
SAP AG 373
SAP System
______________________________________________________________
Activities
To create a condition table, proceed as follows:

1. Before you create a new condition table, you should check whether the fields available in
the field catalog meet your requirements. If you want to use a field that is intended for
the standard delivery system, you must include it in the field catalog.
2. Enter the name of the table that you want to create. Note that the name must start with
'CUS' and that you can then enter a maximum of 5 characters.
3. Choose 'Change' and enter a short description for the condition table. If you do not enter
a description, a short description is generated from the field names in the table when the
table is saved.
4. Choose the fields required for the condition table from the list of fields contained in the
field catalog.
5. Generate the new condition table.
6. Specify the condition tables in the access sequences. By doing this you connect the
determination procedure to the condition type, access sequence, and condition record.
6.2.13.1.7.3 Define Access Sequences
Use
In this IMG activity, you define access sequences.

The access sequence is a search strategy that the SAP system uses to search for valid
determination records for a packing instruction condition type.
Each condition table contains a particular combination of fields that the system is to search for
in the condition records. The search sequence should go from special to general condition
records:
For example, you can define in packaging specification determination that the SAP system first
searches for a packing instruction only using the combination of product and goods recipient
(you define this combination using the condition tables) and then only using the goods recipient.
You use the exclusive indicator to define that the system finishes searching in additional
condition types from the access sequence once it has found a valid condition record. All valid
condition records of this condition type are returned. The logical conditions are evaluated once
the actual determination has taken place. This means that in some processes it could be that no
condition record is found.
______________________________________________________________
SAP AG 374
SAP System
______________________________________________________________
Activities
1. Check the extent to which you can use the access sequences contained in the standard SAP
delivery.
2. Create new access sequences. The namespace for customer-specific entries is A* to Z* and
8*, 9*.
3. Maintain the accesses for the access sequence by specifying the condition tables in the
required sequence. To do this, select your new access sequence and choose 'Accesses'.
You use the sequence to define the priority of the accesses.
4. Select the new accesses one after the other and choose Fields. You use the access type to
define whether the field is in the fixed or free part of the key. If the field is an optional
key field (field in the free part of the key), you must also define the evaluation priority.
6.2.13.1.7.4 Define Condition Types
Use
In this IMG activity, you define certain condition types for packaging specifications. For
example, you can define the condition type Pack in Shipping and assign packaging specifications
to this condition type. In this way, the condition types are used to group the packaging
specifications permitted for a certain area. In each condition type you specify an access
sequence that you use to define the fields that the SAP system searches for a valid
determination record (condition record).
You always define determination records for a condition type.
Activities
1. Check to what extent you can use the determination types included in the standard SAP
delivery.
2. Create the new determination type. The namespace for customer-specific entries is A* to
Z* and 8*, 9*.
3. Specify an alphanumeric key, which can be up to 4 digits long, and a description.
4. Specify an access sequence for the determination type.
5. If required, specify a date proposal when creating condition records.
______________________________________________________________
SAP AG 375
SAP System
______________________________________________________________
6.2.13.1.7.5 Define Determination Procedure
Use
In this IMG activity, you define the packaging specification procedures.

In a packaging specification procedure you define which condition types are taken into account
and in which order. When determining the packaging specification, the system automatically
determines which procedure is valid for a business transaction and takes into account the
determination types contained within, one after the other.
Activities
1. Create the new determination procedure. The namespace for customer-specific entries is A*
to Z* and 8*, 9*.
2. Specify an alphanumeric key for the determination type, which can be up to 6 digits long,
and a description.
3. Maintain the search sequence of the condition types by specifying the condition types in the
required sequence. To do this, select your new determination procedure and choose
Procedure Element. You use the level number to define the access sequence.
More Notes
You define which procedure is used for which business transaction in the IMG activities in the
relevant application.
6.2.13.1.7.6 Create Condition Maintenance Group
Use
The condition maintenance group groups together condition tables and condition types for
condition maintenance.
You can assign permitted condition tables and condition types for packaging specification
determination.
______________________________________________________________
SAP AG 376
SAP System
______________________________________________________________
6.2.13.1.8 Business Add-Ins for Packaging Specifications
6.2.13.1.8.1 Packaging Specification User Interface
USE&
enhancement spot /SCWM/ES_PS_UI.
6.2.13.1.8.1.2 BAdI: User Interf. Enhancement of Packaging Specification

Header Attributes
Use
This Business Add-In (BAdI) is used in the Packing Basics (SCM-BAS-PAK) component. You
can use this BAdI to enhance the user interface for packaging specifications (transaction
/SCWM/PACKSPEC). The following subscreen areas are available for this purpose:
- BADI_HEADER_TAB - Display header attributes on an extra tab (size: 87 columns, 21
lines )
- BADI_HEADER_ORG - Display header attributes on tab 'Org. Data' (size: 87 columns, 15
lines )
Standard settings

The BAdI is not designed for multiple use.
______________________________________________________________
SAP AG 377
SAP System
______________________________________________________________
Activities
For your own implementation of subscreen BADI_HEADER_TAB and/or BADI_HEADER_ORG,
you must create a screen (subscreen) and implement the method SET_PACKSPEC.
If you want to hide a standard screen field for a packspec header, you must implement method
HIDE_FIELD.
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_HEADER interface.

For more information, display the interface in the Class Builder.
6.2.13.1.8.1.3 BAdI: User Interface Enhancement for Content
Use
can use this BAdI to enhance the user interface for packaging specifications (transaction
/SCWM/PACKSPEC). The following subscreen areas are available for this purpose:
- BADI_CONTENT_MAT - Display Product Attributes (Size: 90 columns, 24 lines )
- BADI_CONTENT_PS - Display Attributes of a Subordinate Packspec (Size: 90 columns,
24 lines )
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_PS_UI is activated. The default
code is executed automatically. The default coding contains an implementation for the subscreen
area BADI_CONTENT_MAT.
Activities
______________________________________________________________
SAP AG 378
SAP System
______________________________________________________________
For your own implementation of subscreen BADI_CONTENT_MAT and/or

BADI_CONTENT_PS, you must create a screen (subscreen) and implement the method
SET_CONTENT.
If you want to hide a standard screen field for a packspec content, you must implement method
HIDE_FIELD.
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_CONTENT interface.


Level Attributes
Use
can use this BAdI to to enhance the user interface for packaging specifications (transaction
/SCWM/PACKSPEC). The following subscreen area is available for this purpose:
- BADI_LEVEL_TAB - Display level attributes on an extra tab (size: 88 columns, 22
lines )
Standard settings

Activities
For your own implementation of subscreen BADI_LEVEL_TAB , you must create a screen
(subscreen) and implement the method SET_LEVEL.
If you want to hide a standard screen field for a packspec level (on any tab), you must
implement method HIDE_FIELD.
______________________________________________________________
SAP AG 379
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_LEVEL interface.

6.2.13.1.8.1.5 BAdI: User Interface Enhancement of Packaging Specification

Elements
Use
can use this BAdI to enhance the user interface for elements in a packaging specifications
(transactions /SCWM/PACKSPEC and /SCWM/PSEG). The following subscreen area is available
for this purpose:
- BADI_ELEMENT - Display element attributes in the form view (size: 87 columns, 12
lines )
Standard settings

Activities
For your own implementation of subscreen BADI_ELEMENT, you must create a screen
(subscreen) and implement the method SET_ELEMENT.
If you want to hide a standard screen field of a packspec element, you must implement method
HIDE_FIELD.
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_ELEMENT interface.

______________________________________________________________
SAP AG 380
SAP System
______________________________________________________________
6.2.13.1.8.1.6 BAdI: Best Possible Packaging Material for Level
Use
can use this BAdI to determine a best fitting packaging material for a level.
The method 'GET_BEST_FITTING_PACKMAT' is called when the user hits the button 'Find
Pack. Material' in the transaction /SCWM/PACKSPEC.
Parameters:
- IV_MATID_PREV - product(guid) of the previous level or the content
- IS_DIMENSION_PREV - dimensions, weight and volume of the previous level
- IS_LEVEL_QUAN - target quantity of this level
- IS_ELEMENT - current element of the level
- IT_CONTENT - all contents of this packaging specification
- EV_PACKMAT - product(guid) of the packaging material (RESULT)
Standard settings
code is executed automatically.
The default implementation is an algorithm that finds the best closed packaging material based
on dimensions, weight and volume. It works only for target quantity 1. As a start it takes the
list of allowed packaging materials for this level. Within a loop all packaging materials are
filtered out that do not meet the following requirments:
- dimensions of the packaging material must be greater than the (outer) dimensions of the
previous level or the content
- weight must be less than the maximum weight of the packaging material
- volume must be less than the maximum volume of the packaging material
- packaging material must have the 'closed pack. material' flag
The resulting list of packaging materials is then sorted by volume and the smallest is returned.
Activities
______________________________________________________________
SAP AG 381
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_LEVEL_FIT interface.

6.2.13.1.8.1.7 BAdI: Best Possible Target Quantity for Level
Use
can use this BAdI to find the optimum target quantity for a level.
The method 'CALCULATE_LEVEL_QUANTITY' is called when the user hits the button
'Calculate Quantity' in the transaction /SCWM/PACKSPEC (subscreen LEVEL). This button is
visible only, if an active implementation exists for this method.
Parameters:
- IO_LEVEL - object reference to the current level
- IO_PACKSPEC - object reference to the whole packaging specification
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_LEVEL_BESTTQ interface.

______________________________________________________________
SAP AG 382
SAP System
______________________________________________________________
6.2.13.1.8.1.8 BAdI: Calculate Level Dimension
Use
can use this BAdI to calculate the level dimensions (length/Width/height).
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_LEVEL_CALCD interface.

6.2.13.1.8.1.9 BAdI: Additional Change Documents
Use
can use this BAdI to insert additional change documents or make own conversions for already
read change documents (for packaging specifications, element groups and worksteps).
Standard settings

The BAdI is filter-dependent.
______________________________________________________________
SAP AG 383
SAP System
______________________________________________________________
Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_CDOC interface.

Example
If you write change documents for condition records (see other BAdI
/SCWM/EX_PS_DET_SAVE), you can read and add these change documents here.
6.2.13.1.8.1.10 BAdI: Display Change Documents
Use
can use this BAdI to change the change document display (for packaging specifications, element
groups and worksteps).
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_PS_UI_CDOC_DISPLAY is

activated. The default code is executed automatically.
The default implementation calls the function module 'CHANGEDOCUMENT_DISPLAY'.
Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_CDOC_DISPLAY interface.

______________________________________________________________
SAP AG 384
SAP System
______________________________________________________________
6.2.13.1.8.1.11 BAdI: Automatic Condition Records from Packaging

Specification
Use
can use this BAdI to adapt the automatic creation of condition records from the condition
records of the template packaging specification.
Requirements
You entered a packaging specification as template for a level set, the corresponding condition
records are copied to the newly created packaging specification.
Standard settings
code is executed automatically.
In the default implementation all application fields are cleared and only the product field is
filled with the new product number (if available).
Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_COND_RECORD interface.

Example
During the creation of the condition records you want to take over the product and the location
from the template condition record.
6.2.13.1.8.1.12 BAdI: Enhance Input Help in User Interface for Packaging
______________________________________________________________
SAP AG 385
SAP System
______________________________________________________________
Specification
Use
can use this BAdI to augment/modify search helps for packaging specification related objects.
The main aim should be to restrict possible input values according to a given context.
The method F4_EXIT_FUNCTION is called in function module /SCWM/PS_F4EXIT_GENERIC.
This function module, in turn, is referenced by several packaging search helps as a function
module exit. This means that F4_EXIT_FUNCTION should trigger different functionality
depending on which search help it is called from.
The following F4-helps use this exit:
- workstep
- packaging material
- work step type
- element group
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_PS_UI_F4 is activated. The

deafault code is executed automatically.
Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_F4_GENERAL interface.

Example
The default methods provided in class /SCWM/CL_EI_PS_UI_F4 also serve as useful examples.
An active implementation will essentially "replace" the methods in this class. Therefore, it may
be useful to call the existing methods explicitly or use them as a basis for creating own copies.
______________________________________________________________
SAP AG 386
SAP System
______________________________________________________________
6.2.13.1.8.2 Packaging Specification
USE&
enhancement spot /SCWM/ES_PS_CORE.
6.2.13.1.8.2.2 BAdI: Check Changes to Packaging Specification
Use
can use this BAdI to validate the changes of a packaging specification.
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_CORE_VALIDATE interface.

______________________________________________________________
SAP AG 387
SAP System
______________________________________________________________
6.2.13.1.8.2.3 BAdI: Check Changes to Element Group
Use
can use this BAdI to validate the changes of an element group.
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_CORE_VAL_EG interface.

6.2.13.1.8.2.4 BAdI: Check Changes to Work Steps
Use
can use this BAdI to validate the changes of worksteps.
Standard settings

______________________________________________________________
SAP AG 388
SAP System
______________________________________________________________
Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_CORE_VAL_WS interface.

6.2.13.1.8.2.5 BAdI: Determine Packaging Specification Labels
Use
can use this BAdI to calculate or determine a list of packspec labels.
You can use method SET_LIST to derive a list of labels that need to be printed for a
packspec.
In import parameter IV_GUID_PS the information is passed, for which packspec the labels shall
be derived.
In case import IV_QTY is supplied, the quantites of the labels must be calculated. In case the
parameter IV_QTY is not supplied, the list of labels should be provided for the total quantity
defined in the packspec.
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_PS_PARTLABEL is activated.

Activities
______________________________________________________________
SAP AG 389
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_PARTLABEL_LIST interface.

Example
An example implementation can be found in class /SCWM/CL_EI_PS_PARTLABEL
6.2.13.1.8.2.6 BAdI: PDF printing of Packaging Specification
Use
can use this BAdI to perform the PDF printing of a packaging specification. This BAdI is
called when you enter a PDF form name in Customizing. For further information see the
Implementation Guide (IMG) for SCM Basis under Pack -> Packaging Specification ->
Define General Packaging Specification Parameters.
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_PS_PRINT_PDF is activated.

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_PRINT_PDF interface.

______________________________________________________________
SAP AG 390
SAP System
______________________________________________________________
6.2.13.1.8.2.7 BAdI: Print Packaging Spec. Labels for Packaging

Specification or VAS Order
Use
can use this BAdI to to define own methods for the printing of labels of a packspec.
In method SET_PRINTER you can provide own logic, on which printer the labels shall be
printed.
In method SET_LANGUAGE you can provide own logic, in which language the printout should
occur.
In method EXECUTE you can print all labels that are listed in IT_PS_LABELS.
The badi methods are called:
- within the packspec maintainance (transaction /SCWM/PACKSPEC) when choosing option
'Print Labels'
- within the VAS order printing, if the action /SCWM/PARTLABEL has been configured
properly.
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_PS_PARTLABEL is activated.

The default code is executed automatically. Within the default implementation, the smartform
printing is called.
Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_PARTLABEL_PRINT interface.

______________________________________________________________
SAP AG 391
SAP System
______________________________________________________________
6.2.13.1.8.3 Packaging Specification Determination
USE&
enhancement spot /SCWM/ES_PS_DET.
6.2.13.1.8.3.2 BAdI: Prepare Packaging Specification Determination for Ext.

Field Catalog
Use
can use this BAdI to modify the determination data for packaging specification determination.
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_DET_PREPARE interface.

______________________________________________________________
SAP AG 392
SAP System
______________________________________________________________
Example
If you add additional fields to the packaging specification field catalogue, the determination data
for this new fields can be completed.
6.2.13.1.8.3.3 BAdI: Change Results of Packaging Specification

Determination
Use
can use this BAdI to modify the result of packaging specification determination.
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_DET_DETERMIN interface.

6.2.13.1.8.3.4 BAdI: Determine Results of Packaging Specification

Determination
Use
can use this BAdI to modify the result of packaging specification determination by doing own
evaluation after the system evaluation of the logical conditions.
______________________________________________________________
SAP AG 393
SAP System
______________________________________________________________
Standard settings

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_DET_EVALUATE interface.

6.2.13.1.8.3.5 BAdI: Additional Data When Saving Condition Records
Use
This Business Add-In (BAdI) is used in the Packings Basics (SCM-BAS-PAK) component. You
can use this BAdI to write additional data when saving condition records (such as change
documents).
Standard settings

Activities
______________________________________________________________
SAP AG 394
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface /SCWM/IF_EX_PS_DET_SAVE.

Example
If you want to write change documents for condition records, implement both methods: see
example implementation. (You also have to generate change document objects for the generated
condition tables.)
6.2.13.1.8.4 Work Steps User Interface
Use
enhancement spot /SCWM/ES_PS_WRKSTP_UI.
6.2.13.1.8.4.2 BAdI: User Interface Enhancement for Work Steps
Use
can use this BAdI to enhance the user interface for maintaining work steps, transaction
/SCWM/PSWORKSTEP. This is particularly suited in cases where implementation- specific
attributes need to be maintained/displayed.
The following subscreen areas are available:
- BADI_SUB_WS_DETAIL
- SUBSCREEN_2100 (TAB)
______________________________________________________________
SAP AG 395
SAP System
______________________________________________________________
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_WORKSTEP_UI is activated.

Activities
Create an implementation and assign your own subscreens.
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_WORKSTEP interface.

6.2.13.1.8.4.3 BAdI: Maintain Dynamic Attributes for Work Step
Use
can use this BAdI to maintain additional dynamic fields on the workstep user interface.
Standard settings
In the standard system, the BAdI implementation /SCWM/CL_EI_WORKSTEP_UI is activated.

Activities
______________________________________________________________
SAP AG 396
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCWM/IF_EX_PS_UI_WORKSTEP_DYN interface.

6.2.13.1.8.5 Distribution
Use
enhancement spot /SCWM/ES_PS_DISTR.
6.2.13.1.8.5.2 BAdI: Distribute Packaging Specification
Use
can use this BAdI to change data in the sending or receiving system when distributing
packaging specifications.
Standard settings

Activities
______________________________________________________________
SAP AG 397
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface /SCWM/IF_EX_PS_DISTR_PACKSPEC.

Example
For example, you can filter out packaging specifications of certain packaging specification
groups because they are not valid in the system.
6.2.13.1.8.5.3 BAdI: Distribute Element Groups
Use
can use this BAdI to change data in the sending and receiving system when distributing element
groups (for packaging specifications).
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCWM/IF_EX_PS_DISTR_ELEMGROUP.

Example
For example, you can filter out element groups in a system because they are not valid in the
system.
______________________________________________________________
SAP AG 398
SAP System
______________________________________________________________
6.2.13.1.8.5.4 BAdI: Distribute Work Step
Use
can use this BAdI to change data in the sending or receiving system when distributing work
packaging work steps.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCWM/IF_EX_PS_DISTR_WORKSTEP.

Example
For example, you can filter out packaging work steps of a particular type in the system,
because they are not valid in the system.
6.2.13.1.8.5.5 BAdI: Distribute Condition Records
Use
can use this BAdI to change data in the sending or receiving system when distributing condition
records (for packaging specifications).
Standard settings
______________________________________________________________
SAP AG 399
SAP System
______________________________________________________________

Activities
See also:
This BAdI definition uses the interface /SCWM/IF_EX_PS_DISTR_CONDITION.

Example
For example, you can filter out condition records for certain packaging specification groups in a
system, since these packaging specifications are not valid in the system.
6.2.13.2 Handling Units
6.2.13.2.1 Define Packaging Material Types
Use
Activities
______________________________________________________________
SAP AG 400
SAP System
______________________________________________________________
- Closed
- Status profile
- Delete
6.2.13.2.2 Define Packing Groups for Products
Use
In this IMG activity you define packing groups for products.

You can use packing groups to group products together that should be packed in the same way.
Example
A packing group can contain all products that are packed into bottles.
By assigning packing groups to packaging material types, you can prevent incorrect packing.
6.2.13.2.3 Maintain Allowed Packaging Material Types for Packing Group
Use
In this IMG activity, you define the allowed packaging material for the individual packing
groups.
When packing materials or handling units, the system checks whether the packaging material
type of the packaging material is permitted as packaging for the packing group of the material.
______________________________________________________________
SAP AG 401
SAP System
______________________________________________________________
Activities
For each packing group required create an entry with a required unit and a packaging material
type.
You can maintain the allowed packaging material types for each packing group depending on
the unit of measure of the material to be packed. Make sure that you maintain entries that are
to be independent of the unit of measure with an initial value.
To pack handling units, you must maintain an initial entry for the packing group of the
packaging material (and thereby) the handling unit, since handling units do not have units of
measure.
6.2.13.2.4 Define HU Types
Use
In this IMG activity, you define handling unit types (HU types).
HU types are used to describe the spatial appearance of a handling unit, and thus to find the
optimum storage bins, or to check whether a handling unit can be stored in a storage bin.
When constructing handling units on the basis of a packaging specification, the HU type is
copied from the packaging specifiation, or from the product master of the packaging material.
Requirements
If you have activated the enhancement for products in ERP, you must maintain the standard HU
type in the ERP system, and create identical HU types in Customizing for the ERP system.
Activities
Define all the HU types that exist in your company (or warehouse). You can copy HU types
created in the ERP system into Extended Warehouse Management.
6.2.13.2.5 Define Identification Types
Use
In addition to its main identification, you can also assign a number of other identifications to a
handling unit. To do this, you must define the identification type of the other possible
identifications here.
______________________________________________________________
SAP AG 402
SAP System
______________________________________________________________
Activities
Define here all the types of additional identifications that you want to assign to a handling unit.
Example
If you use serialized packaging materials with a fixed number stamped on, define an
identification type 'Serial Number' to be able to assign the packaging material identification to
the handling unit.
6.2.13.2.6.1 Basic Enhancements for Handling Units
Use
spot /SCWM/ES_HU_BASICS.
6.2.13.2.6.1.2 BAdI: Handling Unit Header Data
Use
This Business Add-In (BAdI) is used in the Extended Warehouse Management (SCM-EWM)
component. You can use this BAdI to change handling unit header data or to fill
customer-specific header data.
______________________________________________________________
SAP AG 403
SAP System
______________________________________________________________
Standard settings
The BAdI implementation is not activated in the standard system.

Activities
See also:
This BAdI definition uses the /SCWM/IF_EX_HU_BASICS_HUHDR interface.

6.2.13.2.6.1.3 BAdI: Nesting and Unpacking of Handling Units
Use
component. You can use this BAdI to perform your own check when packing and unpacking
handling units. You can also change customer-specific data in the handling units and their
higher-level handling units.
Standard settings

Activities
______________________________________________________________
SAP AG 404
SAP System
______________________________________________________________
See also:
This BAdI definition uses the interface /SCWM/IF_EX_HU_BASICS_NESTING.

6.2.13.2.6.1.4 BAdI: Product-Specific Checks During Packing / Unpacking
Use
component. You can use this BAdI to perform your own checks when packing and unpacking
products. You can also change customer-specific data in the affected handling unit and its
higher-level handling units.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCWM/IF_EX_HU_BASICS_PRODUCT.

6.2.13.2.6.1.5 BAdI: Automatic Packing By Packaging Specification
Use
This Business Add-In (BAdI) is used in the Extended Warehouse Management (SCM-EWM) and
Inventory Collaboration Hub (SCM-ICH) components. You can use this BAdI to create handling
______________________________________________________________
SAP AG 405
SAP System
______________________________________________________________
units in the inbound delivery or ASN automatically.
Standard settings

Activities
See also:
This BAdI definition uses the interface /SCWM/IF_EX_HU_BASICS_AUTOPACK.

6.2.14 Transport Load Builder (TLB)
6.2.14.1 Define TLB Parameters
Use
In this IMG activity, you define parameters for Transport Load Builder (TLB).
6.2.14.2 Make TLB Basic Settings
Use
In this IMG activity, you can make basic technical settings for the planning run of the
Transport Load Builder (TLB). The system takes these settings into account when you execute a
______________________________________________________________
SAP AG 406
SAP System
______________________________________________________________
TLB planning run in the background or interactively. The TLB is relevant to Supply Network
Planning in SAP Advanced Planning and Optimiziation (SAP APO) and to SAP Supply Network
Collaboration (SAP SNC).
You save the TLB basic settings as a profile and activate one of the profiles. The activated
profile is then globally valid for all TLB planning runs. However, before executing the TLB,
you can choose a different profile in the settings for the planning run.
You can make the following settings:
- Building Method: You determine whether the TLB forms the basis for the rounding value
of the product or the capacity of the means of transport in load building. Generally, you
can achieve a higher level of performance with the capacity-based method (standard value).
- Shipment Upsizing/Downsizing: In load building, remaining quantities can occur that are
not within the valid parameter limits for a shipment. For such cases, you can determine
that the TLB uses certain methods to upsize or downsize the quantities to be shipped. The
standard value is the binary search method.
- Heuristics for Shipment Upsizing/Downsizing: You can determine that the TLB skips
products with large rounding values (that therefore could prevent the creation of a valid
shipment) when shipment quantities are being upsized or downsized. The standard value is
that TLB does not use heuristics.
- Backtracking: You can determine the basic procedure for the TLB when products with
large rounding values prevent transport load building. The standard value is that TLB does
not use backtracking,
- Maximum Shipment Upsizing: For the method of shipment quantity upsizing, you can
determine that the TLB loads the shipments to the parameter upper limit as far as this is
possible. In the standard system, the TLB only carries out shipment upsizing up to the
valid area between the lower and upper limits.
- Shipment downsizing after shipment upsizing: If shipment quantity upsizing has failed, you
can determine that the TLB subsequently carries out shipment quantity downsizing. In the
standard system, the TLB does not carry out this kind of shipment downsizing.
- Redistribution: You can determine that the TLB loads all shipments to the parameter upper
limit. In the standard system, the TLB attempts to create valid shipments by only loading
some shipments up to the parameter lower limit.
- Settings for the Weight/Volume Mix function: The TLB can load a means of transport
in such a way that the load reaches a target weight/volume ratio. The target weight/volume
ratio is the ratio between the total weight and the total volume of the products loaded onto
the means of transport. In this IMG activity, you can choose between the following
methods:
- Static weight/volume ratio
Here the weight/volume ratio has a fixed, predefined value.
- Dynamic weight/volume ratio
Here the weight/volume ratio is the ratio between the total weight and the total
volume of the planned receipts in the horizon that you specify in this IMG activity.
You specify the weight/volume ratio in the units of measurement from the TLB profile of
the means of transport.
In this IMG activity, you can specify a tolerance for the weight/volume ratio. If the
______________________________________________________________
SAP AG 407
SAP System
______________________________________________________________
weight/volume ratio assumes a value beyond the tolerance during loading, the TLB
algorithm attempts to achieve a value within the tolerance again by loading a product with
a suitable weight/volume ratio next.
Standard settings
If you do not determine and activate your own profile, the TLB uses the standard settings
mentioned above.
6.2.15 Planning Service Manager
6.2.15.1 Define Process Profile
Use
In this IMG activity, you define how the system handles planning profile process blocks. A
planning profile can consist of several process blocks. You can set the following parameters for
every process block:
- Selection
- Process profile
- Planning version
- Optional: Trigger group
- Planning services
The system creates packages of objects that are processed together according to these settings.
You can specify the package creation method and maximum and minimum package sizes. You
can also specify whether the system processes the packages in parallel.
At the end of a process block or a package, the system always calls up the storage service
with the &SAVE+INIT profile.
Activities
To create a process profile, follow this procedure:

1. Select New Entries.
2. Enter a technical name for the process profile.
______________________________________________________________
SAP AG 408
SAP System
______________________________________________________________
3. Enter a description for the process profile in the "Process Profile" section.
4. Choose a package creation method in the "Package Creation" section and specify a
maximum package size (mandatory), and a minimum package size (optional). This defines
how the system creates packages in a process block.
5. Using the parallel processing active indicator in the "Parallel Processing" section, determine
whether you want to activate parallel processing.
6. In the "Application Log" area, select a minimum message type and a level of detail.
7. Save the process profile.
6.2.15.2 Define Storage Service Profile
Use
In this IMG activity, you define the profiles for the storage service. You can plan a storage
service in a planning profile as with other planning services.
The storage service saves the results of the previous planning run, or resets the buffer. You
can determine what you want the storage service to do using the Save Data and Clear Buffer
indicators. The system always executes the activities for the Save Data indicator first, and then
the activities for the Clear Buffer indicator. The storage service uses these indicators to access
data that is managed by the data managers.
The storage service profile works in two steps:
1. In the general settings, both the Save Data and Clear Buffer indicators apply for alldata
managers.
2. In data manager-dependent storage, you can set the Save Data and Clear Buffer indicators
individually for each data manager. The system carries out storage in order according to
the sequence number of the data manager
Standard settings
The storage service has the following standard storage service profiles:
- &INIT: Clears all data manager buffers (deletes all data in the buffer)
- &SAVE_ALL: Saves all new and modified data to the database
- &SAVE+INIT: First saves all new and modified data to the database and then clears
all data manager buffers
______________________________________________________________
SAP AG 409
SAP System
______________________________________________________________
Activities
To create a storage service profile, follow this procedure:

2. Enter a technical name for the storage service profile.
The technical name must start with a letter or number. Profiles that start with a special
character are reserved for SAP standard profiles.
3. Make the following settings in the "Storage Service General Settings" section:
- Enter a description of the storage service profile.
- Set the Save Data and Clear Buffer indicators, where necessary. Note that here, the
Save Data and Clear Buffer indicators apply to all data managers.
4. Make the following settings in the "Data Manager-Dependent Storage" section:
- Select New Entries.
- The system proposes a sequence number. You can accept this, or enter a a different
one.
- Select a data manager and set the indicators that you need.
- Select Next Entry to select further data managers
5. Save the storage profile.
6.2.15.3 Define Selections
Use
In this IMG activity, you define selections for the Planning Service Manager. You can define
selections for the following planning objects:
- Location product
- Product
- Location
- Transportation lane
- Expected inbound delivery items
You need the selections in the planning profile, so that the Planning Service Manager knows
which selections to consider in the planning runs.
You can change or delete selections that already exist. Make sure that you only change or
delete selections that you have created yourself.
______________________________________________________________
SAP AG 410
SAP System
______________________________________________________________
Standard settings
Using the SET/GET parameter /SAPAPO/PE_APPL, you can choose between different views:
- SPP: Selections for Service Parts Planning
- VMI: Selections for Responsive Replenishment
You can choose the applications for these views in Customizing under Configure Planning
Service Manager.
If, for instance, you only want the fields that are relevant to Service Parts Planning to be
displayed, you can set this up using the SET/GET parameter SPP. If you do not set any
SET/GET parameters, you will see all fields (generic view for all applications).
Activities
To define a selection, carry out the following activity:

1. In the Selection Type section, select whether you want to define a selection for a
location product, a product, a location, a transportation lane, or an inbound delivery item
to be expected.
2. In the Selection section, enter a new description for the selection.
3. Enter at least one value for the selection parameters.
If you want to define a selection for an expected inbound delivery item, you must make
an entry in at least on of the fields in the Expected Inbound Delivery Items area. For
performance reasons, we recommend that you make your selection not only for expected
inbound delivery items, but also further restrict you selection, for example, by expected
inbound delivery item and location (in this case, target location).
4. If you want to define a selection for a location, a product, or a location product, enter the
necessary data in the fields in the Location / Product / Location Product section.
5. If you want to define a selection for a transportation lane, enter the necessary data for the
means of transport, start location, target location, and product in the Transportation Lane
section.
6. If you want to define a selection for the expected inbound delivery items, enter at least
one delivery status, the number of days from the current date for the expected change in
status , and asynchronous requests in the Expected Inbound Delivery Items section.
7. Save your selection.
8. Finally, you can assign your selection to a planning profile. To do this run the Define
Planning Profile IMG Activity.
Additional Settings for Specific Planning Scenarios
If you work with the Service Parts Planning Scenario in SAP Advanced Planning and
Optimization (SAP APO), you can make the following additional settings in the Further
Selection Parameters section:
- Supplier (Location/Location Product): Enter a supplier.
______________________________________________________________
SAP AG 411
SAP System
______________________________________________________________
- Product Group (Product/Location Product): Enter a product group type and a product
group.
- Planner (Location Product): Enter a planner type and a planner code.
If you use the Responsive Replenishment scenario in SAP Supply Network Collaboration (SAP
SNC), you can select one or more planners is the Further Selection Parameters section.
6.2.15.4 Define Planning Profile
Use
In this IMG activity, you define the planning steps in a planning profile. To do this, you
specify the sequence of planning services that carry out specific planning tasks.
A planning profile is made up of three parts:
- Planning profile header data
- Planning profile process block
- Planning profile service list
You can define different planning profiles for the Planning Service Manager.
Note:
On the SAP Easy Access screen under SCM Basis-> Planning Service Manager ->
Current Settings -> Display Planning Profile, you can display the existing planning profiles
and search for specific planning profiles by selection parameters such as planning service or
process profile.
Requirements
You have defined at least one process profile. For more information, see the IMG activity
Define Process Profile.
You have defined the required selections. For more information, see the Define Selections IMG
activity.
Activities
To create a planning profile follow this procedure:

2. Enter a technical name for the planning profile.
3. Enter a description of the planning profile in the "Planning Profile Header Data" section.
4. Make the following settings in the #Planning Profile Process Block" section:
______________________________________________________________
SAP AG 412
SAP System
______________________________________________________________

- The system proposes a sequence process block number. You can accept this or enter a
different one.
- Choose a selection.
- Choose a process profile.
- Enter a planning version.
- Choose a trigger group (optional).
5. Make the following settings in the "Planning Profile Service List" section:
- The system proposes a sequence number. You can accept this or enter a different one.
- Enter a planning service and an (optional) service profile.
Within a process block, you can only use planning services in the service list that
have been assigned to the package creation method defined in the process profile. If
you have set the /SAPAPO/PE_APPL SET/GET parameter for an application, the only
planning services in input help are the planning services that are assigned to this
application.
If you have already entered a planning service, for this planning service, the input
help is available for service profiles.
- To plan more planning services, select Next Entry.
You can assign several planning services to a process block, which the system calls
up in order according to the sequence number during the Planning Service Manager
execution.
6. To define more process blocks, return to the "Planning Profile Process Block" section,
choose New Entries, and carry out the subsequent steps. A planning profile may consist
of several process blocks that are processed in sequence according to process block
number.
7. Save the planning profile
6.2.15.5 Assign Standard Service Profiles for UI
Use
In this IMG activity, you define standard service profiles for the UI. The standard service
profiles are used by UIs that call the planning services of the Planning Service Manager (PSM).
Not all UIs use the user-dependent standard service profiles, and only use the user-independent
default value (standard service profile with intial user).
Using the planning service optional mode, you can assign various standard service profiles to a
______________________________________________________________
SAP AG 413
SAP System
______________________________________________________________
planning service. The modes of the planning service are supplied with the planning services.
Standard settings
The user-independent default values of the standard service profiles used on the UIs are
provided by SAP.
Activities
To create a user-dependent standard service profile, proceed as follows:

1. Select the user-independent standard service profile you want to create a user-dependent
standard service profile for.
2. Select Copy.
3. Specify a user.
4. Select another service profile.
5. Save the standard service profile.
6.2.15.6 Configure Planning Service Manager
Use
In this IMG activity, you can see the configuration of the Planning Service Manager and make
additional configurations.
You must only execute this IMG activity if you want to create new planning services or data
managers.
Activities
- Under Planning Services you can display all of the Planning Services delivered by us. In
the Y* and Z* namespace you can create additional planning services. If you want to
create a new planning service, proceed as follows:
a) Specify a planning service and its description.
Note that planning services and data managers must not have the same name.
b) In the Class Name field, specify the implementation class of the planning service.
c) Specify a search help name when you create a service profile for a planning service.
Include the search help that was defined and specified here in the collective search
help /SAPAPO/PE_SERVICE_PROFILE so that the system displays it for the service
profile in the service list of the planning profile.
______________________________________________________________
SAP AG 414
SAP System
______________________________________________________________
d) You can specify a selection type.

Here you can specify the planning object with which the planning service is to call up
each service. If the Planning Service Manager can call the service with multiple
planning objects, or if a planning object is not needed for the service, you leave the
Selection Type field empty.
- Under Package Creation Methods you can display package creation methods that already
exist or create new methods in the Y* and Z* namespace. If you want to create a new
package creation method, proceed as follows:
a) Specify a method and a description for the method.
b) In the Class Name field, specify the implementation class of the method.
c) Optionally, you can specify which data manager the planning objects are to select; For
example, you can specify that you want the system to work with a location product
selection during the package creation method.
Alternatively, you can set the No Selection indicator, if you have not defined a
selection in the Planning Profile
For more information, see Package Creation Method.
- Under Assignment of Methods to Services you can display which package creation
method(s) is assigned to which planning service. You can also make your own assignments.
If you have created new planning services, you must assign at least one package creation
method to each one, otherwise the system cannot execute this planning service.
Under Assignment of Methods to Services you can also specify whether the Planning
Service Manager can call the service in parallel processing.
- Under Data Manager you can display the Data Managers delivered by us. In the Y* und
Z* namespace you can create your own additional data manager.
If you want to create a new data manager, proceed as follows:
a) Specify a data manager and the description of the data manager.
Note, that data managers and planning services must not have the same technical
name.
b) In the Class Name field specify the implementation class of the data manager.
c) When you create a data manager, specify with which interface the data manager can
be accessed.
d) Optionally you can specify a selection type.
- Under Data Manager Initial Parameters you can display initial parameters that already
exist, or create new initial parameters in the Y* and Z* namespace. Initial parameters can
be assigned to individual data managers. You control which data the system uses. In this
way you can for example use an initial parameter to define the assignment of a TDL data
manager to a TDL component and thus map the combination of business object and
component.
- Under Assignment Initial Parameters, you can display which initial parameter is assigned
to which data manager. Additionally, you can see the parameter value that is assigned to
the initial parameter.
Under Assignment Initial Parameters, you can also make you own assignments of initial
parameters to data managers.
______________________________________________________________
SAP AG 415
SAP System
______________________________________________________________
- Under Application you can see the applications that work with the Planning Service
Manager or create new applications.
Under Assignment Data Manager and under Assignment Planning Service you can
see which data managers and planning services are assigned to each application. You can
also assign new data managers and planning services to an application here.
- Under Assignment of Modes to Services you can see which mode is assigned to which
planning service. You can also make your own assignments. You can see the assignment of
modes and services in Customizing under Assign Standard Service Profile for UI.
6.2.15.7 Assign Selection Types to Application
Use
In this Customizing activity, you can assign selection types such as location (PE_LOC) or
location product (PE_LOCPROD) for applications such as Service Parts Planning (SPP) (for
more information about the possible applications, see Configure Planning Service Manager).
Additionally, you can assign the necessary selection parameters to the application types.
Activities
1. In the navigation tree, choose Assignment Selection Type and make sure that all
selections you need for a specific application are assigned to it. If any necessary selection
types are not assigned, assign them.
2. Select the necessary selection types one after the other. For each selection type, choose
Assignment Parameter in the navigation tree, and make sure that the necessary
parameters are assigned to the respective selection types. If any necessary parameters are
not assigned, assign them.
Example
You can, for example, assign the transportation lane (PE_LANE) selection type to the SPP
application if an SPP service requires selections of type transportation lane. Additionally, you
can assign the ship-to location (LOCNOTO) parameter and the ship-from location (LOCNOFR)
parameter to the transportation lane selection type. Then, you can define selections of the
PE_LANE selection type and the assigned selection parameters for the SPP application on the
Define Selections screen. You can access the Define Selections screen from the SAP Easy
Access screen by choosing Advanced Planning and Optimization -> Service Parts
Planning -> Environment -> Current Settings -> Planning Service Manager.
______________________________________________________________
SAP AG 416
SAP System
______________________________________________________________
6.2.15.8 Define Service Profile for Example Service
Use
You can use this IMG activity to create a service profile for an example service.
Activities
Enter an ID and a description of the example service and assign an application to the latter. If
you then execute the example service in the planning service manager, the system invokes the
data manager of the assigned application.
6.2.16 Data Management Layer
6.2.16.1 Triggers (for Planning File Entry)
6.2.16.1.1 Configure Triggers
Use
In this IMG activity, you define triggers for the planning file entry.
You enter selection types and services, which you assign to triggers. You can only use selection
types provided by the selection management.
Triggers for the planning file entry are set or deleted when certain changes are made to master
data, and in various planning services of the Planning Service Manager. To limit the selection,
the Planning Service Manager considers triggers for the planning file entry using trigger groups.
Requirements
Selection types and services must be defined in order to define triggers.
Activities
Selection Types
______________________________________________________________
SAP AG 417
SAP System
______________________________________________________________
1. Select a selection type. This determines the planning object the trigger can be set for.
2. Enter the name of the table you want the triggers to be saved in.
3. Enter the access class you want to use to read, set, and delete triggers.
Services
1. Select a service to use for the planning file entry triggers.

2. Enter a description.
3. You also have the option of assigning an external service to the service.
There is an input help for the description and the external service where you can select
the planning services of the Planning Service Manager and their description, for example.
Define Triggers
1. Select a trigger name.

2. Enter a description.
3. Using the BAdI Trigger indicator, determine whether you want the trigger value for this
trigger to be calculated in a Business Add-in (BAdI).
4. In the Trigger Attribute Specifications section, use the Not Visible on UI and Not
Modifiable on UI indicators to determine whether, generally, you want the trigger not to
be visible and/or modifiable on the UI. BAdI triggers are not visible or modifiable on the
UI.
Additionally, specify whether you want the triggers to be deleted from the data base. If the
same trigger is frequently created and deleted, it can improve the performance not to delete
it from the data base.
5. In the Assignment of Service and Attributes to Triggers section, make the following
settings:
a) Select a service.
b) Select a selection type.
c) In the Trigger Attributes for Service/Selection Type section, use the Visible on UI
and Modifiable on UI indicators to determine whether you want the trigger (a
combination of the trigger name, the service, and selection type) to be visible and
modifiable on the UI. Trigger names can be entered for the indicators according to
the settings in the trigger attribute specifications. You can use the Active indicator to
determine whether the trigger (combination of trigger name, service, and selection
type) is activated or deactivated. You can activate triggers in Customizing under
Activate Trigger.
______________________________________________________________
SAP AG 418
SAP System
______________________________________________________________
6.2.16.1.2 Define Trigger Groups and Attributes
Use
In this IMG activity, you define:

1. Trigger groups and
2. Trigger attributes.
You can use the trigger groups in the Define Planning Profile IMG activity of the Planning
Service Manager.
The trigger attributes are evaluated in the Triggers for Planning File Entry transaction.
Activities
To create a trigger group, proceed as follows:

1. Select the Trigger Group section.
3. Enter a technical name and a description.
4. Assign at least one trigger name, service, or selection type to the trigger group in the
relevant sections, or include a trigger in the Include/Exclude Trigger section:
a) Select a trigger name in the Assignment of Trigger Names to Trigger Groups
section (optional).
b) Select a service in the Assignment of Services to Trigger Groups section
(optional).
c) Select a selection type in the Assignment of Selection Types to Trigger Groups
section (optional).
d) Select optional triggers in the Include/Exclude Trigger section that you would like
to include in or exclude from the trigger group. By choosing exclude, you can
exclude triggers that are assigned to the trigger group from the group. By choosing
include you can additionally include triggers that are not assigned to the trigger group
in the group. When you save your settings you can see the new assignment of
triggers to the trigger group on the SAP Easy Access screen under SCM Basis
-> Data Management Layer -> Display Triggers of Trigger Group .
You then determine whether you want the trigger (a combination of the trigger name, service,
and selection type) to be visible and modifiable on the UI. You define this in the Trigger
Attributes section using the Visible on UI and Modifiable on UI indicator. Trigger names can
be entered for indicators according to the settings in the trigger attribute specifications.
Additionally, you can define whether you want triggers to be deleted from the data base. If the
same trigger is frequently created and deleted, it can improve the performance not to delete it
______________________________________________________________
SAP AG 419
SAP System
______________________________________________________________
from the data base.
6.2.16.1.3 Activate Trigger
Use
In this IMG activity, you activate and deactivate triggers for specific planning services. In so
doing, you can either activate and deactivate triggers for individual services or for all services
of a planning area.
6.2.16.1.4 Business Add Ins (BAdIs) for Trigger
6.2.16.1.4.1 Determine Trigger Values for Location Products (Only BAdI

Triggers)
Use
This Business Add-In (BAdI) is used in the Data Management Layer (SCM-BAS-DM)
application component.
You can use this BAdI to set the trigger values.
This BAdI is always called when trigger values are read for a BAdI trigger.
Standard settings
- The BAdI is not active in the standard. If there is no active implementation, the trigger
values for the BAdI trigger are not set.
- The BAdI is not reusable.
Activities
______________________________________________________________
SAP AG 420
SAP System
______________________________________________________________
6.2.16.1.4.2 Determine Trigger Values for Products (Only BAdI Trigger)
Use
You can use this BAdI to set trigger values.
This BAdI is always called when trigger values are read for a BAdI trigger.
Standard settings
- The BAdI is not active in the standard. If there is no active implementation, the trigger
values for the BAdI trigger are not set.
- The BAdI is not reusable.
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 421
SAP System
______________________________________________________________

8. Choose Activate.
you wrote.
6.2.16.1.4.3 Determine Trigger Values for Location (Only BAdI Triggers)
Use
You can use this BAdI to set trigger values.
This BAdI is then always called when trigger values for a BAdI trigger is read.
Standard settings
- The BAdI is not active in the standard system. If there is no active implementation, the
trigger values for the BAdI Trigger are not set.
- The BAdI is not designed for multiple uses.
Activities
6.2.16.2 Transaction Data Layer (TDL)
6.2.16.2.1 TDL: Configure Decision Tables
______________________________________________________________
SAP AG 422
SAP System
______________________________________________________________
Use
In this IMG activity, you configure which transaction data types (business objects) lie in which
data source.
The transaction data layer (TDL) is called with the following parameters:
- Business objects (for example, time series)
- Component (for example, ATP)
- A free table with parameter/parameter value pairs
This table is optional. (for example, version - 000)
TDL uses these parameters to decide, according to the settings that you make here, where the
relevant data lies. Here the place where the data is found corresponds to the relevant data
access object (DAO) that encapsulates the access for a business object in one data source only.
You can make the following settings:
BO component pairs:
- Business object component combinations that define the business objects that the relevant
component is allowed to access.
- Here you can define a default DAO. This field is optional. If no default DAO is defined,
the system looks for DAOs in only those decision tables that are defined for the current
combination.
- If a default DAO is defined, it is used if no other DAO is found in the decision tables.
Valid parameters:
- This defines which parameters are allowed for the current business object component
combination.
Decision table ID:
- Here you define the decision table IDs for the business object component combination that
is currently selected. You must enter a data access object (DAO) in the column DAO. At
runtime if the content of this decision table is the same as the content of the parameters
provided to the TDL, this DAO is used.
Content of decision tables:
- Here you define the content of the current decision table. The whole content must
correspond to the parameters transferred to the TDL at runtime. Partial quantities are not
counted as an agreement.
- The parameters that you can choose here are defined under Valid Parameters.
- You cannot define two decision tables with identical content for one business object
component combination. Otherwise, an error is issued by the maintenance view cluster.
______________________________________________________________
SAP AG 423
SAP System
______________________________________________________________
DAO initialization parameters:
- These settings allow initialization parameters to be transferred to the DAO instances created
at runtime. These settings are purely technical in nature and require knowledge of the
codes for the individual DAOs.
6.2.16.2.2 TDL: Make Basic Settings
Use
In this IMG activity, you configure the transaction data types (business objects) that are
processed by the transaction data layer (TDL). Here you define the types of transaction data
(business objects) that the TDL can administer.
Caution: The settings in the TDL are fundamental settings and can result in
cross-application errors and data inconsistencies if they are handled incorrectly.
The following settings are required for a business object:
Business object type:
- The type of a business object with the relevant class interface and a descriptive text.
Components:
- Application that accesses the business objects.
Factory:
- Object that instantiates the data access objects (DAOs). Each factory refers to a data
source.
Data access object (DAO):
- A DAO is a class that contains the methods for accessing a data source and a business
object, for example, time series (business object) in Business Information Warehouse (data
source).
- A DAO must always be assigned to a factory that then creates a DAO instance at runtime.
______________________________________________________________
SAP AG 424
SAP System
______________________________________________________________
BO component pairs:
- Business object component combinations that define the business objects that the relevant
component is allowed to access.
- Here you can define a default DSO. This field is optional. If no default DAO is defined,
the system looks for DAOs in only those decision tables that are defined for the current
combination.
- If a default DAO is defined, it is used if no other DAO is found in the decision tables.
Requirements
The relevant factories and DAOs must be implemented. You can find them in the packages
/SCMB/TDL and /SAPAPO/TDL.
6.2.16.2.3 TDL: Configure Settings for Semantic Mapping
Use
In this IMG activity, you maintain the semantics that are converted within the transaction data
layer (TDL) from the various data sources into the relevant technical information for reading
transaction data.
Caution: Only use this IMG activity if you have not installed the component Advanced
Planning and Optimization (APO).
If you have installed APO, you must execute the relevant IMG activity in APO. You can find
this in the Implementation Guide (IMG) for Advanced Planning and Optimization under Basis
Settings -> Transaction Data Layer (TDL) -> Configure Settings for TDL Semantics.
In this IMG activity, you can maintain the following semantics:
- Time series key figures: Semantics for the key figures of the TSDM key figures. Here
you must assign a TSDM key figure to each semantic.
- Stock semantics: Semantics for reading stock information from LIME.
In this IMG activity, you can also configure the time series IDs (TSIDs). A time series ID
describes a type of grouping of time series based on business criteria that contains the basic
technical parameters of the data sources liveCache, TSDM, and BW.
Moreover, you can also make the following settings:
- Time series mapping: Here the following is assigned to a time series ID:
- TSDM time series type
______________________________________________________________
SAP AG 425
SAP System
______________________________________________________________
- InfoProvider
- Planning area (for liveCache)
All three parameters are optional.
- Time series semantic: Here the time series IDs are assigned to semantics.
6.2.16.2.4 TDL: Define Service Profile for Copying Transaction Data
Use
In this IMG activity you define a service profile for copying and deleting transaction data.
Activities
Make the following settings under Copy/Delete Time Series in the navigation tree on the left:
- Enter a service profile.
- Enter a source time series ID.
- Enter the planning version of the data source.
- Enter a target time series ID.
- If you do not want to use all available data for copying or deleting transaction data, you
can specify the time period of the data that you want to use.
- Enter the semantic of the time characteristic. You can choose from the following values:
- Year
- Month
- Week
- Day
- Posting period
- Specify whether you want to copy the data of the past forecasts.
- Choose whether you want to copy or delete the time series.
______________________________________________________________
SAP AG 426
SAP System
______________________________________________________________
- Specify a key figure assignment that you have defined under Key Figure Mapping in the
navigation tree on the left.
Make the following settings under Key Figure Mapping in the navigation tree on the left:
- Define a key figure assignment.
- Choose a semantic of the source key figure. The semantic you choose here must be in the
source time series ID that you specified under Copy/Delete Time Series in the navigation
tree on the left.
- Choose a semantic of the target key figure. The semantic you choose here must be in the
target time series ID that you specified under Copy/Delete Time Series in the navigation
tree on the left.
Make the following settings under Copy/Delete Order Documents in the navigation tree on
the left:
- Specify a service profile.
- Specify the planning version of the data source.
- Specify whether the product selection that the system selected for simulation in transaction
/SAPAPO/SPP_SIM is to be applied to start or destination location products. To do this,
choose one of the following selection modes:
- Requirement Date and Start Location Product
- Availability Date and Destination Location Product
- If you do not want to use all available data for copying or deleting transaction data, you
can specify the time period of the data that you want to use. This period refers either to
the requirement date, or the availability date, depending on your entry in the Selection
Mode field.
- Choose whether you want to copy or delete the data.
- Enter an order category selection that you have defined under Order Category Mapping
in the navigation tree on the left.
Make the following settings under Order Category Mapping in the navigation tree on the left:
- Define an order category selection.
- Specify the order category to be copied.
Make the following settings under Copy/Delete Stocks in the navigation tree on your left.
- Specify a service profile.
- Specify the planning version of the data source.
- Choose whether you want to copy or delete data.
- Specify a stock semantic assignment that you have defined under Stock Semantic
Mapping in the navigation tree on the left.
Make the following settings under Stock Semantic Mapping in the navigation tree on your
left:
- Define a stock semantics assignment.
______________________________________________________________
SAP AG 427
SAP System
______________________________________________________________
- Choose the stock semantics to be copied. You can only choose stock semantics that start
with INV_.
6.2.16.2.5 Define Reason Code for Fixed Demands
Use
In this IMG activity, you define the reason codes for fixed demands. Reason Codes is a
mandatory field on the Fixed Demands and Fixed Receipts screen.Therefore, you must
specify a reason code on this screen to create a fixed demand. To access the Fixed Demands
and Fixed Receipts screen, on the SAP Easy Access screen, choose Advanced Planning
and Optimization -> Service Parts Planning (SPP) -> Planning -> Distribution
Requirements Planning (DRP).
Activities
Create reason codes in the customer namespace (meaning they begin with 9) and assign a
description to each reason code .
If you set the Non-Changeable Fixed Demand/Receipt indicator for a reason code, fixed
demands and fixed receipts with this reason code cannot be created, changed, or deleted on the
Fixed Demands and Fixed Receipts screen.
You can upload fixed demands with a reason code for which you have set the
Non-Changeable Fixed Demand/Receipt indicator with a Business Application Programming
Interface (BAPI), for example. You cannot then change or delete these fixed demands on the
Diese Fixbedarfe können Sie dann im Bild Fixed Demands and Fixed Receipts screen. In
this case, you can only change or delete these fixed demands in the BAPI itself.
6.2.16.2.6 Define Reasons for Ordering
Use
In this IMG activity, you can define reasons for ordering for scheduling agreement delivery
schedules, purchase requisition items, or purchase order items. You can use the reasons for
ordering when communicating with your vendors, or for internal purposes.
Examples of reasons for ordering, visible to vendors:
- Last procurement option
______________________________________________________________
SAP AG 428
SAP System
______________________________________________________________
- Analyst decision
- Examples for internal reasons for ordering:
- Quota arrangement change
- Product group procurement
You can view the reasons for ordering that are visible to vendors on the External
Procurement - Delivery Schedule Maintenance screen under Advanced Planning and
Optimization -> Spare Parts Planning (SPP) -> Planning -> DRP.
If multiple reasons for ordering that are visible to vendors are assigned to an order, the system
sends the reason for ordering with the highest priority to the vendor.
You can use the reasons for ordering 'usable without restriction 01' through 'usable without
restriction 08' for your own purposes.
Activities
You can make the following settings for every reason for ordering:
Enter a Description for Reason for Ordering.
Enter a Code for Reason for Ordering.
Set the indicator No Changes Using DRP Allowed(fixed) if you do not want DRP to change
scheduling agreement items, purchase requisition items, or purchase order items.
Specify whether reasons for ordering must always be subject to a manual review.
Specify whether reasons for ordering are visible to your vendors or whether they are for
internal use only.
Assign a Priority to the reason for ordering.
6.2.17 EH&S Services
6.2.17.1 Basic Services
6.2.17.1.1 Specify Environment Parameters
Use
______________________________________________________________
SAP AG 429
SAP System
______________________________________________________________
In this IMG activity, you specify environment parameters that control the processes in EH&S
Services.
Environment Parameter Meaning
ALE_LOG_PRODUCT_NOT_EXIST Messages in Distribution Log
ALE_TRANSFER_LANGUAGE ALE Transfer Language
DG_PAPER_DEFAULT_TEXTPATTERN Default Text Pattern Phrase
DG_PAPER_DEFAULT_TP_<GGVORSCHRIFT> Default Text Pattern Phrase, DG
DG_DISTRIBUTION_SAVE IDoc Update
DG_FILL_EXIT_CHECK User Exit for Verification of Distribution
DG_SERVICES_ACTIVE Activation of Dangerous Goods Services
DG_SUPPRESS_PHR_CHECK Switch Off Phrase Check
GEN_PHRASE_SORT_ORDER Phrase Sorting
HSM_DIST_LOG_TIME_TO_LIVE Validity Period of Entries in Application Log
for Hazardous Substance Distribution
MULTI_CODEPAGE_SUPPORT Conversion by EH&S NLS
Standard settings
Default settings are supplied.
6.2.17.1.2 Manage User Exits
Use
In this IMG activity, you define function modules for the user exits for EH&S Services. The
following user exit categories are available:
User Exit Category Meaning
PHR_QUERY Phrase search
PHR_TEXT Replace text variables for phrases
Standard settings
Standard enhancements (user exits) are supplied with reference function modules. For some
reference function modules, some standard environment parameters with default values are also
supplied.
______________________________________________________________
SAP AG 430
SAP System
______________________________________________________________
6.2.17.1.3 Assign Parameter User Exits
Use
In this IMG activity, you specify the values of the environment parameters for the user exits
you defined under Manage User Exits. The values you specified are then available in the IMG
activity Manage User Exits under Parameters and Values in the input help for the
Environm. Parameter field.
6.2.17.1.4 Specify Validity Area Categories
Use
In this IMG activity, you define validity area categories that you use to group validity areas
together in organizational units in the IMG activity Specify Validity Areas.
If you want to set up dynamic input help that is dependent on the validity area category for the
Validity area field in the IMG activity Specify Validity Areas, enter appropriate values in the
following three fields:
Field Description
Table name DDIC table or your own table
Field name Dependent on table specified
Check function Optional
You can enter a check function to check the value that the user enters in the Validity area
field with regard to the table and field names depending on the validity area category.
6.2.17.1.5 Specify Validity Areas
Use
The validity area determines in which jurisdictions data is commonly valid.

You specify validity areas depending on the validity area categories. You can use the validity
area categories to define plants, business areas, or regions, for example, as validity areas.
You can assign individual jurisdictions or organizational units at a lower level to each validity
area, for example:
- You can assign countries and regions from the country table as validity areas for validity
areas of the category REGION.
- You can assign other organizational units for validity areas of another category.
______________________________________________________________
SAP AG 431
SAP System
______________________________________________________________
Example
The validity area European Union is made up of the member states and requires the
assignment of all member states' country keys.
6.2.17.1.6 BAdI: Wrapper for Material Master and Product Master
Use
This Business Add-In (BAdI) is used in the EH&S Services (SCM-BAS-EHS) component.
The BAdI provides services for accessing material master data or product master data,
depending on whether you use the material master or the product master in your system. To
make this document and the documentation of the methods easier to read, we refer to these
using the terms product and product master only. These services are used in Hazardous
Substance Management and Dangerous Goods Management in EH&S Services. The
BAdI is called at various points in these components.
For more information on the enhancements you can define with this BAdI and the places where
the BAdI can be called and its dependencies, see the documentation of the methods.
Requirements
The default code assumes that the master data is stored in the product master in Advanced
Planning and Optimization (APO) and accesses the relevant tables and function modules. If
you do not use the APO product master or store your master data at a different location in
future, you must adapt the code accordingly.
Standard settings
The BAdI is not active in the standard system. Default code is supplied, which is executed if
there is no active implementation. The BAdI is not filter-dependent and is not intended for
multiple use. If you activate the BAdI in an SCM system without modifying it, the standard
system behavior is not affected.
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 432
SAP System
______________________________________________________________
8. Choose Activate.
you wrote.
Example
See also
Methods
Check Authorizations for Access to Product Master Data
Display Field Help for Product Master Attributes
Display Input Help for Product Master Data Search
Determine Reference Field for Product Number (F4 Help)
Convert Product Number
Check Existence of One Product
Check Existence of Several Products
Read Language-Dependent Short Text for One Product
Read Language-Dependent Short Text for Several Products
Read Environmentally Relevant Data for One Product
Read Environmentally Relevant Data for Several Products
Start Application in EH&S Environment
Convert Product Keys During Distribution
______________________________________________________________
SAP AG 433
SAP System
______________________________________________________________
6.2.17.2 Phrase Management
6.2.17.2.1 Specify Number Ranges for Phrases
Use
In this IMG activity, you define number ranges for phrase keys. Each phrase is identified
uniquely by a phrase key within one client.
From the defined number ranges, numbers are assigned.
Requirements
To be able to define number ranges for phrase keys, you need authorization for the number
range object ESN_PHRID. This object is checked in the authorization object S_NUMBER.
6.2.17.2.2 Specify Phrase Libraries and Phrase Groups
Use
In this IMG activity, you define the phrase libraries and the corresponding phrase groups. You
must mark one library as an active library.
Requirements
You have defined number ranges for the phrase keys.
Activities
1. Create the required phrase libraries. Note that the phrase library key must not contain
hyphens.
2. Define one phrase library as the active library. Note that changing to another active phrase
library is difficult and should therefore be avoided.
3. Enter the phrase groups required for the phrase libraries.
You can also enter phrase groups later in productive systems.
6.2.17.2.3 Specify Language Selection
Use
In this IMG activity, you specify the languages that you can use for phrases in EH&S
______________________________________________________________
SAP AG 434
SAP System
______________________________________________________________
Services.
Caution:
You can specify only languages that can be displayed using the code pages installed.
Activities
1. Enter the language key(s) for the language(s) you require.

2. Specify the sort sequence for the languages. The phrases appear in this sequence in the
phrase display and for translation.
6.2.17.2.4 Specify Phrase Statuses
Use
In this IMG activity, you specify the statuses that you can assign to an individual phrase item.
For each status, you define whether a phrase item with this status can be edited.
Note:
You can also use phrase management without status assignment.
Standard settings
6.2.17.2.5 Configure Distribution for Phrases
Use
This IMG activity describes the settings that you must make in this system to distribute phrases
via Application Link Enabling (ALE) from an ERP system to this system. For more information
about the settings in the ERP system, see the Implementation Guide in that system.
The settings in this system are different from those you have to make in the ERP system
because the Environment, Health and Safety (EH&S) component and thus the corresponding
business object for the distribution of phrases do not exist in this system.
Activities
1. Under Logical Systems, create the logical systems and assignments to clients for all
systems involved in distribution.
2. Since this system does not contain a business object for the distribution of phrases and thus
no distribution model, you must create the partner profiles manually. Create a profile for
the sending system and assign the process code BAPI_SCM_PH to the message type
PHRMAS in the inbound parameter. This code stands for a function module that is called
______________________________________________________________
SAP AG 435
SAP System
______________________________________________________________
to post the phrase IDocs.

3. Since standard serialization using the business object cannot be used for distribution to this
system, you must adapt the partner profile for serialization manually under Processing by
Function Module by choosing the pushbutton Trigger by Background Program. This is
necessary so that the inbound IDocs are not posted immediately but can be processed in
sequence using a report.
Note:
You should make this adjustment for the initial distribution also because otherwise lock
problems can occur with IDocs with large amounts of data. For delta distribution you must
always make this adjustment.
4. Create a variant for serialization for the report RBDAPP01 that is restricted to the message
type PHRMAS (Logical Message field) and sends the maximum number of IDocs.
5. Schedule a periodic job for this variant. This report ensures that the IDocs are posted in
exactly the order in which they were created. This prevents the IDocs being posted in
parallel, which can lead to errors.
6.2.17.2.6 BAdI: ALE and Menu Enhancement for Phrases
Use
With this BAdI you can define enhancements for the distribution of phrases via Application
Link Enabling (ALE), which are executed when phrases are posted by the recipient and when
phrases are distributed by the sender. You can thus transfer additional data via ALE or build in
your own data filters. In addition, you can define up to two menu exits, which are available
when you display or edit phrases. You can thus include additional functions in phrase
management.
Standard settings
The BAdI is not active in the standard system. If you activate it and do not implement your
own method, the standard system behavior is not affected.
The BAdI is not filter-dependent, but is intended for multiple use.
Activities
the implementation.
______________________________________________________________
SAP AG 436
SAP System
______________________________________________________________
Short Text field.

8. Choose Activate.
you wrote.
See also
Methods
Modify Phrases Before Distributing
Modify Phrases After Receiving
Send Own Phrase Data
Receive Own Phrase Data
Menu Exit 1 for Phrase Management
Menu Exit 2 for Phrase Management
6.2.17.2.7 Authorization Management
6.2.17.2.7.1 Specify Authorizations
Use
In this IMG activity, you can create activity groups and create authorization profiles using the
Profile Generator.
Activities
To assign an authorization profile to a user, proceed as follows:

1. Create an activity group.
2. Create a description.
______________________________________________________________
SAP AG 437
SAP System
______________________________________________________________
3. Select transactions.
4. Create and edit authorizations.
5. Assign users and adjust the user master records (this enters the profile for the users).
6. Transport activity groups if desired.
For more information, see the documentation for the transaction.
Note:
Manually created authorization profiles or authorization profiles supplied by SAP can be used in
activity groups. You can create an activity group without the menu and add the corresponding
profile to the authorization data for the activity group.
Choose Edit -> Add Authorization -> From Profile in step 4. to include the data of an
authorization profile in the activity group.
The authorization objects for phrase management are C_EHSP_TPP (phrase item) and
C_SHEP_TPG (phrase library and phrase group).
6.2.17.3 Hazardous Substance Master
6.2.17.3.1 Mast. Data
6.2.17.3.1.1 Specify Storage Hazards
Use
In this IMG activity, you specify the types of storage hazards and the corresponding hazard
ratings, for example:
Storage Hazard Type Hazard Rating
WPC 1
WPC 2
WPC 3
VbF AI
VbF AII
WPC = Water pollution class

VbF = German law on combustible liquids
The storage hazard types and the hazard ratings are then available in the hazardous substance
master for the assignment of hazardous substances, so that you can specify for each hazardous
substance which storage hazard it poses. Since the regulations for hazardous substances can be
different from region to region, in this activity you can assign the storage hazard types to
individual countries and regions. By doing this, you restrict the usage of these storage hazard
______________________________________________________________
SAP AG 438
SAP System
______________________________________________________________
types in the hazardous substance master to the assigned countries and regions.
The putaway checks in Extended Warehouse Management (EWM) use the hazard ratings
you assigned in the hazardous substance master. These ensure that you can store your hazardous
substances safely and correctly.
6.2.17.3.1.2 Specify Text Types
Use
For hazardous substances, you often have to specify certain texts such as R phrases, S phrases,
and hazard symbols. This means you must specify texts of certain text types. In this IMG
activity, you specify which text types are available in the hazardous substance master, that is
which fields the system offers you in the hazardous substance master for these types of text.
For each text type you can define the following:
- You can specify whether the hazardous substance master for a hazardous substance can
contain several texts of a text type.
- You can specify a document that the system offers you in the hazardous substance master
as the F1 help for the text type field.
Example
If you make the following entries in this IMG activity, the hazardous substance master can
contain R phrases, S phrases, and hazard symbols:
Text Type Description for Text Type ID Docu Object
RPHR R phrase TX ZR_PHRASE
SPHR S phrase TX ZS_PHRASE
HAZSYM Hazard symbol TX ZHAZSYM
As the F1 help for the fields, the system displays the general texts ZR_PHRASE, ZS_PHRASE,
and ZHAZSYM.
6.2.17.3.1.3 Specify Numeric Value Types
Use
For hazardous substances, you often have to specify certain numeric values such as a flash
point. This means you must specify numeric values of certain types. In this IMG activity, you
specify which types of numeric values are available in the hazardous substance master. For each
type of numeric value you can specify a document that the system offers you in the hazardous
substance master as the F1 help for the numeric value type field.
______________________________________________________________
SAP AG 439
SAP System
______________________________________________________________
6.2.17.3.1.4 Activate Phrase Assignment
Use
In this IMG activity you activate the fields in the hazardous substance master that are intended
for the assignment of phrases. If you do not activate phrase assignment, you cannot assign any
phrase sets in phrase set-attribute assignment.
6.2.17.3.1.5 Create Standard Phrase Sets
Use
In this IMG activity, you create phrase sets for all fields in the hazardous substance master that
are intended for the assignment of phrases. The following applies here:
- The system automatically assigns the newly created phrase sets to the fields. You can edit
this assignment in the phrase set-attribute assignment.
- The system does not overwrite any existing assignments of phrase sets to fields in the
hazardous substance master.
- If you do not want to create a phrase set and assign it to a field that is intended for the
assignment of a phrase set, you must delete the assignment in phrase set-attribute
assignment and delete the created phrase set.
- The system does not create phrases and does not automatically assign phrases to the
created phrase sets.
Requirements
You have activated phrase assignment.
6.2.17.3.1.6 BAdI: Checks When Deleting Hazardous Substance Master

Records
Use
With this BAdI you can define enhancements that are executed when you delete hazardous
substance master records. For example, with this BAdI you can prevent a hazardous substance
master being deleted if stocks of the hazardous substance still exist.
Note:
This BAdI is not taken into account when hazardous substance master records are
______________________________________________________________
SAP AG 440
SAP System
______________________________________________________________
distributed. This means that when hazardous substance master records are distributed from
an ERP system to this system and hazardous substance master records therefore need to be
deleted in this system, the checks in this BAdI are not run.
Standard settings
The BAdI is not active in the standard system. If you activate it and do not implement your
own method, the standard system behavior is not affected.
The BAdI is not filter-dependent and not designed for multiple use.
Activities
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
See also
Methods
Checks When Deleting Hazardous Substance Master Records
______________________________________________________________
SAP AG 441
SAP System
______________________________________________________________
Use
In this IMG activity, you can create activity groups and create authorization profiles using the
Profile Generator.
Activities
To assign an authorization profile to a user, proceed as follows:

For more information, see the documentation for the transaction.
Note:
Choose Edit -> Add Authorization -> From Profile in step 4. to include the data of an
The authorization object for the hazardous substance master is HSMA.
6.2.17.3.3 Distribution
6.2.17.3.3.1 Configure Distribution for Hazardous Substance Master
Use
This IMG activity describes the necessary settings to receive hazardous substance data that was
distributed via Application Link Enabling (ALE) from an ERP system.
Note:
In EH&S Services in the SCM system, you can only process incoming hazardous
substance data. You cannot therefore distribute hazardous substance data from an SCM
______________________________________________________________
SAP AG 442
SAP System
______________________________________________________________
system.
The settings in the receiving SCM system are different from those in the sending ERP system
because the hazardous substance business object exists only in the sending ERP system. For
more information about the settings in the sending ERP system, see the Implementation Guide.
Activities
1. Under Logical Systems, create the logical systems and assignments to clients for all
systems involved in distribution.
2. Create the partner profiles for the sending ERP system and the receiving system manually.
Create a profile for the sending system and assign the process code BAPI_SCM_HM to the
message type HAZARDOUSSUBSTANCE in the inbound parameter. This code stands for a
function module that is called to post the hazardous substance IDocs.
3. Since standard serialization using the business object cannot be used for distribution to this
system, you must adapt the partner profile for serialization manually under Processing by
Function Module by choosing the pushbutton Trigger by Background Program. This is
necessary so that the inbound IDocs are not posted immediately but can be processed in
sequence using a report.
Note:
You should make this adjustment for the initial distribution also because otherwise lock
problems can occur with IDocs with large amounts of data.
For delta distribution you must always make this adjustment.
4. Create a variant for serialization for the report RBDAPP01 that is restricted to the message
type HAZARDOUSSUBSTANCE (Logical Message field) and sends the maximum number
of IDocs.
5. Schedule a periodic job for this variant. This report ensures that the IDocs are posted in
exactly the order in which they were created. This prevents the IDocs being posted in
parallel, which can lead to errors.
6.2.17.3.3.2 BAdI: Hazardous Substance Distribution
Use
With this BAdI you can define enhancements that are executed when you distribute hazardous
substance data via Application Link Enabling (ALE). The enhancements are executed at the
following points:
- When hazardous substances are posted by the recipient
- When hazardous substances are distributed by the sender
With this BAdI you can also transfer data via ALE at these points or build in your own data
filters.
______________________________________________________________
SAP AG 443
SAP System
______________________________________________________________
Standard settings
The BAdI is active in the standard system and executes default code. If you deactivate it, the
standard system behavior is affected.
The standard implementation executes the following steps when hazardous substance data is
posted and should always be called when data is transferred from an ERP system to an SCM
system:
- If change numbers are used in the data to be transferred, the system replaces these with
change numbers that it searches for in the target system and creates if required. This
means the system does not need to transfer the change numbers. Note that this means
shifting of change numbers is not supported.
- The system checks whether the product keys exist. If they do not, the system ignores the
hazardous substance data for the product, that means it does not post it. Whether it posts
the IDoc depends on the value of the environment parameter
ALE_LOG_PRODUCT_NOT_EXIST:
- If you have set the environment parameter to E, the IDoc is not posted and has the
status Error.
- If you have not set the environment parameter or not set it to E, the IDoc is posted.
Activities
the implementation.
Short Text field.
8. Choose Activate.
______________________________________________________________
SAP AG 444
SAP System
______________________________________________________________
you wrote.
Example
Default code exists for the following methods:

- Send Own Data
- Receive Own Data
See also
Methods
Modify Hazardous Substance Data Before Distributing
Modify Hazardous Substance Data After Receiving
Send Own Data
Receive Own Data
6.2.17.4 Dangerous Goods Management
6.2.17.4.1 Customizing exchange between EH&S in ERP and SCM
Use
For some IMG activities it is possible to exchange the configuration between EH&S in ERP and
EH&S Services in SCM. Customizing transports or customizing comparison can be used for the
following activities:
- Dangerous Goods Master:
- Specify Processing Statuses
- Specify Validity Areas
- Specify Mode-of-Transport Categories
- Specify Collective Mode-of-Transport Categories
- Specify Dangerous Goods Regulations
- Specify Dangerous Goods Classes and Classification Codes
- Specify Not Dangerous Goods Full/Empty Transport
- Specify Transport Types
- Specify Hazard Identification Numbers
______________________________________________________________
SAP AG 445
SAP System
______________________________________________________________
- Specify Danger Labels

- Specify Packing Instruction Numbers
- Specify Packaging Codes
- Specify Profiles for User-Defined Dangerous Goods Texts
- Specify Identification Number Types
- Specify Labels
- Specify Water Pollution Classes
- Specify Combustible Liquid (VbF) Classes
- Specify Storage Hazard Classes
- Specify Stowage Categories
- Specify Regulatory Basis for Transport Restriction
- Dangerous Goods Checks and Dangerous Goods Documents:
- Specify Segregation Keys
- Specify Regulation-Dependent Mixed Loading Groups
- Specify Segregations
- Specify Mixed Loading Rules
- Specify Enterprise-Specific Mixed Loading Groups
- Manage User Exits
The following BC sets are available to provide example entries for EH&S Services:
/SCWM/EHS_DG Dangerous Goods Management
/SCWM/EHS_DG_BUS_CONTEXT Business Context
/SCWM/EHS_DG_CHECKS Dangerous Goods Checks
/SCWM/EHS_DG_CHECKS_DOCS Dangerous Goods Checks and Dangerous Goods
Documents
/SCWM/EHS_DG_CHECK_METHODS Dangerous Goods Check Methods
/SCWM/EHS_DG_CHECK_SCHEMAS Dangerous Goods Check Schemas
/SCWM/EHS_DG_CLASSES_CODES Dangerous Goods Classes and Classification
Codes
/SCWM/EHS_DG_COLL_TRANSPORT_CAT Collective Mode-of-Transport Categories
/SCWM/EHS_DG_DANGER_LABELS Danger Labels
/SCWM/EHS_DG_DOCUMENTS Dangerous Goods Documents
/SCWM/EHS_DG_FULL_EMPTY_TRANSP Not Dangerous Goods Full/Empty Transport
/SCWM/EHS_DG_HAZARD_ID_NUMBERS Hazard Identification Numbers
/SCWM/EHS_DG_IDENT_NO_TYPES Identification Number Types
/SCWM/EHS_DG_IND_CAT Indicator Category
/SCWM/EHS_DG_IND_PROFILE Indicator Profiles for Product Master
______________________________________________________________
SAP AG 446
SAP System
______________________________________________________________
/SCWM/EHS_DG_LANGUAGES Langs
/SCWM/EHS_DG_MASTER Dangerous Goods Master
/SCWM/EHS_DG_MIXED_LOAD_EXAMPLES Dangerous Goods Mixed Loading Checks
Examples
/SCWM/EHS_DG_MIXED_LOAD_EX_SCMBP Dangerous Goods Mixed Loading Checks
Examples Plus
/SCWM/EHS_DG_OUTPUT_COND Output Conditions and Formatting Methods
/SCWM/EHS_DG_PACK_CODES Packaging Codes
/SCWM/EHS_DG_PACK_INSTR Packing Instruction Numbers
/SCWM/EHS_DG_PLUS Dangerous Goods Management
/SCWM/EHS_DG_PROCESS_STATUS Processing Statuses
/SCWM/EHS_DG_PROFILE_TEXT Profiles for User-Defined Dangerous Goods Texts
/SCWM/EHS_DG_REGULATIONS Dangerous Goods Regulations
/SCWM/EHS_DG_REGULATIONS_PLUS Dangerous Goods Regulations
/SCWM/EHS_DG_REG_PROFILE Regulation Profile
/SCWM/EHS_DG_SETTINGS Common Settings
/SCWM/EHS_DG_STOWAGE_CAT Stowage Category
/SCWM/EHS_DG_TAB_PAGES Tab Pages in Dangerous Goods Master
/SCWM/EHS_DG_TRANSPORT_CAT Mode-of-Transport Categories
/SCWM/EHS_DG_TRANSPORT_TYPE Transport Types
/SCWM/EHS_DG_USAGE_PROFILES Usage Profiles for Dangerous Goods Check
Methods
/SCWM/EHS_DG_USER_EXITS User Exits
/SCWM/EHS_DG_VALIDITY_AREAS Validity Areas
6.2.17.4.2 Dangerous Goods Master
6.2.17.4.2.1 Specify Processing Statuses
Use
In this IMG activity, you specify the processing statuses for the dangerous goods master data.
Dangerous goods master data must be released explicitly to be used productively. For this
reason, setting of a processing status for dangerous goods master editing is supported.
______________________________________________________________
SAP AG 447
SAP System
______________________________________________________________
Dangerous goods master data is only used for checks or printing on documents if it has a
processing status that is marked as Released.
Example
You can set the following processing statuses:

- In Process
- Released
For this status, set the RelStat indicator.
Standard settings
Sample settings are supplied.
Recommendation
We recommend that you assign the status key in such a way that the first digit represents a
logical grouping. For example, "0" could represent all statuses that are "in process." You can
then use a generic search (search with "0*") in the dangerous goods master data screens to find
all master data records that are in various processing statuses.
Activities
1. Call the IMG activity.

2. Create your processing status entries and enter descriptions for them in the application
languages you use.
6.2.17.4.2.2 Specify Validity Areas
Use
In this IMG activity, you specify the validity areas.

Countries or countries and regions from the country table are assigned to the validity area as
jurisdictions.
Example
The validity area "ADR" is composed of ADR member states. All the country keys from these
member states must be assigned to this validity area.
Standard settings
Some examples are delivered in the standard system:

DE Germany
______________________________________________________________
SAP AG 448
SAP System
______________________________________________________________
US United States
REG_WORLD World
ADR ADR states
Activities

2. Analyze the jurisdictions of the respective dangerous goods regulation.
Group the jurisdictions to form a validity area.
3. Enter the respective validity area.
4. Select the validity area and choose Assign Validity Area/Country in the navigation.
5. Enter the countries that should be assigned to this validity area.
Further notes
- You cannot delete validity areas that have been used productively.
- Ensure that the validity areas used in dangerous goods management fulfill the following
conditions:
- A country can be included in a validity area that encompasses several countries
("ADR", for example).
- In addition, a validity area can exist that contains this country only. This kind of
validity area represents regulations specific to one country (listed goods regulations in
Germany, for example).
6.2.17.4.2.3 Specify Mode-of-Transport Categories
Use
In this IMG activity, you specify mode-of-transport categories.
Standard settings
Activities
In addition to the standard system settings that you cannot change, specify your own additional
mode-of-transport categories.
Example
11 Inland waterway tanker
______________________________________________________________
SAP AG 449
SAP System
______________________________________________________________
Further notes
The namespace for customers is 30 through 89.
6.2.17.4.2.4 Specify Collective Mode-of-Transport Categories
Use
Collective mode-of-transport categories allow you to group mode-of-transport categories.
Requirements
In the IMG activity Specify Collective Mode-of-Transport Categories, you have created collective
mode-of-transport categories and their descriptions for the base mode-of-transport category 07
(collective mode-of-transport categories).
We recommend that you select two-digit numbers between 90 and 99 for collective
mode-of-transport categories to distinguish them visually from mode-of-transport categories and
base mode-of-transport categories.
Standard settings
The standard system contains the collective mode-of-transport category All mode-of-transport
categories (99). You can edit the collective mode-of-transport category 99.
Activities

2. In the Collective MTC field, select a collective mode-of-transport category using the input
help.
3. Assign a mode-of-transport category to the collective mode-of-transport category in the
MTrCat field using the input help.
You cannot assign any other collective mode-of-transport categories to a collective
mode-of-transport category.
4. Repeat steps 2 and 3 to assign all required mode-of-transport categories to the collective
mode-of-transport category.
6.2.17.4.2.5 Specify Dangerous Goods Regulations
Use
______________________________________________________________
SAP AG 450
SAP System
______________________________________________________________
In this IMG activity, you specify the dangerous goods regulations by assigning a validity area
and mode-of-transport category to the respective dangerous goods regulation.
The data records in the dangerous goods master are based on the dangerous goods regulations.
This means that each time you create or change a dangerous goods master data record, you
must enter the regulation on which it is based.
Each regulation is identified uniquely by a language-dependent abbreviation, for example:
- "ADR" Accord europeen relativ au transport des marchandises dangereuses par route
- "GGVBinSch" dangerous goods regulation for inland waterways
Standard settings
Activities

2. Make the settings for the dangerous goods regulations for the mode-of-transport categories
and validity areas used.
Further notes
In order to assign a regulatory list to a dangerous goods regulation, choose Goto -> Details
and enter the appropriate regulatory list in the Regulatory List field.
6.2.17.4.2.6 Specify Dangerous Goods Classes and Classification Codes
Use
In this IMG activity, you specify the dangerous goods classes and classification codes for the
dangerous goods regulations.
Standard settings
Activities

2. Enter the legally required dangerous goods class-classification code combinations for the
dangerous goods regulations.
______________________________________________________________
SAP AG 451
SAP System
______________________________________________________________
Further notes
If you enter CBL as the dangerous goods class, the text Combustible Liquid is displayed
instead of the dangerous goods class.
6.2.17.4.2.7 Specify Not Dangerous Goods Full/Empty Transport
Use
In this IMG activity, you specify the input help for the following fields in the dangerous goods
master:
- Not Dangerous Goods Full Transport
- Not Dangerous Goods Empty Transport
This means that you can give a reason why the product is not regarded as dangerous goods in
the relevant dangerous goods regulation.
Standard settings
Activities
Specify a key along with a description of the reason, and specify the input help in which the
key appears by setting the full transport and empty transport indicators accordingly.
Further notes
The namespaces for customers are:

- 1 through 9
- L through Z with the exception of X
6.2.17.4.2.8 Specify Transport Types
Use
In this IMG activity, you specify the transport types in accordance with the corresponding
dangerous goods regulation.
______________________________________________________________
SAP AG 452
SAP System
______________________________________________________________
Standard settings
Activities

2. Edit the transport types permitted in accordance with the dangerous goods regulation.
6.2.17.4.2.9 Specify Hazard Identification Numbers
Use
In this IMG activity, you specify hazard identification numbers (kemler numbers) in accordance
with the corresponding dangerous goods regulation.
Standard settings
No default settings are supplied in the standard system.
Activities

2. Enter all hazard identification numbers together with their language-dependent descriptions.
6.2.17.4.2.10 Specify Danger Labels
Use
In this IMG activity, you specify the danger label numbers in accordance with the
corresponding dangerous goods regulation.
Standard settings
Activities

2. Edit the danger label numbers together with their language-dependent descriptions according
to the dangerous goods regulation.
______________________________________________________________
SAP AG 453
SAP System
______________________________________________________________
6.2.17.4.2.11 Specify Packing Instruction Numbers
Use
In this IMG activity, you specify the packing instruction number in accordance with the
corresponding dangerous goods regulation.
Standard settings
Activities

2. Edit the packing instruction numbers with language-dependent descriptions according to the
applicable dangerous goods regulations.
6.2.17.4.2.12 Specify Packaging Codes
Use
In this IMG activity, you specify the permitted entries for the packaging code.
Standard settings
Activities

2. Edit the permitted packaging codes with language-dependent descriptions according to the
applicable dangerous goods regulations.
6.2.17.4.2.13 Specify Profiles for User-Defined Dangerous Goods Texts
Use
In this IMG activity, you specify profiles for the dangerous goods user-defined text fields in the
dangerous goods master.
You can access the output conditions by means of the profiles.
______________________________________________________________
SAP AG 454
SAP System
______________________________________________________________
Further notes
If you do not process this IMG activity, you can still provide the dangerous goods user-defined
text fields in the dangerous goods master with output conditions, independently of the regulation,
in the IMG activity Specify Output Conditions.
6.2.17.4.2.14 Specify Identification Number Types
Use
In this IMG activity, you check the types of identification numbers.
Activities

2. Check whether the following types of identification numbers exist:
- ID (ID number)
- NA (NA number)
- UN (UN number)
6.2.17.4.2.15 Specify Labels
Use
In this IMG activity, you specify the labels for printing.

Up to 10 labels can be entered for one dangerous goods master data record.
The labels are stored as short texts.
Standard settings
Activities

2. Edit the language-dependent short descriptions for the labels.
______________________________________________________________
SAP AG 455
SAP System
______________________________________________________________
6.2.17.4.2.16 Specify Water Pollution Classes
Use
In this IMG activity, you specify the water pollution classes.

There are legal regulations for water-polluting substances. To specify exactly what water
pollution entails, substances are classified according to their potential for pollution.
The water pollution class must be output on several documents in dangerous goods management.
Standard settings
No settings are supplied with the standard system.
Activities

2. Edit the water pollution classes with their language-dependent descriptions.
6.2.17.4.2.17 Specify Combustible Liquid (VbF) Classes
Use
In this IMG activity, you specify the VbF classes.

The VbF class must be output on several documents in dangerous goods management.
Standard settings
Activities

2. Edit the VbF classes with language-dependent descriptions.
6.2.17.4.2.18 Specify Storage Hazard Classes
Use
In this IMG activity, you specify the storage hazard class.

The storage hazard class must be output on several documents in dangerous goods management.
______________________________________________________________
SAP AG 456
SAP System
______________________________________________________________
Standard settings
Activities

2. Edit the storage hazard classes with their language-dependent descriptions.
6.2.17.4.2.19 Specify Stowage Categories
Use
In this IMG activity, you specify the stowage category.
Activities
Specify the stowage categories that are used in the dangerous goods regulations IMDG Code
and 49 CFR.
6.2.17.4.2.20 Specify Regulatory Basis for Transport Restriction
Use
In this IMG activity, you specify the regulatory basis for transport restrictions.
The regulatory basis for the transport restriction is a reference to a paragraph, a section, or a
table in a dangerous goods regulation.
Standard settings
Activities
Enter the regulatory basis for transport restrictions with language-dependent descriptions.
Example
GGVSE, Annex 1, Table 1
______________________________________________________________
SAP AG 457
SAP System
______________________________________________________________
6.2.17.4.2.21 Activate Phrase Assignment
Use
In this IMG activity, you activate phrase assignment.
Activities
Set the indicator in order to activate the fields provided for assigning phrases so that phrase
sets can be assigned.
To execute the program, choose Execute.
Further notes
If you have not activated phrase assignment, you cannot change the phrase sets in phrase
set-attribute assignment or add new entries.
6.2.17.4.2.22 Create Standard Phrase Sets
Use
In this IMG activity you create standard phrase sets for all fields with phrases assigned in
Dangerous Goods Management. The following applies here:
- The newly generated phrase sets are automatically assigned to the fields with phrases
assigned.
- Phrases are not assigned during this generation.
- Existing assignments of phrase sets to fields in Dangerous Goods Management are not
overwritten by the system.
Activities
Execute this IMG activity after the IMG activity Activate Phrase Assignment.
Caution:
If you do not want to create a phrase set for a field with phrases assigned, you must then
delete this assignment manually in the phrase set-attribute assignment.
6.2.17.4.2.23 Specify Tab Pages in Dangerous Goods Master
Use
______________________________________________________________
SAP AG 458
SAP System
______________________________________________________________
In this IMG activity you specify the tab pages for the dangerous goods master.
Standard settings
Activities
To set up a new tab page, proceed as follows:

2. Enter an alphanumeric key for the tab page.
3. In the Seq. field, use the level of the number you enter to specify which position in
relation to the other tab pages the new tab page is to appear in.
4. Enter the program name to call the tab page.
5. Enter the number of the screen for list display.
6. Enter the number of the screen for detailed display.
7. Set the Visible indicator if the tab page is to be visible in the dangerous goods master.
8. Specify the title that should appear on the tab page in the dangerous goods master.
6.2.17.4.2.24 BAdI: Dangerous Goods Indicator Profile for Product Master
Use
With this BAdI you can define enhancements to determine the dangerous goods indicator profiles
for the product master that are executed at the following points:
- Filtering of order items and delivery items in accordance with the dangerous goods
indicator profile during route checks
- Filtering of delivery items in accordance with the dangerous goods indicator profile during
delivery note printing
Standard settings
The BAdI is active in the standard system. No default code is supplied, but only an active
implementation.
The BAdI is not filter-dependent and not intended for multiple use.
______________________________________________________________
SAP AG 459
SAP System
______________________________________________________________
Activities
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
Example
Methods
Read Dangerous Goods Indicator Profiles for Product
6.2.17.4.3 Dangerous Goods Checks and Dangerous Goods Documents
6.2.17.4.3.1 Common Settings
6.2.17.4.3.1.1 Assign Relevant Mode-of-Transport Categories to Means of

Transport
Use
In this IMG activity, you assign the relevant mode-of-transport category to means of transport.
______________________________________________________________
SAP AG 460
SAP System
______________________________________________________________
Activities
1. Check which means of transport are relevant for dangerous goods management.
2. Assign a mode-of-transport category to the means of transport. The mode-of-transport
category is used to classify means of transport in dangerous goods management.
Activities
You make the settings in Customizing for Advanced Planning and Optimization under
Maintain Means of Transport.
6.2.17.4.3.1.2 Specify Regulation Profile
Use
In this IMG activity, you define regulation profiles.

This enables you to specify, independently of the product, the dangerous goods regulations for
which the following additional dangerous goods regulations are to be used in delivery
processing:
- Excepted quantity
- Reportable quantity
- Exemption highly viscous
- Listed goods
Example
You can specify for a particular product that the regulation 'Excepted quantity' is only used for
the ADR regulation.
Activities
Create a profile and assign one or more regulations to this profile under Regulation/Profile
Assignment.
6.2.17.4.3.1.3 Specify Indicator Category
Use
In this IMG activity, you specify which regulation profiles should be available in the phrase
sets for the following indicators for additional dangerous goods regulations:
______________________________________________________________
SAP AG 461
SAP System
______________________________________________________________
- Excepted quantity
- Reportable quantity
- Listed goods
Activities
Assign regulation profiles for the phrase set to the indicators via Assignment Indicator
Category/Regulation Profile.
6.2.17.4.3.1.4 Specify Business Context
Use
In this IMG activity, you specify business contexts and assign them dangerous goods check
schemas.
You use the business context to specify in which context a dangerous goods check schema is
called. Depending on the business context, different or additional data can be read within the
read module of the dangerous goods check schema.
Example
DLVPR Delivery note printing
RGD Route checks for routing guide
6.2.17.4.3.1.5 Specify Indicator Profiles for Product Master
Use
In this IMG activity, you specify the dangerous goods indicator profiles for the product master.
You can assign exactly one indicator profile to each product master record. This assignment
enables you to specify whether the product is:
- Relevant for dangerous goods
- Relevant for dangerous goods and documents
- Relevant for dangerous goods and checks
- Relevant for dangerous goods, checks, and documents
______________________________________________________________
SAP AG 462
SAP System
______________________________________________________________
Standard settings
All relevant dangerous goods indicator profiles are delivered in standard Customizing.
Activities
Check the existing dangerous goods indicator profiles to ensure they are complete.
6.2.17.4.3.1.6 BAdI: Date Determination for DG Checks and Delivery Note

Printing
Use
With this BAdI you can define enhancements for date determination that are executed when
delivery notes are printed and in route checks for requests from the routing guide. With this
BAdI you can influence how date determination for determining dangerous goods master data
works.
Standard settings
The BAdI is not active in the standard system. If you activate the BAdI without modifying it,
the standard system behavior is not affected.
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 463
SAP System
______________________________________________________________

8. Choose Activate.
you wrote.
See also
Methods
Date Determination for Dangerous Goods Master Data
6.2.17.4.3.1.7 BAdI: Product exchange / multiple component explosion
Use
This Business Add-In (BAdI) is used in the EH&S Services (SCM-BAS-EHS) component. With
this BAdI you can enhance the functionality within check or printing routines. It is not always
the product that is specified on the item of a document that holds the dangerous goods
information but a component that is built into the product. The BAdI is called within the
dangerous goods check frame (/SEHS/DGCAPI_CHECK_FRAME) before the check methods for
dangerous goods checks are determined and within the printing of documents
(/SEHS/DGPAPI_PRINT_DATA_GET) for the output of dangerous goods data on documents.
Requirements
Create your own implementation and adapt the methods of the implementation to fulfill your
requirements.
Standard settings
The BAdI is active in the standard system. No default code is supplied.

The BAdI is not filter-dependent and not for multiple usage.
Activities
Example
This BAdI uses the interface /SEHS/IF_BADI_DG_PROD_EXCHANGE.
______________________________________________________________
SAP AG 464
SAP System
______________________________________________________________
6.2.17.4.3.2 Dangerous Goods Checks
6.2.17.4.3.2.1 Specify Dangerous Goods Check Methods
Use
Dangerous goods checks are realized in the form of function modules as user exits. In this
IMG activity, you assign the function modules and define a dangerous goods check method.
Standard settings
The following function modules are delivered in the standard system:

/SEHS/DGCHM_CHECK_DGSTATUS Checks the status of the dangerous goods master
(released)
/SEHS/DGCHM_CHECK_MAXQ_TU Checks the maximum permitted quantity per
transport unit
/SEHS/DGCHM_CHECK_PBI Checks whether Poisonous by inhalation
/SEHS/DGCHM_CHECK_TRALLOWED Checks if transport is permitted
There are sample entries for dangerous goods check methods for these function modules in
standard Customizing.
Activities

2. Define function modules as dangerous goods check methods and enter the
language-dependent descriptions in all application languages you use.
Only assign function modules whose interface corresponds to the interface for the function
modules in the function group /SEHS/DGCH.
3. Assign check method types to the function module as required.
In delivery documents, you can determine the following indicators using your own check
methods:
- Listed goods
- Reportable quantities
- Excepted quantity
The indicators are determined at runtime and output in the delivery document at header or item
level.
______________________________________________________________
SAP AG 465
SAP System
______________________________________________________________
Further notes
If you create your own function modules for dangerous goods check methods, you must retain
the interface used for the function modules delivered in the SAP standard system. To do this,
use one of the function modules named above as a template. These function modules are found
in the function group /SEHS/DGCH.
6.2.17.4.3.2.2 Specify Usage Profiles for Dangerous Goods Check Methods
Use
In this IMG activity, you specify the usage profiles for dangerous goods check methods.
Using this IMG activity you can set the check methods to run in accordance with the
mode-of-transport category, validity area, and role.
These context-dependent usage profiles improve performance considerably. For example, you can
restrict the check method "poisonous by inhalation" to the validity area United States, the
dangerous goods regulation CFR, and the role destination country. The system then just checks
in this context.
If you do not enter a usage profile for a check method, the check method for all countries and
dangerous goods regulations for the document is processed. This means that for each
product/country/mode-of-transport category combination in the document, the system attempts to
find a dangerous goods master record that can be checked with the check method.
A usage profile key is composed of the following elements:
- Dangerous goods check method
- Dangerous goods regulation
You must also specify which role the countries (and possibly regions) in the validity area are to
perform for the shipment during the check. The following roles are supported:
1 Departure country
2 Transit country
3 Destination country
4 Departure and transit country
5 Transit and destination country
6 Departure and destination country
7 Departure, transit, and destination country
During the dangerous goods checks, these countries are determined as follows:
- Departure country from the delivery location
- Transit country from the route or leg stages
- Destination country from the ship-to party
______________________________________________________________
SAP AG 466
SAP System
______________________________________________________________
The usage profile is passed to the check methods so that these can respond to it.
When you define usage profiles, you must take into account that the dangerous goods regulation
and validity area in the profile are used to check whether a check method should be run for a
dangerous goods master record. Because of this, you should always define the usage profile for
a check method taking into account the dangerous goods regulations you are using in the
dangerous goods master.
Note
For header check methods, the role in the usage profile is ignored. That means for header
check methods, the system only checks based on the dangerous goods regulations whether the
check method is executed that is determined in the document from the dangerous goods master
records.
Requirements
You have defined dangerous goods check methods in the IMG activity Specify Dangerous Goods
Check Methods.
You have defined validity areas in the IMG activity Specify Validity Areas.
Activities

2. Specify the usage profile by assigning a dangerous goods check method and a dangerous
goods regulation to the profile.
3. Assign a role to this usage profile.
This assignment is optional.
Example
The Permissibility of transport check method (function module

/SEHS/DGCHM_CHECK_TRALLOWED) must be carried out for each regulation mapped in the
dangerous goods master. You could specify the following usage profiles for this usage profile,
for example:
Dangerous Goods Regulation
ADR
RID
ADNR
IMDG
- The dangerous goods regulation that is defined by mode-of-transport category and validity
area in Customizing for Dangerous Goods Management is used in the dangerous goods
master. The above example contains the corresponding dangerous goods regulation for
dangerous goods master records on which the example is based.
______________________________________________________________
SAP AG 467
SAP System
______________________________________________________________
- If transport takes place on the mode-of-transport category Road, the products are checked
using the dangerous goods master record with the dangerous goods regulation ADR when
the check method is processed. If transport also takes places on mode-of-transport category
Rail, the products are also checked using the dangerous goods master record with the
dangerous goods regulation RID.
6.2.17.4.3.2.3 Specify Dangerous Goods Check Schemas
Use
In this IMG activity, you combine dangerous goods check methods into one dangerous goods
check schema and set up a response for each check schema and check method that influences
how the SD document is processed further.
Standard settings
Activities

2. Create a new check schema and enter descriptions in the required languages.
3. Select the required dangerous goods check schema.
4. Choose Assignment Check Schema/Check Methods in the navigation.
5. Enter a sequence number for the dangerous goods check method.
Note: The check methods are processed in the sequence specified.
6. Assign a response type to the respective check method. You can enter the following
response types:
Value Meaning
I Information
W Warning
E Error
A Termination of the dangerous goods checks for
the document
X No further dangerous goods checks for the
document item
If a check method for which an A response is set responds, the dangerous goods checks
for the document (SD document) currently being checked are terminated immediately. If a
check method for which an X response is set responds, no further dangerous goods checks
are run for the current document item.
For the response types X and A, the check result of the check is set automatically to E
(error) and the specified message is written to the check log as an error message.
______________________________________________________________
SAP AG 468
SAP System
______________________________________________________________
When processing the dangerous goods check methods for each document, an overall
response for each document of the dangerous goods check schema is determined from the
responses of the check methods that have responded. For this, E > W > I. The strictest
response type determines the overall response for the check schema.
7. Assign a message class and message number to the respective dangerous goods check
method.
The message set up is written to the check log for the dangerous goods checks. If you
replace the module for the check method with one of your own, you must assign it a
message class and message number.
6.2.17.4.3.2.4 BAdI: Determination of Dangerous Goods Check Schema
Use
This Business Add-In (BAdI) is used in the EH&S Services (SCM-BAS-EHS) component. With
this BAdI you can enhance the determination of a check schema depending on the business
context and product information. The BAdI is called within the dangerous goods check frame
(/SEHS/DGCAPI_CHECK_FRAME) before the check methods for dangerous goods checks are
determined.
Requirements
Create your own implementation and adapt the methods of the implementation to fulfill your
requirements.
Standard settings
The BAdI is active in the standard system. Default code is supplied.

The BAdI is not filter-dependent and not for multiple usage.
Activities
Example
This BAdI uses the interface /SEHS/IF_BADI_DG_CHK_SCHEM_DET.

______________________________________________________________
SAP AG 469
SAP System
______________________________________________________________
6.2.17.4.3.2.5 Specify Settings for Mixed Loading Checks
6.2.17.4.3.2.5.1 Specify Segregation Keys
Use
In this IMG activity, you specify segregation keys for the mixed loading checks. For this, the
regulations for road and rail transport use the danger label. The regulation for sea transport
(IMDG) and the US regulation CFR49 use the dangerous goods classes.
In specification management, you can assign segregation keys to UN-listed substances and real
substances.
In the master data for the Dangerous Goods Management component, you can assign products
to segregation keys.
In the SAP standard system, the danger label is used as the segregation key.
Standard settings
Sample settings are delivered in the standard system.
Activities
Specify a segregation key and a description of the segregation key for the dangerous goods
regulations.
Further notes
You can find more information in the documentation for the Dangerous Goods Management
component.
In the IMG activity Specify Danger Labels you can group together the danger labels specified
there using the segregation keys.
______________________________________________________________
SAP AG 470
SAP System
______________________________________________________________
6.2.17.4.3.2.5.2 Specify Responses
Use
In this IMG activity you define responses that are used in the segregation rules for segregation
keys and in the segregation rules for enterprise-specific mixed loading groups.
With the Mixed loading permitted indicator you specify that the response permits mixed loading.
The specified message is written to the dangerous goods check log.
Standard settings
Sample settings are shipped.
6.2.17.4.3.2.5.3 Specify Segregation Rules for Segregation Keys
Use
In this IMG activity, you specify segregation rules for the segregation keys. The segregation
rules are a regulation-dependent decision matrix in which you specify which combinations of
segregation keys are prohibited or permitted.
Requirements
You have processed the following IMG activities:

- Specify Segregation Keys
- Specify Responses
Activities
In accordance with the requirements of the individual dangerous goods regulations, specify a
response for combining two segregation keys.
______________________________________________________________
SAP AG 471
SAP System
______________________________________________________________
Standard settings
Sample settings are delivered in the standard system.
Further notes
Unspecified combinations of segregation keys are evaluated during mixed loading checks as if
mixed loading were permitted.
component.
6.2.17.4.3.2.5.4 Specify Regulation-Dependent Mixed Loading Groups
Use
In this IMG activity, you define regulation-dependent mixed loading groups.

Regulation-dependent mixed loading groups are specified in dangerous goods regulations.
Example
- Group 1: Acids
- 1052 Hydrogen fluoride, anhydrous
- 1182 Ethyl chloroformate
- 1183 Ethyldichlorosilane
- ....
- Foodstuffs
In specification management, you can assign regulation-dependent mixed loading groups to
UN-listed substances or real substances.
In the master data for the Dangerous Goods Management component, you can assign
regulation-dependent mixed loading groups to products.
______________________________________________________________
SAP AG 472
SAP System
______________________________________________________________
Activities
Enter mixed loading groups along with their descriptions for the dangerous goods regulations.
Example
Regulation R-D ML grp Description

IMDG 1 Acids
IMDG 2 Ammonium Compounds
IMDG 3 Bromates
Further notes
component.
6.2.17.4.3.2.5.5 Specify Segregations
Use
In this IMG activity, you specify segregations. You need these in order to be able to specify
the physical separation of regulation-dependent mixed loading groups.
Activities
Enter segregations, along with a description, for the dangerous goods regulations.
Example
ADR 1 separated from
Further notes
Segregations cannot necessarily be interchanged (commutative). Whereas, for example, "A
______________________________________________________________
SAP AG 473
SAP System
______________________________________________________________
separated from B" can be equated with "B separated from A", "A not above B" has a different
meaning from "B not above A." The segregation "not above" is therefore not commutative.
When segregation is not commutative, set the Not commutative indicator.
6.2.17.4.3.2.5.6 Specify Mixed Loading Rules
Use
In this IMG activity, you specify mixed loading rules for regulation-dependent mixed loading
groups.
You can assign the mixed loading rules to UN-listed substances and real substances in
specification management.
In the master data for the Dangerous Goods Management component, you can assign the mixed
loading rule to products.
Requirements
You have processed the following IMG activities.

- Specify Regulation-Dependent Mixed Loading Groups
- Specify Segregations
Activities
1. Specify the mixed loading rules for the individual dangerous goods regulations as a
combination of the regulation-dependent mixed loading group and segregation.
2. Specify the response type that is to occur within the dangerous goods check method 'mixed
loading check.'
3. Specify a description for the mixed loading rule.
Example
Regulation IMDG IMDG
MLoad rule 1 2
R-D ML grp 1 (Acids) 50 (Food)
Segregation 2 (separated from) 2
RespType E E
Description separated from acids separated from
food
______________________________________________________________
SAP AG 474
SAP System
______________________________________________________________
Further notes
component.
6.2.17.4.3.2.5.7 Specify Enterprise-Specific Mixed Loading Groups
Use
In this IMG activity, you specify enterprise-specific mixed loading groups.

You can use enterprise-specific mixed loading groups to represent enterprise-specific special
cases and stricter regulations.
Enterprise-specific mixed loading groups can be any groupings or individual substances.
Enterprise-specific mixed loading groups are not regulation-dependent.
In specification management, you can assign real substances to enterprise-specific mixed loading
groups.
In the master data for the Dangerous Goods Management component, you can assign products
to enterprise-specific mixed loading groups.
Activities
Specify enterprise-specific mixed loading groups and the corresponding descriptions.
Example
E-S Ml grp: 1; Description: Pyrophoric metal powder

E-S Ml grp: 2; Description: Hydrogen peroxide 70
______________________________________________________________
SAP AG 475
SAP System
______________________________________________________________
6.2.17.4.3.2.5.8 Specify Segregation Rules for Enterprise-Specific Mixed

Loading Groups
Use
In this IMG activity, you specify the segregation rules for enterprise-specific mixed loading
groups.
Requirements
You have processed the following IMG activities.

- Specify Responses
- Specify Enterprise-Specific Mixed Loading Groups
Activities
For the dangerous goods regulations, specify the corresponding response for combinations of two
enterprise-specific mixed loading groups.
Example
Regulation E-S ML grp E-S ML grp Response

ADR 3 7 1
Further notes
Enterprise-specific mixed loading groups are not specified to be dependent on dangerous goods
regulations.
Segregation rules are, however, specified to be regulation-dependent. This enables you also to
specify different responses for combining two enterprise-specific mixed loading groups when the
mode-of-transport categories are different.
______________________________________________________________
SAP AG 476
SAP System
______________________________________________________________
6.2.17.4.3.3 Dangerous Goods Documents
6.2.17.4.3.3.1 Manage User Exits
Use
In this IMG activity, you manage the user exits that you can use to print out dangerous goods
standard texts on dangerous goods documents and for EDI.
Example
In user exit management, the user exit category PHR_TEXT exists with the following function
modules that are relevant for the dangerous goods documents:
- DG50_PRICOND_ADNR10011_STDT
- DG50_PRICOND_ADNRDECLA_STDT
- DG50_PRICOND_ADR10011_STDT
- DG50_PRICOND_ADRDECLA_STDT
- DG50_PRICOND_EXCPQUAN_STDT
- DG50_PRICOND_SHIPDECLA_STDT
When you create a new function module, enter the name of the function module directly in the
relevant field. Note in this case that you are creating a new function module in the customer
namespace and not in the standard system. In the relevant function group, you must create a
top include that contains the following statement:
type-pools tr, esp1, esp7, esp11, esp12.
Standard settings
A sample user exit is supplied.
Recommendation
If you want to define your own function modules, call the documentation for the corresponding
reference function module (SE37). Write the new function module analogous to the reference
module and its interface.
Activities

2. Check whether the user exit category PHR_TXT is created.
______________________________________________________________
SAP AG 477
SAP System
______________________________________________________________
Further notes
Using the phrase sets, you specify whether the dangerous goods standard texts are output at
header or item level.
You enter the corresponding user exit of the category PHR_TXT in the phrase header under
User Exit Name.
6.2.17.4.3.3.2 Specify Output Conditions and Formatting Methods
Use
In this IMG activity, you specify the output conditions and formatting methods for the data in
the dangerous goods documents.
The output conditions and formatting methods apply to the output of texts in connection with
fields in the dangerous goods master as well as other fields that are required for print output.
Output conditions and formatting methods should be developed as function modules.
Standard settings
Activities

3. Choose the field name for the required field using the input help.
4. Choose Enter. The short description for the field name is displayed.
5. Choose the required function module or enter the required function module.
Further notes
Note that the number of function modules in the system influences performance when printing
dangerous goods documents.
6.2.17.4.3.3.3 Specify Languages
Use
In this IMG activity, you assign the primary languages, that is the valid dangerous goods
languages, to the dangerous goods regulations.
______________________________________________________________
SAP AG 478
SAP System
______________________________________________________________
On the dangerous goods documents, texts are printed in the languages for which the Prt Lang.
indicator is set.
6.2.17.4.3.3.4 BAdI: Enhancements for Delivery Note Printing
Use
With this BAdI you can define enhancements for filtering and sorting languages for the output
of dangerous goods data in delivery note printing. For the output of dangerous goods data,
there are primary languages that are output according to a dangerous goods regulation, and the
language of the departure country and the language for delivery note printing.
With this BAdI you can influence the sort sequence of the languages in which the dangerous
goods data is to be output for a regulation during delivery note printing.
Standard settings
The BAdI is not active in the standard system. If you activate the BAdI without modifying it,
the standard system behavior is not affected.
The implementation class is /SEHS/CL_DEF_IM_DG_BADI_04.
Activities
the implementation.
Short Text field.
______________________________________________________________
SAP AG 479
SAP System
______________________________________________________________
8. Choose Activate.
you wrote.
See also
Default code is implemented for the following methods.

Filtering/Sorting Print Languages for DG Regulations
Specify Sequence of DG Regulations in Delivery Note
6.2.17.4.4 Interface: Distribution
6.2.17.4.4.1 BAdI: Enhancement for Mapping of Dangerous Goods Data
Use
With this BAdI you can define enhancements that are executed at the following points:
- When dangerous goods data is posted by the recipient
- When converting dangerous goods data from an R/3 system to an SCM system
- When checking prerequisites
With this BAdI you can also transfer data via Application Link Enabling (ALE) or build in
customer-specific data filters. The default implementation is /SEHS/DG_BADI_03_DF.
Standard settings
The BAdI is active in the standard system and executes default code. If you activate it and do
not implement your own method, the standard system behavior is affected.
The standard implementation executes the following process when dangerous goods data is
posted and should always be called when data is to be transferred from an R/3 system to an
SCM system.
- Record numbers are replaced by GUIDs.
- If change numbers are used in the data, these are replaced by system-specific change
numbers that are searched for in the target system and created if necessary. Transferring
change numbers is not necessary. Moving change numbers is not supported.
- The product ID is checked. If it does not exist, the dangerous goods data is not posted.
An error message is issued if the environment parameter
ALE_LOG_PRODUCT_NOT_EXIST is set to W or E.
______________________________________________________________
SAP AG 480
SAP System
______________________________________________________________
Activities
the implementation.
Short Text field.
8. Choose Activate.
you wrote.
Example
Methods
Conversion of Dangerous Goods Data
Modify Dangerous Goods Data After Receiving
Consistency Check
Collect Text Pattern Phrases for Conversion
Replace Text Pattern Phrase with New Text Pattern Phrase
______________________________________________________________
SAP AG 481
SAP System
______________________________________________________________
Use
In this IMG activity, you can create activity groups. You can also create authorization profiles
using the Profile Generator
Activities
To assign an authorization profile to a user, do the following:

Detailed information
For details about the procedure, see Transaction documentation.
See also the general documentation on the Profile Generator in the SAP Library. Choose:
Basis Components -> Computing Center Management System -> Users and Roles or in the
Implementation Guide (IMG), choose: Basis Components -> System Administration -> Users
and Authorizations -> Maintain Authorizations and Profiles using Profile Generator.
Note:
Choose "Edit -> Add authorization -> From profile" in step 4. to include the data of an
6.2.18 Basic Settings for Supply Chain Analytics Applications
6.2.18.1 Define Mapping for Business Objects
Use
In this IMG activity you define the assignment of business objects to analysis objects, to be
able to receive and further process business object semantics with different structures. To do
this, specify the classes that translate the business object structures into the corresponding
internal structures of analysis objects. In this way, SAP Supply Chain Management (SAP SCM)
can receive semantics and business objects with different structures and assign these to an
analysis object.
______________________________________________________________
SAP AG 482
SAP System
______________________________________________________________
Standard settings
In the default Customizing settings delivered by SAP, the assignment of analysis objects is
defined; the system uses this assignment for the following default analysis applications:
- Inbound delivery monitor
- Shortage analysis
- Supplier delivery performance rating
- Service fill monitor and service loss analysis
Activities
If you only want to work with the analysis applications delivered by SAP, we recommend
that you do not change the default Customizing.
If you want to work with the analysis applications delivered by SAP, as well as with your own
analysis applications that require business objects defined by you, you can define the assignment
of these business objects to analysis objects here, as follows:
1. Specify the structure of business object data, which the system receives from the server
proxies. The structure must be an existing, non-generic ABAP Dictionary structure.
2. Assign to this structure a mapping class for conversion into the internal analysis object
structure.
The class that you specify here must be an enhancement of the class CL_SCR_BO.
To help you search for the desired structures, you can use the search criteria of the input help.
6.2.18.2 Define Error Queue for Business Objects
Use
In this IMG activity, you can specify the message types for a business object that have to
occur for the system to save the business object and the corresponding messages in the error
queue. You can also specify the length of time that the business objects and messages remain in
the error queue.
______________________________________________________________
SAP AG 483
SAP System
______________________________________________________________
Activities
1. Choose one of the following options:

- The system only saves the business object and the corresponding messages in the error
queue if information messages or warning messages occur.
- The system saves the business object and the corresponding messages in the error
queue if information messages, warning messages, or error messages occur.
queue if error messages or warning messages occur.
queue if error messages occur.
2. Specify the length of time in days that the business object and messages are to remain in
the error queue.
6.2.18.3 Define Analysis Objects
Use
In this IMG activity you define the factory classes that manage the instances of the analysis
objects.
A factory manages the references to analysis objects. For example, a factory manages all
references to instances of the analysis object Purchase Order, in other words, the factory
manages all the purchase orders received as references to purchase order analysis objects.
Standard settings
In the Customizing settings delivered by SAP, factory classes are defined for the analysis
objects that the system uses for the analysis applications delivered by SAP.
Activities
If you only want to work with the analysis objects delivered by SAP, we recommend that
you do not change the default Customizing.
If you want to work with the analysis objects delivered by SAP, as well as with your own
analysis objects, then you have to create the following factory classes for the latter:
1. Provide the identification of an analysis object factory, as well as a description of the
analysis object.
______________________________________________________________
SAP AG 484
SAP System
______________________________________________________________
For the analysis object Outbound Delivery, for example, the identification OD (for the
english terms Outbound Delivery) is specified for the factory ID.
2. Assign a factory class to the analysis object factory.
The class that you specify here must be an enhancement of the class /SCMB/CL_SCR (for
example, /SCMB/CL_SCR_OD for outbound delivery).
To help you search for the desired factory classes, you can use the search criteria of the
input help.
6.2.18.4 Define Analysis Applications and Processing Sequence
Use
In this IMG activity you specify all the analysis applications with which you want to work, as
well as their processing sequence.
Standard settings
In the Customizing settings delivered by SAP, the following analysis applications and their
processing sequences are specified:
- Inbound delivery monitor
To be able to use the inbound delivery monitor, you must have implemented SAP
Advanced Planning and Optimization (SAP APO) and SAP Extended Warehouse
Management (SAP EWM).
- Shortage analysis
To be able use the shortage analysis, you must have implemented SAP APO.
- Supplier Delivery Performance Rating
To be able to use the supplier delivery performance rating, you must have implemented
SAP Supply Network Collaboration (SAP SNC).
- Service fill monitor and service loss analysis
To be able to use the service fill monitor and the service loss analysis, you must have
implemented SAP APO.
For more informationen about these applications, see the SAP Library for SAP Supply Chain
Management under SAP Advanced Planning and Optimization (SAP APO) -> Service
Parts Planning (SPP) -> Analysis, Monitoring and Reporting for Service Parts Planning.
Activities
If you only want to work with the analysis applications delivered by SAP, we recommend
that you do not change the default Customizing.
If there are specific applications delivered by SAP that you do not want work with, you can
______________________________________________________________
SAP AG 485
SAP System
______________________________________________________________
change the default values in the processing sequence fields for these applications, to zero. Then
the system does not consider those particular applications.
If you want to work with the analysis applications delivered by SAP, as with your own analysis
applications, you can specify these and their desired processing sequences as follows:
1. Specify the identification of the analysis application.
2. Provide the identification of an analysis object factory, which you have defined in the IMG
activity Define Analysis Objects.
3. Provice a description of the analysis application.
4. Specify the class name of the analysis application.
The class that you specify here must be an enhancement of the class
/SCMB/CL_SCR_AM.
To help you search for the desired class, you can use the search criteria of the input help.
5. For each analysis application, define its processing sequence, which is broken down into
the following steps:
a) Preprocessing of the document update
b) Document update
c) Postprocessing of the document update
d) Preprocessing of the analysis
e) Analysis
f) Postprocessing of the analysis
The system carries out steps 5a to 5c in real time. It calls the steps 5d to 5f periodically.
By specifying these call sequences, you can consider the dependencies of the individual
analysis applications.
The processing sequence of the analysis applications delivered by SAP is defined in steps
of ten. In this way, you can define your own applications so that they are executed in
between the default analysis applications.
6.2.18.5 Define Application Log for Analysis Tools
Use
In this IMG activity, you specify which of the messages that occur in conjunction with the
supply chain analysis are copied into the application log by the system.
______________________________________________________________
SAP AG 486
SAP System
______________________________________________________________
Activities
In the Detail Level field, choose the message types that the system is to copy into the
application log (transaction SLG1).
6.2.18.6 Create Customer-Defined Analytic Applications
Use
In addition to the analysis applications delivered by us, such as the inbound delivery monitor
and supplier delivery performance rating, you can also work with your own analysis
applications. You can create an analysis application that compares invoices with the
corresponding sales orders, for example.
Requirements
If, for your analysis application, you need document types, such as invoices, that the system
does not use in the analysis applications delivered by us, you must have created these document
types yourself. For more information see Create Customer-Defined Document Types.
Activities
To create you own analysis application, proceed as follows:

1. Under Define Analysis Applications and Processing Sequence create an entry for the new
analysis application.
2. Implement the analysis application. For this, the superclass /SCMB/CL_SCR_AM and
methods are available, which correspond to the individual phases of the analysis.
Immediately after a document reaches the framework using the method
/SCM/SCR_CL=>DOC_UPDATE, the system calls the following method:
- BEFORE_UPDATE
- UPDATE
- AFTER_UPDATE
The method /SCMB/CL_SCR=>SCHEDULE_ANALYSIS calls the following methods to
carry out time-intensive activities.
- BEFORE_ANALYSIS
- ANALYSIS
- AFTER_ANALYSIS
In this method you can define that the system writes analysis data to extractor tables,
from which it is replicated to a Business Intelligence system where it can be edited
______________________________________________________________
SAP AG 487
SAP System
______________________________________________________________
further.
You must schedule the method SCHEDULE_ANALYSIS to be called. This can be done
using the planning service manager (PSM), for example.
6.2.18.7 Create Customer-Defined Document Types
Use
In addition to the analysis applications delivered by us, you can also work with your own
Customer-Defined Analysis Applications. If, for your analysis application, you need document
types, such as invoices, that the system does not use in the analysis applications delivered by
us, you must have created these document types yourself.
Activities
To create a document type, proceed as follows:

1. Create a new ABAP dictionary structure or use an existing structure.
The data structure must be the data structure that the system is to transfer from a server
proxy or from APO Core Interface (APO-CIF).
Restrictions:
The structure that you create in the ABAP dictionary must not be generic.
2. Specify the structure you created in step 1 in the IMG activity Define Mapping for
Business Objects.
For more information see the Implementation Guide (IMG) for SCM Basis under Supply
Chain Analysis Tools -> Framework Settings.
3. You call the method DOC_UPDATE using the structure that you defined in step 1 as the
actual parameter. The method DOC_UPDATE is the central entry method for processing
new data in real time with different analysis tools. The framework calls the instance
method CONVERT_TO_AO of the corresponding mapping class that converts the data into
the internal structure (for more information about this method, see step 5).The system then
transfers the data to the desired analysis tool for further processing.
4. Specify the new document type that you want to create in the IMG activity Define
Analysis Objects. For more information see the IMG for SCM Basis under Supply Chain
Analysis tools -> Framework Settings.
5. Implement the business object class that you specified in step 2 in the IMG activity Define
Mapping for Business Objects in the Display of BO on AO field for the Business
Object Structure that you created in step 1. For this the superclass /SCMB/CL_SCR_BO
and the following method are available:
- INITIALIZE_FACTORIES
______________________________________________________________
SAP AG 488
SAP System
______________________________________________________________
In this method you initialize the factory. For this enter the ID that you specified in
step 4 in the IMG activity Define Analysis Object in the Factory field. The
system recognizes the document type according to this ID.
- CONVERT_TO_AO
In this method you define the assignment of a business object to an analysis object
structure. Here you can use the factory class that you specified in step 4 in the IMG
activity Define Analysis Objects in the Factory Class Name of Analysis Objects
field for managing object references.
- CREATE_EQ
In this method you initialize the error queue, in which the system saves all documents
that it cannot process.
- GET_BO_INFO_EXTID
In this method specify the ID in the source code, that you entered in step 4 in the
IMG activity Define Analysis Objects in the Factory field. In this way the system
can return the ID, based on which it recognizes the document type.
6. Implement the factory class that you specified in step 4 in the IMG activity Define
Analysis Objects in the Factory Class Name of Analysis Objects field.
- The class /SCMB/CL_SCR_AF is available as a superclass.
- So that the system can identify the correct factory for each document type, in the
constructor transfer the ID of the document type to the superclass.
- The method CREATE_EMPTY_AO is available to create instances for analysis objects.
You can manage the references of the analysis objects using further methods.
Example
1. You define the ABAP dictionary structure ZMY_BO_STR and fill it with the data that is
to be transferred to the framework.
2. In the IMG activity Define Mapping for Business Objects create the following entry:
- In the Structure of Business Object field enter the structure ZMY_BO_STR.
- In the Display of BO on AO field enter the class ZCL_MY_BO_STR. This class
converts the structure ZMY_BO_STR into an internal presentation of the data. You
need this internal presentation of data to edit the data in your analysis application.
- Set the Active indicator.
3. To transfer data to the framework, call the method /SCMB/CL_SCR=>DOC_UPDATE
and transfer the data, that is to be processed, as actual parameter. For this enter the
following code:
DATA. Z_DATA TYPEZMY_BO_STR.
CALL METHOD /SCMB/CL_SCR=>DOC_UPDATE
EXPORTING
IS_BUSINESS_OBJECT = Z_DATA
* IV_AO_HEAD_CTYPE = 'M' // DELETION INDICATOR
* IMPORTING
* ET_RETURN =
______________________________________________________________
SAP AG 489
SAP System
______________________________________________________________
4. In the IMG activity Define Analysis Objects create the following entry:
- In the Factory field enter MY.
- In the Description of Analysis Object field enter the description for the new
document type (Invoice, for example)
- In the Factory Class Name of Analysis Object enter the class ZCL_SCR_AF_MY.
- Set the indicator Active.
5. To implement the mapping class, proceed as follows:
Note:
The superclass of the mapping class must be the class /SCMB/CL_SCR_BO.
- Define the method INITIALIZE_FACTORIES as follows:
DATA:
LO_AF_MY TYPE REF TO ZCL_SCR_AF_MY, // FACTORY
LO_AO_MY TYPE REF TO ZCL_SCR_AO_MY. //ANALYT. OBJ.
LO_AF_MY ?= /SCMB/CL_SCR=>GET_AF (
IV_AF_INFO_EXTID = 'MY'
IV_CREATE_WHEN_NOT_EXISTS = 'X' ).
LO_AO_MY ?= LO_AF_MY->CREATE_EMPTY_AO ( ).
LO_AF_MY->SET_AO_TAB ( IO_AO = LO_AO_MY_BO_TYPE ).
- In the method CONVERT_TO_AO enter the factory class ZCL_SCR_AF_MY, in
order manage object references.
- In the method CREATE_EQ initialize an error queue
- Define the method GET_BO_INFO_EXTID as follows:
METHOD GET_BO_INFO_EXTID.
RV_BO_INFO_EXTID = 'MY'.
ENDMETHOD.
6. Implement the factory class ZCL_SCR_AF_MY.
6.2.18.8 Enterprise Services
6.2.18.8.1.1 BAdI for Delivery Information
Use
This Business Add-In (BAdI) is used in the SCM-BAS-SCR component. You can use this BAdI
DeliveryInformationMessage_IN that is part of the process component Supply Chain Analytic
Tools.
______________________________________________________________
SAP AG 490
SAP System
______________________________________________________________
Note:
- The BAdI has two methods: one for inbound deliveries and one for outbound
deliveries.
- There are no separate message interfaces for the actions create, change, and cancel,
since the service operation that processes this message type contains the data type
ActionCode, which contains the information about the action.
Standard settings
In the standard system, there is no acitvated BAdI implementation.

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_SCR_BIF_MSG_DE_IN interface. For more

sdn.sap.com -> Enterprise SOA -> ES Workplace -> Browse service definition ->
6.2.18.8.1.2 BAdI for Information Messages About Sales Orders
Use
to change or extend the data transferred through the following message interface that are part of
the process component Supply Chain Analytic Tools:
- SalesOrderCancelledInformationMessage_IN
______________________________________________________________
SAP AG 491
SAP System
______________________________________________________________
- SalesOrderChangedInformationMessage_IN
- SalesOrderCreatedInformationMessage_IN
Standard settings

Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_SCR_BIF_MSG_SO_IN interface. For more

6.2.18.8.1.3 BAdI for Information Messages About Purchase Orders
Use
to change or extend the data transferred through the following message interface that are part of
the process component Supply Chain Analytic Tools:
- PurchaseOrderCancelledInformationMessage_IN
- PurchaseOrderChangedInformationMessage_IN
- PurchaseOrderCreatedInformationMessage_IN
Standard settings

______________________________________________________________
SAP AG 492
SAP System
______________________________________________________________
Activities
See also:
This BAdI definition uses the /SCMB/IF_EX_SCR_BIF_MSG_PO_IN interface. For more

6.2.18.8.1.4 BAdI for Notifications about Delivery Schedules
Use
DeliverySchedule_Notification_IN that is part of the process component Supply Chain Analytic
Tools.
Note:
There are no separate message interfaces for the actions create, change, and cancel,
since the service operation that processes this message type contains the data type
ActionCode, which contains the information about the action.
Standard settings

Activities
______________________________________________________________
SAP AG 493
SAP System
______________________________________________________________
See also:
This BAdI definition uses the /SCMB/IF_EX_SCR_BIF_MSG_DS_IN interface. For more

6.2.19 Routing Guide
6.2.19.1 General Settings for Route Determination
Use
In this IMG activity, you make the general settings for the routing guide, for example:
- Select a cost profile
If the routing guide does not find a cost profile when calculating the transportation and
penalty costs, it uses this default cost profile.
- Activate/deactivate the routing guide
- Activate/deactivate realtime distribution
6.2.19.2 Define Request Types for Routing Guide
Use
In this IMG activity, you define request types for the routing guide.
______________________________________________________________
SAP AG 494
SAP System
______________________________________________________________
6.2.19.3 Define Modes of Transport for Foreign Trade
Use
In this IMG activity, you define modes of transport for foreign trade. The mode of transport is
a customs term for the type of transport used to transport the goods across a border, for
example, rail, road, or air.
The system uses the route to determine the mode of transport for foreign trade. For this, you
must specify the relevant mode of transport for foreign trade for the last stop in a country.
This applies to each leg of the route.
Note:
Modes of transport for foreign trade are supported for export only.
Activities
1. Define the modes of transport that are relevant to you.

For each country, specify the one-character alphanumeric key and the description.
2. Assign the modes of transport to your routes. To do this, specify the required mode of
transport in the route definition for each stop in each leg of a route. Because route
determination does not take optional stops into account, for correct calculation of the mode
of transport we recommend that you flag the last stop in a country in each case as
mandatory.
6.2.20 Cross-System and Cross-Partner Document Flow
6.2.20.1 Define Document Categories for Document Flow
Use
The document categories are the technical representation of documents or document items.
Assign a role category to the document categories in Customizing for the Object Relationship
Service.
Assign a DDIC structure to each document category that contains all the characteristics or
attributes supported by this document category. The system generates the database table for
storing the characteristics belonging to this document category from this definition.
In Customizing for the Object Relationship Service, define for each document category the form
______________________________________________________________
SAP AG 495
SAP System
______________________________________________________________
in which it is managed in the system (business repository type or persistence category). Only
the type 'BC - Instances of Business Classes (ABAP Objects)' is used in cross-system and
cross-partner document flow.
6.2.20.2 Maintain Object Link Model
Use
Definition of Role Categories
The role categories (for example, predecessor, successor, offer, order) form the nodes of a link.
The link categories are defined between these role categories. A role category can group
multiple document categories and a document category can be used in multiple role categories.
The role category determines the semantic of an object in a link.
Definition of Link Categories
The link categories describe possible links between the defined role categories. The link
category defines the semantic of the link between two documents (or roles). You specify for
each link category the table in which these links are stored. Use a table from cross-system and
cross-partner document flow. Split the management of the links between various tables to
improve performance. By doing this you reduce the number of entries per table. Only one table
is used for each link category, but multiple link categories can be stored in the same table.
You can use only one link category to connect two role categories. Include the same object
type in multiple role categories to connect the same documents using different links.
Link Attributes, Additional Data
You can assign attributes or additional data to each link category. The additional data must be
managed by a persistent class. Assign at least the network ID link attribute to the link category.
This link attribute manages the assignment of an individual link to a related network.
You can optionally update the additional data belonging to a link. You cannot update additional
data for a link that is not assigned to the relevent link category. When you delete the link the
additional data is also deleted.
______________________________________________________________
SAP AG 496
SAP System
______________________________________________________________
6.2.20.3 Define Maximum Chains for Document Flow
Use
When querying and evaluating the document flow network, you can limit the result using a
maximum chain. The maximum chain is a section from the object link model. It is identified
by a description and contains many link categories with predecessor and successor document
categories. Only links that lie within the maximum chain (or whose link category is contained
within the maximum chain) are returned by cross-system and cross-partner document flow,
following a corresponding query or evaluation.
The links that are included in the maximum chain do not contain directions for an evaluation,
that is, a certain area within the network is evaluated, rather than links with a particular
direction. The system always takes into account all links within the maximum chain, irrespective
of the document (within the maximum chain) with which you start the query.
The connection between one link and one or more maximum chains is not saved in the
database. Instead, it is redetermined for each query or evaluation. This means that you can
redefine the maximum chains at any time so long as this does not restrict the functions or
applications. In cross-system and cross-partner document flow you cannot, however, prevent this
change to a maximum chain.
Note that the link categories belonging to a maximum chain must be related.
6.2.21 Enterprise Services
6.2.21.1 Supply and Demand Matching
6.2.21.1.1 Supply Planning Exception
6.2.21.1.1.1 BAdI for Supply Plan SCM Exceptions By Elements Query
Use
This Business Add-in (BAdI) is used in the Alert Monitor (SCM-BAS-AMO) component. You
______________________________________________________________
SAP AG 497
SAP System
______________________________________________________________
can use this BAdI to change or extend the data transferred through the message interface
SupplyPlanningExceptionSCMByElementsQueryResponse_In.
Standard settings

Activities
See also
This BAdI definition uses the /SCMB/IF_EX_SE_SPP_EXSCM01QR interface. For more

6.2.21.2 Enterprise Services for Master Data
Use
You can find Customizing and Business Add-Ins (BAdIs) for enterprise services for master data
in SCM Basis Customizing, by choosing Master Data -> Enterprise Services.
6.2.21.3 Supply Chain Analytics Applications
Use
You can find Business Add-Ins (BAdIs) for enterprise services for supply chain analytics
applications in SCM Basis Customizing, by choosing Basic Settings for Supply Chain Analytics
______________________________________________________________
SAP AG 498
SAP System
______________________________________________________________
Applications -> Enterprise Services.
______________________________________________________________
SAP AG 499
SAP Transportation Management
______________________________________________________________
Copyright
Copyright(c) 2012 SAP AG. All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form
or by any means or translated into another language, without the prior consent of
SAP AG. The information contained in this document is subject to change without
notice.
SAP is a registered trademark of SAP AG.
All other products which are mentioned in this documentation are registered or not
registered trademarks of their respective companies.
______________________________________________________________
6 SAP Transportation Management 1

6.1 Transportation Management 1
6.1.1 Master Data 2
6.1.1.1.1 Define Equipment Groups and Equipment Types 4
6.1.1.1.2 Define Number Range Intervals for One-time Locations 5
6.1.1.2 Organizational Management 6
6.1.1.2.1 Organizational Model 6
6.1.1.2.1.1 Create Organizational Model 6
6.1.1.2.1.2 Change Organizational Model 6
6.1.1.2.1.3 Create and Merge Organizational Hierarchy 7
6.1.1.3 Transportation Network 7
6.1.1.3.1 Location 7
6.1.1.3.1.2 Configuration for Alternative Location Identifiers 8
6.1.1.3.2 Transportation Lane 9
6.1.1.3.2.2 Define Transportation Mode 10
6.1.1.3.3 General Settings for Transportation Network Determination 10
6.1.1.4 Resources 12
6.1.1.4.1 Define Means of Transport 12
6.1.1.4.6 Maintain Registration Number Patterns 14
6.1.1.4.7 Specify Resource Template Types 15
6.1.1.4.8 Specify Categories of Alternative Names 15
6.1.1.4.9 Maintain Settings for Qualifications 16
6.1.1.4.10 Maintain Settings for Grouping Attributes 16
6.1.1.4.11 Maintain Settings for Attached Equipment 17
6.1.1.4.12 Maintain Settings for Aggregated Capacity Requirements 17
6.1.1.4.14 Assign Standard Equipment Type 18
6.1.1.5 Agreements 19
6.1.1.5.1 Define Freight Agreement Types 19
6.1.1.5.2 Define Forwarding Agreement Types 19
6.1.1.5.3 Define Deactivation Reasons 20
6.1.1.5.4 Define Number Range Intervals for Agreements 20
6.1.2 Basic Functions 21
6.1.2.1 User Interface 21
6.1.2.1.1 Define Message Settings 21
______________________________________________________________
SAP AG iii
______________________________________________________________
6.1.2.2 Create Active Version and Model 21

6.1.2.3 Define General Settings for SAP TM 22
6.1.2.4 Define SLD Data of Business Systems 22
6.1.2.5 Charge Calculation 23
6.1.2.5.1 Basic Settings for Charge Calculation 23
6.1.2.5.1.1 Define General Settings 23
6.1.2.5.1.2 Define Rate Templates 24
6.1.2.5.1.3 Define Scale Templates 24
6.1.2.5.1.4 Define Calculation Sheet Templates 25
6.1.2.5.1.5 Define Charge Category Codes 26
6.1.2.5.1.6 Define Charge Subcategory Codes 26
6.1.2.5.1.7 Define Charge Type Codes 27
6.1.2.5.1.8 Define Charge Calculation Related Number Ranges 27
6.1.2.5.1.9 Define Number Range Intervals for Scales 28
6.1.2.5.1.10 Define Number Range Intervals for Rates 28
6.1.2.5.1.11 Define Number Range Intervals for Calculation Sheets 29
6.1.2.5.2 Data Source Binding for Charge Calculation 29
6.1.2.5.2.1 Define Scale Bases 30
6.1.2.5.2.2 Define Calculation Bases 30
6.1.2.5.2.3 Define Dimensional Weight Profile 31
6.1.2.5.3 Rules and Conditions for Charge Calculation 32
6.1.2.5.3.1 Define Rounding Rules 32
6.1.2.5.4 Enhancements of Charge Calculation Engine 33
6.1.2.5.4.1 Define Calculation Methods 33
6.1.2.6 Dangerous Goods 33
6.1.2.6.1 Define Common Settings for Dangerous Goods Processing 33
6.1.2.6.2 Define Dangerous Goods Profile 34
6.1.2.7 Type Codes and Role Codes 34
6.1.2.7.1 Master-Data-Related Type Codes and Role Codes 34
6.1.2.7.1.1 Define Party Roles 34
6.1.2.7.1.2 Define Package Type Codes 35
6.1.2.7.1.3 Define Transportation Goods Identifier Type Codes 35
6.1.2.7.2 General Type Codes and Role Codes 35
6.1.2.7.2.1 Define Business Transaction Document Type Codes 35
6.1.2.7.2.2 Define Business Transaction Document Item Type Codes 36
6.1.2.7.2.3 Define Block Reason Codes 36
6.1.2.8 Text Collection 36
6.1.2.8.1 Define Settings for Text Collection 36
6.1.2.9 Conditions 37
6.1.2.9.1 Data Access Definition 37
6.1.2.9.2 Define Text for Data Access Definition 37
______________________________________________________________
SAP AG iv
______________________________________________________________

6.1.2.9.4 Assign Condition Type to Data Access Definition 38
6.1.2.10 Geographical Map 38
6.1.2.10.1 Define Settings for Geographical Map 38
6.1.2.11 Printing 38
6.1.2.11.1 Assign Text Types to Print Document Text Fields 38
6.1.3 Forwarding Order Management 39
6.1.3.1 Define Number Range Intervals for Forwarding Order
Management 39
6.1.3.2 Forwarding Order 40
6.1.3.2.1 Define Forwarding Order Types 40
6.1.3.3 Forwarding Quotation 41
6.1.3.3.1 Define Forwarding Quotation Types 41
6.1.4 Freight Order Management 41
6.1.4.1 Define Number Range Intervals for Freight Order Management 41
6.1.4.2 Freight Order 42
6.1.4.2.1 Define Freight Order Types 42
6.1.4.3 Tendering 43
6.1.4.3.1 Define Settings for Tendering by E-mail 43
6.1.4.3.2 Define General Settings for Tendering 44
6.1.4.4 Freight Booking 46
6.1.4.4.1 Define Freight Booking Types 46
6.1.5 Planning 46
6.1.5.1.1 Define Profiles and Settings 46
6.1.5.1.2 Configure Process Controller for Planning 47
6.1.5.1.3 Define Transportation Allocation Settings 47
6.1.5.1.4 Define Customer-Specific Functions for Planning 48
6.1.5.1.5 Define Scheduling Constraints 48
6.1.5.2 Freight Unit 49
6.1.5.2.1 Define Freight Unit Types 49
6.1.6 Settlement 49
6.1.6.1 Configure Process Controller for Settlement 49
6.1.6.2 Define Settlement Profile 50
6.1.6.3 Forwarding Settlement 51
6.1.6.3.1 Define Forwarding Settlement Document Types 51
6.1.6.3.2 Define Number Range Intervals for Forwarding SDs 52
6.1.6.4 Freight Settlement 52
6.1.6.4.1 Define Freight Settlement Document Types 52
6.1.6.4.2 Define Number Range Intervals for Freight SDs 53
6.1.7 Global Trade 53
6.1.7.1 Define Customs Profile 53
______________________________________________________________
SAP AG v
______________________________________________________________
6.1.7.2 Define Customs Relevance Check 54

6.1.8.1 ERP Logistics Integration 54
6.1.8.1.1 Order-Based Transportation Requirement 54
6.1.8.1.1.1 Define Order-Based Transportation Requirement Types 55
6.1.8.1.1.2 Assign ERP Text Types to TM Text Types for OTR 55
6.1.8.1.2 Delivery-Based Transportation Requirement 56
6.1.8.1.2.1 Define Delivery-Based Transportation Requirement Types 56
6.1.8.1.2.2 Assign ERP Text Types to TM Text Types for DTR 56
6.1.8.1.3 Order Scheduling 57
6.1.8.1.3.1 Make Settings for Sales Order Scheduling 57
6.1.8.2 Integration to SAP NetWeaver Business Warehouse 57
6.1.8.2.1 Specify Settings for BW Relevance and Data Transfer 57
6.1.8.3 Tracking and Tracing of Processes and Documents 58
6.1.8.3.1 Prerequisites for Tracking and Tracing 58
6.1.8.3.2 Define Transportation Activities for Tracking and Tracing 59
6.1.9 Business Add-Ins (BAdIs) for Transportation Management 60
6.1.9.1 Master Data 60
6.1.9.1.1 General Settings 60
6.1.9.1.1.1 One-Time Locations 60
Locations 60
Address Data 61
6.1.9.1.1.2 Equipment Types and Equipment Groups 62
6.1.9.1.1.2.2 BAdI: Consistency Check for Equipment Types 63
6.1.9.1.2.1 Enhancement of SAP NetWeaver Identity Management Integration
64
Integration 64
6.1.9.1.2.2 Organizational Unit Integration 65
6.1.9.1.2.2.2 BAdI: Creation of Organizational Units 65
6.1.9.1.3 Transportation Network 66
6.1.9.1.3.1 Location 66
Identifiers 66
______________________________________________________________
SAP AG vi
______________________________________________________________
6.1.9.1.3.1.1.2 BAdI: Validation of Alternative Location Identifiers 67

6.1.9.1.3.2 Reuse Component 67
6.1.9.1.3.2.1 Enhancement of Distance and Duration Determination 67
6.1.9.1.3.2.1.2 BAdI: RC LDDD - Distance and Duration Determination 67
6.1.9.1.3.2.2 Enhancement of Basic Distance and Duration Determination 69
69
6.1.9.1.4 Resources 70
6.1.9.1.4.1 Enhancement of Check for Registration Numbers 70
6.1.9.1.4.1.2 BAdI: Extend Check for Registration Numbers of Resources 70
6.1.9.1.5 Agreements 71
Determination 71
6.1.9.1.5.2 BAdI: Agreement and Calculation Sheet Filter 72
6.1.9.1.5.3 BAdI: Condition for Agreement Determination 72
6.1.9.2 Basic Functions 73
6.1.9.2.1 Charge Calculation 73
6.1.9.2.1.1 BAdI: Profitability Calculation 73
6.1.9.2.1.2 BAdI: Calculation Sheet Resolution 74
6.1.9.2.1.3 BAdI: Calculation Sheet Process 75
6.1.9.2.1.4 BAdI: Charge Calculation Data Access for Business Objects 75
6.1.9.2.1.5 BAdI: Charge Calculation Rules 76
6.1.9.2.1.6 BAdI: Charge Calculation Engine 77
6.1.9.2.2 Dangerous Goods 78
6.1.9.2.2.2 BAdI: Definition of Data for Printing and Checking for
Dangerous Goods 79
6.1.9.2.3 Type Codes and Role Codes 80
6.1.9.2.3.2 BAdI: Quantity Type Code Determination 80
6.1.9.2.4 Change Controller 81
6.1.9.2.4.2 BAdI: Determination of Changes for Change Controller 81
6.1.9.2.5 Business Warehouse 82
6.1.9.2.5.2 BAdI: Condition for Extraction 82
6.1.9.2.5.3 BAdI: Fill Extraction Structures 84
6.1.9.2.6 Geographical Map 84
6.1.9.2.6.1 Enhancement to Adapt Displayed Objects 84
______________________________________________________________
SAP AG vii
______________________________________________________________
6.1.9.2.6.1.2 BAdI: Enhancement to Adapt Displayed Objects 85

6.1.9.2.7 Authorizations 86
6.1.9.2.7.1 Authorization Check 86
6.1.9.2.7.1.2 BAdI: Authorization Check 86
6.1.9.2.7.2 Output Management 87
6.1.9.2.7.2.2 BAdI: Register Additional BOs for TM Authorization Check 88
6.1.9.2.7.3 Data Retrieval Before Authorization Check 88
6.1.9.2.7.3.2 BAdI: Data Retrieval Before Authorization Check 89
6.1.9.2.8 Query Extensions 89
6.1.9.2.8.2 BAdI: Query Extensions 90
6.1.9.3 Forwarding Order Management 91
6.1.9.3.1 Approval Workflow 91
Management 91
6.1.9.3.2 Registry Extensions 92
6.1.9.3.2.2 BAdI: Extensions of Field Registry 92
6.1.9.4 Freight Order Management 93
6.1.9.4.1 Tendering 93
6.1.9.4.1.2 BAdI: Creation of Proposals for Tendering Plan 93
6.1.9.4.1.3 BAdI: Evaluation of Quotations 94
Tendering 95
6.1.9.4.1.5 BAdI: Preselection of Freight Requests for Quotation 96
6.1.9.4.1.6 BAdI: Filling of Result Structure for Forwarding and Freight
RFQs 97
6.1.9.4.1.7 BAdI: Filling of Result Structure for Tendering Query 98
6.1.9.4.1.8 BAdI: Sending of Tendering E-Mails 100
6.1.9.4.1.9 BAdI: Triggering of Alerts 101
6.1.9.4.1.10 BAdI: Update of Freight Order (FO) After Successful
Tendering 102
Assigned Carrier 103
6.1.9.5 Planning 104
6.1.9.5.1 BAdI: Determination of Subcontracting-Relevant Quantity 104
______________________________________________________________
SAP AG viii
______________________________________________________________
6.1.9.5.2 BAdI: Calculation of TAL Relevant Quantity 105

6.1.9.5.3 Additional Dimensions 106
6.1.9.5.3.2 BAdI: Additional Dimensions 106
6.1.9.5.4 VSR Optimizer 107
6.1.9.5.4.1 VSR Optimizer Preprocessing and Postprocessing 107
6.1.9.5.4.1.2 BAdI: VSR Optimizer Preprocessing 107
6.1.9.5.4.1.3 BAdI: VSR Optimizer Postprocessing 108
6.1.9.5.4.2 Explanation Tool: Customer Function 108
6.1.9.5.4.2.2 BAdI: Customer Function for Explanation Tool 109
6.1.9.6 Global Trade 110
6.1.9.6.1 Notes on Implementation 110
6.1.9.6.2 BAdI: Change Result of Customs Relevance Check 110
6.1.9.7 Integration 111
6.1.9.7.1 Tracking and Tracing of Processes and Documents 111
6.1.9.7.1.1 BAdI: Providing Execution Data for Transportation Activities 111
6.1.9.7.2 Enterprise Services 112
6.1.9.7.2.1 Forwarding Order Management 112
6.1.9.7.2.1.1.2 BAdI for TransportationRequestRequest_In 112
6.1.9.7.2.1.1.3 BAdI for TransportationRequestCancellationRequest_In 113
6.1.9.7.2.1.1.4 BAdI for TransportationRequestConfirmation_Out 113
6.1.9.7.2.2 Freight Order Management 114
6.1.9.7.2.2.1.2 BAdI for TransportationOrderRequest_Out 114
6.1.9.7.2.2.1.3 BAdI for TransportationOrderCancellationRequest_Out 115
6.1.9.7.2.2.1.4 BAdI for TransportationOrderConfirmation_In 115
6.1.9.7.2.2.2 Tendering 116
6.1.9.7.2.2.2.1 Transportation Request 116
116
117
117
6.1.9.7.2.2.2.2.2 BAdI for TransportationOrderQuotationCreateRequest_Out 118
______________________________________________________________
SAP AG ix
______________________________________________________________
6.1.9.7.2.2.2.2.3 BAdI for TransportationOrderQuotationCancellationRequest_Out

119
6.1.9.7.2.2.2.2.4 BAdI for TransportationOrderQuotationConfirmation_In 120
6.1.9.7.2.2.3 Booking 120
6.1.9.7.2.2.3.1.2 BAdI for TransportationOrderBookingRequest_Out 121
6.1.9.7.2.2.3.1.3 BAdI for TransportationOrderBookingCancellationRequest_Out
121
6.1.9.7.2.2.3.1.4 BAdI for TransportationOrderBookingConfirmation_In 122
122
6.1.9.7.2.3 Global Trade 123
6.1.9.7.2.3.1 Request for Export Declaration 123
6.1.9.7.2.3.1.2 BAdI for ExportDeclarationSUITERequest_Out 123
6.1.9.7.2.3.2 Cancellation Request for Export Declaration 124
6.1.9.7.2.3.2.2 BAdI for ExportDeclarationSUITECancellationRequest_Out 124
6.1.9.7.2.3.3 Confirmation of Export Declaration 125
6.1.9.7.2.3.3.2 BAdI for ExportDeclarationSUITEConfirmation_In 125
6.1.9.7.2.4 Settlement 126
6.1.9.7.2.4.1 Forwarding Settlement 126
126
126
127
6.1.9.7.2.4.2 Freight Settlement 128
128
128
129
6.1.9.7.2.5 ERP Logistics Integration 130
6.1.9.7.2.5.1.2 BAdI for IntracompanyTransportationRequestRequest_In 130
______________________________________________________________
SAP AG x
______________________________________________________________

130
6.1.9.7.2.5.1.4 BAdI for
IntracompanyTranspRequestSimulateReqConfirmation_In 131
6.1.9.7.2.5.2 Outbound Processing of Delivery Proposals 132
6.1.9.7.2.5.2.2 BAdI for InboundDeliveryCreateRequest_Out 132
6.1.9.7.2.5.2.3 BAdI for OutboundDeliveryBulkCreateRequest_Out 133
6.1.9.7.2.5.3 Outbound Delivery Confirmation 133
6.1.9.7.2.5.3.2 BAdI for OutboundDeliveryBulkConfirmation_In 134
6.1.9.7.2.5.4 Inbound Delivery Confirmation 134
6.1.9.7.2.5.4.2 BAdI for InboundDeliveryConfirmation_In_V1 135
6.1.9.7.2.5.5.2 Outbound Shipment Integration 135
6.1.9.7.2.5.5.2.1 BAdI for TransportationOrderSCMExecutionRequest_Out 135
6.1.9.7.2.5.5.2.2 BAdI for
TransportationOrderSCMExecutionCancellationReq_Out 136
137
6.1.9.7.2.5.5.3 Inbound Shipment Integration 137
6.1.9.7.2.5.5.3.1 BAdI for TransportationOrderSCMRequest_In 137
6.1.9.7.2.5.5.3.2 BAdI for TransportationOrderSCMCancellationRequest_In 138
6.1.9.7.2.5.5.3.3 BAdI for TranspOrderSCMTenderingResultNotification_Out 138
6.1.9.7.3 Other Web Services 139
6.1.9.7.3.1 Generation of a URI to Display a Transportation Document 139
6.1.9.7.3.1.2 BAdI for GetTransportationDocumentURI 139
6.2 SCM Basis 140
6.2.1.1 Basic Settings for Creating the System Landscape 140
6.2.1.1.1 Name Logical Systems 140
6.2.1.1.2 Assign Logical Systems to a Client 141
6.2.1.1.3 Set Up RFC Destination 142
6.2.1.1.4 Assign RFC Destinations to Various Application Cases 143
6.2.1.1.5 Maintain Business System Group 144
6.2.1.1.6 Assign Logical System and Queue Type 145
6.2.1.1.7 Settings for qRFC Communication 147
6.2.1.1.7.1 Configure qRFC Communication 147
6.2.1.1.7.2 Set Up QOUT Scheduler 148
6.2.1.1.7.3 Set Up QIN Scheduler 149
______________________________________________________________
SAP AG xi
______________________________________________________________
6.2.1.1.7.4 Set Up qRFC Administration for CIF Queue Display 150

6.2.1.1.8 Activate / Deactivate Background RFC (bgRFC) 151
6.2.1.2 Basic Settings for Data Transfer 151
6.2.1.2.1 Activate Incremental Data Transfer 151
6.2.1.2.2 Set User Parameters 152
6.2.1.3 BAdIs for Specific Applications 152
6.2.1.3.1 Location and Business Partner 152
6.2.1.3.1.1 BAdI: Inbound Processing for Location 153
6.2.1.3.1.2 BAdI: Inbound Processing for Business Partner 154
6.2.1.3.1.3 BAdI: Change of Business Partner Attributes 155
6.2.1.3.1.4 BAdI: Maintain and Save Business Partner Attributes 155
6.2.1.3.2 Product 156
6.2.1.3.2.1 BAdI: Inbound Processing for Product 156
6.2.1.3.2.2 BAdI: Master Data Hierarchy for Product 157
6.2.1.3.2.3 BAdI: Master Data Hierarchy for Location Product 158
6.2.1.3.3 Classes, Characteristics, and Classifications 159
6.2.1.3.3.1 BAdI: Inbound Processing for Classification 159
6.2.1.3.3.2 BAdI: Inbound Processing for Characteristics 160
6.2.1.3.3.3 BAdI: Inbound Processing for Class Hierarchies 161
6.2.1.3.3.4 BAdI: Inbound Processing for Classes 162
6.2.1.3.4 Sources of Supply 163
6.2.1.3.4.1 BAdI: Inbound Processing for Sources of Supply 163
6.2.1.3.4.2 BAdI: Change of Sources of Supply 164
6.2.1.3.5 Transportation Lanes 165
6.2.1.3.5.1 BAdI: Transportation Lanes 165
6.2.1.3.6 Batches 165
6.2.1.3.6.1 BAdI: CIF Inbound Processing for Batches 165
6.2.1.3.7 CIF Core 166
6.2.1.3.7.1 BAdI: Inbound Processing for CIF Error Handling 166
6.2.1.3.7.2 BAdI: Inbound Processing for Master Data Hierarchy PDS 167
6.2.2 Master Data 168
6.2.2.1 Change Notification Agent 168
6.2.2.1.1 Maintain Change Notification Agent 168
6.2.2.2 Define Parameters for Master Data Locking Concept 168
6.2.2.3 Maintain Freely-Definable Attributes 169
6.2.2.4 Calendar 170
6.2.2.4.1 Maintain Factory Calendar 170
6.2.2.4.2 Maintain Planning Calendar (Time Stream) 173
6.2.2.5 Location 174
6.2.2.5.1 Activate Change Documents 174
6.2.2.5.2 Configuration for Alternative Location Identifiers 175
______________________________________________________________
SAP AG xii
______________________________________________________________
6.2.2.5.3 BAdI: Validation of Alternative Location Identifiers 176

6.2.2.6 Business Partner 177
6.2.2.6.1 Define Transportation Service Level Codes 177
6.2.2.6.2 Map ERP Shipping Conditions to Transp. Serv. Level Codes 177
6.2.2.6.3 Define Industry Keys 178
6.2.2.6.4 Define Terms of Payment 178
6.2.2.6.5 Define Customer Account Groups 179
6.2.2.6.6 Define Vendor Account Groups 179
6.2.2.6.7 Define Business Partner Functions 180
6.2.2.6.8 Define Delivery Priorities 180
6.2.2.6.9.1 Organizational Model 181
6.2.2.6.9.1.1 Create Organizational Model 181
6.2.2.6.9.1.2 Change Organizational Model 182
6.2.2.7 Product 183
6.2.2.7.1 Maintain Product-Relevant Hierarchies and Hierarchy
Structures 183
6.2.2.7.2 Specify Output Format of Product Number 183
6.2.2.7.3 Configure Time Base of Fields 184
6.2.2.7.4 Maintain Rounding Profiles 185
6.2.2.7.6 Product Groups 187
6.2.2.7.6.1 Define Product Group Types 187
6.2.2.7.6.2 Define Product Groups 188
6.2.2.7.7 Maintain Type of Alternative Product Number 189
6.2.2.7.8 Define Replenishment Indicator 189
6.2.2.7.9 Define ABC Indicators 190
6.2.2.7.10 Maintain Transportation Group 190
6.2.2.7.11 Define Packaging Material Types 190
6.2.2.8 Partner-Dependent Data 191
6.2.2.8.1 Activate Change Documents for Partner-Dependent Locations 191
6.2.2.8.2 Activate Change Documents for Partner-Dependent Product Data
192
6.2.2.9 Resource 192
6.2.2.9.1 Processor 192
6.2.2.9.1.1 Make Settings for the HR System 192
6.2.2.10 Transportation Lane 193
6.2.2.10.1 Maintain Transportation Mode 193
6.2.2.10.2 Maintain Means of Transport 194
6.2.2.10.3 Set Usage of GIS Tool 195
6.2.2.10.5 Transportation Service Provider Profile 196
______________________________________________________________
SAP AG xiii
______________________________________________________________
6.2.2.10.5.1 Define Freight Code Sets, Freight Codes, and Determination 196
6.2.2.10.5.2 Define Product Freight Groups 197
6.2.2.11 Trailers and Compartments 197
6.2.2.12 Quota Arrangement 199
6.2.2.13 Business Add-In (BAdI) for Source Determination 199
6.2.2.13.1 BAdI: Source Determination 199
6.2.2.14 Product and Location Interchangeability 201
6.2.2.14.1 Application Settings 201
6.2.2.14.1.1 General Settings 201
6.2.2.14.1.2 Maintain Attribute Properties for Supersession Chains 201
6.2.2.14.1.3 Maintain Member Types 202
6.2.2.14.1.4 Maintain Replacement Types 203
6.2.2.14.1.5 Maintain Interchangeability Group Types and Assign
Replacement Types 205
6.2.2.14.1.6 Maintain Graphic Profile 206
6.2.2.14.2 Maintain Number Range for Groups 206
6.2.2.14.3 Maintain Reason Code 207
6.2.2.14.4 Consistency Checks 208
6.2.2.14.4.1 Maintain Field Catalog 208
6.2.2.14.4.2 Maintain Validation 208
6.2.2.14.4.3 Maintain Consistency Profiles and Assign Validation 211
6.2.2.14.4.4 Assign Consistency Profiles and Field Catalog to Group Type 212
6.2.2.14.5 Business Add-Ins (BAdIs) for Product and Location
Interchangeability 213
6.2.2.14.5.1 BAdI: Consistency Checks 213
6.2.2.14.5.2 BAdI: Interface Enhancements 214
6.2.2.14.5.3 BAdI: Master Data Maintenance for Product and Location
Interchangeability 215
6.2.2.14.5.4 BAdI: Rule Resolution 216
6.2.2.14.5.5 BAdI: Group Filter 217
6.2.2.14.5.6 BAdI: XML Upload of Interchangeability Groups 217
6.2.2.14.5.7 BAdI: External Customer Enhancements 218
6.2.2.15 Hierarchy 219
6.2.2.15.1 Define Hierarchy Structure 219
6.2.2.15.2 BAdI: BOD Product Assignment 222
6.2.2.16 Specify Person Responsible (Planner) 222
______________________________________________________________
SAP AG xiv
______________________________________________________________
6.2.2.17 Define Incoterms 223

6.2.2.18 Enterprise Services 223
6.2.2.18.1 Assign Code to Planner 223
6.2.2.18.2 Assign Code to Product Group 224
6.2.2.18.3 Business Add-Ins (BAdIs) 224
6.2.2.18.3.1 Location Data Management 224
6.2.2.18.3.1.1 Location and Bill of Distribution 224
6.2.2.18.3.1.1.1 Note on Implementation 224
6.2.2.18.3.1.1.2 BAdI for
LocationSimpleByIDAndTypeCodeAndDescriptionQueryResponse 225
6.2.2.18.3.1.1.3 BAdI for LocationCreateRequestConfirmation 226
6.2.2.18.3.1.1.4 BAdI for LocationChangeRequestConfirmation 226
6.2.2.18.3.1.1.5 BAdI for LocationByIDQueryResponse 227
6.2.2.18.3.1.1.6 BAdI for LocationDeactivateRequestConfirmation 228
6.2.2.18.3.1.1.7 BAdI for LocationByIDAndTypeCodeQuery 229
6.2.2.18.3.1.1.8 BAdI for BillOfDistributionByIDQueryResponse 229
6.2.2.18.3.1.1.9 BAdI for LocationSimpleByIDAndRadiusQueryResponse 230
6.2.2.18.3.1.1.10 BAdI for
LocationSCMSimpleByIdentifyingElementsQueryResponse 231
6.2.2.18.3.1.2 Supply Planning Area 232
6.2.2.18.3.1.2.2 BAdI for SupplyPlanningAreaCreateRequest/Confirmation 232
6.2.2.18.3.1.2.3 BAdI for SupplyPlanningAreaChangeRequest/Confirmation 233
6.2.2.18.3.1.2.4 BAdI for SupplyPlanningAreaByLocationIDQuery/Response 233
6.2.2.18.3.1.2.5 BAdI for SupplyPlanningAreaDeactivateRequest/Confirmation
234
6.2.2.18.3.1.2.6 BAdI for
SupplyPlanningAreaByLocationIDAndLocationTypeCodeQuery 235
6.2.2.18.3.1.2.7 BAdI for
SupplyPlanningAreaSCMSimpleByLocationQueryResponse 236
6.2.2.18.3.1.3 Transportation Lane 237
6.2.2.18.3.1.3.2 BAdI for TransportationLaneSimpleByElementsQuery/Response
237
6.2.2.18.3.1.3.3 BAdI for
TransportationLaneByTransportationLaneQuery/Response 238
6.2.2.18.3.1.3.4 BAdI for
TransportationLaneSCMByIdentifyingElementsQueryResp 239
6.2.2.18.3.1.3.5 BAdI for TransportationLaneSCMCancelRequestConfirmation_In
239
6.2.2.18.3.1.3.6 BAdI for
TransportationLaneSCMChangeRequestConfirmation_In 240
6.2.2.18.3.1.3.7 BAdI for
TransportationLaneSCMConsistencyCheckQueryResponse_In 241
______________________________________________________________
SAP AG xv
______________________________________________________________
6.2.2.18.3.1.3.8 BAdI for

TransportationLaneSCMCreateCheckQueryResponse_In 242
6.2.2.18.3.1.3.9 BAdI for TransportationLaneSCMCreateRequestConfirmation_In
243
6.2.2.18.3.1.3.10 BAdI for
TransportationLaneSCMValidMaterialChangeRequestConfirmation_243
6.2.2.18.3.1.3.11 BAdI for
TransportationLaneSCMValidTransportMeansChangeRequestConfirm
244
6.2.2.18.3.2 Product Data Maintenance 245
6.2.2.18.3.2.1 Material 245
6.2.2.18.3.2.1.2 BAdI for MaterialSimpleByIDAndDescriptionQuery/Response
245
6.2.2.18.3.2.1.3 BAdI for
MaterialSCMSimpleByIdentifyingElementsQueryResponse 246
6.2.2.18.3.2.1.4 BAdI for MaterialBasicDataCreateRequest/Confirmation 247
6.2.2.18.3.2.1.5 BAdI for MaterialBasicDataChangeRequest/Confirmation 248
6.2.2.18.3.2.1.6 BAdI for MaterialBasicDataByIDQuery/Response 249
6.2.2.18.3.2.1.7 BAdI for
MaterialSCMServicePartsPlanningInventoryPolicyChangeRequest_249
6.2.2.18.3.2.1.8 BAdI for
MaterialSCMServicePartsPlanningInventoryPolicyBulkChangeRequ250
6.2.2.18.3.2.1.9 BAdI for MaterialSupplyPlanningChangeRequest/Confirmation
251
6.2.2.18.3.2.1.10 BAdI for MaterialSupplyPlanningByIDQuery/Response 251
6.2.2.18.3.2.1.11 BAdI for
MaterialSupplyPlanningSupplyPlanningAreaByIDAnd..Query/Respo252
6.2.2.18.3.2.1.12 BAdI for
MaterialServicePartsPlanningChangeRequest/Confirmation 253
6.2.2.18.3.2.1.13 BAdI for MaterialServicePartsPlanningByIDQuery/Response 254
6.2.2.18.3.2.1.14 BAdI for
MaterialServicePartsPlanningSupplyPlanningAreaByID..Query/Re 254
6.2.2.18.3.2.1.15 BAdI for
MaterialServicePartsPlanningSupplyPlanningAreaByIDAndSPAID 255
6.2.2.18.3.2.1.16 BAdI for MaterialDeactivateRequest/Confirmation 256
6.2.2.18.3.2.1.17 BAdI for
MaterialLocationByIDAndLocationIDAndLocationRadiusQuery 257
6.2.2.18.3.2.1.18 BAdI for
MaterialSCMReplenishmentByElementsQueryResponse_In 258
6.2.2.18.3.2.1.19 BAdI for
MaterialSCMReplenishmentChangeRequestConfirmation_In 258
6.2.2.18.3.2.1.20 BAdI for
______________________________________________________________
SAP AG xvi
______________________________________________________________
MaterialSCMSimpleBySupplyPlanningAreaIDQueryResponse_In 259
6.2.2.18.3.2.1.21 BAdI for
MaterialSCMSupplyPlanningAreaAssignmentActivateRequestConf
260
6.2.2.18.3.2.1.22 BAdI for
MaterialSCMSupplyPlanningAreaAssignmentDeactivateRequestConf
261
6.2.2.18.3.3 Source of Supply Determination 261
6.2.2.18.3.3.1 Source of Supply 261
6.2.2.18.3.3.1.1 BAdI for SourceOfSupplySCMByElementsQueryIn 261
6.2.2.18.3.3.1.2 BAdI for SourceOfSupplyByElemenstQueryResponse 262
6.2.2.18.3.4 Interchangeability Group Management 263
6.2.2.18.3.4.1 Material and Site Interchangeability Group 263
6.2.2.18.3.4.1.1 BAdI for
MaterialAndSiteInterchangeabilityGroupSCMByElementsQuery 263
6.2.3 Master Data Layer 264
6.2.3.1 BAdI: Modify Generated Partner ID 264
6.2.4 Configure Parameters 265
6.2.5 Alert Monitor 265
6.2.5.1 Define Number Ranges for Alerts 265
6.2.5.2 Activate/Deactivate Applications in Alert Monitor 265
6.2.5.3 Maintain Prioritization of Alert Types 266
6.2.5.4 Define Additional Status in Alert Monitor 267
6.2.5.5 Limit Additionally Defined Status to Specific Alert Object
Types 267
6.2.5.6 Business Add-Ins (BAdIs) for the Alert Monitor 268
6.2.5.6.1 Change Prioritization of Alerts Read 268
6.2.5.6.2 Extend or Change Alert List 269
6.2.6 Alert Notification Engine 270
6.2.6.1 Specify Message Channels for Alert Notification Engine 270
6.2.6.2 Connection of the Alert Notification Engine to the Portal 270
6.2.6.3 Business Add-Ins (BAdIs) for the Alert Notification Engine 271
6.2.6.3.1 Change Structure of Messages 271
6.2.6.3.2 Change URL for Calling an Alert 272
6.2.6.3.3 Change Attachments 272
6.2.6.3.4 BAdI: Change Authorization Check for Location Products 272
6.2.7 Process Controller 273
6.2.7.1 Define Service 273
6.2.7.2 Define Strategy 273
6.2.7.3 Define Methods 274
6.2.7.4 Assign Methods to a Strategy 274
6.2.7.5 Define Parameters 274
6.2.7.6 Assign Parameters to a Method 275
______________________________________________________________
SAP AG xvii
______________________________________________________________
6.2.7.7 Assign Method Parameters to a Strategy 275

6.2.8 Logistics Inventory Management Engine (LIME) 276
6.2.8.1 Basic Settings 276
6.2.8.1.1 Features of Calling Application 276
6.2.8.1.1.1 Process Type of Calling Application 276
6.2.8.1.1.1.1 Determine Process Type of Calling Application 276
6.2.8.1.1.1.2 Determine External Number Assignment for Inbound Documents
277
6.2.8.1.1.1.3 Dispatcher 278
6.2.8.1.1.1.3.1 Determine Control Data for Dispatcher 278
6.2.8.1.1.1.3.2 Set Filter Values for Dispatcher 278
6.2.8.1.1.1.3.3 Define Filter Values for the Distribution of Documents 279
6.2.8.1.1.1.3.4 Determine Number Assignment for Documents 279
6.2.8.1.2 Index Tables and Hierarchy 280
6.2.8.1.2.1 Generate LIME Source Code 280
6.2.8.1.2.2 Determine Index Tables 280
6.2.8.1.2.3 Determine Hierarchy 281
6.2.8.1.2.4 Determine Node Width 282
6.2.8.1.3 User-Specific Parameters 282
6.2.8.1.3.1 Determine Grouping Parameters 282
6.2.8.1.3.2 Determine Type of Quantity Calculation 283
6.2.8.1.4 Application-Specific Settings 283
6.2.8.1.4.1 Determine Stock Type 283
6.2.8.1.4.2 Determine Indicator for Virtual Stock 284
6.2.8.1.4.3 Determine Indicator for Stock Use 285
6.2.8.1.4.4 Determine Reason for Movement 286
6.2.8.1.4.5 Define Description of Stock Change 286
6.2.8.1.4.6 Determine Global Customizing Settings for Each Client 287
6.2.8.2 Business Add-Ins (BAdIs) 287
6.2.8.2.1 Dependencies Between BAdIs 287
6.2.8.2.2 BAdI: Static Checks of Inbound Documents 288
6.2.8.2.3 BAdI: Read LIME Master Data 290
6.2.8.2.4 BAdI: LIME QCI Converter 293
6.2.8.2.5 BAdI: LIME Customizing 295
6.2.8.2.6 BAdI: Fill LIME Collections 297
6.2.8.2.7 BAdI: Distribution of LIME Documents 299
6.2.9 Physical Inventory 302
6.2.9.1 Basic Settings 302
6.2.9.1.1 Define Physical Inventory Area 302
6.2.9.2 Business Add-Ins (BAdIs) 303
6.2.9.2.1 Influencing Physical Inventory Processing 303
______________________________________________________________
SAP AG xviii
______________________________________________________________
6.2.9.2.1.2 BAdI: Information About Activated Physical Inventory

Document Items 303
Activated 304
6.2.9.2.1.4 BAdI: Influencing of Book Inventory Determination of a PI
Document 305
6.2.9.2.1.5 BAdI: Information About Changed Physical Inventory Document
Items 306
Changed 306
6.2.9.2.1.7 BAdI: Information About Counted Physical Inventory Document
Items 307
Counted 308
6.2.9.2.1.9 BAdI: Setting the Count Date When Creating a Physical
Inventory Document 309
6.2.9.2.1.10 BAdI: Information About Physical Inventory Document Items
Created 309
6.2.9.2.1.11 BAdI: Setting the Priority When Creating a Physical
Inventory Document 310
Created 311
6.2.9.2.1.13 BAdI: Information About Deleted Physical Inventory Document
Items 312
Deleted 312
6.2.9.2.1.15 BAdI: Information About Inventory Adjustment Postings 313
6.2.9.2.1.16 BAdI: Rejection of Inventory Adjustment Postings 314
6.2.9.2.1.17 BAdI: Information About PRL Check Result 315
6.2.9.2.1.18 BAdI: Information About Posted Physical Inventory Document
Items 315
Posted 316
6.2.9.2.1.20 BAdI: Information About Recounted Physical Inventory
Document Items 317
Recounted 318
6.2.10 Configurable Process Scheduling 318
6.2.10.1 Scheduling Schema 318
6.2.10.1.1 Define Elements of Schema 319
6.2.10.1.2 Define Schema 319
6.2.10.1.3 Assign External Date Descriptors 322
______________________________________________________________
SAP AG xix
______________________________________________________________
6.2.10.2 Units of Time 322

6.2.10.2.1 Define Units 322
6.2.10.2.2 Assign Units 323
6.2.10.3 Process Definition 324
6.2.10.3.1 Simple Process Maintenance 324
6.2.10.3.2 Maintain Process 326
6.2.10.3.3 Define Process Alias 326
6.2.10.4 Calendar and Time Zones 326
6.2.10.4.1 Maintain Calendar 326
6.2.10.4.2 Maintain Process Scheduling Calendar (Time Stream) 329
6.2.10.4.3 Time Zones 330
6.2.10.4.3.1 Maintain System Settings 330
6.2.10.4.3.2 Maintain Time Zones 331
6.2.10.4.3.3 Maintain Geographical Assignments 332
6.2.10.5 Master Data for Activities 333
6.2.10.5.1 Assign Calendar 333
6.2.10.5.2 Assign Time Durations 334
6.2.10.5.3 Assign Time Zones 335
6.2.10.6 Scheduling Log 335
6.2.10.6.1 Find, Display, and Delete Logs 335
6.2.10.7 Condition Technique 336
6.2.10.7.1 Create Field Catalog 336
6.2.10.7.2 Define Condition Tables 337
6.2.10.7.3 Define Access Sequences 338
6.2.10.7.5 Define Determination Procedure 339
6.2.10.7.6 Determine Condition Maintenance Groups for Context 340
6.2.10.7.7 Create Condition Maintenance Group 340
6.2.10.7.8 Assign Schema and Activity to a Determination Schema 340
6.2.10.8 Interfaces 342
6.2.10.8.1 Maintain Transportation Zone 342
6.2.10.8.2 Define Assignment of Transportation Zones to Locations 343
6.2.10.8.3 Define Assignment of Default Means of Transport to Shipping
Conditions 344
6.2.10.8.4 Perform Consistency Check 344
6.2.10.8.5 Determine Assignment of Item Category to Process Alias 345
6.2.10.9 Test Scheduling 346
6.2.11 Order Document Management 346
6.2.11.1 Configure Order Document Management 346
6.2.11.2 Define Value Range 349
6.2.11.3 Check Settings in Order Document Management 349
______________________________________________________________
SAP AG xx
______________________________________________________________
6.2.11.4 Activate Settings in Order Document Management 350

6.2.11.5 Generate Settings in Order Document Management 351
6.2.11.6 BAdI: Adjust Worklist of Deletion Report 351
6.2.12 Time Series Data Management 352
6.2.12.1 Configure Time Series Data Management 352
6.2.12.2 Configure Parameters 354
6.2.12.3 Activate Time Profile 354
6.2.12.4 Delete Time Profile 355
6.2.12.5 Activate Time Series Data Type 355
6.2.12.6 Delete Time Series Data Type 356
6.2.12.7 Activate Time Series Data Area 357
6.2.12.8 Delete Time Series Data Area 357
6.2.12.9 Copy Time Series Data Area 358
6.2.12.10 Delete Time Series Data 358
6.2.12.11 Delete Time Series Change History 359
6.2.12.12 BAdI: Definitions for Change Period in Time Profile
Activation 359
6.2.13 Pack 361
6.2.13.1 Packaging Specification 361
6.2.13.1.1 Define Number Range for Packaging Specification 361
6.2.13.1.2 Define General Packaging Specification Parameters 362
6.2.13.1.3 Define Packaging Specification Group 362
6.2.13.1.4 Define RFC Connection for Packaging Specification
Distribution 363
6.2.13.1.5 Maintain Master Data for Packaging Specifications 364
6.2.13.1.6 Maintain Structure of Packaging Specification 364
6.2.13.1.6.1 Define Level Type 364
6.2.13.1.6.2 Define Element Type 365
6.2.13.1.6.3 Define Level Set 366
6.2.13.1.6.4 Define Work Step Type 367
6.2.13.1.6.5 Define Packaging Material Types 367
6.2.13.1.6.6 Assign Packaging Material Type to Element Type 368
6.2.13.1.6.7 Assign Work Step Type to Packaging Material Type 369
6.2.13.1.7 Determination of Packaging Specifications 369
6.2.13.1.7.1 Create Field Catalog 370
6.2.13.1.7.2 Define Condition Tables 373
6.2.13.1.7.3 Define Access Sequences 374
6.2.13.1.7.4 Define Condition Types 375
6.2.13.1.7.5 Define Determination Procedure 376
6.2.13.1.7.6 Create Condition Maintenance Group 376
6.2.13.1.8 Business Add-Ins for Packaging Specifications 377
6.2.13.1.8.1 Packaging Specification User Interface 377
______________________________________________________________
SAP AG xxi
______________________________________________________________

Header Attributes 377
6.2.13.1.8.1.3 BAdI: User Interface Enhancement for Content 378
Level Attributes 379
6.2.13.1.8.1.5 BAdI: User Interface Enhancement of Packaging Specification
Elements 380
6.2.13.1.8.1.6 BAdI: Best Possible Packaging Material for Level 381
6.2.13.1.8.1.7 BAdI: Best Possible Target Quantity for Level 382
6.2.13.1.8.1.8 BAdI: Calculate Level Dimension 382
6.2.13.1.8.1.9 BAdI: Additional Change Documents 383
6.2.13.1.8.1.10 BAdI: Display Change Documents 384
6.2.13.1.8.1.11 BAdI: Automatic Condition Records from Packaging
Specification 385
6.2.13.1.8.1.12 BAdI: Enhance Input Help in User Interface for Packaging
Specification 385
6.2.13.1.8.2 Packaging Specification 386
6.2.13.1.8.2.2 BAdI: Check Changes to Packaging Specification 387
6.2.13.1.8.2.3 BAdI: Check Changes to Element Group 387
6.2.13.1.8.2.4 BAdI: Check Changes to Work Steps 388
6.2.13.1.8.2.5 BAdI: Determine Packaging Specification Labels 389
6.2.13.1.8.2.6 BAdI: PDF printing of Packaging Specification 390
6.2.13.1.8.2.7 BAdI: Print Packaging Spec. Labels for Packaging
Specification or VAS Order 390
6.2.13.1.8.3 Packaging Specification Determination 391
6.2.13.1.8.3.2 BAdI: Prepare Packaging Specification Determination for Ext.
Field Catalog 392
6.2.13.1.8.3.3 BAdI: Change Results of Packaging Specification
Determination 393
6.2.13.1.8.3.4 BAdI: Determine Results of Packaging Specification
Determination 393
6.2.13.1.8.3.5 BAdI: Additional Data When Saving Condition Records 394
6.2.13.1.8.4 Work Steps User Interface 395
6.2.13.1.8.4.2 BAdI: User Interface Enhancement for Work Steps 395
6.2.13.1.8.4.3 BAdI: Maintain Dynamic Attributes for Work Step 396
6.2.13.1.8.5 Distribution 397
______________________________________________________________
SAP AG xxii
______________________________________________________________
6.2.13.1.8.5.2 BAdI: Distribute Packaging Specification 397

6.2.13.1.8.5.3 BAdI: Distribute Element Groups 398
6.2.13.1.8.5.4 BAdI: Distribute Work Step 398
6.2.13.1.8.5.5 BAdI: Distribute Condition Records 399
6.2.13.2 Handling Units 400
6.2.13.2.1 Define Packaging Material Types 400
6.2.13.2.2 Define Packing Groups for Products 401
6.2.13.2.3 Maintain Allowed Packaging Material Types for Packing Group 401
6.2.13.2.4 Define HU Types 402
6.2.13.2.5 Define Identification Types 402
6.2.13.2.6.1 Basic Enhancements for Handling Units 403
6.2.13.2.6.1.2 BAdI: Handling Unit Header Data 403
6.2.13.2.6.1.3 BAdI: Nesting and Unpacking of Handling Units 404
6.2.13.2.6.1.4 BAdI: Product-Specific Checks During Packing / Unpacking 405
6.2.13.2.6.1.5 BAdI: Automatic Packing By Packaging Specification 405
6.2.14 Transport Load Builder (TLB) 406
6.2.14.1 Define TLB Parameters 406
6.2.14.2 Make TLB Basic Settings 406
6.2.15 Planning Service Manager 408
6.2.15.1 Define Process Profile 408
6.2.15.2 Define Storage Service Profile 409
6.2.15.3 Define Selections 410
6.2.15.4 Define Planning Profile 412
6.2.15.5 Assign Standard Service Profiles for UI 413
6.2.15.6 Configure Planning Service Manager 414
6.2.15.7 Assign Selection Types to Application 416
6.2.15.8 Define Service Profile for Example Service 417
6.2.16 Data Management Layer 417
6.2.16.1 Triggers (for Planning File Entry) 417
6.2.16.1.1 Configure Triggers 417
6.2.16.1.2 Define Trigger Groups and Attributes 418
6.2.16.1.3 Activate Trigger 420
6.2.16.1.4 Business Add Ins (BAdIs) for Trigger 420
6.2.16.1.4.1 Determine Trigger Values for Location Products (Only BAdI
Triggers) 420
6.2.16.1.4.2 Determine Trigger Values for Products (Only BAdI Trigger) 421
6.2.16.1.4.3 Determine Trigger Values for Location (Only BAdI Triggers) 422
6.2.16.2 Transaction Data Layer (TDL) 422
6.2.16.2.1 TDL: Configure Decision Tables 422
6.2.16.2.2 TDL: Make Basic Settings 424
______________________________________________________________
SAP AG xxiii
______________________________________________________________
6.2.16.2.3 TDL: Configure Settings for Semantic Mapping 425

6.2.16.2.4 TDL: Define Service Profile for Copying Transaction Data 426
6.2.16.2.5 Define Reason Code for Fixed Demands 428
6.2.16.2.6 Define Reasons for Ordering 428
6.2.17 EH&S Services 429
6.2.17.1 Basic Services 429
6.2.17.1.1 Specify Environment Parameters 429
6.2.17.1.2 Manage User Exits 430
6.2.17.1.3 Assign Parameter User Exits 430
6.2.17.1.4 Specify Validity Area Categories 431
6.2.17.1.5 Specify Validity Areas 431
6.2.17.1.6 BAdI: Wrapper for Material Master and Product Master 432
6.2.17.2 Phrase Management 433
6.2.17.2.1 Specify Number Ranges for Phrases 433
6.2.17.2.2 Specify Phrase Libraries and Phrase Groups 434
6.2.17.2.3 Specify Language Selection 434
6.2.17.2.4 Specify Phrase Statuses 435
6.2.17.2.5 Configure Distribution for Phrases 435
6.2.17.2.6 BAdI: ALE and Menu Enhancement for Phrases 436
6.2.17.2.7 Authorization Management 437
6.2.17.2.7.1 Specify Authorizations 437
6.2.17.3 Hazardous Substance Master 438
6.2.17.3.1 Mast. Data 438
6.2.17.3.1.1 Specify Storage Hazards 438
6.2.17.3.1.2 Specify Text Types 439
6.2.17.3.1.3 Specify Numeric Value Types 439
6.2.17.3.1.4 Activate Phrase Assignment 439
6.2.17.3.1.5 Create Standard Phrase Sets 440
6.2.17.3.1.6 BAdI: Checks When Deleting Hazardous Substance Master
Records 440
6.2.17.3.3 Distribution 442
6.2.17.3.3.1 Configure Distribution for Hazardous Substance Master 442
6.2.17.3.3.2 BAdI: Hazardous Substance Distribution 443
6.2.17.4 Dangerous Goods Management 445
6.2.17.4.1 Customizing exchange between EH&S in ERP and SCM 445
6.2.17.4.2 Dangerous Goods Master 447
6.2.17.4.2.1 Specify Processing Statuses 447
6.2.17.4.2.2 Specify Validity Areas 448
6.2.17.4.2.3 Specify Mode-of-Transport Categories 449
______________________________________________________________
SAP AG xxiv
______________________________________________________________
6.2.17.4.2.4 Specify Collective Mode-of-Transport Categories 450

6.2.17.4.2.5 Specify Dangerous Goods Regulations 450
6.2.17.4.2.6 Specify Dangerous Goods Classes and Classification Codes 451
6.2.17.4.2.7 Specify Not Dangerous Goods Full/Empty Transport 452
6.2.17.4.2.8 Specify Transport Types 452
6.2.17.4.2.9 Specify Hazard Identification Numbers 453
6.2.17.4.2.10 Specify Danger Labels 453
6.2.17.4.2.11 Specify Packing Instruction Numbers 454
6.2.17.4.2.12 Specify Packaging Codes 454
6.2.17.4.2.13 Specify Profiles for User-Defined Dangerous Goods Texts 454
6.2.17.4.2.14 Specify Identification Number Types 455
6.2.17.4.2.15 Specify Labels 455
6.2.17.4.2.16 Specify Water Pollution Classes 455
6.2.17.4.2.17 Specify Combustible Liquid (VbF) Classes 456
6.2.17.4.2.18 Specify Storage Hazard Classes 456
6.2.17.4.2.19 Specify Stowage Categories 457
6.2.17.4.2.20 Specify Regulatory Basis for Transport Restriction 457
6.2.17.4.2.21 Activate Phrase Assignment 457
6.2.17.4.2.22 Create Standard Phrase Sets 458
6.2.17.4.2.23 Specify Tab Pages in Dangerous Goods Master 458
6.2.17.4.2.24 BAdI: Dangerous Goods Indicator Profile for Product Master 459
6.2.17.4.3 Dangerous Goods Checks and Dangerous Goods Documents 460
6.2.17.4.3.1 Common Settings 460
6.2.17.4.3.1.1 Assign Relevant Mode-of-Transport Categories to Means of
Transport 460
6.2.17.4.3.1.2 Specify Regulation Profile 461
6.2.17.4.3.1.3 Specify Indicator Category 461
6.2.17.4.3.1.4 Specify Business Context 462
6.2.17.4.3.1.5 Specify Indicator Profiles for Product Master 462
6.2.17.4.3.1.6 BAdI: Date Determination for DG Checks and Delivery Note
Printing 463
6.2.17.4.3.1.7 BAdI: Product exchange / multiple component explosion 464
6.2.17.4.3.2 Dangerous Goods Checks 465
6.2.17.4.3.2.1 Specify Dangerous Goods Check Methods 465
6.2.17.4.3.2.2 Specify Usage Profiles for Dangerous Goods Check Methods 466
6.2.17.4.3.2.3 Specify Dangerous Goods Check Schemas 468
6.2.17.4.3.2.4 BAdI: Determination of Dangerous Goods Check Schema 469
6.2.17.4.3.2.5 Specify Settings for Mixed Loading Checks 469
6.2.17.4.3.2.5.1 Specify Segregation Keys 469
6.2.17.4.3.2.5.2 Specify Responses 470
6.2.17.4.3.2.5.3 Specify Segregation Rules for Segregation Keys 471
6.2.17.4.3.2.5.4 Specify Regulation-Dependent Mixed Loading Groups 472
______________________________________________________________
SAP AG xxv
______________________________________________________________
6.2.17.4.3.2.5.5 Specify Segregations 473

6.2.17.4.3.2.5.6 Specify Mixed Loading Rules 474
6.2.17.4.3.2.5.7 Specify Enterprise-Specific Mixed Loading Groups 475
6.2.17.4.3.2.5.8 Specify Segregation Rules for Enterprise-Specific Mixed
Loading Groups 476
6.2.17.4.3.3 Dangerous Goods Documents 477
6.2.17.4.3.3.1 Manage User Exits 477
6.2.17.4.3.3.2 Specify Output Conditions and Formatting Methods 478
6.2.17.4.3.3.3 Specify Languages 478
6.2.17.4.3.3.4 BAdI: Enhancements for Delivery Note Printing 479
6.2.17.4.4 Interface: Distribution 480
6.2.17.4.4.1 BAdI: Enhancement for Mapping of Dangerous Goods Data 480
6.2.18 Basic Settings for Supply Chain Analytics Applications 482
6.2.18.1 Define Mapping for Business Objects 482
6.2.18.2 Define Error Queue for Business Objects 483
6.2.18.3 Define Analysis Objects 484
6.2.18.4 Define Analysis Applications and Processing Sequence 485
6.2.18.5 Define Application Log for Analysis Tools 486
6.2.18.6 Create Customer-Defined Analytic Applications 487
6.2.18.7 Create Customer-Defined Document Types 488
6.2.18.8 Enterprise Services 490
6.2.18.8.1.1 BAdI for Delivery Information 490
6.2.18.8.1.2 BAdI for Information Messages About Sales Orders 491
6.2.18.8.1.3 BAdI for Information Messages About Purchase Orders 492
6.2.18.8.1.4 BAdI for Notifications about Delivery Schedules 493
6.2.19 Routing Guide 494
6.2.19.1 General Settings for Route Determination 494
6.2.19.2 Define Request Types for Routing Guide 494
6.2.19.3 Define Modes of Transport for Foreign Trade 495
6.2.20 Cross-System and Cross-Partner Document Flow 495
6.2.20.1 Define Document Categories for Document Flow 495
6.2.20.2 Maintain Object Link Model 496
6.2.20.3 Define Maximum Chains for Document Flow 497
6.2.21 Enterprise Services 497
6.2.21.1 Supply and Demand Matching 497
6.2.21.1.1 Supply Planning Exception 497
6.2.21.1.1.1 BAdI for Supply Plan SCM Exceptions By Elements Query 497
6.2.21.2 Enterprise Services for Master Data 498
______________________________________________________________
SAP AG xxvi
______________________________________________________________
6.2.21.3 Supply Chain Analytics Applications 498
______________________________________________________________
SAP AG xxvii

SAP TM 8.0 IMG Help

Uploaded by

Copyright:

Available Formats

SAP TM 8.0 IMG Help

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP TM 8.0 IMG Help

Uploaded by

Copyright:

Available Formats

What are equipment groups and types used for in transportation management?

What are equipment groups and types used for in transportation management?

What are number range intervals used for in transportation management?

What are number range intervals used for in transportation management?

SAP System

6.1 Transportation Management

6.1.1 Master Data

6.1.1.1 General Settings

6.1.1.1.1 Define Equipment Groups and Equipment Types

We deliver the CN equipment group with 32 default container types.

Define equipment groups and assign equipment types to them.

6.1.1.1.2 Define Number Range Intervals for One-time Locations

- You must define a number range interval of the type "internal".

Possible definitions of number range intervals can be:

Object: Master Data, Locations (C_APO_LOC) authorization object as follows:

6.1.1.2 Organizational Management

6.1.1.2.1 Organizational Model

6.1.1.2.1.1 Create Organizational Model

- You define the validity period for the organizational unit.

6.1.1.2.1.2 Change Organizational Model

Examples of possible changes are:

6.1.1.2.1.3 Create and Merge Organizational Hierarchy

6.1.1.3 Transportation Network

6.1.1.3.1.1 Activate Change Documents

In this IMG activity, you activate change documents for locations.

6.1.1.3.1.2 Configuration for Alternative Location Identifiers

6.1.1.3.2 Transportation Lane

6.1.1.3.2.1 Activate Change Documents

6.1.1.3.2.2 Define Transportation Mode

In this Customizing activity, you can define transportation modes.

Transportation modes can be road, rail, air, or sea.

6.1.1.3.3 General Settings for Transportation Network Determination

In this IMG activity, you can do the following settings:

1. Source location or zone

6.1.1.4.1 Define Means of Transport

In this IMG activity, you define means of transport.

6.1.1.4.2 Define Compartment Type

In this IMG activity you define compartment types.

6.1.1.4.3 Define Means-of-Transport Combination

6.1.1.4.4 Define Attributes of MTr Combination/Compartment

Transportation Planning/Vehicle Scheduling (TP/VS):

6.1.1.4.5 Define Coupling/Uncoupling Duration

6.1.1.4.6 Maintain Registration Number Patterns

No registration number patterns are delivered.

1. Choose the resource type.

6.1.1.4.7 Specify Resource Template Types

6.1.1.4.8 Specify Categories of Alternative Names

6.1.1.4.9 Maintain Settings for Qualifications

In this IMG acitivity, you can specify qualifications.

6.1.1.4.10 Maintain Settings for Grouping Attributes

1. Specify grouping attribute categories.

You have specified the following:

6.1.1.4.11 Maintain Settings for Attached Equipment

In this IMG activity, you specify categories of attached equipment.

6.1.1.4.12 Maintain Settings for Aggregated Capacity Requirements

1. Enter the name of a handling resource.

6.1.1.4.13 Specify Capacity Variants

1. Specify a number for the capacity variant.

6.1.1.4.14 Assign Standard Equipment Type