6/26/2019

Advanced Available-to-Promise (aATP)

Generated on: 2019-06-26

SAP S/4HANA | 1709 001

PUBLIC

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not reect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the SAP Help Portal.

Portal .
6/26/2019

Advanced
Advanced Avai
Availa
lable-to-
ble-to-Pr
Prom
omise
ise (aA
(aATP)
TP)
Advanced Available-to-Promise (ATP) is a business function in SAP S/4HANA that provides a response to order fulllment
enquiries in Sales and Distribution (SD) and Production Planning (PP). The order fulllment enquiries consist of required
materials and plants, as well as their respective requested quantities and dates. The result of the ATP check is based on the
current stock situation and any future, anticipated or planned stock receipts and takes concurrent orders into account.
Furthermore, additional restrictions based on any other order attributes (like region or customers) can be applied. The ATP
function generates conrmation proposals for the requested material and plant, including conrmed quantities and dates.

For more information about advanced Available-to-Promise (aATP) in SAP S/4HANA, see:

Product Availability Check (PAC)

Product Allocation ( PA
PAL)
L)

Backorder Processing (BOP)

Supply Assignment (ARun)

Produc
Productt Avai
Availa
labili
bilitty Check (P
(PA
AC)
You can use the product availability check to determine on which date and in which quantity a particular requirement (for
example, a sales order item) can be fullled. The result of the product availability check is a conrmation.

Scope of check

You can control which document types and stocks (for example, sales orders and stock in transfer) are considered by the
product availability check to calculate the available quantity for the requirement (for more information, see Calculation
of Available Quantities).
Quantities). If a requested quantity cannot be conrmed on the requested delivery date, the system
calculates following Delivery Options.
Options. For more information on the scope of check, see Availability Check Control.
Control.

Scheduling

To determine
deter mine the e arliest conrmed date on which the require ment can be fullled, the system performs backward and
forward scheduling, starting from the delivery date originally requested by the customer. When doing so, scheduling
considers the lead times for picking and packing, loading, and transportation that you have maintained in Customizing.
For more information, see Scheduling
Scheduling..

Check levels

When calculating a conrmation, the product availability check veries if a requirement already exists and to which level
(plant, storage location and batch) it is assigned. In addition, the product availability check considers other existing
document types and stocks. For more information, see Check at Storage Location and Batch Level.
Level .

Replenishment lead time

If the requested quantity is not available yet, the product availability check uses data from in-house production or
external procurement and creates a conrmation for a date after the replenishment lead time. For more information,
see Replenishment Lead Times.
Times.
6/26/2019

requirements. For more information, see Temporary Qua ntity Assignments

Assignments..

Delivery group
gr oups
s

If you are working with a delivery group (multiple items that require a single delivery date), the product availability check
calculates one common date for all requirements in the delivery group.

The following table shows the availability of individual features per application:

Featu r es Sales an d Production Lo gistics Ex

Execu tion Pu r ch asin g Go o ds Mo
Mo vemen ts
Distribution Planning

Scop e of check X X X X X

Delivery op tions X - - X -

Schedul ing X - - X -

Check levels X X X X X

Temporary quantity X X X X X
assignments

Delivery group s X - - - -

Availability
ailability Check Control
The availability check control denes which document types and stocks are taken into account by the product availability check,
as detailed in the following list:

The product availability check can be congured to consider the following document types:

Purchase orders

Purchase requisitions

Dependent requirements

Reservations

Sales requirements

Deliveries

Shipping notications

Dependent reservations

Release order requirements

Planned orders

Production orders

Unrestricted-use stock is always considered in the product availability check. The product availability check can be
congured to include or exclude the following stock types:

Safety stock
6/26/2019

Blocked stock

Restricted-use stock

Subcontractor stock

In addition, the availability check control is used for the following:

Dening the number of days in the future for which the system checks for missing parts during goods receipt posting in
Inventory Management

Receipts in past

Deactivating checks at storage location level

Replenishment lead times (for more information, see Replenishment Lead Times)

Scheduling
The product availability check supports the following two scheduling scenarios:

1. Backward scheduling

2. Forward scheduling

Backward scheduling is executed to calculate the date on which a material must be in stock to enable an on-time delivery for
the requirement. This date is calculated backwards from the requested delivery date and takes factory calendars into
consideration. First the transport time is subtracted to determine t he goods issue date (the date on which the transport has to
start). The loading time is then subtracted from the goods issue date to determine t he loading date (the date on which the
goods have to be ready for loading). Based on the loading date, the following two dates are calculated:

Material availability date

The material availability date is calculated by subtracting the picking and packaging time from the loading date.

Transportation planning date

The transportation planning date is calculated by subtracting the transportation planning time from the loading date.

If the material availability date or transportation planning date is in the past, the system does not conrm the requirement for
the requested delivery date. Instead, the system runs forward scheduling and determines the earliest date for which the
requirement can be conrmed. The latest material availability date and transportation planning date are calculated to keep the
material availability date as close as possible to the conrmed delivery date, as illustrated in the following gure:
6/26/2019

If, for example, the transportation planning date is signicantly earlier than the material availability date, and it is also in the
past, the system performs a new forward calculation. The system sets the earliest date to today and calculates the earliest
delivery date for the conrmation. In addition, the latest material availability date is calculated.

Segmentation
When you run an availability check at the time of order entry, the system checks whether a requirement (a specic material or
product) can be fullled by the requested delivery date. Segmentation can be used to order certain materials or products by
logically categorizing them based on specic criteria or characteristics (for example, color or size.) If the requirement is
relevant for segmentation, you can use segmentation to assign the supply to the requirement. The assignment of the
requirements to the supply (or the supply to the requirement) is determined according to the mappings dened for the
requirement or stock segments in Customizing. Multiple requirement segments can be assigned to a single stock segment.

For more information, see Demand and Supply Segmentation.

Temporary Quantity Assignments

6/26/2019

quantity for competing requir ements. Temporary quantity assignments create d during online processes (for example, sales
order creation) are valid for eight hours and are removed automatically by the system in the following situations:

A document is saved.

An unsaved change in a document is discarded.

A newly created document is canceled.

Temporary quantit y assignments are invalidated by time-outs when t echnical problems prevent the process from ending as
intended.

If an online availability check ends unexpectedly (for example, due to a system dump), temporary quantity assignments
generated during the availability check remain in the system for the duration of their lifetime and block the material quantity in
the temporary quantity assignments from being used by other availability checks. When the next online availability check is run,
a clean up routine is called and locates all invalid temporary quantity assignments. The invalid temporary quantity assignments
are subesequently deleted.

Note that temporary quantity assignments created during availability checks involving the Release for Delivery app are not
deleted automatically and require manual deletion with report ATP_TQA_PAC_DEL_DISPLAY Deletion of TQAs from ATP 
Check . If the temporary quantity assignments are not deleted manually, they will expire after the validity time frame.

When a process after an availability check is terminated unintentionally and unexpectedly, temporary quantity assignments
generated during the availability check remain in the system for the duration of their lifetime and block the material quantity in
the temporary quantity assignments from being used by other availability checks. After their lifetime has been exceeded, the
temporary quantity assignments are deleted automatically when the next availability check is executed.

Report ATP_TQA_PAC_DEL_DISPLAY Deletion of TQAs from ATP Check  can be used to delete temporary quantity
assignments. When the report is executed, all temporary quantity assignments that fulll the selection lters will be deleted.
The following selection lters and settings can be specied before the report is executed:

The is the transaction ID of the termina ted processes.

A user and/or a date range for the creation date of the te mporary quantity assignments

A material and/or plant

A minimum and maximum validity date for the temporary quantity assignments

If the ag is set before the report is executed, the system displays the temporar y quantity assignments to
be deleted. They can be selected and deleted individually.

If the ag is not set before the report is executed, the system only conrms the number of temporary
quantity assignments that have been deleted.

Proceed as follows to use report ATP_TQA_PAC_DEL_DISPLAY:

1. Enter t he user name for the user t hat t riggered the generation of the invalid TQAs.

2. Set the ag.

6/26/2019

Manage Product Allocation Planning Data

Manage Product Allocation Sequences

Backorder Processing (BOP)

Backorder processing can be used to check material availability when the demand or supply situation in your order fulllment
process has changed and you want to check if previously calculated conrmations for sales orders or strock transport orders
are still realistic. For example:

A sales order is canceled, thereby freeing up stock quantities.

An important customer increases the requested quantity for a material and would therefore like to consume stock which
is currently conrmed for other sales orders.

A production order providing planned supply is running late.

Not reacting to the changed availability situation can result in conrmed quantities exceeding available quantities. This can
result in availability checks for over-conrmed materials failing, leaving you unable to release materials for delivery creation.

Advanced Available-to-Promise in SAP S/4HANA offers three apps for setting up automated backorder processing for
requirements items in sales orders and stock transport orders. Each app contains Web Assistant documentation that provides
additional information on key on-screen elements and concepts used:

App name Congure BOP Segment Congure BOP Variant Monitor BOP Run

In addition, the Schedule BOP Run app can be used for scheduling backorder processing runs to execute interactively or as a
background job.

Items are excluded from backorder processing in advanced Available-to-Promise if:

The item does not belong to a checking group or if the checking group is not congured for advanced product availability
checks.

The requirements class to which an item belongs is empty or is not congured for product availability checks, including
product availability checks against product allocation.

The schedule line category to which an item belongs is empty or is not congured for product availability checks,
including product availability checks against product allocation.

The ag is set in the sales order document.

The Advanced ATP functions have not been activated in Customizing.

The functions for backorder processing in advanced Available-to-Promise are dependent on the SAP HANA Rules
6/26/2019

Conguring SAP HANA Rules Framework

Congure SAP HANA Rules Framework (HRF).

Some of the apps for backorder procssing (BOP) in advanced Available-to-Promise (aATP) are reliant on lter rules being
congured so that, for example, requirements can be identied and responsibilities dened. SAP HANA Rules Framework (HRF)
must be set up in your system to enable you to create the lters required by the apps. For more information on HRF, see SAP
HANA Rules Framework - Installation & Upgrade Guide . SAP Note 2400537 describes the activities required to congure HRF
for aATP.

Report ATP_BOP_SYSTEM_CONFIG can be used to set up HRF. The report automates:

The creation of the SAP HANA database (HANA DB) user for accessing the HRF compilation service.

The assignment of the appropriate role to the HANA DB user with authorization to access the HRF compilation service.

The setup of an RFC destination on the ABAP server to enable access to SAP HANA Extended Application Services
(HANA XS).

The following prerequisites must be fullled before you can use report ATP_BOP_SYSTEM_CONFIG:

SAP HANA Rules Framework 1.0 SP09 (or higher) must be installed in your system.

To congure the setup of HRF, a HANA DB user with administra tor aut horization is re quired, the logon credent ials of
which must be entered while executing the report.

The user executing the report must have authorization to create an RFC destination

The HANA DB user with administrator authorization must have, at least, user administrator privileges (system privilege:
USER ADMIN) and role assignment privileges (object privilege: EXECUTE for GRANT_ACTIVATED_ROLE)

Note
The above prerequisites are checked upfront and the setup run is only started if the prerequisites are met.

Report ATP_BOP_SYSTEM_CONFIG can be executed in three ways:

Execution Mode: Purpose: Note:

6/26/2019

Execution Mode: Purpose: Note:

Check HRF Conguration You are not required to provide HANA DB

Checks the conguration settings
administrator user credentials before using
for HRF but does not actually set up
this execution mode.
the HRF conguration.

Checks if, for example, the RFC

destination exists and can be
reached and if SAP HANA XS and
the compilation service in SAP
HANA XS can be accessed and
used.

Set Up HRF Conguration You are required to provide HANA DB

Congures HRF for active use.
administrator user credentials before using

Creates the SAP HANA database this execution mode.

user.

Assigns the required role

Congures the RFC destination.

Renew HRF Role Assignment Checks if the appropriate role is assigned You are required to provide HANA DB
to the HANA DB user administrator user credentials before using
this execution mode.

When the report is executed, a log displays upon completion and provides information about the processes triggered by the
selected execution mode. In addition, the log lists any issues detected when the report is executed.

SAP Note 2400537

Key Concepts in Backorder Processing

The following concepts are used extensively in backorder processing in advanced Available-to-Promise:

Term: Denition:

BOP Abbreviated form of backorder processing

Requirement A requested quantity of a certain material on a certain date, for

example, a line item in a sales order

Conrmation Promised delivery date and quantity, resulting from an availability

check being executed for a requirement

Availability check An SAP functionality that calculates a possible conrmation for a

requirement, for example, from a sales order line item, depending
on the scope of check dened in Customizing at
6/26/2019
are selected and the sequence in which the requirements are
prioritized. BOP segments are maintained in the Congure BOP
Segment app.

Prioritizer Denes the priority with which the requirements in a BOP segment
are handled. Prioritizers are congured in the Congure BOP
Segment app.

BOP variant A saved selection of settings that determines which requirements

are included in a BOP run and how they are checked. A BOP variant
is used to schedule a BOP run. BOP variants are maintained in the
Congure BOP Variant app.

Conrmation strategy Denes how a requirement is handled in a BOP run. Each

requirement in a BOP run is assigned to one of ve potential
conrmation strategies. The assigned conrmation strategy
determines who receives availably quantity  rst. Conrmation
strategies are assigned in the Congure BOP Variant app.

Global segment A BOP variant can have an optional lter which denes the overall
set of requirements to be processed. Global segments are
maintained in the Congure BOP Segment app and assigned in the
Congure BOP Variant app.

Exclusive global segment Unlike an inclusive global segment, the remaining subset of
requirements is ignored. The global s egment is applied to each
BOP segment denition of the applicable BOP variant and restricts
their selection of requirements even further.

Remainder requirement group A set of requirements selected by a global segment but which are
not selected by any other lter/part of any other BOP segment.

BOP run An executed instance of the background functionality that checks

the availability of multiple requirements at the same time, in a
dened sequence and taking any lters into consideration, as
dened in the BOP variant. A BOP run can be simulated or
scheduled for immediate execution in the Congure BOP Variant
app or scheduled as a one-time or regular background job in batch
mode in the Schedule BOP Run app.

Business scenario A rule that denes how the availability check with BOP is executed.

Conrmation Strategies
Conrmation strategies are used in backorder processing to dene and prioritize how individual requirements are handled in
BOP runs when availability is limited. They can lead to requirement quantities being conrmed earlier, later, partially or not at
all.

In the Congure BOP Variant app, you can:

Assign conrmation strategies to BOP segments.

Assign multiple BOP segments to a single conrmation strategy in a BOP variant.

Conrmation Processing Denition: System Behavior:

Strategy: Priority:
6/26/2019
requested material available date is in the not updated. All other sales order documents for
past). the same material-plant combination are also not
updated.

Gain 3 Assigned requirements retain, at least, their If current conrmations cannot be retained, the
conrmation or, if possible, improve. BOP run stops immediately and an alert is
raised. When this happens, all requirements for
the same material-plant combination are
excluded from the BOP run.

Redistribute 4 Assigned requirements can get a better, equal BOP may release quantities of requirements so
or worse conrmation. that they can be used to fulll requirements with
higher priorities. BOP may produce a worse
conrmation when requirements with a higher
priority have reduced the available quantity.

Note that the Restribute   conrmation strategy is

the only strategy currently supported by product
allocation (PAL).

Fill 5 Assigned requirements do not gain additional To conrm requirements from Win   and Gain ,
quantity or get an earlier conrmation date. BOP releases quantities of requirements
They get an equal or worse conrmation. assigned to Fill . This can results in a later
conrmation or a loss in conrmed quantity.

Lose 1 Assigned requirements lose their current The released quantity of the Lose  requirements
conrmation and are not conrmed. can be used to conrm more important
requirements or left as quantity available to
conrm future requirements.

Multiple Requested Schedule Lines for Single Order Items

Conguring and Executing a Backorder

Processing Run
Backorder processing runs are scoped on the basis of dened BOP variants to meet your business requirements and processes.
The requirements included in a BOP run are ltered and prioritized on the basis of the dened BOP segments which are part of
the BOP variant. The lters used in backorder processing are dened on the basis of sales order characteristics that can be
found in the system, for example, sales organization, sold-to party, material, plant or any combination therefore.

To congure, execute and monitor a BOP processing run, proceed as follows:

1. In the Congure BOP Segment app you create a new BOP segment and dene lters (referred to in the app as
) and the desired sequence of the requirements by assigning sort attributes. The resulting BOP segment can be
used in your BOP variants.

2. In the Congure BOP Variant app you create a BOP variant by picking the BOP segment created previously in step 1. You
dene how the requirements in the BOP segment are handled by assigning the BOP segment to a conrmation strategy.
For example: Your BOP segment lters requirements that belong a high-priority customer. You want their requirements
to be conrmed on the requested date: you assign this BOP segment to the conrmation strategy Win . Furthermore, you
can decide if you want to execute the subsequent BOP run using Available-to-Promise and/or Supply Assignment
6/26/2019

You can also choose to run a check against supply assignment if supply assignment has been customized for your
system. If you choose Supply Assignment  as one of the Execution Methods  for the BOP variant, the Supply Assignment 
Conguration  section is displayed. You can choose to congure supply assignment based on a pre-dened supply sort
that that has been maintained previously in tra nsaction ARUN_STKSORT . The supply sort rule denes how supply is
sorted. The Release Check Required  button is a standard function especially for Retail (Fashion). If the button is pressed,
the system checks if a separate release check is required before deliveries can be created.

You can use t he Global Segment   section to assign an additional BOP segment to restrict the list of requirements in a
BOP variant on the basis of a specic condition (for example, a specic material in a specic region). Doing this means
you can implement a common condition to a BOP variant in one step, rather than including it in each BOP segment
individually. This ensures that BOP segments remain simple and can be reused in other BOP variants. You can dene how
to handle remaining items of the global segment that are not part of any assigned BOP segments by assigning them to a
conrmation strategy or choosing Ignore Remaining Items  (if chosen, this setting is displayed on the Related Variants 
screen in the Congure BOP Segment  app.)

The business scenarios you can use depend on the selected document type and execution method:

Selected Execution Selected Document Possible Business Scenarios

Method Type

Available-to- Sales Documents A (checks as if a B (checks as if a

Promise sales order) delivery)
Stock Transport
Orders

Sales Documents
and Stock Transport
Orders

Supply Assignment Sales Documents A (checks as if a B (checks as if a PRE (preview mode, AR (see below for
sales order) delivery) checks which sales additional
Stock Transport orders would be information)
Orders impacted by a
supply shortage)
Sales Documents
and Stock Transport
Orders

Available-to- Sales Documents A (checks as if a B (checks as if a PRE (preview mode,

Promise and Supply sales order) delivery) checks which sales
Assignment Stock Transport orders would be
Orders impacted by a
supply shortage)
Sales Documents
and Stock Transport
Orders

Note that:

If Available-to-Promise  is the only Execution Method  selected, this does not have any impact on the conrmation
strategies.

If Supply Assignment  is the only Execution Method   seleted, this does impact the conrmation strategies.

Business scenario AR  is specically for trigge ring supply assignment with a special scope of check for normal ATP
processing.
6/26/2019

Use business scenario A for all purchase order types if stock transport orders and purchase orders need to be processed
in the same BOP run.

To create a variant, proceed as follows:

Step Action Instructions Expected Result

#

1 Log onto Log onto the SAP Fiori launchpad using the role . The SAP Fiori
SAP Fiori launchpad
launchpad. displays.

2 Access SAP Open the tile. The

Fiori app. screen
displays.

3 Create a Press the button. On the screen, make the following entries: A draft of the
new variant. variant is created.
<your variant name>

<your variant description>

4 Choose the Choose the for which you want to create the variant. Furthermore, select how
the requirements are to be checked, either using execution method are maintained
and/or . The avail able business scenarios/check rules vary dynamical ly, and dis played in
icon. depending on your selection and how your system has been congured. the header data.
Conrmation
You can use the button to assign an additional BOP segment to restrict the
strategy
list of requirements in a BOP variant on the basi s of a specic condition (for example, a
 is
specic material in a specic region). Doing this means you can implement a common
assigned as a
condition to a BOP variant in one step, rather than including it in each BOP segment
default.
individually. This ensures that BOP segments remain simple and can be reused in other BOP
variants. You can dene how to handle remaining items of the global segment that are not part
of any assigned BOP segments by assigning them to a conrmation strategy or choosing
Ignore Remaining Items 

Press the button to nis h editing the . Note that you can adjus t the
variant settings subsequently, if required.

5 Add Start to type <your segment01 name> in the empty eld below The segment and
segment to . its dened
variant. selection criteria
are displayed. The
segment is
automatically
assigned to the

conrmation
strategy.

6 Add Press the button. Conrmation

segment to strategy is
Start to type <your segment02 name> in the new, empty eld.
conrmation added and the
strategy. When the segment and its dened selection criteria are displayed, highlight the segment, chosen segment

press the button and choose conrmation strategy from and selection

the dropdown list (note that the currently assigned conrmation strategy cannot be chosen). criteria are lis ted.

Note that the button at the top of the screen simp ly adds an empty segment line
below the chose conrmation strategy. You cannot use this button to re-assign a segment
from one conrmation strategy to another.
6/26/2019

Step Action Instructions Expected Result

#

7 Save Press the button. The variant is

variant. saved. If you
return to the

screen, the draft

indicator below
the variant name
disappears.

8 Start If you are on the screen, select variant <your variant name> . The app conrms
backorder Alternatively, on the screen, choose from the dropdown next to that a backorder
processing the button. processing run
run. was scheduled for
your variant.

9 Display From the screen, press the button. The

BOP run screen in the
results.
displays and lists
runs for your
variant.

How to Schedule a Backorder Processing

Run
Schedule a run for backorder processing (BOP).

In this procedure, you want to trigger and schedule a backorder processing (BOP) run. The prerequisite for triggering and
scheduling a backorder processing run is the availability of at least one variant, created in the procedure How to Congure a
Variant for Backorder Processing. Proceed as follows:

Step Action Instructions Expected Result

#

1 Log onto SAP Log onto the SAP Fiori launchpad using the role .
Fiori launchpad.

2 Access SAP Fiori Open the tile. The screen

app. displays.

3 Create a new job. Press the button. A new job is created and will
run immediately.
On the screen, dene a name for your BOP run in the eld.

In the section, select the checkbox.

In the section of the subscreen, enter

<your variant name> in the eld.
6/26/2019

Step Action Instructions Expected Result

#

5 Schedule a new Press the button. A new, recurring job is

recurring job. created and scheduled.
Choose .

Make the following entries:

: <today>

: 01:00:00

: Flag checkbox

 After <number> Occurrence(s)

Choose .

For enter <your variant name> .

Choose .

How to Monitor the Results of a Backorder

Processing Run
Monitor the results of a backorder processing (BOP) run.

In this procedure, you want to display the results of a backorder processing (BOP) run. The prerequisite for this procedure is the
execution of at least one run, as processed in the procedure How to Congure a Variant for Backorder Processing or How to
Schedule a Backorder Processing Run. Proceed as follows:

Step Action Instructions Expected Result

#

1 Log onto SAP Fiori Log onto the SAP Fiori launchpad The SAP Fiori launchpad d isplays.
launchpad. using the role
.

2 Access SAP Fiori Open the tile. The screen displays and lists BOP variants for which BOP
app. runs have been processed or are running.

3 BOP run overview. Navigate to the by The information in the is as intended and a lis t of
choosing one of the listed runs. material-plant combinations is displayed.

Check the BOP run information,

for example, the variant name or
user name.

4 Quick lter for In the , press the The list of all material-plant combinations contains only those
conrmation  button. combinations where a conrmation issue exists.
issues.

5 Quick lter for In the , press the The list of all material-plant combinations contains only those
 button. combinations wher
6/26/2019

Step Action Instructions Expected Result

#

6 Select a material- Choose one of the displayed The screen disp lays.
plant combination material-plant combinations and
Detailed information is displayed for each requirement, for example, the
and check its check the conrmation key
conrmation strategy and the name of the BOP segment from which it
details. gures.
was selected. The conrmation key gures are also displayed.

The indicator dis plays the correct status of each requirement.

7 Check Choose one of the listed A dialog screen disp lays the of the selected
requirement requirements. requirement. Date, request and conrmation data is correct.
details.

8 Navigate to the Click on the name of the BOP The screen is disp layed.
BOP run overview. variant in the path above the
header.

9 Select a material- Choose the The conrmation strategies used in the BOP variant are listed and the
plant combination tab in the header. key gures are correct.
and check details.
Choose one of the displayed
conrmation strategies and
examine the conrmation key
gures.

10 Navigate to the Click on the name of the BOP The screen is disp layed.
BOP run overview. variant in the path above the
header.

11 Select a material- Choose the tab The screen is disp layed. The requirements for the
plant combination in the header. sold-to parties from the processed business documents are listed and
and check details. the key gures are correct.
Choose one of the displayed
sold-to parties and examine the
conrmation key gures.

Example 1: First-Come, First-Served

Your company conrms sales orders as they are r eceived and only one supplying plant is used. To ree ct this a pproach when
running backorder processing, you dene a BOP segment that sorts document numbers in a descending order and using the
following parameters:

1. In the Congure BOP Segment app, create a new BOP segment called FirstComeFirstServed.

2. Set the selection criterion for the new BOP segment t o SUPPLYINGPLANT of the ATPDOCUMENT is equal to
'0001'.

3. Set the prioritizer to and sort order.

4. In the Congure BOP Variant app, congure a new BOP variant called MyNightlyBOPRun with the conrmation
strategy and assigned the BOP segment .

5. Execute backorder processing.

6/26/2019

Before the BOP run:

Sales Or der: Requested Qty: Requested Date: Conrmed Qty: Conrmed Date:

954 12 05.08. 8 10.08.

960 8 20.08. 8 20.08.

961 10 09.09. 2 09.09.

972 18 15.09. 18 15.09.

...

After the BOP run:

Sales Or der: Requested Qty: Requested Date: Conrmed Qty: Conrmed Date:

954 12 05.08. 12 (=8+4) 10.08.

960 8 20.08. 8 20.08.

961 10 09.09. 10 (=2+8) 09.09.

972 18 15.09. 6 (=18-12) 15.09.

...

Note that the stock and receipts situation is the same before and after the BOP run.

Example 2: Reacting to Different Customer

Requirements
Your company uses backorder processing to react to the current situation in sales, including sales promotion events for various
customers simultaneously, as well as special customer agreements or credit blocks. To run backorder processing to sat isfy your
customers' requirements as much as possible, you need to create multiple BOP segments that are processed using a single
BOP variant which is congured for multiple conrmation strategies, as required and detailed below.

In the Congure BOP Segment app create the following BOP segments:

BOP segment CustomerHasPromotionEvent

Customer General Retail Inc. has a sales promotion event approaching and requires maximum quantities of certain products. It
is, therefore, crucial that the customers receives what is ordered. To achieve this:

1. Congure a new BOP segment called CustomerHasPromotionEvent.

2. Set the selection criterion for the new BOP segment t o

.

3. When you congure the BOP variant, assign this segment to conrmation strategy Win
6/26/2019

You can use t his app to:

Create prioritized sequences of values based on a specic attribute (for example, sold-to party) in sales and stock
transport documents.

Display, edit and copy existing sequences and their values.

Desktop

Tablet

This app is one of ve apps that you can use to set up, congure and execute backorder processing (BOP) in advanced Available-
to-Promise (aATP). For more information on related apps, see:

Congure BOP Segment

Congure BOP Variant

Monitor BOP Run

Schedule BOP Run

Note
Each app contains Web Assistant
Assistant documentation for key elds and concepts. To display the documentation while working in
the app, press F1 or the question mark symbol displayed in the app header.

Schedule BOP Run

With this app, you can congure and schedule jobs for e xecuting backorder processing (BOP) runs. To do so, you dene t he
technical parameters for the selection and behavior of the BOP run as well as, if required, simulative and recurring runs,
subsequent update processes, and logging. The results of any BOP run scheduled in this app are visible in the Monitor BOP Run 
app.

You can use this app if you have the business role Order Fulllment Manager (R0226).

You can use t his app to:

Schedule jobs which execute BOP runs for a specied BOP variant, either using the pre-dened ATP: Backorder
Processing Default te mplate or a personalized
personalized job template you have created.

Arrange job series that take different time zones and calendars into account.

Schedule recurring jobs.

6/26/2019

Display results of jobs selected on the basis of their status.

For a more detailed overview of the standard key features offered by this app, see Applic
Application
ation Jobs
Jobs..

You have already congured at least one BOP variant (containing at least one BOP segment) in the BOP apps for advanced
Available-to-Promise (aATP),
(aATP), Congure BOP Segment and
Segment and Congure BOP Variant.
Variant .

Desktop

Tablet

This standard app is offered as one of four apps that you can use to set up, congure and execute backorder processing (BOP)
in advanced Available-to-Promise (aATP). For more information on related apps, see:

Congure BOP Segment

Congure BOP Variant

Monitor BOP Run

Monitor BOP
BOP Run
Run
With this app, you can display the results of backorder processing (BOP) runs that have been setup in the Congure BOP 
Variant   app.
app. The app shows the conrmation status of requirements at different levels of granularity, helping you to conrm
that the backorder processing runs complies with your company's strategy.

If the results of the backorder processing run are not as required, you can change the setup of the corresponding BOP variant
and execute the run again. Alternatively, you can use the Release for Delivery  app
 app to adjust the conrmation data manually.

You can use this app if you have the business role Order Fulllment Manager (R0226).

You can use t his app to:

Display overall results of backorder processing runs executed in simulation mode, with document updates or with supply
assignment

Display data about backorder processing and conrmations at predened aggregation levels by material-plant
combination, conrmation strategy and sold-to party

Drill down to the requirement level to display the conrmation details

This app uses the following CDS views:

6/26/2019
C_ABOPRunMaterialPlant Run Conrmation Details by Material-Plant

C_ABOPRunStrategy Run Conrmation Details by Strategy

C_ABOPRunSoldToParty Run Conrmation Details by Sold-to Party

C_ABOPRunRequirement Requested Schedule Line in BOP

C_ABOPRunConfirmation Conrmation of a Requirement in BOP

This displays data only after a BOP run has been executed, either in simulation mode or with document updates.

Desktop

Tablet

Smartphone

This app is one of four apps that you can use to set up, congure and execute backorder processing (BOP) in advanced
Available-to-Promise (aATP). For more information on related apps and the app for manually adjusting conrmation data after
backorder
backorder processing, see:

Congure BOP Segment

Congure BOP Variant

Schedule BOP Run

Release for Delivery

Congure Order Fulllment Responsibilities

With this app, you can congure order fulllment responsibilities to enable your order fulllment specialists to process all the
materials for which they are responsible in the Release for Delivery  app.
 app. This app enables you to scope and personalize the work
of your order fulllment specialists and ensures that they only see sales documents and materials for which they are
responsible within a specic time period. Furthermore, the app helps you to react exibly to changing situations by offering
methods with which to reassign responsibilities from one order fulllment specialist to another.

You can use this app if you have the business role Order Fulllment Manager (R0226).

You can use t his app to:

Display and change existing order fulllment responsibilities, their periods of validity and any existing assignments to
order fulllment specialists.
6/26/2019

order fulllment specialist.

Create multiple order fulllment responsibilities in one step for a specic split criterion (for example, plant or material
group), dene their periods of validity and assign the order fulllment responsibilities to order fulllment specialists.

Before creating an order fulllment responsibility, ensure that:

Your system administrator has created the required user data for your order fulllment specialists in your system.

Your system administrator has assigned business role Order Fulllment Specialist (R0176) to the required fulllment
specialists in your system.

Desktop

Tablet

Release for Delivery

Release for Delivery

With this app, you can prioritize due sales orders containing materials with limited availability in the order fulllment
responsibility to which you are assigned. The app allows you to view the material availability situation of materials for which you
are responsible as well as assess the potential nancial impact of being unable to fulll sales orders. This, in combination with
other factors, helps you decide how to distribute material quantities between sales orders, before you release the sales orders
for subsequent logistics processes.

You can use t his app to:

Display sales orders containing materials for which you are responsible during a specic time period, including sales
order items for materials with limited availability.

Display the availability situation for the materials for which you are responsible.

Display the conrmation and delivery status for the materials in a sales order item.

Display the potential nancial impact for your organization if materials are not available and material redistribution is
not optimized.

Display any constraining elements (for example, reduced available quantity at a storage location) that may prevent a
sales order being fullled partially or completely.

Manually redistribute mat erial quantities between sales order items, as re quired, to fulll a sales order partially or
completely.
6/26/2019

Postpone further processing of sales order items.

Release materials for delivery, thus triggering subsequent logistics processes (for example, picking).

Minimize the number of delivery documents created interactively when sales order documents are processed: where
possible, only one delivery document is created per sales order document processed.

You can use this app if you have the business role Order Fulllment Specialist (R0176) and if at least one order fulllment
responsibility has been assigned to you in the Congure Order Fulllment Responsibilities app.

You can use this app to process materials for which advanced Available-to-Promise (aATP) functions have been activated.

Desktop

Tablet

Congure Order Fulllment Responsibilities

Schedule Deletion of ATP Results Log

With this app, you can create and schedule jobs for deleting backorder processing (BOP) run results that are displayed in the
Monitor BOP Run  and Schedule BOP Run  apps as well as ATP check results displayed in the Release for Delivery  app and written
to the ATP Results Log. To do so, you congure the te chnical parameter s for the delet ion job as well as, if required, a recurre nce
pattern. You can also congure the deletion job settings to delete the results of older BOP runs or BOP runs scheduled by a
specic user.

You can use this app if you have the business role Order Fulllment Manager (R0226).

You can use t his app to:

Schedule jobs which execute the deletion of ATP results logs for specied BOP runs, either using the pre-dened ATP:
Backorder Processing Result Deletion Default te mplate or a personalized job template you have created.

Arrange job series that take different time zones and calendars into account.

Schedule recurring deletion jobs.

Copy and cancel deletion jobs.

Monitor deletion jobs.

Display the results of deletion jobs.

6/26/2019

The assignment process can be executed from Backorder Processing (BOP), the Insight to Action tool, or during the immediate
assignment process:

For more informat ion about Backorder

Backorder Processing in aATP, see Backorder Processing (BOP).
(BOP).

For more information about Insight to Action, see Insight to Action Tool.
Tool.

For more information about immediate assignment, see Changing Sales Orders and
Orders and Changing Stock
St ock Transport Orders
Orders..

Note
If you want to use Supply Assignment (ARun), you must activate business function SUPPLY_ASSIGNMENT_01.

The following explains the ARun process:

Requirement Selection

Only sales orders and stock transport orders (STO) are considered as requirements for the supply assignment process. In the
backorder processing run, requirements are selected based on the BOP variant.

Stock Selection

Stock selection is based on the scope of availability check as determined by the checking group maintained in the material
master. For more information, see Scope of the Availability Check.
Check.

Note
Physical stock (batch stock, storage location stock) and future receipts (purchase orders, shipping notications) are relevant
for supply assignment.

Assignment

In this step, supply is assigned to requirements and the assignments are stored in table ARUN_BDBS. The assignment of supply
to requirements takes place as per the ATP quantity calculation logic. For more information, see Availability Check According
According t o
ATP Logic.
Logic. While executing the assignment with the ATP quantity calculation logic, the order to which supply is assigned is based
on the supply sort rule specied during BOP variant conguration if there are multiple receipt or supply elements on one date.
The supply sort rule is dened in transaction ARUN_STKSRT. If, for example, physical
physical invent ory stock is available in multiple
storage locations, you can use the sort rule to give a higher priority to supply in a specic storage location during assignment.

Note
If no supply sort rule is specied in the BOP variant, the system assigns supply elements to physical inventory, shipping
notication and then purchase orders.

The assignment of supply can be executed as normal or in preview mode, depending on the conguration of the BOP variant. In
preview mode, you can, for example, select existing orders against future supply (for example, purchase orders and shipping
notications) to estimate the possible uctuations in future warehouse inventory. This allows you to simulate issues and react
proactively: assignment in preview mode considers, for example, delayed goods receipts for purchase orders and possible
quantity deviations, and displays the effects on any existing sales orders. Assignment against future stock can take place with
6/26/2019

If a requirement document is not processed by supply assignment then the reason for this behaviour is displayed in the status
eld of the screen .

The document will not be processed by supply assignment for one of the following reasons:

Order has no conrmation quantity

Order item is incomplete for delivery

Order is a third-party order

Order is of type MTO or PTO

Order is a main MSO

Order item cancellation date is in the past

Shipping data is missing for the receiving plant

Shipment scheduling is not set for the STO document type

If some requirements are not completely assigned then the the status is displayed as Incomplete Assignment and the
appropriate reason is displayed.

Not enough stock for assignment on batch, segment, storage location, or plant level.

Not enough stock before cancellation date of the requirements.

Conrmation
Conrmation after cancellation date for t he requirements.

Release Check

The relea se check is only applicable for Retail

Reta il and is mandatory when the indicator is selected during
BOP variant conguration. If the stat us is set to O (Ready for
indicator is set, the supply assignment status
Release). In Insight to Action, transaction ARUNITA is used to execute the release check - for more information, see Insight to
Action Tool.
Tool. If is not selected, all assignments with physical stock have status F (Fix) and all
assignments with future receipts have status R (Reserved) for future receipts.

Note
Activating business function SUPPLY_ASSIGNMENT_RETAIL_01 is a prerequisite for using the release check.

Enhancements
Enhancements to Article Master
Master,, Material
Material
Master, and Site Master
The
The following
following enhancements have been made to Article Master, Material Master and Site M aster:

The article master has been enhanced with two Supply Assignment (ARun) relevant elds.

Supply Assignment relevant: You can set either ARun Relevant or ARun Non-Relevant. You can choose to make a variant
of a generic article relevant in the Supply Assignment (ARun) eld. This setting will also apply to all the other variants of
the generic article in that DC. This setting can be made only for variants of an article in a non-referenced DC. You cannot
change the relevancy of an item if assignments already exist for an article.
6/26/2019

Batches) to " " (Do not Assign Batches) only if no assignments exist for this material. You can change the value from " "
(Do not Assign Batches) to "1" (Assign Batches) only if:

1. There are no assignments for this article.

2. There are no open deliveries with assigned batch numbers.

3. The article is managed in batches.

Note
If Do not Assign Batches is set for an article that is managed in batches in a non-referenced DC, then maintaining batch
numbers in the sales orders or stock transport orders might lead to under conrmation and subsequently, under
assignments.

Note
ARun can be maintained only for variants of non-referenced DCs. If you have maintained the ARun setting for a variant of a
generic article, the same is copied to all the variants of the article in the non-referenced DC.

The material master is enhanced with two elds relevant to supply assignment (ARun).

Supply Assignment relevant – you can set either ARun Relevant or ARun Non-Relevant. You can choose to make a material
ARun relevant in the Supply Assignment (ARun) eld. You cannot change the relevancy of an item if assignments already exist
for a material.

Assign Batches in ARun – If the variant is marked as ARun relevant for a non-referenced DC and if it is batch managed, then you
can choose set either Assign Batches or Do not Assign Batches. You can change the value from "1" (Assign Batches)  to " " (Do
not Assign Batches)  only if no assignments exist for this material. You can change the value from " " (Do not Assign Batches)  to
"1" (Assign Batches)  only if:

There are no assignments

assignments for this material.

There are no open deliveries with assigned batch numbers.

The material is managed in batches.

If Do not Assign Batches is set for a material that is managed in batches

batches in a plant, then maintaining batch numbers
numbers in the sales
orders or stock transport orders might lead to under conrmation and subsequently under assignments.

The site master is enhanced with two elds relevant to Supply Assignment (ARun) on the Listing/Materials Planning tab.

Supply Assignment relevant

Assign Batches in ARun

The values set in the site master are copied to the variants of the generic article when listed to a non-referenced DC by default.
These values can be overwritten in the article master manually.
6/26/2019

Insight to Action is a detailed reporting tool used to monitor and analyze assignment results, check for exceptions and perform
appropriate actions. This tool provides an insight of the stock and requirement assignment, and enables you to perform
appropriate action (such as assign, unassign, release, delivery creation and so on).

You can use the Insight to Action tool to perform the following operation/functions:

Assess the assignment situation in the system: The system considers the existing assignment as well as the unassigned
requirement to analyze the assignment situation and provide an overview after the tool is executed.

Exceptions: Exceptions can be deviation between delivery dates and/or quantities of orders (such as sales orders, stock
transport orders, purchase orders, and so on). You can maintain exceptions using the ARUN_ITAE tra nsaction (see
Maint ain Exceptions for Insight to Action Tool for more information).

E-mail the person responsible for exceptions: The system sends an automated e-mail to the person responsible for the
exception rule.

Adjust assignment results using the actions such as assign, unassign, release, block, delivery creation, and so on.

Provide drill-down levels for and hierarchy conguration in the report output. The drill-down levels can
be dened using the ARUN_ITAH tra nsaction (see Maintain Hier archy Levels for Insight to Action Tool for more
information).

1. You have activated the business function SUPPLY_ASSIGNMENT_01. You can also a dditionally activate business function
SUPPLY_ASSIGNMENT_RETAIL_01

2. Use the authorization object ARUN_ITA (Insight to Action Authorization) to execute the Insight to Action tool.

Note
The following set up steps are optional:

1. You have created an exception rule using the Maintain Exceptions for Insight to Action ( ARUN_ITAE) transaction. If
you do not maintain an exception rule, the orders/requirements will not be checked for any exceptions.

2. You have maintaine d hierarchy or drill-down levels for and conguration using the Maint ain Hierarchy
Levels for Insight to Action ( ARUN_ITAH) transaction. If you do not maintain drill-down levels, the output of the
Insight to Action tool is displayed in a at view. That means, the output is displayed as a normal ALV output.

On the initial screen of the Insight to Action tool, you can execute the Insight to Action tool based on the following search
criteria:

Execution Modes

Choose one of the following execution modes:

Online : The assignments between the requirement and stock are posted. You can perform an action (such as assign,
6/26/2019

Background: You can perform actions such as Unassign, Release, Block and Rele ase Check on a group of orders. The
messages generated during background execution can be seen in the spool.

Selection Modes

Choose from one of the two selection modes:

In preview mode, for example, you can assign existing orders against future stock (for example, purchase orders and shipping
notications) to estimate the possible uctuations of future warehouse stock. This is an early warning system with which you
can simulate problems. That means that you can react proactively and in time.

Assignment in preview mode considers, for example, delayed goods receipts for purchase orders and possible quantity
deviations and shows the effects on the existing sales orders. Assignment against future stock can take place with either status
R (reserved) or F (xed). During preview mode, neither the stock nor the requirements are locked.

The results of the assignments in the preview mode are saved in ARUN_BDBS table t oo. There is no update of the “re al”
requirements and stock. That means you cannot create deliveries, for example, based on an assignment in the preview mode.

The results of the assignments in the normal mode are saved in ARUN_BDBS table. If at all there exists any assignment done in
preview mode for this material plant combination, the same would be deleted from database table and the assignments done in
Normal mode are saved in the database table.

Drill Down/Hierarchy

You can specify how the hierarchy or drill-down level should be displayed in the report output. This helps you analyze and
congure the output according to business requirements. The drill-down levels can be congured using the Maintain Hierarchy
Levels for Insight to Action Tool ( ARUN_ITAH) t ransaction.

Exception Rules

You can specify the exception rule dened for a specic order using the Maintain Exceptions for Insight to Action ( ARUN_ITAE)
transaction. If you have maintained this rule, the system calculates the exceptions for the selected orders and displays in the
respective columns in the output. You can assign one or more persons responsible to for the exception to each exception rule.
You can choose to send an automated e-mail to the person who is responsible for exceptions.

For more information about dening exception rules, see Maintain Exceptions for Insight to Action ( ARUN_ITAE).

Requirements/Stock selection

You can specify which requirements and stock should be included in the Insight to Action tool. Based on the selected
requirement or stock type, a corresponding tab with the relevant selection criteria is displayed on the initial screen of the
Insight to Action tool.

Requirement Selection

You can choose from the following order types that should be included in the Insight to Action tool:

Sales order: Sales orders are included as requirements in the Insight to Action tool if this checkbox is selected. The
tab with the sales order selection criteria is displayed on the initial screen of the tool.

Stock transport order: Stock transport orders are included as requirements in the Insight to Action tool. The tab with
the stock transport order selection criteria is displayed on the initial screen of the tool.
6/26/2019

Stock Selection

This stock selection will be used in the assignment also. If the user selects the stock type at initial screen, only those stock types
will be used in the assignment action. If user has selected the batch stock and purchase order stock then in the assignment pop-
up screen, these stock types are visible and the assignment will be carried out with these stock elements. The user has the
exibility to provide a particular stock number in assignment pop-up screen.

You can choose from the following stock segments that should be included in the Insight to Action tool:Congure Delivery Type &
Availability Check Procedure by Plant

Batch stock : Batch stock is included as a stock type in the Insight to Action tool if this checkbox is selected. The
tab is displayed on the initial screen of the Insight to Action tool with physical stock selection criteria.

Storage location : The stock available at the storage location is included as a stock type in the Insight to Action tool if
this checkbox is selected. The tab is displayed on the initial screen of the Insight to Action tool with physical stock
selection criteria.

Purchase orders : Purchase orders are included as a stock type in the Insight to Action tool if this checkbox is selected.
The tab with the purchase order selection criteria is displayed on the initial screen.

Shipping notications: Shipping notications are included as a stock type in the Insight to Action tool if this checkbox is
selected. The tab with the conrmation selection criteria is displayed on the initial screen.

Choose Action

This push button a ppears on the initia l screen of Insight To Action tool only when Background mode is selected in Execution
Mode.

You can choose from t he following actions:

Unassign: You can unassign a group of orders that were already assigned. Once the assigned orders are unassigned,
those orders will be deleted from ARUN_BDBS table.

Release : You can manually change the status of assigned orders from to or , or
to .

Block: You can block an order by changing the status to the status or , or
to .

Email: In the Insight to Action report, for each exception rule, you can send an automated e-mail to the person
responsible for the e xception rule. You can enter the re levant e -mail address in the Email To eld.

Release Check: This action is used to perform the release check on the order and set the status as per the release rule.
The ARun status of the order changes based on the release rule conditions specied in the release rule. Note that the
orders would be in status if relea se check required indicator was selected during the supply
assignment process in Supply Assignment (ARun).

Release Rule: The default release rule for the release check is maintained here.

Determination Logic: Depending on the option selected here, the release rule is picked up for the release check. It
species the order in which it searches for the release rule till it nds one. The following options are available:

Always Use Default

1ST from Sales Order, 2nd Default

1st Dete rmination, 2nd Default

1st from Sales Order, 2nd Determination, 3rd Default.

For information on Relea se Rule Determinat ion Transaction refer toRelease Rule Det erminat ion Transaction
6/26/2019

4. Choose an exception rule that you have dened (using the Maint ain Exceptions for Insight t o Action Tool( ARUN_ITAE))
transaction. This is an optional eld. If you do not specify an exception rule, then the order/requirements will not be
checked for exceptions.

5. Select the following optional checkboxes:

: When selected, the tool displays only those orders for which exceptions exist, in the
output of the Insight to Action tool.

: When selected, only the orders that are not yet assigned are included in the
output of the Insight to Action tool.

: When selected, it displays the stock situation of material plant for the
requirements selected.

6. Click to specify which requirements and stock should be included in the Insight to Action
tool. Based on the requirement and stock type selected, the corresponding tabs with relevant selection criteria are
displayed.

7. Click to specify the action to perform on orders. This is applicable only in Background Mode of ARUNITA.

8. Enter the relevant selection criteria and execute the tool. The requirement and stock assignment results are displayed
either in a at view or tree view (based on the settings dened in Maint ain Hierarchy Levels for Insight t o Action Tool(
ARUN_ITAH) t ransaction).

Maint ain Exceptions for Insight to Action Tool

Maint ain Hierarchy Levels for Insight to Action Tool

Authorizations for Insight t o Action Tool

Maintain Exceptions for Insight to Action Tool

You can dene an exception rule using the Maintain Exceptions for Insight to Action (ARUN_ITAE) t ransaction.

Exceptions can be deviation between delivery dates and/or quantities of orders (such as sales orders, stock transport orders,
purchase orders, and so on).

Example
A sales order needs to be delivered on March 5, 2015 but is assigned to a purchase order which has a goods receipt on March
10, 2015. In this case, the following exceptions are possible:

Delayed delivery exception: Goods Receipt date of the purchase order exceeds the sales order delivery date.

You can maintain exception rules for delivery dates and quantity checks based on the requirement. You can specify the SAP
system user you want to send the e-mail to.
6/26/2019

You can dene an exception rule for deviations that occur in dates using the comparison operators. For example, an exception
can be created if the delivery date of the purchase order is beyond the delivery date of a sales order.

A sales order is assigned using a purchase order. If you want an exception to occur when the requested delivery date of a
purchase order is greater than the conrmed delivery date of the sales order, then you should dene an exception rule for this
scenario.

Quantity Deviation Checks

You can dene an exception rule for deviations that occur in quantities using the comparison operators. For example, an
exception can be created if assigned quantity is less than the requirement quantity or the assigned quantity is less than
conrmed quantity.

1. Go to ARUN_ITAE.

2. Click to dene a new exception rule.

3. Enter an exception rule and a brief description about the rule.

4. Create exceptions for date and quantity checks using the comparison operators. Enter a brief description of the
exception.

5. For each exception rule, the system sends an automated e-mail to the person responsible for the exception rule. You can
enter the relevant the eld.

Note
You have to select the in the Choose Action option in the Background mode of the Insight to
Action Tool.

Before you enter the of the person responsible for the exception rule, you must ensure that
has a valid e-mail address in the user master data .

You can specify SAP system user to whom the mail would be sent.

6. Save the entries.

Insight to Action Tool

Maint ain Hierarchy Levels for Insight to Action Tool

Authorizations for Insight t o Action Tool

Maintain Hierarchy Levels for Insight to

Action Tool
6/26/2019

Demand Hierarchy Conguration

At the demand hierarchy conguration level, you can maintain a maximum of six drill-down levels and for each level, you can
maintain four different combinations of values. For example, for level 1, you can maintain the combination as Plant/Storage
location and for level 2, you can maintain the combination as Sales organization/Distribution channel/Division.

Supply Hierarchy C onguration

At the supply level, you can maintain a maximum of six drill-down levels.

Note
Few levels are not applicable for a particular requirement or stock (for example, in stock drill-down, the level
FSH_STOCK_SOURCE (stock number) is not applicable for storage location stock but applied to batch stock (batch number).
In this case, for storage location stock, this level appears as in the output screen.

Note
While conguring hierarchy at Demand Level, SAP recommends that nodes such as Stock Source and ARun Status should be
congured in the lowest level in order to avoid splitting of one node into two.

1. Go to transaction ARUN_ITAH.

2. Click on and click to dene a new hierar chy level.

3. Enter a name for the hierarchy and a brief description.

4. Maint ain levels for and based on your requirement.

5. Save the changes.

Insight to Action Tool

Maint ain Exceptions for Insight to Action Tool

Authorizations for Insight t o Action Tool

Authorizations for Insight to Action Tool

The system carries out an authorization check at the start of the transaction. You can authorize a user to execute the Insight to
6/26/2019

ARUN_ITA

This object controls the settings used to execute Insight to Action tool. There are authorization checks at different levels.
The following authorization eld checks are available for this object:

ARUN_ITA: Allows you to execute Insight to Action report. Set the value as 1 to get the authorization to execute
the transaction ARUNITA.

REL_CHECK: Allows you to perform the release rule check in the Insight to Action report.

ITA_ACTIVT: Allows you to choose an action to perform in the Insight to Action report.

The following function codes are available:

MODE: Lock an order

ALLOCATE: Assign an order

DEALLOC: Unassign an order

REL: Release

BLK: Block

RCHK: Relase rule check

DELIVER: Create Delivery

FLAT: Flat view

STKO: Navigate to MD 04P

SIZE_CONV: Perform characteristic value conversion

Insight to Action Tool

Maint ain Exceptions for Insight to Action Tool

Maint ain Hierarchy Levels for Insight to Action Tool

Release Rule

You use release check rules to determine which quantities are acceptable for your customers. You can specify the minimum
percentage of quantities that must be fullled at t he different r elease levels so that an order can be relea sed for delivery.

Release check can be performed both in Online and Background mode using ARun Insight to Action (ARUNITA).

Online mode : In the Online mode, you can specify only one release rule for all the selected orders.

Background mode: In the Background mode, the release rule is determined based on determination logic.

You can specify these parameters for the background mode:

6/26/2019

70% (achieved is 65%), and therefore, the ARun status of Item Material availability dates level changes to Reserved (R). The
system then checks at the order level whether a minimum quota of 70% can be reached. At order level, the total quantity is 140
(that is, 70%) and the ARun status of the schedule lines are not changed

Case 2: Exclude Already Failed Quantities

For Item Material availability date levels, only 30 pieces of the 50 ordered quantity are available and the release check is not
fullled with a minimum quota of 70%. As a result, the Item Material availability date levels are assigned the ARun status
Reserved (R). The system then checks at the item level whether a minimum quota of 70% can be achieved. The available
quantity for Item 1 is 45 (45%) and Item 2 is 35 (35%). Item 1 and Item 2 fail to achieve the minimum release percentage of
70%. Now, the system checks at the order level whether a minimum quota of 70% can be reached. At order level, since no
quantities are carried forward, the total quantity is 0.

Note
If a release rule check fails at a certain level, the schedule lines are never assigned the status or
even though the release rule passes at the higher release check levels. The status of the MBDAT level will be set as
or blank (with no entries) whichever is maintained in the customization. If release rule fails, fail status will be populated in
the the MBDAT level.

Calculation Base

For a requirement in which:

100 units are conrmed

70 units are delievered and

20 units are assigned

The calculation for release rule is as below:

" " Conrmed Quantity: ((Assigned quantity + Delivered or GI quantity) / Conrmed quantity) that is 90/100 = 90 %

"1" (Exclude Delivery or GI Quantity): (Assigned quantity / (Conrmed quantity – Delivered or GI quantity)) that is 20/30
= 66 %

You can dene release rules for:

PSST (Sales Order Only )

Document Header

Delivery Group (Sales Order Only)

Generic Articles

Articles (Items)

Items Material Availability date(s)

The system uses a bottom-up strategy, which means that the check starts at the lowest level and then goes to the next higher
level.
6/26/2019

The system sets the following statuses according to whether the result of a release rule check for a requirement is successful or
not:

Result Status Description

Release rule is successful Fixed (F) Outbound deliveries are possible

Fix and Hold (H) Outbound deliveries are not possible

Release rule is not successful Reserve (R) Reserve the quantities that are assigned to requirements

Blank Do not assign any quantity to the requirement

The ARun status is used for the following scenarios:

When a relea se check fails and the status is maintained as .

When you assign requirement with future receipt stock, the nal status will be maintained as ) and the
relea se check will not be applied in Normal mode. In preview mode, the status can be , or
 based on the release rules dened in transaction ARUN_ITAR.

Release Rule Determination Transaction

You can determine which release rule the system uses for a release check. You can go to transaction ARUN_ITAR to create or
edit release rules.
6/26/2019

You can maintain a release rule for a particular sales area or for a combination such as sales area-customer, sales area-
document type, sales area-customer-document type in following manner:

1. Go to transaction ARUN_ITARD.

2. Toggle from display mode to e dit mode and click on create button.

3. Enter sales area (sales org/distribution channel/division) or customer or document type and release rule and save.

4. Or alternatively you can choose to for a group of sale area in one step. Click on
, enter t he selection criteria where sales area and release rule is mandatory and click the
button.

Stock Sorting Transaction

During the assign action, ATP scheduling logic is used to assign the stock. However, if there are multiple stock elements on one
date then it is possible to specify the sort order in this transaction. For example if stock is available in multiple storage location
then you can use the stock sorting rule to give a higher priority for stock in one storage location than the other during
assignment.

Refer to Availability Check According to ATP Logic

Use the transaction ARUN_STKSORT

You select the Stock Type (ARUN_BSKZ) as a stock sort eld, but you want to assign individual priorities to each stock type as
follows.

Constants Priority Field Text

B 1 Purchase Order

C 2 Batch Stock

L 3 Shipping Notications

This kind of sorting would not be possible with a normal ascending or descending sort method. However, by assigning individual
priorities to each stock type, you can adjust the sort order to meet your needs.

Cross-Applications in Supply Assignment

(ARun)
The cross-application settings include all the supply assignment (ARun) settings pertaining to the different application areas
6/26/2019

For transfer posting between plants: When you do transfer posting from one plant to another plant, orders will be unassigned
based on the rules to unassign orders maintained.

For Transfer Posting between Storage locations:

When you do transfer posting from one storage location to another storage location, you should call the deallocation
logic if the supply is ARun-relevant.

If you are moving to one storage location which is not ARun-relevant, orders will be unassigned based on the mainatined
rules for unassigning orders.

Cross-Applications in Supply Assignment (ARun)

Quantities Reserved by Supply Assignment

(ARun) in MRP

The results from Supply Assignment (ARun) impact the net-requirement calculation during the material requirements planning
(MRP) run. MRP therefore considers the quantities reserved by supply assignment for requirements and stock or receipts.

You have created an article that is relevant for Supply Assignment (ARun).

You have executed the order Supply Assignment (ARun) for the order.

During the planning run, the system checks for the stock or future receipts that are already assigned to the requirements
during the supply assignment (ARun). Since the available stock or future receipts and requirements are already assigned, the
system cannot consume them during the MRP run. Therefore, the system proposes a new procurement proposal for the
requirements.

Assume the following:

Oct 9, 2013: Batch stock of 50 pieces

Oct 16, 2013: Purchase order for 50 pieces

Nov. 3, 2013: Sales order (4711) for 100 pieces

Nov. 10, 2013: Sales order (4712) for 100 pieces

1. Supply Assignment (ARun) assigns the available batch stock and the purchase order to sales order #4712.
6/26/2019

2. During the MRP run, the system proposes a new proposal, for example purchase requisition, for sales order #4711 dated
Nov. 3, 2013.

Note
For an article that is not relevant for supply assignment (ARun) or if supply assignment (ARun) is not executed, MRP always
procures at the latest date, and may even fail to fulll the requirements in certain cases.

Quantities Reserved by Supply Assignment

(ARun) in aATP
6/26/2019

You have created an article that is relevant for Supply Assignment (ARun).

You have executed the Supply Assignment (ARun) for the article.

During the availability check, the system checks for supply or future receipts that are already assigned to the requirements
during the supply assignment (ARun). Since the available supply or future receipts and requirements are already assigned, the
system does not consider them as available quantity during the availability check. Therefore, availability check can promise only
the remaining supply for any future requirements.

Assume the following:

Oct. 9, 2013: Batch stock of 100 pieces

Oct. 16, 2013: Purchase order for 100 pieces

Nov. 3, 2013: Sales order (4711) for 150 pieces

Nov. 10, 2013: Sales order (4712) for 100 pieces

1. Supply Assignment assigns the available batch stock to sales order #4712.

2. During the availability check for a new requirement (sales order #4711 requires 150 pieces), as the batch stock is already
assigned to a requirement, the system only proposes the remaining quantity of supply or future receipts and
requirement as the ATP quantity. That is, the availability check promises the purchase order of quantity 100 pieces and
the remaining 50 pieces will be delivered later.
6/26/2019

Application Programming Interfaces (APIs)

for advanced Available-to-Promise (aATP)
An application programming interface (API) is an interface provided by an application for interacting with other applications. An
API comprises, in essence, functions that other applications can call and data they can access.

The following APIs may be useful for interacting with aATP:

OData Service for Basic Product Availability Information API

OData Service for Product Allocation Object API

OData Service for Product Allocation Sequence API

Data Protection & Privacy in advanced

Available-to-Promise (aATP)
For information about Data Protection & Privacy in the context of advanced Available-to-Promise (aATP), seeBusiness Partner
End of Purpose (EoP) Check Class for aATP.

For more information about Data Protection & Privacy, see the security guide for SAP S/4HANA 1709 FPS01 available at
.