Error in Transaction SARA - ECC 6.0

Hi ,
When executing the report MMREO050N in ECC 6.0 there are two fields MATNR_EX and MATNR_VE  with no description against the same.
Please let me know whether anyone has corrected through a SAP Note.
If yes please provide me the Note Number.
If not through note what is other alternative to correct the same.
Regards
Ramesh

Thanks for the solution.
Regards
Ramesh

Similar Messages

  • Error in Transaction launcher - CRM 5.0 / ECC 6.0

    Hello all,
    I am trying to pull one ECC 6.0 transaction into CRM 5.0 IC webclient through launch transaction.
    When I click the link in the NavBar, I get the logon box for ECC system but after I enter the logon details below error message is getting displayed.
    The transaction call failed
    Reason:: Function module EWB_PROC_CREATE does not exist
    But this FM exists in both CRM and ECC systems.
    Any ideas about this error message?
    Best Regards,
    Nag

    Hi Sudeep,
    Thanks for the reply.
    I am not sure about the EEWB extensions.
    Initially I created a launch transaction using BOR method the path of the ECC logical system is given as below.
    http://ssever:port/sap/bc/gui/sap/its/CRM_CIC_RABOX
    But now I've changed the path as: http://ssever:port/sap/bc/gui/sap/its/CCMP_RABOX
    and it is working now. I am able to pull the transaction from ECC although some other data flow issues are there.
    So looks like there is some issue with the serivce CRM_CIC_RABOX in our system.
    Thanks to all,
    Nag

  • Errors while transaction download from ECC- CRM

    we are trying to download transactions from ECC 5.0 to CRM 5.0.
    the initial download has stopped in between and we get an error "SysFail" in the Inbound queue (SMQ2). Information on this error is "The current application triggered a termination with a short dump"
    when we try to analyze the short dump, it says the termination occured in the ABAP program :SAPLCRM_DOWNLOAD_MAP - in "FILL_BTM_PARTNER". In the source code you have the termination point in line 254  of the include program "LCRM_DOWNLOAD_MAPF37".
    please provide pointers to resolve this issue .
    thanks
    RH

    following is the place where the error is being triggered in the program, any suggestions?
    Information on where terminated                                                                   |
    Termination occurred in the ABAP program "SAPLCRM_DOWNLOAD_MAP" - in                         
    "FILL_BTM_PARTNER".                                                                          |
    The main program was "SAPMSSY1 ".                                                             |
    In the source code you have the termination point in line 254  of the (Include) program "LCRM_DOWNLOAD_MAPF37
    Source Code Extract                                                                               
    Line
    SourceCde
    number_int = <ls_bapisdpart>-itm_number.                                |
      if sy-subrc eq 0.                                                                     |
    ls_btm_partner-ref_guid = ls_item_keys-guid.                                        |
    ls_btm_partner-ref_kind = gc_object_ref_kind-orderadm_i.                            |
    endif.                                                                                |
    endif.                                                                                |
    *orderadm_h_guid
    ls_btm_partner-orderadm_h_guid = ls_orderadm_h-orderadm_h_guid.                         |
    *bp_partner_guid                                                                          |
    if lv_nrart = gc_partner_r3_types-customer.                                             |
    *-----AG, WE, RE, RG, etc.                                                                  |
      call function 'CRM_BUPA_MAP_CUSTOMER_TO_BP'                                           |
    exporting                                                                           |
    iv_customer       = <ls_bapisdpart>-customer                                      |
          importing                                                                           |
    ev_partner        = ls_btm_partner-bp_partner_guid                                |
    exceptions                                                                          |
    partner_not_found = 1                                                             |
    others            = 2.                                                            |
    if sy-subrc eq 0.                                                                     |
    display_type                                                                             |
    s_btm_partner-display_type =                                                       |
                           gc_partner_no_type-business_partner_no.                             |
    no_type                                                                                |
    ls_btm_partner-no_type =                                                            |
    gc_partner_no_type-business_partner_no.                              |
         else.                                                                                |
    if ls_btm_partner-partner_fct = '00000001'.                                         |
    >>>>>
    message x020(crm_order_misc) with gv_logsys_r3.
    endif.                                                                              |
       endif.                                                                                |
      if ls_btm_partner-task     eq gc_bdoc_task-delete and                                 |
      ls_btm_partner-ref_kind eq gc_object_ref_kind-orderadm_i.                          |
    special handling for deleting item partner. In this case the item                         |
    partner must not be deleted but updated with the header partner                           |
      insert ls_orderadm_h-orderadm_h_guid into table lt_header_guid.                     |
    insert gc_object_name-partner into table lt_requested_objects.                      |
    call function 'CRM_ORDER_READ'                                                      |
    exporting                                                                         |
      it_header_guid       = lt_header_guid                                           |
    iv_only_spec_items   = true                                                     |
    it_requested_objects = lt_requested_objects                                     |
    importing                                                                         |
    et_partner           = lt_partner_header                                        |
    exceptions                                                                        |
    others               = 1.                                                       |

  • Error in transaction Launcher handler class

    Hello friends,
    I am following the step from the CookBook for the creation of the Transaction Launcher
    but in side the class method
    IF_CRM_IC_ACTION_HANDLER~PREPARE_DATA_FLOW
    it is showing the error
    CREATE_ENTITY is unknown or Protected or Private.
    Its supper class is CL_CRM_IC_ABOX_ABSTRACT_BOR
    and interface included is IF_CRM_IC_ACTION_HANDLER.
    Will i have to make any change in side these class or there any other way to configure the transaction launcher.
    Regards
    Pulkit Agrawal

    Hi Sudeep,
    Thanks for the reply.
    I am not sure about the EEWB extensions.
    Initially I created a launch transaction using BOR method the path of the ECC logical system is given as below.
    http://ssever:port/sap/bc/gui/sap/its/CRM_CIC_RABOX
    But now I've changed the path as: http://ssever:port/sap/bc/gui/sap/its/CCMP_RABOX
    and it is working now. I am able to pull the transaction from ECC although some other data flow issues are there.
    So looks like there is some issue with the serivce CRM_CIC_RABOX in our system.
    Thanks to all,
    Nag

  • Archiving Transaction SARA throws dumps.

    S0003731475
    Hi Gurus
    I am trying to run archiving transaction SARA but it throws dumps and I canu2019t seem to find the reasonu2026u2026
    Here is the dumpu2026u2026..Anyone who faced similar problemu2026u2026.Please help.
    Runtime errors         SYNTAX_ERROR
           Occurred on     12/08/2009 at   13:45:09
    Syntax error in program "SAPLARCH ".
    What happened?
    The following syntax error occurred in the program SAPLARCH :
    "Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
    Error in ABAP application program.
    The current ABAP program "SAPMAADM" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLARCH ".
    You can also perform the syntax check from the ABAP/4 Editor.
    If the problem persists, proceed as follows:
    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.
    Error analysis
    The following syntax error was found in the program SAPLARCH :
    "Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "M3SAPA01"
    Network address.......... "136.133.230.177"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "M3SAPA01"
    Database type............ "MSSQL"
    Database name............ "RDS"
    Database owner........... "rds"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Mar 10 2009 01:13:21"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "SQL_Server_8.00 "
    Patch level.............. "274"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    User, transaction...
    Client.............. 220
    User................ "RHEMNANI"
    Language key........ "E"
    Transaction......... "SARA "
    Program............. "SAPMAADM"
    Screen.............. "SAPMAADM 0001"
    Screen line......... 2
    Information on where terminated
    The termination occurred in the ABAP program "SAPMAADM" in "D0001_DISPLAY".
    The main program was "SAPMAADM ".
    The termination occurred in line 278 of the source code of the (Include)
    program "MAADMO01"
    of the source code of program "MAADMO01" (when calling the editor 2780).
    Source code extract
    002480   * check if parameters exists
    002490     progname = arch_obj-retrie_prg.
    002500     answer = 'YES'.
    002510     CALL FUNCTION 'RS_SELSCREEN_EXISTS'
    002520       EXPORTING
    002530         report            = progname
    002540       IMPORTING
    002550         answer            = answer
    002560       EXCEPTIONS
    002570         no_report         = 01
    002580         program_incorrect = 02
    002590         program_not_found = 03.
    002600     IF sy-subrc EQ 0.
    002610       IF answer EQ 'NO'.
    002620         LOOP AT SCREEN.
    002630           CHECK screen-group1 = 'VAR'.
    002640           screen-active = 0.
    002650           MODIFY SCREEN.
    002660         ENDLOOP.
    002670       ENDIF.
    002680     ENDIF.
    002690   ENDMODULE.                             " D0300_DISPLAY  OUTPUT
    002700
    002710   *&---------------------------------------------------------------------*
    002720   *&      Module  D0001_DISPLAY  OUTPUT
    002730   *&---------------------------------------------------------------------*
    002740   *       text                                                           *
    002750   *----------------------------------------------------------------------*
    002760   MODULE d0001_display OUTPUT.
    002770     SUPPRESS DIALOG.
    ----->     CALL FUNCTION 'ARCHIVE_DISABLE_MONITORING'.
    002790   ENDMODULE.                             " D0001_DISPLAY  OUTPUT
    002800   *&---------------------------------------------------------------------*
    002810   *&      Module  INIT_0120  OUTPUT
    002820   *&---------------------------------------------------------------------*
    002830   *       text
    002840   *----------------------------------------------------------------------*
    002850   MODULE d0120_display OUTPUT.
    002860     DATA: format1(12) TYPE c.
    002870     DATA: format2 TYPE i.
    002880     LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
    002890     SET PF-STATUS 'SPACE'.
    002900     SET TITLEBAR '105'.
    002910     WRITE: / 'Archivverzeichnis:'(060), file_path.
    002920     ULINE.
    002930     MOVE freespace TO format2.           "to format with points
    002940     WRITE format2 TO format1.
    002950     WRITE: / 'Verfügbarer Freiplatz:'(061),format1 NO-ZERO,'KB'.
    002960     LEAVE SCREEN.
    002970
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 0                             SY-DBCNT 0
    SY-FDPOS 0                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY
    SY-UCOMM                               SY-TITLE Archive Management Module Pool
    SY-MSGTY                               SY-MSGID
    SY-MSGNO 000                           SY-MSGV1
    SY-MSGV2                               SY-MSGV3
    SY-MSGV4
    Active calls / events
    No.... Type........ Name..........................
           Program
           Include                                  Line
           Class
         2 MODULE (PBO) D0001_DISPLAY
           SAPMAADM
           MAADMO01                                   278
         1 MODULE (PBO) D0001_DISPLAY
           SAPMAADM
           MAADMO01                                   278
    Chosen variables
         2 MODULE (PBO) D0001_DISPLAY
           SAPMAADM
           MAADMO01                                   278
    %_DUMMY$$
                                   2222
                                   0000
                                   0000
                                   0000
         1 MODULE (PBO) D0001_DISPLAY
           SAPMAADM
           MAADMO01                                   278
    No dump information available
    Application Calls
    No dump information available
    Application Information
    No dump information available
    Internal notes
    The termination occurred in the function "ab_genprog" of the SAP
    Basis System, specifically in line 1423 of the module
    "//bas/640_REL/src/krn/runt/abgen.c#14".
    The internal operation just processed is "FUNC".
    The internal session was started at 20091208134509.
    Program name.........: "SAPLARCH ".
    Error message........: "Method "GET_DATA" is unknown or PROTECTED or PRIVATE.".

    Rajesh,
    This might happen if the orginal function module ARCHIVE_GET_INFORMATION in LARCHF03 program is altered, bring back the the function module to original, it might solve your problem.
    Anand B Vodnala

  • Error in installation of ECC 6 Import ABAP

    I have got error during installation of ECC 6 on win 2003 and oracle.
    "Not all objects are succefully processed. DIAGNOSIS: For detail  see output file with invalid objects invalid_objects.txt and log file object_checker.log SOLUTION: Normally it indicates the data load error but in some special case (for example if some objects were created or loaded externally) you can press OK to continue.
    Here is invalid_objects.txt
    checkObjects=
    dbType=ORA
    strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
    trace=all
    tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
    package   object  type  action  status
    SAPDFACT  ?N      pkey  create
    and object_checker.log
    INFO: 2020-12-31 10:12:55
    Object Checker is started.
    CONFIG: 2020-12-31 10:12:55
    Application options:
    checkObjects=
    dbType=ORA
    strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
    trace=all
    tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
    CONFIG: 2020-12-31 10:12:55
    List of packages with table structure: 'SAP0000'.
    INFO: 2020-12-31 10:12:55
    19 packages found in 'E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA' directories.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'MAPR~ADQ' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (!MSS) index 'MLST~1' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'MLST~1AD' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (!MSS) index 'MLST~2' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'MLST~2AD' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (!MSS) index 'MLST~4' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'MLST~4AD' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'PLMK~ADQ' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES_APP~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES_RB~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOYES_TI~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOY_CSH~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'SEMPLOY_SEARCH~ARE' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (MSS) index 'STXH~TDN' found in STR file for 'SAPAPPL0' package.
    TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'BBSID~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'BSID~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (DB6) index 'DB6CSTRACE~1' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'KBED~3' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'KBED~4' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'NAST~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S003~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S003BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S003BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S004~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S004BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S004BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S006~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S006BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S006BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S011~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S011BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S011BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S012~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S012BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S012BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S013~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S013BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S013BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S031~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (ADA) index 'S032~ADQ' found in STR file for 'SAPAPPL1' package.
    TRACE: 2020-12-31 10:13:02 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Database specific (DB6) index 'VARIS~DB6' found in STR file for 'SAPAPPL2' package.
    TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Data load must be skipped for table 'DBPROPERTIES' from STR file for 'SAPSDIC' package.
    TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
    Data load must be skipped for table 'DDLOG' from STR file for 'SAPSPROT' package.
    ERROR: 2020-12-31 10:13:05
    1 objects have error/ignore/execute or unknown status in the task lines.
    Invalid objects are saved in 'invalid_objects.txt' file.
    INFO: 2020-12-31 10:13:05
    Object Checker is stopped.
    I have not installed any object manually. Also not sure which object did not installed properly? Any idea or suggestion for this?
    Thanks
    Edited by: Prinesh Patel on Jan 7, 2008 7:35 PM

    Hi Patel,
                         Thanks for your update.
    Regards,
    Hari.

  • Error committing transaction in Stored Proc call - prev solns not working

    Hi All,
    Our process invokes a DB adapter to fetch the response from the table for our request via Stored Procedure call but facing the below issue. Its a synchronous process. Stored Procedure is present inside the Package and we are calling the Stored procedure using that Package.
    What we did is created a DB datasource of XA type and tried to call the Stored Proc but it was giving a problem “ORA-24777: use of non-migratable database link not allowed” and hence according to this thread Using DB links in Stored proc call in DB adapter 11G SOA we have modified the datasource as non-XA type.
    While we do that, we could see that Stored Proc is called and the response is present in the reply payload inside the flow trace. But the instance is getting faulted and the error is “Error committing transaction:; nested exception is: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source.”
    We have tried the properties of global transaction support as one phase commit, emulate two phase commit and logging last resource but error remains the same.
    Database from which we are getting the response is of version "Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production". Will the database link error arises even if we connect to Oracle Database?
    Please could you advise me solutions to resolve this issue.
    Thanks in advance.

    You are using Non-XA because it means (among all others) that the commit issue can be handle by the DB as well.
    The Emulate Two Phase property imitating the XA transaction in that way, that it allows you to manage a local db transaction.
    You can stay with XA connection, but then you will have to use "AUTONOMOUS_TRANSACTION pragma" in your procedure.
    Enter the following link to find good explanation about all of your questions:
    http://docs.oracle.com/cd/E15523_01/integration.1111/e10231/adptr_db.htm#BGBIHCIJ
    Arik

  • Error while registering SAP ECC system in UWL systems

    hi,
    Error while registering SAP ECC system in UWL systems.
    Errors:
    System R3Production: Thu Nov 27 16:12:05 GMT+05:30 2008
    (Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Thu Nov 27 16:12:05 GMT+05:30 2008
    (Connector) :com.sap.mw.jco.JCO$Exception:Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=132.147.0.112 SYSNR=00 GWHOST=132.147.0.112 GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '132.147.0.112:sapgw00' not reached
    TIME        Thu Nov 27 16:12:05 2008
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       79
    ERRNO TEXT  A remote host refused an attempted connect operation.
    COUNTER     2
    Item type retrieval and registration requires a connection to the systems and may take a couple of minutes
    For each system, they are generated as the configuration named 'uwl.webflow.<system_alias>' or 'uwl.alert.<system_alias>'.
    After configuration changes in the backend system, you must re-register the system.
    regards.
    Srinivas.

    Hi,
    you can check few things prior proceeding:
    Does your connector test after adding your backend system in portal works fine?
    Did you define a system alias?
    Make sure your SSO is working,
    Also check your Jco detination webdynpro tab.
    Regards,
    Vamshi.

  • Archiving Objects in SAP Retail (transaction SARA)

    Hi All.
    I have problem with archiving object WS_ACSITE in SAP RETAIL.(Transaction SARA)
    When I write data archiving, message appeard is that archive sessions are created.
    When I try to execute the next step: delete - the archive sessions are not appearing in the dialog box where we should choose the archive sessions for deletion.
    The above situation appear when I am working with plants existing in system for a while, but when I've create a new one and try to go through all SARA's steps it is OK, and master date of sites are deleted (e.g WB03).
    Can anyone help me?
    The second question is u2013 can I restore deleted sites to system?
    thanks in advance.
    Marcin

    Hello,
    Check below information for Material master record required to archive:
    1. Is there any stocks in the plant for which MMR need s to be archived? (Stock = Zero)
    2. Is there any open items at FI accounting? (There should be no pending bills or parked documents)
    3. Is there any pending delivery for this material? (there should be no open deliveries)
    If all the above criteria is met then set the deletion flag and indicator for perticular Plant you are looking for.
    Note: Make sure that non of the other plants which is sharing this MMR is marked for deletion flag / indicatory
    Then execute Archive run for archiving object MM_MATNR.
    Note: All the required configuration is done for archiving object MM_MATNR.
    Hope this will help you to archive MMR only for your required plant.
    -Thanks,
    Ajay

  • Error in Transaction data

    Hi Folks,
    In System logs, daily I am encountering the message as "Error in transaction data".
    The messages are listed in SM21 in sequence as -
    Error processing batch input session PMFMASSIGN
    > Queue ID: 07011706105177351507
    > Transaction no. 1, block no. 1
    > Error in transaction data
    On more detailed analysis, after drilling further through each message I found the following message relevant -
    Documentation for system log message D2 0 :
    Entry relating to an error during the processing of a batch input session.  In the batch input session the data for the next transaction is requested.  However, the data read is no transaction data. The session has probably been destroyed in the database.
    Please explain as why the issue is occuring. I remember some time back, I executed RSBTCDEL2 on Production to clear invalid batch sessions but had to terminate due to long run.
    Kindly help me fix this.
    Regards,
    Nick

    One interesting discovery I just found in R/3, was this job log with respect to the above process chain:
    it says that the job was cancelled in R/3 because the material ledger currencies were changed.
    the process chain is for inventory management and the data load process that get cancelled are for  the job gets cancelled in the source system:
    1. Material Valuation: period ending inventories
    2. Material Valuation: prices
    The performance assistant says this but I am not sure how far can I work on the R/3 side to rectify this:
    Material ledger currencies were changed
    Diagnosis
    The currencies currently set for the material ledger and the currency types set for valuation area 6205 differ from those set at conversion of the data (production startup).
    System Response
    The system does not allow you to post transactions after changing the currency settings to ensure consistency.
    Procedure
    Replace the current settings with the those entered at production
    start-up.
    If you wish to change the currency settings, you must use programs to convert data from the old to the new currencies.
    Inform your system administrator
    Anyone knowledgable in this area please give your inputs.
    - DB

  • Error In Transaction F-44 for Foreign Vendor Payment

    Hi Experts,
    User is getting the Error In Transaction F-44 (G/L account 14281001 xxxx does not exit) while doing Vendor Payment to Foreign Vendors.
    When I checked in Vendor Master Data, Reconcilliation account is maintained for all Foreign(other) & Foreign(Intercompany) Vendors.
    The GL 14281001 is maintain in the account determination configuration for other Foreign Vendors.
    User is getting this Error After successful FF67 transaction Process.
    Please advice.

    Hi Amitash,
    GL is created @ COA level & not mark for deletion. This GL is not created in Company code. I discussed with user she was saying
    F-44 transaction is booked a realized gain/loss while a foreign vendor invoice clearing vs payment. Normally this realized gain/loss must be booked directly to the foreign vendor account which is linked to GL XXXXXXXX for all IC foreign vendors and linked to GL YYYYYYYY for all other foreign vendors .
    It will be not correct to book a foreign vendor realized gain/loss to a separate account therefore a new GL 14281001 should not be created in comp code XXXX,  instead of incorrect GL14281001 SAP must select either GL XXXXXXXX for IC foreign vendors or GL YYYYYYYY for all other foreign vendors.

  • Error in transaction SOAMANAGER from Dev ECC6

    Hi,
    I am getting below error in transaction SOAMANAGER  -- Application & scenario comm -- single service admin -- select service Z* -- apply selection -- Open Web Service navigator for selected binding then getting error as below:
    Error:
    Cannot download WSDL from http://<host>:8010/sap/bc/srt/wsdl/bndg_DF5CDA3549E109F1A9D000145E7A77A0/wsdl11/allinone/ws_policy/document?sap-client=010: It is not allowed to access this service. If you believe you should be able to, please contact your system administrator
    I appreciate if you could help me in this.
    - Pankaj

    Hi Pankaj,
    This error message is caused by security considerations. The WS Navigator can access only web services which are deployed on the local engine. To allow the WS Navigator to access an external hosts, you have to add
    these hosts, to the WS Navigator white list. The white list is a list hosts which the WS Navigator should be able to access.
    Please refer to this link, which describes where the white lists are maintained in the visual administrator: http://help.sap.com/saphelp_nw04/helpdata/en/7c/f257422d095542e10000000a1550b0/content.htm
    When configuring the white lists one can use wild card. For instance. If a web service deployed on www.sap.com should be accesseed by the WS Navigator, then the the white list should contain *.sap.com. The whitelist can contain more then one host, in that case they should be separated by an comma or semi-column.
    Hope this can fix your issue.
    Regards,
    Blanca

  • LSMW - Error BDC_INSERT, Transaction code .. is invalid XD01

    Dear all.
    I have done the following Steps:
    1 - Maintain Object Attributes. Chose the Object type Batch Recording, then created a Record using the name (CLI_PMR). And created the Batch record and then assign the fields name.
    2 - Maintain Source Structures – Created the Struture (CLI_PMR1)
    3 - Maintain Source Fields – Assign the fields name and length that I used in my program. (CLI_PMR1).
    4 - Maintain Structure Relations – Assign the Struture (CLI_PMR1 to CLI_PMR)
    5 - Maintain Field Mapping and Conversion Rules – The normal thing in this point.
    6 - Specify Files - Specified the Legacy Data, path for the file.
    7 - Generate Read Program – Generated the Program.
    8 – Read Data – Executed this Step and every thing is correct
    9 - Generate Conversion Program – Generated the program
    10 - Convert Data – Convert data
    11 - Display Converted Data – Every thing is fine, with no errors
    12 - Create Batch Input Session- At this the error message appears Error BDC_INSERT, Transaction code .. is invalid  time.
    At the time we have created other LSMW programs for this T-Code and every thing is OK.
    I'm using the T-CODE=XD01
    Best Regards
    Pedro Miguel Rodrigues

    Hi, I had the same problem in LSMW when generating a batch input for trx IE01. The cause was that there were tab/newline-characters in my text file (some descriptions contained tab-characters). Since I used a tab delimited file, these tabs/newlines in the fields messed up my file.
    The excel file contained multiple lines per cell in some description fields. When this was exported to tab delimited text, it contained additional tabs. After checking the contents and removing the tabs/newlines from Excel and performed a new export to txt-file, it was solved.
    Best regards,
    Jan-Peter Molenaar
    SAP EAM Consultant

  • Error: [129]: transaction rolled back by an internal error:  [129] transaction rolled back by an internal error: exception 141000274: exception 141000274: TRexUtils/ParallelDispatcher.cpp:275 message not found; $message$=

    Hello Gurus,
    I have a couple of calculation views in HANA and each of them has text fields (like Employee Name, Country Name etc.).
    As part of my project requirement, I have join those two views and get all the fields that exist in them.
    When I am doing so, I am getting a weird error as shown below.
    Error: [129]: transaction rolled back by an internal error:  [129] transaction rolled back by an internal error: exception 141000274: exception 141000274:
    TRexUtils/ParallelDispatcher.cpp:275
    message not found; $message$='TSR HTKD JFSDFM'
    Please check lines: 59,
    Upon, researching further, I could see that the value 'TSR HTKD JFSDFM' is the value in text field of Employee Name.
    I did try to increase the length of the field and change the data types but nothing has worked.
    Could you please help me in getting this one resolved.
    Thanks,
    Raviteja

    Hi,
    I am exactly facing the same issue:
    Error: [129]: transaction rolled back by an internal error:  [129] transaction rolled back by an internal error: exception 141000274:
    But i found a fix :-) .....
    This may be a very late reply but it would help people who desperately searching for an answer for this issue.
    I used CAST function .. The problem is, we are selecting data from table and of course we dont know the size of the data (attribute) @ runtime. We assign the length by looking at the table attr length or view op attr length. But what happens is the junk data which exceeds the limit of the allocated space hence we get this error.
    So i used CAST function to truncate the excess junk values (may be spaces).
    Example:
    I have a ATTR view of date in the format YYYY-MM-DD which means 10 char size.
    In my CALC view I have created date OP column of VARCHAR(10) but I get the above error for no reason. Eventhoug i am 100% sure about my ATTR date would be max of 10 char my CALC view is failing @ runtime.
    So i did a CAST on date as CAST(my_date as varchar(10)) and the magic happend. It works .......
    But you need to be careful in using this because if you use CAST you may lose data. Careful. In my case i dont.
    Somebody from HANA team should look at this issue from SAP and solve this. I am sure it is a serious bug from HANA (eventhough i am using SAP HANA SP09 Rev 92 the most latest as of today !!!!!!!!!! )
    Enjoy....
    Thanks & Regards
    Prakash K

  • New Added RF Transactions in ECC 6.0?

    Hi,
    What are the new RF transactions added to ECC 6.0??
    I would appreciate if someone can provide a list of all supported RF transactions in ECC 6.0
    Thanks,
    Sen

    hi
    new Gl is the main functionality of ECC6
    u can know more about new GL at
    Re: Classic G/L and New G/L
    and also  check the link for Delta between 3.1-4.0- 46C - ECC5.0 & ECC 6.0
    http://solutionbrowser.erp.sap.fmpmedia.com/
    assign points if useful
    regards
    Srilakshmi

Maybe you are looking for