Global Available-to-Promise (Global ATP Check)

ndice

Global Available-to-Promise (Global ATP Check)..............0

ndice.....................................................................................................................1
Global Available-to-Promise (Global ATP Check)..........................................3
General Settings..................................................................................................3
Maintain Global Settings for Availability Check...............................................4
Maintain Category...............................................................................................5
Maintain Business Event....................................................................................6
Maintain Check Mode.........................................................................................6
Maintain Check Instructions...............................................................................7
Maintain Requirements Profile..........................................................................8
Transportation and Shipment Scheduling.......................................................9
Interfaces............................................................................................................11
Maintain Transport Zone...................................................................................11
Define Assignment of Transportation Zones to Locations...........................11
Define Assignment of Default Vehicles to Shipping Conditions.................12
Perform Consistency Check............................................................................12
Perform Field Mapping for Scheduling...........................................................12
Maintain Weight Groups for Scheduling........................................................12
Maintain Volume Groups for Scheduling.......................................................13
Define Condition Table for Scheduling...........................................................13
Maintain Access for Scheduling......................................................................14
Maintain Control for Scheduling......................................................................15
Product Availability Check................................................................................15
Maintain ATP Group..........................................................................................15
Maintain Check Control....................................................................................16
Maintain Characteristics View.........................................................................16
Product Allocations............................................................................................17
Maintain Field Catalog......................................................................................18
Maintain Product Allocation Object.................................................................19
Maintain Product Allocation Group.................................................................19
Maintain Product Allocation Procedure..........................................................21
Maintain Sequence of Product Allocations Procedures..............................23
Maintain connection to planning area............................................................24
Check Settings for Product Allocation............................................................24
Rules-Based Availability Check.......................................................................25
Define Condition Table......................................................................................25
Maintain Access Sequences............................................................................25
Maintain Condition Type...................................................................................26
Maintain Rule Strategy.....................................................................................26
Assign Rule Strategy........................................................................................26
Tools....................................................................................................................27
Maintain Parameters for ATP Application Log...............................................27
Maintain Filter Type...........................................................................................28
Maintain Sort Profile..........................................................................................29

Maintain Special Sorting...................................................................................29

Generate Filter Type and Sort Profile.............................................................30
Enhancements...................................................................................................30
Maintain Enhancement Projects for Product Allocation..............................31
Set ATP Segment..............................................................................................32
Choose Substitutions........................................................................................32
Initialize ATP Controller.....................................................................................32
Set Location Alias..............................................................................................32
Check Existence of Location Alias..................................................................33
Determine and Evaluate Rules........................................................................33
Initialize Batch Backorder Processing............................................................33
Carry Out Filter for Batch Backorder Processing.........................................33
Sort for Batch Backorder Processing or CRM..............................................33
Define Scope of Check for Batch Backorder Processing............................33
Adopt Results in Batch Backorder Processing.............................................33
Define Backorder Processing Results Output..............................................34

Global Available-to-Promise (Global ATP Check)

The settings for global ATP are described in the following sections.

General Settings
You make the general settings relevant to Global ATP.
Dependencies of settings and their relationship to the OLTP system

Maintain Global Settings for Availability Check

In this IMG activity, you maintain the global settings for the availability check. Global settings include the
following:
Temporary quantity assignments : yes/no

Import Customizing data using the CIF integration model in the connected OLTP system:
allowed/not allowed

Note

We recommend that you transfer the Customizing data only once. If you
transfer the Customizing data more than once, the existing settings could be
overwritten.
We recommend that you carry out the availability check using temporary
quantity assignments. When you work with an R/3 System you should have
set the quantity lock in the R/3 System. This is necessary so that the ATP
check can deliver consistent results. If this lock is active, the material is only
locked at the time of the availability check when creating or changing a sales
document. It is thereby possible that several users can process the same
material at the same time within different operations without blocking each
other. For unlocking, APO can only call from the unlock routines in the
R/3 System. The quantity lock for the checking group in the R/3 System
is a necessary prerequisite for the ATP check in APO bringing
consistent results. If the quantity lock is not active in the R/3 System,
then unlocking cannot occur in APO. In the R/3 System you set the
quantity lock in Customizing for Sales and Distribution via Basic Functions
Availability Check and Transfer of Requirements Availability Check
Availability Check with ATP Logic or Against Planning Define checking
groups.
Requirements

Ensure that the ATP time series in Model Management and Version Management are
updated.
You can only set this indicator in the active model (000) and in an active version (000). You
cannot change this setting subsequently. To reset this indicator you must delete the active
version and recreate.
For further information see Creating model.
Make sure that the update of ATP time series is switched on. You set this indicator in Model and
Planning Version Management from the SAP Easy Access screen by choosing Master Data -> Planning
Version Management -> Model and Version Management.

Procedure
1. In Customizing for the Advanced Planner and Optimizer select Global ATP
General Settings Maintain Global Settings for Availability Check.
2. Set the Temporary qty asgmt indicator if you want to make it possible for several
users to check the same planning object simultaneously and, nevertheless, obtain
consistent results from the availability check.
3. Choose Import Customizing not allowed in the list field, if you want to prevent the
Customizing data from being overwritten by the APO Core Interface Model imports.
4. Choose Save.

Exemplo: You create an order for planning object 1 (location, product and account
assignment). Planning object 1 is then locked for the duration of the availability
check according to the setting. The quantity reserved for this operation is saved

as temporary quantity assignments in liveCache. These temporary quantity

assignments are taken into account in the checks of all other users who check
this planning object.
The lock is removed after the availability check has been carried out; the
temporary quantity assignments are reduced at the end of the LUW.

Maintain Category
In this IMG activity, you maintain the categories.
Example
"BM" stands for sales order, "BN" stands for SD scheduling agreement.
Activities
You can only create non-SAP categories using your own dialog. To create non-SAP categories, proceed
as follows:

1. You maintain the categories in Customizing for the Advanced Planner and Optimizer
via Global ATP General Settings Maintain Category.
You branch to the Change View "Maintain SAP Categories": Overview screen.
2.

Choose Non-SAP-categories -> New entries.

You branch to the details view.

3.

Define the category by entering a two-digit value. Note that the namespace "U" to "Z" is
reserved for this value. All values up to "U" are reserved for SAP categories.

4.

Enter a short and long text describing the category.

5.

Enter a value (maximum two-digits) for the sort string (or sort key). The sort string determines
the sequence in which the categories are taken into account by the system in the availability
check and in the display.

6.

Choose a category type using the input help (F4). The category type divides the categories into
the following types:
o Stock

Receipts

Requirements

Forecast

Only stock, receipt and requirement are used for product

availability checks.
7.

Set the corresponding indicator, if you want the category to be relevant on the sublocation level
only.
Note: A stock transfer reservation (category 'AO') between sublocations is only relevant on the
sublocation level. This category may not be taken into account on the location level
since no changes to the availability situation of the location result from a stock transfer
within a location.

8.

Save your entries

Maintain Business Event

In this step, you create a business event. The business event describes an operation within a
business. You define a business event for each business context.
Example
Incoming orders, sales and shipping
Activities

1. To maintain a business event in Customizing for the Advanced Planner and Optimizer
select Global ATP General Settings Maintain Business Event.
2. Choose New entries.
3. Enter a two-digit (maximum) alphanumeric value and a description (maximum 40
characters).
4. Choose Save.

Maintain Check Mode

In this step, you create the check mode.

The check mode, together with the business event, determines the type and scope of check
to be carried out. In addition, the check mode controls consumption using the forecast.
The check mode derived from the product master record and the business event determine
the type and scope of the checks to be carried out. In addition, the check mode controls
consumption using the forecast.
The SD (R/3) uses the requirements class of the requirement as check mode. As of R/3
Plugin 2000.1, the requirements class (via the strategy group in the material master) is
transferred to the location-specific APO product master (tab page ATP). No plausibility check
takes place.

Activities
1. In Customizing for the Advanced Planner and Optimizer select Global ATP
General Settings Maintain Check Mode.
2. Choose New entries.
You branch to the details view.
3. Create the check mode by entering a three-digit alphanumeric value.
4. Choose an Assignment mode, if you want the customer requirements to be
consumed against the forecast.
5. Choose a production type.
6. Enter a description (maximum 40 characters) for the check mode.
7. Choose Save.
Note: The check mode is equivalent to the requirements type with requirements class in R/3.
The requirements type with requirements class is transferred to SD during runtime. No
other applications transfer a requirements class. In this case, the check mode is read in
the APO product master. This is also the case for a rules-based ATP check for the
subsequent requirements (substitutions) Therefore, you should have entered the check

mode in the location-specific product master. To do this, choose Master Data -> Product
from the SAP Easy Access screen. Choose Location, enter the location product and
choose the ATP tab.

Maintain Check Instructions

In this step, you maintain the check instructions. You determine the following in the check instructions:
Basic methods to be executed

Neutral results check

Use of the Rules-based availability check

Immediate start of the rules-based availablity check

Remaining requirements

ATP alert

Start production

Definition of production times

Prerequisites

You created a business event.

You created a check mode.

Activities

Activities
1. You maintain the check instructions in Customizing for the Advanced Planner and
Optimizer via Global ATP General Settings Maintain Check Instructions.
2. Choose New entries.
You branch to the detail view.
3. Choose a check mode and a business event.
4. Determine the sequence of the basic methods by assigning the checking steps from 1
through 3.
You can switch off the availability check by setting No check for all basic methods.
5. Set the Neutral indicator, if the results of the corresponding basic method should
have no affect on the final results.
If the result of a "neutral result" basic method is smaller than the final result, a
message appears (or an alert appears that you can then process in the Alert Monitor).

If you have set the Neutral indicator for all basic methods, the final result is always
the complete requirement quantity.
6. Set the Rules-based ATP indicator, if a rules-based availability check should be
carried out for an order type.
7. Set the Start immediately indicator, if the rules-based availability check should be
started immediately.
8. Determine if and for which substitution in the rules-based availability check an
unconfirmed quantity should be created as the requirement.
9. Set the ATP Alert active indicator, if you want to display the possible shortage
situations in the Alert Monitor.
10. Choose the corresponding entry depending on if you want to execute production or
not.

If you want to configure Production direct, you must have activated the Availability
check with cumulated, confirmed quantities in R/3 Customizing in the checking group.
In R/3 Customizing for Sales and Distribution select Basic Functions Availability
Check and Transfer of Requirements Availability Check Availability Check with
ATP Logic or Against Planning Define Checking Groups.
11. Determine the production time.
12. Choose Save.

Maintain Requirements Profile

In this IMG activity you maintain requirements profiles.
Requirements profiles contain parameters at requirements level which are relevant to the availability
check, the transfer of requirements and for transportation and delivery scheduling. The requirements
profile is used for connection to external systems (for example, a CRM system) that do not transfer
these control parameters.
Requirements
You have maintained the following IMG activities
Maintain category

Maintain check mode

Maintain business event

To enter the rules strategy for location determination, you need to maintain the following IMG activities:
Maintain condition tables

Maintain access sequences

Maintain condition type

Maintain rule strategy

Create a rule with location determination procedure of procedure type 3 (= lists) in rules
maintenance.

You call up integrated rules maintenance from the SAP Easy Access screen by choosing
Master Data -> Rules Maintenance -> Integrated Rules Maintenance.
Standard Settings
If the system connected is a SAP CRM System, you should define an ATP profile and assign an item
type in CRM Customizing in Basic Functions -> APO Connection. The ATP profile in CRM must
correspond to a requirements profile in APO.
Activities
1. Define a key word for the requirements profile. This value is transferred to the connected
system (for example, to a SAP CRM System) during runtime.
2. Enter the relevant data.
Note that the activation parameter is intended for the execution of a rules-based ATP check in
the case of under confirmation (see replacement rule). In the case of an initial location
determination for a CRM system, these activation parameters are not required.
3. Save your entries.

Transportation and Shipment Scheduling

The automatic scheduling of shipment activities and transportation is possible in SAP APO.
Shipment Scheduling

In shipment scheduling, the system considers those operations necessary for initiating the
transportation of the goods. These include loading and picking/packing. The availability and
load dates are determined using shipment scheduling.
Transportation Scheduling
In transportation scheduling, the system considers all dates used for preparing and executing
the shipment. This includes the transportation lead time and the transportation duration. The
goods issue date is determined from the desired delivery date in transportation scheduling. If
the system performs forward scheduling, the possible delivery date is also calculated.
The following dependencies may arise for the Supply Chain Cockpit and Transportation
Planning or Vehicle Scheduling when the transportation duration is determined.
If the system does not determine the transportation duration using the transportation lanes and
vehicles maintained in the Supply Chain Cockpit, then the values in the conditions are used to
determine the transportation duration.
If no conditions have been maintained, the duration of the transportation is determined by
standard default settings with the help of an automatic calculation:
o Distance is determined as the crow flies from the location (geographical data: latitude
and longitude) of the vendor and the transportation zone (also contains a location) of
the ship-to party, taking account of the vehicle-dependent surcharge on the distance
(as the crow flies)

Average vehicle speed

The concepts used in scheduling are briefly defined below. A distinction is made between
Times (duration) that are required to perform certain activities.
In order to calculate scheduling, the system requires empirical values that you define in the
form of
o Planning preparation

Load time

Pick/pack time

Transportation duration

Duration of unloading and transfer (important for stock transfers) is not currently
supported.

In-house activities such as picking/packing and loading are calculated on the basis of the
shipping calendar entered in the location master.
Transportation activities are calculated on the basis of the transportation calendar to which a
transportation line is assigned. If no transportation lane is found, the system performs its
calculations without a calendar.
o Consideration of goods acceptance times

Goods acceptance times that can be predefined by an OLTP system, are supported
in SAP APO. If a SAP R/3 system is connected to SAP APO, and an unloading point is
used in the SAP R/3 document, the master data (calendar and goods acceptance
times) is taken into account in scheduling. If no calendar or goods acceptance times
are maintained in SAP R/3 for the ship-to party, the shipping calendar from the
location master for the restriction of goods acceptance times is used in SAP APO.
The dates calculated on the basis of these times include the

10

Availability date

Planning date

Load date

Goods issue date

Delivery date

Process Flow
During order entry, you can specify a desired delivery date for each item schedule line. The goods
should be delivered to the customer on this date. The system can automatically schedule when the
required shipment activities such as picking, loading, and transporting must be started in order for the
desired delivery date to be observed during order entry.
Scheduling is performed in a backwards direction using the desired delivery date as a basis. For this
reason, it is referred to as backward scheduling.
If the system establishes that the availability or planning dates are located in the past during scheduling,
it automatically performs forward scheduling in order to determine a confirmable delivery date.
The system first performs backward scheduling using the desired delivery date as a basis that looks like
this:
Desired delivery date - Transportation duration = Goods issue date

Goods issue date - Loading time = Loading date

Two further dates, the planning and availability date, are determined from the loading date
Loading date - Planning preparation time = Planning date

Loading date - Pick/pack time = Availability date

You define the type of transportation and shipment scheduling with the help of the condition technique.
The condition types are grouped in a scheduling procedure. The access sequence of the condition types
within the procedure is set. Note that the condition type UNLD is not currently supported. The
scheduling procedure is set in APO 3.0A.
The settings for transportation and shipment scheduling are described in the following sections.
Note
You can test scheduling directly from here.
Return ->
Application

Interfaces
The following section describes which settings you must make in the Customizing for interfaces to
ensure that shipment and transportation scheduling can be used as a central service in APO.
The following is performed in interfaces Customizing
Customizing entries of a calling or predecesor system are assigned to the corresponding
Customizing entries in APO

Customizing entries are checked for consistency particularly if they must also exist in a calling
or predecessor system, and not just in APO

Return ->
Application

Maintain Transport Zone

11

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
Considering the transportation zone of the ship-to party and further factors like, for example,
Country of origin and recipient country

Shipping conditions

Transportation group

the system automatically proposes a suitable route during sales order processing and outbound delivery
processing.
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.
Return ->
Application

Define Assignment of Transportation Zones to Locations

If you do not want to work with a ship-to party, for example, then you can use the transportation zones in
scheduling. To do this, define the assignment of transportation zones to locations.
Activities
Assign the transportation zone of the calling or predecessor system to a location.
Return ->
Application

Define Assignment of Default Vehicles to Shipping Conditions

In this IMG activity, you define the assignment of default vehicles to shipping conditions.
The vehicle is necessary to determine the transportation duration from the transportation lane. Assign a
default vehicle to the shipping condition.
Requirements
The shipping conditions must be maintained uniformly in all calling or predecessor systems.
Recommendation
We recommend that you create an entry with the shipping condition ' <SPACE>'; this is the default
vehicle in the event that no shipping condition was transferred.
Return ->
Application

Perform Consistency Check

With this IMG activity, you can check the Customizing entries which you have entered for the
transportation and shipment scheduling interfaces.
Further Notes
For more information, see Report Documentation.
Return ->
Application

Perform Field Mapping for Scheduling

12

You can perform field mapping in this IMG activity.

You can display the condition fields that are transferred in the interface table /SAPAPO/ATPFIELD on a
condition field of the /SAPAPO/KOMGU using the mapping table.
If it cannot be guaranteed that the fields of the interface table /SAPAPO/ATPFIELD from the OLTP
system can always be filled with values, and the fields for performing transportation and shipment
scheduling must be transferred to a condition table from /SAPAPO/ATPFIELD, you can specify several
source fields from /SAPAPO/ATPFIELD for a target field of /SAPAPO/KOMGU.
Example
The location is unknown in an OLTP system, and therefore cannot be transferred to the APO system. As
an alternative, the customer number can be transferred to APO and displayed on the LOCTO. In this
case, you can specify the field LOCTO as the target , and the field 'Customer number' as the source in
this IMG activity and thereby define a mapping of these two fields.
Further Notes
If you want to specify several source fields for a target field, you must use the assignment priority.
Return ->
Application

Maintain Weight Groups for Scheduling

In this IMG activity, you can assign a weight group to the gross weight of a document item. This is
necessary as the weight group, and not the weight, appears in /SAPAPO/KOMGU.
The weight groups that you define here do NOT overlap.
Example
You have created the following weight groups with a To-weight:
Group 1: ->10
Group 3: ->30
You add a new weight group.
Group 2: ->20
The values appear as follows before a new group is added:
Group 1: 0-10
Group 3: 10-30
The values appear as follows after a new group is added:
Group 1: 0-10
Group 2: 10-20
Group 3: 20-30
Recommendation
We recommend that you maintain a maximum weight group with the weight 9,999,999,999,000. This
enables you to subsequently add additional weight groups without any problems.
Activities
1. Define the display unit of measure (unit of measure for weight) for which you want to
maintain a weight group in the dialog. If you want to work with a standard unit of weight,
choose Cancel . If you want to work with a selected weight unit, choose a weight unit using the
F4 help and choose Continue.
2. Specify the gross weight and a weight group.
3. Save your entries.
Return ->
Application

Maintain Volume Groups for Scheduling

In this IMG activity, you can assign a volume group to the volume of a document item. This is necessary
as the volume group, and not the volume, appears in /SAPAPO/KOMGU.
The volume groups that you define here do NOT overlap.
Example
You have created the following volume groups with a To-weight:
Group 1: ->10
Group 3: ->30
You add a new volume group.
Group 2: ->20
The values appear as follows before a new group is added:

13

Group 1: 0-10
Group 3: 10-30
The values appear as follows after a new group :
Group 1: 0-10
Group 2: 10-20
Group 3: 20-30
Recommendation
We recommend that you maintain a maximum volume group with the volume 9,999,999,999,000. This
enables you to subsequently add additional volume groups without any problems.
Activities
1. Define the display unit of measure (unit of measure for volume) for which you want to
maintain a volume group in the dialog. If you want to work with standard units of volume,
choose Cancel . If you want to work with a selected volume unit, choose a volume unit using
the F4 help and choose Continue.
2. Enter the volume and a volume group.
3. Save your entries.
Return ->
Application

Define Condition Table for Scheduling

A condition table defines the combination of fields (keys) which identify an individual condition record.
The system stores specific condition data in a condition record which you enter in the system.
Example
For example, the condition table for planning could contain the following fields:
ALAND (Supplying country)

AZONE (Supplying transportation zone)

LLAND (Supplied country)

LZONE (Supplied transportation zone)

VSBED (Shipping condition)

The first four fields define a relationship between supplying and supplied locations, while the
last field defines the shipping condition.
Activities
1. Create a field catalog for scheduling.
By doing this, you define the fields that you can select when creating or maintaining a condition
table for transportation and delivery (usage "U") scheduling.
o Choose New Entries.

Generate the selection list using the F4 help.

Choose the fields you want to use as parameters in the condition tables by means of
a double-click.

Save your entries.

2. Create a condition table for scheduling.

o Enter the name of the table you want to create.

Specify whether you want to create the table with or without a validity period.

Specify a description for the condition table.

14

Choose the desired fields for the condition from the list of allowed fields in the field
catalog.

Generate the new condition table.

Return ->
Application

Maintain Access for Scheduling

In this step, you define access to the condition tables for transportation and delivery scheduling (usage
"U").
The access sequence controls the priority of the individual consition records. When the system is
accessed, it is informed where it should look for a valid condition record first and where it should look
subsequently. There is a defined access sequence for each condition type for which you create
condition records.
You should set the "exclusive" indicator when defining new accesses. This specifies that no condition
tables are evaluated after the first successful access.
Activities
1. Create an access.
o Choose an access sequence and choose Accesses.

Choose New Entries.

Choose the condition tables. Note that the sequence number may not be equal to 0.
Set the "exclusive" indicator for several accesses.

2. Maintain the fields.

o You can replace the value of the source field by a direct value.
3. Save your entries.
Return ->
Application

Maintain Control for Scheduling

You maintain scheduling control in this IMG activity. Because the scheduling procedure is firmly
configured, you can only exclude individual condition types before accessing the condition records.
Activities
1. Select the procedure and choose Control.
2. Exclude the desired condition type by choosing the entry 100 (exclusion) in the field
Condition.
3. Save your entries.
Further Notes
If you exclude the condition type TRAN by selecting the condition (100), transportation
scheduling takes place based on transportation lanes and locations.

The condition type UNLD is not currently supported.

Return ->
Application

Product Availability Check

15

The settings for the product availability check are described in the following sections.
Return ->
Application

Maintain ATP Group

In this IMG activity, you maintain the ATP group.
Activities
To create an ATP group, proceed as follows:
1. Enter a two-digit value.
2. Choose the corresponding entry in the Cumulation list field, if you want to use the shortage
check. For more information, see Example .
3. Determine the reaction to shortfall.
4. Enter a short description for the ATP group and save your entries.
Further Notes
Enter the ATP group in the location-specific product master. From the Easy Access screen, choose
Master data -> Product . Choose Location, enter a location product and choose the ATP tab.
The ATP group is read from the product master for the run time. The ATP group is equivalent to the
checking group in R/3.
Return ->
Application

Maintain Check Control

In this step, you define the check control for the product availability check. The check control consists
of the following:
check control

scope of check

Activities
To define the check control, proceed as follows:
1. Choose an ATP group and a business event.
2. Enter the data required to maintain the check control.
3. Save your entries.
To define the scope of check, proceed as follows:
1. Choose an ATP group and a business event.
2. Choose the categories that should be included in the product availability check.
3. Save your entries.
Return ->
Application

Maintain Characteristics View

In this IMG activity, you maintain the ATP characteristics view for a product availability check at the
characteristics level.
For the product availability check, currently, only the CDP characteristics ( characteristic-dependent
planning ) can be used in APO.
In the characteristics view, you group products together. You can use all the intersecting characteristics
for the characteristics-based product availability check.
In the characteristics view, you define the ATP-relevant characteristics.
Example
Product Characteristics Characteristics Characteristics
A
Color
Size
Length
B
Color
Size
C
Color
Size
You can use the intersecting characteristics, color and size, in the characteristics view.

16

Note
A product can only be assigned to one ATP characteristics view.
If you activate or deactivate an ATP characteristics view, no transaction data can exist in the liveCache
for those products in the characterisics view. The system checks for transaction data in the liveCache.
Depending on the result of the check, the system issues the appropriate error message.
During the activation or deactivation, no transactions data can be transferred from the OLTP to APO.
This is also valid for changes in the transaction data.
For the transfer from the R/3 system using the APO Core Interface, SAP recommends using separate
integration models for the master data and the transaction data.
An ATP characteristics view can only be deleted in the inactive status.
Activities
1. Create a characteristics view.
2. Determine a name for the characteristics view
3. Go to the Products subdialog. To group the products, select them.
The system only accepts products with characteristics. In the F4 value for the products, those
products with characteristics are selected.
4. When leaving the Products subdialog, the intersection of the characteristics to the selected
products is determined and entered in the subdialog's Characteristics screen.
5. If you want to change the automatic assignment of the characteristics, go to the
Characteristics subdialog. Here, you can remove the characteristic assignments.
Modify the ATP characteristics view
1. Select an ATP characteristics view
2. Go to the Products subdialog. Regroup the products by adding or deleting products from the
list.
The system only accepts products with characteristics. In the F4 value help for the product,
only those products that have characteristics are selected.
If the ATP charactersitics view is already active, only products can be assigned that already
possess assigned characteristics. An active product can only be removed if no transaction data
exists.
3. When leaving the Products dialog, only intersections for the characteristics and the selected
products are determined. Characteristics that have already been assigned, but are not included
in the new intersection, are automatically removed from the list. If characteristics have already
been assigned, no characteristics are added to the list automatically.
4. If you want to change the automatic assignment of characteristics, go to the Characteristics
dialog. Here you can remove the characteristics assignments.
5. Activate and save the characteristics view. You can also save the characteristics view
without activating it.
Delete ATP characteristics view
1. Select an ATP characteristics view.
2. If the characteristics view is active, deactivate it as the first step.
The characteristics view can only be deactivated if no transaction data exists in the liveCache
for the active products.
3. Delete the characteristics view.
4. Save your changes.
Return ->
Application

Product Allocations
Competitive order processing that aims to deliver the required quantity to the customer at the requested
time demands precise planning and control mechanisms. Unpredicatable problems, such as
breakdowns in production or increased demand, can lead to critical situations in order processing and
must be brought under control before they arise.
Product allocation offers a function that provides this sort of control, and enables your company to avoid
these critical situations in demand and procurement. An equal division of products in short supply must
be possible, as must speedy reaction to bottlenecks and changing market situations.
In the R/3 system, product allocations represent an ordered assignment of products to specific periods.
Product allocations can be created according to different criteria, for example customers or regions.
Function overview
The product allocation functionality combines planning tools with realtime ATP functionality. Info
structures have been partially replaced by the product allocation group. The product allocation group
defines a group of characteristics and is used for saving product allocation quantities and their
assignment.

17

Within the product allocation group, the planning hierarchy was replaced by the characteristics
combination. The characteristics combination contains the values of the characteristics from the current
sales order and corresponds to the lowest level of the planning hierarchy, in which all characteristics are
assigned.
Using a characteristics combination, a product allocation time series is selected in product allocations.
The check will be carried out against this time series. If the characteristics combination was defined, all
product allocation quantities can be planned (for example, from the market level right to the customer
level). An active check against product allocations by the sales order and an availability check are
carried out. Based on the check date (delivery date, goods issue date, product availability date), the
system ensures that the ordered quantity does not exceed the product allocation quantity. If the required
quantity exceeds the free product allocation quantity for the period, the system can suggest future
delivery dates as soon as the product allocation quantity is available. The incoming orders quantity is
updated for the product allocation quantity.
Analysis of the product allocation process
Before you define the processes and settings for product allocations, you must first analyze the
business process that is used as a basis. You should ask the following questions:
At what level should product allocations be set up?

for example, sales organization, customer, distribution channel

Are there unused quantities from earlier periods that could be taken for an availability check for
the current period? If so, what size is the consumption period? How many past and future
periods should be included in the current product allocations?

Should product allocations be carried out in one or several steps?

e.g. 1st step: Analysis of product allocation quantities at plant level

2nd step: Analysis of product allocation quantities at customer level
For consistent results (between the steps), we recommend that you combine the periods and
consumption intervals similar to those combined in the following example. Note that with each
step, the flexibility allocating products is further restricted.

The steps must be sorted in descending order - similar to a funnel - according to the length of
the consumption period. The periodicity is is insignificant.
Example for 01.01.98
STEP 1: PERIODICITY:
Monthly
CONSUMPTION PERIOD: From -1 to +3 (12/97-4/98)
STEP 2: PERIODICITY:
Weekly
CONSUMPTION PERIOD: From -2 to +5 (50/1997-6/1998)
STEP 3: PERIODICITY:
Daily
CONSUMPTION PERIOD: From -4 to +4 (12/27/97-01/05/98)
You can find the explanation for the calculation under Example .
For which period should the product allocation be active?
For example, 01.01.99-31.05.99.
Notes about planning
The infoCubes should have a similar structure to the product allocation groups. They can be structured
with more detail, but not with less.
Prior to planning, you should consider how the product allocation priorities are to be set, that is, which
characteristic combinations contain what percentage of the total product allocation quantity.
Return ->
Application

Maintain Field Catalog

In this step, you define the fields that you can choose when creating or maintaining a condition table.
Activities
1. Choose New entries.
2. Generate the selection list using the input help (F4).
3. Choose the fields that you want to use as parameters in the condition tables. These fields
are filled at runtime with the values from the sales order in the connected (calling) OLTP

18

system. You can also enter the data manually when simulating the rules-based availability
check in APO.
4. Save your entries.
Return ->
Application

Maintain Product Allocation Object

In this step, you define the product allocations object because product allocations are saved per
object for a characteristics combination in the product allocation group.
Prerequisites
The product allocations object is assigned to a product allocations procedure in the product
allocations control. This assignment is prerequisite for product allocations. To reflect a change in the
reason for product allocations, the product allocations object can be exchanged by the product
allocations control.
Activities
1. Choose New entries.
2. Specify the product allocations object by entering a key (maximum 18 characters) and a
description.
3. Choose Save.
4. Ensure that the product allocations object has been assigned to a procedure.
Example
The product allocations object could also display the following:
a product (personal computer) or a product group

a component (processor)

a season (summer, winter)

a production line

Return ->
Application

Maintain Product Allocation Group

You maintain the product allocation group in this step. A product allocation group defines a group of
characteristics. These characteristics come from the field catalog.
The product allocation group is used for saving product allocation quantities and their assignments.
Using a characteristics combination (the values of characteristics from the current sales order), a
product allocation time series, against which the check is executed, is chosen for product allocations. A
product allocation group consists of a period and the following:
Characteristics - information suitable for selecting a product allocation (for example, purchasing
organization or sales organization). The characteristic 'Product allocations object' must be the
first characteristic in each product allocation group.

Key figures - information that is saved for a combination of characteristic values. Key figures
are the product allocation quantity (the quantity offered in a period) and the incoming orders
quantity (the product allocation quantities of a period that have already been assigned). Key
figures are determined in APO and cannot be enhanced.

Maintain Product Allocation Group

The settings that you can make for the product allocation group include the following:
Communication structure
The communication structure determines the hierarchy level of the sales order (header, item or
schedule line), from which the check date is used for product allocations. Only the schedule
line level is currently supported.

19

Check date

The check date is the date on which checking is executed in product allocations. Possible
check dates include the product availability date, the goods issue date and the delivery date.
The check date is used for selecting periods with the product allocation quantities. The check
date is the start of the consumption period. The consumption period situation is determined
anew for each product allocations step of the product allocations procedure, and for the
schedule line of the sales order.
Time buckets profile

Indicator that specifies in which periods the key figures (quantities, product allocation quantities
or capacity) are copied (for example, daily, weekly, monthly posting periods).
Determine Characteristics
The product allocation is chosen by a characteristics combination. The values of the characteristics
combination are copied from the sales order to the availability check. If the characteristics combination
does not exist in the characteristics directory, the system searches for a collective product allocation
using the masking indicator. The structure /SAPAPO/KOMGO contains the maximum quantity of allowed
characteristics that can be used for rules-based ATP and for product allocations. The field catalog
includes the used characteristics.
Determine the Characteristics Sequence
The item determines the characteristics sequence in the product allocation group. The sequence is used
for displaying characteristics and for searching for collective product allocations. The characteristics are
displayed by item in ascending order. Characteristics without items are displayed in alphabetical order at
the end. Using the masking indicator, the characteristics are filled by item in reversed order when
searching for collective product allocations. Characteristics without items are not taken into account by
the system when searching for collective product allocations. The product allocations object must be the
first characteristic in the product allocation group. The product allocations object is not taken into
account by the system when searching for collective product allocations.
Determine Consumption Periods
Consumption periods consist of the number of past (backward consumption period) and future (forward
consumption period) periods:
Backward consumption period

The number of periods before the product allocations check date from the sales order that can
be used to calculate the current product allocation quantity. Unused product allocation
quantities in these periods are cumulated before checking product allocations for the current
period.
Forward consumption period

The number of periods after the product allocations check date from the sales order that can
be used for the current consumption period. The schedule lines with the confirmed quantities
are postponed by product allocations at the latest until the specified period. The period
category (day, week, month and posting periods) is defined in the settings for the product
allocation group. If you have set the Without past period indicator, product allocations from past
periods (before today) are not used - even if they lie in the consumption period.
Consumption periods can be used as follows:
Past periods Future periods Results
999
999
Unlimited consumption
999
0
Unlimited cumulation of unused quantities from past periods and
no future product allocation quantities
0
999
No cumulation of unused product allocation quantities
from past periods, unlimited future product allocation quantities.
This is an old product allocations method.
The functionality of the consumption period is not available for the old product allocations method.
Note
The check date and consumption period are determined per product allocation group. The product
allocation group can be used in different product allocations procedures, but the settings for
consumption always remain the same.
Activities
1. Choose New entries.
2. Enter a product allocation group.
3. Using the input help (F4), choose the communication structure. You can choose from the
following check dates:
o Delivery date

20

Product availability date

Goods issue date

4. Using the input help (F4), choose the time buckets profile.
5. The fiscal year is determined in the FY variant field. Using the fiscal year variant, you define
how many posting periods exist in a fiscal year, how many special periods you need, and how
the system should determine the posting periods when posting.
6. Choose F3. A message appears indicating that you need to check object validities when
changing the period category. You may ignore this message when creating a period category.
7. Choose Enter.
Note
When you save your entries in this step, a message appears indicating that errors have occurred when
generating internal objects. This message appears because you still have not maintained any
characteristics for the product allocation group. The product allocation object must always be the first
characteristic. Choose Enter.
8. Choose Characteristics.
9. Choose New entries.
10. Using the input help (F4), choose the characteristics and their sequence. Note that the
product allocations object must always be the first characteristic.
11. Choose Consumption period.
12. Choose New entries.
13. Using the input help (F4), choose the product allocation group and define the consumption
periods.
14. Save your entries.
Return ->
Application

Maintain Product Allocation Procedure

In this step, you define the product allocations procedure used for product allocations.
The procedure determines how products are allocated. Use the procedure as follows:
You must enter the product allocations procedure in the product master record (basic data
screen, general data). You can enter location- independent and location-dependent
procedures in the product master record. The location-dependent and location-independent
product allocation procedures control product allocations in the same manner. Entries are
made per location in the APO product master data screen.
In product allocations, you can use two different methods to consume order quantities against
product allocation quantities. Using the indicator for the product allocations method
(cumulated ), you determine which method is used. You have two options:
o Discrete check

If you do not set the indicator, the method for product allocations available since
Release 3.0F will be used (discrete ATP check).
Using this method, the quantity from the sales document is consumed against the
product allocation quantity. This is carried out on the basis of the product allocation
quantities for current and future periods only (unused product allocation quantities
from past periods are not taken into account).
Example
Product allocation quantities:
January February March April May
50
50
50
50 50
If an order is placed for 150 pieces on 01.03., the product allocations check proposes
50 pieces for March, 50 pieces for April, and 50 pieces for May. The quantities still
available in January and February are not taken into account by the system.
If you use this method, the product allocations counter, with which you can define
several product allocations steps with different product allocation groups, is not
available for product allocations. The only step value allowed for the hierarchy is 1.
Cumulated check (using ATP logic)

21

If you set the indicator, the product allocations method available since Release 4.0A,
which uses one of the corresponding ATP cumulated checking logics, is used. Using
the standard ATP checking logic, the quantity is consumed against the remaining
product allocation quantities still available. Unused product allocation quantities from
past periods are included in the calculation of the available product allocation quantity
for the current period.
Example:
Product allocation quantities:
January February March April May
50
50
50
50 50
If a customer places an order for 150 pieces on 01.03, the unused product allocations
from past periods (50 pieces for January + 50 pieces for February) are first cumulated
in the product allocations check. A total available product allocation quantity of 150
pieces is determined and confirmed by the system for the date.
Note:
In addition, the following additional product allocations functions are available:
Product allocations counter

Using the product allocations counter, you have the option of defining several product
allocation steps using different criteria. The final confirmed quantity is the minimum
quantity confirmed of the individual product allocations steps. Using this function, the
system carries out, for example, the following checks:
1. Step: Check the order quantity against the plant capacity for the relevant periods
Check the order quantity against the product allocation quantities allowed for
2. Step:
the customer
Consumption period

Number of periods before and after the checking period

A product allocation group, which determines the criteria for selecting the product allocation
time series, is assigned to the product allocations step in the sequence of product allocation
procedures.
Note
A product allocation group can be used for several product allocation procedures. All
procedures, which have been assigned to a product allocation group, must have the
same product allocation method. This means that a product allocation group supports
either a discrete, or a cumulated check. In addition, a product allocation group can
only be used once in a procedure.
You can specify a masking indicator for each product allocation group. The key for the general
entries (= collective product allocations) is created from the masking indicator. Using the
collective product allocation characteristics function, the characteristics directory can be
supplemented with the general entries. A default entry is thereby generated for each node in
the planning hierarchy (determined by the sequence).
Note
You must use the same masking indicator per product allocation group even if the
product allocation group has been assigned to different procedures. For multiple
assignments of a product allocation group, you can decide if a masking indicator
should be used or not. However, differing masking indicators are not allowed for the
same product allocation group.
Several objects with different validity periods can be assigned to the product allocations step.
The validity periods do not overlap. The relevant product allocations object is determined
based on the check date from the order. The characteristics combination with the saved
product allocations is determined using the product allocations object. The product allocations
check is not carried out in inactive validity periods. Nevertheless, in such instances, for
technical reasons involving the database, a product allocations object must be assigned even
though it is not taken into account.

Activities
To create a new product allocations procedure, proceed as follows:
1. Choose New entries.
2. Enter an alphanumerical key (maximum 18 characters) and an accompanying name for the
procedure.
3. If you have set the cumulated indicator, the standard product allocations method available
since Release 4.0A, which implements a cumulated ATP checking logic, is used. If you have

22

not set this indicator, the method available since Release 3.0F is used for product allocations
(discrete ATP check).
4. Ensure that the product allocations procedure has been entered in the product master
record.
To determine the step sequence, proceed as follows:
1. Choose Step sequence.
2. Choose New entries.
3. If you want the system to check product allocations in two or more steps, enter the
corresponding number and a name in the step field. Note that the step counter may not be
zero.
4. Using the input help (F4), choose the desired product allocation group and assign it to the
product allocations procedures.
5. Specify for which combinations you want to use the masking indicator. You can choose the
masking indicator using the input help (F4). The search for collective product allocations is
thereby activated.
To determine the control for product allocations, proceed as follows:
1. Choose Control.
2. Choose New entries.
3. Assign the product allocations objects to procedures by choosing the object using the input
help (F4).
4. Specify a validity period for each object.
5. Determine which assignments should be active.
6. Using the product allocations factor, you can display how the product allocation quantity is
consumed by the requested quantity of a sales order (for example, if the factor in a product
allocations period has been set to 2 and a sales order with 100 pieces is created, a product
allocation quantity of 200 pieces is than consumed by the sales order).
7. Save your entries.
Return ->
Application

Maintain Sequence of Product Allocations Procedures

With a sequence of product allocation procedures, several product allocations procedures are combined
into a specific sequence.
The sequence of product allocation procedures determines several alternative product allocations
procedures and their sequence for a product.
The list of product allocations procedures is used for product allocations in the availability check.
If the quantity cannot be fully confirmed in a product allocations procedure when checking, product
allocations is executed for the remaining quantity in the next product allocations procedure of the
sequence. The first product allocations procedure used is the product allocations procedure from the
product master record. All other procedures originate in the sequence of product allocations procedures.
If the product allocations procedure from the product master record reappears in the list, the system
ignores it.
Activities
1. Choose New entries.
2. Enter a procedure sequence and a name.
3. Choose Save.
4. Choose Procedure list.
5. Choose New entries.
6. Choose the product allocations procedures using the input help (F4).
7. Enter the sequence of the product allocations procedures.
8. Specify a procedure name.
9. Choose Save.
Further Notes
In addition to the product allocations procedure, the sequence of product allocations procedures is also
entered in the product master record.
You can enter location-independent as well as location-dependent sequences of product allocation
procedures in the product master record.
The sequence of product allocation procedures is only used as a supplement to the product allocations
procedure. If you do not enter a product allocations procedure for the product, the system ignores the
sequence of product allocation procedures, and product allocations is not carried out.

23

A sequence of product allocation procedures can be used - similar to the product allocations procedure for several products. The variety of products for which a sequence of product allocation procedures can
be used, does not have to cover products of a product allocations procedure.
Return ->
Application

Maintain connection to planning area

In this step, you maintain the assignment of the planning area to the product allocation group. You
must make this assignment because characteristics of the product allocation group have different
names from the info objects of the planning area.
All characteristics of a product allocation group must be assigned to an info object. Multiple info objects
can be assigned to one info object.
It is not always necessary to assign every info object to a characteristic. It is possible for aggregation
and disaggregation (depending on the direction of transfer) to take place with info objects that are not
assigned.
Requirements
You must have created a planning area and a product allocation group.
Activities
Assign a planning area to the product allocation group as follows:
1. Choose New entries.
2. Use F4 help to enter the product allocation group, the planning area, the planning version
and the indicator for the periodicities in the time buckets profile.
To assign a characteristic to an info object, proceed as follows:
1. Choose New entries.
2. Use F4 help to select the characteristic and info object.
To assign a key figure to an info object, proceed as follows:
1. Choose New entries.
2. Use F4 help to enter the key figure and info object.
3. Save your entries.
Note
Note the following when you use the recovery function: if you carry out the check against product
allocations directly in the planning area, you should choose a small enough interval for the checkpoints,
since the data in Demand Planning is lost during a recovery within this interval.
This also applies to the time series' that are used by product allocation in Demand Planning. The
changes to product allocations or the updated product allocation assignment can be lost within the
selected interval for the checkpoints during a recovery.
You can, however, check and adjust the product allocation assignment by choosing, from the Easy
Access menu, Global ATP -> Environment -> Product Allocations -> Repairs -> Product Allocation
Assignment Check.
If you want to avoid the behaviour described, you should not check directly against the planning area.
You can create a backup copy by transferring the data from the planning area to the InfoCube.
Return ->
Application

Check Settings for Product Allocation

In this step, you can check the consistency of the settings which you have made for each product
allocations procedure (determined in the product allocations control).
To restrict the scope of the check, specify the product allocations procedures.
Activities
1. Specify the product allocations procedure.
2. Choose Progam -> Execute.
3. You can branch to long texts in the check results list.
Return ->
Application

24

Rules-Based Availability Check

The settings for rules-based ATP are described in the following sections.
Return ->
Application

Define Condition Table

A condition table defines the combination of fields (key) that lable an individual condition record. The
system stores the specific condition data that you have entered in the system in a condition record.
Activities
1. Create a field catalog.
In this way, you define the fields that you can select for rules-based ATP (usage "O") when
creating or maintaining a condition table.
o Choose New Entries.

Generate the selection list using the F4 input help.

Choose the fields you want to use as parameters in the condition tables by means of
a double-click. These fields are filled with values from the calling OLTP system during
runtime.

Save your entries.

2. Create a condition table for rules-based ATP.

o Specify the name of the table you want to create.

Specify whether you want to create the table with or without a validity period.

Specify a description for the condition table.

Select the desired fields for the condition table from a list of the allowed fields in the
field catalog.

Generate the new condition table.

Return ->
Application

Maintain Access Sequences

You maintain the access sequence in this step. You determine the access sequences after you have
defined the required condition tables.
Using the access sequence, you determine:
which condition tables are used to access the condition records,

the sequence of these condition tables and

which field contents are used as criteria for reading them.

Activities
To create an access sequence, proceed as follows:

25

1. Define an alphanumeric key (maximum four-digits).

2. Define the accesses by defining the access sequence and choosing the corresponding
condition tables. If, after the first successful access, you do not want the system to evaluate
additional condition tables, set the exclusive indicator.
3. You can enter a direct value in the fields view so that the system overwrites the value that is
copied from the calling application. You can set an initial indicator for the rest.
4. Save your entries.
Return ->
Application

Maintain Condition Type

In this step, you maintain the condition type and assign it to an access sequence.
Condition types are used for determining rules in the rules-based availability check.
Activities
To create a condition type, proceed as follows:
1. Define an alphanumeric value (maximum four-digits) and specify a name.
2. Assign an access sequence to the condition type by choosing an access sequence using the
input help (F4).
3. If necessary, specify a validity period that is proposed in the rule determination.
4. Save your entries.
Return ->
Application

Maintain Rule Strategy

In this step, you maintain the rule strategy. The rule strategy determines the condition types and
defines the sequence in which they are evaluated.
Activities
To create a procedure, proceed as follows:
1. Define an alphanumeric value (maximum six-digits) and specify a name.
2. Determine the rule strategy control by choosing condition types and determining the
sequence in which they are evaluated.
3. Save your entries.
Return ->
Application

Assign Rule Strategy

In this IMG activity, you determine the following activation parameters to determine the rule strategy:
technical scenario

business transaction

action type

Activities
1. Create three activation parameters.
2. Choose the rule strategy.
3. Specify how several calculation profiles, which are derived from successive accesses,
behave. You determine if a subsequent calculation profile overwrites or supplements the
previous calculation profile.
4. Save your entries.
Return ->
Application

26

Tools
The following sections describe the settings for the tools for checking availability. Backorder processing
is a component of these tools.
Return ->

Maintain Parameters for ATP Application Log

In this IMG activity, you maintain the parameters for the ATP application log. You also switch on the ATP
application log here.
Make sure that you use the OLTP user name to switch on the log when calling APO from a linked OLTP
system.
Log on

Switches on the writing of the log.

Note
Switching on the log has a negative impact on the performance of the availability check.
Display direct

If the Direct display indicator is set, a log is displayed in a dialog box for messages from
particular application classes that are reached in the program code. The application classes,
for whose messages a log display should be created immediately, can be selected at the start
of the log in a dialog box.
In the dialog box for the log display, the program continues to run until the next message, if you
confirmed with Enter in order to display the log again.
If you choose Switch on debugging, debugging is switched on (assuming you have the
apporpriate authority); that is, after exiting the display log, the program sequence is continued
in the debugger.
If you want to switch off the message display, choose the Switch off message display
pushbutton. When you have selected the pushbutton and confirmed using Enter, the check
runs without any further message display.
Action at log end
The indicator determines which action should be carried out automatically after the log has
been created and exited. The following options exist:
o Log remains in the main memory without any particular action

After the end of the log, nothing happens. When the calling transaction has ended and
the main memory has been released, the log disappears.
Display log

The log is displayed at the end. The log is displayed only in the dialog transactions,
not in batches or asynchronous RFCs. The log disappears after the main memory has
been released.
Save log to database

The log is written to the database at the end and can later be displayed and deleted
again.
Display log and save to DB

The log first can be displayed and then saved to the database. If the log cannot be
displayed because the user is not in the dialog transaction, the log is still saved to the
database.
Initialize log in main memory
The log is initialized in the main memory, that is, all messages in the log are deleted.
However, the log header continues to exist. Initializing is helpful when several LUWs
are executed one after the other within a transaction (for example, T-Code VA01),

27

without the main memory being released (for example, when several orders are
created within the VA01).
Display log and then initialize in the main memory

First the log is displayed (only dialog transaktion) and then initialized.
Save log to DB and then initialize in the main memory

First the log is saved to the database and then initialized.

Display log, save to DB and then initialize in the main memory

First the log is displayed (only dialog transaktion), then saved, and finally initialized.
C-trace availability check
If you set this indicator, a log file for the product availability check in liveCache (in C++
code) is also created. A corresponding message about the creation of this file is written to the
application log. The C-trace file is displayed immediately by selecting the detailed information
about this particular message.

Note
If too many messages are displayed, the system performance can rapidly get worse.
Activities
1. Enter your user name.
2. Set the corresponding parameters.
3. Save your entries.
Return ->
Application

Maintain Filter Type

In this step, you define a filter type . In a filter type, you define which characteristics can be used in a
filter for backorder processing.
Activities
1. Define a filter type.
2. Specify the order categories for which the filter type should be used.
3. Choose the characteristics of the filter type from the template structure.
If you have specified several order types, you can only select the intersection of the usable
characteristics as these characteristics must occur in each order category.
4. A report for the filter is generated from the filter type. The filter itself can be stored as a
variant for the selection screen of the generated report. Generate the filter type using Tools ->
Generate Filter Type and Sort Profile.
Generation is only necessary if errors occur during transports to Customizing. Normally, filter
types are generated automatically. The variants you have maintained up to now are not lost if
only minor changes were made to the filter type.
Further Notes
Filter types are delivered for filtering using alerts and netchange selection.
Return ->
Application

Maintain Sort Profile

In this step, you define a sort profile for backorder processing. You define the processing sequence for
order items in backorder processing with specifications in the sort profile. You specify characteristics,
their sequence (or weighting), and the sort order in this profile.
You can choose all characteristics from the template structure, and can also specify for each
characteristic whether it should be sorted in ascending or descending order. Special sortings (for
example, non-alphabetical) can be used for some characteristics.
Sorting results in a priority for the documents in backorder processing.
Activities
1. Create a sorter.
2. Define the details of the sort profile.

28

Choose the characteristics.

Define the order (weighting) according to which order items should be sorted in
backorder processing by fixing the item.

Define whether sorting should be performed in ascending or descending order, or

whether sorting should be performed with special sorting.

You define special sorting using Tools -> Maintain Special Sorting.
3. Save your entries.
4. Generate the sort profile using Tools -> Generate Filter Type and Sort Profile.
Generation is only necessary if errors have occurred during transports to Customizing. Sort
profiles are normally generated automatically.
Return ->
Application

Maintain Special Sorting

In this step, you maintain a particular sorting for the special sorting in the sort profile. Sorting ensures
that order items are arranged in a processing sequence for backorder processing (priority assignment).
Example
You define a special sorting for the criterion 'sales document category' in the sort profile:
Item Sales document category
1
Order
2
Quotation
3
Query
Activities
1. Select a selection criterion by means of a double-click and choose New Entries.
2. Define the item and choose the desired entry
3. Save your entries.
Return ->
Application

Generate Filter Type and Sort Profile

In this step, you can perform the generation of a filter type and a sort profile. Manual generation is not
normally necessary. If the Customizing settings are changed, the filter type and sort profile are
subsequently regenerated if required.
If you have transported Customizing settings for backorder processing, it may be necessary to generate
coding for either the filter type or sort profile.
Further Notes
If existing filter types are regenerated, previously defined filter variants can be deleted.
Return ->
Application

Enhancements
The SAP enhancement concept allows you to use function exits to enhance individual functions in the
SAP standard systems that cannot be adapted by means of the Customizing functions, and to tailor
them to meet your requirements using 'SAP enhancements'.
An SAP enhancement consists of at least one component. A distinction is made between the different
kinds of components (for example, function exits, screen areas).
In contrast to modifications, enhancements are basically compatible with all release levels, as they are
not incorporated in the original SAP System, but exist in a name range that is reserved for customers.

29

In the Customizing activities below, you have the option of compiling the SAP enhancements relevant to
your business in enhancement projects, editing the enhancement components, and finally activating the
enhancement projects. Enhancements are only visible once activation has taken place in the
corresponding transaction.
Note
Once an SAP enhancement has been allocated to a project, you can no longer use it in another project.
Activities
1. First check the functionality of the standard functions.
2. If the functionalities necessary for your business are not covered by the Customizing
functions, you can then use the transaction CMOD to develop the functional enhancements.
To do this, proceed as follows:
a) In the Project field, specify a name for your enhancement project.
b) Choose Project -> Create.
c) Enter a short description for your project.
d) Save the attributes (maintenance info) for the project using Attributes -> Save.
e) Choose the function Goto -> SAP enhancements.
f) Enter the name of the SAP enhancement that you would like to edit in the
Enhancement field.
You can find the names of the SAP enhancements in the corresponding
documentation in the Implementation Guide.
You can combine several SAP enhancements to make an enhancement project.
To display the SAP documentation on an SAP enhancement, place the cursor on the
name of this SAP enhancement and choose SAP enhancements -> SAP
documentation.
g) Save your entries. Return to the initial screen.
h) Select the sub-object Enhancement components.
i) Choose Change.
The system now displays the SAP enhancements you specified along with the
accompanying components.
j) Place the cursor on the name of the component (for example,
EXIT_SAPLRSTH_001) that you want to edit and choose Edit ->Component.
You branch to the ABAP/4 Editor (function module display).
k) When you double-click on the INCLUDE line, the system will ask you to create the
object INCLUDE.
If you have already created this object, then double-click to branch directly to the
ABAP/4 Editor (program display).
This is where you can store your own coding.
l) If you have not yet created the object, you first need to specify the program
attributes.
m) Save the program attributes. Choose Goto -> Source text.
You branch to the ABAP/4 Editor.
n) Enter the coding for your program.
o) Save the program.
p) Return to the initial screen.
q) Activate the project via Project -> Activate project.
Your enhancement only takes effect once it has been activated.
Further Notes
Detailed information about developing functional enhancements is available in the documentation on
enhancing SAP transactions. You can find it by branching from the intitial screen via Tools -> Online
Handbook.
Return ->
Application

Maintain Enhancement Projects for Product Allocation

In this IMG activity, you can edit customer exits for the global availability check.
Product allocations
The enhancement for the initialization is APOQT001 .
The user exits for product allocations are divided into two different call sequences:
Product allocations is the requirements check against the product allocation time series from
planning. A complete check is executed for this call sequence.
The enhancements for product allocations are:

APOQT010 copy parameters

30

APOQT012 product allocations control

APOQT021 product allocations

APOQT022 consumption at beginning situation

APOQT023 order consumption

APOQT032 results control

APOQT033 sequence of product allocation procedures

APOQT007 product allocation assignment of partial deliveries

APOQT018 adjusting field catalog

The comparison adjusts the results of product allocations to the results of the other basic
methods. This adjustment is necessary when product allocations is not the last basic method
executed.
The enhancements for the comparison are:

APOQT011 copy parameters

APOQT014 product allocations control

APOQT024 consumption

APOQT034 results control

APOQT035 sequence of product allocation procedures

The sequence of the basic methods is configured in the check instructions.

When comparing, the entries in the table for the product allocation assignment and the temporary
quantity assignments (delta records) are adjusted to the final results of the ATP check.
If the behavior of product allocations is changed by the user exits, the behavior of the comparison must
be adapted accordingly in the corresponding user exits!
Return ->
Application

Set ATP Segment

You can set the ATP segment using the customer exit APOAT001.
You will find additional information
In the documentation for the customer exit APOAT001

In the function module documentation for EXIT_/SAPAPO/SAPLATPT_001

Return ->
Application

Choose Substitutions
You can select replacements in rules-based ATP using the customer exit APOAT002.

31

You will find additional information

In the documentation for the customer exit APOAT002

In the function module documentation for EXIT_/SAPAPO/SAPLATPT_002

Return ->
Application

Initialize ATP Controller

You initialize the ATP controller using the customer exit APOAT003.
You will find additional information
In the documentation of the customer exit for APOAT003

In the function module documentation for EXIT_/SAPAPO/SAPLATPT_003

Return ->
Application

Set Location Alias

You can set a location alias using the customer exit APOAB004.
You will find additional information in the documentation for the customer exit APOAB004.
Return ->
Application

Check Existence of Location Alias

You can perform a check for the existence of a location alias using the customer exit APOAT004.
You will find more information
In the documentation for the customer exit APOAT004

In the documentation for the function module EXIT_/SAPAPO/SAPLATPT_004

Return ->
Application

Determine and Evaluate Rules

You can determine and evaluate rules using the customer exit APORB001.
You will find additional information in the documentation for the customer exit APORB001.
Return ->
Application

Initialize Batch Backorder Processing

Using this customer exit you initialize backorder processing (batch). For additional information see
the documentation on the customer exit APOBO000.
Return ->
Application

32

Carry Out Filter for Batch Backorder Processing

Using the customer exit APOBO010, you can perform filtering for backorder processing. You will find
additional information in the documentation on the customer exit APOBO010.
Return ->
Application

Sort for Batch Backorder Processing or CRM

Using the customer exit APOBO020, you can perform sorting for backorder processing in the
background or for a CRM system. For more information, see the documentation on the customer exit
APOBO020.
Return ->
Application

Define Scope of Check for Batch Backorder Processing

Using the customer exit APOBO040, you define the scope of check for backorder processing in the
background. For more information, see the documentation on the customer exit APOBO040.
Return ->
Application

Adopt Results in Batch Backorder Processing

Using the customer exit APOBO050, you can perform results transfer in backorder processing in the
background. For more information, see the documentation on the customer exit APOBO050.
Return ->

Define Backorder Processing Results Output

Using customer exit APOBO100 you can define the results output of backorder processing. For
further information see the documentation on the customer exit APOBO050.
Return ->
Application

33