Error when collect process-chain

hi all,
When I collect the process-chain to transport in the transport-connection,an error occured in the below windows:
Object 'ATTRIBCHANEVEN_485MDFX3NYUF8PKGN9RSFATRD' (RSPV) of type 'Process Variants' is not available in version 'A'.
Could anybody help me?
The BI is 3.5 version
Best rgds!

the system tip of the error as below:
Object 'ATTRIBCHANEVEN_485MDFX3NYUF8PKGN9RSFATRD' (RSPV) of type 'Process Variants' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name 'ATTRIBCHANEVEN_485MDFX3NYUF8PKGN9RSFATRD' (in transport request RSPV) of type 'Process Variants' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System response
The object was not taken into account in the next stage of processing.

Similar Messages

  • Invalid DataStore object name error when running process chain after EHP1

    Hello,
    We recently upgraded our BW Dev platform to NW7.01 EHP1 SP6. I noticed that the layout for "Delete PSA Request" process in the Process Chain has changed after the upgrade. We can no longer specify the actual PSA table to delete eg, /BIC/B0001645. Instead we need to specify the Datasource name and the Source System.
    Now after the upgrade when I run one of my process chains, it fails at "Delete PSA Request" step with error message "Invalid DataStore object name /BIC/B0001645: Reason: No  valid entry in table RSTS". This datasource is based on the flat file source system and the PSA table for this Datasource is /BIC/B0001653.
    Unfortunately the process chain is picking up an older PSA table for this datasource and there is no way for me to specify the current PSA table name after this change in layout with EHP1 upgrade. Any suggestions on how to resolve this issue.
    Many Thanks,
    Al

    Hi,
    Please implement OSS 1345331.
    If this does not help try the below steps:
    1.  Run the report 'RSAR_PSA_CLEANUP_DIRECTORY/_MS' in check mode for a 
           particular PSA table for finding the inconsistencies.
    2.   After that please analyze the logs and if there is any problems related to partition, you need to correct them using the report u2013
    3.  'SAP_PSA_PARTNO_CORRECT' in repair mode for the
          PSA tables.  Run the report again after this
    4.  'RSR_PSA_CLEANUP_DIRECTORY/_MS' in check mode to 
         double check that the invalid partitions are 
         corrected.
         Once this is done you can execute the report     
         'RSR_PSA_CLEANUP_DIRECTORY/_MS' in repair mode.
    -Vikram

  • Error when run Process Chain via BPC NW

    Hi Gurus,
    I am implementing SAP BPC 7.5 NW in a customer and I´m facing the following error when try to run a process chain via Data Manager: "Failed to analyze instruction ,TAB,%TAB% ".
    Here is the scenario: we created a process chain that will be able to capture values recorded in a BPC application, load them into an DSO (make some transformations there) and finally send those transformed values to an specific table at ECC. This process will be started after some simulations at BPC and, when the user ends its simulation, start this process chain via BPC; this process chain is named as PC_ECC.
    We made a  copy of /CPMB/DEFAULT_FORMULAS and named it PC_FORMULA and, before step /CPMB/CLEAR, I assigned my process chain PC_ECC.
    So, at Data Manager, I add this process chain (PC_FORMULA) and in Advanced button, I put this statement:
    INFO(%EQU%,=)
    INFO(%TAB%,;)
    TASK(PC_FORMULA,TAB,%TAB%)
    TASK(PC_FORMULA,EQU,%EQU%)
    TASK(PC_FORMULA,SUSER,%USER%)
    TASK(PC_FORMULA,SAPPSET,%APPSET%)
    TASK(PC_FORMULA,SAPP,%APP%)
    //TASK(PC_FORMULA,LOGICFILENAME,DEFAULT.LGF)
    //TASK(PC_FORMULA,REPLACEPARAM,TESTE3%EQU%%TESTE3%%TAB%ASARENT%EQU%%ASARENT%%TAB%SOURCE%EQU%%SOURCE%%TAB%TARGET%EQU%%TARGET%)
    As we do not have any script logic to be executed, we commented the two last statements.
    When we run this package via DM, it gives us the message error:  "Failed to analyze instruction ,TAB,%TAB% "
    Looking through SDN forum we found two posts similar to this issues:
    But the suggestion to supress the statement TASK(PC_FORMULA,TAB,%TAB%) do not work; when we comment this statement, the message error gives us the message:"Failed to analyze instruction ,EQU,%EQU% "; when we comment the statement TASK(PC_FORMULA,EQU,%EQU%) and the previous (with TAB). the DM gives us the message: TASK(PC_FORMULA,SUSER,%SUSER%) and so on, until nothing has left to comment.
    Anyone of you view or has some similar case of error?
    Thanks in advance to you all
    Best Regards
    Adriano

    Hi Rich,
    Thanks for your answer.
    I checked the parameter at my process chain and it has a variant (/CPMB/DEFAULT_FORMULAS_LOGIC) with the parameters:
    TAB
    SUSER
    SELECTION
    SAPPSET
    REPLACEPARAM
    MEMBERSELECTION
    LOGICFILENAME
    EQU
    So, when I put in the task PC_FORMULA, TAB, %TAB%, it will be able to be recognized by the task...and the other parameters too. And when I take one of them off the task instructions, the system complains.
    Any other suggestion?
    Once again, thanks..a.nd best regards
    Adriano

  • 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 ‘0000’and 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 IP’s by selecting manual update in the context menu.
    Alfa confirming value error, Time conversion error, Chain didn’t 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 didn’t start: A scheduled chain didn’t 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

  • Send sms when bi process chain failed

    Hi SAP Gurus,
    Is some one inform me how is it possible to send an SMS when a process chain failed ?
    Is there a possibility to paramter something on the SAP BI system to execute this action ?
    Thanks

    Hi,
    I dont think there is an SMS option . But an email can be send when a Process chain gets failed.  The detail step for this is
    1. go to ALRTCATDEF
    2. select classification "Process Chains"
    3. click on display/change
    4. double-click on "error in a process of a process chain"
    5. click on "fixed recipients"
    6. write in your username (you have to maintain your e-mail address in SU01 for that to work)
    7. save
    8. In RSPC, take the required process chain
    9. go into edit mode
    10. from the menu, select Process chain -> attributes -> alerting
    11. check "send alerts if errors occur"
    Regards
    Lekshmi

  • 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.

  • Error when running process

    Hi I get following error when executing process in htmldb. Process type used is Anonymous PLSQL block executing following >> EXEC PRE_AUD.TRANS.DBSTAT_ALL
    error is ORA-06550: line 1, column 12: PLS-00103: Encountered the symbol "PRE_AUD" when expecting one of the following: := . ( @ % ; The symbol ":=" was substituted for "PRE_AUD" to continue.
    Can I not execute package/proc > EXEC PRE_AUD.TRANS.DBSTAT_ALL as anonymous block?
    thanks

    Vinat,
    "EXEC" or "EXECUTE" is a SQL*Plus command. Your PL/SQL process should simply be:
    PRE_AUD.TRANS.DBSTAT_ALL;
    Joel

  • Sending mail to GROUP ID when a process chain fails.

    Hi All,
    Can one suggest me, how to send a failure/success mail to a Group mial id when a process chain fails.
    I am awere about sending mails to individual mail id's when a any process fails or succed. I want to know the group ID creation part & how to tag the same SOCT.
    Thanks in advance.
    BR,
    Kiron.

    hi,
    The Distribution List/Group_id is created in SO23 transaction.
    hope it is helpful to u
    thanks

  • Errror when activating process chain

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

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

  • Collecting Process Chain Statistics

    Hi anyone,
         I'm looking to write some ABAP Code to collect Process Chain Statistics so they can be coherently evaluated and not by looking at the process chains individually. I'll be looking to identify variances in # of records, load times, etc. so I can send out alerts.
         I've been able to collect a lot of Process Chain Process information so far using existing API and FM calls.  I'm able to get down to the Process Log Levels so far, but I'm trying to think how to go about collecting the actual key figures I need. 
    <b>I'm looking to capture things like the following:</b>
    - Statistics of each process chain and related process chain process like I need to know that my ODS activation started @ 10am actived 10,000 records and ended at 10:01 am. (how long it took).
    - I need to know that my data load loaded 1,000 records and how long it took.
    - I need to know that my rollup compressed x number of records and took how long.. Etc, Etc, Etc.
    I know the BI Administration Cockpit in 2004s might provide some/most of this information, but it isn't an option right now.
    The way I see it I really only 1 option with a 2nd potential option:
    1. Most likely option is to write a program to go out and collect the statistics for all the processes executing the program on a scheduled basis.
    2.  Modify/Copy the process chain process classes to somehow output the statistics I need.  No idea how I would do this yet.
    So again I am currently down to the process level logs and just don't know how to collect the statistical key figures I need like how many records were loaded, compressed, activated, etc...  I'm thinking of somehow parsing the logs to get the key figures, but that seems like it would be difficult.
    Anyone have any suggestions or ideas how to collect this information so I can report on it?
    I posted this here because I thought the bw abappers would frequent this area.  Also, If anyone thinks this would be better suited in another forum then please suggest.
    Thanks,
    Ken Murray

    Do you subscribe to BWexpert?
    There is an article a person posted specifically on this...
    <a href="http://www.bwexpertonline.com/">BE Expert</a>
    "Identify Failed Data Loads with This Check Tool"
    Thanks.
    /smw
    Message was edited by: Steve Wilson

  • Error occured when starting process chain

    When we want to start a process chain via SAP_BW_ProcessChainRun we get the following error log:
    Failed to start process chain /NSN/C_DSP_TR_GLOBAL_II. No logid was returned by the BW-SCH API.
    com.redwood.scheduler.connector.sap.rfc.connection.exception.SapBapiException: BAPI exception while calling RSPC_API_CHAIN_START: E RSPC 022 Processes with Error
    BAPI exception while calling RSPC_API_CHAIN_START: E RSPC 022 Processes with Error
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.checkBapiReturnCode(ClientConnectionImpl.java:789)
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.handleRscpApiErrors(ClientConnectionImpl.java:808)
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:505)
         at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:296)
         at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:120)
         at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:461)
         at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:289)
         at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:200)
         at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:109)
         at com.redwood.scheduler.connector.sap.rfc.command.impl.BwProcessChainCommand.execute(BwProcessChainCommand.java:98)
         at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:86)
         at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)
         at com.redwood.scheduler.connector.sap.rfc.service.operation.RunJobOperation.doWork(RunJobOperation.java:103)
         at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:38)
         at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)
         at java.lang.Thread.run(Thread.java:579)
    What could be the reason?
    Thanks
    Br
    Günter

    O.K. I can answer the question by myself: Is an authorisation issue. The rfc user who starts the PCs didn't have enough rights.
    Br
    Günter

  • 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 ( termination error : 8) when scheduling Process chain.

    Hi Friends,
                    We are just configuring the BW system 3.5 ( Installing etc etc), I created a Process chain and trying to schedule it, I get the following Error.
    " Job terminated with error code : 8" , when I check the details of the message I see this " Cannot schedule the job with Id : BW REMOTE". Is it something that the basis/ securtity has to set up for the BW guys , to schedule jobs.
    Thanks,

    Hi Smily,
    The possible reason for that error is the User type of the background user. Please check out OSS note 511475 which talks about this problem and possible solution. I have used this earlier.
    You can see this for info on how to make the change:
    /message/685940#685940 [original link is broken]
    Hope this helps...

  • Error Messages when Transport Process Chain to Production

    I am able to transport three related process chain to Q, but failed in Prodtion. Can anyone look at my error messages? Thank you!
    Start of the after-import method RS_RSPC_AFTER_IMPORT for object type(s) RSPC
    Version 'M' of chain USFCMD was saved without checking
    Results of check for process     in chain  :
    Results of check for process     in chain  :
    Results of check for process TRIGGER START_USLDFORECT_MD in chain USFCMD:
    Version 'M' of chain USLDFC was saved without checking
    Results of check for process     in chain  :
    Results of check for process     in chain  :
    Results of check for process TRIGGER START_USLDFORECT in chain USLDFC:
    Version 'M' of chain USLDFORECT was saved without checking
    Results of check for process     in chain  :
    Results of check for process     in chain  :
    Results of check for process ODSACTIVAT USDSOFC_ACTIVATE in chain USLDFORECT:
    Results of check for process ODSACTIVAT USDSOFC_ACTIVATE in chain USLDFORECT:
    Results of check for process TRIGGER START_USLDFORECT_TD in chain USLDFORECT:

    Try to transport the process chain by removing the process chain from schedule.
    Go to Process chain select execution in menu..go for option "Remove from schedule"
    It may help you.
    Regards,
    Srinivas.

Maybe you are looking for