Tuesday, August 27, 2013

How to Restart a Failed Process Chain if Repeat Option is not Applicable

Introduction

Sometimes the process chain fails at particular step due to some kind of error and the “Repeat” option also
will not be applicable for the failed process. This article explains the steps for how to complete the process
chain and get the issue resolved.

Business Scenario

1. Data is loaded from R3 to BI using process chain. Variants involved in process chain are to load data
from R3 to different InfoProviders in BI.
2. Data is loaded successfully in one of the DSO (Z_OFCPS), but the process chain failed while further
data load to next DSO (Z_OPSF01).
3. This is because while doing the delta update, there are some erroneous records found and the process
chain failed.
4. Manual corrections are made on the erroneous records and uploaded data manually in the DSO
(Z_OPSF01).
5. The process chain is restarted from the One Step Ahead where it was failed as the manual corrections
are done and loaded data. Therefore, that step has to be skipped. (Also as process chain contains many
steps to be executed, and doing it manually is not a best practice.)

Step by Step Solution

The process chain fails at the step below while loading data into InfoProvider (marked in red box).


Process chain failure at this step is due to the erroneous records. It is necessary to manually correct it and
load data manually into the respective InfoProviders.
Once the data is loaded successfully at this step, start the process chain from next step onward as this step
is not required to execute again.

Finding the Variants and Instance of the Failed Process

Right-click the failed process. Select the Displaying Messages option.


It will open the screen as below.


Copy the Variant and Instance from above screen.
Go to the transaction SE11. Select the table – RSPCPROCESSLOG. 
Put the value for variant and instance received from above screen.



Execute this, and the value of the other fields is returned: LOG_ID, TYPE, BATCHDATE and BATCHTIME.

Report to Execute Process Chain

Go to the transaction SE38. Enter the program name - RSPC_PROCESS_FINISH and execute.
Enter the values in the fields received from above table. Additionally, make the STATE as „G‟ -> Execute.


Once the program is executed with all mandatory fields as described above, it will move the process chain to the next step. And the process chain execution will start from that step as below screenshot. Also it will mark
the previously failed step as green.

The next data load can be done smoothly.

Monday, August 26, 2013

Inventory Management (0IC_C03) Part:2


Introduction:

To monitor the Inventory Management and to take any decisions on Inventory Controlling, 
Management/Users need reports on Inventory Management; basically they need complete status/details of 
the all Materials i.e. from Raw Materials to Finished Goods. I.e. In-Flow and Out-Flow of the Materials in the Organization.
In the coming Articles we will discuss about Process Keys and Movement Types and other details.

DataSources:

A DataSource is a set of fields that provide the data for a business unit for data transfer into BI System. From 
a technical viewpoint, the DataSource is a set of logically-related fields that are provided to transfer data into 
BI in a flat structure (the extraction structure), or in multiple flat structures (for hierarchies).
There are two types of DataSource (Master Data DataSources are split into three types.):
1. DataSource for Transaction data.
2. DataSource for Master data.
a) DataSource for Attributes.
b) DataSource for Texts.
c) DataSource for Hierarchies.
To full fill the Industry requirements, SAP given the following Transactional DataSources for Inventory 
Management/ Materials Management.
1. 2LIS_03_BX : Stock Initialization for Inventory Management.
2. 2LIS_03_BF : Goods Movements From Inventory Management.
3. 2LIS_03_UM : Revaluations.
All the above DataSources are used to extract the Inventory Management/ Materials Management data from 
ECC to BI/BW.

About 2LIS_03_BX DataSource:

This DataSource is used to extract the stock data from MM Inventory Management for initialization 
to a BW system, to enable the functions for calculating the valuated sales order stock and of the 
valuated project stock in BW.
See the SAP help on 2LIS_03_BX DataSource.

About 2LIS_03_BF DataSource:

This DataSource is used to extract the material movement data from MM Inventory Management 
(MM-IM) consistently to a BW system. A data record belonging to extractor 2LIS_03_BF is defined 
in a unique way using the key fields Material Document Number (MBLNR), Material Document 
Year (MJAHR), Item in Material Document (ZEILE), and Unique Identification of Document Line 
(BWCOUNTER).
See the SAP help on 2LIS_03_BF DataSource.

About 2LIS_03_UM DataSource:

This DataSource is used to extract the revaluation data from MM Inventory Management (MM-IM) 
consistently to a BW system.
See the SAP help on 2LIS_03_UM. DataSource.
To use the all above DataSources, first you need to install in ECC. See the steps given below.

How to Install?

In ECC using Transaction Code RSA5, we can install the above DataSources. SAP given all DataSources in the form of “Delivered Version (From this System)”, once you install it, then the status will changes to “Active Version”.


Select the DataSources one by one and Click on Activate DataSources.


Post Process DataSources:

Once we install the DataSources, it will be available in RSA6 and you can see the DataSources in RSA6.
So go to Transaction Code RSA6 and then do the Post Processing steps that are required for DataSources.


Select DataSource and then click on Change Icon and



Once you click on Change Icon, it will go to DataSource Customer Version, here you can hide the unwanted fields and you can select the fields for Data Selection in InfoPackage. After that you save and come back.


Selection:

Set this indicator to use a field from the DataSource as the selection field in the Scheduler for BW. Due to the properties of the DataSource, not every field can be used as a selection field.

Hide Field:

To exclude a field in the extraction structure from the data transfer, set this flag. The field is then no longer available in BW for determining transfer rules and therefore cannot be used for generating transfer structures.

Inversion:

Field Inverted When Cancelled (*-1)
The field is inverted in the case of reverse posting. This means that it is multiplied by (-1). For this, the extractor has to support a delta record transfer process, in which the reverse posting is identified as such.
If the option Field recognized only in Customer Exit is chosen for the field, this field is not inverted. You cannot activate or deactivate inversion if this option is set.