Activation of M Records from DataStore Object

Automatic-Notification-for-Process-Chain-Status

Behind The Process Chain

BW_Start Event chain

Following is youtube link which explains the BW architecture in very efficient way. The video needs to be appreciated in the way it captured the wholestic view and interaction between various sections in BW throughout version 3.5 , 7.0 . Awaiting video on 7.3

http://www.youtube.com/watch?v=fovmnSIplpc ( BW 3.5 architecture)

http://www.youtube.com/watch?v=dCcyKmdwVYk (BW 7.0 archetecture)

creating-process-chains-for-dso

Introduction to Process Chains in SAP BI 7.0

Loading Hierarchies Using a Process Chain

Make the Process Green Manually in the Process Chain

Process chain tips and tricks

Process Chains in SAP BI

Process-Chains

Related to Process types in BI 7.0%3a Interrupt and Remote Process chain

Triggering the Process Chains at Last Day of Every Month using Events

Using selective deletion in Process chain

Monitoring in SAP Event Management

Event Management Objects

The following transactions are used to monitor SAP Event Management objects.

/SAPTRX/EH_LIST – Event Handler List

The Event Handler List provides details about an Event Handler. It’s the equivalent of WE05 for Idocs.

EH status
Event Messages
Error messages
Parameters
Tasks executed
History
Measurements, …

/SAPTRX/EE_MON - Expected Events Monitor

Scheduled background job to continuously identify expected events that are past their expected date as set in the expected event extractor / expected event profile. If an event has exceeded the expected date, it’s status is updated to “Overdue” and any defined expected event monitor activity will be executed e.g. Send an alert, email, …

/SAPTRX/EVM_STATUS - Event Message Processing Status List

Lists system generated messages and data related errors for event messages

/SAPTRX/ER_MS_LIST - Event Message Processing Error List

Lists problems during the event message process

/SAPTRX/LOCKED_PROC - Process Event Messages for Locked Event Handler

/SAPTRX/LOCKED_PSET - Process Locked Event Handler Sets
/SAPTRX/EMJOBS – Schedule background jobs for SAP EM

Can check the overview of the related jobs using this transaction

/SAPTRX/ASAPLOG – Application log

Use this transaction in the application System to view the details of errors during the creation of Application Object Types and Event Types

/SAPTRX/CONS_CHECK - Consistency Checks in Customizing

qRFC Monitoring

If you don’t use synchronous processing the SAP EM will make use of qRFC to communicate backwards and forwards with the Application System (AS)

SMQ1 – Outbound qRFC monitor

The queue name here is determined in the BAdI on the AS that initiates the call to the SAP EM interface. See the documentation surrounding queuing in SAP EM.

SMQ2 – Inbound qRFC monitor

General Monitoring

The following are transactions that can also be used to help identify issues on the system.

SM58 - Transaction RFC monitor

If you use tRFC to communicate with SAP EM from the AS the use this to process through any errors in this process

SM59 – RFC Definition

Gain access to the RFC Trace file

SM37 – Job Monitor

Check that the SAP EM jobs are correctly scheduled

SM21 – System Log
ST22 – Short Dumps
SM12 – Lock table
SM13 – Update errors
SM50, SM51, SM66 – Monitor Work processes on the system

Process Chain Monitoring from RSPCM & /SSA/BWT

let us first look at the benefits of monitoring the process chains from ST13 (or /SSA/BWT program) compared to RSPCM transaction.

Process Chain Monitoring from RSPCM	Process Chain Monitoring from /SSA/BWT
Need to add every Process chain MANUALLY to be monitored in RSPCM	Whenever a Process chain is created it is automatically included on the chain's first run.
Only the LATEST INSTANCE of the process chain will be displayed even if it had run multiple times in a day.	All the instances will be displayed in the given time interval.
Details like whether the Process chain is a Main chain or a Sub chain, End Date/Time, Number of sub-chains, Number of steps in each chain, Number of Failed/In-Progress steps, Total number of errors in the chain will NOT be displayed.	All these details can be viewed here.
The Refresh time will be VERY SLOW if the number of process chains included in RSPCM increases.	The time taken for Refresh is very much faster compared to RSPCM.
Added/Transferred number records will NOT be displayed in the detail view	The number of Added/Transferred records will be displayed against each LOADING/DTP_LOAD step in the first detail view.
The Runtime CANNOT be compared for each step in the process chain.	The Runtime for each step in the process chain can be compared.

In many systems, ST13 authorization will not be given. But don’t worry, follow the below steps.

1) In SE38 (or SA38) transaction, enter the Program “/SSA/BWT” and execute (F8)

SAP BW Production Support Issues – Part 4 (Object Lock Issues)

In this post lets discuss the object lock issues that we sometimes encounter in SAP BW production support role.

Lets take the below example where the InfoObject(0material) load has failed and the load monitor (T-Code: RSMO) looks like this.

STEP 1

Go to lock monitor (T-Code: SM12) screen and put an asterisk(‘*’) in the selection for ‘User name’ and then click‘List‘ button at the top, as shown below.

STEP 2

Now the ‘Lock Entry List‘ screen displays all the locks currently set in the system. Click the ‘Find‘ button at the top, as shown in below pic

STEP 3

Now in the ‘Find‘ screen enter the object that has failed; In our caste ‘material‘, as shown in pic below.

If you find an entry in list, then look at ‘Lock Argument‘ to find what action/process is locking the object. Generally this could be another request loading into the same object or a load from this object to other objects. Our load cannot run until the current lock is cleared.

So wait until some time and check again for lock on the object. If you don’t find any entries in list then we are good to resume our load that has failed earlier.

STEP 4

Now go to the load monitor again and then click on ‘Status‘ button. Here click on the ‘Total‘ traffic light as shown below.

STEP 5

Now we will be in ‘QM status set‘ screen. Here select the ‘Status Not OK‘ (red traffic light) option and hit ‘Save‘ button as shown below.

STEP 6

Now, if it’s a transactional load into InfoCube or ODS/DSO then delete the failed request from the data target, and if it’s a master data data into and InfoObject this step is not required.

Note: STEPS 4, 5 and 6 are very important in case of delta loads, otherwise there is a good chance of missing delta records

Now repeat the failed load and should not encounter any lock issues.

How to change table entries in SAP

Pre req: You need to have DEBUG access in the SAP system.

STEP 1
Display the table records using SE16 (For illustration below is the active table of an ODS).

STEP 2

Enter ‘/h’ in command line & Press enter.

Display The records by pressing the Display Button

It will take to Debugging screen.

(Change to classic debugger if you’re in new BI7 debugger as shown below).

Press F7 it reach the below screen

STEP 3

Press F5 to place the cursor on above line. Double click on CODE to display the value in Field names, bottom of the above screen. Delete SHOW, enter EDIT and press change button (R-hand bottom) to change the CODE value.

STEP 4

Then F8, It will show the below screen to change the records manually. Change the values of record and press save to save the record in the table with new value. Do the changes for next records by pressing arrow button and save them individually after changes.

STEP 5

After your changes, exit from the table (Table-> Exit) it will take to the SE16 table display. Refresh and the changes will be displayed as shown in below pic.

SAP BW Production Support Issues – Part 1 (Long running BW loads)

STEP 1:

Go to T-code ‘RSMO‘ and identify the long running load. Then find the ‘Request Number‘ of the load as shown in below pic.

STEP 2:

Clicking on the Req. No. pops up a window as shown in below pic. Copy this Req. No.

STEP 3:

Then goto the Job monitor screen (T-code: SM37) in the source system (Same system if source exist in the same SAP system) and enter the Req. No. we got in STEP 2 as shown below, prefixed with an asterisk ‘*’ and then hit ‘Execute’ button.

This will take you to ‘Job Overview screen‘ as shown below.

STEP 4:

Double clicking on the job in above screen takes you to below screen. Here click on ‘Job details‘ button

STEP 5:

From the job details screen note the PID# as shown below

STEP 6:

Now goto T-code ‘sm66‘ screen which give the global work process overview. Hit ‘find’ button (Ctrl+F) and input the PID# we obtained in STEP5

STEP 7:

This will display the status of our load process (In our example ‘Stopped’ as shown below)

STEP 8:

Clicking on the PID # in above screen will put the cursor on our load process, as shown below.

STEP 9:

Now leave the cursor on our process as in STEP 8 and then goto menu bar ‘Goto‘->’Local work processes‘, as shown below.

STEP 10:

Now you will be in ‘Process Overview‘ screen. Hit Ctrl+F and input our PID# from STEP 5. This will takes you to our load process row.

STEP 11:

Double click on our load process row and you will reach ‘Detail Display‘ screen as shown below. Here our load status will be displayed. (‘Running’ in present case) and also you can find the current action performed by the process (‘Sequential Read’ on a table) as shown below.

STEP 12:

In the same screen, at bottom we can find the detailed information about the database reads/inserts.

In summary:

If the load process is active and progressing, the ‘Action’ message moves continuously from one table to to another and database read count in STEP 12 progresses, then our load is progressing well and we can let it run
If the process gets stuck with status ‘Stopped’ or ‘Waiting’ forever, then we need to investigate the reasons and may have to kill the our process PID# and delete the failed load from targets and restart the load.

SAP BW Production Support Issues – Part 2 (Hanging tRFCs)

We learned how to analyze a long running BW load in Part 1 of SAP BW Production Support Issues series in ‘Process Overview‘ transaction ‘Detail Display‘ screen.

When a BW load takes long time to finish and if the ‘Detail Display‘ screen looks like the pic. below, we need to investigate for hanging tRFCs in the system.

STEP 1

Go to the long running load monitor (T-code: RSMO) screen and from menu at top navigate to ‘Environment‘ -> ‘Transact. RFC‘ and then,

-> To ‘In the Data Warehouse‘ , if the data source is in same SAP system as of the current load

-> To ‘In the source system‘ , if the data source exists in external SAP system (like R/3)

as shown in pic below.

STEP 2

Now we will be in ‘Transactional RFC‘ list selection screen. Here enter the input parameters. Put wild character asterisk ‘*’ in you need to get entire list of tRFC’s in the system as shown below, and hit ‘Execute‘ button.

STEP 3

Now the screen will list all the tRFCs currently scheduled to execute or held up. If a tRFC is held for long time, then we can manually push it by clicking on it from the list and then from menu go to ‘Edit‘ -> ‘Execute LUW‘ or pressing F6 as shown in below pic.

These steps will clear the held up BW loads due to hung tRFCs.

SAP BW Production Support Issues – Part 3 (Long running ODS/DSO Activation)

As part of the Produciton Support Issues of SAP BW series, lets see how to analyze a long running ODS activation step in this post.
STEP 1
Lets assume that we encountered the long running ODS/DSO step in a Process Chain(T-code: RSPC1) as shown in below pic.

STEP 2

Right Click on the ODS activation step in PC and select ‘Administer Data Target‘ from the context menu options as shown below.

STEP 3

Now you will be in ‘manage’ screen of the ODS. Here, copy the activation request number ( ODSR_…..) of the request that is currently in activation status (yellow status) as shown below.

STEP 4
Now go to Table: ‘RSODSACTREQ’ (T-code: SE16) and input the activation request number (obtained in STEP 3) in ‘ACTREQUEST‘ field selection. Now hit the ‘Number of Entries’ button and the number we obtain is the total number of DataPackets to be activated. (1658 in our case, as shown in below pic.)

STEP 5
Now, in the same table browser screen, input ‘status‘ selection condition as ≠0 as shown below and hit ‘execute‘ button at top.

STEP 6

Now look at the ‘DATAPAKID‘ values for non-zero ‘STATUS‘ entries ( DataPackets 836-838 in our case, as shown below)

The conclusion can be that the activation step has finished about 835 DataPackets out of 1658 total DataPackets (about half way) and based on the time it took to reach this point, we can estimate the how long its going to take to complete the ODS activation.

RELATED POSTS

This sections provides knowledge about the transport management in SAP BI. Which includes

a) Transport Creation and adding objects to it.

b) Moving transports from one system to other.

c) Regular issues we face.

d) Best Practices.

Analyzing and Fix the Failed Transports in SAP BW

Collecting Multiple Objects in a Transport through Transport Connection – A Simple way

Detailed View on Transports and the Common Issues in BW 7.0

Display Objects in Transport

How to Handle Inactive Transformations-Transport of Deletions

How to Integrate the Transport Objects between Non-Connected SAP Systems

SAP BW Change Request Management