Process Chain Problem - infopackage do not run

Dear coleagues,
I am using BW 7.0, when i execute process chain some info packages of initialization do not start, if execute those infopackages manually they are execute correctly, do you have any idea about what is happening ? Could you help me ?
Regards,
Fabricio

Hi Fabricio,
INIT Infopackage is used to set the delta pointer.
Are you using init infopackage in process chain or delta infopackage?
You should use Delta one.
Thanks,
Vinod

Similar Messages

  • 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

  • The 0co_om_opa_6 ip in the process chains takes long time to run

    Hi experts,
    The 0co_om_opa_6 ip in the process chains takes long time to run around 5 hours in production
    I have checked the note 382329,
    -> where the indexes 1 and 4 are active
    -> index 4 was not "Index does not exist in database system ORACLE"- i have assgined to " Indexes on all database systems and ran the delta load in development system, but guess there are not much data in dev it took 2-1/2 hrs to run as it was taking earlier. so didnt find much differnce in performance.
    As per the note Note 549552 - CO line item extractors: performance, i have checked in the table BWOM_SETTINGS these are the settings that are there in the ECC system.
    -> OLTPSOURCE -  is blank
       PARAM_NAME - OBJSELSIZE
       PARAM_VALUE- is blank
    -> OLTPSOURCE - is blank
       PARAM_NAME - NOTSSELECT
       PARAM_VALUE- is blank
    -> OLTPSOURCE- 0CO_OM_OPA_6
       PARAM_NAME - NOBLOCKING
       PARAM_VALUE- is blank.
    Could you please check if any other settings needs to be done .
    Also for the IP there is selction criteris for FISCALYEAR/PERIOD from 2004-2099, also an inti is done for the same period as a result it becoming difficult for me to load for a single year.
    Please suggest.

    The problem was the index 4 was not active in the database level..it was recommended by the SAP team to activate it in se14..however while doing so we face few issues se14 is a very sensitive transaction should be handled carefully ... it should be activate not created.
    The OBJSELSIZE in the table BWOM_SETTINGS has to be Marked 'X' to improve the quality as well as the indexe 4 should be activate at the abap level i.e in the table COEP -> INDEXES-> INDEX 4 -> Select the  u201Cindex on all database systemu201D in place of u201CNo database indexu201D, once it is activated in the table abap level you can activate the same indexes in the database level.
    Be very carefull while you execute it in se14 best is to use db02 to do the same , basis tend to make less mistake there.
    Thanks Hope this helps ..

  • ABAP program to add in the process chain before the attribute change run

    Hi
    I need a ABAP program to add in the process chain before the attribute change run(process) to avoid the locks, can any one send me the program
    Regards,
    Satish

    I am not sure of any standard program .... but you can write your own... should be a small one..
    you can check if the table RSDMDENQ has entry for your InfoObject... if yes, then its locked.. if not.. its not locked

  • Process chains problems : Working every day with error (red)

    Hi All,
    I have a next question, about process chains problem.
    When I start my process chains immediate, then working without errors,  but I want this process chains work every day and chainged properties, selected date/time and periodicaly (every day) but now it work with error.
    How to I find problems? What are yours offers?
    p.s. I see logs, but every day have diffence between errors.
    Regards,
    Mahir M. Quluzade

    HI,
    just check the time which you have given is OK or is overlappintg with some other job which is locking your table in process chain
    or is colliding with attribute change run
    or it fails because of lack of background processes.
    There could be numerious reasons and you need to analyze the log for this.
    But as you said the job is failing everday for different reasons..try to find the most common errors and try to remove it or mention that here.
    Thanks
    Ajeet

  • How to determine whether process Chain is active or Not

    Hello Experts,
    How to determine whether process Chain is active or Not, because i have large number of PC to activate.

    Hi,
    Please check this program in SE38---- /SSA/BWT
    This program will give you information regarding all your process chains which are active and running based on there timings.
    Hope it helps.
    Regards,
    AL

  • FAIL: process disp+work.EXE Dispatcher not running

    Hi All,
    I've reinstalled OS and installed NW 7.01 ABAP Trial. The installation is fine (no error). At the time I "start application server" through "SAP NW 7.01 ABAP Trial Version => NSP => Start Application Server", it shows the error on command dos window as below:
    ===================================================
    ============== Starting System NSP ================
    ===================================================
    =============== Starting database instance ...
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    The MaxDB Database Starter, Version 7.7.04.23
    Copyright 2000-2008 by SAP AG
    OK
    ============== Starting ABAP instance ...
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    12.10.2008 12:25:40
    Start
    OK
    12.10.2008 12:25:50
    StartWait
    FAIL: process disp+work.EXE Dispatcher not running
    ============== Start operation timed out !
    Press any key to continue . . .
    Please help me out,
    Peerasit

    Clean uninstall and delete 'sapdb; and 'SAP' folders. Then reinstall again.

  • Error in process chain creation :  SET SCREEN not allowed in subscreens

    Hello,
    We are getting an  Error in process chain creation  :  SET SCREEN not allowed in subscreens  SAPRSSM 0100.
    Please give a solution. Thanks in advance.
    RR.

    Just do detail view on in the process chain. It will take you to the error. See the message and then display message. You can know why the message is appearing.

  • How to identify whether that particular process chain is active or not?

    Hi all,
    How to identify whether that particular process chain is active or not ?
    thanxs
    haritha

    If see the process chain then it will not be greyed out if it is active. Or else check in these tables.
    RSPCCHAIN
    RSPCCHAINT
    to check the logs
    RSPCLOGS               
    RSPCPROCESSLOG
    Give the chain name and check in the object version.
    Khaja

  • Execute Process chain after infopackage run for a PC file

    Hello all.
    The scenario I need to solve is the following.
    I have several files to be load to ODS from P users PC. I will do this with an info package. But after this load there are some more process that have to be run whoch are created in a process chain.
    I would like to automate the execution of the precess chain right after the load from PC file is done.
    Any sugestions?
    Thanks and regards,

    Hello Javier Alvarado,
    If you use process chains, the automatically integrated processes are ignored and have to
    be implemented using the process chain. If you schedule a specific process in a chain,
    you support the automatic insertion of additional, relevant standard processes with the
    consideration of such automatic actions.
    For example, if you have selected the processing types Only PSA and Subsequently in
    Data Targets in the InfoPackage from the tabstrip Processing, and you are using this
    InfoPackage in a process chain, then the further processing into the data target does not
    automatically happen. Instead, it only happens if the process Update PSA is scheduled in
    the respective process chain after the loading process. Thus, the process chain
    maintenance supports the automation in this case. In this way, you generate a process
    variant for updating from the PSA in the chain when inserting the loading process with the
    process types Only PSA and Subsequently in Data Targets automatically into a chain.
    Well i am talking about 30B Version
    Regards,
    Mohan.

  • Infopackage in process chain taking long time to run

    HI Experts,
    One of the element (Infopackage) in process chain(Daily process chain) is taking much longer time(6 hr and still runing) as generally it takes 15-20 mins to complete and the status is in yellow and still running in process monitor without giving any clear picture of  error. Manually we are making the staus red and we are updating from PSA and this time it is getting completed in time as specified.
    Flow from PSA to datatarget(DSO) in series
    For last one week we are facing same issue and i would like to mention that we don't have access to SM37,SM12 to look the logs
    and any locks.
    without this i need to investigate what is the root cause for the same.
    with regards,
    murali

    Hi,
    please find the job log.
    Date
    Time
    Message
    MsgID/No./Ty
    13.12.2010
    21:45:30
    Job started
    00
    516
    S
    13.12.2010
    21:45:30
    Step 001 started (program SBIE0001, variant &0000000109368, user ID RFCUSER)
    00
    550
    S
    13.12.2010
    21:45:30
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    R3
    413
    S
    13.12.2010
    21:45:30
    DATASOURCE = 2LIS_17_I3HDR
    R3
    299
    S
    13.12.2010
    21:45:30
    RLOGSYS    = PBACLNT200
    R3
    299
    S
    13.12.2010
    21:45:30
    REQUNR     = REQU_D9GSSV08BTS93Z6Y7XWP1ZEUJ
    R3
    299
    S
    13.12.2010
    21:45:30
    UPDMODE    = D
    R3
    299
    S
    13.12.2010
    21:45:30
    LANGUAGES  = *
    R3
    299
    S
    13.12.2010
    21:45:30
    R8
    048
    S
    13.12.2010
    21:45:30
             Current Values for Selected Profile Parameters               *
    R8
    049
    S
    13.12.2010
    21:45:30
    R8
    048
    S
    13.12.2010
    21:45:30
    abap/heap_area_nondia......... 0                                       *
    R8
    050
    S
    13.12.2010
    21:45:30
    abap/heap_area_total.......... 25500319744                             *
    R8
    050
    S
    13.12.2010
    21:45:30
    abap/heaplimit................ 40000000                                *
    R8
    050
    S
    13.12.2010
    21:45:30
    zcsa/installed_languages...... ED                                      *
    R8
    050
    S
    13.12.2010
    21:45:30
    zcsa/system_language.......... E                                       *
    R8
    050
    S
    13.12.2010
    21:45:30
    ztta/max_memreq_MB............ 2047                                    *
    R8
    050
    S
    13.12.2010
    21:45:30
    ztta/roll_area................ 3000320                                 *
    R8
    050
    S
    13.12.2010
    21:45:30
    ztta/roll_extension........... 2000000000                              *
    R8
    050
    S
    13.12.2010
    21:45:30
    R8
    048
    S
    13.12.2010
    21:45:31
    70 LUWs confirmed and 70 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    RSQU
    036
    S
    13.12.2010
    21:45:33
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 9,895 records
    R3
    407
    S
    13.12.2010
    21:45:33
    Result of customer enhancement: 9,895 records
    R3
    408
    S
    13.12.2010
    21:45:33
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 9,895 records
    R3
    407
    S
    13.12.2010
    21:45:33
    Result of customer enhancement: 9,895 records
    R3
    408
    S
    13.12.2010
    21:45:33
    PSA=0 USING & STARTING SAPI SCHEDULER
    R3
    299
    S
    13.12.2010
    21:45:33
    Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
    R3
    409
    S
    13.12.2010
    21:45:34
    IDOC: Info IDoc 2, IDoc No. 5136702, Duration 00:00:00
    R3
    088
    S
    13.12.2010
    21:45:34
    IDoc: Start = 13.12.2010 21:45:30, End = 13.12.2010 21:45:30
    R3
    089
    S
    13.12.2010
    21:45:35
    Asynchronous transmission of info IDoc 3 in task 0003 (1 parallel tasks)
    R3
    413
    S
    13.12.2010
    21:45:35
    Altogether, 0 records were filtered out through selection conditions
    RSQU
    037
    S
    13.12.2010
    21:45:35
    IDOC: Info IDoc 3, IDoc No. 5136703, Duration 00:00:00
    R3
    088
    S
    13.12.2010
    21:45:35
    IDoc: Start = 13.12.2010 21:45:35, End = 13.12.2010 21:45:35
    R3
    089
    S
    13.12.2010
    21:55:37
    tRFC: Data Package = 1, TID = 0AF0842B00C84D0694000F00, Duration = 00:10:03, ARFCSTATE = SYSFAIL
    R3
    038
    S
    13.12.2010
    21:55:37
    tRFC: Start = 13.12.2010 21:45:34, End = 13.12.2010 21:55:37
    R3
    039
    S
    13.12.2010
    21:55:37
    Synchronized transmission of info IDoc 4 (0 parallel tasks)
    R3
    414
    S
    13.12.2010
    21:55:37
    IDOC: Info IDoc 4, IDoc No. 5136717, Duration 00:00:00
    R3
    088
    S
    13.12.2010
    21:55:37
    IDoc: Start = 13.12.2010 21:55:37, End = 13.12.2010 21:55:37
    R3
    089
    S
    13.12.2010
    21:55:37
    Job finished
    00
    517
    S

  • Process chain--failed infopackage--urgent....

    Hi Experts,
    can anyone tell me why the process chain when triggered has successfully started but the first infopackages after the start varient did not sucessfully run.
    the infopackages show in the process chain in yellow status as if the data loadings are taking place but when u go to the monitor screen the data loadings will not be taking place. if you manually trigger the infopackage then only the data loadings are taking place.
    what could be the reason and how to make the process chain run successfully after it gets triggered.
    i have deleted all the released jobs for all the processes in the process chain and triggered manually that chain but it is of no use. still the same problem is persisting, is there anything on BW part that we could or is it Basis work that needs to be done for the solution of this type of problem.

    Hi Experts,
    can anyone tell me why the process chain when triggered has successfully started but the first infopackages after the start varient did not sucessfully run.
    the infopackages show in the process chain in yellow status as if the data loadings are taking place but when u go to the monitor screen the data loadings will not be taking place. if you manually trigger the infopackage then only the data loadings are taking place.
    what could be the reason and how to make the process chain run successfully after it gets triggered.
    i have deleted all the released jobs for all the processes in the process chain and triggered manually that chain but it is of no use. still the same problem is persisting, is there anything on BW part that we could or is it Basis work that needs to be done for the solution of this type of problem.

  • Process Chain Problem - RSPCPROCESSLOG

    Hi,
    we have just upgraded from BW3.5 to BI7(patch 11) and we are currently experiencing a sporadic problem when executing process chains. 
    In some loading chains, even though the previous infopackage has finished successfully, the next package does not start.  The entries for the previous processes in table RSPCPROCESSLOG have field ACTUAL_STATE = 'F' (Completed), whereas normally the completed loads have status = 'G'.  This causes our process chains to get stuck and we can waste quite a lot of loading time due to this.
    Does anyone know why these (apparently) successful loads would be stored in RSPCPROCESSLOG with status = 'F'?
    I noticed in another thread that there is a function module (RSPC_PROCESS_FINISH) which can change the status, but as our chains are not constantly monitored we can lose a considerable amount of time before this function module can be executed.
    Also, I found OSS note 1002791 which looks relevant, although when I look at the correction instructions, it refers to TYPE = DTP_LOAD in table RSPCPROCESSLOG, whereas our problem is occurring with TYPE = 'LOADING', because we have not yet migrated from BW3.5 functionality.
    Any suggestions would be greatfully received.
    Thanks.
    Trevor Cowan.

    Really don't know about when the status gets set.  Have to look at that a bit.
    I do know that some changes were made in 7.0 to some things like change runs and I think other processes to use background processes instead of dialog.  Not saying this is your problem, but still something to look at.  Sometimes if you look at jobs in SM37 and if you see that you had jobs with delays before they actually started, that can suggest insufficent background processes. 
    Can you adjust your chains or timings so that not as many chains try to run at the same time or reduce the number of subchains that are triggered at the same time.  There is an OSS Note that talks about how many background processes you need to have free for process chains to work proprely - try searching for that.

  • Process Chain takes alonf time to run

    Hello All,
    We have a process chain which loads data for texts, attributes etc.
    On certain days the process chain will run extremely fast and maybe take a couple of hours, other days the same process chain may take 24 hours to run.  It appears to get stuck when extracting the data from our source system.
    Is there any reason for these strange performance issues and does any body else have the same problem?  Is there anything that can be done about it?
    Thanks,
    Nick.

    Hi Nick,
    This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
    Whenever we are loading the Master Data for the first time, it creates SID’s. If system is unable to create SID’s for the records in the Data packet, we can get this error message.
    If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
    Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
    If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
    It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
    It is a system error which can be seen under the “Status” tab in the Job Over View.
    Cheers
    Raj

  • Process chains get an error when run analysis process

    When my PRD system‘s process chains run analysisi process, I  gets below error message:
    Error occurred when starting the parser: Error when opening an RFC connection (FUNCTION: 'R
    Message no. BRAINOLAPAPI011
    Diagnosis
    Failed to start the MDX parser.
    System Response
    Error when opening an RFC connection (FUNCTION: 'R
    Procedure
    Check the Sys Log in Transaction SM21 and test the TCP-IP connection MDX_PARSER in Transaction SM59.
    It's OK when i test the TCP-IP connection MDX_PARSER in Transaction SM59.
    The Sys Log in Transaction SM21(error part):
    M Wed Mar 19 09:22:50 2014
    M  *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35, r, ..) returned -14 [thxxexec.c
    M  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
    A  RFC 1878  CONVID 18933904
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    A  RFC> ABAP Programm: SAPLSTPA (Transaction: )
    A  RFC> User: JY-LKZ (Client: 900)
    A  RFC> Destination: CALLTP_AIX (handle: 8, DtConId: 530F4E5C30AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
    A  RFC SERVER> RFC Server Session (handle: 1, 68443927, {5328109B-5F5D-12A0-E100-8000C0A8642F})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
    A  RFC SERVER> Called function module: TMS_CI_START_SERVICE
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
    FUNCTION: 'RfcExecProgramKernel'
    RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35
    [abrfcio.c    9213]
    A  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE
    M
    M Wed Mar 19 09:23:15 2014
    M  *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61, r, ..) returned -14 [thxxexec.c
    M  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
    A  RFC 1878  CONVID 18968493
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    A  RFC> ABAP Programm: SAPLSTPA (Transaction: )
    A  RFC> User: TMSADM (Client: 000)
    A  RFC> Destination: CALLTP_AIX (handle: 3, DtConId: 530F4E7830AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
    A  RFC SERVER> RFC Server Session (handle: 1, 70212851, {53281195-8F75-0F10-E100-8000C0A8642F})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
    A  RFC SERVER> Called function module: TMS_CI_START_SERVICE
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
    FUNCTION: 'RfcExecProgramKernel'
    RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61
    [abrfcio.c    9213]
    A  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE.
    ps.
    1、IT's everything ok in the development system.
    2、It’s ok when i repeat this analysis process .
    3、It’s ok when i run this analysis process in analysis process designer.
    4、Attachment is the sys log in sm21.
    Thanks everyone.

    Hi Vignesh.B,
    Yes,it's not user's problem . But i don't  think it APD's problem .Cause all APD has the same problem and .
    Below is one of APD souce and target :
    Hope this information  is useful .
    Regards,
    Lian

Maybe you are looking for