Plzz correct me reagrding process chains.

hi friends,
iam working on BW in process chains.
i want to know the possible ways of correcting the process chains and plz help me if iam wrong and by providing ur suggestions.
1) whenever process chain fails , we will check process monitor in logview and find out that type of load . if it full load, we delete the request and we will restart the entire process chain.
restarting means we will again schedule and activate it right?
I refer a weblog on restarting of PC , it said that
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
My question is why will make the request green from red? and also if we the reuqest from rd to green , will the process chain works normally though it contains errors ?
2) how to correct if teh load is delta load.
Iam very much confused in handling the errors of process chains .
can any one explain me clearly plzz. any good documentation for error handlin plzz.
regards,
Siddartha

No duplicate posts please. Moderators will not entertain the duplicate posts.

Similar Messages

Best way to know correct forecast model - process chain set up with multiple forecast models

Hi Experts,
I need your help in selecting best forecast model for our company. We have some of the models already used for our company, and because of multiple models used it is taking very long time for process chain to finish. There is no existing documentation available on which model was used why initially. Please help me to make out forecasting process smooth.
- What is the best way to know, which forecast model is correct and should be used for our forecasting process.
- In case multiple forecasting models are really required to be used, please suggest ways to optimally schedule them in process chain.
- At times we get messages like "not enough data available" for specific model - any way to avoid this.
- How to optimally use parallel processing profiles forecasting process in process chain.
- Things which should be avoided.
Request your help, please share your experiences.
Regards
NB

Hi Neelesh,
There are many points you need to consider to redesign forecast process for your company/client.
You need to select the best suited forecast model first depending on the business. This has to be well tested & agreed by business users. Complexity will be an outcome of this exercise with business users. Best id to give then a brief intro on all available models & then help them selection the best one as per their requirement.
Auto selection models are generally more time taking & should be used only when you have no idea at all on the business/demand pattern.
Run time will depend how you are clubbing the CVCs to get the forecast generated & also parallel processing. For parallel processing profile you will need to do trial & error testing along with help from Basis team on how many free dial up processes are available.
Even you can run many forecast calculations in parallel if the product/cvcs are totally different. - As per my personal experience maximum run time reduction can be achieved here.
Daily run is not advisable except only for businesses where you have too much dynamism in demand planning i.e. you expect the demands to be changed overnight. Most of the companies run forecast on monthly basis or at weekly basis at the max.
"Not Enough data" will be a problem if you are having the irrelevant models used in forecast profiles. This means users are not bothered to maintain the needed data for he forecast calculations or they are not aware at all of the situation. Running such models on daily basis is not advised at all. Better users should use interactive forecasting & saving the results in such cases.
Just to give a crude example we get forecast calculated on monthly basis for approximately 4 lac cvcs in less than 3 hrs using moving avg, seasonal linear regression, seasonal trend, croston models. We use parallel profiles also everywhere with 10 blocks & 500 cvc/block.
Hope this helps. Let me know if you have nay more questions & also the results using any of this.
Regards,
Rahul

Data load Error using Process chain

Hi,
In NW2004s when I schedule delta loads for 2LIS_11_VAITM using process chains, when there is zero delta, the manage screens of the infocubes show green light with zero records correctly whereas the process chain log display shows red. The details of the process monitor show zero records. Is this right? I assume that even if there is zero delta, the log must show green and all the subsequent processes like activation of ODS, deleting of PSA, construction of indexes must be carried out. Please confirm. Is this a bug?
Thanks.
Param

Hi Victor,
Can you please advice how you solved issue as we are having similar issue where it works fine when loaded manually but throws communication error when process chain runs, following is error message..
Communication error: call FM RSSDK_DATA_REMOTE_GET
Thanks in advance for your help!!
Sandeep

Process Chain Red 'X', Exec Infopckg Yellow, Infopckg monitor/data correct

Dear and respectable colleagues of the forum,
I am experiencing a problem in a process chain when executing infopackages. The process chain has 6 "Execute infopackage" processes. Sometimes (1 of 4 attempts average) my process chain ended with red color with 'X' status in the Process Chain Display Log View.
Reviewing within the chain Log, there is one of the "Execute infopackage" processes that appears in yellow color (it loads from direct update ODS to an infocube). However, revising the Logs for its corresponding Infopackage execution I found that it says that "Data successfully updated". Moreover, If I review the data loaded it seems to have been loaded correctly.
Then, Why does the "Execute infopackage" process in PC finishes with yellow color if the Infopackage execution itself finishes correclty?
To complete the whole scenario: I execute this process chain every night from an Abap program; the program has a Loop that traverses a table, and executes the process chain as many times as the quantity of rows in that table (table has 10 rows meaning offices). As you can understand, the chain is executed 10 times, and the error occurs in any of the 6 "Execute infopackage" processes indistinctly.
I review ST22 and SM37 for all users for the datetime when the error occured butnothing bizarre was reported. It is left to review SM21.
The following is the detail of messages.
Logs for Execute Infopackage
   Data successfully updated
Monitor of Infopackage
Details Tab
     Requests (messages): Everything OK
     Extraction (messages): Everything OK
     Transfer (IDocs and TRFC): Everything OK
     Processing (data packet): Everything OK
       Data Package 1 ( 45 Records ) : Everything OK
         Transfer Rules ( 45 -> 45 Records ) : No errors
         Update rules ( 45 -> 45 Records ) : No errors
         Update ( 45 new / 0 changed ) : No errors
         Processing end : No errors
     Process Chains : Errors occurred
       Llena cubos de carteras vtas sec por distrib - autom

Dear s v desh,
I am on SAP BW 3.5, I already checked the cube and it is green - all right.
The message in the infopackage excution node in the process chain says (non-error):
"Data successfully updated"
The error message in process chain monitor (log) says:
......"Overall status: Error occurred: or: Missing messages
............Process Chains : Errors occurred"
I just realized that there is no messages at all in the infopackage monitor (log).
I have received a clue, someone asked me to review note 1396417, and I will.
Regards
Juan Alonso Teevin

DP macros are not being calculated correctly using process chain

Hello all!!
I have this DP planning book with two grids, which the second grid has some macros. I have to put this macros execution in a Process Chain, but it´s very strange because, when I execute the macro directly in the interactive planning the result is correct, but when I execute it using the process chain, the result is wrong.
The selection profile and the aggregation level in the Process Chain is the same that is being used in the selection profile.
I´ve already created the activities and also the planning job to be used in the process chain.
Could you help me?
Best regards
Angela

I would suggest to create a test selection Id with a few products (say 5) and create a new job with this selection profile and include that job in the process chain and execute it. Please monitor the job log while porcessing... for this right click on the process in the process chain and select 'Display all jobs'..it will take you to the SM37 screen..there click the job log and spool file and observe what exactly the job is doing i.e whether its executing correctly or its skipping that process or something else is doing...
The second thing you can try out is by creating a separate dataview for the second grid in the test sytem and replicate the scenario and check if it has any impact, my guess is if process chain is not supporting the macros in the second grid
Edited by: sai balakavi on Dec 12, 2008 8:14 PM

Modification of info object to correct the error in process chain.

Hi Gurus,
I'm facing some problem as mentioned below.
I'm loading data by using 5 info packages. Out of these 5 only one info package data has loaded properly the remaining 4 info packages are showing red status in process chain. Even though monitor status is green. When i checked the process chain it is showing error that duplicate data records.
I did analysis and i came to know that due to info object data type the info object Material number and Material group are showing same values. Now I need to correct the data type for those info objects. I've loaded these directly to info cube and to ODS object.
Now can anybody tell me the solution how do we go about to change the data type from Numc to Char. If we change how does it affect in cube as well as in ODS. How do we correct these type of errors when we are in Production system.
Thanks in advance....
Amarnath

hi Ravi,
Thanks for your help.
Thanks & regards,
Amarnath.
Message was edited by:
amarnath Reddy

Infopackage loads 0 record in process chain as BG job not running correctly

Hi Experts,
I have scheduled a daily process chain for Purchasing.
The infopackage in the process chain loads 0 records from R/3 and shows green status but data is available in R/3. Its a FULL update.
But when I load the data manually the infopackage fetchs the record form R/3.
When I checked the background job in R/3 that loaded 0 records, the job gets finished abruptly without fetchig any data.
Please find the job log below:
Job started
Step 001 started (program SBIE0001, variant &0000000210024, user ID RFCUSR)
DATASOURCE = ZPUR_S600
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 0                                       *
abap/heaplimit................ 40894464                                *
zcsa/installed_languages...... ED                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000320                                 *
ztta/roll_extension........... 2000683008                              *
Job finished
But the background job for the request when I run the infopackage manually calls a function BW_BTE_CALL_BW204010_E (BTE) and fetches the record from R/3.
Please find the job log that fetches the record when run manually.
Job started
Step 001 started (program SBIE0001, variant &0000000210036, user ID RFCUSR)
DATASOURCE = ZPUR_S600
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 41230008320                             *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000000                                 *
ztta/roll_extension........... 2000000000                              *
Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 26,596 records
Result of customer enhancement: 26,596 records
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 26,596 records
Result of customer enhancement: 26,596 records
Asynchronous send of data package 000001 in task 0002 (1 parallel tasks)
Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 26,596 records
Result of customer enhancement: 26,596 records
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 26,596 records
Result of customer enhancement: 26,596 records
Asynchronous send of data package 000002 in task 0004 (1 parallel tasks)
Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,062 records
Result of customer enhancement: 1,062 records
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,062 records
Result of customer enhancement: 1,062 records
Asynchronous send of data package 000003 in task 0006 (1 parallel tasks)
tRFC: Data Package = 000001, TID = , Duration = 000001, ARFCSTATE =
tRFC: Start = 20110217 054648, End = 20110217 054649
tRFC: Data Package = 000003, TID = , Duration = 000000, ARFCSTATE =
tRFC: Start = 20110217 054652, End = 20110217 054652
tRFC: Data Package = 000002, TID = , Duration = 000001, ARFCSTATE =
tRFC: Start = 20110217 054651, End = 20110217 054652
Job finished
Kindly help me on this issue as why the job run through process chain is not fetchibg any records.
Regards,
Indhuja

Hi Prasanth,
If the background jobs are not availbale when IP is triggered then the BG job will ot be executed and the IDOCs will get struck.
Once we push the IDOc only the BG job will be executed until then the PC will wait with yellow status.
Hence this is not the issue with the non availability of BG WP.
Also for last one week this issue was happening but today the job executed successfully through the Process chain itself.
Then it shows this is not the issue with PC also.
The job is executed using RFCUSR.
Please suggest what would be the possible cause for this issue.
Regards,
Indhuja
Edited by: Induja Rajkamal on Feb 23, 2011 11:48 AM

Process chain - How to correct?

Hi friends,
i have a process chain which failed at process LOAD INFOPACKAGE . subsequent to this process is UPDATE FROM PSA. .
we loaded the infopackage manually and tried to repeat the Update from PSA , but it got failed.
I have done any mistake in repeating the process update from PSA.??
plz tell me what should i do in this case.
regards,
Pavan

Dear Pavan,
When you repeated the process chain from update PSA step, it will take the failed instance of 'LOAD INFOPACKAGE' step. So it will fail only. Now what you can do is you can manually make this update PSA step green.
Follow these steps:
> GO to failed step, right click say maintain variant.
> go to tab chain
> open se11, table-rspcprocesslog, display list
> copy variant, instance, date from chain to respective fields of this table
> execute
> open se38, Program-rspc_process_finish
> copy everything (variant, log-id, instance, date) which has copied earlier and write status as G.
> execute
> Refresh the chain
After doing this your update PSA will become green and process chain will continue further.
Hope this helps.
Thanks,
Nabha

Correct Process Chain Sequence

Hi, I was reviewing some SAP Help on Process Chains and noticed that the Sequence Graphic they provide for Process Chains does not include the very import step of "Compression" (see the link below)
Does anyone think this should be in there or is there a reason it is not included?
Thanks for your opinions.
http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm

Hi
Compression is also one of the important task in Info Provider Administration. Once you do compression, you can not do request based deletion in Info Cube.
Lets take a situation, after one week or 10 days you found one request was wrongly loaded to your cube. If you compress your cube daily, then you have to go for selective deletion which difficult activity.
for this reason, generally compression will be performed after 15 days or 1 month.
It again depends on how much data you are getting daily as delta, because if you have huge uncompressed data in your cube this will decrease the report performance.
Regards,
Venkatesh

Process chain failed due to activation of a DSO

Hi friends,
Three four days back the process chain has been failed due to the activation error.The issue was with data and i have deleted the request in manage screen and reloaded again as repeat of delta with corrections in PSA. Which is afterwards activation is successful. Now process chain is getting failed daily saying that request is not present in the DSO( Request is no longer exists in the DSO ). But manual activation of DSO is successful.
Please help me in this reagrd.
Regards,
anil
PS: I tried by removing process chain from scheduling and rescheduling back.

Hi........
Deleting request from the PSA will not help............what is the update mode of ur ODS..........if it is overwritten............then no probs...load the request again in the target...........if not..........then do one thing...........push the request again in the target.........then...........make the QM status red................then delete the request again............just check whether u face the same issue again or not...........
Generally we face this issue............suppose we load a delta request successfully in the target.........then we delete the request without making the QM status red............and after that next delta also loaded............then while activation...............it will ask for the deleted request...........I think there is some confusion...........and u can try the trick..............it may work............
Regards,
Debjani........

SAPSQL_ARRAY_INSERT_DUPREC during saving of Process Chain

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

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

Error while activating data in process chain

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

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

Cannot update data from DSO to Cube with further update in process chain

Hi Guys,
              This is the message am getting when am trying to update to cube by process further update with process chain.Process fails at further update with the following below message.
However at DSO level i can see the data mart status but no request at cube level.
Error Message:
Cannot update request REQU_D57WAP7Z2WAI1CG5Y5OQ5W7JR in data target
    Message no. RSM1523
Diagnosis
    System checks show that request REQU_D57WAP7Z2WAI1CG5Y5OQ5W7JR cannot be
    updated to a data target.
    The system checked whether
    o   request REQU_D57WAP7Z2WAI1CG5Y5OQ5W7JR is already in the data target
    o   the data target has active update rules for the InfoSource
    o   the data target was selected for updating
    o   locks exist
    o   for a DataStore object as a data target, that the request was
        updated in the correct order, if the DataStore object stipulates
When i check the monitor screen under status tab it says "A caller 01, 02 or equal to or greater than 20 contains an error meesage" and under details tab "Data Package 1 : arrived in BW ; Processing : Data packet not yet processed "
Regards,
Krishna.
Edited by: krishna Krishna on Mar 4, 2009 6:37 PM

Hi
It seems you used infopack when you select update data inot datatarget then system prompts you a infopack.That's the infopack which is generated by system being used in process chain variant to update data into datatarget.
Create new infopack/ DTP manually then use that infoapck/DTP on the process chain variant then try.
Chandu.

Process chain tables and tcodes

Hi frinds,
can any one send me the process chain tables and tcodes . plzz
regards,.
rajesh
my mail id is [email protected]

Hi Rajesh,
Process chain tables:
RSPC_BUFFER Shared Buffer for Processes (Esp. Customer
RSPC_MONITOR Monitor individual process chains
RSPCABAPASYNC Logging for ABAP Processes(Synchronously a
RSPCCATEGORY Process Type Categories
RSPCCATEGORYT Texts for Category
RSPCCHAIN Process chain
RSPCCHAINATTR Attributes for a Process Chain
RSPCCHAINEVENTS Multiple Events with Process Chains
RSPCCHAINT Texts for Chain
RSPCCOMMANDLOG System Command Execution Logs (Process Cha
RSPCENQUEUE Dummy Table for Runtime Locks of a Process
RSPCEXOR Excluding Or: Log Table
RSPCINFO Special Values for Communication between P
RSPCINFOT Special Values for Communication between P
RSPCINSTANCE Generic Instance Storage
RSPCINSTANCET Texts for Generic Instance-Storage
RSPCLOGCHAIN Cross-Table Log ID / Chain ID
RSPCLOGCROSS Cross-Table Log ID Old / Log ID New
RSPCLOGS Application Logs for the Process Chains (G
RSPCPROCESSLOG Logs for the Chain Runs
RSPCRUNVARIABLES Variables for Process Chains for Runtime
RSPCTRIGGER Variants for the Trigger Processes
RSPCTRIGGERT Texts for the Trigger Variants
RSPCTYPESDEP Dependencies for Processes
RSPCTYPESPROC Attributes of BW processes (RSSM)
RSPCVARIANT Generic Variant-Storage
RSPCVARIANTATTR Attributes of a Process Variant
RSPCVARIANTT Texts for Generic Variant Storage
Regards,
R.Ravi

Long running process chains - No Dump / error message.

Hello,
We have defined some steps in process chain that contains default macros. We mainly included that to ensure calculations happens even when users dont open or access the DP Planning book.
Issue is, these steps are running endless. normally it takes some 400 n odd seconds. But its running for the last 60000 secs.
No. of Planning objects or CVC is 2027 only. I had to cancel them and tried to re run this step or the whole chain no luck....
I have checked active jobs in SM37, there is none. So ideally there is no load on the system. Also no change to Macro or CVC's has been done. there was only one Transport that was moved and it was on the product master.
Also I have done the time series, Live cache, PA Consistency checks. only in Live Cache there was some Superflous time series and it was corrected.
I am not getting a clue of why its happening nor where to start the analsysis.
Any help or suggestion is greatly appreciated.
Currently I have made the subsequent events as independent,& the chain is running execpting this step.
Many Thanks
Aswath Ram.

Thanks for the reply,
These are custom macros. It adds two KF and copies to another.
The no. of periods is 24 time periods and roughly no. of CVC is 2100.
Another thing, this process chain has been running for last 5 to 6 months with no issues. Since sunday, its messing up....
I am doubting if its taking time read data from table or live cache. or is it because of some indexing. Not sure how to check that.
have asked Basis to check the system performance, if it might cause this issue.
Many Thanks
Aswath

Plzz correct me reagrding process chains.

Similar Messages

Maybe you are looking for