Process chain errror handling

Hi Experts,
One of my process chain failed and it includes locan process chain which is failed and message is :
"Start Infopackage (infopackage number)"
what should I do in this case? simply repair?

Hi Pia,
Right click on local PC(process chain) ,,,,,,,,,,Display messages,,,,,,,,,, go to the failed process,,,,,,, right clik on he fail process,,,,,,,,, click on display messages,,,,,,, you will directly go to manage screen,,,,,,,, Set the QM status to red in status tab,,,,,,,,delete the request ,,,,,,,,,, reload the data data i.e schedule start,,,,,You will get message request again click yes,,,,,, your problem get resolved,,,,,,,,if you want to set the process chain status to green,,,,, you need to use FM ,,,,,,,if you need any further clarification,,,,,, lot of post are there in SDN.
Regards,

Similar Messages

Step by Step documents for Process Chain Error Handling with Screen Shots

Hi
Is anybody having Step By Step Documents for Process Chain Error Handling with Screen Shots ?. Please forward it to me to my e-mail [email protected] . I will reward points to u immediately.
bye
Aamira Khan

Hi,
You can find lots of topic related to process chain issues in SDN.Please make a search in SDN.
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_library&query=process+chain&adv=true&sdn_author_name=&sdn_updated_on_comparator=ge&sdn_updated_on=&sortby=cm_rnd_rankvalue
Regards.

Error handling -- automatic process chain

Hello Experts,
I need your suggestions.
1) I want to set up the error handling for the ILTC(Intiail load from the trusted client). Do I need to create a process chain to handle errors manually? or will the Process type 'Error handling for ILTC' collects and creates the process chain for the each object type?
2) Say some how the process chain for the error objects has started. How can the error objects be handled automatically ?
Thanks,

Dear Sweatha,
1 - You have to create a process chain with a start step, error handling step and a step to edit data and then a post step
2 - If error occurs during ILTC, the error handling chain will be started automatically. Data will be stored in the error handling step.
To process the error really you have to go to the error handling monitor and press the continue button. Data will be sent to the edit step. Here you can correct manually the errors.
Please find additional information in the SAP Help Portal: http://help.sap.com/saphelp_mdm300/helpdata/EN/88/454ba493cb43f1b74336772a7f3508/frameset.htm
Kind regards,
Markus

Collection Processes in Process Chains

Hi ALL,
I want to know what is the real importance of using AND, OR and EXOR Processes in Process Chains.I have gone through all the material available on SDN.But i could not clearly understand these Processes as of what's the real purpose it serves when used in Process chains.
We have Process Chains in our system which contains Planned data as well as Actual data which are parallelly loaded using our Process Chains.Where in we have Different infopackages.With every infopackage,If it is successful ,it is connected to AND Process And in case,if it is a failure,It is connected to an OR Process.
So ,if it is Successful ,then it goes to And Process or else it connected to OR Process which triggers an ERROR event for that particular process chain.
So,Please Do Provide an good answer as I have to implement certain changes to my process chains.I have added 3 more infopackages to my process chain and now ,I want to know whether I should connect them to OR process,if a Failure occurs and what will be the consequences ,if I connect/Do not these new packages to OR process when a failure occurs.
I hope you understand this Problem and <b>reply as it is very urgent.</b>
Points will be assigned.
Regards,
samir

Hi
Definition
A collection process collects several chain strings to form one string in the process chain maintenance.
Use
Process chain management handles collection processes in a particular way. The system makes the variant names consistent and guarantees that all processes of the same name that have been scheduled more than once, trigger the same event. This enables the several chain strings to be collected to form one and also makes multiple-scheduling of the actual application processes unnecessary.
The following collection processes are available in the process chain maintenance:
And Process (Last)
This process does not start before all events of the predecessor processes, that is including the last event, that it has waited for, have been successfully triggered.
Use this collection process when you want to combine processes and when further processing is dependent on all these predecessors.
Or Process (Every)
The application process starts every time a predecessor process event has been successfully triggered.
Use this collection process when you want to avoid multi-scheduling the actual application process.
XOR Process (First)
The application process starts when the first event in one of the predecessor processes has been successfully triggered .
Use this collection process when you want to process processes in parallel and schedule further independent processes after these ones.
Owing to the time components, the collection processes do not display logical gates in the normal sense, because the system cannot distinguish between whether a 0 entry (no event received), means that the event was never received or whether it has not been received yet. The reason for this is that the checks do not run continuously but only take place when the event is received.

Error handling in process chain-doubts

Hi ,
I have some doubts in error handling of process chains.
1) I have aprocess load infopackeage and subsequent process is update fromPSA.
process load infopackage got failed , so i loaded the IP manually and repeated the next i.e process update from PSA .
How to correct the process chain from now?
2) I have aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed , so i loaded the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
Plz help me as this is urgent and daily i have to deal with this issues. If any documents on error handling is greatly appreciated.
My mail id is [email protected]
Regards,
Pavan

Hi Pavan,
Hope the following links will give u a clear idea about process chains and clear ur doubts.
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
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 ...
U can even 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
****Assign Points if Helpful****
Regards,
Ravikanth.

How to handle delta failed process chain steps

Hi All,
I have a query regarding process chains were in processstep has delta load and there is dependency between the predeseccor and successor process steps,then
if the delta load fails due to any one of the following reasons
1) due to remote_icp locked the prtclr Infoobject the process step is executing .
2) due to any psa records errors and so on
Then how to handle delta and see that correct delta records were updated .
Because again for the nextday loads if the previous delta is incorrect it will give pop-up message that it is not possible.
If any suugestions pl guide me.
thanks
Venkat
[email protected]

1)Remove the lock by force from sm12 or wait till the lock is gone.Then see if the delta data has come till the PSA.Mark failed delta load RED and back it out from target.Then read everything in manually from PSA to target.
In process chains u can go the monitor entry for the failed load by..highlight chain..click log icon..give selection..for proper selection..see the failed node..right click..display messages..click on process monitor.
Sometimes even if infopackage is run successful manually,next steps in the chain do not kick off.
Use Siggi's excellent blog on this..(it works really well)
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
2)Make request RED and back it out from target.
Correct records in the PSA and read everything in manually from PSA to data target.
Then use Siggi's blog.
If data hasnt come to PSA do a delta repeat.
Always check yesterday's chain run about 1-2 hrs before today's chain kicks off.
cheers,
Vishvesh
Message was edited by: Vishvesh

How to Handle Long running alerts in process chain...Urgent!!!

Hi All,
I am trying to find ways for handling long running alerts in process chains.
I need to be sending out mails if the processes are running for longer than a threshold value.
I did check this post:
Re: email notification in process chain
Appreciate if anyone can forward the code from this post or suggest me other ways of handling these long running alerts.
My email id is [email protected]
Thanks and Regards
Pavana.

Hi Ravi,
Thanks for your reply. I do know that i will need a custom program.
I need to be sending out mails when there is a failure and also when process are running longer than a threshold.
Please do forward any code you have for such a custom program.
Expecting some help from the ever giving SDN forum.
Thanks and Regards
Pavana
Message was edited by:
pav ana

Handling Error Messages in Process Chain

Hi Gurus,
I am developing a process chain which contains more than 40 Master Data Objects. Those are connected serially with "always" link.
Start -> Load Data -> DTP -> Load Data -> DTP -
EX-OR (connected to all Processes for error message)
Here the EX-OR Process is not allowing me to connect with "Error" link to all processes (by default it is giving "Always" link). i.e i want to get the error message from EX-OR process only in the case of failure not always.
Can any one help me out.
Thanks in advance,
Chenna.

Greetings Chenna,
First we need to check why the "always" link is used to connect the process chain steps?
If you take such "always" link to connect the steps, we cannot raise an error message link to EXOR( by default it will also take "always" link)
Here we can explore an error message thru EXOR step whenever a failure occurs in the process.
Things we need to do:
1. Steps in the process chain should be connected only on "successful" option selected.
2. We need to link the required steps to the EXOR step with "errors" selected on the pop up.
3. Need to link an Error message to EXOR step by selecting "Create message" on EXOR step.
Now if any failure occurs in the process the error message will be raised.
this helps...

How to handle hierarchies in process chain

Hi All,
I am designing the process chain for a master GL account number . It has attribute hierarchy and text.
I am successfully able to create the process chain for the attribute and text . But when i add the infopackage for the hierachy I am confused as I have two hierachy infopackages as the client is using two hierachies for the GL accounts.
How should i incorporate these two infopackages which are refereing to two different hierarchies of R3.
I will appreciate your replies.
Regards
Rahul Bindroo

Hi all,
But when I try to put the infopackage with first hierarchy in the process chain I dont get the save hiearchy and attribute change run automatically while as for attributes i get the attribute change run automatically.
If I have to add the load process 'Save hierachy ' i do the following steps:--
Drag and drop save hiearchy--->if i use F4 no list appears/if i create the variant i get a screen with the object type field -
What should I select there.......?>**
Am I following right steps or I am missing something.
Regards
Rahul Bindroo

Process chain design errror

we are creating a process chain, till date we are loading data with a infopackage. Now we wants to incorporate this IP in the process chain, but process chain becomes red at ODS and gives error 'Not able to use as loading varient' .
can some one put light on this error and suggest me a solution.
replies will be rewarded with points.

Hi
Go through these links
http://help.sap.com/saphelp_nw2004s/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.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
Regards
GTR

Errror when activating process chain

Hi All,
Geeting the error while activing process chains in Quality.
Error is *'Node Characteristic 0classnum is not entered as hierarchy characteristic for 0material*
can any one help on this.
Thanks in Advance.
Srinivas

Hi
This is not advisable to activate a process chain in quality directly. You should do it in development and then transport it across.
This error is realated to hierarchy. Do you have a hierarchy load attached to this chain?
Check the hierarcy first. Then activate the chain.
Cheers
Chanda

Handling Process chain

Hi Experts,
In my project Basis people are going to down the BW production server, in this project total 37 process chains are there, in this time what kind of action i have to take on process chains, .
Please guide me......
Thanks in advance
Venkat

1. Check if any process chains are going to start and still run during the down time.
If so, stop them and schedule them after... so that no process will end in the middle....
2. If there are some process chains scheduled to start during the down time.
If possible run them in advance or you can schedule them after words since this schedule will be skipped.
Hope it helps,
Naveen Vytla

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.

Infopackage and process chain status

Hello expert,
I am new in BW technology and I need some help...
Well I have created a process chain in order to load data into infoprovider. This process chain is running everyday in production system, (it's a tipical PC: delete PSA request, run infopackage, run DTP....)
I have checked the last status of the process chain and it's yellow since two days ago... It was due a communication error between ERP and BW system, therefore (for some reason), the infopackages started but never ended (always yellow status).
So, my questions are:
1.- Is there any configuration for the infopackage to prevent yellow status (for more than X time)?
2.- Could we control it in a process chain?
Thank you and best regards

Hi,
We can configure for infopackage incase of no records found however you can setup for time linmit.
You can set the status the request is to receive per InfoPackage in the Scheduler, via Scheduler Warning Handling. This setting overrides the system-wide setting.
Check the below link for more info :
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65cfe07211d2acb80000e829fbfe/frameset.htm
Regards,
Satya

The 0co_om_opa_6 ip in the process chains takes long time to run

Hi experts,
The 0co_om_opa_6 ip in the process chains takes long time to run around 5 hours in production
I have checked the note 382329,
-> where the indexes 1 and 4 are active
-> index 4 was not "Index does not exist in database system ORACLE"- i have assgined to " Indexes on all database systems and ran the delta load in development system, but guess there are not much data in dev it took 2-1/2 hrs to run as it was taking earlier. so didnt find much differnce in performance.
As per the note Note 549552 - CO line item extractors: performance, i have checked in the table BWOM_SETTINGS these are the settings that are there in the ECC system.
-> OLTPSOURCE - is blank
   PARAM_NAME - OBJSELSIZE
   PARAM_VALUE- is blank
-> OLTPSOURCE - is blank
   PARAM_NAME - NOTSSELECT
   PARAM_VALUE- is blank
-> OLTPSOURCE- 0CO_OM_OPA_6
   PARAM_NAME - NOBLOCKING
   PARAM_VALUE- is blank.
Could you please check if any other settings needs to be done .
Also for the IP there is selction criteris for FISCALYEAR/PERIOD from 2004-2099, also an inti is done for the same period as a result it becoming difficult for me to load for a single year.
Please suggest.

The problem was the index 4 was not active in the database level..it was recommended by the SAP team to activate it in se14..however while doing so we face few issues se14 is a very sensitive transaction should be handled carefully ... it should be activate not created.
The OBJSELSIZE in the table BWOM_SETTINGS has to be Marked 'X' to improve the quality as well as the indexe 4 should be activate at the abap level i.e in the table COEP -> INDEXES-> INDEX 4 -> Select the u201Cindex on all database systemu201D in place of u201CNo database indexu201D, once it is activated in the table abap level you can activate the same indexes in the database level.
Be very carefull while you execute it in se14 best is to use db02 to do the same , basis tend to make less mistake there.
Thanks Hope this helps ..

Process chain errror handling

Similar Messages

Maybe you are looking for