Help document on Forecasting and Replenishment

Manage Data Consistency for IS-Retail

Forecasting and Replenishment

Best Practice SAP F&R Data Consistency

Version Date: Oct 2008The newest version of this Best Practice can be

obtained in the SAP Service Marketplace<http://service.sap.com/retail>

Content1 General ...................................................................................................................................3

1.1 Introduction........................................................................................................................31.2 Purpose .............................................................................................................................31.3 Roles and Responsibilities .................................................................................................31.4 Focus ................................................................................................................................41.5 Preliminary Tasks ..............................................................................................................41.6 Business Process Overview...............................................................................................6

2 Daily Monitoring Tools for Data Consistency..........................................................................112.1 SM37 – Batchjob Overview..............................................................................................112.2 ST22 – ABAP Dump overview..........................................................................................132.3 FRE_UI – Connectivity Exception Monitor ........................................................................142.4 /FRE/CON – Interface Workbench ...................................................................................182.5 /FRE/BIF_LOG – Interface Log ........................................................................................192.6 /FRE/EXC – Exception Workbench ..................................................................................212.7 /FRE/FRP_LOC_STATUS - Check of Location Status......................................................23

3 Data Consistency Checkreports.............................................................................................253.1 FRE_CHECK_LOC_PROD..............................................................................................25

3.1.1 Implementation........................................................................................................253.1.2 Functionality ............................................................................................................253.1.3 Result......................................................................................................................293.1.4 Interferences and Prerequisites ...............................................................................303.1.5 Scheduling ..............................................................................................................313.1.6 Cleanup of detected inconsistencies........................................................................323.1.7 Miscellaneous..........................................................................................................32

3.2 FRE_CHECK_LAYOUT_MOD.........................................................................................333.2.1 Implementation........................................................................................................333.2.2 Functionality ............................................................................................................333.2.3 Result......................................................................................................................363.2.4 Interferences and Prerequisites ...............................................................................373.2.5 Scheduling ..............................................................................................................383.2.6 Cleanup of Detected Inconsistencies .......................................................................38

Best Practice SAP F&R Data Consistency SAP ERP Retail / SAP F&R

© 2008 SAP AG 2

3.2.7 Miscellaneous..........................................................................................................393.3 FRE_CHECK_SUPPLY_NET ..........................................................................................40

3.3.1 Implementation........................................................................................................403.3.2 Functionality ............................................................................................................403.3.3 Result......................................................................................................................443.3.4 Interferences and Prerequisites ...............................................................................453.3.5 Scheduling ..............................................................................................................463.3.6 Cleanup of detected inconsistencies........................................................................46

4 Checkreports – Operational Overview....................................................................................485 Monitoring in SAP Solution Manager .....................................................................................506 Appendix ...............................................................................................................................51

6.1 Support............................................................................................................................516.2 Documents for Operation of SAP F&R Forecasting and Replenishment ...........................51

7 Copyright...............................................................................................................................52


© 2008 SAP AG 3

1 General

1.1 Introduction

In an integrated SAP scenario with SAP ERP Retail, connected SAP F&R system, SAPF&R receives master data and master data updates from SAP ERP Retail through built-ininterfaces. With own separate databases and high volume of daily master data changes thathave to be sent and processed by complex interfaces, it can never be excluded thatmalfunctions occur, resulting in data inconsistencies on SAP F&R side.

Data inconsistencies can lead to inadequate forecast calculations by using, for example,wrong sources of supply, wrong minimum stocks, wrong procurement cycles, wrong listingintervals, and so on. and can result in out-of-stock or overstock situations and therefore canseriously impact a customers business.

It is impossible for a Retailer to manually check the consistency of all data across systemsfrequently. So, to speed up the detection of issues, data consistency checkreports andmonitoring tools are available in the standard solution of SAP ERP Retail to compare SAPERP Retail and SAP F&R master data and to display found inconsistencies which can berepaired by customers at an early stage.

The data consistency checkreports and monitoring tools ensure that the SAP F&R solutionworks based on correct master data and therefore allow customers to operate their businesssmoothly.

1.2 Purpose

This Best Practice document describes which monitoring tools and data consistencycheckreports in the SAP ERP Retail and SAP F&R system can be used, and how, to ensuredata consistency between these two systems.

With this information you should be able to set up a concept which defines applicationoriented business process steps to use the monitoring tools frequently and to include thecheckreports into the existing job scheduling so that you can detect data inconsistencies atan early stage.

1.3 Roles and Responsibilities

To implement and drive a concept based on this Best Practice document, you require atleast the following team:


© 2008 SAP AG 4

-Application Team and Key Users:This team defines, introduces, integrates and executes application oriented business processsteps to frequently use the monitoring tools FRE_UI, /FRE/BIF_LOG, /FRE/CON,/FRE/EXC.

-IT department or System Administration Team:This team sets up the batchjob scheduling for the checkreports according to the businessprocess requirements defined by the Application Team.

-System Monitoring Team:This team monitors the batchjobs using the monitoring tools SM37 and ST22 but alsoSM50, SM66, and so on, and informs the Application Team or Business Process Championin case of problems.

-Business Process Champion:The Business Process Champion is the person that is responsible for the successfulexecution of the business process. He/she coordinates all activities necessary for thebusiness process. Therefore, he/she is usually responsible for the escalation paths in case ofproblems. Often, the Business Process Champion is a second level in the escalationprocedure, if the application monitoring team needs to escalate an issue.

More information about roles and responsibilities can be found in the super-ordinate BestPractice General Business Process Management, which you can obtain through SAPSolution Manager or the SAP Service Marketplace http://service.sap.com/bpm .

1.4 Focus

This document focuses on the tools and data consistency checkreports that are available inthe standard to ensure data consistency between SAP ERP Retail and SAP F&R, aftermaster and transactional data is transferred from/to SAP ERP Retail to/from SAP F&R.

For the transfer of master and transactional data, the related transactions (FRE01, FRE02,FRE03, FRE04 and so on) on the SAP ERP Retail side can be found in the main SAP ERPRetail transaction WFRE00 for SAP F&R, menu ‘Main Data Transfer to SAP F&R’ and‘Data Transfer to SAP F&R after Customizing Change’.

On SAP F&R side, the related transactions are /FRE/BIF (report /FRE/ BIF_INB01) for theorder outbound and alternatively /FRE/OPM_MASSREL (report/FRE/FU_OPM_MASS_REL).

1.5 Preliminary Tasks

Before using this Best Practice document, ensure that you have performed the followingpreliminary tasks or checks in the system:

http://service.sap.com/bpm


© 2008 SAP AG 5

-Complete all installation and post-installation actions and procedures includingcustomizing.-Ensure that the initial download to SAP F&R has been successfully executed.-Apply all SAP recommendations from SAP Service Sessions and any SAPrecommendations resulting from customer problem messages.-Implement all current SAP Support Packages upon availability.

Keep your current ERP and SCM Support Package level and Plug-In up-to-date, to ensurethat the newest corrections for data consistency are applied. This is the best prerequisite toavoid inconsistencies in advance. Because of the complexity of these corrections and toreduce the effort involved in applying the corresponding SAP Notes individually, it isrecommended that ERP/SCM customers upgrade to the latest Support Package as soon aspossible.


© 2008 SAP AG 6

1.6 Business Process Overview

This section takes you through the main basic core business processes of an SAP F&Rsolution step by step.

SAP AG

Store

RWBS

BWSAP ERP (Retail)

SAP F&R

SAP SCM

send master data

Forecasting and Replenishment

send Daily Sales data(from Cash-Boxes)

send Open PurchaseOrders

BW

Reporting/Analysis

send Historical Sales DataMaintain F&R Profiles

Transfer released OP’s

send Stock/Inventory

send DIF‘s, references

Upload master and transactional data

Exception Handling

Manual Release of OPscreate Purchase Orders

Result:-automatically released Order Proposals

-Exceptions and unreleased OP’s-Forecasted TimeSeries

Supplier

ship articles to Stores

-Exception Handling;-Create/change/release OP’s manually

(RWB)

FRP RunForecasting

Requirements Calculation

Requirements Quantity Optimization

Auto-Release of Order Proposals

Col

lab.

Pla

tform

, Em

ail,

Fax,

ED

I, Fl

atfil

e

RFC

RFC

RFC

RFC

RFC,http

Customers buy articles;inventory is reduced

Start

flatfile

= data consistency check by using the available checkreports after master andtransactional data was transferred to SAP F&R.

Business Process Description:

This business process description will describe only the most important steps that arenecessary to operate an SAP F&R solution. Individual SAP F&R implementations ofcustomers are not considered. Therefore, it can be that individual critical steps are notdescribed, or that some steps in this description are not relevant for specific customers.

Master Data Load:The master data is sent via RFC to SAP F&R using the standard SAP ERP Retail Plug-InInterface.


© 2008 SAP AG 7

Transactional Data Load:Open and changed orders in SAP ERP Retail and Stock/Inventory data are sent to SAPF&R via RFC using the standard SAP ERP Retail Plug-In Interface.

For master data of new SAP F&R relevant article/site combinations there is an initial load(report FRE_INIT_LOAD, transaction FRE01) first from SAP ERP Retail to SAP F&R.This report is supposed to be started once for the initial data supply of SAP F&R. Then, thedelta load (report FRE_DELTA_LOAD, transaction FRE02) for changepointers due tomaster data changes by planners is executed daily.

The sales data per cash-box/store of the current day is sent as consumption data to SAPERP Retail via flatfile.

Report FRE_SEND_TSD (transaction FRE03) is used for the transfer of the stockinformation together with the consumption data (transactional data, time series data) fromSAP ERP Retail to SAP F&R.

Report FRE_DELTA_LOAD or alternatively FRE_ORD_START_OUTB_INTVL(transaction FRE04) is used to transfer open order data from SAP ERP Retail to SAP F&Rvia the standard SAP ERP Retail Plug-In Interface.

DIFs (demand influencing factors like promotions) can be transferred using reportFRE_DIF_INIT_LOAD (transaction FRE11, initial transfer) or reportFRE_DIF_DELTA_LOAD (transaction FRE12, delta transfer).

References for materials without own history can be transferred using reportFRE_SEND_REFERENCE (transaction FRE14).

In an initial data transfer, historical consumption data (sales data) of new SAP F&Rrelevant article/site combinations or its reference articles is sent from SAP BW to SAPF&R via RFC. The horizon is typically 2 years.For this, report /FRE/BIF_BICONS_IMPORT is scheduled as a batchjob in SAP F&R andit requests the related sales data from BW and stores it in SAP F&R keyfigureCONS_DATA as time series in weekly granularity.

The data sent to SAP F&R is stored temporarily in the corresponding inbound interfacetables (tables /fre/bif_*). With report /FRE/BIF_INB01 (transaction /FRE/BIF), the entriesin the /fre/bif_* tables are processed and posted into SAP F&R. The report should bestarted immediately after the data has been sent into the /fre/bif_* interface tables.

The FRP Run is the central function to execute the automatic forecast and replenishmentand the automatic release of order proposals depending on customizing. The forecast andreplenishment calculation is done by the SAF environment where shell scripts execute C++executables on Application Server File System Level where the necessary SAP F&R data isconverted and stored in Flat Files.

The results are forecast time series, order proposals per article/store and also exceptions.The calculation is done internally per store. The calculated forecast time series are stored inthe SAP F&R TSDM-Database (TSDM = time series data management). The orderproposals are stored in the SAP F&R ODM-Database (ODM = order data management).


© 2008 SAP AG 8

The results of the FRP run (exceptions, order proposals) can be reviewed manually by thecentral planner using the SAP F&R RWB Replenishment Workbench.

Alternatively, with the RWBS (Replenishment workbench for Stores, Web-terminal in thestore using http Web-Dynpro, Web-based version of the SAP F&R RWB Replenishment-Workbench but with less functionality) in each local store, the exceptions can be checkedand the order proposals can be changed and released manually by the local planner / storemanager.

If order proposals that are created from the FRP-Run in SAP F&R could not be releasedautomatically due to exceptions, they have to be checked and released manually by theplanner. This could be done in the RWB or via RWBS.

With the release of an order proposal its status is set to green, this is the prerequisite for thetransfer to SAP ERP Retail later. The release of Order Proposals can be done manually orby executing the mass release report /FRE/FU_OPM_MASS_REL.

Afterwards, the released order proposals are transferred from SAP F&R to SAP ERP Retailusing the outbound interface of report /FRE/BIF_INB01 or report/FRE/FU_OPM_MASS_REL with flagged checkbox for the transfer. In SAP ERP Retail,the order proposals are converted automatically to purchase orders.If orders in SAP ERP Retail are changed or still are open, these orders are sent again toSAP F&R via the daily delta load and are taken into account again by the next FRP-Run.

To enable reporting and analysis afterwards via SAP BW, analytical information like orderproposal data and exceptions can be extracted to SAP BW.The analytics data is updated at the end of the FRP Run.

Additional weekly step:In SAP F&R, consumption data from the stores is aggregated weekly from dailygranularity to weekly granularity using transaction /FRE/TS_AGG_DAY_WEEK (report/FRE/FU_TS_AGGREG_DAY_WEEK). The weekly granularity is necessary for the FRPRun.


© 2008 SAP AG 9

Example of daily process steps and the related monitoring tools and consistencycheckreports:

Step Daily Process System Sequence Time MonitoringTool

Checkreport

1End of master datamaintenance byplanners.

SAP ERPRetail

18:00

2FRE02: transfermaster datachanges to SAPF&R into /fre/bif_*interface tables.

SAP ERPRetail

12:00 –13:30

18:00 –19:30

SM37, ST22,FRE_UI

3/FRE/BIF: process/fre/bif_* interfacetables to updateSAP F&R withmaster datachanges.

SAP F&R after 2 SM37, ST22,/FRE/CON,/FRE/BIF_LOG

FRE_CHECK_LOC_PROD,FRE_CHECK_LAYOUT_MOD,FRE_CHECK_SUPPLY_NET

4Transfer stock(FRE03), open andchanged Orders(FRE02, FRE04)from SAP ERPRetail into /fre/bif_*tables.

SAP ERPRetail

19:30 –20:30

SM37, ST22,FRE_UI

5/FRE/BIF: process/fre/bif_* tables toupdate SAP F&Rwith stock data,open and changedOrders.


6Send POS data(daily sales /consumption data)from Stores intoSAP ERP Retail.

Store whendeterminedin the store

21:00 –23:00

7FRE03 : send POSdata (consumptiondata) into /fre/bif_*tables.

SAP ERPRetail

after 6 SM37, ST22,FRE_UI

8/FRE/BIF: process/fre/bif_* tables toupdate SAP F&Rwith consumptiondata.


9FRP Run SAP F&R after 8 00:00 –

03:00ST22,/FRE/EXC,/FRE/FRP_LOC_STATUS


© 2008 SAP AG 10

10Store-Manager :check inventory,change/create/release OP‘s and processExceptions viaRWBS.

RWBS,Store

after 9 05:00 –07:00

11Central Planner :change/create/release OP‘s and processExceptions via RWBor RWBS.

SAP F&R after 9, 10 08:00 –18:00

12/FRE/OPM_MASSREL: Mass release oforder proposals.

SAP F&R after 10, 11 SM37, ST22,/FRE/EXC

13/FRE/BIF or/FRE/OPM_MASSREL: Transfer OrderProposals to SAPERP Retail.

SAP F&R after 10, 11,12

11:00 –12:30

SM37, ST22,/FRE/CON,/FRE/BIF_LOG


© 2008 SAP AG 11

2 Daily Monitoring Tools for Data Consistency

The following monitoring tools should be executed and used daily to be able to detect datainconsistencies at an early stage.

2.1 SM37 – Batchjob Overview

Action to ensure data consistency:

Transaction SM37 should be monitored to check if background jobs for the SAP F&Rinterface that transfer data into SAP F&R like FRE_DELTA_LOAD, FRE_SEND_TSD,/FRE/BIF_INB01 and so on, could finish successfully without error.If the status of the background job should be ‘cancelled’ or if the runtime of the job issignificantly higher than usual and the job does not fit into the available time windowanymore, then the responsible key user or business process champion has to be informedimmediately to decide about the next actions to ensure that the business requirements canstill be met.The root cause for the cancellation or the performance problem has to be analyzed andsolved as soon as possible.

If the user wants to select the jobs for a specific report like FRE_DELTA_LOAD, thereport name can be entered on the selection screen of SM37 into the field ‘ABAP programname’.


© 2008 SAP AG 12

If the batchjob cancelled due to a dump, the transactions ST22 (ABAP Dump analysis) andSM21 (System Log) should be checked for more information.For analyzing performance issues of a currently running batchjob, the transactions SM50and SM66 should be used as a starting point (then further ST03N, STAD, ST02, ST04 andso on).

If, for example, the FRE_DELTA_LOAD cancels, not all changepointers could beprocessed and therefore not all master data changes could be transferred to SAP F&Rleading to temporary inconsistencies. The FRE_DELTA_LOAD should then be restarted toprocess the remaining changepointers.


© 2008 SAP AG 13

2.2 ST22 – ABAP Dump overview


Transaction ST22 should be checked if dumps occurred for background jobs that transferdata into SAP F&R like FRE_DELTA_LOAD, FRE_SEND_TSD, /FRE/BIF_INB01 andso on. If such dumps are found in ST22, then the responsible key user or business processchampion has to be informed immediately to decide about the next actions to ensure thatthe business requirements can still be met.The root cause for the dumps has to be analyzed and solved as soon as possible.


© 2008 SAP AG 14

2.3 FRE_UI – Connectivity Exception Monitor

Transaction FRE_UI is the ‘Connectivity Exception Monitor - User Interface for Messages’and is a monitor for the outbound and inbound interface between SAP ERP Retail and SAPF&R.

FRE_UI can be used to show the content and to delete and retransfer data packages fromprevious interface runs (for example, FRE01-FRE04).Errors, warnings, other transfer information and so on that occur during outboundprocessing from SAP ERP Retail to SAP F&R and inbound processing from SAP F&R toSAP ERP Retail can be displayed as so-called messages. The transmitted datasets are savedinto Files, to give the users the possibility to repeat the transmission if an error on thereceiving site should have happened. FRE_UI can be used to check every singleinbound/outbound data package if it was sent successfully.

With the radio buttons, you can switch between the functions of the report.

Function ‘Show Messages / Exceptions’:

This function can be used to check error/warning messages.The select option “Interface” can be used to show only a specific type of master ortransactional data:


© 2008 SAP AG 15

The select option “Transmission Date” is used to show only interface runs of the specifieddate.The select options “Object” and “Object Key” could be used to further filter the selectionfor analysis aspects.The Select Option “Message Type” can be used to select Messages with a specific status:E (Error), W (Warning), S (Success), I (Info), A (Abort).

Function ‘Show interface Files’:

The select option “Filename” can be used to specify a specific filename, for example,20080311110247I.


© 2008 SAP AG 16

The select option “Interface” can be used to show only a specific type of master ortransactional data, for example, MD2 for location product data.The select option “Send Date” can be used to show only files created on the specified date.

Example:Though FRE_DELTA_LOAD finishes successfully in SM37, FRE_UI shows that singledata packages/files sent via RFC were not transferred successfully due to a technical orfunctional problem.

The erroneous files could be retransmitted to SAP F&R using the FRE_UI reprocessingfunction. This function includes more than only a retransmission of the selected files,because the retransmission could overwrite current documents with out of date informationin the target system. This would happen if the same SAP ERP Retail document would becontained in an erroneous data transmission and also in a later and correctly processed datatransmission. In this case, a retransmission of the failed dataset would lead to an error,because the up to date values in the document would be overwritten with out of date valuesfrom preceding transmissions. The reprocessing function therefore reads the actual datafrom the corresponding SAP ERP Retail tables for all the documents contained in the fileand transmits the latest version of the document to SAP F&R.


© 2008 SAP AG 17


Use function ‘Show Interface Files’ to check the outbound interface after FRE01-FRE04was run. If there are Interface files displayed with a red light, then the responsible key useror business process champion has to be informed immediately to decide about the nextactions to ensure that the business requirements can still be met, for example,retransferring the red files using the button ‘Retransmitt’.The root cause for the red files has to be analyzed and solved as soon as possible.


© 2008 SAP AG 18

2.4 /FRE/CON – Interface Workbench

SAP AG

SAP F&R Connectivity Workbench trx /FRE/CON

Monitor for F&R interfaceprocessing via Trx /FRE/BIF:

check for not processed orerroneous data.


The Connectivity Workbench transaction /FRE/CON in SAP F&R should be checked afterthe report /FRE/BIF_INB01 has finished to look for records that could not be processedand posted successfully into SAP F&R. These records remain in the /fre/bif_* interfacetables with status E (Error) or P (in process) and can be displayed in /FRE/CON.Additionally, erroneous records with segments without headers are listed in the statusoverview.In such a case, the responsible key user or business process champion has to be informedimmediately to decide about the next actions to ensure that the business requirements canstill be met.First, the exceptions that show the cause of the problem that the records could not beposted have to be checked and solved for each erroneous record.Afterwards, those records have to be reset to status N (new, not processed yet) via report/FRE/BIF_INB03 before they can be reprocessed with report /FRE/BIF_INB01.


© 2008 SAP AG 19

2.5 /FRE/BIF_LOG – Interface Log

To see only red erroneous Log entries from previous runs of report /FRE/BIF_INB01,check the radio button [x] ‘Only important logs’.


© 2008 SAP AG 20


Check the details and the message text of the erroneous red log entries, after report/FRE/BIF_INB01 has finished. Then, inform the responsible key user or business processchampion immediately to decide about the next action to solve the cause of the error andto ensure that the business requirements can still be met.


© 2008 SAP AG 21

2.6 /FRE/EXC – Exception Workbench

In the Exception Workbench transaction /FRE/EXC on the SAP F&R side which is basedon the alert monitor, the SAP F&R exception messages can be listed when an appropriateprofile is maintained.

It is possible to select different types of SAP F&R exception business areas in the profilefor which the related exception messages can be displayed after ‘Redetermine Alerts’ :

System AdministrationCustomizingMaster DataDemand Influencing FactorsInventory ManagementConsumptionForecastReplenishmentOrder Quantity OptimizationOrder Proposal ManagementOrder Proposal Release Management


© 2008 SAP AG 22


Check at least the detailed description of the erroneous red Priority 1 exception messages.Then, inform the responsible key user or business process champion immediately todecide about the next action to solve the cause of the exception and to ensure that thebusiness requirements can still be met.


© 2008 SAP AG 23

2.7 /FRE/FRP_LOC_STATUS - Check of Location Status

The transaction /FRE/FRP_LOC_STATUS (report FRE/UI_FRP_SHOW_LOC_STATUS)displays a list showing the status, start and end time of the last FRP Run for each locationand the single execution steps.

Listed tasks:/FRE/FU_CL_FRP_MAINT_LOC_BAS/FRE/FU_CL_FRP_SAFOUT_ONDEM/FRE/FU_CL_FRP_SAFOUT_NOCRITMD/FRE/FU_CL_FRP_CONFIG_CHECK/FRE/FU_CL_FRP_SAFRUN_NOCRIT/FRE/FU_CL_FRP_SAFOUT_NOCRITTD/FRE/FU_CL_FRP_SAFOUT_CRIT/FRE/FU_CL_FRP_SAFRUN_CRIT/FRE/FU_CL_FRP_DIF_DELTA_SET/FRE/FU_CL_FRPMID_LOC_RESET/FRE/FU_CL_FRP_OPM/FRE/FU_CL_FRP_SAFIN_RWB/FRE/FU_CL_FRP_SAFIN_ANA


© 2008 SAP AG 24

The Location GUID is also listed.If Errors/Fatal errors are displayed, this could indicate an inconsistent data status in theSAF environment.


Check transaction /FRE/FRP_LOC_STATUS after each FRP Run and check the status ofeach listed task. If the status shows errors, inform the responsible key user or businessprocess champion immediately to decide about the next action and to ensure that thebusiness requirements can still be met. This could be, for example, restarting of the FRPRun for the specific location with erroneous tasks after the cause of the problem was foundand solved. To get information about the cause of the problem, check the exceptions of theFRP Run using transaction /FRE/EXC.


© 2008 SAP AG 25

3 Data Consistency Checkreports

In this section, the data consistency checkreports that are available in the standard aredescribed. In Section 4, the most important information is combined in an OperationalOverview.

The checkreports can be executed in case of found data inconsistencies or, periodically, tosearch for potential data inconsistencies and to check the data status in the SAP F&Rsystem so that you can detect data inconsistencies at an early stage.

3.1 FRE_CHECK_LOC_PROD

3.1.1 Implementation

This checkreport for location product data is included in the following service packs:SAP ERP 2005 SP13 SAP SCM 5.0 SP13SAP ERP 2005 EhP2 SP3 SAP SCM 5.1 SP06SAP ERP 2005 EhP3 SP2 SAP SCM 7.0SAP ERP 2005 EhP4 SAP SCM 7.0

3.1.2 Functionality

Report FRE_CHECK_LOC_PRODto be executed on System SAP ERP RetailTransaction FRE_C1ERP Release ERP 2005 and higherSAP F&R Release SCM 5.0, 5.1 and higher

The report FRE_CHECK_LOC_PROD (transaction FRE_C1) is included in the SAP menutree for Forecasting and Replenishment in SAP ERP Retail that can be reached viatransaction WFRE00.

The report FRE_CHECK_LOC_PROD compares location product master data and optionalsales price, listing information, reference modules and unit of measure between SAP ERPRetail and SAP F&R and displays found inconsistencies like missing location product datain SAP F&R or SAP ERP Retail as well as differing location product master data fieldvalues.

In a first step on the SAP ERP Retail side, the relevant location products that exist inFRE_DB_ART_SITE are read according to the selected site and article.


© 2008 SAP AG 26

The required data from SAP F&R is collected via remote function call using FM/FRE/MD_CHK_READ_DATA.Then, the required data is selected from the SAP ERP Retail side using FMFRE_MD_CHK_READ_DATA.

In a following step, the collected master data values from SAP ERP Retail and SAP F&Rare compared.

The report compares master data fields from the following database tables:SAP ERP Retail SAP F&R

marc /sapapo/matloc

mara /sapapo/matloc

marm /sapapo/matkey

wlk1 /sapapo/matloctd

wrf_ref_head /sapapo/matloc, /fre/refmod_head

wrf_ref_item /fre/refmod_item

Master data fields which are maintainable manually are not compared. Instead, only masterdata fields which are “Maintainable only using the interface” (see customizing ofMaintainable Attributes in SAP F&R, table /SCMB/MDL_AU_CUS) are compared,otherwise inconsistencies with the SAP ERP Retail system would be the rule. Furthermore,only these fields will also be used for displaying inconsistencies in the output.

Selection screen:

Master data:Site

Article

F&R System

The displayed F&R System is determined from FRE_SEND_OPTION-SEND_DEST. Thefield is not ready for input.

Check options:

Check Selection:Check Location/Product Data checkboxCheck Reference Module checkboxCheck Unit of Measure checkbox


© 2008 SAP AG 27

If Check Location/Product Data is checked then Check Sales Prices and Check ListingStatus can be selected.

Time Dependent Field Check:Check Sales Prices checkboxCheck Listing Status checkbox

Additional Checks:Consider BAdI entrance SAP F&R checkboxConsider Change Pointers checkboxChange pointer period Field, 3-digits [hours]Consider F&R Interface Tables checkbox

Consider BAdI entrance SAP F&R:The implemented BAdIs in the inbound interface of SAP F&R are checked here. For thecomparison of location product data between the SAP ERP Retail system and SAP F&R itis necessary to process these inbound BAdIs, too.The following SAP F&R Inbound BAdIs have to be processed if implemented:/FRE/IF_CON_BADI_005 – method IF_CON_BADI_005_ENR_PRODUCT/FRE/IF_CON_BADI_009 – method IF_CON_BADI_009_ENR_PRODLOC/FRE/IF_EX_IF_CON_BADI_023 – method IF_CON_BADI_023_ENR_REFMOD

Consider Change Pointers/ Change pointer period:If the check for change pointers is flagged, the report determines at the beginning if thereare relevant unprocessed change pointers in the defined past time period in hours for anarticle/site combination. If yes, the found corresponding differences are considered astemporary and are not shown.

Consider F&R Interface Tables:If the check for interface tables (/fre/bif_* tables) is flagged, the report checks at thebeginning if there are relevant BIF-entries for an article/site combination. If yes, the foundcorresponding differences are considered as temporary and are not shown.

Output Control:Max Number of Inconsistencies

Split by site checkboxSummary checkboxIssue inconsistencies with changepointer/interface entry

checkbox

Job interruption in batch checkbox

Maximum number of inconsistencies per spool:


© 2008 SAP AG 28

The user can enter the number of inconsistencies per output/spool. In interactivemode, the maximum number cannot exceed 10.000 inconsistencies due tolimitation of the used grid control for displaying.

Split by site:If this checkbox is flagged, a spool split will be performed not only in regards tothe inconsistency type, but also in regards to the site number if the report runs inbackground. The site number will be part of the spool title. Reference moduleand Unit of measure inconsistencies are not split by site.In the summary, the deviations are always split by site whether this checkbox isset or not.

Summary:If this checkbox is flagged, the report will issue an additional output (ALV Gridin interactive or spool in batch processing) containing the overall number ofchecked location products as well as the number of deviations per field.

Split by site is always considered by the Summary function.

Issue inconsistencies with change pointer/interface entry:This checkbox allows the user to choose whether he/she would just want theinconsistencies not to be issued, or if he/she would prefer the inconsistenciesissued but marked with an icon indicating that change pointers or interfaceentries have been found for the inconsistency.

Job interruption in batch:If this checkbox is flagged and if inconsistencies are detected by the batchjob, the job thenends with a red status ‘Cancelled’ in SM37 and shows the following lines in the joblog:-Inconsistencies found during processing!-Job cancelled after system exception ERROR_MESSAGE

Performance Options:Parallel Processing checkboxLogon/server group

Max. number parallel processes

Article/Site comb. p. Package

If the checkbox for Parallel Processing is checked, the other fields will be visible.If Parallel Processing is activated, the selected data volume is split automatically andprocessed in parallel DIA processes executed on the entered logon server group. Themaximum number of those parallel DIA processes can be entered. The number of locationproducts processed per task can be entered in the field ‘Records per Package’.Using Parallel Processing can significantly improve the performance of the report.

Separate register Exclude fields :


© 2008 SAP AG 29

On this separate register, the master data fields that have to be excluded from theconsistency check can be selected. This could be fields that are modified in a user exit orBAdI that can not be considered by the checkreport and therefore would lead topermanently displayed inconsistencies.

3.1.3 Result

For found inconsistencies, a separate spool (in background processing) or ALV Grid (ininteractive processing) is created for each type of inconsistency (Summary,Location/Product, RefMod Header, RefMod item, TimeDependent, UoM).

For the Summary, an own ALV Grid or spool is created.

In interactive processing it is possible to switch between the various inconsistency typeswith buttons in the button line.

A button for an inconsistency type will only be shown if the type exists in the set of foundinconsistencies. The inconsistent fields are highlighted in red (the red colour for the SAPERP Retail column is slightly different from the SAP F&R column).

The output (spool or ALV Grid) contains columns for SAP ERP Retail fields and next toeach column on the right side the corresponding SAP F&R field. In order to distinguishthem better, the SAP ERP Retail fields are coloured in a slightly darker shadow than theSAP F&R fields.The first column to the left contains an indicator telling the user what type of inconsistencyapplies to the output row:

If the report was executed in background as a job, the inconsistencies are displayed inspools. The spool numbers can be taken out of the joblog in sm37 and can be displayed intransaction SP01.

When Split by Site is checked, then in background processing, a separate spool per site iscreated.


© 2008 SAP AG 30

Note the following points:1) If Parallel Processing is activated, the spool numbers are not mentioned in the joblog butcan be determined and displayed via transaction SP01.

2) Note that a listing horizon/interval of one day is not considered by theFRE_CHECK_LOC_PROD because single day listings are not transferred by SAP ERPRetail to SAP F&R.

3) Fields that are not transferred by SAP ERP Retail to SAP F&R like PROFCST and otherprofiles like PROEXCP, PROFREQ should not be customized in SAP F&R as "MaintainOnly Using Interface", otherwise deviations after manual changes in SAP F&R will alwaysbe displayed by FRE_CHECK_LOC_PROD as inconsistency.

4) The Sales Price is only considered as Time Dependent if more than one Sales Priceexists in SAP ERP Retail (different Sales Prices are valid for different time intervals;seasonal change of Sales Price). In this case, more than one Sales Price is transferred toSAP F&R and considered there as time dependent (/SAPAPO/MATLOCTD). TheFRE_CHECK_LOC_PROD then considers deviations for Sales Price as inconsistency typeTime DependentIf there is only one Sales Price in SAP ERP Retail, it will be considered as not TimeDependent though SAP F&R copies this value into /SAPAPO/MATLOC and also/SAPAPO/MATLOCTD.

3.1.4 Interferences and Prerequisites

Interferences:

Reports that should not run in parallel:

FRE_INIT_LOAD + /fre/bif_inb01

FRE_REINIT_LOAD + /fre/bif_inb01

FRE_DELTA_LOAD + /fre/bif_inb01

FRE_SEND_REFERENCE + /fre/bif_inb01

RWRF_REF_AUTO_ASSIGNMENT

RWRF_REF_DB_REORG

/FRE/FU_REFMOD_REORG

FRE_LOAD_VKP_DELTA + /fre/bif_inb01

/SAPAPO/DM_REORG_PROD_LOC_TD

These reports should not run in parallel to FRE_CHECK_LOC_PROD because thesereports can change data that is checked by the report.


© 2008 SAP AG 31

Prerequisites:

1) The consistency of table FRE_DB_ART_SITE compared to MARC has to be ensured.This table is used to determine the location products out of the selection that have to bechecked.

2) Execute the report FRE_MD_PRODUCT_CLEAN frequently, for example, weekly, toensure consistency of the product table FRE_MD_PRODUCT.

3) A prerequisite for checking reference module data is that the reportsRWRF_REF_DB_REORG (SAP ERP Retail) and /FRE/FU_REFMOD_REORG (SAPF&R) were executed in advance.

4) For Sales Price changes, no change pointers are created, therefore please execute thereport FRE_LOAD_VKP_DELTA + /fre/bif_inb01 in advance before checking Salesprices.

3.1.5 Scheduling

The report has to be scheduled outside the critical job chain, depending on the availabletimeframes and system resources.

The report has to be scheduled using the Parallel Processing option with a high number oftasks and optimized number of locations per task depending on the available systemresources.

If you want to check the total data volume, a selection with blank entry for site and productor wildcards like * are not allowed, therefore please enter a suitable selection to cover thecomplete data volume, for example, a range of locations.

Check the total data volume frequently in a 1 or 2-week cycle.

Additionally, there could be one small job scheduled daily with a small reference datavolume and short runtime to check for general inconsistencies (one or more referencelocation(s), or specific locations for which Init Load or Delta Load have just transferredsignificant/critical changes or high amount of new/changed data).


© 2008 SAP AG 32

3.1.6 Cleanup of detected inconsistencies

The content of the displayed spool or ALV Grid can be downloaded manually with thebutton

‘Local file…’ or ‘Save to local file…’ into a spreadsheet file. Then, in Excel, the file canbe sorted and filtered. The location products that have to be corrected and retransferred toSAP F&R can be copied by Cut&Paste and entered into the selection forFRE_REINIT_LOAD.

To cleanup the detected location product inconsistencies, the report FRE_REINIT_LOAD+ option P_LOCPR (‘Send Location Product data to F&R’) has to be scheduled for theinconsistent location products. Afterwards, report /FRE/BIF_INB01 for option Product,Location, Product Location has to be executed to post the entries from the /fre/bif* tablesinto the SAP F&R database.

To correct reference module inconsistencies, FRE_REINIT_LOAD + option P_REFMOD(‘Send Reference Module data to F&R’) + option P_LOCPR (‘Send Location Product datato F&R’) has to be executed. Afterwards, report /FRE/BIF_INB01 for option Product,Location, Product Location, Reference Modules has to be executed to post the entries fromthe /fre/bif* tables into the SAP F&R database.

Alternatively, the report FRE_SEND_REFERENCE can be executed to send referencemodule data to SAP F&R.

To correct Sales Prices inconsistencies, the report FRE_LOAD_VKP_DELTA +/FRE/BIF_INB01 for option Product, Location, Product Location has to be executed.

3.1.7 Miscellaneous

To delete outdated reference data on SAP F&R side, transaction /FRE/REF_REORG canbe used.

To delete outdated location products on SAP F&R side, report/FRE/DB_MATLOC_DELETE can be used.


© 2008 SAP AG 33

3.2 FRE_CHECK_LAYOUT_MOD


This checkreport for location product data is included in the following service packs:SAP ERP 2005 SP13 SAP SCM 5.0 SP13SAP ERP 2005 EhP2 SP3 SAP SCM 5.1 SP06SAP ERP 2005 EhP3 SP2 SAP SCM 7.0SAP ERP 2005 EhP4 SAP SCM 7.0

3.2.2 Functionality

Report FRE_CHECK_LAYOUT_MODto be executed on System SAP ERP RetailTransaction FRE_C3ERP Release ERP 2005 and higherSAP F&R Release SCM 5.0, 5.1 and higher

The report FRE_CHECK_ LAYOUT_MOD (transaction FRE_C3) is included in the SAPmenu tree for Forecasting and Replenishment in SAP ERP Retail that can be reached viatransaction WFRE00.

The report FRE_CHECK_ LAYOUT_MOD compares layout module data between SAPERP Retail and SAP F&R and displays found inconsistencies like missing layout moduledata in SAP F&R or SAP ERP Retail as well as deviations in layout module data fieldvalues.

In a first step, on the SAP ERP Retail side the relevant location products existing inFRE_DB_ART_SITE are read according to the selected location and product.

The required data from SAP F&R is collected via remote function call. Then, the requireddata is selected from the SAP ERP Retail side.

In a following step, the report searches for inconsistencies by comparing the layout moduledata between SAP ERP Retail and SAP F&R.

The report compares SAP ERP Retail layout module data with the following SAP F&Rdatabase tables:SAP ERP Retail SAP F&R

MALG, WLMV, WRS1-LAYGR,WRSZ

/FRE/LAYOUT, /SAPAPO/MATLOCTD


© 2008 SAP AG 34

On SAP F&R side, layout module data is determined from the database table/FRE/LAYOUT in SAP F&R and, in the case of time dependent layout module fields (forexample, stock), also from table /SAPAPO/MATLOCTD.On the SAP ERP Retail side, the layout information is determined from tables MALG,WLMV, WRS1-LAYGR,WRSZ and so on.Only released and actual or future (according to sy-datum) layout module version data ischecked.


Selection screen:

Master data:Site

Article

F&R System


Check options:

Additional Checks:Consider BAdI entrance SAP F&R checkboxConsider Change Pointers checkboxChange pointer period Field, 3-digits [hours]Consider F&R Interface Tables checkbox

Consider BAdI entrance SAP F&R:The implemented BAdIs in the inbound interface of SAP F&R are checked here. For thecomparison of layout module data between the SAP ERP Retail system and SAP F&R, it isnecessary to process these inbound BAdIs too.The following SAP F&R Inbound BAdIs have to be processed if implemented:/FRE/IF_CON_BADI_020 – method ENRICH

Consider Change Pointers/ Change pointer period:If the check for change pointers is flagged, the report checks at the beginning if there arerelevant unprocessed change pointers for message type FRE_LAYMOD in the defined pasttime period in hours. If yes, the found corresponding differences are considered astemporary and are not shown.


© 2008 SAP AG 35

Consider F&R Interface Tables:If the check for interface tables (/fre/bif_* tables) is flagged, the report checks at thebeginning if there are relevant BIF-entries. If yes, the found corresponding differences areconsidered as temporary and are not shown.

Output Control:Max Number of Inconsistencies

Split by site checkboxSummary checkboxIssue inconsistencies with changepointer/interface entry

checkbox


Maximum number of inconsistencies per spool:The user can enter the number of inconsistencies per output/spool. In interactivemode, the maximum number cannot exceed 10.000 inconsistencies due tolimitation of the used grid control for displaying.

Split by site:If this checkbox is flagged, a spool split will be performed, not only in regards tothe inconsistency type but also in regards to the site number if the report runs inbackground. The site number will be part of the spool title.In the summary, the deviations are always split by site whether this checkbox isset or not.



Issue inconsistencies with change pointer/interface entry:This checkbox allows the user to choose whether he/she would just want theinconsistencies not to be issued, or if he/she would prefer the inconsistenciesissued but marked with an icon indicating that change pointers or interfaceentries have been found for the inconsistency.

Job interruption in batch:If this checkbox is flagged and if inconsistencies are detected by the batchjob, the job thenfinally ends with a red status ‘Cancelled’ in SM37 and shows the following lines in thejoblog:-Inconsistencies found during processing!-Job cancelled after system exception ERROR_MESSAGE


© 2008 SAP AG 36




If the checkbox for Parallel Processing is checked, the other fields will be visible.If Parallel Processing is activated, the selected data volume is split automatically andprocessed in parallel DIA processes executed on the entered logon server group. Themaximum number of those parallel DIA processes can be entered. The number of locationproducts processed per task can be entered in the field ‘Records per Package’.Using Parallel Processing can significantly improve the performance of the report.

Separate register Exclude fields :On this separate register, the master data fields that have to be excluded from theconsistency check can be selected. This could be fields that are modified in a user exit orBAdI that can not be considered by the checkreport and therefore would lead to permanentdisplayed inconsistencies.

3.2.3 Result

For found inconsistencies, a separate spool (in background processing) or ALV Grid (ininteractive processing) is created for each type of inconsistency (Summary, LayoutMod,TimeDependent).

For the Summary, an own ALV Grid or spool is created.

In interactive processing it is possible to switch between the various inconsistency typeswith buttons in the button line.

A button for an inconsistency type will be only be shown if the type exists in the set offound inconsistencies.

The output (spool or ALV Grid) contains columns for SAP ERP Retail fields and, next toeach column on the right side, the corresponding SAP F&R field. To distinguish thembetter, the SAP ERP Retail fields are coloured in a slightly darker shadow than the SAPF&R fields.The first column to the left contains an indicator telling the user what type of inconsistencyapplies to the output row:


© 2008 SAP AG 37

The inconsistent fields are highlighted in red (the red colour for the SAP ERP Retailcolumn is slightly different from the SAP F&R column).

If the report was executed in the background as a job, the inconsistencies are displayed inspools. The spool numbers can be taken out of the joblog in sm37 and can be displayed intransaction SP01.

When Split by Site is checked, then in background processing, a separate spool per site iscreated.

Note the following points:

1) If Parallel Processing is activated, the spool numbers are not mentioned in the joblog butcan be determined and displayed via transaction SP01.


Interferences:




RWRF_LAYOBJ_REORG

/FRE/DB_LAYOUT_REORG

These reports should not run in parallel to FRE_CHECK_LAYOUT_MOD because thesereports can change data that is checked by the report.

Prerequisites:

1) The consistency of table FRE_DB_ART_SITE compared to MARC has to be ensured.This table is used to determine the location products out of the selection that have to bechecked.


© 2008 SAP AG 38

2) A prerequisite for checking layout module data is that the reportsRWRF_LAYOBJ_REORG (SAP ERP Retail) and /FRE/DB_LAYOUT_REORG (SAPF&R) were executed in advance.

3.2.5 Scheduling

The report has to be scheduled outside the critical job chain depending on the availabletimeframes and system resources.

The report has to be scheduled using the Parallel Processing option with a high number oftasks and an optimized number of locations per task, depending on the available systemresources.

If you want to check the total data volume, a selection with a blank entry for site andproduct or wildcards like * are not allowed, therefore please enter a suitable selection tocover the complete data volume, for example, a range of locations.


Check the total data volume frequently in a 1 or 2-week cycle.


3.2.6 Cleanup of Detected Inconsistencies


‘Local file…’ or ‘Save to local file…’ into a spreadsheet file. Then, in the Excel, the filecan be sorted and filtered. The location products that have to be corrected and retransferredto SAP F&R can be copied by Cut&Paste and entered into the selection forFRE_INIT_LOAD.

To cleanup the detected inconsistencies, the report FRE_INIT_LOAD + optionP_LAYMOD (‘Send layout modules’) has to be scheduled for the inconsistent layoutmodule data by entering location and article as selection for site and material for theselection.


© 2008 SAP AG 39

Please note: FRE_REINIT_LOAD does not transfer layout module data to SAP F&R;instead, the FRE_INIT_LOAD has to be used.

Afterwards, on the SAP F&R side, the report /FRE/BIF_INB01 has to be executed foroption LAYOUT to post the entries in the /fre/bif* tables into the SAP F&R database.

3.2.7 Miscellaneous

In customizing ‘Maintain Basic Settings for Data Transfer’, the checkbox ‘Send LayoutModules’ has to be flagged (fre_send_option-send_laymod is set to ‘X’) to activate theoptions in FRE_INIT_LOAD and FRE_DELTA_LOAD to send layout module data


© 2008 SAP AG 40

3.3 FRE_CHECK_SUPPLY_NET


This checkreport for supply net data is included in the following service packs:SAP ERP 2005 SP13 SAP SCM 5.0 SP13SAP ERP 2005 EhP2 SP3 SAP SCM 5.1 SP06SAP ERP 2005 EhP3 SP2 SAP SCM 7.0SAP ERP 2005 EhP4 SAP SCM 7.0

3.3.2 Functionality

Report FRE_CHECK_SUPPLY_NETto be executed on System SAP ERP RetailTransaction FRE_C2ERP Release ERP 2005 and higherSAP F&R Release SCM 5.0, 5.1 and higher

The report FRE_CHECK_SUPPLY_NET (transaction FRE_C2) is included in the SAPmenu tree for Forecasting and Replenishment in SAP ERP Retail, which can be reached viatransaction WFRE00.

The report FRE_CHECK_SUPPLY_NET compares supply net data (internal and externaltransportation lanes) between SAP ERP Retail and SAP F&R and displays foundinconsistencies like missing transportation lanes in SAP F&R or SAP ERP Retail as well asdeviations in supply net data field values.

Depending on the SAP F&R release, the supply network consists of different tables. Thereport considers if the old lanes model or the new lanes model is active (tableFRE_SEND_OPTION, field FRE_NEW_LANES).

In a first step on the SAP ERP Retail side, the relevant location products that exist inFRE_DB_ART_SITE are selected according to the selection with Site (=target location,locnoto) and Article.

The required supply net data is collected from SAP F&R via remote function call.

Then, the required supply net data is determined on SAP ERP Retail side (SOS source ofsupply determination).

In a following step, the collected supply net data from SAP ERP Retail and SAP F&R iscompared.


© 2008 SAP AG 41

The report compares SAP ERP Retail supply net data with the following SAP F&Rdatabase tables:SAP ERP Retail SAP F&R

eine, eina, marc, mara, wrf3, lfm2, SOSmapping logic

/sapapo/tpsrc, /sapapo/trprod, /fre/trprod2,/fre/trprod2td, /fre/lane, /fre/lanetd


Selection screen:

Master Data:Site

Article

F&R System


Check options:

Lane TypesCheck Internal Lanes checkboxCheck External lanes checkbox

If the checkbox Check Internal Lanes is checked, only transportation lanescoming from table WRF3 will be subject to the checks.

If the check box Check External Lanes is checked, only transportation lanescoming from purchase inforecords will be subject to the checks. This includespurchase info records with a DC as vendor.

Additional Checks:Check Purchase Prices checkboxConsider rounding effects checkboxCheck Time Dependent Data checkboxConsider BAdI entrance F&R checkboxConsider Change Pointers checkboxChange pointer period Field, 3-digits [hours]


© 2008 SAP AG 42

Consider F&R interface tables checkbox

Check Purchase Prices:Because purchase prices will only be determined for external lanes, the checkbox‘Check Purchase Prices’ will only be available if checkbox ‘Check ExternalLanes’ is marked.The currently valid purchase prices of both systems are compared.

Consider rounding effects:In the SAP F&R inbound processing, natural rounding effects can occur whenthe SAP ERP Retail prices have to be converted into the one common F&Rclient currency.With the checkbox ‘Consider rounding effects’, the report therefore ignoresinconsistencies of an absolute difference of 0,0001 units between SAP ERPRetail and SAP F&R to reduce the amount of inconsistencies raised from therounding effect.

Check Time Dependent Data:With ‘Check Time Dependent Data’, inconsistencies regarding time dependentsupply net data (transportation lanes for sub ranges (/FRE/TRPROD2TD)) canbe found and displayed.

Consider BAdI entrance F&R:The implemented BAdIs in the inbound interface of SAP F&R are checked here. For thecomparison of supply net data between the SAP ERP Retail system and SAP F&R, it isnecessary to process these inbound BAdIs too.The following SAP F&R Inbound BAdIs have to be processed if implemented:/FRE/IF_CON_BADI_010 TRPROD2, TRPROD2TD/FRE/IF_CON_BADI_011 TRPROD/FRE/IF_CON_BADI_012 TPSRC, CSCALE/PCOST, LANE, LANETD

(method IF_CON_BADI_012_ENR_TPSRC)

Consider Change Pointers/ Change pointer period:If the check for change pointers is flagged, the report checks at the beginning if there arerelevant unprocessed change pointers in the defined past time period in hours. If yes, thefound corresponding differences are considered as temporary and are not shown.

Consider F&R Interface Tables:If the check for interface tables (/fre/bif_* tables) is flagged, the report checks at thebeginning if there are relevant BIF-entries. If yes, the found corresponding differences areconsidered as temporary and are not shown.

Output Control :Max Number of Inconsistencies

Split by site checkboxSummary checkbox


© 2008 SAP AG 43

Issue inconsistencies with changepointer/interface entry

checkbox


Maximum number of inconsistencies per spool:The user can enter the number of inconsistencies per output/spool. In interactivemode, the maximum number cannot exceed 10,000 inconsistencies due tolimitation of the used grid control for displaying.

Split by site:If this checkbox is flagged, a spool split will be performed not only in regards tothe inconsistency type but also in regards to the site number if the report runs inbackground. The site number will be part of the spool title.In the summary, the deviations are always split by site whether this checkbox isset or not.



Issue inconsistencies with change pointer/interface entry:This checkbox allows the user to choose whether he would just want theinconsistencies not to be issued, or if he would prefer the inconsistencies issuedbut marked with an icon indicating that for the inconsistency change pointers orinterface entries have been found.

Job interruption in batch:If this checkbox is flagged and if inconsistencies are detected by the batchjob, the job thenfinally ends with a red status ‘Cancelled’ in SM37 and shows the following lines in thejoblog:-Inconsistencies found during processing!-Job cancelled after system exception ERROR_MESSAGE




If the checkbox for Parallel Processing is checked, the other fields will be visible.If Parallel Processing is activated, the selected data volume is split automatically andprocessed in parallel DIA processes, executed on the entered logon server group. The


© 2008 SAP AG 44

maximum number of those parallel DIA processes can be entered. The number of locationproducts processed per task can be entered in the field ‘Records per Package’.Using Parallel Processing can significantly improve the performance of the report.

Separate register Exclude fields :On this separate register, the master data fields that have to be excluded from theconsistency check can be selected. This could be fields that are modified in a user exit orBAdI that can not be considered by the checkreport and therefore would lead to permanentdisplayed inconsistencies.

3.3.3 Result

For found inconsistencies, a separate spool (in background processing) or ALV Grid (ininteractive processing) is created for each type of inconsistency (Summary, LANE,LANTD, TRPROD2, TRPROD2TD, PCOST…).

For the Summary an own ALV Grid or spool is created.

In interactive processing, it is possible to switch between the various inconsistency typeswith buttons in the button line.

A button for an inconsistency type will only be shown if the type exists in the set of foundinconsistencies. The inconsistent fields are highlighted in red colour (the red colour for theSAP ERP Retail column is slightly different from the SAP F&R column).

The output (spool or ALV Grid) contains columns for SAP ERP Retail fields and next toeach column on the right side the corresponding SAP F&R field. In order to distinguishthem better, the SAP ERP Retail fields are coloured in a slightly darker shade than the SAPF&R fields.The first column to the left contains an indicator telling the user what type of inconsistencyapplies to the output row:

If the report was executed in the background as a job, the inconsistencies are displayed inspools. The spool numbers can be taken out of the joblog in sm37 and can be displayed intransaction SP01.


© 2008 SAP AG 45

When Split by Site is checked, then in background processing a separate spool per site iscreated.

Please note the following points:

1) If Parallel Processing is activated, the spool numbers are not mentioned in the joblog butcan be determined and displayed via transaction SP01.

2) For changes of purchase prices, BDCP2 change pointers are only created which arereflected by an EINE-NETPR update. This implies that a customer would make sureto run report RM06INP0 (transaction ME1B) to update EINE-NETPR as soon as acondition is changed. Only then the change will be updated to SAP F&R. Theconsistency check for purchase prices only makes sense if this procedure is followedas otherwise inconsistencies will be the rule.


Interferences:



FRE_REINIT_LOAD + /fre/bif_inb01


FRE_PROCYC_AFT_CUST_CHG + /fre/bif_inb01

These reports should not run in parallel to FRE_CHECK_SUPPLY_NET because thesereports can change data that is checked by the report.

Prerequisites:The consistency of table FRE_DB_ART_SITE compared to MARC has to be ensured. Thistable is used to determine the location products out of the selection that have to be checked.


© 2008 SAP AG 46

3.3.5 Scheduling


The report has to be scheduled using the Parallel Processing option with high number oftasks and optimized number of locations per task depending on the available systemresources.

If you want to check the total data volume, a selection with blank entry for site and productor wildcards like * are not allowed, therefore please enter a suitable selection to cover thecomplete data volume, for example, a range of locations.

Please check the total data volume frequently in a 1- or 2-week cycle.


3.3.6 Cleanup of detected inconsistencies


‘Local file…’ or ‘Save to local file..’ into a spreadsheet file. Then, in Excel, the file can besorted and filtered. The target location / article combinations for the transportation lanesthat have to be corrected and retransferred to SAP F&R can be copied by Cut&Paste andentered into the selection for FRE_REINIT_LOAD.

To cleanup the detected inconsistent supply net data, the report FRE_REINIT_LOAD +option ‘Send Transportation Lane data to F&R’ should be scheduled afterwards for theinconsistent transportation lanes by entering target location and article as selection for siteand material.The FRE_REINIT_LOAD also sends Delete-records to delete the current transportationlanes on SAP F&R side together with Insert-records for creating new consistent lanes.

Afterwards, on the SAP F&R side the report /FRE/BIF_INB01 must be executed for option‘Transportation Lane Subranges’ + ‘Transportation Lane Products’ to post the BIF-entriesinto SAP F&R.

To correct inconsistencies related to procurement cycles, the transaction FRE20 (reportFRE_PROCYC_AFT_CUST_CHG) on SAP ERP Retail side should be executed with theinconsistent procurement cycles. Afterwards, on the SAP F&R side the report


© 2008 SAP AG 48

4 Checkreports – Operational OverviewConsistencyCheck Object

Consistency CheckTool

Consistency CheckFrequency and Time

Indicator for aninconsistency

InconsistencyHandlingProcedure

Respon-sibility

EscalationProcedure

What to check? How to check? When and how often? How to identify aproblem?

How to correct aproblem?

Whoexecutes?

Who mustbeinformed?

-check locationproduct masterdata andoptional salesprice, listinginformation,referencemodules andunit of measure.

-cross-systemcomparison andcheck betweenSAP ERP Retailand SAP F&R.

-schedule SE38,standard reportFRE_CHECK_LOC_PROD as background job.

-use a specific selectionfor the daily check.

-use a specific selectionfor the periodical check.

-use checkboxes toselect the objects thathave to be checked.

-use the parallelizationoption to reduce theruntime.

-use option ‘Jobinterruption in batch’,then if inconsistenciesare detected thebatchjob finally endswith a red status(‘Cancelled’) in SM37.

-daily for few referenceor critical sites orarticles with shortruntime as part of thedaily job chain.

-periodically weekly orbi-weekly for completedata volume outside thecritical job chain or timewindow.

-prerequisites: scheduledirectly after FRE02 +/FRE/BIF.

-prerequisitesspecifically if option‘check ReferenceModule’ is selected:executeRWRF_REF_DB_REORG and/FRE/FU_REFMOD_REORG in advance.

-do not schedule whenFRE01, FRE02,FRE_REINIT_LOAD,FRE_LOAD_VKP_DELTA,/SAPAPO/DM_REORG_PROD_LOC_TD or/FRE/BIF is running.

-specifically if option‘check ReferenceModule’ is selected: donot schedule ifFRE_SEND_REFERENCE,RWRF_REF_AUTO_ASSIGNMENT,RWRF_REF_DB_REORG or/FRE/FU_REFMOD_REORG is running.

-the batchjobends with a redstatus(‘Cancelled’) inSM37.

-in the joblog amessage’Inconsistencieswere found’ israised and spoolnumbers arementioned orcan be displayedvia transactionSP01.

-the spools arefilled with foundinconsistencies.

-correct thearticle/sitecombinationswith listedinconsistenciesby retransferringthe master datausing transactionFRE01 (InitialLoad) on SAPERP Retail sidewith the relevantselect options,for example,‘SendLoc/Prod/LocProd/TranspLanesData to F&R’.

-alternatively useReportFRE_REINIT_LOAD and option‘Send LocationProduct data toF&R’.

-afterwardstransaction/FRE/BIF onSAP F&R sidehas to executedwith the relevantselection optionslike PRODUCT,PRODLOC,LOCATION,P_REFMOD.

-the article/sitecombinationsthat have to becorrected haveto be extractedmanually out ofthe spools.

-key user.

-businessprocesschampion.

-BasisTeam.

-automaticjob chainscheduling tool.

-key user.


-check supplynet master datafor external andinternaltransportationlanes andinforecord salesprice.


-schedule SE38,standard reportFRE_CHECK_SUPPLY_NET as backgroundjob.





-use option ‘Jobinterruption in batch’,then if inconsistenciesare detected the

-daily for few referenceor critical targetlocations or articles withshort runtime as part ofthe daily job chain.



-do not schedule whenFRE01, FRE02,FRE_REINIT_LOAD,FRE_PROCYC_AFT_CUST_CHG, /FRE/BIF isrunning.




-correct thearticle/targetlocationcombinationswith listedinconsistenciesby retransferringthe master datato SAP F&Rusing transactionFRE01 (InitialLoad) with therelevant selectoptions, forexample, ‘SendLoc/Prod/LocProd/TranspLanesData to F&R’

-alternatively useReportFRE_REINIT_LOAD and option‘Send

-key user.


-BasisTeam.


-key user.



© 2008 SAP AG 49

batchjob finally endswith a red status(‘Cancelled’) in SM37.

TransportationLane data toF&R’.

-inconsistenciesrelated toprocurementcycles have tobe correctedusing transactionFR20 toretransferprocurementcycle data toSAP F&R.

-afterwardstransaction/FRE/BIF onSAP F&R sidehas to executedwith the relevantselection optionslike TRSUB,TPSRC&TRSUB, LANE,PROCYC.

-the article/sitecombinationsthat have to becorrected andretransferredhave to beextractedmanually out ofthe spools.

-check layoutmodule masterdata.


-schedule SE38,standard reportFRE_CHECK_LAYOUT_MOD as backgroundjob.





-use option ‘Jobinterruption in batch’,then if inconsistenciesare detected thebatchjob finally endswith a red status(‘Cancelled’) in SM37.

-daily for few referenceor sites or articles withshort runtime as part ofthe daily job chain.



-do not schedule whenFRE01, FRE02,RWRF_LAYOBJ_REORG,/FRE/DB_LAYOUT_REORG or /FRE/BIF isrunning.




-correct thearticle/targetlocationcombinationswith listedinconsistenciesby retransferringthe master datausing transactionFRE01 (InitialLoad) with therelevant selectoptions, forexample, ‘Sendlayout modules’.

-afterwardstransaction/FRE/BIF onSAP F&R sidehas to executedwith the relevantselection optionLAYOUT.

-the article/sitecombinationsthat have to becorrected andretransferredhave to beextractedmanually out ofthe spools.

-key user.


-BasisTeam.


-key user.



© 2008 SAP AG 50

5 Monitoring in SAP Solution Manager

Please take a look at the newest versions of Best Practice documents for Business ProcessMonitoring on SAP Service Marketplace under <http://service.sap.com/bpm> .

For some monitoring activities, it is possible to use a tool for automated monitoring. Suchautomated monitoring is optimally implemented using Business Process Monitoring inSAP Solution Manager.Business Process Monitoring (BPMon) within SAP Solution Manager is the proactive andprocess-oriented monitoring of the core business processes of your company. It includesthe observation of all technical and business application-specific functions that are requiredfor a smooth and reliable flow of the business processes.Business Process Monitoring (BPMon) reveals even slight deviations from a pre-definedideal business process state which would otherwise remain undetected until the flow of theprocess would be seriously impacted. It gives automated alerts including the possibility tonotify these via various communication means like email, SMS and so on.Types of errors that can be monitored are for example, errors from logs (system log,application log and so on), throughput and backlog KPIs for various applications, dialogperformance, update errors, and so on.The possibility to keep the alerts for a defined time allows you to evaluate a kind of historyand to identify trends in the alert occurrence at an early state.Wherever monitoring via SAP Solution Manager is possible, you will find a separate tablefor the specific business process step, indicating the relevant automatic monitoringfunctionalities.

http://service.sap.com/bpm


© 2008 SAP AG 51

6 Appendix

6.1 Support

In case…

-you should observe issues with the checkreports-you should observe issues in the interface leading to inconsistencies between SAP ERPRetail and SAP F&R that are not yet resolved by an existing SAP note-you need help to find the root cause of found inconsistencies-you experience the necessity to analyze the status of inconsistencies for other types of datain the SAP F&R system that are not covered by the existing checkreports

…then please create a customer message on component SCM-FRE-IF with the appropriatepriority.

6.2 Documents for Operation of SAP F&R Forecastingand Replenishment

Documents are available on the retail homepage of the SAP Service Marketplace(http://service.sap.com/retail). Choose "SAP for Retail in Detail" >> "Forecasting &Replenishment".

Online documentation is available under help.sap.com. Choose “SAP for Industries” >>“SAP for Retail” >> “SAP Forecasting and Replenishment”.

http://service.sap.com/retail


© 2008 SAP AG 52

7 Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for anypurpose without the express permission of SAP AG. The information contained herein maybe changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390,AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks ofIBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®,World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. Allother product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specificationsmay vary.

The information in this document is proprietary to SAP. No part of this document may bereproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.


© 2008 SAP AG 53

This document is a preliminary version and not subject to your license agreement or anyother agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does notwarrant the accuracy or completeness of the information, text, graphics, links, or otheritems contained within this material. This document is provided without a warranty of anykind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct,special, indirect, or consequential damages that may result from the useof these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has nocontrol over the information that you may access through the useof hot links contained in these materials and does not endorse your use of third-party Webpages nor provide any warranty whatsoever relating to third-party Web pages.

Help document on Forecasting and Replenishment

Documents

Transcript of Help document on Forecasting and Replenishment