Termination of Process chain

Hi,
I have a BIG process chain with a lot of master data loadings from the source system up to BI. All activities in the chain are linked to ALWAYS move on either the step was successful or failed.
When I started the chain I immediately faced problems with the connections towards the source system. Therefore I wanted to terminate the entire process chain. I do not know how to do that.
If I teminate the single activity (change the traffic light to red) it will move on to the next activity. When I check SM50 there are no background processes and in SM37 everything is marked "Finished".
Regards,
Sofie

Hi Sofie,
When the process chain is half run , the steps that have not run have jobs in the backgrounfd in the released state , witing for the event above them to schedule them.
You can go to SM37 and delete all such jobs. The chain will have no jobs then to complete the chain completely and it will terminate with an error that an even was triggered but no job could process it.
If you have chain set as periodic, new set of jobs would be release as soon as you delete the old ones. If this doesnt happen you would need to reactivate the chain.
Also please ensure you are deleting only the jobs relevant to the chain and not any other unintended jobs.
To see the jobs of the chain, you can right click any process variant in the active chain and click on command display all scheduled jobs.
You said in SM37 everything is marked as finished, check if you had swithced on scheduled jobs in your selection , they are switched off by default.
Also why are you desisting from changing the events to trigger only when successful?
Hope this helps.
Regards,
Sunmit.

Similar Messages

ABAP Program Termination in Process Chain

Hello
in my process chains i have one abap program and it is getting dump while loading.
where can i check whether this program got terminated in this particular chain.
as i have many chains i am not able to check in each and every chain.
kindly let me know where to check the program termination in process chains.
do i have any chance to set an automatic process for checking the termination of the program.
regards,
Ala.

Hi Ala,
If u know the process chain name, u can directly see log view of that process chain and right click on that failed ABAP program click "display mesaged". Now note down the error message and see that in st22.
If u dont know the process chain name..
In SM37 go to the job log for that pirticular job which is failed, it gives u tha program name and varient name.
now goto SE38 and give that program name and variant then click on display.It gives u process chain name.
Hope it helps.

Process chain Types.

Hi Gurus,
Can some one explainhow many process chain types are there in sap bw3.5.I searched in forums.But i didnt get answer.
Regards
Arun

Hi ,
Process chain types are two.
1) direct chain : meanns single chain
2) meta chain: Process chains can be scheduled as processes in additional process chains, which are known as meta chains. If the process chain you want to execute is in another system, use the process type Process Chain Remote, called remote process chain in the following. A remote process chain is a local process in the calling system that calls a process chain in this system, using a destination in another system, that is to be executed there. The remote process chain communicates with the other system and synchronously starts the executed process chain. After terminating the process chain in another system, this is reported back to the meta chain in the calling system.
Thanks & Regards,
Ramnaresh.

Process Chain - Status Green but log says "Termination of chain "

Hello Friends,
One of the Steps in a Sub Chain of the Meta Chain shows the log as follows:
30.10.2009 05:20:28 Job started
30.10.2009 05:20:28 Step 001 started (program RSPROCESS, variant &0000000049485, user ID SCMREMOTE)
30.10.2009 05:20:35 Spool request (number 0000017553) created without immediate output
30.10.2009 05:20:35 Entire chain now has status 'G'
30.10.2009 05:20:35 Termination of chain has been reported to meta chain D6SBR9M64EV91ZX911UJI7K36
30.10.2009 05:20:35 Job finished
and the Step has changed to Green. So we normally assume that it has executed succesfully. Recently, there came this data issue. This step loads Open Sales Order data from a Cube to APO DP Planning area. Now few Open Sales Order Qty for a material are missing in planning area.
Does this step in the Process chain has executed Succefully or as the log says is it terminated? Though the step changes to green , were all the materials not loaded into planning area?
Please advice and suggest.
Thanks,
Chandra.

Hii
This log shows that chain has been successfully terminated. This is a common log
The missing of Open Sales Order Qty for a material may be due to other reason .
Try to get into more details for which Orders this has happened and check in the source system.
Thanks
Sonal...

Process Chain Termination issue.

Hi,
     I ran a process chain, its been terminated in the middle.
here is the message from log.
Process Execute InfoPackage , variant WBS Hierarchy has status Ended with
errors (instance REQU_AI8QGHV5KCC7KC1VSNGPRY9VF )
Process chain termination has been confirmed in meta chain
CE0BOS15OV4H1VDIEVZSFDEH8 , destination 'NONE '.
Looking forward to your solution.
Cheers
Senthil

what is the messege it gives in the display messege screen. if the load is successful how it will get terminated.
chk the details tab of RSMO.
is the load is for ods? then in the details tab chk for subsequent processing is failed? chk the error messege, hope this may be due to invalid records. correct it in PSa and push to ods.
if any thing else pl revert us
Ramesh

Process Chain error after Enpk1(7.01) upgrade - "Termination discovered"

Hello We have upgraded our BW from 7.0 to Enhpk1 (7.01) with latest stack.
After our upgrade I'm seeing our Process chain when a step errors out and there is a next step to continue with always link inspite of the error in prev step, but the Process chain does not continue and hangs and when checking the log it gives a prompt of "Termination discovered"
Gives a prompt something like this
"The analysis of chain ZP_MD_OTHER_CUST showed that process
ODSACTIVAT ZP_MD_OTHER_CUST_ACTV was terminated However the
occur) or a metachain Run 4KFMOYW9CGL10CGCQV2ZL691R could
not be ended due to the termination. It may be the case that
a metachain was not informed about the error Continue run
for chain ZP_MD_OTHER_CUST and any corresponding metachain?"
with yes or No prompt
So the chain hangs and does continue only after we enter Yes to the prompt.
We are in Q testing the upgrade this can be big issue when we dont our chain to hang for something that we want to continue always.
Opened a msg with SAP, they got back say its because of note 1398868 in the support pack, asked us to implement the manual update on RSADMIN and apply another note 1473491 - Chain not continued with termination and "ALWAYS" link.
But this has not fixed the issue, Have notified back to them and waiting.
If any of you have encountered this and resolved . pl let me know.
Thanks
Mayil

Since you just upgraded the source SAP system, it's likely that the delta queue doesn't exist for the data and has to be re-initialized. I'd suggest doing an Init w/o Data Transfer and do a Full Repair extraction to catch up on any missed data. From then on, you shouldn't have an issue with your Delta mode extraction from the source system.

Error ( termination error : 8) when scheduling Process chain.

Hi Friends,
We are just configuring the BW system 3.5 ( Installing etc etc), I created a Process chain and trying to schedule it, I get the following Error.
" Job terminated with error code : 8" , when I check the details of the message I see this " Cannot schedule the job with Id : BW REMOTE". Is it something that the basis/ securtity has to set up for the BW guys , to schedule jobs.
Thanks,

Hi Smily,
The possible reason for that error is the User type of the background user. Please check out OSS note 511475 which talks about this problem and possible solution. I have used this earlier.
You can see this for info on how to make the change:
/message/685940#685940 [original link is broken]
Hope this helps...

Process chain termination - Attributes are not yet maintained

Hi Experts ,
I am running a process chain in the production system , which is failed , however the below objects in the chain is completing successfully.
Please see the below msg descriptions
Attributes are not yet maintained
Entire chain now has status 'R'
Process Start Process, variant Technical InfoObjects Attribute Load has status Undefined
Process Execute InfoPackage, variant InfoPackage has status Undefined ...
Process Execute InfoPackage, variant BW Systems has status Undefined
Process Execute InfoPackage, variant InfoSource has status Undefined
Process Execute InfoPackage, variant InfoCube has status Undefined
Process Execute InfoPackage, variant Application Component has status Undefined
and many things which are undefined ..
Have nay one come across this issue , how to resolve this ?
Thanks

Hi,
Is there any changes done for the respective IP's/objects used in the chain recently. It might be the cause and before running jst test the chain using CHECK option and accordingly redesign, activate and schedule the process chain,
rgds,

Repairing/Repeating Terminated Processes - Process Chains

Hi,
Can any one please explain me with a simple example about repeat and repair in case of process chain.
Ive referred http://help.sap.com/saphelp_nw04s/helpdata/en/f3/0d4a975f450443be900e89a47ad48e/content.htm but yet I am not very clear about the two.
Which option do we use under what circumstances?
Thank you,
sam

Hi Sam,
Normally with Repeat option next processes automatically trigger. But after manual update u should do them manually.
Check this Function module.
Look into this FM - RSPC_PROCESS_FINISH and execute with G(complete) this will start the next process automatically without doing anything manually.
or
Go to the plan view of that chain, in trasaction field enter '=copy', it asks for the name and description, then u remove the processes which r already ran, connect a start process to which r yet to run ( means to the first process in that). select the immediate option in maintain variant for start process then trigger it.
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.
Regrads,
Ravikanth

Error while activating Process Chains

Hi all,
while activating the Process Chains, i am getting the following error "Job BI_PROCESS_PSAPROCESS could not be scheduled. Termination with returncode 8"
when i double click on the error msg, i got the following help msg: "
Message no. RSPC065
Diagnosis
Program RSPROCESS is to be scheduled as job BI_PROCESS_PSAPROCESS under user ALEREMOTE.
Can any one please show some way to solve this problem? please do this favor, i have been suffering with error for a long time.
Points will be given
Thanks
Ganesh

Hi,
Just analyze the error message that you get while activating the PC, don't give any server name.If you are trying to run process chain using Flat file, it won't work,
and you should have source system R/3 or you have own datasources in BW system itself at that toime you can use PC to extract data. If your source system is Flat ile, it won't work. other wise you should place your flat file in application server, using AL11 tcode.
OSS : 511475
Symptom
You cannot schedule or perform any batch jobs with the BW or source system background user.
The error RSPC 065 occurs in the process chains:"Job could not be scheduled, termination with return code 8"
Other terms
RSPC065
Reason and Prerequisites
The user type is
"CPIC" up to 4.6B
"Communication" as of 4.6C
This user type may not execute or start any batch jobs, irrespective of the user authorizations.
Solution
Set the type of background user to
"Background" up to 4.6B
"System" as of 4.6C
This user type corresponds to the "Communication" type and may also perform background functions.
Through the Customizing, the BW user is automatically created by mistake as a communication user.Depending on your BW system release, you can solve this problem as follows:
BW 2.0B
 Import Support Package 24 for 2.0B (BW2.0B patch24 or SAPKW20B24) into your BW system. The Support Package is available once note 456551 with the short text "SAPBWNews BW 2.0B Support Package 24", which describes this Support Package in more detail, has been released for customers.
BW 2.1C
 Import Support Package 16 for 2.1C (BW2.1C patch16 or SAPKW21C16) into your BW system. The Support Package is available once note 456566 with the short text "SAPBWNews BW 2.1C Support Package 16" has been released for customers.
BW 3.0A
 Import Support Package 8 for 3.0A (BW3.0A patch08 or SAPKW30A08) into your BW system. The Support Package is available once note 452632 with the short text "SAPBWNews BW 3.0A Support Package 08" has been released for customers.

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.

Error while activating data in process chain

Hi All,
Am getting following error msgs in process chain while activating the data store object variant
1.Cannot activate request 0000015195(REQU_78CEI406HFCMG85RWNSKW6HW4) of DataStore object RC2SCD10
2.Activation of M records from DataStore object RC2SCD10 terminated.
Any help how to resolve this error.
Regards
Sirisha.
Edited by: sirisha gupta on Dec 29, 2008 10:16 AM

hello,
firstly see if the DSO and the transfomration, DTP are all active.
or
This can be due to the incorrect data record in ods
find that record in PSA correct that one and then try to run the load fro PSA to Data target.
or
Uncheck "SID's Generation upon activation" in DSO's settings.
or
you can also try by changing the "Parallel Processing" to "Serial Processing".
In the maintenance screen of DSO, select "Requests" tab:
Click on the "Activate" button at the bottom
Click on the "Activate in Parallel" button
Change the "Number of Processes" to "1" for Serial Processing
Save the setting
You should see the "Activate in Parallel" button with a cross icon now.
Check SAP Notes: 1118205 & 947481
refer:
DataStore object Activation
reg,
dhanya

Process chain AND process

Hi,
I have a process chain that has two parallel processes of loading DSO and Infocube data. There are two infopackages on one side and two on the other side. The two processes are connected with and AND process at the end and after that there is a datastore activation process.
When I executed the process chain, the infopackages on both sides started loading data. The two infopackages on the left side finished first while the second infopackage on the right side had not finished yet when the AND process errored. I get the following message:
This AND process is not waiting for event RSPROCESS , parameter
47VKUORHMXQKR2AN73AVAR0C9
After the AND process I have a Datastore generation process and I want it to continue only when all infopackages have been loaded.
Why does the process stop at AND even though all infopackages have not finished yet?
thanks
Michalis

There was no error message in ST22 or SM37. There was very little info to go on. I just deleted the requests and run the process chain again and there's no error. However the process chain does fail at a later step.
Update Datastore Object Data (Further update)
I don't know what that further update is for. It was automatically selected in my Process chain when I selected the infopackage for the DSO.
There's a MESSAGE_TYPE_X error.
Information on where terminated
 Termination occurred in the ABAP program "SAPLRSM2" - in "RSSM_MON_WRITE_3".
 The main program was "RSBATCH1 ".
 In the source code you have the termination point in line 2659
 of the (Include) program "LRSM2U16".
 The program "SAPLRSM2" was started as a background job.
 Job Name....... "BI_PROCESS_ODSPROCESS"
 Job Initiator.. "CSPAPADM"
 Job Number..... 14103000
Source Code Extract
Line SourceCde
2629 CALL FUNCTION 'RSSM_GET_TIME'
2630 EXPORTING
2631 i_datum_utc = rsreqdone-tdatum
2632 i_uzeit_utc = rsreqdone-tuzeit
2633 IMPORTING
2634 e_timestamps = l_s_status-t_timestamp.
2635 IF rsreqdone-tstatus(3) = icon_green_light(3) OR
2636 rsreqdone-tstatus(3) = icon_red_light(3).
2637 CALL FUNCTION 'RSSM_GET_TIME'
2638 IMPORTING
2639 e_timestamps = l_s_status-ts_proc_ended.
2640 l_not_yellow = 'X'.
2641 ENDIF.
2642 IF l_not_yellow = 'X'.
2643 CALL FUNCTION 'RSSTATMAN_SET_STATUS'
2644 EXPORTING
2645 i_s_status = l_s_status
2646 i_with_commit = 'X'.
2647 IF l_s_status-t_status(3) = icon_green_light(3) AND
2648 l_s_status-dta_type = 'ODSO' AND
2649 t_data-aufrufer <= '70'.
2650 CALL FUNCTION 'RSS2_CALLBACK_ODSADM_ODS_SUCC'
2651 EXPORTING
2652 i_ods = l_s_status-dta(30)
2653 i_rnr = l_s_status-rnr.
2654 ENDIF.
2655 ENDIF.
2656 ENDLOOP.
2657 IF sy-subrc <> 0.
2658 IF t_data-aufrufer <> '09'.
2660 ENDIF.
2661 ELSE.
2662 IF l_not_yellow = 'X'.
2663 CALL FUNCTION 'RSB1_OSNAME_TO_ICNAME'
2664 EXPORTING
2665 i_osource = g_s_minfo-oltpsource
2666 * I_OSTYPE = RSAOT_C_OSTYPE-TRAN
2667 IMPORTING
2668 e_icname = l_icname
2669 EXCEPTIONS
2670 name_error = 1
2671 OTHERS = 2.
2672 IF sy-subrc = 0.
2673 CALL FUNCTION 'RSAWB_MAINTAIN_DTA'
2674 EXPORTING
2675 i_method = rsatr_c_dta_get
2676 * I_TYPE =
2677 i_objvers = rs_c_objvers-active
2678 i_dta = l_icname
Any idea what that means? Also do I need that further update step in my process chain?

Process chain is long running

We have a process chain that is long running even though there is not much data.
It is long running in Load PSA step. It is getting data from other R/3 sap system. A job is also long running in the R/3 system.
We can see data coming to BW system but not getting updated to PSA and even the job in R\3 is also not getting terminated.
There are many other process chains too running in the system and they are running fine. So i feel that this may not be due to system performance. This is happening for last one and half week.
If any one has faced similar problems or if you have any solution or checks that i can do, please reply.
Regards,

Hi sarafraz,
If there are more than one run are active and running ,then delete the other extraction job and have only one at a time in source system. Because those may be causing lock issue .
Also see system log in SM21 ,if you have any system termination message for this extractor .
Check ST22,if you have any short dump for this extractor
Also you can try to load for particular selection in Infopackage (for a month,company code or some other selection that restrict the data) and check whether it is completed or not.
Also check to RSA3 and extract there.
See SM12 -for lock entires
SM51,SM66 in source system - What is running for this extractor,which program is being read,which table etc...
so you can know the step where it got stuck or taking long time.
Thanks,
Naween

Process chain taking long time to complete

Hi,
I am having following issues in the process chain daily loads
1) The PSA deletion is taking very long time on fridays only (nearly 3 hrs). Other days it gets deleted in 1 hr max.
2) Just to load 381 records via dtp from DSO to cube takes nearly 2 hrs(Delta load). No major routines are written in the transformation.
How to analyse a process in process chain which does not fail, but takes very long time to complete. Is there any tool or transaction in BW which can help us to analyse why the process chain takes so long time to complete in different days. One day it completes in 8 hrs, another day it takes 12 hrs.
None of the transactions, SM37, SM50, SLG1, LOGS etc are giving me any help to analyse this issue.
If it fails we have error logs to check and analyse, but without failing how we can analyse and fix the delay and reduce the time of loading data. Please guide me.
Thanks in advance.
Vishwanath

Hi.......
1) This might be due to the poor performance of the system ..there wont be enoughwork processes avilabe in teh system .- What needs to be done if it does not have enough work processes available. Though I can find that lots of dialog processes were free during these jobs as well some Background processes were also free.?
Look to increase Work Process.......................u can do two things..............U can cancel some Job...........which r not progressing...........or which r not very important for the time being..........
Or if possible........u can increase number of servers..........
Look When a Job will start...............first it will run in background.............u can start in in Dialog also..........but for Dialogue after some time ..load will go to time out.................now many Child jobs will be created for a single background jobs..............they may run in Dialogue..........u can monitor them through SM66............
2) Check ST04 for lock waits and dead locks ..if the same lock persist for long then check with basis team.
What needs to be conveyed to the basis team when these locks happen?
generally these will be temporary Locks.............after some time locks will be realeased..............if they persist for a long time...........then u can contact Basis people..........Or if u can understand that which job is creating the lock.............like if u double click on the job >> click on Job details...............from there u will find the PID................copy that.............and check in ST04..........whether they matches or not..............now suppose it match.............and u know that job is not very important............then u can cancel the job.............
Check also the table space availba in St04 . the usuage should nt be more than 90%
What needs to be conveyed to the basis team if the usage is more than 90%.?
U can ask them to increase the Table space........
Check the sm37 >> delay column it should nt be high
What needs to be done if delay column is high. Actually it is high for these jobs (PSA deletion and load from DSO to Cube visa DTP (Delta load)?
If Delay is more.............it means ...........that there is no free work process...jobs r going to Release state............solution I had already given u.......
Check the PID refeclting in lock waits in sm66 wether they are progressing or nt ..
If they are not progressing what action needs to be taken?
Actually...........suppose one Dialogue job is running............it may change..........ie that Dialogue job will go to Stop status.........some other job will start............anyways if it does'nt progress............u can cacel the JOb.........
Check OS07 for DB if the idle time is less then 20% then its a problem ..
If the Idle time is less than 20% what action needs to be taken?
U can contact the Basis people.......
Check sm21 and RFC connection with other source systems in sm59 ..
What needs to be checked in SM21 and SM59 specifically? What parameter i need to check?
In SM21.............if red status is there............check the Log beside that..............may be it will be some Terminal disconnected.......
In SM59...........clck on test connection..........
if the problem is occuring due to only one source system then check the performance of that system ..
How to check the performance of these systems? Any tools available in R/3 system to check its performance?
No.....in this way u can check performance for all the source system...........go to SM59............double click on the desired source system>> click on test connection......
If All these are persisting then its a performance problem and check with basis team ..
Is there any special settings which needs to be maintained to achieve better performance of Process chain loads?
U can Improve the performance of process chain by Parallel Processing..........ie split the loads by giving selections...........and execute thenm in parallel..........
Regards,
Debjani........

Termination of Process chain

Similar Messages

Maybe you are looking for