FIGL Process Chain

Hi Friends !
In our system, we have the following FIGL DSO's Cubes. I want to make a process chain on FIGL. Query is do we have any data sequence? or we can load in parallel? Please advise.
Average Daily Balances (Direct) 0FIGL_V60
Cost of Sales Ledger: Financial Statements 0FIGL_VC2
Cost of Sales Ledger: Transaction Figures 0FIGL_C02
Financial Statements (Direct) 0FIGL_V30
Financial Statements (Replicated) 0FIGL_C30
Financial Statements (from Replicated Balances) 0FIGL_V31
G/L (New): Balance Sheet and Profit and Loss 0FIGL_V10
G/L (New): Balance Sheet and Profit and Loss Remote 0FIGL_V11
G/L Accounts: Plan Line Items (Direct) 0FIGL_R50
G/L Accounts: Transaction Figures (Direct) 0FIGL_R20
G/L Accounts: Transaction Figures (Replicated) 0FIGL_C20
GL Accounts: Line Items (Direct) 0FIGL_V40
General Ledger (New): Transaction Figures 0FIGL_C10
General Ledger (New): Transaction Figures Remote 0FIGL_R10
General Ledger: Financial Statements 0FIGL_VC1
General Ledger: Transaction Figures 0FIGL_C01
Average Daily Balances (Replicated) 0FIGL_D60
FIGL: Transaction Figures 0FIGL_O06
FIGL: Transaction Figures - Cost of Sales Ledger 0FIGL_O07
G/L Accounts: Line Items (Replicated) 0FIGL_D40
General Ledger (New): Transaction Figures 0FIGL_O10
General Ledger Accounting (New): Line Items 0FIGL_O14
General Ledger: Line Items 0FIGL_O02
With Regards
Rekha

Hi Rekha,
Process chain needed to be defined based on Dependencies, there is only dependency with standard FIGL objects are standard one like we need to load masters first before DSO/Cube load and in a single data flow you need to go in a sequence. Also it is based on if any lookup you have written to load data in Cube/DSO.
Please check complete flow for all these Objects in this list and then you can make independent flows in parallel.
Regards,
Ganesh

Similar Messages

Process Chain Failed

Hi
Process chain for FIGL Extractor has been failed.
the Status is showing Red in Load monitor of info package , No Data came till PSA.
But the Job in R3 system is still running, it seems IDocs have been stuck in Trfc queue.
i informed Basis team about this situation.
Please let me know if any appropriate step should be taken from my side to ensure all Delta records will come successfully in BW system.
my ques is "Is Repeat of the prcess chain will fetch Complete Delta without missing a single record"
*BW info package Load Monito
r*Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
in the source system
R3 System Job Log
Asynchronous sending of InfoIDOCs 2 in task 0001 (0 parallel tasks)
Regards
Atul

It is showing No error found in diagnosis..
I think it is not error.. it will turn to green from red when it will get finish at R3 system.
I have also faced same problem before, it gives red but shows no error and background job still running..
and if there is RFC connection problem that you can check using t-code SM59..

Process Chain Arrangement

Dear All,
I am working on process chains. There is this parent process chain which is already made with its blocks(which represents sub chains). The parent chain runs once everyday(scheduled) and has been running fine till yesterday. I have to change the order of the blocks . At present it is Sales Block -
> Costing Block--> FIGL Block--> FIAR Block>Stock Block. I want it as Sales Block-> FIGL Block--> FIAR Block->Costing Block--->Stock Block. I go to the links between blocks and delete the links and then rearrange the blocks as required and then make "successful" links between blocks. I verify whether chain is OK and it is. I save it and then activate it. Then I go to the log and see previous day's log and it shows me a disfigured process chain with blocks lying alround the place misplaced. Why has this happened? Will my process chain work according to the order I have made or will it be affected by the disruption of chain shown in log of previous days?
Regards,
Ratish

Hi,
 I go to the log and see previous day's log and it shows me a disfigured process chain with blocks lying alround the place misplaced. Why has this happened?
because the process chain is different from yesterday, so it will behave like misplaced only.. refresh the screen for the previous log entries..
It will work according to your order.

Process Chain - Delete File from Application Server

Hi Gurus,
Im working with Process chain, and i have a load from a flat file, so my question is :
How can i delete that file from the application server after was loaded ?
THANKS IN ADVANCED !!! I REALLY APRECCIATE YOUR HELP.
Marcos

hi,
I have gone through the forum you have posted for deleting files from application server through process chain.
I have similar reuirement in my project.
Can you please provide me the solution?
Your inputs will be highly appreciated.
Thanks in advance.
Regards,
Lavanya.

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

BPM Process chain takes long time to process

We have BI7, Netweaver 2004s on Oracle and SUN Solaris
There is a process chain (BPM) which pulls data from the CRM system into BW. The scheduled time to run this chain is 0034 hrs. This chain should ideally complete before / around 0830 Hrs. Now the problem is that every alternate day this chain behaves normally and gets completed well before 0830 hrs but every alternate day this chain fails there are almost 40 chains running daily. Some are event triggered (dependent with each other) or some run in parallel. In this, (BPM) process chain, usually there are 5 requests with 3 Delta and 2 full uploads (Master Data). The delta uploads finishes in 30 minutes without any issues with very few record transfers. The first full upload is from 0034 hrs to approximately 0130 hrs and the 2nd upload is from 0130 hrs to 0230 hrs. Now if the 1st upload gets delayed then the people who are initiating these chains, stop the 2nd full upload and continue it after all the process chains are completed. Now this entire BPM process chain sometimes takes 17 -18 hrs to complete!!!!!
No other loads in CRM or BW when these process chains are running
CRM has background jobs to push IDOCS to BW which run every 2 minutes which runs successfully
Yesterday this chain got completed successfully (well within stipulated time) with over 33,00,000 records transferred but sometimes it has failed to transfer even 12,00,000 records!!
Attaching a zip file, please refer the 21 to 26 Analysis screen shot.doc from the zip file
Within the zip file, attaching Normal timings of daily process chains.xls the name explains it.
Also within the zip file refer BPM Infoprovider and data source screen shot.doc please refer this file as the infopackage (page 2) which was used in the process chain is not displayed later on in page number 6 BUT CHAIN GOT SUCESSFULLY COMPLETED
We have analyzed:--
1) The PSA data for BPM process chain for past few days
2) The info providers for BPM process chain for past few days
3) The ODS entries for BPM process chain for past few days
4) The point of failure of BPM process chain for past few days
5) The overall performance of all the process chains for past few days
6) The number of requests in BW for this process chain
7) The load on CRM system for past few days when this process chain ran on BW system
As per our analysis, there are couple of things which can be fixed in the BW system:--
1) The partner agreement (transaction WE20) defined for the partner LS/BP3CLNT475 mentions both message types RSSEND and RSINFO: -- collect IDOCs and pack size = 1 Since the pack size = 1 will generate 1 TRFC call per IDOC, it should be changed to 10 so that less number of TRFCs will be generated thus less overhead for the BW server resulting in the increase in performance
2) In the definition of destination for the concerned RFC in BW (SM59), the Technical Setting tab says the Load balancing option = No. We are planning to make it Yes
But we believe that though these changes will bring some increase in performance, this is not the root cause of the abnormal behavior of this chain as this chain runs successfully on every alternate day with approximately the same amount of load in it.
I was not able to attach the many screen shots or the info which I had gathered during my analysis. Please advice how do I attach these files
Best Regards,

Hi,
Normally index creation or deletion can take long time in case your database statistics are not updated properly, so can check stat after your data loading is completed and index generation is done, Do creation of database statistics.
Then try to recheck ...
Regards,
Satya

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.

Error while Activating a process chain

Hi,
I have just modified the existing process chain with the new info package for loading into ODS and then delta update into the Info Cube.
when i am clicking on the option schedule and activate.
Its giving error as :
"InfoPackage ZPAK_49RJW545FSO2MB3NF1MIZ9NJ9 is
generated; NOT able to be used as loading variant"
This is a IP, which is used for delta update from ODS to cube.
I have checked the IP, its fine like i can do the delta through this pacakge manually.
Please help, points will be rewarded....

Dear himanshu arora ,
Go and check whether the Info Package exist ,
You can check in Rsa1 and give IP name and find it.
If your IP is not there please create it,
If tehre please check the all parameter associated with it.
Also go through these
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Process chain creation - step by step
/people/juergen.noe/blog/2008/01/11/process-chain-creation--step-by-step
Data Load errors and Process chains
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
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/3507aa90-0201-0010-6891-d7df8c4722f7
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
ope 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 it helps
Regards
Bala

Error while creating a process chain

Hello BI Gurus,
I have activated the Business Content Scenario in Plant Maintenance for Infocube 0PM_C08(Measurement Results).
It provides a datasource -> infocube flow,through DSO with transfer and update rules.(3.X scenario)
I have two questions -
1.When I am trying to create a process chain for this scenario for regular delta loads(Loading from the datasource - > DSO - > infocube),
Start - >Execute InfoPackage->Activate DSO Data ->
Then when i insert the Execute Infopackage for the load step from DSO to Infocube in the process chain and check it, it is giving an error saying "InfoPackage ZPAK_D50AJ26831X6L4IIOTZTSXWAE is generated; NOT able to be used as loading variant ".
I got this infopackage by right clicking on the context menu and going to Additional Functions -> Update 3.x data to Data targets.
Why am I getting this error and how to resolve it, bcos when i load it manually it is working fine?
2.If the error is because I did not use a infopack created by me, then how to create a infopack for loading to the infocube from DSO in BI7, because when i select from the Context Menu for creating infopack, it is taking me to the already generated IP ?
Also instead of using the 3.X mechanisms, if I decide to create a DTP, will the transformation created with it automatically map all the rules in the "Update Rules" for all fields?
Waiting for your guidance.
With Warm Regards,
Vineeth
Edited by: VINEETH SUBRAMANIAN.B on Jan 31, 2009 12:11 PM

Hi,
Check in SDN
Problem with process chain
Re: Updating Data from ODS to IC using Process chains
Indirect Spend Analysis
Thanks
Reddy

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

Error While Deleting cube Contents in Process Chain

Hi All ,
   I am getting a error when i am trying to delete the contents of two cubes in a Process Chain . The data of one cube is getting successfully deleted but while deleting the second one it results in a error.
Following are the messages :
1>Database table /BIC/FZCFEXP01 was deleted and recreated
2>Database table /BIC/EZCFEXP01 was deleted and recreated
3>Database table /BIC/FZCFEXP02 was deleted and recreated
4>Database table /BIC/EZCFEXP02 was deleted and recreated
5>Content Of Data Target ZCFEXP01 Successfully Deleted
6>Content Of Data Target ZCFEXP01 Successfully Deleted
7>System error: RSDU_DATA_EXISTS_TABLE_DB6/ DB6
8>Drop Cube Failed In Data Target ZCFEXP02
Can anyone Help ??
Sam
Any pointers . Help is highly appreciated.
Edited by: Samir Bihari on May 14, 2009 8:54 AM
Edited by: Samir Bihari on May 14, 2009 8:55 AM

Hi,
I'm not sure for this issue but it may relate to SP issue...
jst chk this notes:
Note 385293
Note 987754
rgds,

Error while deleting data from a write optimized DSO using a Process Chain?

Dear Bwers,
I am facing a strange error while using process chains to delete data from data target which is a write optimized DSO. The process shows as failed but the data gets deleted in the DSO. The error message is as below. Did anybody have a similar problem? Any suggestions.
Thanks
Raj
Error while deleting content of InfoCube/DataStore object ZLSD_G03
Message no. RSDODSO153

Please, check if you get any short dump in ST22 related to this issue.

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.

Regarding "Delete Index" process in the process chain.

Hi Gurus
In the process chain, I have Delete Index -> Load Info pacakge -> Create Index process in the above order.
I am loading few records, so no need to delete indexes everytime. Can i remove the "Delete Index" process from the Chain without deleting the Create Index process. Or do I have to delete both.
Could you please clarify my doubt if possible in detail.
Thanks,
Regards,
aarthi

With the numbers you provided, you probably don't need to have the steps. With Oracle (not sure about all the other DB flavors) there are some other considerations:
Not having the indexes when loading the data can improve the load time since the bitmap indexes are not very efficient with respect to inserts/updates. The more dimensions you have, the more indexes there will be and the more noticable the impact of having the indexes present when loading.
The drop index process only drops the F fact table indexes. If you compress your cubes regularly so that you don't have many uncompressed requests, the index rebuild time will remain small, but if you have many uncompressed requests in your cube, the index rebuild time can begin to exceed whatever time you might save on the load with indexes deleted.
With bitmap indexes present, you can also occasionally receive a ORA-0600 deadlock error during the load process, and that can be prevented by dropping the indexes before loading or chose the load option packet by packet so that two packets are not trying to update the same index block at the same time.
Another concern in shops where reporting on the cube might occur during the load process - if you drop indexes prior to a load, any one trying to run a query on teh cube could have poor query performance since all the indexes will be missing onthe F fact table, this agina becomes more apparent the more data you have in the uncompressed fact table.
So it really comes down to your environment, but certainly drop the indexes any time you have large loads.

Event is not getting triggered in the process chain

Hi,
We had a process chain which was triggered by an Event, and it was running fine until few days ago. So I removed the chain from schedule and re-scheduled it again with these details:
File load: every 2 hrs
Process chain setting
Immediate tab: start immediately
After event: "event name" and "parameter name" and periodic job: ticked
I activated the chain and scheduled it. But the event is not triggered and the chain does not start. I even tried to trigger the process chain manually in sm64 but the process chain did not start.
Can someone please tell me steps to automate the event triggering and also any setting that should be taken care off in the info package and the process chain.
Thanks In advance.
Ram

Hello Ram, to start your Process Chain by an event, then you need to maintain the Start process of the process chain.
Select "Direct Scheduling".
In the Change Selections, press After Event. Put your event name and parameter (if any). Also click on Periodic job.
Press Save. Then Activate and Schedule your process chain. All your processes should turn green.
To verify, right-click on the Start process and select Displaying Scheduled Job(s).... You should see a job called BI_PROCESS_TRIGGER in a Released status. You can click on the job and look at the start conditions.
When you go to trigger the event, use the same event name and parameter (if any) as in the start condition. Your process chain will then execute. To insure, use RSPC to view your process chain and press the Logs icon (last one at the top).
Does this help?

FIGL Process Chain

Similar Messages

Maybe you are looking for