Connecting lines in process chains.

Hello Gurus,
I would like to know about the different colours of the lines connecting the various processes in the chians. There are GREEN, BLACK AND RED ones both BOLD and DOTTED. That means, all in all there are 6. Could you please tell me when do we see each one of them.
Its my pleasure to award points,
Thanks and best wishes,
i-bi

Hi i-bi,
The different colors indicate conditional executions:
Black: to be executed without condition
Green: to be executed if predecessor ends sucessfully
Red: to be executed if predecessor ends with errors
The line style indicates if a step has already been executed:
Dotted: Is to be executed
Bold: Has been executed
Greetings,
Stefan

Similar Messages

Process chain program variant will not change from yellow...

Hello,
Problem:
I have a process chain that has two branches with 3 process chain variants on each leg in a parallel configuration. The process chain variants run different program variants. I am using variant object called "ABAP Program with Success/Failure " which can have a yellow, green, or red status and has status arrows that can be either red or green that connect to other process chain variants. The program executed with these variants is a customized BPS UPC_BUNDLE_EXECUTE program. When I run this PC the first variant on each leg usually hangs indefinitley on the yellow status. In the Backg tab log (double click PC variant in Log View) I can see the various SQL code that was ran. The last line of the log is an SQL-END:... Sometimes it will get past the first 2 varaints and hang on the next set of 2. Other times it will just hang on the last variant of one leg. It is very sporadic.
What I have observed and tried:
If I check my SM51 for the server the chain is running on I can see that the program in question is not running. If I run the same program through SE38 that runs via a PC variant it runs sucessfully in an appropriate amount of time. If I kill the process that has been running indefinitley through SM51 the process chain variant will go from a yellow status to a red as expected.
I changed they way I ran the programs from running in parallel in 2 legs to running all of them in one leg serially. That did not work. At least one program variant will hang on the yellow status.
I replaced all the variants using "ABAP Program with Success/Failure" to "ABAP Program" which has a red/green status but no red or green arrows, but black coming out of the variant forcing it to move down the chain on a sucess or failure. The process chain variants also hung in the yellow status using the "ABAP Program" variant.
I have tried starting the process chain using both "Direct Scheduling" with "Immediate" and "After Event." I have also kicked it off using "Start Using Meta Chain or API" so it was functioning as a sub process chain. Programs were still yellow in every case without changing to red or green.
I created new process chain variants for every single program/variant that I am using. Still no luck.
I have tried removing the chain from the schedule and re-activating and re-running and still no luck.
Thanks in advance,
Gary Martins

bump

How to connect processes in Process chain

Hi,
How to connect processes in Process chain.
how to make it as black,green,red.
Thanks,
Madhu.

Hi,
u can connect first process in a Process chain to second, just click on first process and drag and drop onto second one.
3 options will appear:
1. succesfull---green line
2. unsuccesfull----red line
3. always-----black.
select one option then linked will be formed.
green line means the second process will be executed if and only if first process ran successfully.
red line means the second process will be executed if and only if first process ran unsuccessfully.
black line means line means the second process will be executed even if first process ran successfully or unsuccesfully.
bye.
"assign points if info. is helpful"
Narendra reddy.

Transport process chain by transport connection step by step

Hello expert:
how to transport process chain by transport connection step by step?
Many thanks,

Go to RSA1 -> Transport Connection.
Make sure Only Necessary objects is selected under Grouping.
Expand Process Chain -> Click on Select Objects -> Search for the process chain you want to transport.
Select it and click transfer.
When finished collecting - Click on the Red Truck. Create a transport request when prompted to create a request.
Then go to SE10 or SE09 -> Find your request and right click and select release on your transport request as well as the task under it.
After it is released you can check the log by clicking on the log button and see if your transport moved successfully to target system.
Good Luck.
MP.

Missing subject line in BW Process Chain Messages

Hi Experts!
We are using BW3.5 (Support pack 16) process chains. There are a number of process chains and almost every thing is working fine.
But 2 process chains, send message without any subject into the email.
I did a number of tricks e.g. reactivated/rescheduled process chains, removed from scheduling and rescheduled, also deleted and recreated the message but nothing is working.
Did any one else face the similar problem?
Please let me know,
Thx
Praveen

Praveen I also had similar problem and i raised one earlier post here also .., you can check that
Re: Process Chain Maintain Message Edit Document Problem
what i found it is because of some bug and needed to import 23 support package for bw 3.1 there I noticed one more note for 3.5
hope it guides u some way
Message was edited by: Sukthi Sri

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?

DYNPRO_SEND_IN_BACKGROUND short dump in BW while calling Process chain remotely from APO

Hi,
While trying to call a process chain remotely from SCM APO system to SAP BW system - we are getting below short dump -
Short text
    Screen output without connection to user.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSDH4" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Checked the RFC connection between APO and BW system through SM59 and it is working fine - Can anyone pease suggest what configuration could be missing which might be causing this short dump.
Thanks in advance.

Additinal Data from Log -
User and Transaction
    Client.............. 200
    User................ "AQ1ALE200"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "53F896E0992E0A50E10080000AF04150"
    Program............. "SAPLSDH4"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "AQ1"
    Database Release.... 701
    Kernel Release...... 720
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 200
    User................ "KANDIS"
    Transaction......... "RSPC"
    Call Program........."SAPLRSPC_PROCESSES"
    Function Module..... "RSPC_DESTINATION_F4"
Call Destination.... "BQ2CLNT200_DIALOG"
Error analysis
    During background processing, the system attempted to sen
    screen to a user.
    Current screen: "SAPMSSY0 " 0120.
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    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:
    "DYNPRO_SEND_IN_BACKGROUND" " "
    "SAPLSDH4" or "LSDH4F09"
    "DISPLAY_LIST"
Information on where terminated
    Termination occurred in the ABAP program "SAPLSDH4" - in "DISPLAY_LIST".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 2205
    of the (Include) program "LSDH4F09".

UNCAUGHT_EXCEPTION with msg CX_RSR_X_MESSAG while scheduling Process chain

Hi Gurus,
We are facing a short dump while scheduling process chains, as follows:
 
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_RSR_X_MESSAGE
 
Error analysis
 An exception occurred which is explained in detail below.
 The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
 and
 therefore caused a runtime error.
 The reason for the exception is:
 No text available for this exception
 
Information on where terminated
 Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
 The main program was "RSPC_MAINTAIN_SINGLE ".
 In the source code you have the termination point in line 82
 of the (Include) program "LRRMSU13".
 
We tried to schedule it as a remote process chain from some other system it cancelled the job there with an ERROR_MESSAGE. We checked the RFC Connections at the source system side but it is working properly. We then tried to schedule the chain manually, we had this exception. Then we tried to have a look at previous logs of the process chain. It had this exception. We tried to reactivate the chain it was successful but when tried to schedule the chain same issue again. We tried to run the Meta chains under the same chain separately. They too gave us the same exception.
Please help.
Regards,
Sourabh Deo

S Simran wrote:
Hi,
>
> Ours is a fresh installation..
>
> When i am loading for the first time till PSA it is successful..
>
> As HR data sources are 3.5 datasources, i am loading cube via infopackage..
>
> When i start the load to cube it is giving me dump with exception CX_RSR_X_MESSAG.
>
> i checked note 615389 which talks about "buffering of number range object BIM9999998". the 0REQID is not buffered, but it does not throw any error msg in RSRV to correct the error..
>
> and one more note 1157796 which talks about patches with version BI 7.0.
>
> Now we are in BI 730 with heighest level 0005.
>
> Not sure how to solve this error
>
> Any ideas?
What's your SP? Are you having any master data updates left unattended? Check the Master data objects, check the flows. Related SAP Notes : 914304 / Check 967202(SP10) and 998673(SP11), 1157796, 763203 and 615389
Edited by: Arun Bala G on Feb 12, 2012 9:50 PM

Process Chain stuck

Hi... I'm very new to BI. I'm facing the following problem.
A process chain that was running got stuck. The process steps are green in color except that one of the source step has a green dotted line connection with the target step where the chain has stuck. Also the status of the source step is undefined. Kindly help me to make the chain run completely.

Hi,
There could be possible reasons to this issue, but one common reason is " when you try to refresh the PC and at that exact time if any processes gets completed, it wud ask for :Request change pop up, wud ask you for :save and trigger the next events: if you give :NO: , then the below event wont get triggred:
The above wud be of 1 off issue and if you get the same issue repeatedly, then check with BASIS for any absolute locks occured for any processes in the PC
Thanks,
Shaw

Send email if any step fails in Process Chain

I want to send an email if any step in the Process Chain fails. I know I can add a Message to each step but this is very cumbersome. I was trying to use the 'OR' collector and link each one of my steps to the 'OR' if it fails. I can do this for every step but the very last one. It does not allow me to drag a line from my last step to the 'OR'. Can someone tell me why?
Thanks.
Ryan

Boater,
I am not able to understand the scenario, but from what I understand you should be able to connect to. Could you explain?
Goodluck,
Alex(Arthur Samson)

Questions on Multiprovider and Process Chain

Hai All,
          I have two questions. One on Multiprovider and the other on Process chain.
1. Multiprovider:
          For example, I have 2 ODSs. ODS1 has Objects ORDER NUMBER, COUNTRY and PRODUCT, ODS2 has objects ORDER NUMBER, DELIVERY STATUS, CREATION DATE.
Now if I make a multiprovider on ODS1 and ODS2, then as ORDER NUMBER is common in both the ODSs, can I make a report like this:
ORDER NUMBER - DELIVERY STATUS, CREATION DATE?
         I have a problem here bacuase its not getting those details from the other ODS even though the ORDER NUMBER(value) is same. Am I making nay mistake or is it a system problem.
I beleive thats how a Multiprovider works.
2. Process chain:
                I have an END connector in my process chain that connects 3 processes and lets the following task start only after the success of all the above 3 processes.
The system is displaying the END connector seperately under each process. But the name and everything else is same. Is this a setting somewhere in the process chain?
Thank you.

Hi,
1. Those fields are in ODS2, you don't need to make a multiprovider.
2. You mean an AND connector. Maybe you need to refresh the screen. if this doesn't work, delete the three and connectors and insert a new one.
Hope this helps.
Regards,
Diego

Error while copying a process chain.

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

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

SAPSQL_ARRAY_INSERT_DUPREC during saving of Process Chain

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

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

Process Chain and e-mail configuration

We have configured a process chain e-mail message recipient by keying in the full recipient e-mail address in the message screen. This works successfully.
However, we would prefer to use the SAP User ID in the process chain message configuration. (The sap User Id would contain the external e-mail id)
Why: Because we do not want to have to reconfigure the process chain every time a user or an e-mail changes. We would like to use a generic user in the process chain configuration, and then only change the generic user e-mail when changes occur.
When trying to use the sap user id in the process chain no mail message is received.
We would like to seek input from folks in this forum who may have worked with a similar scenario and have developed a solution, or could provide suggestions on how to make this work.
Thanks in Advance

Barbara,
          Mine all work fine on WLS or Jserve, maybe you should include a code snippet??
          Barbara Singer wrote:
          > Hello:
          >
          > We have some simple servlets that need to process forms and bundle this
          > information up in a SMTP message. This is very basic stuff but we can not
          > seem to get this to work with WebLogic AppServer 4.51. I've built the
          > sample servlet /examples/servlets/MailServlet and this does not work either.
          > It also throws now exception. I can see it connect to the SMTP server ans
          > send the information but nothing comes through.
          >
          > I also read in your documentation that /utils/sendMail will be a deprecated
          > method in a future release. Is it still supported in 4.51?
          >
          > Any input, sample examples working, etc. is welcome.
          >
          > /bas
          Russell Castagnaro
          Chief Mentor
          SyncTank Solutions
          http://www.synctank.com
          Earth is the cradle of mankind; one does not remain in the cradle forever
          -Tsiolkovsky

Process chain and Control M

Hi Gurus
We are designing process chain for our BW solution.
We have identified the dependancies of various loads which includes flat file loads and loads from R/3.
Now we would like to control ERP and BW jobs by Control M .
I have the following questions:
1. Which portion of BW process chain do we need to plug in to Control M. ? Do we need to connect the Meta chain to control M or different process chains to Control M?
2.When we create Process chain for BW, what is the best practice? Is it good to create small chains and connect them via Meta chain? or we have to create small chains only?
3. Can we include R/3 extraction Jobs and V3 Jobs in our BW process chain? so that they will trigger when we run the process chain?
4. If we decide to run V 3 jobs after every half an hour on R3 side then how often we have to extract data to BW? and how to catch correct delta without missing single record?
I would appreciate if you can help me with your knowledge.
Thanks
Kris

Hi Kris,
Control M is a third party scheduling tool provided by BMC software.
1) You have option to either include a meta chain or individual chains in Control M .
2) It depends on how your data is extracted. If you have any dependecy jobs on sourcre system, then it is better to create small process chians and include them along with your dependecy jobs in Control M
3)you can include R/3 dependency jobs and V3 jobs in Control M. Once those jobs are finished you can run BW process chains via Control M.
4)You have several scheduling options availalbe in control M to take care of your BW and R/3 jobs.
V3 jobs collect data from R/3 application tables and fill R/3 delta queue(RSA7). when you run BW process chain it will collect all the data available from R/3 delta queue.
If both jobs are running at same time, then it is better to apply some wait time on BW jobs(in process chians).
hope this helps

Connecting lines in process chains.

Similar Messages

Maybe you are looking for