Error in transporting process chain

Hi
i added two DTP's in the process chain and transported. The transport ended with errors.
The following is the error msg:
Results of check for process AND EVEN_4CEJM320EVCIY0L5L62W61JVB in chain PC_BI_TD_POSDM_CAST:
Process variant AND EVEN_4CEJM320EVCIY0L5L62W61JVB does not exist in version A
Results of check for process AND EVEN_4CEJM320EVCIY0L5L62W61JVB in chain PC_BI_TD_POSDM_CAST:
Process variant AND EVEN_4CEJM320EVCIY0L5L62W61JVB does not exist in version A
I saved and activated the process chain but still transport to QA ending with errors.
When i saved the process chain in DEV, i am getting the msg:
Version 'M' of chain PC_BI_TD_POSDM_CAST was saved without checking
What does that mean?
REgards
Annie

Hi
If I got your question properly, Your AND Event is not Collected at the time of Transport.
Try to Re Export the Process chain with all necessary grouped objects.
Version 'M' of chain PC_BI_TD_POSDM_CAST was saved without checking
What does that mean?
Try to Check-- Save and then Activate and Then Transport .
Please follow the Sequence for the transport, You may recheck the flow again
Transport Sequence
Info Objects,
DSO
INFO CUBE
TRANSFORMATIONS
MP
INFOSETS
PROCESS CHAINS
QUERIES
Objects need to be transported with respect to their
dependencies
InfoProviders will bring in all relevant InfoObjects
Importing of Global variables is dependant on their reference
InfoObject being already active
Queries, workbooks and roles are dependant on InfoProviders
and InfoObjects being active
Use the Transport Connection Tool to analyze your objects
Transport all customer-defined packages (dev classes) before
transporting objects
Transport InfoProvider(s) using the "In Data Flow Before" or
"Only Necessary Objects" grouping option
Transport all Global Variables with primary package
assignment
i.e. ZBW
Transport BEx objects with appropriate individual package
assignment
Transport roles and workbooks together.
Hope it helps

Similar Messages

Error in Transporting Process Chain in BI 7.0

Hi Gurus,
i m getting following error "Object 'DM' (APCO) of type 'Application' is not available in version 'A' " in BI 7.0 while transporting a process chain.
I thought it my have issues with version of process chain, but the proces chain is in A version still is gives above error.

[Hello Sonal,|http://chandranonline.blogspot.com]
APCO denotes the OLTP Application Component. So check all the Application Components used in the PC are available.
Also see
SAP Note 382471 BW-OLTP-APCO: How do I transport it?
[BI Content Delivery in OLTP Systems by SAP (SAP Library - Customer Content in OLTP Systems)|http://help.sap.com/saphelp_nw04s/helpdata/en/ca/85f911c4bda4479af0a062bd9dfa94/frameset.htm]
[Thanks|http://chandranonline.blogspot.com]
[Chandran|http://chandranonline.blogspot.com]

Error in Transporting Process Chains

Hi All,
I have a requirement of changing the object name of the Process Chain.
This I have achieved by copying the existing process chain and meeting the naming conventions of the process chain as per client requirement.
Now As both the process chain have the same start variant shows the error. Again I have solved the same by removing the start process of the original process chain and created a new start process for the original process chains. This now shows no error.
The problem is when I try to transport the copied process chains I am getting the error pop up message
"Edit objects separately since they belong to different original systems"
Kindly help how to transport the same

Hi DPN,
Check oout this thread. This might solve yuor problem.
Errors in Transportation
Thanks and Regards
Subray Hegde

Error on Transporting Process chain

Hallo,
Can you please help me with the following error?
I am trying to transport a process chain into productive system and I receve the error below:
Start of the after-import method RS_RSPC_AFTER_IMPORT for object type(s) RSPC (Activation Mode)
Version 'M' of chain SV_CSM_MD_R3_START_VIL was saved without checking
Error in remote call of destination ALE_EP1010_BTC
Start of the after-import method RS_RSPT_AFTER_IMPORT for object type(s) RSPT (Delete Mode)
Errors occurred during post-handling RS_AFTER_IMPORT for RSPC L
RS_AFTER_IMPORT belongs to package RS
The errors affect the following components:
   BW-WHM (Warehouse Management)
Could you please help me?
Thanks
Ramona

Hello Ramona,
Please check the following points,
1. Process Chain is active without any error before transporting
2. All the Processes, variants are collected in the transport request and package.
3. Do set the Process Chain Start to Immediate(background jobs) in the schedule, because this will trigger the process chain once tranported and may cause similar errors
Thanks
Chandran

Errors transporting process chains

Hi,
we got some problems while transporting process chains.
The error occurs in the method execution. The transport log says:
Start of the after-import method for object type R3TR RSPC (Activation Mode).
Version 'M' of chain <i><name of the chain></i> was saved without checking.
0 Chains Were Selected.
Message no. RSPC031
Specifying process chain ID <i><name of the chain></i>, type V2&', and variant '' has resulted in the selection of 0 process chains. The selection has been called without confirmation by the user. This means that the user was unable to make a selection.
The function is terminated.
There is probably an error in the program. Look for corresponding notes.
We can't find any notes for this error message. The whole thing is confusing, because sometimes we find the chain in the target system, sometimes not.
Has anybody experiences with this kind of problem and how to solve it?
Thanks.
Knut

Hi,
Did you make sure that you transported all the process variants that the chain is using?
Please, check that by going to transport connection and transporting your process chain.
We always use that method to transport process chains: first getting all variants from the chain on transport connection and putting them on a transport request. Second establishing the start time of the PC and finally activating and scheduling the PC. You then release and transport that order.
Which version is your system? 3.0B?
Regards,
David.
Message was edited by: David Sirvent

Error in remote call of destination - when transporting process chain

Hi all,
I have earlier not had troubles transporting process chains from development system to test. Now I get the following error
Error in remote call of destination BW Test
Message no. RSPC051
Diagnosis
The following error occurred during the remote function call for destination BW Test:
Name or password is incorrect (repeat logon)
System Response
A short dump has probably been written in the other system.
Procedure
Look at the short-dump overview in the other system.
I know we have a transaction (RSTPRFC) where we give the password for the user that will do the activation of the PC after transport, but checking with the basis guy, and according to him there has not been any changes to this user. (As the user is the same as the RFC user used when setting up source systems). Running a check on the source systems from RSA1 gives green on all, so then the user should be correct...
(there is also no short dump available in the other system)
Does anyone have a clue on what could be done to locate the error..?
Thanks
Regards,
Øystein

Hi,
you are both right, and I got the issue corrected. In SM59 i have an ABAP connection that when checking it, gave me a logon error. When getting this connection working (by giving another password) and then setting the same password in RSTPRFC, the transport worked.
I'm just not sure I understand why this became an issue.
But anyway, thanks for the input.
Regards,
Øystein

Error messages in Process chains

Hello BI fans
In which transaction can I maintain batch-initiated error messages from process chains.
I am not looking for the process chain variant for messages.
I would like to create messages only for errorness messages.
thanks
BEO

Hi,
Please check the forum before posting for this issue.
Here You can follow below steps:
1) right click on process type and select "create messages".
2) choose "error" and create variant for error message
3)write message body in "EDIT DOCUMENT" and mention email ID's in "Maintain Recipient list" tab
4) save and schedule the chain again
Edited by: shailesh patil on Nov 14, 2011 5:51 PM

Error handling in process chain-doubts

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

Hi Pavan,
Hope the following links will give u a clear idea about process chains and clear ur doubts.
Business Intelligence Old Forum (Read Only Archive)
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Errors in monitoring of process chains can be categorized into 4 different sections...
Master data - Full Update
Master data - Delta Update
Transaction data - Full Update
Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
U can even look into these links:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
For common data load errors check this link:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
****Assign Points if Helpful****
Regards,
Ravikanth.

How to identify what are all the errors appears in process chain,

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. Check for the load timing for the respective master data, if it less than an hour then make the request red and repeat the ip.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with Single as postfix.
         4. Goto data selection tab and change the range.
Tip: change the last 4 digits for from to 0000and the last 4 digit for to     9999.
        5. Repeat the ip.
         6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error
Reason: Data source replication Failed.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
         5. Delete the red request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select Initialize delta process try going for with data transfer.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto processing tab and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. Do remember to change the ip settings back to the original once after the second step.
ODS activation failure
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
         1. Goto maintain variant.
         2. Check for the QM status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g green.
         5. Execute and refresh the status.
Lock issue
Reason: The same ip is been locked by other user or may be used by other process chain.
         1. We can see the locked entries and in the transaction SM12.
         2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. And the manually update the failed IPs by selecting manual update in the context menu.
Alfa confirming value error, Time conversion error, Chain didnt start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didnt start: A scheduled chain didnt triggered at the prescribed timing.
-For all the above error we have to raise a ticket.
Idoc or TRFC error
Reason: An Idoc is been stuck somewhere.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is Transaction Recorded it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is Transaction executing then it means its fine wait.
         6. Or raise ticket.
Error Due to short Dump
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
Process terminated in the Source system.
           Reason: Sometimes we face that a load has failed due to job Termination at Source System.
      This happens due to unavailability of the source system or some connectivity problem between source and target systems.
1.      Make the request red.
2.      Delete the request from the data target.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu

Transporting Process Chains that execute based on Events

Hi,
I am new to Process Chains and would appreciate some help. I created a process chain in our Development environment. The Chain executes based on an Event trigger. I activated and scheduled the chain. I then transported the chain to our Quality Assurance environment. The chain looks like it transported correctly. However, if I look in sm37, there is not a job out there for the Process Chain with a Release status. Therefore, if I trigger the event, the Process Chain does not run.
What am I missing?
Thanks.

Hi Tekii:
I created many Process Chains and I never had this problem.
NOTES: You cannot transport Process Chain Scheduling.
Do these steps in sequence and let us know what happened.
1) Go to DEV. Open the Process Chain Start Process. Copy the Event Technnical Name. If the Event has a parameter, copy that one too.
2) Go to QAS. Run transaction SM62. See if the event does exist in QAS. (You cannot transport Events, they have to be manually created). If the event doesn't exist, create that event.
3) GO to QAS Process Chain, De-Schedule the Chain. Open the Start Process. Check and see if the Event is the same name. Make sure that, if there is a parameter in DEV paste it in QAS. Check Mark Periodic. Now, Activate and schedule the Process Chain.
4) Now, trigger the event. If the Event has a Parameter, you have to add the parameter too. NOTE: Parameter is case sensitive.
5) The name of Function Module to trigger is: BP_EVENT_RAISE
It needs: Event Name, Event Parameter (if needed), & TARGET_INSTANCE (Copy the Source System Technical Name from BW QAS using RSA1 so that therer are no typos).
Now, tell what happened.
Good luck.
Ram Chamarthy.

Transporting Process Chains

I have not transported process chains before so wanted to check:
When transporting process chains do they by default come across inactive and you need to activate them on the receiving system, or are they supposed to be transported in the active state. I would expect the latter but just needed a confirmation

Hi Niten,
process Chains will be transported and needs to be activated and Schedules in the target system, i face the same probelm when transportes from DEV to QTY System.
even for meta Chains you have to trigger events and schedule the meta chains to be triggered by main chain for else mata chains will not be triggered.
hope this helps
Regards
Daya Sagar

Transport process chains

Hi all
Please list out the steps to transport process chains from QAU to PRD.
We have all hte infopackages,DTP's,infoobjects int he production.
Now we need to transport ProcessChains.
Intransport connection->Grouping option?collection option?
Please suggest me.
Thanks,
Harika.

Hi Harikag,
The problem that you are facing is most often faced when the transport is made from DEV / QUA system to production system. This occurs more often when objects already existing in production are re-transported to production. Most of the times the corresponding transformation / DTP's get inactive. Nothing can be done as the the entire thing depends on way you transport the objects to production, only prevention is possible or else you need to apply the cure :). Don't worry as this is common scenario during transports. Try activating the transformations manually or you can try to re-transport objects in correct order. Please check the below thread, it will help you to find out the programs that can be used to activate the inactive objects manually.
ODS and Transformations get inactive after i transport it in PD.
Also check the below SCN doc which would be really helpful in case of handling inactive transformations:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10858449-1f59-2e10-0095-dde76e16d330?QuickLink=index&overridelayout=true
Also in case you are transporting a chain then do remember that the start variant of your Metachain & all the local chains if any should be for future date else the chain starts to run automatically once the chain is moved to production. Once the chains are moved then you will need to manually change the scheduling option as per your requirement i.e main or metachiain for the required time & local chains with "start using a metaching or API option". This point should always be remembered during a fresh transport for a new process chain.
Hope that the above info helps you in solving your problem.
Thanks
Edited by: Pawan Chaturvedi on Oct 27, 2011 12:59 PM

Maintaining Transported Process Chains

Hello,
we transported few process chains from our Dev system to Production BW. Now, we are trying to modify the transported process chains in Production BW. It is asking for a transport# when we try to do this. Is it possible to set the system, so it won't ask us for a transport# when making changes to transported process chains?
We are currently on BI 7.0.
Thanks.

If it asking for transprots then Your Prodcution system is Open ....
System Open options:
SCC4: Changes without automatic recording
Changes to repository and cross client customizing objects allowed
Protection level1: NO overwriting
eCATT and CATT allowed
Uncheck all restrictions
then go to se06
System change option: global settings
change from non modifiable to modifable
Systsem closed options:
Changes and transports for client-specific objects-- No changes allowed
Client-independent object changes
No changes to Repository and cross-client customizing objects
Protection level 1: no overwriting
Restriction wehnt starting CATT and ecATT:
ecatt and catt allowed
se06 and change all modifiable to non modifiable.

Transport process chain by transport connection step by step

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

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

Error "Object 'DM' (APCO) of type 'Application' is not available in version 'A'" while transporting process chain to production system.

Hi Gurus,
Whenever I try to transport a process chain ZFI_0FIGL_C10 from dev. to qua. & prod. the error “Object 'DM' (APCO) of type 'Application' is not available in version 'A'” is displayed in the end of creating transport package.
The process chain was created to load data to 0figl_c10 and it works all right on all systems (dev. qua. prod.).
The process chain contains processes for:
- starting the process chain
- executing infopackage (for loading data to 0figl_o10),
- ACR (activate data in 0figl_o10)
- delete index 0figl_c10
- DTP loading data from 0figl_o14 to 0figl_c10
- executing infopackage 80FIGL_O10
- creating index in 0figl_c10
- building DB statistics
- rolling up aggregates in 0figl_c10
- deleting of requests from the changelog 0figl_o10
- deleting of requests from PSA (0fi_gl_10)
How to find what cause that error.
Regards,
Leszek

Hi,
A SAP consultant told me to ignore that error.
Indeed, after creating transport with some new process chains (again I was informed about that error "APCO ...") and transporting it to production everything works all right.
The problem is described in sap note: 883745.
Regards, Leszek

Error in transporting process chain

Similar Messages

Maybe you are looking for