Process chains administration

Hi experts!
I want your advice about the best way for administering process chains.
We have been adding process chains because of delivering new models and now we want to adopt best practices about the way to monitor these process.
We use RSPCM transaction to monitor process chains (and eventually many others : rsmon, changerunmoni, etc) but we want to implement automated warnings that can alert via email about: process chains terminated with red status, process chains still running after certain hour (long running or "hanged " process), or even process chains that do not run but have to.
We have programmed emails from process chains, we know about ccms alerting...but still we don't know about which practice to adopt.
We think about developing some abap code with events handling, but we want to know if there are not better ways.
Thanks in advance

Hi,
Please check the following links these might help you
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/9bdd42cadf2878e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/92/5e073c8e56f658e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/bb/f0033c128f4a7de10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/bb/f0033c128f4a7de10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/bb/f0033c128f4a7de10000000a114084/frameset.htm
Regards,
MADhu

Similar Messages

Need information-BW System administration-process chains

Hi gurus,
I need information about BW System administration-process chains
can anyone send me the docs related to
1)process chain modellin aspects
2)process chain monitoring &error handling
3)BW statistics and query tuning with aggregates
Thanks in advance..
regards
s ram

Hi,
Check these links:
http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ce/dc87c1d711f846b34e0e42ede5ebb7/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d5/e80d3dbd82f72ce10000000a114084/frameset.htm
Process Chain
process chain
BW STATISTICS
If you are asking abt the flags that you see in RSA1 -> Tools -> BW Stats...you can check BW Stats for each and every infoprovider. Whenever you create an infopprovider you should always decide whether you want to turn on the BW Stats for this infoprovider. This is a manual step and can be done in each and every box individually or can be transported across the systems. Coming to your question...BW Stats are of two kinds...
1) OLAP -
If you check this flag for an infoprovider...all the statistical data for the queries built on this infoprovider gets updated into the corresponding infocubes (0BWTC_C02 and 0BWTC_C03). An example would be like number of users that ran the report in a given time, the average run time of the query and so on. This data is of immense value in deciding the steps for performance tuning techniques like aggregates!
2) WHM (Warehouse Management) -
If you turn this flag on for an infoprovider, all the statistical data like how often the cubes are loaded, when are the requests deleted from the infocubes, data abt condensing of cubes and so on is loaded into the corresponding cubes like 0BWTC_C04, 0BWTC_C05, 0BWTC_C09 and 0BWTC_C11.
You have to activate the infopackages to load into these cubes and schedule them through process chain to run once in a while so that your statistical data is uptodate.
Production support for maintaining the process chains primarily involves monitoring activities of all the chains that are running in the background...
Errors in monitoring of process chains can be categorized into 4 different sections...
Master data - Full Update
Master data - Delta Update
Transaction data - Full Update
Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
Majority of the issues will be based on these things only..
****Assign Points If Helpful****
Regards,
Ravikanth
Message was edited by:
RK.PNV

Archiving Administration data in a process chain using BWREQARCH

On our project i need to archive administration data.But i want to do it using a process chain. Whatever is needed to archive data like program BWREQARCH in a step in a process chain.
any help in this regard will be really helpful. ~Thanks in advance.
--sumit

Hi
I am really curious of your answer to change that to background.
Is it a new feature of BW7.0 ? I am going to have a look, as it it very interesting.
The tiem out issue is due to a lakc of performances in the treatment of data in each package, as you will have one DIA for each packageof your load.
To reduce the probability of time out:
- check the routines you have in the update rules
- check that the indexes of the cube you laod are dropped before you start to laod as you might create contention during the load.
PY

Process chain for personal administration

Hi
I have standard cube 0PA_C01
have 2 datasources.
0HR_PA_0
0HR_PA_1
both are full directlty to cube?
i created process chain like this
START
DELETE PSA REQUEST (0HR_PA_0)
DELETE PSA REQUEST (0HR_PA_1)
LOAD TO PSA ( 0HR_PA_0_
LOAD TO PSA ( 0HR_PA_1)
DELETE DATA TARGET CONTENT ( 0PA_CO1)
DTP (0HR_PA_0)
DTP ( 0HR_PA_1)
CREATE INDEXES
Please let me know my chain is correct or i need to do any modifications?

Hi Suneel....
i used sequence instead of parallen, will be any probelm?
Look.........we use parallel method......bcoz it will help to reduce the runtime of the Process chain....
Again for parallel mechanism there r many loop holes..........bcoz each Job will create many child Jobs.......suppose at that time many Jobs r running in the system.......then it will effect the performance.....
So u can use sequence instead of parallen........no probs........
Deleting recent PSA requests is not a good practice.........bcoz suppose there is some errorneous records.......u need to reload the records again ........then if u delete the PSA request.........u hav to again extract the data from the source system............which will be time consuming.......
U can delete old PSA requests..........ex..........older than 10 days.....
Now since it is a Full upload............ur flow is correct......but u hav to Drop Index before deleting the content........ie......
START
DELETE PSA REQUEST (0HR_PA_0)
DELETE PSA REQUEST (0HR_PA_1)
LOAD TO PSA ( 0HR_PA_0_
LOAD TO PSA ( 0HR_PA_1)
DROP INDEX
DELETE DATA TARGET CONTENT ( 0PA_CO1)
DTP (0HR_PA_0)
DTP ( 0HR_PA_1)
CREATE INDEXES
Regards,
Debjani........

Error while copying a process chain.

Hi All,
I get an error message while copying the process chain in Production environment.It says "SAP System has status 'not modifiable'".Choose display object or Cancel.I hope this is because of the config. that there is no option to create anything .
Please confirm.
Regards,
Shailja.

Hi Shailja,
That means that you can not change that type of object on Quality or Productive server.
Go to Administrator Workbench, sub menu Transport Connection, there you will find a button called Object Changeability (with a truck). Click on that and change the types of the concerned objects to 'Every changeable' in your case.
Beware that you must change the status not with a double click but with a right click
also refer the following thread you can find your solution
Error message after process chain transport
Hope this helps
Regards
Karthik
<3rd Reminder for points removed>
Message was edited by:
Moderator

SAPSQL_ARRAY_INSERT_DUPREC during saving of Process Chain

Dear all,
On saving, when adding a process to an existing Process Chain - like Rollup or Change Run - in our SCM 5.0 system, we receive a short dump 'SAPSQL_ARRAY_INSERT_DUPREC' (complete short dump at the end of the msg).
A problem arose on the line 'insert rsbatchparallel from table g_t_batch_par.' of include 'LRSBATCHF01'.
The version of this include is the same as all other systems in our environment.
In the table 'rsbatchparallel' we don't find any entry that can cause a duplicate entry.
We are really stuck with this issue - any help is highly appreciated!
Best regards,
Ingrid
Complete short dump
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          08.10.2007 16:56:50
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSBATCH" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "SAVE_SETTINGS" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"SAPLRSBATCH" or "LRSBATCHF01"
"SAVE_SETTINGS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SAVE_SETTINGS" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "eccdb603"
Network address...... "19.106.69.177"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C485BD4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "eccdb603"
Database type..... "DB6"
Database name..... "A8P"
Database user ID.. "SAPA8P"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 19 2007 20:40:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 102
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory consumption
Roll.... 16192
EM...... 25139088
Heap.... 0
Page.... 212992
MM Used. 16132952
MM Free. 4812888
User and Transaction
Client.............. 510
User................ "IERNAELS"
Language key........ "E"
Transaction......... "RSPC "
Transactions ID..... " "
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSSM_PROCESS 0100"
Screen line......... 19
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in "SAVE_SETTINGS".
The main program was "RSPC_MAINTAIN ".
In the source code you have the termination point in line 1082
of the (Include) program "LRSBATCHF01".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "SAVE_SETTINGS" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLRSBATCH "; its source code begins in line
1045 of the (Include program "LRSBATCHF01 ".
Source Code Extract
Line
SourceCde
1052
loop at g_t_batch_par.
1053
if g_t_batch_par-pc_variant is initial.
1054
l_var = '//SPACE//SPACE//SPACE//SPACE//'.
1055
else.
1056
l_var = g_t_batch_par-pc_variant.
1057
endif.
1058
do.
1059
call function 'ENQUEUE_ERSBATCHSERVER'
1060
exporting
1061
mode_rsbatchserver = 'E'
1062
process_type       = g_t_batch_par-process_type
1063
pc_variant         = l_var
1064
_scope             = '3'
1065
_wait              = 'X'
1066
exceptions
1067
foreign_lock       = 1.
1068
if sy-subrc = 0.
1069
exit.
1070
endif.
1071
enddo.
1072
endloop.
1073
1074
loop at g_t_batch_par.
1075
delete from rsbatchparallel where
1076
process_type = g_t_batch_par-process_type and
1077
pc_variant   = g_t_batch_par-pc_variant.
1078
delete from rsbatchserver where
1079
process_type = g_t_batch_par-process_type and
1080
pc_variant   = g_t_batch_par-pc_variant.
1081
endloop.
>>>>>
insert rsbatchparallel from table g_t_batch_par.
1083
insert rsbatchserver   from table g_t_batch_serv.
1084
call function 'DB_COMMIT'.
1085
1086
loop at g_t_batch_par.
1087
if g_t_batch_par-pc_variant is initial.
1088
l_var = '//SPACE//SPACE//SPACE//SPACE//'.
1089
else.
1090
l_var = g_t_batch_par-pc_variant.
1091
endif.
1092
do.
1093
call function 'DEQUEUE_ERSBATCHSERVER'
1094
exporting
1095
mode_rsbatchserver = 'E'
1096
process_type       = g_t_batch_par-process_type
1097
pc_variant         = l_var
1098
_scope             = '3'
1099
_synchron          = 'X'.
1100
if sy-subrc = 0.
1101
exit.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
3
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
0001
SY-UCOMM
SAVE
SY-TITLE
Process Maintenance: Attribute Change Run
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
1
SY-DATUM
20071008
SY-UZEIT
165610
SY-XPROG
SAPFGUICNTL
SY-XFORM
%_CONTROL_EXIT_DYNPRO
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
20 FORM         SAPLRSBATCH                         LRSBATCHF01                          1082
SAVE_SETTINGS
19 FUNCTION     SAPLRSBATCH                         LRSBATCHU08                           279
RSBATCH_MAINTAIN_PAR_SETTINGS
18 FORM         SAPLRSSM_PROCESS                    LRSSM_PROCESSF04                     1917
MAINTAIN_PARALLEL_SETTINGS
17 MODULE (PAI) SAPLRSSM_PROCESS                    LRSSM_PROCESSI01                      125
USER_COMMAND_0100
16 FUNCTION     SAPLRSPC_VARIANT                    LRSPC_VARIANTU01                       93
RSPC_VARIANT_MAINTAIN
15 FUNCTION     SAPLRSSM_PROCESS                    LRSSM_PROCESSU01                       56
RSSM_PROCESS_VARIANT_DIALOG
14 METHOD       CL_RSSM_ATTRIBCHANGE==========CP    CL_RSSM_ATTRIBCHANGE==========CM003     3
CL_RSSM_ATTRIBCHANGE=>IF_RSPC_MAINTAIN~MAINTAIN
13 METHOD       CL_RSPC_FRONTEND==============CP    CL_RSPC_FRONTEND==============CM00E    16
CL_RSPC_FRONTEND=>_EDIT_NODE
12 METHOD       CL_RSPC_FRONTEND==============CP    CL_RSPC_FRONTEND==============CM00T   139
CL_RSPC_FRONTEND=>_ON_MENU_SEL
11 METHOD       CL_RSPC_FRONTEND==============CP    CL_RSPC_FRONTEND==============CM016    40
CL_RSPC_FRONTEND=>_ON_NET_DOUBLECLICK
10 METHOD       CL_GUI_RSNETGRAPHIC_NETPLAN===CP    CL_GUI_RSNETGRAPHIC_NETPLAN===CM00W    40
CL_GUI_RSNETGRAPHIC_NETPLAN=>_HANDLE_OBJECTDBLCLICK
9 METHOD       CL_GUI_RSNETGRAPHIC_NETPLAN===CP    CL_GUI_RSNETGRAPHIC_NETPLAN===CM005    37
CL_GUI_RSNETGRAPHIC_NETPLAN=>HANDLE_EVENTS
8 METHOD       CL_GUI_RSNETGRAPHIC_NETPLAN===CP    CL_GUI_RSNETGRAPHIC_NETPLAN===CM003     3
CL_GUI_RSNETGRAPHIC_NETPLAN=>DISPATCH
7 METHOD       CL_GUI_CFW====================CP    CL_GUI_CFW====================CM00K   173
CL_GUI_CFW=>DISPATCH_SYSTEM_EVENTS
6 FORM         SAPFGUICNTL_CFW                     SAPFGUICNTL_CFW                        23
CONTROL_DISPATCH
5 FORM         SAPFGUICNTL                         SAPFGUICNTL                            20
CONTROL_DISPATCH
4 FORM         SAPMSSYD                            SAPMSSYD                              288
%_CTL_INPUT
3 MODULE (PAI) SAPMSSYD                            SAPMSSYD                              236
%_CTL_INPUT1
2 FUNCTION     SAPLRSPC_FRONTEND                   LRSPC_FRONTENDU10                      76
RSPC_CHAIN_MAINTAIN
1 EVENT        RSPC_MAINTAIN                       RSPC_MAINTAIN                          11
START-OF-SELECTION
Chosen variables
Name
Val.
No.      20 Ty.          FORM
Name SAVE_SETTINGS
G_T_400_SAVE
Table[initial]
<%_TABLE_RSBATCHSERVER>
SYST-REPID
SAPLRSBATCH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
G_H_DEBUG_TYPE
Table[initial]
SY-REPID
SAPLRSBATCH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
G_T_WAIT
0.1.
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_T_BATCH_PAR-PROCESS_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
%_DUMMY$$
0000
0000
2222
0000
G_T_300_OBJECT[]
Table[initial]
G_T_BATCH_PAR-PC_VARIANT
CHANGE_RUN_MASTER_DATA
000000000000000000000000000000
000000000000000000000000000000
444444555454455455445422222222
381E75F25EFD13452F414100000000
G_T_300_OBJECT
0000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222223333
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<%_TABLE_RSBATCHPARALLEL>
G_S_ADM-PRIORITY
0
0
2
0
G_T_BATCH_PAR[]
Table IT_8429[3x212]
FUNCTION-POOL=RSBATCHDATA=G_T_BATCH_PAR[]
Table reference: 176
TABH+ 0(20) = 0700000040337FA0000000000000000000000000
TABH+ 20(20) = 000000B0000020ED00000003000000D4FFFFFFFF
TABH+ 40(16) = 04000276000007400010249401800000
store        = 0x0700000040337FA0
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 176   (0x000000B0)
label        = 8429 (0x000020ED)
fill         = 3     (0x00000003)
leng         = 212   (0x000000D4)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000024
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000410D8D60
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 6428 (0x0000191C)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
G_T_BATCH_SERV[]
Table IT_8430[2x166]
FUNCTION-POOL=RSBATCHDATA=G_T_BATCH_SERV[]
Table reference: 181
TABH+ 0(20) = 07000000410D9AB8000000000000000000000000
TABH+ 20(20) = 000000B5000020EE00000002000000A6FFFFFFFF
TABH+ 40(16) = 04000276000003E00010249401800000
store        = 0x07000000410D9AB8
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 181   (0x000000B5)
label        = 8430 (0x000020EE)
fill         = 2     (0x00000002)
leng         = 166   (0x000000A6)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000006
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0700000040360F08
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 6429 (0x0000191D)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
No.      19 Ty.          FUNCTION
Name RSBATCH_MAINTAIN_PAR_SETTINGS
I_NO_DIALOG
0
0
2
0
I_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
I_VARIANT
CHANGE_RUN_MASTER_DATA
000000000000000000000000000000
000000000000000000000000000000
444444555454455455445422222222
381E75F25EFD13452F414100000000
E_T_SERVER
Table[initial]
C_T_BATCH_PAR[]
Table IT_8427[3x210]
FUNCTION-POOL=RSSM_PROCESSFORM=MAINTAIN_PARALLEL_SETTINGSDATA=L_T_PAR
Table reference: 377
TABH+ 0(20) = 070000004050EFA8070000004033896000000000
TABH+ 20(20) = 00000179000020EB00000003000000D2FFFFFFFF
TABH+ 40(16) = 040001900000CEF00010249401800000
store        = 0x070000004050EFA8
ext1         = 0x0700000040338960
shmId        = 0     (0x00000000)
id           = 377   (0x00000179)
label        = 8427 (0x000020EB)
fill         = 3     (0x00000003)
leng         = 210   (0x000000D2)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#001089
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0700000040332390
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 6426 (0x0000191A)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0x070000004110CD08
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000040F34148
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
G_T_CLASS_100[]
Table IT_8436[3x122]
FUNCTION-POOL=RSBATCHDATA=G_T_CLASS_100[]
Table reference: 355
TABH+ 0(20) = 07000000410F9E48070000004110865000000000
TABH+ 20(20) = 00000163000020F4000000030000007AFFFFFFFF
TABH+ 40(16) = 0400027600000B900010249401800000
store        = 0x07000000410F9E48
ext1         = 0x0700000041108650
shmId        = 0     (0x00000000)
id           = 355   (0x00000163)
label        = 8436 (0x000020F4)
fill         = 3     (0x00000003)
leng         = 122   (0x0000007A)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000047
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x070000004081DE00
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 6435 (0x00001923)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0x07000000406795C8
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x07000000410FB438
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
G_T_CLASS_100
C'C'
0000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
4242222222222222222222222222222222222222222222222222222222222
3737000000000000000000000000000000000000000000000000000000000
%_FL2*CTRL_SERVER
1
0000
0001
G_T_CLASS_100-TEXT
'C'
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
242222222222222222222222222222222222222222222222222222222222
737000000000000000000000000000000000000000000000000000000000
TEXT-008
'C'
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
24222222222222222222222222222222222222222222222222
73700000000000000000000000000000000000000000000000
SAVEOK
SAVE
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
5454222222222222222222222222222222222222222222222222222222222222222222
3165000000000000000000000000000000000000000000000000000000000000000000
OKCODE
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
G_SUBRC
0
0000
0000
G_FIRST_TIME_100
0
0
2
0
G_T_WP_400
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_500_WP_NO
000
000
222
000
CX_TRUE
X
0
0
5
8
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
SPACE
0
0
2
0
SY-MSGNO
000
000
000
333
000
SY-MSGV1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
No.      18 Ty.          FORM
Name MAINTAIN_PARALLEL_SETTINGS
SY-REPID
SAPLRSSM_PROCESS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555455544455222222222222222222222222
310C233DF02F3533000000000000000000000000
SYST-REPID
SAPLRSSM_PROCESS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555455544455222222222222222222222222
310C233DF02F3533000000000000000000000000
P_VARIANT
CHANGE_RUN_MASTER_DATA
000000000000000000000000000000
000000000000000000000000000000
444444555454455455445422222222
381E75F25EFD13452F414100000000
G_T_BATCH_PAR
ATTRIBCHANCHANGE_RUN_MASTER_DATA        03C
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
455544444444444455545445545544542222222233422
144292381E381E75F25EFD13452F41410000000003300
G_T_BATCH_PAR[]
Table IT_8382[3x90]
FUNCTION-POOL=RSSM_PROCESSDATA=G_T_BATCH_PAR[]
Table reference: 344
TABH+ 0(20) = 070000004049B188000000000000000000000000
TABH+ 20(20) = 00000158000020BE000000030000005AFFFFFFFF
TABH+ 40(16) = 04000190000016A00010249401800000
store        = 0x070000004049B188
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 344   (0x00000158)
label        = 8382 (0x000020BE)
fill         = 3     (0x00000003)
leng         = 90    (0x0000005A)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000106
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0700000040F33B90
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 6392 (0x000018F8)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
L_PC_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
SPACE
0
0
2
0
P_PC_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
L_T_PAR
Table IT_8427[3x210]
L_S_PAR
ATTRIBCHANCHANGE_RUN_MASTER_DATA        03C
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
4555444444444444555454455455445422222222334222222222222222222222222222222222222222222222222222
144292381E381E75F25EFD13452F414100000000033000000000000000000000000000000000000000000000000000
G_S_CHAIN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_T_F4
Table IT_4031[5x222]
FUNCTION-POOL=RSSM_PROCESSDATA=G_T_F4
Table reference: 122
TABH+ 0(20) = 0700000040293BE0000000000000000000000000
TABH+ 20(20) = 0000007A00000FBF00000005000000DEFFFFFFFF
TABH+ 40(16) = 04000190000009B00010249401800000
store        = 0x0700000040293BE0
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 122   (0x0000007A)
label        = 4031 (0x00000FBF)
fill         = 5     (0x00000005)
leng         = 222   (0x000000DE)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000037
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x070000004035B278
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 3652 (0x00000E44)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>&

When modifying the PC, you are likely using a process variant twice, or, using a variant already used somewhere else.

Process chain status shows incorrect status

When ever i receive bad data requests from R/3, BW pulls the error requests into a separate PSA and pass-thru the good once in another PSA and then into datatarget.
However the overall status is green for the job/package and the package when executed in ProcessChain does not show an errors. But the errors are not noticed until user notices it in the qyuery.
How to capture such errors and notified, is their any automation possible? I have setup e-mail on process chain failures but these kind of errors are not captured because the overall status of request is GREEN.
Here is the status on infopackage.
Incorrect data records - error requests (total status GREEN)
Diagnosis
Data records were recognized as incorrect.
System response
The valid records were updated in the data target and can be used in reporting.
The incorrect records were not written to the data target, but were posted retractively under a new request number in the PSA.
Procedure
Check the data in the error requests, correct the errors, and post the error requests.

Hi Gopikrishna,
Please check if "Error Handling" in the Update Tab of your Infopackage has been enabled, I guess it is.
If this has been enabled , then the error recs will be isolated and only the Correct records will be posted into the Data Target. It is the responsibility of the BW Administrator to identify such errored records, correct them and Post it back to the DAta target. Because error handling is used, the Monitor will show Green, as all the error recs have been separated.
To avoid this, you have to remove Error Handling from the INfopackage, then you will see the Load failing and the Process Step in the process chain would turn RED with the corresponding error messages.
Regards,
Praveen.

Problem in creating a Process Chain

Hi,
I am using BI 7.0. I followed the following steps to create a process chain:
1. Create Start Process
2. Create Process Variant
3. And once this is created and saved, I clicked on process types
4. I dragged and dropped the Execute InfoPackage to the right side
5. And here, when I click on F4, it says, No Data Selected.
I have lot of infopackages that are created in my Datawarehousing Workbench.
But I am unable to view them...please let me know, how do I go about solving them...would definitely assign points for the solution. Thanks in advance.
Thanks & Regards.

Hi Ganesh,
just go to your administrative workbench and select your info package and copy the technical name... and now go to your process chain.. now click on Execute info package process type.. -> in that search help.. you can choose find option and give your info package technical name..(which you copied ) and press enter..
you can able to find that info package.. and clcik on taht.. and press eneter..
regards
@jay

Warning Error message while scheduling the Process Chain

Dear All,
I have created the meta Chain, which contains 7 Local Chains. I have tested this chain in BI Development and Quality. It was working fine. I have moved this Meta Chain to production. While i am trying to schedule this chain, i got the warning message.
Too many parallel processes for chosen server BICI
Message no. RSPC118
Diagnosis
On the server TVSBICI you have chosen, there are only 0 batch processes available. The process chain has been designed in such as way that 3 processes must be processed parallel.
System Response
Only 0 processes can be processed parallel. Note also that to be able to start sub-chains, AT LEAST TWO free batch processes must be available. Otherwise a lock situation may arise.
For more information, see SAP Note 621400.
Procedure
Reduce the number of parallel processes in the chain or include sub- chains. This warning applies to all relevant processes.
Procedure for System Administration
Increase the number of batch processes available. You should note however that it makes no sense to set up more batch processes than there are CPUs on server BICI.
Pls help on this issue.
Thanks,
Siva.
Edited by: Siva Kumar on Jun 15, 2009 9:16 AM

I have Ignored this warning and now process Chain is working fine.
Thanks,
Siva.

Error while executing the Process chain

Hi Friends,
The process chain that I scheduled is getting failed at the Infopackage loading stage.
On checking the diplay message, I found the following log:
Cannot stage requested data for datasource
Error in source system
I activated the datasource in source system, then replicated the same and tried to load data.
But the issue remains the same.
I checked in RSA7. The status corresponding to this datasource is in yellow status.
Can I delete this entry and try again?
Please suggest.
Thanks in advance.
Surjit P

Hi,
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Deadlock
http://help.sap.com/saphelp_nw04s/helpdata/en/2e/44934257a5c86ae10000000a155106/frameset.htm
Dead Locks
2. Error in unit conversion
Units of measure
3.Error 1 in update
When Src file is already open or not accessible.
4.Processing no data
theres no data selected after extraction
5.Caller 70 missing
" This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
1) Whenever we are loading the Master Data for the first time, it creates SIDs. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
2) If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
3)Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
4) If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
5) It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
6) It is a system error which can be seen under
the Status tab in the Job Over View.
solution:
" If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SIDs and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
6.Idoc not processed completely.
Here the request remains yellow (in process) and with the same details (as seen in the details tab of the monitor) for an abnormally long time. Many-a-times, the port for communication is not open and re-starting the load helps. For long running jobs, it may not be advisable to restart the extraction
Contact the BASIS administrator to push the IDOC.
look into these links:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
For common data load errors check this link:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Majority of the issues will be based on these things only..
Hope the following links will give u a clear idea about process chains and clear ur doubts.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-03/using%20process%20chains%20in%20sap%20business%20information%20warehouse
Business Intelligence Old Forum (Read Only Archive)
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Siggi's weblogs for data load error and how to restart process chain
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Hope this helps.
pls award me some points
thanks.
Thanks

Error in process chain (psa data)

We have got an error in our PROCESS chain for master data.
Info object Name : 0customer
In that it was showing there was error in our request. When I wanted to correct data in the request there it was showing no error records. All the records are good and also it is showing as error in request. I have deleted the request from infoobject and also from the PSA. And the last updated good request is also showing error as No data packets available for the request .
0Customer is delta update ; Process chain is daily based.
My doubt is whether the records in the deleted requests will be reloaded again from sap R/3 into PSA, as requests during Process chain or not.
While monitoring the request details in Monitor u2013 Administrator Work bench, it shows the following:
1.     Requests (messages) Everything Ok
2.     Extraction (messages) Missing messages
3.     Transfer (IDocs and TRFC) Missing messages
4.     Processing (data Packet) No data
5.     Process chains : Everything Ok.
Even after deleting the requests my process chain is not getting updated.
Kindly help me in solving the above problem
Regards
Padma

Hi,
Once deleted the request, try to manually trigger the load and see whether it completes. if it completes and pulls reocrd then you can push the chain process ahead with the program RSPC_PROCESS_FINISH
Regds,
Shashank

Interview questions in process chain

hi
cany any one send me possible interview questions in process chain and errors with answer.
thanks in advance
pradeep

Hi Pradeep
1.Procedure for repeat delta?
You need to make the request status to Red in monitor screen and then delete it from ODS/Cube. Then when you open infopackage again, system will prompt you for repeat delta.
also.....
Goto RSA7->F2->Update Mode--->Delta Repetation
Delta repeation is done based on type of upload you are carrying on.
1. if you are loading masterdata then most of the time you will change the QM status to red and then repeat the delta for the repeat of delta. the delta is allowed only if you make the changes.
and some times you need to do the RnD if the repeat of delta is not allowed even after the qm status id made to red. here you have to change the QM status to red.
If this is not the case, the source system and therefore also the extractor, have not yet received any information regarding the last delta and you must set the request to GREEN in the monitor using a QM action.
The system then requests a delta again since the last delta request has not yet occurred for the extractor.
Afterwards, you must reset the old request that you previously set to GREEN to RED since it was incorrect and it would otherwise be requested as a data target by an ODS.
Caution: If the termianted request was a REPEAT request itself, always set this to RED so that the system tries to carry out a repeat again.
To determine whether a delta or a repeat are to be requested, the system ONLY uses the status of the monitor.
It is irrelevant whether the request is updated in a data target somewhere.
When activating requests in an ODS, the system checks delta repeat requests for completeness and the correct sequence.
Each green delta/repeat request in the monitor that came from the same DataSource/source system combination must be updated in the ODS before activation, which means that in this case, you must set them back to RED in the monitor using a QM action when using the solution described above.
If the source of the data is a DataMart, it is not just the DELTARNR field that is relevant (in the roosprmsc table in the system in which the source DataMart is, which is usually your BW system since it is a Myself extraction in this case), rather the status of the request tabstrip control is relevant as well.
Therefore, after the last delta request has terminated, go to the administration of your data source and check whether the DataMart indicator is set for the request that you wanted to update last.
If this is NOT the case, you must NOT request a repeat since the system would also retransfer the data of the last delta but one.
This means, you must NOT start a delta InfoPackage which then would request a repeat because the monitor is still RED. For information about how to correct this problem, refer to the following section.
For more information about this, see also Note 873401.
Proceed as follows:
Delete the rest of this request from ALL updated data targets, set the terminated request to GREEN IN THE MONITOR and request a new DELTA.
Only if the DataMart indicator is set does the system carry out a repeat correctly and transfers only this data again.
This means, that only in this case can you leave the monitor status as it is and restart the delta InfoPackage. Then this creates a repeat request
In addition, you can generally also reset the DATAMART indicator and then work using a delta request after you have set the incorrect request to GREEN in the monitor.
Simply start the delta InfoPackage after you have reset the DATAMART indicator AND after you have set the last request that was terminated to GREEN in the monitor.
After the delta request has been carried out successfully, remember to reset the old incorrect request to RED since otherwise the problems mentioned above will occur when you activate the data in a target ODS.
What is process chain and how you used it?
A) Process chains are tool available in BW for Automation of upload of master data and transaction data while taking care of dependency between each processes.
B) In one of our scenario we wanted to upload wholesale price infoobject which will have wholesale price for all the material. Then we wanted to load transaction data. While loading transaction data to populate wholesale price, there was a look up in the update rule on this InfoObject masterdata table. This dependency of first uploading masterdata and then uploading transaction data was done through the process chain.
What is process chain and how you used it?
A) We have used process chains to automate the delta loading process. Once you are finished with your design and testing you can automate the processes listed in RSPC. I have a real time example in the attachment.
for more detail
Collecting Process Chain Statistics
/thread/235805 [original link is broken]
Advice regarding process chains
creation of process chains
Message was edited by:
Kalpana M

System command in Process chain

Hello,
I have a system command in the process chain which points to a command file that is supposed to run. My problem is that when I transport the PC, the path on the system command remains same.
I want it to change the path from /md.... in dev to /mq... in QA and /ma... in PROD.
Is there anyway to automate this process? Right now i have to keep track of it and change the system command in each system. I have missed a couple and it creates some problems.
Thanks
Sam

Hello Sam,
One way to solve this is to work this with your UNIX administrator. You can do the following:
1) Create a symbolic link in your dev, qa, and prod which points to the correct directory.
For example, in dev, you can do the following:
link -s <whatever new name here, e.g. target> /md
In QA, you can do the following:
link -s <whatever new name here, e.g. target> /mq
and so on..
2) Instead of using the /md, /mq directories, you can use the symbolic directory instead in your system commands.
e.g. ls -l /target instead of ls -l /md
This might not help you a lot now but it will make things easier in the future because you will know that the symbolic link points to the correct directory of whatever box.
Hope this helps.

Process Chain (Urgent)

HI Gurus,
HI have a process chain called production daily process in these process chain we have 2 local chains.this process chain is not triggering from 2 days .and im selecting first local chain to correct manually its showing some dump problem and if i open info package also its is showing the same problem plz give solution for this.
IT IS SHOWING LIKE DES
ERROR:
Runtime Errors         MESSAGE_TYPE_X
Date and Time          05.09.2007 17:01:00
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
     administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
Short text of error message:
Scheduler
Long text of error message:
Technical information about the message:
   Message class....... "RSM1"
   Number.............. 000
   Variable 1.......... " "
   Variable 2.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
ow to correct the error
   Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the following
   keywords:
"MESSAGE_TYPE_X" " "
   "SAPLRSSM_LOAD" or "LRSSM_LOADU07"
   "RSSM_RSREQDONE_READ"
If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
   (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
      Restrict the time interval to 10 minutes before and five minutes
   after the short dump. Then choose "System->List->Save->Local File
   (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
   Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
ystem environment
   SAP-Release 700
Application server... "biprdn"
   Network address...... "10.20.0.8"
   Operating system..... "AIX"
   Release.............. "5.3"
   Hardware type........ "00C6DDDD4C00"
   Character length.... 8 Bits
   Pointer length....... 64 Bits
     Work process number.. 1
    Shortdump setting.... "full"
Database server... "biprdn"
    Database type..... "ORACLE"
    Database name..... "BWP"
    Database user ID.. "SAPR3"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
    created (date)... "Jan 28 2007 20:40:17"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 95
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory consumption
    Roll.... 16128
EM...... 12569760
    Heap.... 0
Page.... 65536
MM Used. 4316536
    MM Free. 4060576
User and Transaction
Client.............. 200
    User................ "SISLBW"
    Language key........ "E"
    Transaction......... "RSPC "
    Transactions ID..... " "
Program............. "SAPLRSSM_LOAD"
    Screen.............. "SAPLRSPC_FRONTEND 0300"
    Screen line......... 0
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSSM_LOAD" - in
     "RSSM_RSREQDONE_READ".
    The main program was "RSPC_MAINTAIN ".
In the source code you have the termination point in line 41
    of the (Include) program "LRSSM_LOADU07".

Hi Prashanth,
Please look at SAP Note: 962365
Hope it helps you.
Cheers!
Amit

All Process Types not visible in RSPC ( process chain)

Hi,
When I go to create a new process chain in RSPC & look for process types to choose from I am not able to see all the process types.
when I go to table RSPROCESSTYPES or setting-->maintain process types , it shows all the enteries.
Am I suppose to do some steps before I start seeing all the process types in the left panel of my RSPC--process types.
looking forward to your help.
regards
Vikash

Hi Agarwal
check the table RSPCCATEGORY ..In this table check whether there is an entry for the following..
General services
Load Process and Post-Processing
Data Target Administration
Reporting Agent
Other BW Processes
if not there maintain them..
bye
Shu Moh..

Process chains administration

Similar Messages

Maybe you are looking for