Application Help for SAP Cross-Channel Order Management ...

Application Help PUBLIC

SAP Cross-Channel Order Management for RetailDocument Version: 2.0 – 2018-03-30

Application Help for SAP Cross-Channel Order Management for RetailRelease 2.0, Support Package 6

Content

1 SAP Cross-Channel Order Management for Retail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 What's New. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Sales Order Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.1 Working with ATP Sales Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.2 Delivery Program Determination in Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3 Shipping Group Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.4 Setting Up Shipping Group Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Stock Transport Order Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 Delivery Program Determination in STOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2 Delivery Program Overview Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

5 Hard Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.1 Hard Allocation Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.2 Hard Allocation for Time-Dependent Stock Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285.3 Hard Allocation Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Executing Functions on Header Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Executing Functions on Detailed Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

6 Delivery Program Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356.1 Uploading Delivery Programs from MS Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.2 Specifying a Validity for a Delivery Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

7 Working with Stock Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407.1 Time-Dependent Stock Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427.2 Defining Stock Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.3 Creating and Maintaining Stock Pool Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Uploading Data from MS Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Uploading Data Using the Stock Pool API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

7.4 Maintaining Stock Pool Relevant Articles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.5 Item-Level Stock Pool Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527.6 Working with Stock Pool Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .547.7 Deleting Stock Pool Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

8 Working with Standalone ATP Sales Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

9 Order Life Cycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2 P U B L I CApplication Help for SAP Cross-Channel Order Management for Retail

Content

10 Operations Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.1 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.2 Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6210.3 System Administration and Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6310.4 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Application Help for SAP Cross-Channel Order Management for RetailContent P U B L I C 3

1 SAP Cross-Channel Order Management for Retail

Product Information

Product SAP Cross-Channel Order Management for Retail

Release 2.0 SP 6

Based On SAP ERP 6.0 Enhancement Pack 4; SAP for Retail is active

Documentation Published March 2018

Use

SAP Cross-Channel Order Management for Retail helps you fulfill the customer orders both from a timing and quantity perspective by considering some individual agreements with the customers, such as, Minimum Fill Rate or Maximum Number of Shipments.

Integration

SAP Cross-Channel Order Management for Retail is an add-on for SAP ERP. A minimum release of SAP ERP 6.0 enhancement package 4 is required and SAP for Retail must be active.

Features

● Master DataThe Additional Data Cross-Channel Order Management pushbutton enables access to a screen where you can maintain fields such as, Fill Rate, Maximum Number of Shipments, Minimum Number of Days between Shipments, Stock Pool ID, and so on.

NoteThis pushbutton is active only for customers for whom this function is activated as per Customizing, which depends on the account group to whom they belong.

For more information, see SAP Customizing Implementation Guide Sales and Distribution SalesCross-Channel Order Management for Retail Master Data Enhance Customer Master Data.


SAP Cross-Channel Order Management for Retail

● Order Entry○ Shipping group determination logic

You can use the shipping group logic to combine a few delivery dates or to minimize number of partial deliveries. You get a condensed view of deliveries on the Shipping Group tab, for example, what is the confirmed quantity and so on. For more information, see Setting Up Shipping Group Logic [page 16].

○ ATP Sales GridThis grid enables you to see available-to-promise (ATP) quantities at the level of a generic article. For more information, see Working with ATP Sales Grid [page 10].

● Hard AllocationYou can use hard allocation processing to allocate stock-on-hand to sales or stock transport orders or even a contract. It means the allocation quantity and allocation status is determined according to some business rules, such as stock selection rule, stock allocation rule, and fix allocation rule.For more information, see Hard Allocation [page 24].

● Delivery CreationDeliveries can only be created for sales or stock transport orders with allocated schedule lines.

● Delivery ProgramYou can define a delivery program using season, collection, and theme. One or more themes are collated together under a collection. One or more collections are collated together under a season.For more information, see Delivery Program Definition [page 35].

Application Help for SAP Cross-Channel Order Management for RetailSAP Cross-Channel Order Management for Retail P U B L I C 5

2 What's New

The following sections tell you what is new in SAP Cross-Channel Order Management for Retail 2.0 and what has changed since the last release:

Function Type of Change Description More Information SP

Standalone ATP Sales Grid

Enhanced You can differentiate between the stock available on hand and stock that will be available in the distribution center by a certain date. This is done using Material Availability Date.

Working with Standalone ATP Sales Grid [page 58]

-

ATP Sales Grid – Hard Allocation Grid

Enhanced You can display the quantities available for hard allocation. When you choose the hyperlink for a quantity, you can display quantities that have already been hard allocated along with the corresponding document.

-

Delivery Program Integration with Stock Transport Orders

New You can display which delivery program is assigned to which stock transport order item and redetermine a delivery program for a stock transport order item.

Delivery Program Determination in STOs [page 20]

-

Delivery Program Definition

Enhanced You can specify additional information for a delivery program, specifically additional information for season, collection, or theme.

Delivery Program Definition [page 35]

-


What's New


Uploading Delivery Programs from an External Source

New You can upload delivery programs from a Microsoft Excel file.

Uploading Delivery Programs from MS Excel [page 37]

-

Delivery Program Overview

New In a stock transport order, you can display aggregated delivery program information at the header level.

Delivery Program Overview Display [page 22]

-

Hard Allocation Workbench Result Screen

Enhanced You can use the Undo pushbutton to undo the last performed action, for example, to undo allocation operation.

Executing Functions on Header Level [page 32]

-


Enhanced You can allocate either full or partial quantities using the Allocate Full or Allocate Partial option.

Partial allocation can be done based on either an amount or a percentage.

Hard Allocation Workbench [page 30]

-


Enhanced You can deallocate full or partial quantities using the Deallocate Full or Deallocate Partial option.

Partial deallocation can be done based on either an amount or a percentage.

Hard Allocation Workbench [page 30]

-

Stock Pool Workbench Enhanced You can use the Calculate pushbutton tp recalculate stock pool data, such as pool potential and so on.

Working with Stock Pool Workbench [page 54]

-

Application Help for SAP Cross-Channel Order Management for RetailWhat's New P U B L I C 7


Working with Stock Pools

Enhanced You can use the Mass Change pushbutton to change pool quantity or status for multiple stock pools.

Working with Stock Pool Workbench [page 54]

-

Priorities for Stock Pools

New You can assign priorities to stock pools using the stock pool header configuration. The system calculates the available quantity for each pool based on the priority.

Defining Stock Pools [page 47]

-

Time-Dependent Stock Pools

New You can assign a validity period to a stock pool.

Time-Dependent Stock Pools [page 42]

SP02

Item-Level Stock Pool Determination

New You can determine the stock pools on item level instead of header level for the entire document. You can do this by implementing a BAdI with custom logic for stock pool determination at item level.

Item-Level Stock Pool Determination [page 52]

SP02

Additional Attributes for Stock Pools

Enhanced You can define additional attributes for stock pools (for example, channel, country, promotion ID, and so on).

SP02

Exclusion of Free Floating Quantity from a Pool

Enhanced As part of Customizing, you can exclude a stock pool from access to free floating quantity.

SP02


What's New


New API for Stock Pool Data

New You can use an RFC function module to import stock pool data (time-dependent stock pools with stock pool characteristics, article relevance for stock pools, stock pool quantities).

Uploading Data Using the Stock Pool API [page 50]

SP02

Hard Allocation Relevance on Article and Site Level

New You can implement a new BAdI to determine the hard allocation relevance of a document item based on article and site information.

Hard Allocation Processing [page 24]

SP02

SP Priorities as HA Sort Criterion

Enhanced You can use stock pool priority as sorting parameter for hard allocation processing.

SP02

Data Protection New Additions concerning data protection have been made to the Master Guide for SAP Cross-Channel Order Management.

Please see the master guide available at http://help.sap.com/wom.

SP05

Data Protection and Privacy

Updated Section has been updated in the Master Guide for SAP Cross-Channel Order Management.

Please see the master guide available at http://help.sap.com/wom.

SP06

Application Help for SAP Cross-Channel Order Management for RetailWhat's New P U B L I C 9

http://help.sap.com/wom




3 Sales Order Processing

The chapter lists functions that have been used to enhance the standard sales order process.

3.1 Working with ATP Sales Grid

Prerequisites

You have maintained customizing tables for the ATP sales grid. You can maintain activation criteria for combinations of sales organization, distribution channel, division, and sales document type.

For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail ATP Grid Maintain Settings for ATP Grid.

NoteThe ATP sales grid is displayed only if these criteria are fulfilled.

Context

When a sales order is created or changed manually, the person entering the data needs to quickly access the information about variants that are available for the generic article, which has been entered. In this case, the article availability date as well as the delivery date is equally important.

Therefore, the available-to-promise (ATP) sales grid is available for the maintenance transactions of sales orders and contracts. The ATP sales grid can be activated by sales area and order type. It is embedded in the standard sales order screen and positioned below the variant matrix where the user can enter quantities for the different article variants.

NoteA standalone version of the ATP sales grid is available and can be used outside of the order maintenance transactions. For more information, see Working with Standalone ATP Sales Grid [page 58]

The ATP sales grid contains the available quantities for the chosen article’s characteristics. You can switch between different views, such as, daily, weekly, or monthly. You can display subtotals for the displayed


Sales Order Processing

characteristics, if required. If the displayed ATP quantities are obsolete then you can trigger a recalculation and get the current information from the system.

Procedure

1. Create or change or display a sales document or a contract.

You can either create a sales order using Create Sales Order transaction (VA01) or create a contract using Create Contract (transaction VA41).

To change a sales order use Change Sales Order (transaction VA02) or change a contract using Change Contract (transaction VA42).

If you only want to display the sales order use Display Sales Order (transaction VA03) or display a contract using Display Contract (transaction VA43).

2. To access the ATP sales grid, enter a generic article number in the Item Overview and choose Enter.

If a generic article owns more than two characteristic values then you have to choose which characteristic value is displayed within the ATP sales grid and which value is considered as fixed.

3. The system displays ATP Sales Grid.

You can see what combinations or variants are possible at a glance along with their quantities. The ATP quantities can deviate because an article variant can be assigned to one or more stock pools. If an article is assigned to at least one stock pool then this information is provided in the description of the frame for the ATP sales grid.

The quantity displayed for this article variant is the sum of the ATP quantity and the free floating quantity (quantity that is not directly assigned to a distinct stock pool).

If you start the transaction to change the sales order and select a line in the Item Overview, which contains a generic article then all confirmed article quantities belonging to the selected item position are not considered in the displayed ATP quantities -> Delta-Handling.

ExampleStarting point: Generic article A exists with the variant A001 and an available ATP quantity of 100 PC.

Let’s say you want to create a sales order with this generic article and the prerequisites for displaying the ATP sales grid have been met. The system displays a quantity of 100 PC for the article variant A001.

If you enter a quantity of 10 PC for the current item position 1 then only 90 PC of article variant A001 are available for the next item positions or for other sales orders. If you select position 1 and navigate to the ATP sales grid again then the system displays available quantity and does not consider the quantity of the position selected in the Item Overview (position 1).

You can also see Mat.Avail. Date in this grid. A date in this column indicates the earliest date by when goods will be available in the distribution center.

NoteA row without a material availability date indicates the goods that are already available in your distribution center.

Application Help for SAP Cross-Channel Order Management for RetailSales Order Processing P U B L I C 11

Additionally, you can also use the hyperlink for article variant to navigate to the Availability Overview (transaction CO09) directly.

4. Enter the required quantities and navigate back to the previous screen.

All quantities, which have been entered and confirmed for that item position, are considered in future ATP checks for the ATP sales grid.

3.2 Delivery Program Determination in Sales Orders

Use

The Delivery Program tab is available in the item details. On this tab, you can see which validity of a delivery program is currently assigned to the order item. The system also displays a log where you can see why this delivery program validity was assigned to the sales order item.

A delivery program must fulfill certain criteria in a particular sequence to be considered as a match:

1. In Customizing, activate Delivery Program Determination at the following levels○ Sales Document Type○ Sales Org.○ Distribution Channel○ Division

2. Assign the article of the sales order item to at least one delivery program.If the article is not assigned to any delivery program, no further checks are performed.

3. Ensure that the sales order creation date is within the order window, which means within Order From and Order To of the assigned delivery program.If the validity has Allow Outside Order Window checkbox selected, then this check is not performed and the program is considered as valid.If there is more than one validity that fulfills this criteria, then a three-step evaluation of the fitting validities takes place. This process is described below:1. The validities are given a priority by evaluating how many attributes of the validity (for example,

Distribution Channel, Country, Region and so on) match the sales order.There is a hierarchical view on validity definition. The finer the granularity of the validity definition, the higher the validity is rated.

ExampleThere are two validities with the following attributes defined:

○ Sales Org: DC-Customer○ Sales Org: DC-Country-Customer Group

In this case, the first validity is chosen because Customer is the finest granularity level on which you can define validities. In other words, the first validity is more specific, so it has a higher priority than the second validity.

If there is more than one validity remaining after this evaluation step then the following evaluation is done.



2. A delivery program can be defined on the season level, season-collection level, or on season-collection-theme level.The more detailed the definition, the higher the priority for the validity in the delivery program. This means that a delivery program defined on the season level has a lower priority than a program defined on the theme level.If more than one validity is still being evaluated with the same priority, then the following check is performed:

3. The validity with the earliest date in Delivery From is chosen.If there is still more than one fitting validity, then the system displays an overview of all delivery program validities that fit the order data, the order creation date, and the requested delivery date.You can manually choose a different validity and save it with the item.

NoteThe delivery program determination also influences the Cancellation Date of the order. It is set to the latest Delivery To date of the delivery program validities assigned to the items.

Prerequisites

You have made delivery program-relevant settings. The delivery programs have been created and validities and articles have been assigned.

For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Delivery Program .

3.3 Shipping Group Display

Use

Shipping groups are virtual bundles of planned physical shipments. The number of shipping group for a sales order does not necessarily reflect the number of deliveries to be created for the sales order.

You can find the shipping group screen on the Shipping Group tab at the header level of the sales order.

Shipping group calculation is either done automatically when you save a sales order or manually using the Calculate Shipping Group pushbutton on the shipping group screen.

An automatic calculation is triggered by one of the following:

● An available-to-promise (ATP) relevant change in the sales order.This means changes that also trigger standard scheduling or ATP changes in ordered quantity or delivery date for an item.

● Deletion or rejection of an item.● Change of a shipping group parameter, such as, aggregation level, fill rate, maximum number of shipments,

and so on.


The shipping groups display is customizable on sales area and order type level. For more information about Define Shipping Group Views option, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Shipping Groups Set Up Shipping Group Calculation and Display .

Prerequisites

You have maintained relevant settings for shipping groups under SAP Customizing Implementation GuideSales and Distribution Sales Cross-Channel Order Management for Retail Shipping Groups. .

Features

Shipping Group consists of:

● Shipping group headerThe shipping group header is a dynamically generated screen. Its content depends on the step parameters in Customizing for shipping groups. Each active parameter has an input field on the header screen. For example:○ Cancellation Date○ Minimum Number of Days Between Shipments○ Fill Rate for Articles

During order creation, the system defaults the shipping group header values from customer master record with two exceptions:○ Aggregation level: If you have entered the aggregation level in Customizing, it overrules the level taken

from customer master.○ Cancellation date: If delivery program is active for the order, then during order creation, the latest

Delivery To Date of all delivery programs overrules the cancellation date from the customer master.The shipping group parameters are manually overwritten and stored together with the sales order data, regardless of how the default values were determined.

● Shipping Group Views (Tree)The tree control on the left hand side contains an overview of the active shipping group view. Depending on the Customizing, the following views can be displayed:○ Article○ Shipping Group○ Ship-to Party○ Delivery Site○ Delivery Program

Each view corresponds to a different aggregation, such as, by article, by shipping group, by delivery program and so on. When you click the root node in the tree, the system switches the content of the area view to the right of the tree. When you click the subnode, the content of the area view is filtered by the key from the subnode.

● Shipping Group Area Views (Grid)The grid area contains the sales order data aggregated by the selected view. The quantities, for example, ordered quantity, confirmed quantity are cumulated onto the selected key combination, such as, article or



shipping group. For the article view there is the additional option to control the aggregation level for generic articles. There are five aggregation levels possible○ First Level: Complete Order○ Second Level: Generic Article○ Third Level: Characteristic Value for Colors of Variant○ Forth Level: Characteristic Value for Main Size of Variant○ Fifth Level: Characteristic Value for 2nd Size of Variant

ExampleIf the aggregation level is 00003 - Color, then only the generic article and the color attribute are displayed on the article view. The data on other levels is cumulated onto this level.

On the area views, standard ALV functions, such as, sorting, filtering, subtotals and different layouts are available. Additional functions are available using the following pushbuttons:○ Calculate

This option works on the complete order and no line selection is necessary. It triggers a recalculation of shipping groups. A yellow icon on the calculate button indicates a change in the sales order, which might make a new calculation necessary.

NoteA green icon indicates that no automatic calculation on save would take place because there is no relevant change. Nevertheless, a manual calculation is always possible.

○ DetailsWhen you select a single line and choose the Details pushbutton you can navigate to the details view.

○ MessagesThe messages are collected for the complete order (no line selection is necessary). When you choose the Messages pushbutton, the system opens the messages view.

○ Tree On/OffThis pushbutton hides the shipping group views tree on the left.

● Shipping Group Detail ViewThe detail view contains the sales order data on the lowest aggregation level. This is not equal to the schedule line level of the order, because potentially multiple order items can be cumulated into one entry. On the detail level, the following navigation options are available:○ Overview: Switches back to the shipping group area view○ Previous/Next: Navigates back and forth between the different entries on detail level

● Shipping Group Exception Dialog BoxThis dialog collects messages during the shipping group determination. You can review all the errors which occurred during one step, for example, during fill rate determination. This helps you to make decisions about the parameter on header level, such as fill rate, cancel date, and so on.As a general rule, the level on which errors occur is processed as far as possible. For example, if the error is found during fill rate determination, then the follow-up calculation of minimum number of days is not executed. This also means that shipping groups are created even if they contain errors, for example, fill rate could not be met.


ExampleCancellation date is April 1st and for generic article 5654 and with size M, the fill rate of 90% cannot be met. In this case, all delivery dates for this article or width are cumulated onto the latest delivery date before the cancellation date of March 26th.

More Information

Setting Up Shipping Group Logic [page 16]

3.4 Setting Up Shipping Group Logic

Use

The shipping group logic is customizable on the sales area and order type level. The Customizing for shipping groups consists of two parts:

● Define Steps for Shipping Group CalculationDuring the step definition, you can create calculation steps, which are the building blocks for the shipping group calculation. You can define the steps once and use them multiple times in different combinations. A certain number of steps is already predefined.

● Set Up Shipping Group Calculation and DisplayThe Customizing for the shipping group calculation selects the steps defined earlier and arranges them in a sequence.

Prerequisites

You have maintained relevant settings for shipping groups under SAP Customizing Implementation GuideSales and Distribution Sales Cross-Channel Order Management for Retail Shipping Groups .

Features

The following steps are available, which are based on methods of class /WOM/CL_SG_PROCESS_STEPS. These can be used to create the shipping group logic:

● Pre-Processing Step for Shipping Group CalculationStep ID: /WOM/PREP (/WOM/IF_SG_LOGIC~PREPROCESS_DATA)This is a data preparation step. The schedule lines are analyzed and a table with control information is created. This table contains information from both item (for example, site, generic, delivery program) and



schedule line (confirmed delivery date, confirmed quantity). A couple of general checks are also done here. For example, it is checked whether Fixed Date and Qty or Delivery Groups are used in the sales order.As a result of this step. we have the information based on which the actual determination of shipping groups takes place.

● Post Processing Step for Shipping Group CalculationStep ID: /WOM/POST (/WOM/IF_SG_LOGIC~POSTPROCESS_DATA)This is a data collection step. The information from the control table, which at this point contains the confirmed delivery dates resulting from the shipping group calculation, is matched against the schedule lines from the order. If a schedule line date has to be moved, the old line is marked as deleted (UPDKZ set to D) and a new line with same data but new date is inserted (UPDKZ set to I). If only the quantity (or shipping group number) is being changed, then the line is marked as updated (UPDKZ set to U). The new schedule lines are then passed back into the sales order.

● Calculation Based on Delivery ProgramStep ID: /WOM/DPCA (CALCULATE_DELV_PROGRAM)The system calculates the confirmed delivery date based on the delivery program information in the sales order. Depending on the delivery program configuration, this is either the delivered from“delivered from” or the “delivered to” date of the delivery program.

CautionAll sales order items belonging to the same delivery program need to have the same configuration. Otherwise, the system displays an exception and a calculation is not possible.

● Check Based on Delivery ProgramStep ID: /WOM/DPCK (CHECK_DELV_PROGRAM)This step collects all error messages regarding delivery programs in the order. The system raises an exception if an error is found. If the exception is classified as an error in OLM Customizing, then shipping groups are marked as faulty. Additionally, the system checks the consistency of the shipping groups for a delivery program based on the configuration of the delivery program.The consistency check can result in an exception which can be an error or a warning, depending on the settings at the delivery program. If this is configured as an error, the shipping groups are marked as faulty.

CautionAll sales order items belonging to the same delivery program need to have the same configuration. Otherwise, the system displays an exception and a check is not possible.

● Fill Rate for Shipping Group (Article)Step ID: /WOM/FRAT (CALCULATE_FILLRATE_FOR_ART)This is a fill rate-related step. Fill rate calculation is controlled by the parameter aggregation level. The following levels are possible:○ Complete Order○ Style (generic article)○ Color (Characteristic Value for Colors of Variants)○ Size1 (Characteristic Value for Main Sizes of Variants)○ Size2 (Characteristic Value for 2nd Sizes of Variants)

Fill rate is calculated as the cumulated confirmed quantity divided by the related ordered quantity. The confirmed delivery dates in the control table are shifted to achieve the target fill rate depending on the calculation.

● Fill Rate for Shipping Group (Delivery Program)


Step ID: /WOM/FRDP (CALCULATE_FILLRATE_FOR_DP)This is a rate-related step. Fill rate calculation is controlled by the delivery programs of the items. The data is aggregated on the delivery program levelFill rate is calculated as the cumulated confirmed quantity divided by the related ordered quantity. The confirmed delivery dates in the control table are shifted to achieve the target fill rate depending on the calculation.

● Calculate First ShipmentStep ID: /WOM/FISH (CALCULATE_FIRST_SHIPMENT)If fill rate is active, the first shipment is calculated here. The basic idea is to have all aggregation combinations from the sales order within the first shipping group for each site. This is achieved by sorting the control table for different key fields, such as, site, generic, confirmed delivery, and so on.

● Maximum Number of ShipmentsStep ID: /WOM/MAXS (CALCULATE_MAX_SHIPMENTS)This step ensures that a certain number of shipping groups (cross site) is not overshot. The shipments in excess are merged if they are on the same site. If merging is not possible, which means maximum number of shipments is smaller than number of sites, then the system raises an exception.

● Minimum Number of Days between ShipmentsStep ID: /WOM/MIND (CALCULATE_MIN_DAYS)This step ensures that a certain number of days exist between the different shipments (cross site). Compatible entries in the control table that are too close to each other are merged. If there is no entry to merge, then the control record is attached to the end of the list, that is latest confirmed delivery date plus minimum number of days.

Activities

1. Preprocess dataThis is a data preparation step. The schedule lines are analyzed and a table with control information is created. The calculation process always starts with the preprocess data step.

NoteShipping group calculation is only done up to cancellation date.

2. Process steps1 to N process steps can be arranged into a sequence in Customizing. This sequence is executed during shipping group calculation, whereby the result of one step is the input for the following step. If an exception occurs during the processing of one step, which is classified as an error in the Order Life Cycle Management (OLM) Customizing , then the current step is finished, but the following steps are skipped. As a result, all calculated shipping groups are marked as faulty.

3. Post process dataThis is a data collection step. Based on the information from the control table, which at this point contains the confirmed delivery dates resulting from the shipping group calculation, schedule lines are altered or newly created.These schedule lines are then passed back as a result set. The calculation process always ends with the post process data step.

4. Integrate calculation result into sales order



Since it is not possible to directly change the schedule line information in the order, standard form routines are used to manipulate sales order data. The system ensures that all index tables on item and schedule line level are consistent.


4 Stock Transport Order Processing

The chapter lists functions that have been used to enhance the stock transport order process.

4.1 Delivery Program Determination in STOs

Use

The Delivery Program tab is available in the item details. On this tab, you can see which validity of a delivery program is currently assigned to the stock transport order item. The system also displays a log where you can see why this delivery program validity was assigned to the stock transport order item.

A delivery program (DP) must fulfill certain criteria in a particular sequence to be considered as a match:

1. In Customizing, activate the Delivery Program Determination at the following levels○ Supplying Site○ Purchase Document Type○ Sales Org.○ Distribution Channel○ Division

2. Assign the article of the stock transport order item to at least one delivery program.If the article is not assigned to any delivery program, no further checks are performed.

3. Ensure that the stock transport order creation date is within the order window, which means within Order From and Order To of the assigned delivery program.If the Allow Outside Order Window checkbox is selected for the validity, then this check is not performed and the program is considered valid. If there is more than one validity that fulfills this criteria, then a three-step evaluation of the fitting validities is performed. This process is described below:1. The validities are given a priority by evaluating how many attributes of the validity (for example,

Distribution Channel, Country, Region and so on) match the stock transport order.There is a hierarchical view on validity definition. The finer the granularity of the validity definition, the higher the validity is rated.

ExampleThere are two validities with the following attributes defined:

○ Sales Org: DC-Customer○ Sales Org: DC-Country-Customer Group

In this case, the first validity is chosen because Customer is the finest granularity level on which you can define validities. In other words, the first validity is more specific, so it has a higher priority than the second validity.

If more than one validity remains after this evaluation step, then the following evaluation is done.


Stock Transport Order Processing

2. A delivery program can be defined on the season level, season-collection level, or on season-collection-theme level.The more detailed the definition, the higher the priority for the validity in the delivery program. This means that a delivery program defined on the season level has a lower priority than a program defined on the theme level. If more than one validity are still being evaluated with the same priority, then the following check is performed.

3. The validity with the earliest date in Delivery From is chosen.If more than one fitting validity is still found, then the system displays an overview of all delivery program validities that fit the order data, the order creation date, and the requested delivery date. You can manually choose a different validity and save it with the item.

NoteThe delivery program determination also influences the Cancellation Date of the order. It is set to the latest Delivery To date of the delivery program validities assigned to the items.

Prerequisites

You have made delivery program-relevant settings. The delivery programs have been created and validities and articles have been assigned.

For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Delivery Program .

Features

You can execute the following additional functions based on the parameters defined for the delivery program:

● Proposal Date○ Delivery Date From

If the confirmed delivery date is before the Delivery Date From of the program, the confirmed delivery date is shifted accordingly.

○ Delivery Date ToIf the confirmed delivery date is before the Delivery Date To of the program, the confirmed delivery date is shifted accordingly.

○ No proposalConfirmed delivery date is not moved based on the delivery program.

● Message Type for DP Check○ No Message

The system does not check if the confirmed delivery date is within the delivery window of the program.○ Warning

The system checks if the confirmed delivery date is within the delivery window. If this is not the case, then a warning message is displayed.

○ Error

Application Help for SAP Cross-Channel Order Management for RetailStock Transport Order Processing P U B L I C 21

The system checks if the confirmed delivery date is within the delivery window. If this is not the case, then an error message is displayed. If hard allocation is active for the supplying site, then the schedule lines outside the delivery window cannot be fix allocated during the allocation step.

4.2 Delivery Program Overview Display

Use

The Delivery Program Overview gives you access to the stock transport order (STO) data on an aggregated level.

Prerequisites

You have maintained relevant settings for delivery program overview under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail .

Features

Delivery Program (DP) Overview consists of:

● Aggregated Views (Tree)The tree control on the left hand side contains an overview of the following aggregated views:○ Article○ Ship-to Party○ Delivery Program

Each view corresponds to a different aggregation, such as by article, delivery program, and so on. When you click the root node in the tree, the system switches the content of the area view to the right of the tree. When you click the subnode, the content of the area view is filtered depending on the key from the subnode.

● Grid ViewThe grid area contains the order data aggregated by the selected view. The quantities, for example, ordered quantity, confirmed quantity are cumulated onto the selected key combination, such as by article or delivery program.On the area views, standard ALV functions such as sorting, filtering, subtotals and different layouts are available. Additional functions are available using the following pushbuttons:○ Details

When you select a row and choose the Details pushbutton you can navigate to the details view.○ Messages

The messages are collected for the entire order; row selection is not required. When you choose the Messages pushbutton, the system opens the messages view.


Stock Transport Order Processing

○ Tree On/OffThis pushbutton hides the views tree on the left.

● Detail ViewThe detail view contains the order data on the lowest aggregation level. This is not equal to the schedule line level of the order because potential multiple order items can be cumulated into one entry. On the detail level, the following navigation options are available:○ Overview

Switches back to the shipping group area view.○ Previous/Next

Navigates back and forth between the different entries on the detail level.● Messages View

This view collects exceptions from date shifts and checks based on the delivery programs.

Application Help for SAP Cross-Channel Order Management for RetailStock Transport Order Processing P U B L I C 23

5 Hard Allocation

All available-to-promise (ATP) checks and confirmations during order entry and rescheduling are a type of soft allocation. However, when the time of logistical execution and delivery to the customer comes closer, it’s necessary to change this to real hard allocation, which is understood as a fixed assignment between open sales orders and the stock available in the delivering distribution center.

You can create deliveries only when quantities have been hard allocated with status fix. The hard allocated quantities are kept until the goods issue booking is done.

5.1 Hard Allocation Processing

The hard allocation transaction allows you to allocate available quantities to a list of sales orders, contracts, or stock transport orders. It is typically executed in the background without any user interaction once the relevant business rules for selection, sorting, and processing are fixed and maintained.

Prerequisites

● You have maintained relevant settings for hard allocation under SAP Customizing Implementation GuideSales and Distribution Sales Cross-Channel Order Management for Retail Hard Allocation .

● You have maintained relevant settings for hard allocation relevance of the distribution center under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail General Activate Switches on Site Level .

NoteOptionally, you can also use the BAdI Determination of Hard Allocation Relevance to determine hard allocation relevance at a level that is lower than delivering site. For more information, see the description of the BAdI under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Hard Allocation Enhance Standard Logic for Determination of Hard Allocation Relevance .


Hard Allocation

Features

You perform hard allocation processing using transaction /WOM/HA. The process consists of a sequence of steps that are controlled by entries in the selection screen of the report and in the Customizing for hard allocation:

● SelectionThe Selection Parameters for hard allocation processing and the Hard Allocation Workbench are mostly identical. You can specify generic selection criteria, for example, by article or by customer or selection criteria for the sales document or the stock transport order. For example, you can use the sales document number or purchasing document number.You can also specify delivery program attributes, such as season, collection, or theme to select required sales documents or stock transport orders.To select sales orders that are beyond a certain date, you can also specify a Sales Order Cancellation Date. This date is the last date by when the customer would like to receive the goods. With the Reduce Order Quantity field, this function can be used to reject sales orders that lie beyond the cancellation date.For more information about Reduce Order Quantity, see Hard Allocation Workbench [page 30].

● SortingIn addition to the selection criteria mentioned above, you can sort the selected items by defining sorting priorities. The sorting priorities can influence the sequence in which the selected documents are processed. Therefore, you can specify priorities for each sorting parameter to define an individual sorting sequence in which the document workload for the hard allocation processing is processed. You can assign a maximum of seven different sorting parameters and priorities. If a parameter is not used for sorting, then you must select N/A (not applicable).

● Free AllocationThe existing allocations can be reset for the selected documents depending on settings made on the selection screen under Increase Fix Allocated Quantity and Increase Reserved Quantity.The system ensures that quantities that are in deliveries but not yet goods issued remain fix allocated even if the Increase Fix Allocated Quantity checkbox has not been selected.The freed allocated quantity can be redistributed again onto the selected documents during the stock allocation step.

● Stock SelectionThe stock selection step is implemented by the classes that are entered in Customizing under Maintain Rule Types for Hard Allocation for the rule type Stock Selection Rule. On the selection screen for the report. you can select one entry for processing.The following business logic is implemented in class /WOM/CL_HA_DEFAULT_RULES for the stock selection rule:The Customizing settings in Maintain Stock Types for Hard Allocation is taken into account to find suitable stock by storage location and stock type based on the selection. The system determines the stock on hand.The system subtracts the already allocated quantities from stock on hand while taking into account the quantities freed in the free allocation step. This result in the quantity available for allocation.

● Stock AllocationThe stock allocation step is implemented by the classes entered in Customizing under Maintain Rule Types for Hard Allocation for the rule type Stock Allocation Rule.

Application Help for SAP Cross-Channel Order Management for RetailHard Allocation P U B L I C 25

On the selection screen for the report, you can select one entry for processing. The following business logic is implemented in class /WOM/CL_HA_DEFAULT_RULES for the stock allocation rule:The stock allocation takes the quantity available for allocation and distributes it onto the documents from the selection. However, the following scenarios are considered:○ Batches

In case of batch-handled articles, the allocated quantity can come from different batches. Therefore, a batch determination is done.

○ Contracts or CallOffsContract items from which a calloff has been done can no longer be allocated. The calloff must be allocated instead. If a calloff is allocated, the system first tries to use the allocated quantity from the contract and move it onto the calloff.

○ Stock PoolsStock pools can limit the quantity that is available for allocation. If a document contains a stock pool ID for an active stock pool, then for stock pool-relevant articles, the pool quantity of the not closed pool (site-dependent) is used as an upper limit for hard allocation quantity. This means that the following criteria must be fulfilled:○ Stock pool is active○ Article is currently stock pool-relevant for the site○ Pool quantity exists

If a document item is pool-relevant, then the maximum quantity that can be allocated is calculated from the pool quantity, the already HA used quantity for the pool, and any free floating quantity (quantity that is not claimed by any stock pool).

ExampleThere is an HA available quantity of 300 units and the following two pools.

○ Wholesale with pool quantity of 200 and 100 HA used○ Retail with pool quantity of 200 and 50 HA used

For a sales order belonging to the Retail pool, you have a HA available quantity of:

Open pool quantity of Retail pool (150) + free floating quantity

The free floating quantity is calculated as follows:

HA available of 300 – (open pool quantity Wholesale of 100 + Retail of 150) = 50.

Therefore, even if we have an HA available quantity of 300, we can only distribute 200 (150 + 50) onto a sales order from the Retail pool.

NoteThe free floating quantity cannot be less than zero. If it is zero, no additional free floating quantity can be distributed. In this case, each pool can receive up to the open pool quantity (if there is enough HA available).

○ Time-dependent stock poolsHard allocation is also performed for time-dependent stock pools,

○ Stock pools and contractsSince contracts and calloff are in the same pool, shifting allocated quantity from one to another has no impact on the HA used quantity.


Hard Allocation

● Fix AllocationThe stock allocation step is implemented by the classes entered in Customizing under Maintain Rule Types for Hard Allocation for the rule type Fix Allocation Rule.On the selection screen for the report, you can select one entry for processing. The following business logic is implemented in class /WOM/CL_HA_DEFAULT_RULES for the fix allocation rule:During the fix allocation step, it is decided if the allocation becomes fix or reserved depending on the allocated quantities from the allocation step. This is done based on the following criteria:○ Shipping group is active for the document

In this case, allocation can only be fixed if an entire shipping group is free of errors and completely allocated.

NoteYou can overrule this behavior using Customizing for Order Life Cycle Management.

○ Shipping group is not active for the documentIn this case, the decision is based on the release rate. The system creates virtual groups within the sales order depending on the Customizing for the release rate group configuration variant (Maintain Release Rate for Fix Allocation Step). Fix allocation for schedule lines from these groups is done based on two conditions:○ The entire document fulfills the release rate. That is, the sum of all allocated quantities from the

document divided by the sum of the ordered quantities (multiplied by 100) is greater than or equal to the release rate percentage.

○ The group fulfills the group release rate. That is, the sum of all allocated quantities from the group divided by the sum of the ordered quantities (multiplied by 100) is greater than or equal to the release rate percentage.

● Data StorageIn addition to the Execution Mode, you can also execute hard allocation processing in simulation mode. In this case, all changes done in the hard allocation processing are not written to the database. Furthermore, you can specify a variant for the parallelization of processing. The system displays the default variant for the program by default. If the field is empty, the default variant is also used for processing.You can define a Message Log Level especially for the background processing. In this case, the system takes into account messages according to the selected log level.

Activities

1. Select sales orders, contracts, and stock transport orders based on selection criteria, such as customer, article, and so on.

NoteYou can exclude sales orders and items from the allocation workload based upon:○ Delivery block○ Credit block○ Already hard allocated sales orders

2. The system sorts the selected documents using prioritization criteria, such as:○ Document creation time


○ Requested delivery date○ Cancellation date○ Delivery priority

3. The system determines the stock using the stock calculation logic for hard allocation.4. The system allocates the stock based on stock allocation rules.5. The system performs final checks based on fix allocation rules.

5.2 Hard Allocation for Time-Dependent Stock Pools

Time-dependent pools for hard allocation are handled similarly to handling during ATP (available-to-promise). The current date (system date) is compared with the valid-to date at header level for the stock pool. If the system date is after the SP Header Valid To date, open quantity for the pool is not taken into account. Any documents for this pool can only access the free floating hard allocation quantity (these documents are treated like documents that do not have any pool assignment).

NoteThe Stock Pool Header Valid From date is not used during hard allocation. In addition, pools that have this valid-from date in the future block stock for lower level pools and start cumulating used HA quantity.

Example

Pool Priority Open Quantity Valid From Valid To

A 10 50 17.08.2016 29.08.2016

B 20 50 02.08.2016 17.08.2016

C 30 100 07.08.2016 22.08.2016


Hard Allocation

ExampleSystem date is 05.08; stock on hand: 100 (3 valid pools, no free floating quantity)

Example 1

Pool Potentially Available for Allocation of Documents from Pool

A 50

B 50

C 0

ExampleSystem date is 20.08; stock on hand: 100 (2 valid pools, no free floating quantity)

Example 2


A 50

B 0

C 50

ExampleSystem date is 30.08; stock on hand: 100 (no valid pools, free floating quantity is 100)

Example 3


A 100

B 100

C 100


5.3 Hard Allocation Workbench

Use

The Hard Allocation Workbench allows you to make a kind of manual interference or emergency handling for hard allocations for sales orders, contracts, or stock transport orders. It provides additional functions to resolve problems.

The Selection Parameters for the Hard Allocation Processing and the Hard Allocation Workbench are mostly identical.

You can specify generic selection criteria, such as by article or customer for sales documents or by sales document number or purchasing document number for stock transport orders.

In addition to the selection criteria, you can specify a Basic Workload Definition. This means that only a specific kind of documents are considered during the selection. For example, this may be only documents with fix allocated quantities or only documents without any allocations. All documents that do not satisfy these workload definition criteria are excluded from processing.

You can restrict the document workload for the processing to specific document items by using the Process Selected Items checkbox. As a result, only items that fulfill the selection criteria exactly are considered during the selection and processed.

Following two main function blocks are possible within the Hard Allocation Workbench:

● Allocate/Deallocate○ Allocate provides you an opportunity to assign hard allocated quantities to an entire document or

document item depending on the hard allocation rules.You can choose Allocate Full or Allocate Partial from the dropdown list to allocate either full or partial quantity. Partial allocation can be done based on an amount or a percentage.

NoteAllocation is done for each item of the selected sales document. For example, if you decide to allocate a partial amount of 5 to a selected sales order, then all items of this sales order are allocated an additional quantity of 5 each. Quantities calculated out of percentages are rounded commercially.

○ Deallocate allows you to reset hard allocated quantities for an entire document or document item depending on the hard allocation rules. This means that the system considers quantities for items that are already in delivery.You can choose Deallocate Full or Deallocate Partial from the dropdown list to deallocate full or partial quantity. Partial deallocation can be done based on an amount or a percentage. Quantities calculated out of percentages are rounded down to a whole number to be deallocated.

NoteDeallocation is done for each item of the selected sales document. For example, if you decide to deallocate a partial quantity by percentage, say 20%, then all items of the selected sales order are reduced by 20% each.


Hard Allocation

○ With the Toggle function, you can switch fix or reserved allocated quantities for a whole document or document item depending on the hard allocation rules. This means that the system considers quantities for items that are already in delivery.

● Reduce Order QuantityThis function allows you to adjust the ordered quantity of an entire document to the hard allocation situation. This means that the ordered quantity is recalculated considering the sum of goods issue booked quantity and the quantity that is currently in delivery for the document.

NoteThis function is available only at the header level.

Example

Document Item Ordered Confirmed Delivered GI Booked

A 1 10 5 2 3

After executing Reduce Order Quantity, the data appears as follows.

Document Item Ordered Confirmed Delivered GI Booked

A 1 5 5 2 3

As a result, all documents satisfying the initial specified selection criteria are displayed in a list. All the displayed information in the list is aggregated over all document items. If you need a more detailed view of a document, you can choose the Detail pushbutton.

All information is aggregated by additional criteria, for example, article, shipping group, or delivery site.

For more information about the shipping group view, see Shipping Group Display [page 13]

Prerequisites

You have maintained relevant settings for hard allocation under SAP Customizing Implementation GuideSales and Distribution Sales Cross-Channel Order Management for Retail Hard Allocation Workbench .

Features

Hard Allocation Workbench allows you to:

● Perform search and selection for manual interference handling for documents● Perform multiple functions within one session without having the need to save the changes after every

function executed.


● Assign or remove hard allocation quantities and status due to the hard allocation rules.● Adjust ordered quantity to allocated quantity for sales orders and stock transport orders.

Activities

When you exit the application, it is checked if any changes were made during the session. If there are changes, the system displays a result dialog box containing all the changes made during the session. You can Save or Discard the changes to save the data to the database or discard the data. Only then can you exit the application.

Related Information

Executing Functions on Header Level [page 32]Executing Functions on Detailed Level [page 33]

5.3.1 Executing Functions on Header Level

Prerequisites

For more information, see Hard Allocation Workbench [page 30]

Context

You use this procedure to perform functions on the header level.

Procedure

1. Select sales orders, contracts, and stock transport orders based on the selection criteria.2. Execute Allocations/Deallocations or Reduce Order Quantity.3. According to the function selected in the step above, select at least one row and choose the Allocate,

Deallocate or Toggle-HA-Status pushbutton.

The system locks all selected documents. These cannot be processed by someone else. If the system cannot lock a document, then a message is displayed.


Hard Allocation

The changes done in the list are not written directly to the database and are only valid in the current session. You can perform different functions in one session without saving the data after every function.

4. Use the Undo pushbutton to undo the last performed action.

ExampleIf you made a partial allocation, you can choose Undo to change the values back to previous quantities.

NoteThe undo function works only if you have not yet saved the data to the database.

5. If all changes are done, the data can be written to the database using the Save pushbutton.

The system displays a dialog box containing all changes made in the session. You can decide to commit or discard the changes using the Save or Discard pushbutton. After saving, the system releases all locks for the changed documents.

5.3.2 Executing Functions on Detailed Level

Prerequisites

For more information, see Hard Allocation Workbench [page 30]

Context

You use this procedure to perform one of the functions in the detail shipping group view.

Procedure

1. Select sales orders, contracts, and stock transport orders based on the selection criteria.2. Execute eAllocations/Deallocations or Reduce Order Quantity.3. Select exactly one document in the result screen and choose the Detail pushbutton to go to the next

screen.

The system locks the document so that nobody else can perform actions on this document. If the system is unable to lock the document, then a message is displayed.

4. On the next screen, you can perform different functions on different views.


The available views are listed in the ALV tree in the area on the left. Each of these views has a kind of aggregation of the schedule lines, which fulfill the view criteria. You can choose one of the following function pushbuttons for one or several rows.

○ Allocate○ Deallocate○ Toggle HA Status

You can also navigate into the second-level detail screen. To do this, you must select exactly one row and choose the Detail pushbutton on the toolbar. All functions, such as, Allocate, Deallocate, Toggle-HA-Status, are available here and can be performed for one or several lines.

The changes done in the list are not directly written to the database and are only valid for the current session. You can perform different functions in one session without having to save the data after every function.

5. You can save the changes by choosing the Save pushbutton or navigate back to the result screen (at the header level).

The system displays a popup containing all changes made in the session. You can decide to commit the changes or discard the changes. The system releases all locks for the changed documents after changes have been saved.


Hard Allocation

6 Delivery Program Definition

Use

You can define delivery programs ahead of time and plan for the next season. A delivery program is defined through a combination of season, collection, and theme.

A season can define a delivery program, as well as a combination of season and collection or a combination of season, collection, and theme.

When you define a delivery program, you have to specify validities and also make article assignments. The validity of a delivery program is defined through an order window and a delivery window. Furthermore, you can combine the time window definitions with order-related attributes, such as Sales Organization, Distribution Channel, Country, Region, Customer Group, and Customer. For example, you can have different delivery programs with different validities in different countries. This also enables you to have different validities for the same set of articles for different customers or for different regions or countries.

When you enter the Delivery Program Definition transaction, the system displays a hierarchical view on all existing Season-Collection-Theme combinations. You can restrict this list by entering selection criteria on the selection screen. The transaction also allows you to create and change texts of existing delivery programs for several languages. You can delete a delivery program and also copy validities and article assignments.

1. Specify a validityFor more information, see Specifying a Validity for a Delivery Program [page 38].

2. Assign articlesOn the Articles tab, choose the Assign Articles pushbutton to call a search dialog. You can search for the articles by article-related and article hierarchy-related criteria. The system displays a list of articles that fulfill the search criteria. If you add a generic article, a list of single articles which belong to the selected generic article is displayed.

Prerequisites

You have made delivery program-relevant settings in Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Delivery Program .

NoteIn the Customizing, you can:

● Activate the sales area for delivery program search● Deactivate the item types for delivery program definition

Application Help for SAP Cross-Channel Order Management for RetailDelivery Program Definition P U B L I C 35

Activities

1. Define a delivery program.1. Add a season using Delivery Program Definition transaction (/WOM/DLV_PROG).

Enter season short key, short text, and a description.2. Select one or more seasons and add a collection.

NoteThis is an optional step.

Enter collection short key, short text, and a description.3. Select one or more collections and add a theme.

NoteThis is an optional step.

Enter theme short key, short text, and a description.2. Define validities for the delivery program.3. Select either season, collection, or theme and use the Change Text pushbutton to specify additional

information.For example, you can provide some background on why the delivery program exists.

NoteThese text fields are customizable. The Customizing offers the possibility to define up to five fields. Each with its own data type and description. These fields are not used for any application logic. They provide additional information that can be used for reporting purposes.

For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail General Maintain Attributes .

4. Use the hyperlink for Season, Collection, or Theme to navigate to the validities overview screen.5. Choose the Assign Articles pushbutton to assign articles existing delivery programs.6. Select required articles and navigate to the previous screen.

The system displays a value Article Assignments Exist in the DP Status column.



6.1 Uploading Delivery Programs from MS Excel

Context

You can use the Upload Delivery Program (/WOM/DP_UPLOAD) to upload delivery programs from an MS Excel file into the system. The system displays the uploaded data in following three subscreens. These are:

● Delivery Program Texts● Article Assignments● Validities

The system expects the following structure for the MS Excel file:

● Worksheet of Delivery Program Texts○ Column A: Delivery Program Season○ Column B: Delivery Program Collection (empty for season texts)○ Column C: Delivery Program Theme (empty for collection and season texts)○ Column D: Language○ Column E: Description○ Column F: Short Description○ Column G: Attribute 1 (optional)○ Column H: Attribute 2 (optional)○ Column I: Attribute 3 (optional)○ Column J: Attribute 4 (optional)○ Column K: Attribute 5 (optional)

● Worksheet of Article Assignments○ Column A: Article Number○ Column B: Delivery Program Season○ Column C: Delivery Program Collection (empty if assigned on season level)○ Column D: Delivery Program Theme (empty if assigned on season or collection level)

● Worksheet of Validities○ Column A: Delivery Program Season○ Column B: Delivery Program Collection (empty if maintained on season level)○ Column C: Delivery Program Theme (empty if maintained on season or collection level)○ Column D: Sales Organization○ Column E: Distribution Channel (optional)○ Column F: Country (optional)○ Column G: Region (optional)○ Column H: Customer Group (optional)○ Column I: Customer (optional)○ Column J: Delivery Date From○ Column K: Delivery Date To○ Column L: Order Date From


○ Column M: Order Date To○ Column N: Proposal Date (can be empty, 1 or 2)○ Column O: Availability Start (optional)○ Column P: Delivery Date Check (either empty or 1 or 2)○ Column Q: Allow Outside Period (either empty or X)○ Column R: Message Type (either empty or E or W)

Procedure

1. Enter the filename including complete path of the MS Excel file located on your desktop.

Alternatively you can choose the file using the file selector (F4-Help).2. Select Overwrite Existing Data checkbox if you want to overwrite the existing data.

If you do not select this checkbox then existing data is not changed and only new data is inserted.3. The system uploads the data.

NoteYou cannot make changes to the data that has been uploaded in the application. However, you can make changes to the MS Excel and then upload the data again.

6.2 Specifying a Validity for a Delivery Program

Procedure

1. Maintain order-related attributes

These attributes are used to check if the validity fits the order data before starting the actual delivery program search. The fields are only checked if they are filled.

NoteSales Organization is the only mandatory field.

2. Define a delivery window.

Specify Delivery From and Delivery To. The field Delivery Date Check defines how these dates are considered in the check. You can specify that the delivery window is not to be checked at all. This means that the requested delivery date need not fit into the delivery window. You can also specify that the delivery window is checked, which means either the requested delivery date must be after or equal to the Delivery From date or that it is between Delivery From and Delivery To.



NoteThe Delivery From and Delivery To are mandatory fields.

3. Define an order window.

Specify Order From and Order To. The field Allow Outside Period defines if the order window needs to be checked or not. If you select this checkbox then the order window is not checked for this validity.

NoteOrder From and Order To are mandatory fields.

4. Enter Availability Start Date.

The Availability Start Date defines from which date onwards an available-to-promise (ATP) check should be performed for the item, which is assigned to the validity. If the validity is assigned to an item there is no availability check performed before this date. This means that the item is automatically confirmed. If some changes are done to the item, which trigger an ATP on this date or later, then regular ATP check is done and the confirmation is done according to the result of the ATP check.

5. Specify shipping group properties.

The shipping group determination considers the assigned delivery program for the item. The proposal date is the date to which the Confirmed Delivery Date (= schedule line date) is shifted if the confirmation date is no longer fitting into the delivery window. If this date is shifted, then the system displays a message depending on the message type defined in the delivery program validity. The proposal date can take one of the following three different values:

○ Delivery Date FromThe Confirmed Delivery Date on item level is set to Delivery Date From of the chosen delivery program.

○ Delivery Date To:The Confirmed Delivery Date on item level is set to Delivery Date To of the chosen delivery program.

○ No proposalThe Confirmed Delivery Date is not shifted.

Next Steps

Delivery Program Definition [page 35]


7 Working with Stock Pools

Prerequisites

● You have maintained relevant settings for stock pools● You have defined articles that are part of more than one stock pool for your site

For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Stock Pools

Context

You can do a virtual segmentation of your stock quantities over several distribution channels using stock pools. The virtual stock segmentation can be defined individually for articles and distribution centers. This stock segmentation can be used for articles in promotion, for example.

ExampleDistribution Channels Modelled as Stock Pools

The same article can be part of different stock reservations at the same time for different distribution channels (for example, wholesale, retail, and web). Using stock reservation, you can ensure that no sales channel is consuming more than its allotted quantity.

ExamplePromotions Modelled as Time-Dependent Stock Pools



The following diagram shows an example of stock pool reservations for promotions for one article.

The available-to-promise (ATP) logic considers these virtual stock pools while determining the confirmed quantities.

The stock pool process consists of different phases:

● In the planning phase, the planned quantities for the stock pools are entered. You can do this manually or by importing plan data from an external tool (CSV import).

● After the planning phase, quantities are filled up (for example by ordering articles from the supplier or manufacturer).This means that you get more and more documents (purchase orders, sales orders, and stock transport orders) in the system which describe the availability situation. This enables you to validate your stock pool plan against the "real" situation in the system. In order to compare the plan with the current situation, there are rule-based options to match the current quantities with the stock pools (for example, by percentage or by proportion of the planned quantities).

In general, the stock pool life cycle consists of the following steps:

Procedure

1. The stock pool header is created (manually or using an API).2. Maintain articles as stock pool-relevant (manually, using MS Excel upload, or using an API).3. Assign articles on site level to a stock pool4. Change stock pool quantities, article assignment, and status.5. Optionally, you can delete stock pool data, if required. You can also archive data if necessary.6. You can run the stock pool calculation report to adjust the stock pool tables to the current document

situation.

Application Help for SAP Cross-Channel Order Management for RetailWorking with Stock Pools P U B L I C 41

You can run this report using the transaction /WOM/SP_CHECK.

This report is usually planned as a periodic background job. The report reads quantities of all stock pool-relevant documents (sales orders, stock transport orders and so on) and stocks. The report updates the table for stock pool quantities with the current determined data, if the report is not run in the simulation mode.

The report can also be started in the background in update mode, if you select the Calculation Report checkbox in the Stock Pool Workbench.

Related Information

Time-Dependent Stock Pools [page 42]Defining Stock Pools [page 47]Uploading Data from MS Excel [page 49]Uploading Data Using the Stock Pool API [page 50]Maintaining Stock Pool Relevant Articles [page 51]Item-Level Stock Pool Determination [page 52]Working with Stock Pool Workbench [page 54]Deleting Stock Pool Data [page 55]Archiving [page 62]

7.1 Time-Dependent Stock Pools

You can use time-dependent stock pools to give an added time dimension to stock pool management. A time-dependent stock pool has Valid From and Valid To fields on header level. If you have activated time dependency as part of your Customizing settings for stock pools, these fields are mandatory when creating stock pool headers.

You can activate the time dependency setting in Customizing under SAP Customizing Implementation GuideSales and Distribution Sales Cross-Channel Order Management for Retail Stock Pools Maintain

General Stock Pool Settings .

NoteThese header fields are to not to be confused with the validity of the pool relevance for an article. For time-dependent pools, the article must still be relevant for pool handling. Since stock pool handling takes place in addition to the normal ATP (available-to-promise), the confirmed delivery date from the original ATP call is used to determine the pool relevance of the article during the ATP call.



NoteFor the example implementation of item level stock pool determination, the time period described by the Valid From and Valid To fields for time-dependent pools is checked against the confirmed delivery date. For this check, Valid From is adjusted by Header Attribute 8 (assumed lead time) for check purposes.

Stock Pool Workbench

When starting the Stock Pool Workbench, the selection for Time Period Validity is prefilled with the system date. Only pool assignments which fall into this selection according to the SP Header Valid From and SP Header Valid To are displayed.

The time dependency validity interval of stock pools impacts the calculation result as follows:

● System date is before the date in the SP Header Valid From fieldPool quantity is calculated as normal by considering pool priority from header data. All open quantities from stock pools that fulfill this condition are taken into account.

● System date is after the date in the SP Header Valid To fieldThe SP Article Status is set to I – Inactive and cannot be changed. The overall status is Red = Error.Available pool quantity is not calculated for pools for which the system date is after the SP Header Valid To date. The open quantity for these pools is also not considered when calculating quantity for other pools. That is, stock pools that have a SP Header Valid To date that lies in the past are no longer considered in the Stock Pool Workbench.

ATP (Available-to-Promise)

The time dependency validity interval of pools impacts the calculation result as follows:

● Confirmed Delivery Date is after the date in the SP Header Valid To fieldIf pool determination is on header level, the stock pool ID is found even if the confirmed delivery date is outside the time period specified by the SP Header Valid From and SP Header Valid To fields of all the articles in the document.During determination of available quantity, if the document belongs to a stock pool that is no longer valid, then it automatically receives the lowest priority (99) and is eligible for free floating quantity. The open quantity for pools that have a confirmed delivery date that is after the date in the SP Header Valid To is no longer taken into account and is also not blocked in ATP.

● Confirmed Delivery Date is before the date in the SP Header Valid From fieldThe document receives the normal priority based on the determined pool, and the pool's open quantity is taken into account. In addition, the open quantity of other pools that have a confirmed delivery date that is before the date in the SP Header Valid From field is taken into account during calculation. The quantity for other pools is blocked for the Valid From date.


Basic Stock Pool Compared with Time-Dependent Stock Pools

The basic (not time-dependent) stock pools only collect quantity up to a limit (plus free floating quantity, if allowed). This means that these stock pools only cover the quantity dimension. The only constraint regarding the time dimension is that pools with a higher priority receive confirmed quantity before stock pools with a lower priority. This is achieved by blocking the open quantity of higher priority pools for the system date in ATP.

ExampleBlocking Quantity with Basic Stock Pools (No Time Dependency)

● Pool A: Open quantity 100, priority 10● Pool B: Open quantity 100, priority 20

ATP quantity: 100 Stock on hand (today 15.08); 100 goods receipt (PO) planned for 22.08; sales order for pool B with order quantity 10 and requested delivery date for 17.08.

Since Pool A is blocking the entire stock on hand for the sales order for Pool B (lower priority), the next possible confirmed delivery date will be 22.08.

Using above principle, time-dependent pools work on two dimensions. They limit the pool available quantity by the upper limit set for the pool (quantity dimension) and block ATP quantity at a specific point in time (time dimension). The difference is that for time-dependent pools, this is not blocked according to the current date, but according to the start date of the respective pool, which can also be in the future. Each time-dependent pool blocks its open quantity so that it cannot be used by other pools.

NoteIf the pool's start date is in the past, the block date is set to the current date in the system. Lower priority pools only block quantity if Limited Priority is set in Customizing. Higher and equal priority pools block their open quantity if enough ATP quantity is available. If there is not enough ATP quantity, the blocked quantity is reduced, beginning with the lowest priority block.

The blocking and reserving mechanism for time-dependent pools uses standard ATP functionality. The block for a pool with an open quantity of X units has the same effect on other pools as, for example, a sales order with a confirmed quantity of X.

For the following examples, limited priority is active and free floating quantity is not excluded for any pool.

ExamplePool Quantity Blocked Before Purchase Order




A 10 50 05.08.2016 31.12.2016

B 20 50 01.01.2016 31.12.2016

C 30 100 10.08.2016 31.12.2016

ATP quantity as of today (01.08): 100 stock on hand; 100 goods receipt (PO) planned for 15.08.

Based on this scenario, the earliest confirmed delivery date for a Pool B sales order is 15.08 (when the purchase order arrives). Before that, all available quantity is blocked by Pool A and C. The maximum confirmed quantity would be 50.

ExamplePool Quantity Blocked After Purchase Order


A 10 50 05.08.2016 31.12.2016

B 20 50 01.01.2016 31.12.2016

C 30 100 15.08.2016 31.12.2016

ATP quantity as of today (01.08): 100 stock on hand; 100 goods receipt (PO) planned for 10.08.


Based on this scenario, up to 50 units can be confirmed for a Pool B sales order starting today (01.08). Since the valid from date for Pool C is after the goods received date of the purchase order, the Pool C block quantity is subtracted from the purchase order quantity. This leaves 50 units (100 stock minus 50 block quantity from Pool A) available for Pool B.

ExamplePool Quantity Blocked after Replenishment Lead Time


A 10 50 05.08.2016 31.12.2016

B 20 50 01.01.2016 31.12.2016

C 30 100 20.08.2016 31.12.2016

ATP quantity as of today (01.08): 100 stock on hand; 100 goods receipt (purchase order) planned for 10.08. End of replenishment lead time for the article is 15.08.



Based on this scenario, up to 150 units blocked (100 stock minus 50 Pool A block plus 100 from purchase order) can be confirmed for a Pool B sales order starting today (01.08) until the end of replenishment lead time. Only the quantity from Pool A is blocked because the Valid From date for Pool C is after the end of replenishment lead time. As a result, Pool C has no effect on an ATP check executed today (01.08).

7.2 Defining Stock Pools

Prerequisites

● You have maintained stock pool definitionrelevant information using application ID STOCKPOOL.For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail General Maintain Attributes

● You have activated the Time Dependency checkbox, for time-dependent stock pools.For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Stock Pools Maintain General Stock Pool Settings


● You have defined the additional attributes for Additional Selection Criteria for Customer Attributes.For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail General Maintain Attributes

Procedure

1. Execute the stock pool header definition transaction (/WOM/SPID).

The system displays all defined stock pools.

NoteFor time-dependent stock pools, execute transaction /WOM/SPIDN. Enter the relevant details in the Stock Pool Header with Selection screen.

2. You can add new stock pool IDs or change the descriptions and status of existing stock pools.3. To define a new stock pool, choose the New Entries pushbutton or copy an existing stock pool.4. Enter a new stock pool ID and the corresponding stock pool status and description.

You can also assign a stock pool group to your stock pool. A stock pool group can be used for authority checks.

NoteYou have defined stock pool groups in Customizing.

5. You can assign a priority ranging from 1 to 99 to the stock pool.

Priority 1 is the highest priority. If Priority is left empty, the system sets a priority of 99, which is the lowestpriority.

The pool priorities are interpreted based on the Customizing settings for stock pool logic. The following options are available:

○ Full PriorityThis means that a stock pool can use available quantities from stock pools with lower priority without restrictions. However, shortage situations are handled separately for each priority level.

○ Limited PriorityExcept in the case of a shortage situation, each stock pool can only receive the free floating quantity in addition to its open quantity. Free floating quantity is defined as the available quantity minus the open quantity from other stock pools.

NoteFor free floating quantity, the system does not consider the priority of stock pools. All pools are considered equal when calculating free floating quantity

In a shortage situation, for example, when available quantity does not cover the sum of the open quantity of all stock pools; stock pools with a higher priority reserve quantity from stock pools with a lower priority.



For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail General Activate Switches on Site Level.

6. Save your data.

Next Steps

Working with Stock Pools [page 40]

7.3 Creating and Maintaining Stock Pool Data

You can create and maintain stock pool data in the following ways:

● Manual maintenanceYou can create and change stock pools manually with the user interface directly in the system. If time-dependent pools are activated, the stock pool header validity period can be maintained and is also available in the selection criteria for pools during header maintenance and article assignment.

● Upload using MS ExcelYou can upload article assignments to a stock pool with its quantities from MS Excel. In addition, you can also upload 10 freely definable attributes at the stock pool header level and 3 freely definable attributes at the article assignment level. In order to upload from MS Excel, the matching stock pool header must be created before you start.

● Upload using APIsYou can import stock pool headers (including stock pool header attributes), article relevance for pool handling, and the article assignments into the system with an RFC function.

7.3.1 Uploading Data from MS Excel

Context

You can use the upload program (/WOM/SP_UPLOAD) to load planned stock pool quantities from an MS Excel file into the stock pool tables.

The system expects the following structure for the MS Excel file:

● Column A: Stock Pool ID● Column B: Site (DC)● Column C: Article Number (Variant)


● Column D: Planned Quantity for this Stock Pool/Article● Column E: Unit of Measure for Quantity● Column F: Valid From● Column G: Valid To

NoteIf there is no time dependency for the stock pools, the system does not consider the values in column F and G.

Procedure

1. Enter the file name including complete path of the MS Excel file located on your desktop.

Alternatively you can choose the file using the file selector (F4-Help).2. Select Excel Contains Header Line if the first line of MS Excel sheet contains a header line.

In this case, the import ignores the first row of MS Excel.3. Select Overwrite Existing Data checkbox if you want to overwrite the existing data.

If you do not select this checkbox, then existing data is not changed and only new data is inserted.4. The system displays loaded data in an ALV list including any messages.

You can now save the loaded data. The system does not save data with errors.

Next Steps


7.3.2 Uploading Data Using the Stock Pool API

As an additional option for maintaining stock pools, you can use an RFC-capable function module. This RFC function allows you to maintain stock pool header information, maintain article assignment to stock pools, and maintain article relevance for stock pools. These processing blocks are only executed if the corresponding import parameters are filled.

Based on the transferred stock pool ID, the function module either creates a new stock pool header (with new article assignment or a new article relevance to be added) or modifies existing objects (header, relevance, assignment):

● If a stock pool ID is transferred to the function module, the corresponding stock pool data is modified using the transferred data. If no stock pool exists with this ID, a new set of pool data is created.



● If no stock pool ID is transferred to the function module, then the system tries to find a matching stock pool ID using the BAdI Enhance Standard Logic for Stock Pool determination within API. If a matching pool can be found, the corresponding stock pool data is modified using the transferred data.If the BAdI is not implemented or no stock pool ID can be found, the function module assigns the "next" stock pool ID from a stock pool number interval (object /WOM/SP_ID, interval 01). If a pool exists with this ID, the corresponding data is modified; otherwise a new set of pool data is created.

ExampleStock Pool ID Determination within API

The example implementation (/WOM/CL_EX_IM_SP_DET_API) provided with the BAdI Enhance Standard Logic for Stock Pool determination within API uses the stock pool header attributes Promotion, Sales Organization, and Distribution Channel. For this, the attributes must be configured as follows:

● Attribute 1: Promotion● Attribute 3: Sales Organization● Attribute 4: Distribution Channel

The stock pool ID is then determined based on matching attributes from the input structure and the pool header configuration.

7.4 Maintaining Stock Pool Relevant Articles

Context

You use this procedure to maintain articles that you want handle in stock pools. You can add articles and change the validity of stock pool handled articles. You can also change the article status to one of the following statuses:

● Active: Article is active and can be considered in stock pools depending on the validity date and stock pool status.

● Planning: Article is in planning and is not considered in stock pool checks.● Inactive: Article is deactivated and is not considered in stock pool checks.

Procedure

Adding Articles as Stock Pool-Relevant1. Execute a selection using Stock Pool Relevant Articles (/WOM/SPREL)

You can use any selection criteria to retrieve articles.2. The system displays a list of already maintained articles according to the selection criteria.


3. Choose the Add Article pushbutton and enter selection criteria to select the possible articles.

The system displays a list with the selected articles.4. Select your articles and enter the article-relevant status and the validity period by specifying Start Date

and Valid To.5. Choose the Add and Close pushbutton to add the articles and exit the dialog box.

If you want to stay in the dialog box to add other articles with a different validity, then you can choose the Add pushbutton and repeat Steps 4 and 5.

6. Save your data.Changing Validity of Stock Pool-Relevant Articles7. Execute a selection using Stock Pool Relevant Articles (/WOM/SPREL).

You can use any selection criteria to retrieve articles.8. The system displays a list of already maintained articles according to the selection criteria.9. For the required article, change the Valid To Date and or the article-relevant Status.10. Save your data.

Mass Changing Validities of Stock Pool-Relevant Articles11. Execute a selection using Stock Pool Relevant Articles (/WOM/SPREL).

You can use any selection criteria to retrieve articles.12. The system displays a list of already maintained articles according to the selection criteria.13. Select one or more articles from the list and choose the Mass Change pushbutton.14. Change the Valid To Date and or the article-relevant Status and choose the Change pushbutton.

The system changes data for the selected articles in the list.15. Save your data.

Next Steps


7.5 Item-Level Stock Pool Determination

You can activate pool determination at item level in Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Stock Pools Maintain General Stock Pool Settings .

This allows you to implement the determination of stock pool ID using the BAdI: Stock Pool Determination at Item Level.



ExampleSince the actual logic for determining stock pool IDs is highly customerspecific, only an example implementation for the BAdI is provided. This example implementation uses a specific configuration for the following stock pool attributes:

● Attribute_1 for PROMOTION● Attribute_3 for VKORG● Attribute_4 for VTWEG● Attribute_5 for SPART● Attribute_8 for LEADING TIME of SP

If the promotion number matches, the stock pool is selected. Otherwise, the pool ID is taken from a pool with matching sales organization attributes.

NoteFor time-dependent pools, the example implementation for pool determination on item level also checks the Valid From and Valid To date at stock pool header level where the Valid From date is adjusted by Attribute_8 (LEADING TIME of SP).

This means that, for example, a sales order that has a confirmed delivery date before the adjusted validity of the pool does not contribute to the pool. This is different from the handling for pool determination on header level, where a sale order with a confirmed delivery date before the Valid To date at stock pool header level contributes to the pool.

BAdI Methods

The BAdI provides two methods: one for pool determination for ATP-relevant items, and one for pool determination of items that are not ATP-relevant.

● For sales order or contract: Method SP_DET_FOR_ITEM is called during ATP check. If no ATP has been executed, then method SP_DET_FOR_ITEM_WO_ATP is called when saving the sales order or contract.

● Stock transport order: Method SP_DET_FOR_ITEM is called during ATP check. If no ATP has been executed or no SPID can be identified during ATP, then method SP_DET_FOR_ITEM_WO_ATP is called during item processing.

● Delivery: Method SP_DET_FOR_ITEM is called when saving the delivery if no predecessor document (sales order or stock transport order) can be found. If a predecessor document exists, stock pool determination is done during the handling for the predecessor.


7.6 Working with Stock Pool Workbench

Context

You can use the Stock Pool Workbench to change your stock pool quantities, article assignments, and status.

You can use any selection criteria to retrieve article or stock pool combinations that were defined earlier. You can also decide to run the calculation report in the background to get up to date data for the selected articles.

NoteIf you choose not to run the report in the background, then processing is faster because the system displays the data stored from the last run.

The transaction /WOM/SPWB_DISPLAY opens the Stock Pool Workbench in display-only mode.

Procedure

Transferring Single or Multiple Articles Across Stock Pools1. Execute a selection using the Stock Pool Workbench transaction /WOM/SPWB.

You can use any selection criteria to retrieve article or stock pool combinations that were defined earlier.2. You can do one of the following.

○ Transfer multiple articles1. Select one ore more articles for which a quantity transfer should be initiated.2. Select the stock pool that should act as the receiving pool.3. Select the method of transfer and choose the Transfer pushbutton.

○ Transfer single article1. Choose the Transfer pushbutton on the article row.2. Select the stock pool that should act as the receiving pool.3. Enter a transfer quantity and choose the Transfer pushbutton.

3. You can repeat the previous steps with different transfer options.4. Save your data.

Recalculating Stock Pool Data5. Execute a selection using the Stock Pool Workbench transaction /WOM/SPWB.

You can use any selection criteria to retrieve article or stock pool combinations that were defined earlier.6. Make any of the changes defined above.7. Choose the Calculate pushbutton.

The system recalculates the data.



8. Save your data.Adding Articles to Stock Pool9. Execute a selection using the Stock Pool Workbench transaction /WOM/SPWB

You can use any selection criteria to retrieve article or stock pool combinations that were defined earlier.10. Choose the Add Article pushbutton.11. Enter selection criteria to determine the articles.12. Choose the Next pushbutton to display the result list.13. Select one or more articles from this list and choose the Next pushbutton to navigate to the list of possible

stock pools.14. Select one or more stock pools and choose the Finish pushbutton.

The article is now assigned to the chosen stock pool and displayed in the Stock Pool Workbench list.15. Save your data.

Mass Changing Data for Selected Stock Pools16. Execute a selection using the Stock Pool Workbench transaction /WOM/SPWB.

You can use any selection criteria to retrieve article or stock pool combinations that were defined earlier.17. Select one or more stock pools from the list and choose the Mass Change pushbutton.

The system displays the Mass Change dialog box.18. Enter Pool Quantity and or SP Article Status and choose the Change pushbutton.

The system changes the data for the selected stock pools.19. Save your data.

Next Steps


7.7 Deleting Stock Pool Data

Context

You use this procedure to delete stock pool data from the appropriate database tables. This deletion is done using the Deletion Report, which is run periodically as a background job.

The stock pool header data can only be deleted if:

● There is no active (not archived) sales order using the stock pool ID in the system.● There is no active (not archived) STO using the stock pool ID in the system.


● There is no customer master data using the stock pool ID in the system.

Procedure

1. Execute a selection using the deletion report (transaction /WOM/SPDEL).

NoteFor time-dependent stock pools, execute the transaction /WOM/SPDELN

You can use any selection criteria to retrieve article or stock pool combinations that were defined earlier. You can select one the following checkboxes:

○ Consider Assigned DocumentsIf you select this checkbox, the report takes in to consideration the assignments made to other documents such as sales orders, stock transport orders and so on.

○ Delete Data with HeaderIf you select this checkbox, then the stock pool header data (/WOM/SP_CUST_HD), stock pool quantities (/WOM/SP_QUAN, /WOM/SP_QT_CHK) and stock pool documents (/WOM/SP_DOCS) are deleted.

○ Delete SP Data (without header)If you select this checkbox, then stock pool quantities and stock pool documents are deleted.

○ Delete SP Article Relevant DataIf you select this checkbox, then stock pool article-relevant data is deleted.

○ Stock Pool GroupYou can group different stock pools into one stock pool group with this option.

○ Valid To Date (SP Relevance)You can select data based on the validity of the stock pool relevance.

○ Valid To Date (SP Header)You select stock pools based on the validity date by the header data. This option is only visible if time dependency has been activated in Customizing.

○ Simulation modeIf you select this checkbox, then the deletion report is executed without the database update. This means that checks and protocol are executed, but no data is deleted.

NoteYou can include attributes under Additional Selection Criteria for Customer Attributes. The attributes can be customized under SAP Customizing Implementation Guide Sales and Distribution SalesCross-Channel Order Management for Retail General Maintain Attributes .

2. The system deletes the data according to the option selected in the previous step.



Next Steps



8 Working with Standalone ATP Sales Grid

Use

The standalone available-to-promise (ATP) Sales Grid enables you to get the ATP situation without having to navigate into the maintenance transactions for sales order or contracts.

The activation for the standalone ATP sales grid is the same as the embedded grid.

The result screen of the standalone ATP sales grid is divided into following three areas:

● The first area describes the characteristic value that are chosen as a fix, if an article owns more than two characteristic values. For example, if the used generic article has only two values, then this area is not displayed.

● The second area contains ATP quantities for all variants of the entered generic article. This information is already known from the embedded ATP sales grid.

● The third area contains the hard allocation situation for the generic article and its variants. The hard allocation grid shows the quantity for each variant of the entered generic article that can be hard allocated.

Furthermore, if an article is used in a stock pool, then you get a hint in the ATP sales grid and the HA grid that the quantities displayed for the article variants can deviate because of their usage within stock pools. You can choose to navigate directly in the stock pool workbench (only in display mode) and get more details for the article variants.

Prerequisites

You have maintained Customizing tables for the ATP Sales Grid. You can maintain activation criteria for combinations of sales organization, distribution channel, division, and sales document type.

For more information, see Customizing under SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail ATP Grid Maintain Settings for ATP Grid .

Process

1. Start the transaction /WOM/ATPGRID.The system displays the selection screen.

2. You have to enter at least a generic article, a site, and select either ATP Quantities or Hard Allocated checkbox.The checkbox With Requirement Quantities allows you to calculate the total requirement quantities during the ATP calculation. If you do not select this checkbox, then only the confirmed quantities are considered during the ATP calculation.


Working with Standalone ATP Sales Grid

3. Choose Execute pushbutton.4. If the generic article has more than two characteristic values, then you have to choose which characteristic

values should be displayed and which characteristic value should be handled as a fix.The system displays ATP Sales Grid.

5. If the generic article has more than two characteristic values, then first grid containing the characteristic values is chosen as fix. You can double-click these characteristic values to change their value.The system recalculates all quantities in the ATP sales grid and hard allocation grid.

6. If the variants of the generic article are used in stock pools, then the system displays a pushbutton that allows you to navigate directly to the Stock Pool Workbench and get more details on the article variants.

NoteThe Stock Pool Workbench is only available in display mode. You cannot make any changes.

Application Help for SAP Cross-Channel Order Management for RetailWorking with Standalone ATP Sales Grid P U B L I C 59

9 Order Life Cycle Management

Order life cycle management (OLM) is a reporting tool with a single point of entry for sales orders, contracts, and stock transport orders (STO). You use OLM to:

● Select orders and or contracts by order-related selection criteria such as, Article, Delivering Site, Sales Document Number, Sales Area and so on to get a list of orders. You can also specify that you want to display exceptions that occur during the order life cycle.

● Bundle messages to exception classes.● Select orders only with exceptions and by exception classes.● Navigate to order maintenance or to allocation workbench and see details.

NoteWhen you resolve an exception during navigation to another function, the exception disappears from this list.

Prerequisites

You have made OLM-relevant settings in Customizing, such as defined exception classes, assigned messages to exception classes, and set up pushbuttons for navigation to other applications.

For more information, see SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Order Lifecycle Management .

Features

In OLM, there are different tabs for different document types, such as sales orders, stock transport orders, and contracts.

Additionally, there are pushbuttons for navigation to other functions. When you choose the hyperlink for the order number, the system calls the maintenance transaction for the respective order type. You can display the exceptions for the orders by choosing the traffic light symbol in the Exception column. The traffic light indicates if messages exist for the order and the severity level of the exceptions for the order. When you choose the Refresh pushbutton, the system refreshes the exception list and the order list.

Activities

Execute transaction /WOM/OLM (Order Life Cycle Management).


Order Life Cycle Management

10 Operations Information

Certain administrative activities are required for the proper functioning of SAP Cross-Channel Order Management for Retail. These are periodic activities that affect areas of data integration, data consistency, and system performance. The following activities are specific to the solution:

● Monitoring [page 61]● Archiving [page 62]● System Administration and Management [page 63]● Software Change Management

SAP transport tools have to be used. The add-on development can be found within the package /WOM/MAIN.

● Troubleshooting [page 64]

10.1 Monitoring

Use

Order Life Cycle Management (OLM) is the central monitoring tool. It is used to collect and review all document based exceptions.

Exceptions can be assigned to exception classes in OLM Customizing. For more information, see SAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order Management for Retail Order Lifecycle Management Assign Message to an Exception Class .

Certain assignments are preconfigured and can be reviewed in OLM Customizing. For more information, seeSAP Customizing Implementation Guide Sales and Distribution Sales Cross-Channel Order

Management for Retail Order Lifecycle Management Assign Message to an Exception Class (Standard) .

The messages can be separated by the different stages of the order life cycle using exception classes.

Features

● Alert MonitoringAlert monitoring using application log can be activated in OLM. For more information, see SAP MenuLogistics Retailing Cross-Channel Order Management for Retail General Functions Message Logging Configuration. .The messages are collected in the application log under object /WOM/ALL.Messages of message type as “A Cancel” are forwarded by the OLM message framework to the CCMS. These messages are used by the application to indicate severe system failure.

Application Help for SAP Cross-Channel Order Management for RetailOperations Information P U B L I C 61

To check this messages, the CCMS Monitor can be configured (transaction RZ20) in the following way:1. Enable the maintenance functionality (Extras - Activate Maintenance Functionality).2. Create a new alert monitor.3. Enhance the subtree for your system or instance.4. Select CCMS MsgLog for Cross ChOrdMgt for Retail.5. Generate your monitor.

For more information about CCMS, see http://help.sap.com SAP NetWeaver SAP Netweaver 7.0Application Help SAP Library SAP NetWeaver SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring System Monitoring with CCMS Monitoring in the CCMS .

● Error LogsThe exceptions are collected into the table /WOM/MESSAGES. Document-related exceptions from this table can be reviewed using OLM.The messages in the table /WOM/MESSAGES are invalidated by the applications. These messages are not deleted so they are still available for reference purposes.

● Workload MonitoringThe default tools, namespace for add-on is /WOM/.

● Background Job MonitoringNo default background jobs are delivered.The following functions run in the background and provide log information into job log and spool, if requested.○ Hard Allocation Report (/WOM/HARD_ALLOCATION)○ Shipping Group Recalculation (/WOM/SG_RECALCULATE)○ Stock Pool Calculation (/WOM/STOCKPOOL_CHECK)

10.2 Archiving

You can archive data that you no longer need operatively.

During the archiving of sales orders (archiving object SD_VBAK) and stock transport orders (archiving object MM_EKKO), the corresponding entries from the stock pool documents table (/WOM/SP_DOCS) are also deleted. In order to keep the fill grade of the pool intact during archiving, table /WOM/SP_DOCS_QTY keeps track of the archived goods issue quantity. This quantity is kept in the pool, even if the table is rebuilt using transaction /WOM/SPREBUILD (Stock Pool Consistency Check).

ExampleStock Pool 001 for Article A contains a confirmed quantity of 20, with 10 goods issued (GI). Two sales orders are in the stock pool: 1001 (10 goods issue quantity) and 1002 (10 confirmed quantity). Order 1001 has been archived. In this case, the stock pool's confirmed and goods issue (GI) quantity remain the same (20 confirmed and 10 GI), but the GI archived quantity is increased by 10. When the pool is rebuilt, the 10 GI archived quantity is added again to the 10 confirmed from Order 1002, since Order 1001 is no longer available.


Operations Information

http://help.sap.com

10.3 System Administration and Management

Use

This chapter contains tasks performed by an administrator.

Features

● Technical configuration impacts the following topics○ Configuration for parallelization

Certain functions, such as, Hard Allocation Workbench, Hard Allocation Report and so on, rely on parallelization to improve performance. The settings for parallelization are combined into variants that can be selected within the application. If no variant can be selected, the variant marked as Default is used.Variants can be created using Paralleliz. Settings per Application. For more information, see SAP Menu Logistics Retailing Cross-Channel Order Management for Retail General FunctionsParalleliz. Settings per Application.

○ Activation of additional tracesUsing the transaction SAAB, additional traces can be activated for hard allocation and shipping group calculation. The traces can be displayed using the Tracefile Reader.For more information, see SAP Menu Logistics Retailing Cross-Channel Order Management for Retail General Functions Tracefile Reader.

○ Message LoggingMessage logging can be configured using Message Logging Configuration. For more information, see

SAP Menu Logistics Retailing Cross-Channel Order Management for Retail General FunctionsMessage Logging Configuration.

● Backup and RecoveryMost of the applications from the add-on are using tables in /WOM/ namespace to manage additional data. This data has to be checked or synchronized after an incomplete recovery.Data inconsistencies in the area of allocation can be removed using tools provided by the solution.For more information, see SAP Menu Logistics Retailing Cross-Channel Order Management for Retail Hard Allocation Hard Allocation Reset.Other inconsistencies have to be considered on a case by case basis.

● Periodic TasksPeriodic reorganization of data, such as, messages could be beneficial. The frequency depends on the data volume.For more information, see SAP Menu Logistics Retailing Cross-Channel Order Management for Retail Reorganization

● User ManagementThe area menu /WOM/MAIN_MENU can be included into user roles as needed.For more information about the authorization objects, see the Master Guide for SAP Cross-Channel Order Management for Retail at http://help.sap.com/wom.

Application Help for SAP Cross-Channel Order Management for RetailOperations Information P U B L I C 63


● Load Balancing and ScalabilityParameters influencing the parallelization such as, blocksize, servergroup, maximum number of parallel processes can be configured on the application level.For more information, see SAP Menu Logistics Retailing Cross-Channel Order Management for Retail General Functions Paralleliz. Settings per Application .

10.4 Troubleshooting

● Order Life Cycle ManagementThe main tool for troubleshooting is the Order Life Cycle Management Workbench (OLM). The document-based exceptions are logged here using the OLM message framework. Exception classes can be used to group the messages and identify the area in which the exception occurred, such as shipping group, hard allocation, delivery creation, and so on.

● Set appropriate log levelYou can set the level of message logging during background processing to the following levels:○ Log All Messages○ Log Errors and Warnings○ Log No Messages○ Log Only Errors

● Additional tracesIf you need a deeper analysis, you can activate traces for shipping group calculation and hard allocation. The following checkpoint groups are available for this purpose in the transaction SAAB:○ Shipping Group Protocol (/WOM/SG_PROT)○ Write Protocol of Hard Allocation (/WOM/HA_PROT)

To activate additional logging, set assertions (foreground) to Log on the Activation tab. You can view the logs using the Tracefile Reader.For more information, see SAP Menu Logistics Retailing Cross-Channel Order Management for Retail General Functions Tracefile Reader .

● Checkpoint groups for debuggingFor debugging purposes, certain checkpoint groups can also be activated in the transaction SAAB:○ Stock Pool (and Delivery Program) /WOM/SP_ATP ATP○ Checkpoint Group for SG Tab in Sales Order /WOM/SG_SO○ Parts belonging to Parallel Selection /WOM/SEL_PARALLEL○ Checkpoint Group for Generic Selection in /WOM/SEL○ Checkpoint Group for Central UI component /WOM/GRID○ Delivery Program Save /WOM/DP_SAVE○ Delivery Program Breakpoints /WOM/DP


Operations Information

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: https://help.sap.com/viewer/disclaimer).

Application Help for SAP Cross-Channel Order Management for RetailImportant Disclaimers and Legal Information P U B L I C 65

https://help.sap.com/viewer/disclaimer

go.sap.com/registration/contact.html

© 2018 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see https://www.sap.com/corporate/en/legal/copyright.html for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

https://www.sap.com/corporate/en/legal/copyright.html

Application Help for SAP Cross-Channel Order Management ...

Documents

Transcript of Application Help for SAP Cross-Channel Order Management ...