Business process step 2: Run change version to evaluate master data changes, collect and prepare data, create IDoc

2.3.2.1 Description and general information

This step runs the job for the daily change version which collects the changes done by business in daily online transactions like article maintenance, listing, price maintenance, customer maintenance. It selects the changes done recently and the changes becoming valid in the customized relevant period. The changes are evaluated and the data, which need to be transferred, are prepared, completed, and saved in an IDoc.

Here too, the distinction depending on configuration takes place if HPR features like WIND or BDCP2 are evaluated.

The following transactions and reports are used:

Classic assortment list: WDBU Report RWDBBUPD HPR assortment list: WDBU_HPR Report RWDBBUPD: HPR Scenario-specific sample

The data are prepared for the stores selected in the job variant.

For the process of the assortment list supporting the data transmission to a POS system, a daily data update to POS is usually the best business practice. Therefore, both reports for the change version have the option to ignore the cycle time of the assortment list. The cycle time is usually only important for the printed assortment list and if full versions and change version follow each other or get together in a mixed version.

This is not required for the work with the assortment list sent to the POS system, because the POS system needs the changes daily or even immediately.

2.3.2.2 Monitoring requirements Error monitoring

For error monitoring of a change message, the POS monitor transaction WPER is used mainly. It is also necessary to monitor the job in SM37.

Performance monitoring

For performance monitoring of a change message, you have to watch the runtime of the job.

Throughput monitoring

To increase throughput, parallel processing should be used. The reports for creating change versions allow you to select several stores and to set the flag for parallelization and enter a server group where parallel process can run on and also the maximum number of parallel processes.

Backlog monitoring

It is important to watch the runtime of the job regularly. If a job takes too long, it must be considered that, as long as it is not finished, the IDocs are not created and the prices and other data cannot be sent to the store in time. That would increase the risk that stores are selling articles which are incorrectly priced.

The operator has to be in touch with the business process champion so the business can inform the operating team about large data changes at one time. Otherwise, POS outbound is likely to work with much

more changes than necessary. For example, when a new season with new prices starts or new collections are listed, the operator has to change the starting time of the report RWDBBUPD or RWDBBUPD_HPR to accommodate for longer runtime caused by a larger amount of data.

Scenario-specific sample

It is import that RWDPOSUP finishes in time before stores are opening and require correct prices.

So if stores open at 8.00 o’clock and transmission and conversion need around one hour it must be ensured that the report RWDBBUPD or RWDBBUPD_HPR is finished not later than 7.00 o’clock.

2.3.2.3 Monitoring objects in SAP Solution Manager

Monitoring Object

Selection Criteria Alert Analysis Tool on

Satellite System error messages in job log

SM37 Runs usually daily; monitor when job is running in periodic intervals system/ runtime performance

2.3.2.4 Further monitoring objects

Monitoring Object Selection Criteria Alert Analysis Tool on Satellite System

Look for tree branch in outbound processing – not fully processed – preparation mode U = update double click to read system log text with error message

WPER After job execution

2.3.2.5 How to find meaningful thresholds per monitoring object

You can determine the threshold when POS outbound needs to be finished depending on your business needs. Therefore, you need to work backwards on your timetable under consideration of the time for conversion and for transmission as well as some security time to determine when RWDPOSUP has to be finished latest. Then you need to work out with business how many changes they do on average and look how long job takes on average and work backwards. If business leaves average due to business reason, you have to accommodate threshold once more and start the job earlier.

2.3.2.6 Error handling per monitoring object Background job for RWDBBUPD or RWDBBUPD_HPR Check the job log for cancellations and runtime.

2.3.2.7 Scheduling of background jobs

This job is usually scheduled on a daily basis in the evening after all master data changes have been carried out in the system. Depending on the version used, either the program RWDBBUPD or the program RWDBBUPD_HPR is used.

Job scheduling requirements

2.3.3 Business process step 3: Copy IDocs within ECC retail (optional) and send out IDocs from ECC retail

2.3.3.1 Description and general information

The POS download IDocs (POS outbound IDocs and assortment list IDocs) from many stores are identical or only differ very slightly. To optimize performance and decrease runtime it is not necessary to generate IDocs for all stores but just for certain reference stores. Then, those IDocs created for the reference stores with RWDPOSUP in step before, can be copied according to certain rules. This can significantly improve performance. The following chapter describes how this works. Note, that this is optional. IDoc copy management is not possible for all customers (for example, if store individual prices exist).

In addition, for the initial supply of a new store you can use IDoc copy management as a one-off for the initialization (as described in step 1) if the stores can be grouped and a reference store can be determined.

Then for the stores which are able to get a copied IDoc only a dummy initialization is required.

To enable copy management for IDocs, there must be a copy rule in the SAP system. A programming interface port must be assigned to the reference recipient. Define an ABAP programming interface port in the port description (IDoc and EDI basis) and assign it to the function module WDL_COPY_LOG. File ports must be assigned to the recipients of the copies. All recipients that are assigned to a reference must be assigned to one and the same file port. The partner profiles for the recipients must be maintained in such a way that IDocs are collected first. The IDoc copy management tool sends the IDocs automatically.

Various applications generate outbound IDocs for the reference recipients. Using the programming interface port, which is assigned to each reference customer within the partner profile, the SAP system logs these reference IDocs in table WDLCOPY. The IDoc copy management tool uses this log.

The program RWDLCOPY_MANAGE copies the reference IDocs to the recipients (customers) that are assigned to it using the copy rule. It then generates trigger files for the individual recipients for each message type if this is set in the copy rule.

The tool optimizes its performance internally using asynchronous processes. Multiple scheduling is therefore not recommended.

A second program, which is mandatory, is the program RSEOUT00 which sends out the collected IDocs in the SAP ECC database as files to the following conversion tool. RSEOUT00 is only necessary if in the partner agreement configuration in WE20 the IDocs are set to collect IDocs. SAP strongly recommends this because of performance and monitoring reasons and as stated above, it is mandatory for the IDoc copy management tool.

2.3.3.2 Monitoring requirements Error monitoring

You have to control the logs and monitor the jobs for the reports RWDLCOPY_MANAGE and

RSEOUT00

See screenshot how the job’s log for the report RWDLCOPY_MANAGEMENT looks like:

Figure 21: Result of IDoc copy management tools

Performance monitoring

You need to monitor the runtime of jobs for both reports but usually they are not performance critical. The most performance critical is RWDBBUPD or RWDBBUPD_HPR POSUP in the step before.

Throughput monitoring

Just make sure that RWDLCOPY_MANAGE and RSEOUT00 are planned in time before the data are required in the store for selling and under consideration of required time for data conversion and transmission outside SAP ECC.

Backlog monitoring

Just make sure that RWDLCOPY_MANAGE and RSEOUT00 are planned in time before the data are needed in the store.

2.3.3.3 Monitoring objects in SAP Solution Manager

Monitoring

WE05 or WE02 every 15 minutes

2.3.3.4 How to find meaningful thresholds per monitoring object

You have to determine the thresholds depending on your business needs when POS outbound has to be finished. So if necessary, you can backwards schedule the jobs RWDLCOPY_MANAGE and RSEOUT00 under consideration of the time needed for conversion and transmission and with some security time reserve 2.3.3.5 Error handling per monitoring object

Background job for RWDLCOPY_MANAGE and RSEOUT00 Check the job log for cancellations and runtime.

2.3.3.6 Scheduling of background jobs

If copy management is used, the jobs are usually scheduled daily after the assortment list was generated.

Job scheduling requirements

2.3.4 Business process step 4: Monitor, correct, and repeat data transfer of assortment list 2.3.4.1 Description and general information

For the operator role, the business process for the assortment list has a separate transaction, the POS monitor. This transaction should be viewed daily after processing of the change version, after initialization and after manual request.

The POS monitor is not only to view errors, it is also a great tool to view the successful transmissions and also to enable to find the corresponding IDocs after a report or request for POS assortment list has been performed.

This can be valuable also to track a request and the corresponding IDoc number through the process steps outside SAP ECC that you know when and with which content IDoc was created.

Scenario-specific sample

You can verify the following information using the POS monitor:

The recipient of the IDoc

The system type that the IDocs belong to (POS outbound or assortment list) When IDocs are created for the recipient

The type of preparation (for example, initialization, change message) Whether preparation and transfer of data was completed

Number of IDocs which were created for each recipient Whether the IDocs were created completely for each recipient

To which IDoc type the IDoc in question belongs (for example, article master, EAN/UPC references) The key (IDoc number) under which the IDocs can be found in the database

How many segments the IDoc contains

Which IDocs contain errors, and how many errors (you can display an error log for incorrect IDocs) Which data areas are contained in the IDoc (smallest and largest object key)

Which data an IDoc contains