Initial customizing loads (DNL_*) causing short dumps in R/3

Hi,
I'm trying to run the initail loads for the DNL_* customizing objects.  When I start a load in R3AS and check the status in R3AM1, it shows "Running".  In the CRM oubound queue (SMQ1), there is an entry for the load with status SYSFAIL.  The detailed status message is "The current application triggered a termination with a short dump". 
The short dump in R/3 shows an error "No external system (such as CRM) connected" which occurs in function module CRM_FIRST_CALL_OPERATIONS.  Looking at the code, there seems to be a problem with the CRMRFCPAR table.  I had only one record in this table for object CUSTOMER_MAIN, so I tried adding a record with Object Name "*" and Load Type "I", but this had no effect. 
What is the proper configuration of table CRMRFCPAR for customizing loads?  Is it possible that this error is related to some other config or a problem with the RFC connection?  These loads work fine in our quality system which is configured the same as production (as far as I can tell).
Thanks.
Martin

hi,
Maintaining Table CRMRFCPAR (SAP R/3)
The parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.
You can send data to a certain consumer only in an initial download and not in a delta download by making the appropriate specifications for the data exchange.
User- That uses the OLTP plug-in functions as data receivers
Object name -Object name
Destination -Specifies the destination of the CRM server
Load Type -Restricts CRMRFCPAR entries to the initial (I) or delta (D) download.
Out Queue - Name RFC outbound queue
In Queue -Name RFC inbound queue
BAPI name
INFO -Information/Comments
InQueue flag- Controls whether qRFC inbound queues are used on the CRM server
Send XML -XML supports (Should data be sent in XML format?)
Stop data -Causes the OLTP System to place data into the outbound queue.
Regards
sri

Similar Messages

  • HP OV Operations integration is causing short dumps RFC_CONVERSION_FIELD

    Application Integration to monitor CCMS 4x using r3monal process from HP Open View Operations is causing short dumps on R/3 Database and Application Server.
    DUMP INFO:
    Conversion error "ab_rfcImplode" from character set 4102 to character set 1100.
    When executing a remote function call a conversion error occurred. This
    occurred when receiving or sending the data. The conversion error can
    only appear, when the data is transferred from a Unicode system to a
    non-Unicode system.
    Internal SAP notes
    The termination occurred in the function "ab_rfcImplode" of the SAP
    Basis System, specifically in line 7788 of the module
    "//bas/640_REL/src/krn/rfc/abrfcimp.c#25".
    The internal operation just processed is "FUNC".
    The internal session was started at 20061229000713.
      CLUDE INCL_INSTALLATION_ERROR

    Dear Pallavi,
    Very useful post!
    I am looking for similar accelerators for
    Software Inventory Accelerator
    Hardware Inventory Accelerator
    Interfaces Inventory
    Customization Assessment Accelerator
    Sizing Tool
    Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
    Request help on such accelerators... Any clues?
    Any reply, help is highly appreciated.
    Regards
    Manish Madhav

  • Urgent: Data Loading error(Load failed with Short Dump) caller 70 missing

    Hi please go through the error occured.
    <b>"Request is still running.
    Diagnosis:
    No error could be found. The current process has probably not finished yet.
    System Response:
    The ALE Inbox of the SAP BW is identical to ALE Outbox of the source System and /or the maximum wait time for this request has not yet run out and/or the batch job in the cource system has not ended.
    current status
    in the source sytem."</b>
    Update mode: Full, processing Online.
    I think we processed the infopackage in the online. if we process it in the back ground then we won't face any problem. Singal turns to Red.
    Please guide us. we need to load it immidiately.
    Thanks in advance.
    Regards,
    Nagesh.
    Message was edited by: Nagesh Ganisetti
    Message was edited by: Nagesh Ganisetti

    Hi Friends,
       at last the load has Terminated with Short Dump. Can any one guide me how can i reslove this. we could see the data in PSA.
    i'm sending the part of the short dump.
    Too many parameters specified with PERFORM.                                                                               
    What happened?                                                                               
    In a subroutine call, there were more parameters than in the  routinedefinition.                                                                         
    Error in ABAP application program.                          
    The current ABAP program "GP3KGSUXARXPB2F9YCR4B3MFPT6 " had to be terminated because one of statements could not be executed.                    
    This is probably due to an error in the ABAP program.                       
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                    
    and make a note of the actions and input that caused the                                    
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                              
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer                    
    termination messages, especially those beyond their normal deletion                        
    date.                           
    is especially useful if you want to keep a particular message.                              
    Error analysis                                                                               
    A PERFORM was used to call the routine "VALUE_TO_SID_CONVERT_DB" of the program             
    "GP3KGSUXARXPB2F9YCR4B3MFPT6 ".                                                            
    This routine contains exactly 7 formal parameters, but the current                       
    call contains 8 actual parameters.                                                          
    parameters.                                                     
    How to correct the error                                         
    Correct the PERFORM call. You can find out where the call occurs in the section "Active calls / events".
    You may able to find an interim solution to the problem                                     
    in the SAP note system. If you have access to the note system yourself,                     
    use the following search criteria:     
    Please guide me.
    Regards,
    Nagesh.
    Message was edited by: Nagesh Ganisetti

  • WBS Conversion FM using RFC Causing Short Dumps

    Hello,
    I have been trying to validate WBS element entries by using an RFC call to a FM on the back-end.  However, I keep getting short dumps on the back-end system with 'Statement "MESSAGE E" is not allowed in this form.' message.  The custom back-end FM calls one of the CPJN FMs like CONVERSION_EXIT* that deal with WBS elements.
    So, I tried changing the custom FM to use the data element that does a the conversion instead of the FM. Now, I get a short dumps on the front-end with CALL_FUNCTION_REMOTE_ERROR with 'Key does not correspond to mask: B/0000-XXXXXXX.0.0.0' message.
    Has anyone been successful without duplicating the CONVERSION_EXIT* FMs in order to validate a WBS element entry remotely?
    Thank you in advance for any assistance.
    Regards, Dean.

    Hello Dean
    On ERP 6.0 (IDES) there is the RFC-enabled fm /SPE/WBS_ELEM_CONV_INT_EXT available.
    If you feed the fm with an external ID it tries to convert it into the corresponding internal ID and vice versa. Perhaps this fm might be useful for you.
    Probably the BAPI BAPI_PROJECT_EXISTENCECHECK is more useful (can be feed either with internal or external ID).
    Regards
      Uwe

  • What is the maximum number of recursive call as i think it is causing short dump

    Hi All,
    This may not have a specific answer i suppose but approx is also fine. There was a short dump in production ( the background job failed , an is failing each day since a week now ). I was analysing it  what i found was the cause for there was numerous call to the same routine within it self ( recursion ). The exact number i dont have but they were atleast more the 200.
    The error message which i get is :
    Are there any solution regarding
    Category          
    Resource Shortage
    Runtime Errors    
    TSV_TNEW_PAGE_ALLOC_FAILED
    Short text
        No more storage space available for extending an internal table.
    What happened?
        You attempted to extend an internal table, but the required space was
        not available.
    it would be great if we know the max numbers of an recursive call so that i can do the necessary changes or if some 1 has any other alternative solution pls. help.
    Regards,
    Dhruvin
    P.s : it's a productive environment issue.

    The dump is not caused by depth of recursion but rather memory limits being exceeded by your process, these are controlled by profile parameters (System administrator stuff) and "normally" (unless changed to other values) allow up to 4 GB of memory usage (mostly by internal tables). You can quickly check the current memory consumption of your active process via SM50.
    Make sure that the routine that is called recursively (or other relevant parts of your process) free up memory by using CLEAR and FREE statements for internal tables that are no longer needed.
    If data is being selected from the database also look into block processing via the PACKAGE SIZE option.
    Thomas

  • How to find which Badi Implementation is causing Short Dump

    Hi Experts,
    We are getting short dump on IW32 transaction when the users hit SAVE button.
    The Dump Details:
    Runtime Errors SYNTAX_ERROR
    Short text
    Syntax error in program "WORKORDER_UPDATE==============CP ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_WORKORDER_UPDATE========CP" had
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "WORKORDER_UPDATE==============CP " in include
    "WORKORDER_UPDATE==============CM000 " in
    line 12:
    "The specified type cannot be converted into the target variable
    The current ABAP program "CL_EX_WORKORDER_UPDATE========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
    The following syntax error was found in the program
    WORKORDER_UPDATE==============CP :
    "The specified type cannot be converted into the target variables."
    Information on where terminated
    Termination occurred in the ABAP program "CL_EX_WORKORDER_UPDATE========CP" -
    in "IF_EX_WORKORDER_UPDATE~AT_SAVE".
    The main program was "SAPLCOIH ".
    After going through the dump analysis, I found that there are around 25 BADI Implementations got created on Enhancement Spot "WORKORDER_UPDATE".
    How to find out which BADI Implementations is causing this dump?
    Please let me know.
    Thanks.
    Edited by: ravi kumar on Feb 22, 2011 1:12 PM

    Yes, I tried the Active Calls Stack also. The Short Dump is occuring exactly at the line :-
    method IF_EX_WORKORDER_UPDATE~AT_SAVE.
    in Class:-
    CL_EX_WORKORDER_UPDATE
    I was informedby the user that this is working perfectly fine in DEV System. The Short Dump is occuring in SBX System.
    When I executed the Class "CL_EX_WORKORDER_UPDATE" and Method "IF_EX_WORKORDER_UPDATE~AT_SAVE" via SE24 in SBX, I got the same dump. However it worked fine in DEV System.
    I am wondering if the issue is with the Standard Program itself?
    Any ideas?
    Thanks a lot again.
    Another thing is: It is short dumping even before calling any of the BADI Implementations.
    Wanted to give some more info on this: I put a break point in Function "CO_ZV_ORDER_POST" after the CALL FUNCTION 'CO_BADI_GET_BUSINESS_ADD_IN'.
    And the program dumps right after that when it calls the: CALL METHOD lp_badi_if->at_save.
    Thanks.
    Edited by: ravi kumar on Feb 22, 2011 1:51 PM
    Edited by: ravi kumar on Feb 22, 2011 2:11 PM

  • VOFM on data transfer: shipments causing short dump

    I created two new requirements as copies of routine 008 and 012 into 908 and 912. Both routines are activated and I even ran the RV80HGEN.
    Although code is the same as the original routines, short dump is being produced. (The original code was unmodified to test that the new routine would work the same).
    I also noticed that if I use the 'where-used', the system comes back to say it is not found in selected search area, but otherwise would be.
    The include RV56CNNN has the two includes listed in it and is also active.
    What is missing?

    Hello,
    I removed this from being a thread and closed it, but it apparently is still showing somewhere.
    I was able to figure it out. The internal table in the SAP logic was i_, but when the custom requirement was created, it is c_ so that is why it wouldn't work. It did activate regardless but still had other issues. Once I updated the internal table reference, it was fine.
    Thanks to all who responded. Unfortuntaley points may not be awarded since it was removed early on from being a thread.

  • Customized Table is giving Short Dump .Want to extract data in Production S

    Hi ,
    I have a problem in customized table .Table is giving a data after trying to access 185th record.There is some problem in the table.But I want to pull out all the data from the table..Is it possible to download it .Pls suggest..
    Even If I put one select query also it is givning dump..
    Pls suggest some other technique to download it..
    Regards
    Arun.P

    Hi Arun,
    Where there you are using WHERE condition  in select statement while fetching the records?
    if yes means check for the fields are primary key, available in WHERE condition, or else create secondary index for those
    non Primary key Fields in WHERE condition.
    This may help you.
    Thanks and Regards,
    Prakash.K

  • Error "ERROR_PERIOD_VERSION" when loading DTP  - Abap short dump

    Hi,
    I got this Error when loading with DTP. it occured in the transformation end routine.
    I have this function module in my End routine. * REBW_FIRST_DAY_OF_PERIOD_GET*
    Information on where terminated
        Termination occurred in the ABAP program "SAPLREBW_UTIL" - in
         "REBW_FIRST_DAY_OF_PERIOD_GET".
        The main program was "RSAWBN_START ".
        In the source code you have the termination point in line 41
        of the (Include) program "LREBW_UTILU03".
    Source Code Extract
    Line  SourceCde
       11 *"     REFERENCE(E_SPERIOD) TYPE  XFELD
       12 *"  EXCEPTIONS
       13 *"      ERROR_PERIOD
       14 *"      ERROR_PERIOD_VERSION
       15 *"      FIRSTDAY_NOT_DEFINED
       16 *"      PERIOD_NOT_DEFINED
       17 *"----
       18 DATA:
       19     DATUM(8),
       20     TAG(2),
       21     IMONAT     TYPE I,
       22     JAHR       type rsfiscyear,
       23     DATE       type rscalday,
       24     PERZAHL(4) TYPE N,
       25     IRC(1)     TYPE N,
       26     ls_t009    like t009,
       27     ls_t009y   like t009y,
       28     ls_t009b   like t009b.
       29
       30 *
       31 * Version der Periodenermittlung nachlesen
       32 *
       33   IF I_FISCVAR NE ls_T009-PERIV.
       34     SELECT SINGLE * FROM  T009
       35                     into ls_t009
       36                     WHERE PERIV = I_fiscvar.
       37     IF SY-SUBRC NE 0.
       38 *
       39 *     In Tabelle $ fehlt der Eintrag $
       40 *
    >>>>>       RAISE ERROR_PERIOD_VERSION.
       42     ENDIF.
       43   ENDIF.
       44 *
       45 * Periode überprüfen
       46 *
       47   PERZAHL = ls_T009-ANZBP + ls_T009-ANZSP.
       48   IF I_FISCPER < 1 OR I_FISCPER > PERZAHL.
       49 *
    does any knows how I can resolve it.
    thanks

    check table t009, it seems you have some entries missing (based on fiscal variant)
    you can solve this, by going to the source system tree, right-click on your source system and choose transfer global settings.
    you can transfer all settings now...
    M.

  • OOPS ALV - Short dump

    Hi,
    While i create a report with grid display with oops ALV using custom container, its giving short dump..
    DUMP: CNTL ERROR ouccured..

    Hi Phani,
    Make sure you have done below things correctly.
    While creating a container control in SE51, make sure you have given a name to it in the attributes & use the same name in the ABAP code with data declaration as below:
    Suppose you have named the container control in SE51 as CC_CONTAINER
    DATA :
      g_Container TYPE scrfname VALUE 'CC_CONTAINER',
    g_Custom_Container TYPE REF TO CL_GUI_CUSTOM_CONTAINER
    g_Grid TYPE REF TO CL_GUI_ALV_GRID.
    Also first create a CONTAINER object with reference to container name in the screen & then  Create GRID object with reference to parent name
    IF g_Custom_Container IS INITIAL.
        CREATE OBJECT g_Custom_Container EXPORTING CONTAINER_NAME = g_Container.
        CREATE OBJECT g_Grid EXPORTING I_PARENT = g_Custom_Container.
    & Finally called method Set table for display for Grid as below :
    " SET_TABLE_FOR_FIRST_DISPLAY
        CALL METHOD g_Grid->SET_TABLE_FOR_FIRST_DISPLAY
          EXPORTING
    Also make sure that you have activated the code in PBO & PAI in SE51.
    With these it shouldnt give the above error.
    Hope this helps.
    Regards
    Abhii

  • ABAP Short Dump - COMPUTE_BCD_OVERFLOW - CX_SY_ARITHMETIC_OVERFLOW

    Runtime errors      COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    I want to move Currency variable with 4 decimals to another currency variable with 2 decimals. Please advice me with a suitable solution without causing short dump.
    Appreciate Your Help in Advance.
    Thanks.
    Kannan.

    SAP catch the exception like this :
    CATCH SYSTEM-EXCEPTIONS conversion_errors = 1
                                        arithmetic_errors = 5.
                  xkwert = xkomv-kwert * 1000 * xkomv-kpein / komp-mgame.
                  xkomv-kbetr = xkwert.
                ENDCATCH.
                IF sy-subrc = 1 OR sy-subrc = 5.
                  xkomv-kbetr = 0.
                  xkomv-fxmsg = '802'.
                  komp-fxmsg  = '802'.
                ENDIF.

  • Short dump in debug mode

    Hi All,
    We have recently upgraded our server from SAP R/3 4.6b to ECC 5.0. Whenever we are debugging any program(Both standard and Z-programs) getting short dump
    in the select and endselect statements. This is happening only when we are going on DEBUG MODE only Appreciate any lights on this issue.(All programs are Unicode enabled).
    Regards,
    Ameer.

    hi
    your problem will solve if you put the break point after <b>ENDSELECT</b> statement. let the cursor not go inside the select-endselect statement. it causes short-dump.
    thx
    murthy

  • Short dump with decimal issue

    Now I want to get total weight of the material as weight * quantity. When I doing this process the program short dump.
    If my user setting in su01 is 1,234,567.89 it will work normally, but if I changed my user setting to 1.234.567,89 it will get weight like 6,55 which cause short dump in total weight get. Please help me for solution that no mater user setting is dot or comma it will work successfully. thanks.

    I think the problem lies in fact that you are treating this variable as character one (of type c or string ) . This is not correct. You should use only packed numbers (of type p ) for calculation.
    The user settings has nothing to do with the calculation. These are purely for displaying data, not for calculating them. So what you need is something like
    data: weight type p decimals 2 value '1234567.89',
             quantity type i value 3,
             result(10) type p decimals 2.  
    result = weight * quantity. "the value stored in variable has form 3703703.67
    "only when you display your data it will receive the format of user settings
    write: weight,  "displayed as 1,234,567.89 or 1.234.567,89 -> depending on the settings
              result.    "displayed as 3,703,703.67 or 3.703.703,67 -> depending on the settings
    Regards
    Marcin

  • Regarding Short Dump While loading data from DB Connect

    Dear All,
    We are having an issue of getting short dump while loading data from DB Connect to BW. We were able to load the data into BW Dev using the same data source without any problem. Whereas in Production, I am getting the following error:
    Runtime Error          PERFORM_CONFLICT_TAB_TYPE  
    Except.                   CX_SY_DYN_CALL_ILLEGAL_TYPE
    What could be the reason for the error that I am getting

    hi,
    Refer Note 707986 - Writing in trans. InfoCubes: PERFORM_CONFLICT_TAB_TYPE
    Summary
    Symptom
    When data is written to a transactional InfoCube, the termination PERFORM_CONFLICT_TAB_TYPE occurs. The short dump lists the following reasons for the termination:
    ("X") The row types of the two tables are incompatible.
    ("X") The table keys of the two tables do not correspond.
    Other terms
    transactional InfoCube, SEM, BPS, BPS0, APO
    Reason and Prerequisites
    The error is caused by an intensified type check in the ABAP runtime environment.
    Solution
    Workaround for BW 3.0B (SP16-19), BW 3.1 (SP10-13)
    Apply the attached correction instructions.
    BW 3.0B
    Import Support Package 20 for 3.0B (BW3.0B Patch20 or SAPKW30B20) into your BW system. The Support Package is available oncenote 0647752 with the short text "SAPBWNews BW3.0B Support Package 20", which describes this Support Package in more detail, has been released for customers.
    BW 3.10 Content
    Import Support Package 14 for 3.10 (BW3. 10 Patch14 or SAPKW31014) into your BW system. The Support Package is available once note 0601051 with the short text "SAPBWNews BW 3.1 Content Support Package 14" has been released for customers.
    BW3.50
    Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available once note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, has been released for customers.
    The notes specified may already be available to provide advance information before the Support Package is released. However, in this case, the short text still contains the term "Preliminary version" in this case.
    Header Data
    Release Status: Released for Customer
    Released on: 18.02.2004 08:11:39
    Priority: Correction with medium priority
    Category: Program error
    Primary Component: BW-BEX-OT-DBIF Interface to Database
    Secondary Components: FIN-SEM-BPS Business Planning and Simulation
    Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    SAP_BW 30 30B 30B
    SAP_BW 310 310 310
    SAP_BW 35 350 350
    Support Packages
    Support
    Packages Release Package
    Name
    SAP_BW_VIRTUAL_COMP 30B SAPK-30B20INVCBWTECH
    Related Notes
    693363 - SAPBWNews BW SP03 NW'04 Stack 03 RIN
    647752 - SAPBWNews BW 3.0B Support Package 20
    601051 - SAPBWNews BW 3.1 Content Support Package 14
    Corrections Instructions
    Correction
    Instruction Valid
    from Valid
    to Software
    Component Ref.
    Correction Last
    Modifcation
    301776 30B 350 SAP_BW J19K013852 18.02.2004 08:03:33
    Attributes
    Attribute Value
    weitere Komponenten 0000031199
    Thanks
    (Activate ODS/Cube and Transfer rules again..)

  • Load getting failed due to short dump

    Hi All,
    Process Chain is getting failed due to following short dump Include Report LFZI_CA_PCA_DERIVATIONSU37 not found. Please suggest on rectifying this dump. Its a delta load.
    Regards,
    Asim

    Hi All
    As requested please find details short dump below. And datasource name is this GECPC_GLPCP and its extractor is ZPCC_V_GLPCP.
    Short text
       Syntax error in program "SAPLZFI_CA_PCA_DERIVATIONS ".
    hat happened?
       Error in the ABAP Application Program
       The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
        because it has
       come across a statement that unfortunately cannot be executed.
       The following syntax error occurred in program "SAPLZFI_CA_PCA_DERIVATIONS " in
        include "LZFI_CA_PCA_DERIVATIONSUXX " in
       line 77:
       "INCLUDE report "LZFI_CA_PCA_DERIVATIONSU37" not found"
       The include has been created and last changed by:
       Created by: "SAP* "
       Last changed by: "SAP* "
       Error in the ABAP Application Program
       The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
        because it has
       come across a statement that unfortunately cannot be executed.
    What can you do?
        Please eliminate the error by performing a syntax check
        (or an extended program check) on the program "SAPLZFI_CA
        You can also perform the syntax check from the ABAP Edito
        If the problem persists, proceed as follows:
        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 lo
        at and manage termination messages, and you can also
       keep them for a long time.
    Error analysis
        The following syntax error was
        "INCLUDE report "LZFI_CA_PCA_DE
    How to correct the error
        Probably the only way to elimin
        If you cannot solve the problem
        notification to SAP, include th
        1. The description of the curre
           To save the description, cho
        (Unconverted)".
        2. Corresponding system log
    Display the system log by callin
    Restrict the time interval to 10
    ter the short dump. Then choose "
    nconverted)".
    If the problem occurs in a probl
    ogram: The source code of the pro
    In the editor, choose "Utilities
    ilities->Upload/Download->Downloa
    Details about the conditions und
    tions and input led to the error.
    Information on where terminated
        Termination occurred in the ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" - in
         "START_ROUTINE".
        The main program was "RSBATCH_EXECUTE_PROZESS ".
        In the source code you have the termination point in line 102
        of the (Include) program "ZFICA_DERIVE_PCA_OBJECTS_S".
        The program "GP9IQHCDEPFH201E24O25IAYXXW" was started as a background job.
        Job Name....... "BIDTPR_6726959_1"
        Job Initiator.. "ALEREMOTE"
        Job Number..... 17271800
    Line  SourceCde
       72 ASSIGN 'L_DERIVE_CHRT_ACCTS-UPD_CHRT_AC
       73 assign (<derive_chrt_accts_field>) to
       74 IF <derive_chrt_accts> IS ASSIGNED.
       75   zzi_attributes_upd-chrt_accts_upd = '
       76 ENDIF.
       77 zzi_attributes_upd-/bic/gactivity_upd
       78 zzi_attributes_upd-/bic/gfactv_upd
       79 zzi_attributes_upd-/bic/gglobacct_upd
       80 zzi_attributes_upd-/bic/ggforacc_upd
       81 zzi_attributes_upd-/bic/ggrracc_upd
       82 zzi_attributes_upd-/bic/ggra_code_upd
       83 zzi_attributes_upd-/bic/gsegmtion_upd
       84 zzi_attributes_upd-/bic/ggaapflg_upd
       85 zzi_attributes_upd-/bic/gsub_item_upd
       86 zzi_attributes_upd-/bic/gsegmnt_upd
       87 zzi_attributes_upd-/bic/gacctgrp_upd
       88 zzi_attributes_upd-comp_code_details_up
       89 zzi_attributes_upd-gbfi0600_upd
       90 zzi_attributes_upd-/bic/zaccsuf_upd
       91 zzi_attributes_upd-/bic/gconunit_upd
       92 zzi_attributes_upd-/bic/gtpunit_upd
       93 *--------------------------------------
       94 * Store a copy of the source fields if
       95 *--------------------------------------
       96 MOVE-CORRESPONDING <source_fields> TO z
       97 CLEAR zze_attributes.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          04.08.2014 17:27:39
        98 *----------------------------------------------------------------------*
        99 * Derive all PCA fields for reporting
       100 *----------------------------------------------------------------------*
       101
    >>>>> CALL FUNCTION 'ZFI_CA_DERIVE_PCA_ATTRIBUTESII'
       103   EXPORTING
       104     i_zfi_ca_pca_attributes     = zzi_attributes
       105     i_zfi_ca_pca_attributes_upd = zzi_attributes_upd
       106     msgty                       = 'I'
       107     recno                       = <source_fields>-record
       108   IMPORTING
       109     e_zfi_ca_pca_attributes     = zze_attributes
       110   TABLES
       111     monitor_recno               = lt_monitor_recno.
       112
       113 *----------------------------------------------------------------------*
       114 * On the recurrsive load delete entries where the data is the same
       115 *----------------------------------------------------------------------*
       116 IF zzg_realignment_run = 'X'.
       117   IF  zzi_attributes = zze_attributes.
       118     DELETE  source_package INDEX la_tabix.
       119   ELSE.
       120     MOVE-CORRESPONDING zze_attributes TO <source_fields>.
       121   ENDIF.
    SY-SUBRC 0
    SY-INDEX 3
    SY-TABIX 1
    SY-DBCNT 10
    SY-FDPOS 0
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE Execute Batch Proces
    SY-MSGTY E
    SY-MSGID R7
    SY-MSGNO 057
    SY-MSGV1 ZBAL_LC
    SY-MSGV2 A
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20140804
    SY-UZEIT 172720
    SY-XPROG SAPCNVE
    SY-XFORM CONVERSION_EXIT
    No.   Ty.          Program                             Include                             Line
          Name
        8 FUNCTION     GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
          START_ROUTINE
        7 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
          LCL_TRANSFORM=>START_ROUTINE
        6 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         GP9IQHCDEPFH201E24O25IAYXXW          1299
          LCL_TRANSFORM=>EXECUTE
        5 METHOD       CL_RSTRAN_TRFN_CMD============CP    CL_RSTRAN_TRFN_CMD============CM005    70
          CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
        4 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM00Q    93
          CL_RSBK_PROCESS=>PROCESS_REQUEST
       3 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM002    13
          CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
        2 FUNCTION     SAPLRSBATCH                         LRSBATCHU13                           437
          RSBATCH_EXECUTE_PROCESS
        1 EVENT        RSBATCH_EXECUTE_PROZESS             RSBATCH_EXECUTE_PROZESS               374
          START-OF-SELECTION
    REQUEST
        DTPR_1FR9TKO2U6M616ATG9C2EYKRH
        455553453544353433345434345454
        4402F16294BF256D61614793259B28
        000000000000000000000000000000
        000000000000000000000000000000
    DATAPACKID
        000001
        333333
        000001
        000000
        000000
    MONITOR
        Table[initial]
    SOURCE_PACKAGE
        3000000001012P2013K4AU0ACD 2013005          00                                               0
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013001000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013002000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013003000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013004000000000000000000000000000000000000000000000000000000000000
      00000000000000000000000000000000000
      00000000000000000000000000000000000
      33333333333335333343453444233333332
      300000000101202013B4150134020130050
      00000000000000000000000000000000000
      00000000000000000000000000000000000
      Table IT_110723[600000x1144]
      {A:114*\TYPE=%_T00003S00000115O0000
      Table reference: 3570
      TABH+  0(20) = 90A161080000000060C1
      TABH+ 20(20) = F20D000083B00100C027
      TABH+ 40(16) = 03730000242D00000400
      store        = 0x90A1610800000000
      ext1         = 0x60C1190C00000000
      shmId        = 0     (0x00000000)
      id           = 3570  (0xF20D0000)
      label        = 110723 (0x83B00100)
      fill         = 600000 (0xC0270900)
      leng         = 1144  (0x78040000)
      loop         = 128   (0x80000000)
      xtyp         = ROL.115.11556
      occu         = 4     (0x04000000)
      accKind      = 1     (ItAccessStand
      idxKind      = 0     (ItIndexNone)
      uniKind      = 2     (ItUniNo)
      keyKind      = 1     (default)
      cmpMode      = 8     (cmpManyEq)
      occu0        = 1
      stMode       = 0
      groupCntl    = 0
      rfc          = 0
      unShareable  = 0
      mightBeShared = 1
      sharedWithShmTab = 0
      isShmLockId  = 0
      isUsed       = 1
      isCtfyAble   = 1
      hasScndKeys  = 0
      hasRowId     = 0
      scndKeysOutdated = 0
      scndUniKeysOutdated = 0
      ----- Shareable Table Header Data -----
      tabi         = 0xB008190C00000000
      pgHook       = 0x404CE73B00000000
      idxPtr       = 0x0000000000000000
      id           = 61767 (0x47F10000)
      shmTabhSet   = 0x0000000000000000
      refCount     = 1     (0x01000000)
      tstRefCount  = 0     (0x00000000)
      lineAdmin    = 606204 (0xFC3F0900)
      lineAlloc    = 600004 (0xC4270900)
      shmVersId    = 0     (0x00000000)
      shmRefCount  = 2     (0x02000000)
      rowId        = 18446744073709551615
      scndKeyAdmin = 0x0000000000000000
      ----- 1st level extension part --------
      regHook      = 0xC8C0190C00000000
      collHook     = 0x0000000000000000
      ext2         = 0x0000000000000000
    RI-CLUSTR
       0
       00
       00
    ZE_ATTRIBUTES
                         00000
       22222222222222222233333
       00000000000000000000000
       00000000000000000000000
       00000000000000000000000
    ZI_ATTRIBUTES
       AU0A    070221000020130
       45342222333333333333333
       15010000070221000020130
       00000000000000000000000
       00000000000000000000000
    ZI_ATTRIBUTES_UPD
       XXXXX XXXXXX  XX XXXX
       55555255555522552555522
       88888088888800880888800
       00000000000000000000000
       00000000000000000000000
    SOURCE_FIELDS>-RECORD
       1
       0000
       1000
    T_MONITOR_RECNO
       Table[initial]
    ZG_REALIGNMENT_RUN
       2
    Regards,
    Asim
    GECPC_GLPCP   

Maybe you are looking for