stock balancing management - sap help portal · stock balancing management ... (stock transport...

User GuideStock Balancing ManagementDocument Version: 1.0 – 2013-06-28

CUSTOMER

Stock Balancing Management

2CUSTOMER© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Stock Balancing ManagementTypographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, table names, and key concepts of a programming language when theyare surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,names of variables and parameters, source text, and names of installation, upgrade anddatabase tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as theyappear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characterswith appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

Stock Balancing ManagementDocument History

CUSTOMER© 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

Document History

Version Date Change

1.0 2013-06-28 Final Version


Stock Balancing ManagementTable of Contents

Table of Contents

1 Overview ...................................................................................................................................................61.1 Prerequisites ............................................................................................................................................................ 71.2 Assumptions ............................................................................................................................................................ 71.3 Logon and Site Authorization ................................................................................................................................. 7

1.3.1 Authorizations ......................................................................................................................................... 71.3.2 Notes ........................................................................................................................................................ 7

1.4 List of Abbreviations ................................................................................................................................................ 81.5 Screen Overview ...................................................................................................................................................... 8

2 Screen Layout for Stock Balancing Management Introduction ............................................................92.1 Tool Bar - SAP GUI Status..................................................................................................................................... 102.2 Selection Area ........................................................................................................................................................ 12

2.2.1 Selection in Manual Scenario ............................................................................................................... 142.2.2 Selecting Stock Transfer Documents ................................................................................................. 152.2.3 Selection for Worklist Scenario ........................................................................................................... 162.2.4 List of Functions in the Selection Area ................................................................................................20

2.3 Screen Area – Header Data .................................................................................................................................. 232.3.1 Header Data Detailed View ................................................................................................................... 23

2.4 Screen Area – Item Data ....................................................................................................................................... 252.4.1 Store-to-Store Stock Transfer ............................................................................................................. 262.4.2 Stock Transfer Store – Distribution Center - Store ........................................................................... 262.4.3 List of Functions in the Item Area ........................................................................................................ 28

2.5 Stock Transfer Process ........................................................................................................................................ 302.5.1 Manually Controlled Stock Transfer ................................................................................................... 302.5.2 Stock Transfer from Worklist ............................................................................................................... 322.5.3 List of Functions in the Store Assignment Dialog Box ....................................................................... 33

2.6 Stock Transfer Document (Stock Transport Order) .......................................................................................... 352.6.1 General ................................................................................................................................................... 352.6.2 Purchase Order Creation...................................................................................................................... 35

3 Overarching Functionalities .................................................................................................................. 373.1 BW Data Transfer .................................................................................................................................................. 37

3.1.1 General ................................................................................................................................................... 373.1.2 Calling the Enrichment Report ............................................................................................................. 37

3.2 Reorganization Report .......................................................................................................................................... 383.2.1 General ................................................................................................................................................... 383.2.2 Calling the Reorganization Report ....................................................................................................... 39

4 List of Business Add-Ins (BAdIs)........................................................................................................... 414.1 /STWACS/X_COLUMN_NAMES (Fill Article Column Names) ......................................................................... 414.2 /STWACS/X_DC_QTY_PROPOSAL (DC Quantity Proposal for DC to Store Process) .................................. 414.3 /STWACS/X_MANDATORY_QTY (Mandatory Quantity Determination) ........................................................ 424.4 /STWACS/X_QUANTITY_DISTRIBUTE (Stock Quantity Distribution across Articles) ................................. 42

Stock Balancing ManagementTable of Contents


4.5 /STWACS/X_SENDER_QT_DISTRIBUTE (Distribute Sender Quantity to Respective Receiversacross Articles) ..................................................................................................................................................... 43

4.6 /STWACS/X_DELIVERY_DATE (BAdI to fill Delivery Date).............................................................................. 444.7 /STWACS/X_PLAUSI_CHECK (Plausibility Check) .......................................................................................... 444.8 /STWACS/X_PURCH_ORG (Determination of Purchasing Organization Data) ............................................ 454.9 /STWACS/X_STOCK_IDENT (Stock Identification) ......................................................................................... 464.10 /STWACS/X_STOCK_UNIT (Stock Unit Handling) ............................................................................................474.11 /STWACS/X_STORAGE_LOCATION (Storage Locations) ...............................................................................474.12 /STWACS/X_SET_NODE_TXT_ARTICLE (Set Article Node Texts) ................................................................ 484.13 /STWACS/X_STORE_CLASS (Determination of Store Classifications (Sender vs. Receiver)) ................... 494.14 /STWACS/X_STORE_DIST (Store Distribution/Assignment Rules) .............................................................. 494.15 /STWACS/X_STORE_SELECT (Store Selection from DB) .............................................................................. 504.16 /STWACS/X_ENR_ACTUALITY (Actuality (Quantities) Handling within Enrichment Report)...................... 514.17 /STWACS/X_ENR_DELIV_DATE (Delivery Date Initialization within Enrichment Report) ............................ 514.18 /STWACS/X_ENR_DOUBLETS (Doublet Handling within Enrichment Report) ............................................ 524.19 /STWACS/X_ENR_GROUP (Grouping of Work List Entries within Enrichment Report) ............................... 534.20 /STWACS/X_ENR_PLAUSI (Plausibility Checks and Adjustments within Enrichment Report) .................. 544.21 /STWACS/X_ENR_PRIORITY (Priority of Work List Entries) ........................................................................... 554.22 /STWACS/X_ENR_RESTRICT (Restriction of Work List Data)........................................................................ 554.23 /STWACS/X_ENR_VALUE_INFO (Work List Store Value Information) .......................................................... 564.24 /STWACS/X_ENR_UNIT (Determination of Enrichment Unit of Measure (Stock + Stock

Transfer Quantity)) ................................................................................................................................................ 57


Stock Balancing ManagementOverview

1 Overview

Article stocks are frequently transferred between an enterprise's stores in order to optimize sales. This process iscommon in the fashion sector, above all. The execution of operational stock transfers is supported by StockBalancing Management, so that efficient and rapid processing is possible on the basis of all the necessaryinformation within just one transaction.

Stock Balancing Management is an add-on to the existing SAP ERP portfolio, so full integration in the standardPurchasing processes is ensured.

Stock Balancing Management supports the creation of stock transport orders for articles that are to betransferred between the stores of an enterprise.

The overall stock transfer process is split into the main three sub steps:

Reporting to determine possible articles for stock transfer as part of a bestseller/slow seller analysis in the SAPBW system (optional);

Operational distribution of stocks between the stores of an enterprise;

Follow-on processing of the operational stock transfers in the form of SAP ERP stock transport orders and theirpurchase order history.

The functional scope of Stock Balancing Management is concentrated on the operational distribution of stocksthrough the creation of stock transport orders. Integration in the existing SAP ERP portfolio ensures that follow-on processing for the stock transport orders (for example, goods issues and receipts in the stores concerned) canbe carried out with the standard functionality for the SAP ERP purchase order and its history (Purchasing).

The identification of possible articles for operational stock transfer, which is controlled by reporting, should takeplace in the SAP BW system through bestseller or slow seller analyzes. These analyses make it possible to identifyfor example, which articles sell particularly well in which stores, and in which stores they have the worst salesfigures. In the example described above, it would make sense to transfer the articles from the stores in which theydo not sell well (slow seller stores) to stores in which they sell better (bestseller stores), in order to optimize sales.The identification of bestsellers and slow sellers using SAP BW is extremely important for the broadest possiblesystem-supported automation of the stock transfer process.

These analyses take place in SAP BW, and the analysis results are transferred to Stock Balancing Management.As a result, stock transfers can be created that are based on this transferred BW analysis data.

You also have the option of not using BW data. In this case, you manually select possible stock transfercandidates. Information such as store-specific stock information helps well-founded decisions to be made on thetransfer of articles and support the execution of this using stock transport orders.

Stock Balancing Management is primarily a tool for professional users in the company or group head office forefficiently making and implementing decisions on stock transfers.



1.1 Prerequisites

This user guide provides all the information needed to use Stock Balancing Management.

Stock Balancing Management is primarily a tool for professional users in the company or group head office forefficiently making and implementing decisions on stock transfers.

1.2 Assumptions

This user guide is based on the assumption that you have some level of familiarity with the terminology andfunctions associated with Stock Balancing Management.

The aim of this user guide is to provide you with the information you need to navigate through and optimize theperformance of Stock Balancing Management.

We recommend that you refer to this user guide whenever necessary during the hands-on operation of StockBalancing Management.

1.3 Logon and Site Authorization

1.3.1 Authorizations

Stock Balancing Management can be called using transaction /STWACS/START_MAIN.

Transaction /STWACS/START_ENR is used to access the enrichment report and transaction/STWACS/START_REORG to access the reorganization report.

The user is assigned the authorization to execute the functionalities by being assigned the above mentionedtransactions (standard authorization object S_TCODE).

1.3.2 Notes

You can add these transactions as favorites to your SAP Easy Access Menu.



1.4 List of Abbreviations

Abbreviation Meaning

ACS Adaptable Custom Solution

ALV SAP List Viewer

BAdI Business Add-In

ERP Enterprise Resource Planning

SAP BW SAP Business Information Warehouse

SAP ERP SAP ERP Central Component

DC Distribution center

1.5 Screen Overview

Stock Balancing Management consists of the following areas:

Selection area

Stock transfer screen area – header data

Stock transfer screen area – item data

Figure 1: Graphical representation of Stock Balancing Management screen

Stock Balancing ManagementScreen Layout for Stock Balancing Management Introduction


2 Screen Layout for Stock BalancingManagement Introduction

An overview of the most important functions and contents of the individual areas is provided below:

Selection area

o Selection of the scenario (manual scenario, worklist, stock transfer document)

o Selection of the articles to be transferred or an existing stock transfer document

o Selection of the sender and recipient stores and (optional) a distribution center

o Moving of the selected data to the processing area

Stock transfer screen area – header data

o General data for a stock transfer document (including description, purchasing organization, purchasinggroup)

Stock transfer screen area – item data

o Detailed data for the selected articles and stores (including stock information for the individual variantsdepending on the selected stores or distribution center)

o Definition of the stock transfer quantities per variant and store

Figure 2: Screenshot of transaction /STWACS/START_MAIN



2.1 Tool Bar - SAP GUI Status

No. Functionality Description

1 Hide/show individual screenareas:

Selection area

Screen area stock transfer – header

data

Screen area stock transfer – item

data

You can hide or show each area by selecting the relevantbutton.

2 Toggle between display andchange mode:

Toggling button to switch between the two modes.

3 Refresh functionality: This button is only active in change mode for a stocktransfer document.

You use this pushbutton functionality to have the systemread the current stock information for the article and storedata displayed and compare this with the currentlydisplayed information. This comparison takes place atarticle and store level and includes the current stock values.As a result of this comparison, the new stocks arecalculated on the basis of the existing stock transfer stocks.

4 Check consistency: This executes consistency checks for the current stocktransfer document. All errors are displayed in thenotification log area (under the item area). If there are noerror messages, a success message is displayed.

5 Release stock transferdocument:

The following steps are carried out by the system if youchoose Release Stock Transfer Document:

Update check and consistency check;

Switch of status to "Released";

Creation of an SAP ERP purchase order with order type




"stock transport order" (if the company code is the same)or "standard PO" (if the company codes for the stores aredifferent);

Moving of collective number/PO number to the header areaof the stock transfer document

Adequate updating of the stock transfer order document onthe database.

Stock Balancing Management is switched from change todisplay mode, the stored document remains in theprocessing area for Stock Balancing Management.

6 Create new document: Creation of a new document through:

Initializing the work area with the option of moving the datafrom the selection area to the processing area;

Switching to change mode for Stock BalancingManagement.

7 Error log; Shows/hides error log:

In the standard system, the error log is displayed below theitem area. The log is displayed automatically as soon aserrors occur or if you manually display it.

Once displayed, the error log remains on screen until:

You explicitly hide it, or

The cause of the error is eliminated.

Stock transfer documents can be stored on the databaseeven if errors exist in the error log.

8 Delete: Deletes the displayed stock transfer document:

As long as the stock transfer document has not beenreleased – no follow-on document exists – you can deletethe stock transfer document. The document is directlyphysically deleted from the database. A warning with theoption of terminating deletion is displayed to inform you ofthe consequences of deletion.

Deletion is only possible for an individual stock transferdocument; for this the stock transfer document must betransferred to the processing area for Stock BalancingManagement.

9 Enrichment log: Displays the log that recorded all errors and warnings thatoccurred during execution of the enrichment report.

10 Save (hold) stock transferdocument:

If you use this button to save a stock transfer document,the system performs the following steps:




The system creates a unique stock transfer documentnumber (if this is the first time you have saved thedocument)

The stock transfer document is assigned the status "InProcess"

The stock transfer document is adequately updated on thedatabase

Stock Balancing Management is switched from change todisplay mode, the stored document remains in theprocessing area for Stock Balancing Management.

2.2 Selection Area


In the selection area, you can decide which articles to transfer. There are three options:

Manual scenario:Manual selection of articles using the selection criteria offered on the selection screen.



Stock transfer document:Call of a document already created for a stock transfer and further processing of this (if the document statuspermits this)

Worklist:Call of analysis data based on various selection criteria provided by an SAP BW system, to which thenecessary data has already added by the enrichment report

The following functions are available on the selection screen for all the scenarios:

GUI ICON Description

Terminate current selection

Delete previously selected criteria

Confirm current selection. After selection, the articleis displayed with all variants.

By setting the indicator Overwrite old selection, youcan overwrite the previous article selections and onlyuse the currently selected article selections.



2.2.1 Selection in Manual Scenario

Figure 4: Selection screen – Manual Scenario

You can select the following generic articles and their variants using various criteria:

Article number

Article short text

Hierarchy

Hierarchy node

Merchandise category

Season (only in connection with season year)

Season year (only in connection with season)

Collection

Fashion grade

Vendor



Figure 5: Example- Selection result for Manual Scenario

2.2.2 Selecting Stock Transfer Documents

Figure 6: Selection screen – Stock Transfer Documents

You can select the following existing stock transfer documents using various selection criteria:

Document number: Number of the stock transfer document;

Description of the stock transfer document

Scenario: Manual or BW worklist

Process: Store-to-store or Store - DC - Store

Status: In process, Released, Cancelled, For deletion

Created by: User name

Created on: Creation date



Figure 7: Example of selection result for Stock Transfer Documents

2.2.3 Selection for Worklist Scenario

Figure 8: Selection screen - Worklist Scenario

You can select the following existing BW worklists using various selection criteria:

Article

Worklist status:

o 01 (enriched, no transfer yet to ACS Stock Balancing Management)

o 02 (enriched, transferred to stock transfer document)

o 03 (flagged for deleted)

o 04 (not relevant)

o 99 (error)



NoteYou can select status 04 and 99 only for deletion in the reorganization report

Priority: You can use a BAdI to define customer-specific priorities for articles and stores (in the standardsystem, no priority is specified);

Enrichment date

Figure 9: Example of selection result for Worklist Scenario

2.2.3.1 Groupings for the Worklist

During processing of the transferred SAP BW analysis data by the enrichment report (see section 0), animplementation of a BAdI can be used to group the data. For example, you can subdivide the analysis data bysales territories, so that you get one group with sender and recipient stores in the north and one group with



sender and recipient stores in the south of a sales territory. If the BAdI is not implemented, no specific groupingtakes place. Instead, in the standard system, grouping takes place at generic article level, with all related variantsbeing shown below generic article level.

2.2.3.2 Priorities for the Worklist

During processing of the transferred SAP BW analysis data by the enrichment report, an implementation of a BAdIcan be used to assign a priority based on defined criteria for each article or variant. During selection of theworklist, this priority can be used to restrict the worklist in order to only display the stock transfer candidates withthe highest priority, for example, if the BAdI is not implemented, no priorities are assigned.

2.2.3.3 Data Retention Levels for the Worklist

The worklist can have different data retention levels. The data retention level that is displayed depends on theanalysis performed in the SAP BW system or the transferred analysis results.

Only one article is displayed, which was identified as a stock transfer candidate on the basis of the BWanalysis. In subsequent processing you define the sender and recipient stores (apart from selection of thearticle, the procedure here is the same as that for the manual scenario, see section 2.5).

Figure 10: Article

One article and one store are displayed; the store was classified by the SAP BW system as a bestseller store.In this case, the BW analysis returns the store, but you must decide whether the store is the sender orrecipient. You define this and choose at least one other store in the store assignment dialog box.

Figure 11: Article and bestseller store

One article and one store are displayed; the store was classified by the SAP BW system as a slow seller store.In this case, the BW analysis returns the store, but you must decide whether the store is the sender orrecipient. You define this and choose at least one other store in the store assignment dialog box.



Figure 12: Article and slow seller store

One article and one store are displayed; the store was classified by the SAP BW system as a neutral store. Inthis case, the BW analysis returns the store, but you must decide whether the store is the sender or recipient.You define this and choose at least one other store in the store assignment dialog box.

Figure 13: Article and neutral store

Article and assignment to sender and recipient storeIn the following example, store P120 is proposed as the recipient and store P121 as the sender. This can beseen through the hierarchical arrangement of the tree, which always shows the recipient at the highest leveland with the sender below this, if Best-Slow display is activated.

Figure 14: Indicates if Best-Slow display is active

If Slow-Best display is activated, the data is displayed in reverse.

Figure 15: Indicates if Slow-Best display is active

One article and at least one sender and one recipient store are displayed. In this case, the BW analysisprovides all the relevant information, and when the data is moved, the sender and recipient stores areproposed in the store assignment dialog box. However, you can select different stores or change theassignment of sender and recipient stores. After the data has been moved to the processing area, you simplyneed to define the stock transfer quantities.

In addition to the article and sender and recipient stores, other information can be provided from the BWanalysis. This data is displayed if you choose the Display Worklist Information pushbutton in the StoreAssignment group box.



Figure 16: Store assignment group box with proposed sender and recipient

In this case, the BW analysis provides all the relevant information (current stock, target stock, differencebetween current stock and target stock). The values shown are absolute values. It would also be possible tospecify percentages.

Figure 17: Screenshot of relevant values in BW analysis

2.2.4 List of Functions in the Selection Area


1 Change between scenarios:

- Worklist (analysis data/stock transfercandidates from SAP BW)

- Manually controlled stock transfer(generic articles freely selected by user)

- Existing stock transfer documents

The choice of scenario determines the display of thesearch results in the selection area.




2 Switch between display options Switch between Best-Slow and Slow-Best display (only forworklist scenario)

3 Scenario-dependent selection options Depending on the scenario you selected, a selectionscreen is displayed containing the selection options foruser input.

On the selection screen, you can use an indicator tocontrol whether the results of the new selection overwritean existing selection in the selection area or whether theold data is to be compared to or enriched with the newdata. (A comparison only takes place within the samestock transfer scenario).

The selection result is displayed as a hierarchy in the TreeControl area

4 Selection option of current worklistwithout specification of other selectionoptions (automated selection, workliststock transfer candidates as per SAP BWanalysis)

No selection options are displayed. Instead, the currentworklist of stock transfer candidates is selected by thesystem on the basis of the SAP BW analysis (correspondsto selection of data with "01" – enriched).

This button is only activated for the "Worklist" scenario.

5 Delete entries in worklist, cancel deletion Dropdown list for deleting entries from the worklist orcancelling deletion (button only active for "Worklist"scenario).

Deletion always relates to the selected node and all levelsbelow this.

If an article or variant is deleted, it is assigned a deletionflag and in the standard system is no longer displayed inthe worklist.

However, if you set certain selection options, you can alsoselect articles with a deletion flag (selection with status"03“). For articles selected in this way, you can canceldeletion both on a selection-specific basis(individual/multiple selection) and completely (for all thearticles currently displayed with a deletion flag).

6 Move to item area The data is moved on a generic article-specific basis,which means that a maximum of one generic article can bemoved to the processing area of Stock Balancing




Management. Move includes:

The displayed variants of the generic article, in the case ofa manual stock transfer scenario;

The generic article including all variants according to thespecified stock transfer document, in the case of stocktransfer document selection;

The generic article including all variants identified by SAPBW as stock transfer candidates, in the case of a stocktransfer scenario triggered by the SAP BW worklist.

When the data is moved, generic article-related data ismoved to the header area and the variant data is moved tothe item area of Stock Balancing Management.

Data successfully moved from the selection area to theprocessing area is hidden in the selection area.

In the selection area, you can select the generic article,including variants that you want to transfer at both genericarticle level and variant level.

If the processing area of Stock Balancing Management isnot initial, that is, an article has already been moved to theprocessing area, a dialog box containing the followingoptions is displayed:

Create and save current data in the processing area;

Create without saving current data.

7 Compress/Expand Button for compression/expansion if a hierarchy levelselection is displayed. Compression/expansion takesplace step by step from hierarchy level to hierarchy level.

Button for compressing/expanding the completehierarchy level to the highest or lowest hierarchy level

8 Search function If you choose the Binoculars button, a dialog box isdisplayed in which you can enter a user-defined searchterm. The search is then carried out across the selectionresults currently displayed in the selection area.

If you choose the Find Next pushbutton the systemcontinues to search for the same search term from anidentified search result or carries out a new search to thenext search result.



2.3 Screen Area – Header Data

The header data screen area is used to display

Relevant, cross-store article data of a generic article

Administrative data of the stock transfer or stock transfer document


2.3.1 Header Data Detailed View

The following fields are shown in the detailed view of the header data:

General Data:

o Document Number: Number of the stock transfer document (this number is assigned when you save forthe first time)

o Description: (input field): User-defined text as a description

o Status: Status of the document (new, in process, released, cancelled, deleted)

o Scenario: Manual or worklist

o Purchasing Org.: (input field):This is the standard purchasing organization for the recipient store. If there are several recipients with



different purchasing organizations, the correct purchasing organization is determined automaticallywhen the stock transfer document is released (field EKORG in table T001W)

o Purch. group: (input field);

o Follow-on Document: This contains the number of the number of the collective document ("SubmissionNumber") for the stock transport order or standard purchase order following release of the processeddocument. (All the purchase orders that belong to a transaction can be selected using selection with thecollective number field in table EKKO.)

Article Data:

o Article

o Category: 01 Generic article

History:

o Created by: Name of the user who created the document

o Created on: Creation date

All fields apart from Description, Purchasing Org. and Purch. group are filled automatically.

Figure 19: Header data detailed view



2.4 Screen Area – Item Data

The item data area is used to display the following information:

Recipient stores (bestseller stores) to which the articles are to be transferred

Sender stores (slow seller stores) from which the articles are to be removed in order to be transferred to therecipient stores

A distribution center, if the stock transfer from the sender store to recipient store is to be carried out througha distribution center

Information about the article itself, that is, information on article variants, and in particular their store stocks

The sender and recipient stores are defined in the store assignment dialog box.

There are two display alternatives for determining possible stock transfer candidates:

From bestseller to slow seller

From slow seller to bestseller




2.4.1 Store-to-Store Stock Transfer

The stock transfer data is calculated and displayed in a similar way for the two display options "from bestseller toslow seller" and "from slow seller to bestseller". Processing of the item data is explained using the example of"from bestseller to slow seller":

In the store assignment dialog box, store P120 was defined as the sender store and store P122 as the recipientstore.

Two new lines are displayed in the item overview for each sender/recipient store assignment pair.

For each generic article variant, the currently available stock is displayed at both recipient store level andsender store level.

In addition, you can enter the stock to be transferred in an input field at sender store level.

It is also possible to leave a minimum stock in the sender store (this option is only possible if the BAdI is fullyprogrammed).

The new stock in the sender store is calculated as the currently available stock minus the stock transferamount.

The new stock of a generic article variant in the recipient store is calculated as the current stock plus thestock transfer amount from all sender stores.

For each sender store, the total stock to be transferred – aggregated across all generic article variants – andthe resulting new stock (difference: current stock – stock transfer amount) are displayed in addition to thecurrent stock.

For each recipient store, the total stock to be transferred, that is, the transferred stock and the resulting newstock (sum of current stock + stock transfer amount from sender store) are displayed in addition to thecurrent stock.

You can also enter the delivery date for the purchase order to be generated for each sender store.

A special case is when one sender store supplies two recipient stores. In this case, the direct display of the currentstock minus stock transfer stock = new stock is somewhat more complicated, because the new stock results fromthe stock transfer amounts from two recipient stores.

Figure 21: Example of detailed view of store-to-store stock transfer

2.4.2 Stock Transfer Store – Distribution Center - Store

The stock transfer data is calculated and displayed in a similar way for the two display options "from bestseller toslow seller" and "from slow seller to bestseller". Processing of the item data is explained using the example of"from bestseller to slow seller":



In the store assignment dialog box, store P120 was defined as the sender store for recipient store P121, withdistribution center P100 first receiving the articles to be transferred and then forwarding them (possible in adifferent quantity) to the recipient store.

For each generic article variant, the currently available stock is displayed at both sender/recipient store leveland distribution center level.

In addition, you can enter the stock to be transferred in an input field at sender store level.

It is also possible to leave a minimum stock in the sender store (this option is only possible if the BAdI is fullyprogrammed).

The new stock in the sender store is calculated based on the currently available stock minus the stocktransfer amount.

The new stock of a generic article variant in the DC is calculated as the current stock plus the stock transferamount from all sender stores.

The new stock of a generic article variant in the recipient store is calculated as the current stock plus thestock transfer amount from the DC.

For each sender store, the total stock to be transferred – aggregated across all generic article variants – andthe resulting new stock (difference: current stock – stock transfer amount) are displayed in addition to thecurrent stock.

For each DC, the total stock to be transferred – aggregated across all generic article variants – and theresulting new stock (difference: current stock – stock transfer amount) are displayed in addition to thecurrent stock.

For each recipient store, the total stock to be transferred, that is, the transferred stock and the resulting newstock (sum of current stock + stock transfer amount from sender store) are displayed in addition to thecurrent stock.

You can also enter the delivery date for the purchase order to be generated.

In the scenario described here, processing takes place in two steps. First, only the quantities to be transferredfrom the stores to the DC can be determined. The stock is then distributed from the DC to the recipient stores.Simultaneous processing of the two steps is not possible.

Figure 22: Example of detailed view of store – distribution center - store stock transfer



2.4.3 List of Functions in the Item Area


1 Switch between display options Switch between Best-Slow and Slow-Best display

2 Switch between processing steps For DC scenario only: Switch between the two work steps(Store to DC and DC to Store)

3 Toggle input fields With a customer implementation of the relevant BAdI, youcould for example store the following control option:

In the normal view, the stock to be transferred is entered atvariant level.

In the Sum Edit view, the stock to be transferred is defined atgeneric article level, with the number of variants to betransferred being automatically determined through theequal distribution of the total number among the variants.

4 Compress/expand item lines Compress/expand higher-level item lines

Single selection and multiple selection

Compress/expand complete item area (compression athighest display level)

5 Scroll This functionality allows you to scroll within the item area, asif numerous variants are used, not all can be displayedsimultaneously.

6 Complete stock transfer A complete stock transfer of the selected sender item lines(multiple selection possible) to the assigned recipient itemline is carried out.




The sender stores selected for complete stock transfer mustnot be assigned to several recipient stores.

7 Generation of distributionproposals

This button allows you to generate distribution proposals,but only with customer implementation of the related BAdIs.

8 Complete variants, removevariants (only SAP BW-controlledstock transfer scenario)

If you use the SAP BW-controlled stock transfer scenario,the displayed variants exactly match the variants from theresult of the SAP BW analysis and executed enrichmentreport (see also section 2.2.4). As this does not necessarilycontain all the variants of the generic article, you cansubsequently add the other variants of the generic article tostock transfer processing. You can also remove thesevariants again.

9 Insert line Insertion of new sender item lines following selection of thehigher-level recipient item line.

10 Delete line Deletion of recipient or sender item lines after you haveselected these lines.

If a higher-level item line was selected, all dependent, lower-level item lines are also deleted.

If a single item line (with no lower-level items) is selected,only this one line is deleted.

11 Display store assignment dialogbox

In the manual stock transfer scenario and in the case ofresulting stock transfer documents, the store assignmentdialog box is used to determine/display the recipient andsender stores (see section 2.5).

12 Refresh The displayed stocks and other data at both recipient andsender store level are refreshed.

13 Delivery date/Mass maintenance The delivery date to be used in the purchase order ismaintained for all the selected lines at sender store level.




14 Search for specific entries withuser-defined input

If you choose the Find pushbutton, a dialog box is displayedin which you can enter a user-defined search term. Thesearch that is then carried out relates to the data currentlydisplayed in the item processing area.

If you choose Find Next pushbutton the system continues tosearch for the same search term from an identified searchresult or carries out a new search to the next search result.

15 ALV layout settings Option of user-specific modification of the displayed ALVgrid.

2.5 Stock Transfer Process

2.5.1 Manually Controlled Stock Transfer

In manually controlled stock transfer, you must select both the articles to be transferred and the sender andrecipients stores.

You select the articles in the selection area.

When the articles are moved to the item area, the header data is filled automatically. In addition to the articles, thesender and recipient stores are also needed for display in the item area. These are defined in the store assignmentdialog box. If the stock transfer from the sender store to the recipient store is to go through a DC, this must alsobe entered in the store assignment dialog box.

The data is moved from the selection area to the processing area in two steps: You first select the stores, and thenselect the sender stores, recipient stores, and distribution center.

2.5.1.1 Store Selection

By setting the indicator you can overwrite a previous selection.



Figure 23: Example of store selection

2.5.1.2 Store Assignment Dialog Box: Selecting SenderStores, Recipient Stores, and Distribution Center

Selection of sender stores, recipient stores, and distribution center

In this dialog box, all stock information (aggregated stock across all storage locations of a site from tableMARD "Storage location data for article") for the variants across all stores, based on the listing, is displayed inaddition to the selected stores.

Within the dialog box, you can now use the indicator to determine which stores are recipients and which aresenders. Various plausibility checks are implemented here that ensure that at least one store is selected as asender and another is selected as a recipient. A store can only be selected as either a sender or a recipientstore.

By selecting a distribution center (optional), you can also define that the stock transfer from the sender torecipient store takes place through a distribution center.

When you choose Overtake (apply), you move the selection of the DC and/or sender and recipient stores tothe item area of Stock Balancing Management. Entries that are not selected are not moved.

In addition to the automatic display of the dialog box when you move data to the item area, you can also explicitlydisplay the dialog box within the item area. You can then cancel assignments that have been made or create newones.



Figure 24: Example of the store assignment dialog box in manually controlled stock transfer

2.5.2 Stock Transfer from Worklist

If you carry out stock transfer using the worklist, you must select the required articles from the data transferredfrom the BW system and displayed in the selection area. The data is always moved from the selection area to theprocessing area for the articles of a group within the worklist. In the standard system, without customerimplementation of the BAdI, the generic article and all its variants identified during the BW analysis forms thisgroup.

Several data retention levels are possible in the worklist. If sender and recipient stores have already beenspecified for the articles, this information is copied to the store assignment dialog box. If only the articles orarticles and assigned neutral stores were included in the worklist, you must define in the store assignment dialogbox whether the neutral store is a sender or recipient store, as in manual stock transfer. You can also select otherstores. Selection of the stores and processing in the store assignment dialog box are carried out on manual stocktransfer.

When the articles are moved to the item area, the header data is filled automatically.



2.5.3 List of Functions in the Store Assignment Dialog Box


1 Sort sequence After selecting the relevant columns, the data in the ALV GridControl is displayed in either ascending or descending order.

2 Search for specific entries withuser-defined input If you choose the Find pushbutton, a dialog box is displayed

in which you can enter a user-defined search term. Thesearch that is then carried out relates to the data currentlydisplayed in the selection screen.

If you choose the Find Next pushbutton the systemcontinues to search for the same search term from anidentified search result or carries out a new search to thenext search result.

3 Display filter Option of defining filters for the displayed entries.

4 ALV layout settings Option of user-specific modification of the displayed ALVgrid.

5 Sender store selection For selected lines, the indicator is set in the sender storecolumn.

6 Recipient store selection For selected lines, the indicator is set in the recipient storecolumn.

7 Deselect For selected lines, the indicator in the sender store column isremoved.

8 Deselect all All existing assignments are cancelled, the indicators for the




recipient/sender store are removed.

9 Selection Access of selection screen for stores (see section 2.5.1.1).

10 Add entries that were nottransferred

BW scenario only:

Within the item area, option of moving all default values thathave not been moved from the selection area.

11 Display worklist information BW scenario only:

Option of displaying all the data provided by SAP BW for aselected line (target stock, current stock, difference)

12 Scroll This functionality allows you to scroll within the display area,as if numerous variants are used, not all stock informationcan be displayed simultaneously.

13 Select lines Select/deselect all store-specific lines

14 Apply assignment Move the store assignments defined in the dialog box to theitem area

15 Cancel Do not move the store assignments defined in the dialog boxto the item area.



2.6 Stock Transfer Document (Stock Transport Order)

2.6.1 General

All the stock transfers processed in Stock Balancing Management are grouped into stock transfer documents.

Each stock transfer document relates to exactly one generic article and its variants.

After a stock transfer document is released, an actual stock transfer is generated in the form of a stock transportorder (or, in the case of different company codes, a standard purchase order).

The stock transfer document has a history that provides information on when a document was created, changed,or released, and by whom. The document also contains stock transfer-specific information such as the purchasingorganization or purchasing group.

Permitted statuses in a stock transfer document are:

New: Set by the system the first time a stock transfer document is processed;

In process: Set by the system the first time a stock transfer document is saved;

Released: If a stock transfer document has been released, it can no longer be put back to status "In process"and changed.

Deleted: As long as the stock transfer document has not been released – and consequently no follow-ondocument exists – you can delete the stock transfer document. Stock transfer documents with the status"Deleted" can be displayed but no longer processed. Physical deletion of the stock transfer document doesnot take place until the reorganization report has been run.

The collective number forms the link between a stock transfer document and the resulting purchase orderdocuments. You can display all related purchase order documents by selecting the collective number (fieldSUBMI) in the purchasing document header table (EKKO).

Note

Changes made in the follow-on document (purchase order) are not updated in the preceding stock transferdocument.

2.6.2 Purchase Order Creation

2.6.2.1 Purchase Order Document

When a stock transfer document is released, the resulting purchase orders are created automatically based onthe information in the item area.



The collective number forms the link between a stock transfer document and the resulting purchase orderdocuments. You can display all related purchase order documents by selecting the collective number (fieldSUBMI) in table EKKO (purchasing document header).

NoteChanges made in the follow-on document (purchase order) are not updated in the preceding stock transferdocument.

2.6.2.2 Document Type

The document type for purchase order document creation is stored in Customizing under SAP Reference IMG ->Materials Management -> Purchasing -> Purchase Order -> Set Up Stock Transport Order -> Assign DocumentType, One-Step Procedure, Underdelivery Tolerance.

This is part of standard Customizing, and a document type can be stored for each sender and recipient store(table T161W).

2.6.2.3 Cross-Company Code Purchase Order

If the sender store and recipient store have different company codes, the standard system requires moreextensive data to create the purchase order than is required for purchase orders within one company code.

Valid vendor data for the sender store (table T001W, field LIFNR) is a prerequisite for the creation of a purchaseorder for stores with different company codes.

Stock Balancing ManagementOverarching Functionalities


3 Overarching Functionalities

3.1 BW Data Transfer

The identification of possible articles for operational stock transfer, which is controlled by reporting, should takeplace in the SAP BW system through bestseller/slowseller analyses. These analyses make it possible to identifyfor example, which articles sell particularly well in which stores, and in which stores they have the worst salesfigures. In the example described above, it would make sense to transfer the articles from the stores in which theydo not sell well (slowseller stores) to stores in which they sell better (bestseller stores), in order to optimize sales.The identification of bestsellers and slowsellers using SAP BW is extremely important for the broadest-possiblesystem-supported automation of the stock transfer process.

Stock Balancing Management obtains these analysis results through the call of an RFC function module/STWACS/ANA_DATA_IMPORT from the SAP BW system and the storage of the initially unchecked data in the SAPERP system (tables /STWACS/WL, /STWACS/WL_ASS, /STWACS/WL_STRVL). For further use, additionalinformation must be added to this raw data within Stock Balancing Management with the help of the enrichmentreport and the data must be converted into the structures required for Stock Balancing Management.

3.1.1 General

So that the analysis data transferred from SAP BW system can be used in Stock Balancing Management, anenrichment report is used to enrich the data with information, some of which only exists in the SAP ERP system.

During enrichment, numerous existence checks are carried out on the transferred data in tables /STWACS/WL,/STWACS/WL_ASS and /STWACS/WL_STRVL (articles, stores, stock transfer amounts). In addition, the data ismoved to the structures and tables needed for Stock Balancing Management (primarily tables/STWACS/ARTICLES, /STWACS/STORES, /STWACS/STOCK).

3.1.2 Calling the Enrichment Report

The enrichment report is called using transaction /STWACS/START_ENR. Any errors and inconsistencies thatoccur are written to an error log, which is accessed within stock transfer management (Environment -> ShowEnrichment Log).



Figure 25: Enrichment report selection screen

3.2 Reorganization Report

3.2.1 General

The reorganization report enables you to delete data that has accumulated over time from the system andtherefore ensure transparency and clarity. Only data of a temporary nature in terms of meaning and the existenceof which is not a condition for tracing the integrative process flow within the SAP system can be deleted from theSAP system.

Entries for the following objects can be deleted from the system using the reorganization report:

WorklistThe worklist provides the analysis data from an SAP BW system, which is then used to enrich additionalinformation for further processing.

Stock transfer documentAll the stock transfers processed in Stock Balancing Management are grouped into stock transfer documents.Each stock transfer document relates to exactly one generic article and its variants.

Plausibility dataWhen stock transfer documents are released and the stock transport orders are then created, certain data,such as the article number and sender and recipient store, is updated in tables. This data enables you to carryout customer-specific plausibility checks in BAdIs. For example, you can use these to ensure that an articlethat has already been transferred is not processed again, or that a sender store is not flagged as a recipient



store in further processing. The configuration of these checks and the reaction to the results of the check canbe defined within a BAdIs.

3.2.2 Calling the Reorganization Report

The reorganization report is called using transaction /STWACS/START_REORG. The following selection options areavailable for the worklist, stock transfer document, and plausibility entry:

Worklist:

Article

Store

Worklist status:

o 00 Raw data imported, not enriched

o 01 Enriched but not transferred to Stock Balancing Management

o 03 Entries flagged for deletion

o 04 Entries not relevant

o 99 Errors

NoteWorklist entries with status 02 (transferred) cannot be deleted directly and instead must be deleted by deletingthe related stock transfer document.

Enrichment Date

Clear Entire Worklist Data Indicator: If you set this indicator, the complete worklist – that is all imported data – isdeleted.

Clear Related Plausibility. Data Indicator: If you set this indicator, the data, stored in the plausibility tables that isrelated to the entry for deletion in the worklist is also deleted.

Stock transfer document:

Stock transfer document: Number of the stock transfer document

Status: New, In process, Released, Cancelled, For deletion

Created On: Creation date

Clear Related Plausibility. Data Indicator: If you set this indicator, the data, stored in the plausibility tables, that isrelated to the stock transfer document for deletion is also deleted.

Plausibility Entries:

Stock transfer document

Article

Sender Store



Receiver Store

Changed date: Change date

Clear Entire Plausibility Data Indicator: If you set this indicator, the entire contents of the plausibility tables aredeleted.

Stock Balancing ManagementList of Business Add-Ins (BAdIs)


4 List of Business Add-Ins (BAdIs)

4.1 /STWACS/X_COLUMN_NAMES (Fill Article ColumnNames)

BAdI method /STWACS/IF_X_COLUMN_NAMES~FILL_ARTICLE_COLUMN_NAMES:

Parameter name Type Description

XT_ARTICLE_COLUMN_NAMES Changing Item area Column names to bepassed to BAdI

This BAdI is used to set customer-specific column names in the Item area ALV Grid for the article columns. Thechanging parameter XT_ARTICLE_COLUMN_NAMES that is passed to the BAdI contains the technical column nameand the corresponding article number. In the BAdI implementation the field labels SCRTEXT_S (Short Field Label),SCRTEXT_M (Medium Field Label) and SCRTEXT_L (Long Field Label) need to be filled. No defaultimplementation is provided for this BAdI.

This BAdI is called from the following methods:

/STWACS/CL_WA_SET_BESTSLOW_V->CREATE_ALV_FIELDCAT

/STWACS/CL_WA_SET_SLOWBEST_V->CREATE_ALV_FIELDCAT

/STWACS/CL_WA_SET_DC_V->CREATE_ALV_FIELDCAT

/STWACS/CL_WA_SET_STORE_V->CREATE_FIELDCATALOG

4.2 /STWACS/X_DC_QTY_PROPOSAL (DC QuantityProposal for DC to Store Process)

BAdI method /STWACS/IF_X_DC_QTY_PROPOSAL~PROPOSE_QUANTITY:


IT_DC_TOTAL_RELOCATION_STOCK Importing Total quantity per Article thatcomes into the DC

IT_DC_STOCK Importing Total quantity per Article at theDC

ET_DC_STOCK Exporting Relocation quantity per Articleproposed from DC for “DC toStore” process

This BAdI proposes the relocation quantities per article from DC in “DC to Store” process. The quantities perarticle that are shipped from sender stores are proposed by default. The importing parameter



IT_DC_TOTAL_RELOCATION_STOCK contains the total relocation quantity per article into DC from all senderstores. The importing parameter IT_DC_STOCK contains the present stock per Article at DC. The exportingparameter is to be filled with the relocation quantity per article that needs to be relocated from DC to differentReceiver stores. A default implementation is provided for this BAdI.

This BAdI is called from the following method:

/STWACS/CL_WA_SET_ITEM->GET_DC_STOCK_PROPOSAL

4.3 /STWACS/X_MANDATORY_QTY (Mandatory QuantityDetermination)

BAdI method /STWACS/IF_X_MANDATORY_QTY~DETERMINE_MANDATORY_QUANTITY:

Interface


IT_ARTICLES Importing Relocation document Articles

IT_STORES Importing Relocation document Stores

IT_STOCK Importing Relocation document Articlestock at Stores

XT_MANDATORY_STOCK Changing Mandatory Stock for eachArticle at each Store

This BAdI provides the flexibility to the customer to determine mandatory stock for an article at a store. Theimporting parameters IT_ARTICLES, IT_STORES and IT_STOCK can be used to determine the mandatory stock.In the changing parameter XT_MANDATORY_STOCK only the QUANTITY field needs to be changed for theconcerned article. No default implementation is provided for this BAdI.


/STWACS/CL_WA_SET_ITEM->FILL_MANDATORY_STOCK

4.4 /STWACS/X_QUANTITY_DISTRIBUTE (Stock QuantityDistribution across Articles)

BAdI method /STWACS/IF_X_QUANTITY_DISTRIBU~DISTRIBUTE

Interface




IT_STOCK Importing Relocation document Articlestock at Stores




IT_RELOCATION_STOCK Importing Relocation documentRelocation stock

IT_DISTRIBUTION_STOCK Importing Stock to be distributed

ET_RELOCATION_STOCK Exporting Distribution stock proposal

This BAdI is applicable for “Best Slow” stock transfer process and “Store to DC” process in the DC scenario. ThisBAdI distributes the quantity that is provided at reference article level across all articles using the exportingparameter ET_RELOCATION_STOCK. No default implementation is provided for this BAdI.


/STWACS/CL_WA_SET_ITEM->DISTRIBUTE_STOCK

4.5 /STWACS/X_SENDER_QT_DISTRIBUTE (DistributeSender Quantity to Respective Receivers across Articles)

BAdI method /STWACS/IF_X_SENDER_QT_DISTRIB~DISTRIBUTE

Interface




IT_STORE_STOCK Importing Relocation document Articlestock at Stores

IT_RELOCATION_STOCK Importing Relocation documentRelocation stock

IT_DISTRIBUTION_STOCK Importing Stock to be distributed

XT_RELOCATION_STOCK Changing Distribution stock proposal

This BAdI is applicable in the “Slow Best” stock transfer process and the “DC to Store” process in the DCscenario. This BAdI distributes the article quantity from a sender store to all the corresponding receiver storesusing the changing parameter XT_RELOCATION_STOCK. No default implementation is provided for this BAdI.


/STWACS/CL_WA_SET_ITEM->DISTRIBUTE_SENDER_STOCK



4.6 /STWACS/X_DELIVERY_DATE (BAdI to fill DeliveryDate)

BAdI method /STWACS/IF_X_DELIVERY_DATE~DEFAULT_INITIAL_DELIVERY_DATE:

Interface:


RV_DATE Returning Delivery date

This BAdI determines the delivery date that is used while creating the stock transport order. A defaultimplementation is provided for this BAdI that determines the delivery date as the following day – class/STWACS/IF_X_DELIVERY_DATE.


/STWACS/CL_RELOCDOC->LINK_RELOCATION_TO_RELOCDOC

4.7 /STWACS/X_PLAUSI_CHECK (Plausibility Check)

The BAdI is to enable the customer to implement customer specific plausibility checks in order to influence thecreation as well as the handling of stock transfer documents. Such plausibility checks could typically be:

Stock for the same article should not be transferred more than once within a certain period of time.

The same article should not be transferred between particular shops within a certain period of time.

Some articles should be generally excluded from the stock transfer processing.

As for the BAdI /STWACS/X_PLAUSI_CHECK, the following methods are provided, as per BAdI Interface/STWACS/IF_X_PLAUSI_CHECK:

CHECK_PLAUSIBILITY

ADJUST_PLAUSIBILITY_TABLE

Hereby, the method ADJUST_PLAUSIBILITY_TABLE can be used e.g. for the update of the database table/STWACS/PLAUSI. Then, the method CHECK_PLAUSIBILTY can be used e.g. to perform appropriate checksbased on the formerly performed plausibility table adjustments, accordingly.

Parameters of method CHECK_PLAUSIBILITY


IS_HEADER Importing Stock Transfer Documentheader data

IT_EVENTS Importing Stock Transfer Document eventdata

IT_STORES Importing Stock Transfer Document storedata

IT_ARTICLES Importing Stock Transfer Documentarticle data




IT_STOCK Importing Stock Transfer Document stockdata

IT_RELOCATION Importing Stock Transfer Documentrelocation data

ET_MESSAGES Changing Error messages according toplausibility check

Call Stack

/STWACS/CL_RELOCDOC->CHECK_CONSISTENCY

/STWACS/CL_RELOCDOC->CHECK_CONSISTENCY_SIMPLE

Parameters of method ADJUST_PLAUSIBILITY_TABLE


IS_HEADER Importing Stock Transfer Documentheader data

IT_EVENTS Importing Stock Transfer Document eventdata

IT_STORES Importing Stock Transfer Document storedata

IT_ARTICLES Importing Stock Transfer Documentarticle data

IT_STOCK Importing Stock Transfer Document stockdata

IT_RELOCATION Importing Stock Transfer Documentrelocation data

ET_PLAUSI_CHG Changing Change information for DBtable /STWACS/PLAUSI

Call Stack

/STWACS/CL_DB->DET_DB_ADJUSTMENTS_PLAUSI

4.8 /STWACS/X_PURCH_ORG (Determination of PurchasingOrganization Data)

BAdI method /STWACS/IF_X_PURCH_ORG~GET_PURCH_ORG_DATA:

Interface




I_PURCH_ORG_DEFAULT Importing Default Purchase organization

I_PURCH_GRP_DEFAULT Importing Default Purchasing group

I_BUKRS_RECEIVER Importing Company code of the ReceiverStore

I_SENDER_STORE Importing Sender store

I_RECEIVER_STORE Importing Receiver store

E_PURCH_ORG_RECEIVER Changing Determined PurchaseOrganization

E_PURCH_GRP_RECEIVER Determined Purchasing group

This BAdI provides the flexibility to determine the purchase organization as well as the purchasing group based onthe importing parameters I_PURCH_ORG_DEFAULT, I_PURCH_GRP_DEFAULT, I_BUKRS_RECEIVER,I_SENDER_STORE, I_RECEIVER_STORE, E_PURCH_ORG_RECEIVER and E_PURCH_GRP_RECEIVER.

Default Implementation -> Class /STWACS/CL_DEF_IM_X_PURCH_ORG

As per SAP standard, a default implementation of BAdI /STWACS/X_PURCH_ORG is provided, that is, class/STWACS/CL_DEF_IM_X_PURCH_ORG. Here, the purchasing organization is determined as per the mainassignment as defined within the data base table T001W (Sites/Branches). For the purchasing group, the entry asformerly made by the user is applied, accordingly.


/STWACS/CL_RELOCDOC->PREPARE_PO_HEADER_COMP_INT

/STWACS/CL_RELOCDOC->PREPARE_PO_HEADER_CROSS_COMP

4.9 /STWACS/X_STOCK_IDENT (Stock Identification)

BAdI method /STWACS/IF_X_STOCK_IDENT~IDENTIFY_STOCK.

Interface


IT_SELOPT_STORES Importing Stores Range

IT_SELOPT_ARTICLES Importing Articles Range

IT_STORAGE_LOCATIONS Importing Storage locations

ET_STOCK Exporting Stock

This BAdI provides flexibility to identify stock.

As per SAP standard, two implementations, that is, one default implementation – class/STWACS/CL_DEF_IM_X_STOCK_IDEN - as well as one additional example implementation – class/STWACS/CL_EXM_IM_X_STOCK_IDEN - of the BAdI /STWACS/X_STOCK_IDENT are provided.



Here the default implementation summarizes all MARD (Storage Location Data for Article) entries – field LABST(Valuated Unrestricted-Use Stock) – that is the stock summarized over all storage locations with DISKZ (Storagelocation RP indicator) set as “Storage location stock also planned at site level”. In contrast to that, the exampleimplementation determines the stock as per storage location as refer to BAdI/STWACS/X_STORAGE_LOCATION as given below, accordingly.

This BAdI is called from the following function modules:

/STWACS/STOCK_SELECT_SIMPLE

/STWACS/STOCK_SELECT

4.10 /STWACS/X_STOCK_UNIT (Stock Unit Handling)

BAdI method /STWACS/IF_X_STOCK_UNIT~DET_QUANTITY_UNIT_TO:

Interface


IT_STOCK Importing Article stock

E_UNIT_TO Exporting Target quantity unit

This BAdI provides flexibility to determine the unit for the stock.


/STWACS/CL_RELOCDOC->GUARANTY_UNIQUE_STOCK_UNITS

4.11 /STWACS/X_STORAGE_LOCATION (Storage Locations)

BAdI method /STWACS/IF_X_STORAGE_LOCATION~IDENT_STORAGE_LOCATIONS:

Interface


IT_SELOPT_STORES Importing Stores Range

IT_SELOPT_ARTICLES Importing Articles Range

ET_STORAGE_LOCATIONS Exporting Storage locations

This BAdI provides the flexibility to determine storage locations by customer specific needs.

As per SAP standard, a default implementation – class /STWACS/CL_DEF_IM_X_STORE_LOC – is provided whichdetermines the storage location by a three step algorithm:

Determination of the storage location through appropriate MARC (site data for article) entry – if given. (Takefirst, if given so)

If the previous step has failed – determination of the storage location through appropriate MARD (storagelocation data for article) entry – if given. (Take first, if given so)



If both previous steps have failed – determination of the storage location through data base table T001L(Storage locations) – if given.

This BAdI /STWACS/X_STORAGE_LOCATION is called from the following function modules:

/STWACS/STOCK_SELECT_SIMPLE

/STWACS/STORAGE_LOCN_SELECT

4.12 /STWACS/X_SET_NODE_TXT_ARTICLE (Set ArticleNode Texts)

BAdI method /STWACS/IF_X_SET_NODE_TXT_ART~SET_NODE_TEXT_ARTICLE:

Interface


IT_ARTICLES Importing Article information (For e.g.generic article along withvariants or single article’s.).

IT_STORES Importing Store information identified bythe work list data. (Applicableonly in the work list scenario).

IT_RELOCATION Importing Relocation informationidentified by the work list data.(Applicable only in the work listscenario).

IT_WL Importing Work list specific information.(For e.g. Priority of the work listdata, User information, Statusof the work list entry).

I_RELOCATION_SCENARIO Importing Relocation scenario that is,Manual or work list.

ET_NODE_TEXTS Exporting The customer specific Nodetexts for the Article in the treedisplay.

The BAdI is applicable to manual and work list views in the selection area. It enables the customer to specify thenode texts to be displayed in the tree view of the selection area in the workbench. The customer specified nodetexts will be applied only at the generic article or the single article level. No default implementation is provided forthis BAdI.


/STWACS/CL_SEL_SET_ART_V-> FILL_HIERARCHY

/STWACS/CL_SEL_SET_WORKLIST_V-> SET_NODE_TEXTS_FROM_BADI



4.13 /STWACS/X_STORE_CLASS (Determination of StoreClassifications (Sender vs. Receiver))

BAdI method /STWACS/IF_X_STORE_CLASS~GET_STORE_CLASSIFICATIONS:

Interface


IT_ARTICLES Importing Article information (Forexample generic article alongwith variants or single articles.)

IT_STORES Importing Store information identifiedduring the transfer of an articleor a work list entry.

IT_STOCK Importing Stock information pertaining tothe stores and articlesidentified.

ET_STORES_CLASSIFICATION Exporting Store information along withthe classification as sender orrecipient.

This BAdI enables the customer to specify the classification for the stores involved in the Stock BalancingManagement. The classification is to be either as a sender or as a recipient. The result of this implementationwould be reflected on the store assignment screen wherein the checkboxes for sender and recipient are checkedappropriately. The Propose Store Assignments pushbutton on the ALV toolbar on the store assignment screenneeds to be used for triggering this check. No default implementation is provided for this BAdI.


/STWACS/CL_WA_SET_STORE->PROPOSE_STORE_ASSIGNMENTS

4.14 /STWACS/X_STORE_DIST (StoreDistribution/Assignment Rules)

BAdI method /STWACS/IF_X_STORE_DIST~GET_STORES_ASSIGNMENT:

Interface


I_SCENARIO Importing Relocation scenario that is,manual or work list.

I_DC Importing Distribution center specified inthe store assignment screen.




IT_STORES Importing Store information identified onthe store assignment screenduring the transfer of an articleor a work list entry.

IT_RELOCATION_WL Importing Relocation informationspecified by the work list data.This consists of the sender –recipient combination(specified as GUIDS).

ET_STORE_ASSIGNMENT Exporting Store assignment dataconsisting of sender – recipientinformation (in form of storeIDs).

This BAdI method enables the customer to specify the appropriate sender – recipient combination for the stocktransfer. The store information along with the user specified assignments as sender or recipient is retrieved fromthe store assignment screen and supplied to the method along with the relocation scenario and the work listproposed relocation information. No default implementation is provided for this BAdI.


/STWACS/CL_WA_SET_STORE->APPLY_NEW_STORE_ASSIGNMENTS

4.15 /STWACS/X_STORE_SELECT (Store Selection from DB)

BAdI method /STWACS/IF_X_STORE_SELECT~GET_STORES_INFO:

Interface


RT_STORES Returning Store information for the stocktransfer.

This BAdI enables the customer to specify the stores involved in the stock transfer. If this BAdI is notimplemented, then the stores required for the stock transfer are to be determined through a selection screen. Nodefault implementation is provided for this BAdI.


STWACS/CL_WA_SET_STORE_V->DET_STORES_INFO



4.16 /STWACS/X_ENR_ACTUALITY (Actuality (Quantities)Handling within Enrichment Report)

BAdI method /STWACS/IF_X_ENR_ACTUALITY~APPLY_ACTUALITY.

Interface


IT_WL Importing General work list data table (type /STWACS/T_WL)

IT_WL_STRVL Importing Store specific work list data table (Type/STWACS/T_WL_STRVL)

IT_WL_ASS Importing Store assignment specific work list data (Type/STWACS/T_WL_ASS)

ET_WL_CHG Exporting Change table for work list entries as given by IT_WL

(Type /STWACS/T_WL_ACTUALITY_X)

ET_WL_STRVL_CHG Exporting Change table for store specific work list data as givenby IT_WL_STRVL (Type/STWACS/T_WL_STRVL_ACTUALITY_X)

ET_WL_ASS_CHG Exporting Change table for store assignment specific work listdata as given by IT_WL_ASS (Type/STWACS/T_WL_ASS_ACTUALITY_X)

XT_MSG_ERR Changing Message table for error like situations

The BAdI /STWACS/X_ENR_ACTUALITY is to enable the customer to define costumer specific actualityconsiderations and restraints within the enrichment process of the stock transfer related work list data asimported into the SAP ERP system.

Hereby, as per the interface as described above – the following changes/interactions by the customer areallowed:

Status change of work list entries: Allowed status 99 “Error”, 04 “Irrelevant” (see interface parameterET_WL_CHG)

Stock quantity changes of store specific work list entries (see interface parameter ET_WL_STRVL)

Stock transfer quantity changes of store assignment related work list data (see interface parameter ET_WL_ASS)

Call Stack

Include /STWACS/ANA_DATA_ENR_CHECKF01, that is, form APPLY_ACTUALITY_CHECKS of program/STWACS/ANA_DATA_ENR

4.17 /STWACS/X_ENR_DELIV_DATE (Delivery DateInitialization within Enrichment Report)

BAdI method /STWACS/IF_X_ENR_DELIV_DATE~DEFAULT_INITIAL_DELIV_DATE

Interface




IT_ARTICLES Importing Stock Transfer Workbench related article data (Type/STWACS/T_ARTICLES)

IT_STORES Importing Stock Transfer Workbench related store data (Type/STWACS/T_STORES)

IT_STOCK Importing Stock Transfer Workbench related stock data (Type/STWACS/T_STOCK)

IT_RELOCATION Importing Stock Transfer Workbench related relocation data(Type /STWACS/T_RELOCATION)

ET_RELCOATION_CHG Exporting Relocation change data table

(Type /STWACS/T_WL_DELIV_DATE_X

The BAdI /STWACS/X_ENR_DELIV_DATE is to enable the customer to define or initialize costumer specificdelivery dates within the enrichment process of the stock transfer related work list data as imported into the SAPERP system.

Call Stack

Include /STWACS/ANA_DATA_ENR_MAP_INF01, that is, form MAP_INTO_DB_STRUCTURES of program/STWACS/ANA_DATA_ENR

4.18 /STWACS/X_ENR_DOUBLETS (Doublet Handling withinEnrichment Report)

BAdI method /STWACS/IF_X_ENR_DOUBLETS~HANDLE_DOUBLETS

Interface




IT_WL_ASS Importing Store assignment specific work list data table (Type/STWACS/T_WL_ASS)

ET_WL_CHG Exporting Work list data change table by doublets

(Type /STWACS/T_WL_DOUBLET_X)

ET_WL_STRVL_DEL Exporting Store specific work list data table as for deletion

(Type /STWACS/T_WL_STRVL_DOUBLET_X)

ET_WL_ASS_DEL Exporting Store assignment specific work list data table as fordeletion

(Type /STWACS/T_WL_ASS_DOUBLET_X)




ET_MSG_ERR Exporting Error message table

(Type BAL_T_MSG)

Within the enrichment process – see report /STWACS/ANA_DATA_ENR - duplicate entries – so called doublets –are identified and handled as identical groupings. This means that work list data that is grouped in this wayrepresents more or less identical work list data and as such, data that is to be handled as one, accordingly.

The BAdI /STWACS/X_ENR_DOUBLETS can be used by the customer to define own doublet identification rulesbased on own logical or own process related considerations and constraints.

As per SAP standard, a default implementation, that is, class /STWACS/CL_DEF_IM_X_ENR_DOUBL is providedwhich identifies doublets based on the following rules:

Identification of duplicate article entries

Identification of store duplicates per article

Identification of duplicate sender store vs. - receiver store combinations

As for more details, please refer to class /STWACS/CL_DEF_IM_X_ENR_DOUBL within the ABAP workbench itself.

Call Stack

Include /STWACS/ANA_DATA_ENR_CHECKF01, that is, form APPLY_DOUBLET_CHECKS of program/STWACS/ANA_DATA_ENR

4.19 /STWACS/X_ENR_GROUP (Grouping of Work ListEntries within Enrichment Report)

BAdI method /STWACS/IF_X_ENR_GROUP~APPLY_GROUPING

Interface




IT_WL_ASS Importing Store assignment specific work list data (Type/STWACS/T_WL_ASS)

ET_WL_CHG Exporting Work list data change table by grouping

(Type /STWACS/T_WL_GROUP_X)

The BAdI /STWACS/X_ENR_GROUP is to enable the customer to define groupings of article related work list data.Such groupings are to enable the user – in a follow-on step within the Stock Transfer Workbench – to handle suchgrouped article based work list data in one go.

Within the Stock Transfer Workbench, articles that are grouped together are always handled as some kind ofappropriate article set. Such article groupings are displayed under the same nodes within the selection tree of theStock Transfer Workbench as well as they are handled by the same stock transfer document, accordingly.



ExampleWithin the Stock Transfer Workbench, all dark colored T-shirts should be worked on at the same time, as well asall light colored T-shirts. However dark colored and light colored T-shirts should never be worked on together. Insuch a case, both the dark colored T-shirts as well as the light colored T-shirts would be grouped each,accordingly.

As per SAP standard, a default implementation, that is, class /STWACS/CL_DEF_IM_X_ENR_GROUP, is provided.Here, the following logic applies:

All variants of the same generic article are grouped together

All single articles are grouped 1 to 1.

Call Stack

Include /STWACS/ANA_DATA_ENR_CUSTF01, that is, form APPLY_CUSTOMER_GROUPING of program/STWACS/ANA_DATA_ENR

4.20 /STWACS/X_ENR_PLAUSI (Plausibility Checks andAdjustments within Enrichment Report)

BAdI method /STWACS/IF_X_ENR_PLAUSI ~/STWACS/IF_X_ENR_PLAUSI

Interface





ET_WL_CHG Exporting Work list data change table

(Type /STWACS/T_WL_PLAUSI_X)

ET_WL_STRVL_DEL Exporting Store specific work list data table with appropriateentries as for deletion

(Type /STWACS/T_WL_STRVL_PLAUSI_X)

ET_WL_ASS_DEL Exporting Store assignment specific work list data table withappropriate entries as for deletion

(Type /STWACS/T_WL_ASS_PLAUSI_X)

XT_MSG_ERR Changing Error Message table

(Type BAL_T_MSG)

The BAdI /STWACS/X_ENR_PLAUSI is to enable the customer to apply customer-specific logical checks to thework list data that is to be enriched by the enrichment report, that is, program /STWACS/ANA_DATA_ENR.



ExampleA possible plausibility check could e.g. be that a former (e.g. last work list data import and enrichment) senderstore is not identified as a new receiver store within the actual work list data enrichment report run.

Call Stack

Include /STWACS/ANA_DATA_ENR_CHECKF01, that is, form APPLY_PLAUSI_CHECKS of program/STWACS/ANA_DATA_ENR

4.21 /STWACS/X_ENR_PRIORITY (Priority of Work ListEntries)

BAdI method /STWACS/IF_X_ENR_PRIORITY ~GET_PRIORITIES

Interface





ET_PRIORITIES Exporting Work list data priority table

(Type /STWACS/T_PRIORITY_X)

The BAdI /STWACS/X_ENR_PRIORITY is to enable the customer to define priorities on grouping level –see BAdI/STWACS/X_ENR_GROUP above.

Within the Stock Transfer Workbench, such priorities are displayed within the selection area to tell the user whate.g. critical stock transfers are and what stock transfers are of less importance, etc.

Call Stack

Include /STWACS/ANA_DATA_ENR_CUSTF01, that is, form APPLY_CUSTOMER_PRIORITIES of program/STWACS/ANA_DATA_ENR

4.22 /STWACS/X_ENR_RESTRICT (Restriction of Work ListData)

BAdI method /STWACS/X_ENR_RESTRICT ~MODIFY

Interface








ET_WL_CHG Exporting Work list data change table

(Type /STWACS/T_WL_RESTRICT_X)

ET_WL_STRVL_FOR_DEL Exporting Obsolete store specific work list data entry table(Type /STWACS/T_WL_STRVL_RESTRICT_X)

ET_WL_ASS_FOR_DEL Exporting Obsolete store assignment specific work list dataentry table (Type/STWACS/T_WL_ASS_RESTRICT_X)

The BAdI /STWACS/X_ENR_RESTRICT is to enable the customer to restrict the work list data that is to beenriched by the enrichment report, that is, program /STWACS/ANA_DATA_ENR, based own that is, customer-specific needs and considerations, accordingly.

Call Stack

Include /STWACS/ANA_DATA_ENR_CUSTF01, that is, form APPLY_CUSTOMER_RESTRICTIONS of program/STWACS/ANA_DATA_ENR

4.23 /STWACS/X_ENR_VALUE_INFO (Work List Store ValueInformation)

BAdI method /STWACS/IF_X_ENR_VALUE_INFO~GET_VALUE_INFO

Interface





ET_VALUE_INFO Exporting Work list data value info table

(Type /STWACS/T_VALUE_INFO_X)

The BAdI /STWACS/X_ENR_VALUE_INFO is to enable the customer to provide additional information to storespecific work list data in terms of additional explanatory comments.

Call Stack



Include /STWACS/ANA_DATA_ENR_CUSTF01, that is, form APPLY_CUSTOMER_VALUE_INFOS of program/STWACS/ANA_DATA_ENR

4.24 /STWACS/X_ENR_UNIT (Determination of EnrichmentUnit of Measure (Stock + Stock Transfer Quantity))

BAdI method /STWACS/X_ENR_UNIT~DET_OVERALL_UNIT_TO

Interface





ET_UNIT_TO Exporting Target unit of measure table

(Type /STWACS/T_UNIT_X)

The BAdI /STWACS/X_ENR_UNIT is to enable the customer to define the unit of measure for any quantity relatedwork list data entry that is stock as well as stock transfer quantity related.

Call Stack

Include /STWACS/ANA_DATA_ENR_CHECKF01, that is, form APPLY_LOGICAL_CHECKS_UNIT of program/STWACS/ANA_DATA_ENR

www.sap.com/contactsap