MESSAGE_TYPE_X error

Hello all,
We are facing an issue, that "Message_type_X " short dump occurs .
the actual short dump message is:
"MESSAGE_TYPE_X" " "                                                                          |
"CL_RSQ_ISET_SERVICE===========CP" or "CL_RSQ_ISET_SERVICE===========CM016"
"EXTEND_FIELD_BUFFER"     .
kindly help me..
|

hi,
kindly check SAP Note 1137254 , it might be helpfult to you
also check in sm21 about system log, in ST22 check on information on where termiinated and in error analysis that will give you some clue on job which is effected
regards
laksh

Similar Messages

  • Message_type_x error in mr11

    hi gurus ,
    i am getting a message_type_x error in mr11 in the following code in the function module 'CKMLGRIR_POST_GRIR_MAINTAIN
    i have commented the line which throws run time error
    FORM CHECK_ACTIVITY_TAB_POST.
    Pflegen der Tabelle ACTIVITY_TAB
      CLEAR WF-EXIT.
      CLEAR ACTIVITY_TAB.
      ACTIVITY_TAB-NAME   = UF-ACTIV.
      READ TABLE ACTIVITY_TAB WITH KEY ACTIVITY_TAB-NAME.
       Prüfen, ob Fehler im Belegkopf oder Eintrag nicht gefunden
      IF SY-SUBRC                   NE 0    OR
         ACTIVITY_TAB-HEADER_ERROR   = 'X'  OR
         ACTIVITY_TAB-POSITION_ERROR = 'X'  OR
         ACTIVITY_TAB-POSITION       = ' '.
         MESSAGE X167 WITH UF-ACTIV.   " the  run time error is reported on this line
         WF-EXIT = 'X'.
         EXIT.
      ENDIF.
       wenn kein Fehler, dann Vormerken zur verbuchung.
      ACTIVITY_POST-ACTIVITY = UF-ACTIV.
      COLLECT ACTIVITY_POST.
    ENDFORM..
    plz hehp
    Edited by: anandkishor on Sep 9, 2009 9:21 AM

    hi gurus ,
    i am getting a message_type_x error in mr11 in the following code in the function module 'CKMLGRIR_POST_GRIR_MAINTAIN
    i have commented the line which throws run time error
    FORM CHECK_ACTIVITY_TAB_POST.
    Pflegen der Tabelle ACTIVITY_TAB
      CLEAR WF-EXIT.
      CLEAR ACTIVITY_TAB.
      ACTIVITY_TAB-NAME   = UF-ACTIV.
      READ TABLE ACTIVITY_TAB WITH KEY ACTIVITY_TAB-NAME.
       Prüfen, ob Fehler im Belegkopf oder Eintrag nicht gefunden
      IF SY-SUBRC                   NE 0    OR
         ACTIVITY_TAB-HEADER_ERROR   = 'X'  OR
         ACTIVITY_TAB-POSITION_ERROR = 'X'  OR
         ACTIVITY_TAB-POSITION       = ' '.
         MESSAGE X167 WITH UF-ACTIV.   " the  run time error is reported on this line
         WF-EXIT = 'X'.
         EXIT.
      ENDIF.
       wenn kein Fehler, dann Vormerken zur verbuchung.
      ACTIVITY_POST-ACTIVITY = UF-ACTIV.
      COLLECT ACTIVITY_POST.
    ENDFORM..
    plz hehp
    Edited by: anandkishor on Sep 9, 2009 9:21 AM

  • RFC_ERROR_SYSTEM_FAILURE error while  updating the sick leave in MSS

    Hi Guru ,
    We are  getting  RFC_ERROR_SYSTEM_FAILURE error while updating the Sick leave for team member from portal .
    Please tell how to resolve this .
    Dump part :
    Runtime Errors         MESSAGE_TYPE_X
    Error analysis
        Short text of error message:
        System error
        Long text of error message:
        Technical information about the message:
        Message class....... "HRTIM00BUFMSG"
        Number.............. 001
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    Information on where terminated
        Termination occurred in the ABAP program "SAPLHRTIM00_TMWBUFFER" - in
         "INITIALIZE".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 55
        of the (Include) program "LHRTIM00_TMWBUFFERCB5".

    When an RFC fails from the portal to an SAP Backend, probably ECC 6.0 in your case, there are a few options that I use to troubleshoot:
          1. Ensure that all your jco's are set up ok, passwords, ect. JCOs do not appear to be the problem here
          2. Have an ABAP programmer review where the RFC is failing on the Backend System
          3. Set up an External Breakpoint in the backend RFC. Step to do this:
                   a. Get the Backend UserID of a test portal user that is having this issue.
                   b. Ensure that test user has "Debug Display" access in the Backend System
                   c. Log into the Backend system, go to SE 37 and display your RFC
                   d. Go to Utilities --> Settings --> Debugging in the top menu and add the Test User ID to the "Users" field.
                   e. Set an external breakpoint any where you want in the RFC.
                   f. Run the Leave request as the test user.
                   g. a new SAP GUI screen will popup once it hits the breakpoint. The portal browser will stay frozen until you step thru the ABAP program.
      Option 3 may sound like alot at first if you never used it, but if you are responsible for troubleshooting portal issues like this one, it is a skill you must have. You can also have an ABAP resource responsible for external debugging when you come accross issues like these. It helps you see exactly what data is being passed in from the portal and what is happening to cause the error.
    Regards,
    Tom

  • How to remove this error every time in extraction

    Dear folks,,
    I have a difficulties in extraction .. Could you share to me how to remove this error please .. ??
    In one ODS: Quotation (Fetching the data from CRM), it always raise up the error every time do an extraction ..
    The message error is like this:
    Runtime Errors     :    MESSAGE_TYPE_X
    Error analysis                                                             
    Short text of error message:                                           
    Req. 0000508314 in DataStore ZCRMQUTO must have QM status green before it is activated
    Another Clues:
    SY-TITLE : CPIC and RFC Control     
    SY-MSGTY : X                        
    SY-MSGID : RSM1                     
    SY-MSGNO : 110                      
    SY-MSGV1 : 0000508314               
    SY-MSGV2 : ZCRMQUTO                 
    SY-MODNO : 0                        
    SY-DATUM : 20080116                 
    SY-UZEIT : 083744                   
    SY-XPROG : SAPLRSSM                 
    SY-XFORM : RSSM_MON_START_2ND_PROCESS
    My Questions are :
    1. Do you ever have the problem like this ??
    2. Do you know the problem regarding CPIC & RFC Control, is that any correlation with RFC/Connection to CRM.
    3. Do you know regarding the message error: RSSM_MON_START_2ND_PROCESS
    Need really your guidance and response..
    Regards,
    Niel..
    will appreciate any response ..

    Hi,
    Just try this.
    As per the error message "Req. 0000508314 in DataStore ZCRMQUTO must have QM status green before it is activated" there is a request(0000508314) in red/yellow status in the ODS (ZCRMQUTO).
    This error normally occurs while activation of ODS/DSO.
    Activation may fail saying that there is a request with status other than green in target. Ideally system expects to activate a green request. But if it find a request with other (red/yellow) it may throw an error.
    This is the error message we get for that kind of errors
    'Request REQU_* in ODS must have QM status green before it is activated." and this is the same one you are getting.
    Try to find the bad request, rectify/delete it.
    This may resolve your problem.
    thanks,
    JituK

  • MESSAGE_TYPE_X in POS Retail

    Hi,
          I'm facing a short dump error is POS DM. When I read data from the remote cube using LISTCUBE / RSA3 (checking the datasource), I'm getting MESSAGE_TYPE_X error in the following line, this is due to the SY-SUBRC NE 0.
    If NOT SY-SUBRC IS INITIAL.
    MESSAGE X000(/POSDM/COMMON) with " " " " " ".
    ENDIF.
    My datasource is 0RT_PA_TRAN_CON_REM
    Please let me know if there is any OSS for this.
    Thanks,
    Chandran

    Hi,
    This behaviour can be observed if there were changes done to tablespace in the target system during deletion (for example: the tablespace assigned to ZAGILE_ECO does not exist anymore). Do check for ORA-00959 errors in the system logs in such a situation.
    Also check if the table ZAGILE_ECO has already been deleted. In that case, you can just ignore the error and change the status of the activity to complete via tha troubleshooter.
    Regards,
    Suman

  • Abap dump MESSAGE_TYPE_X in SAPLSLVC - in "FILL_DATA_TABLE

    Gurus ,
    we get the MESSAGE_TYPE_X error in saplslvc in "FILL_DATA_TABLE '  when we execute our custmized program .
    but the same program was executed successfully in the Development system .
    i get this error in quality and production alone
    we have dev , qua & pro at the same level .
    what could be the problem ?
    hoping for your valuable response

    Look if these OSS notes are applicable in  your system (april 2008)
    - [ Note 1034895 - ALV mean value: Decimal places in mean value calculation|https://service.sap.com/sap/support/notes/1034895]
    - [Note 840240 - ALV total: Average with P fields without decimal places|https://service.sap.com/sap/support/notes/840240]
    - [Note 717669 - ALV grid: Hidden columns result in unreadable grid|https://service.sap.com/sap/support/notes/717669]
    - [Note 442295 - ALV toolbar: Change Layout dial. box contains hidden functs|https://service.sap.com/sap/support/notes/442295]
    - [Note 1136738 - ALV-Total: Subtotals of numeric columns without values|https://service.sap.com/sap/support/notes/1136738]
    Regards

  • Run Time Error when trying to select hierarchy node

    Hy all,
    the situation is the following:
    i attempt to create a variable of type "hierarchy node" (for cost center cha) in my planning area, i used the replacement type "user defined value", check on "input allowed by user" and then i create the user entry, in selection condition i run match code and when i try to select a single cost center (not a hierarchy node) expanding the hierarchy tree the system goes dump with the following message:
    Runtime Errors         MESSAGE_TYPE_X
    Error analysis
    Short text of error message:
    Program is inconsistent -> see long text
    Technical information about the message:
    Diagnosis:
    An inconsistent program status has occurred. The program cannot be continued.
    System response:
    The system crashes.
    Procedure
             1.  Look in OSS for a note under the error message UPC099.
             2.  When you open a problem message, send the first pages of the
                 system crash message including the section 'Source code excerpt
                 ' with the message.
         Procedure for System Administration
        Message classe...... "UPC"
        Number.............. 099
    Selecting a hierarchy node (not a single cost center but a text node grouping more cost conter) this problem does not occur.
    I appreciate (and reward) any hints.
    Thanks in advance
    Fabio

    Hi,
    Go through the oss notes with error message UPC099
    Dump during hierarchy selection:<b>536694</b>
    Dump when reading a hierarchy with intervals :<b>423953</b>
    Regards-
    Siddhu
    Message was edited by: sidhartha

  • Error: Object Name cannot be Empty, when loading Master Data

    Hi all,
                  We are loading mater data for one of the InfoObject, which is failing at Processing Step. Data is loaded properly till PSA. There is short dump error giving MESSAGE_TYPE_X error. On analyzing Job Log, We found the error like, "OBJECT NAME CANNOT BE EMPTY".
                  We checked InfoObject and found that, One of its attribute is inactive. Can it be the cause of error? Please Reply soon.
    Thanks,
    Harpal

    It must be the cause of error. Please activate all inactive attributes and load the data again.
    Regards
    Pankaj

  • Process chain AND process

    Hi,
    I have a process chain that has two parallel processes of loading DSO and Infocube data. There are two infopackages on one side and two on the other side. The two processes are connected with and AND process at the end and after that there is a datastore activation process.
    When I executed the process chain, the infopackages on both sides started loading data. The two infopackages on the left side finished first while the second infopackage on the right side had not finished yet when the AND process errored. I get the following message:
    This AND process is not waiting for event RSPROCESS , parameter
    47VKUORHMXQKR2AN73AVAR0C9
    After the AND process I have a Datastore generation process and I want it to continue only when all infopackages have been loaded.
    Why does the process stop at AND even though all infopackages have not finished yet?
    thanks
    Michalis

    There was no error message in ST22 or SM37. There was very little info to go on. I just deleted the requests and run the process chain again and there's no error. However the process chain does fail at a later step.
    Update Datastore Object Data (Further update)
    I don't know what that further update is for. It was automatically selected in my Process chain when I selected the infopackage for the DSO.
    There's a MESSAGE_TYPE_X error.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRSM2" - in "RSSM_MON_WRITE_3".
        The main program was "RSBATCH1 ".
        In the source code you have the termination point in line 2659
        of the (Include) program "LRSM2U16".
        The program "SAPLRSM2" was started as a background job.
        Job Name....... "BI_PROCESS_ODSPROCESS"
        Job Initiator.. "CSPAPADM"
        Job Number..... 14103000
    Source Code Extract
    Line  SourceCde
    2629       CALL FUNCTION 'RSSM_GET_TIME'
    2630         EXPORTING
    2631           i_datum_utc  = rsreqdone-tdatum
    2632           i_uzeit_utc  = rsreqdone-tuzeit
    2633         IMPORTING
    2634           e_timestamps = l_s_status-t_timestamp.
    2635       IF rsreqdone-tstatus(3) = icon_green_light(3) OR
    2636          rsreqdone-tstatus(3) = icon_red_light(3).
    2637         CALL FUNCTION 'RSSM_GET_TIME'
    2638           IMPORTING
    2639             e_timestamps = l_s_status-ts_proc_ended.
    2640         l_not_yellow = 'X'.
    2641       ENDIF.
    2642       IF l_not_yellow = 'X'.
    2643         CALL FUNCTION 'RSSTATMAN_SET_STATUS'
    2644           EXPORTING
    2645             i_s_status    = l_s_status
    2646             i_with_commit = 'X'.
    2647         IF l_s_status-t_status(3) = icon_green_light(3) AND
    2648            l_s_status-dta_type   = 'ODSO' AND
    2649            t_data-aufrufer <= '70'.
    2650           CALL FUNCTION 'RSS2_CALLBACK_ODSADM_ODS_SUCC'
    2651             EXPORTING
    2652               i_ods = l_s_status-dta(30)
    2653               i_rnr = l_s_status-rnr.
    2654         ENDIF.
    2655       ENDIF.
    2656     ENDLOOP.
    2657     IF sy-subrc <> 0.
    2658       IF t_data-aufrufer <> '09'.
    2660       ENDIF.
    2661     ELSE.
    2662       IF l_not_yellow = 'X'.
    2663         CALL FUNCTION 'RSB1_OSNAME_TO_ICNAME'
    2664           EXPORTING
    2665             i_osource        = g_s_minfo-oltpsource
    2666 *           I_OSTYPE         = RSAOT_C_OSTYPE-TRAN
    2667           IMPORTING
    2668             e_icname         = l_icname
    2669           EXCEPTIONS
    2670             name_error       = 1
    2671             OTHERS           = 2.
    2672         IF sy-subrc = 0.
    2673           CALL FUNCTION 'RSAWB_MAINTAIN_DTA'
    2674             EXPORTING
    2675               i_method                   = rsatr_c_dta_get
    2676 *             I_TYPE                     =
    2677               i_objvers                  = rs_c_objvers-active
    2678               i_dta                      = l_icname
    Any idea what that means? Also do I need that further update step in my process chain?

  • Short Dump while Complete deletion of data Contents from a Cube.

    Hello Experts,
    I am facing a runtime Short dump whenever i attempt to delete data from a Cube. Shown Below:-
    Runtime Errors         MESSAGE_TYPE_X
    Error analysis
        Short text of error message:
    Data request to the OLTP
        Long text of error message:
        Technical information about t
        Message class....... "RSM"
        Number.............. 000
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "MESSAGE_TYPE_X" " "
        "SAPLRSM1" or "LRSM1U43"
        "RSSM_UPDATE_RSBKREQUEST"
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRSM1" - in
         "RSSM_UPDATE_RSBKREQUEST".
        The main program was "RSAWBN_START ".
        In the source code you have the termination point in line 117
        of the (Include) program "LRSM1U43".
    Line  SourceCde
       87   call function 'RSSTATMAN_GET_TYPE_FOR_DTA'
       88     exporting
       89       i_dta  = l_dta
       90     importing
       91       e_type = l_dta_type
       92     exceptions
       93       error  = 1
       94       others = 2.
       95   if sy-subrc <> 0.
       96     message id sy-msgid type sy-msgty number sy-msgno
       97             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
       98   endif.
       99   call function 'RSSTATMAN_DELETE_STATUS'
      100     exporting
      101       i_dta      = l_dta
      102       i_dta_type = l_dta_type
      103       i_process  = 'ALL'.
      104
      105   sort l_t_iccont by rnsidlast ascending.
      106   loop at l_t_iccont.
      107     data: l_s_reqdone like rsreqdone.
      108     select single * from rsreqdone into l_s_reqdone where
      109            rnr = l_t_iccont-rnr.
      110     if sy-subrc <> 0.
      111       read table l_h_dtpreq with key
      112            requid = l_t_iccont-rnsidlast.
      113       if sy-subrc = 0 and
      114          ( l_h_dtpreq-ustate = '0' or l_h_dtpreq-tstate = '0' ).
      115         clear l_s_reqdone-archived.
      116       else.
    >>>>>         message x000.
       118       endif.
      119     endif.
      120     if l_s_reqdone-archived <> rs_c_false.
      121       call function 'RSREQARCH_RELOAD_REQUEST'
      122         exporting
      123           i_rnr         = l_t_iccont-rnr.
      124     endif.
      125     select single * from rsbkrequest into l_s_req where
      126            requid = l_t_iccont-rnsidlast.
      127     if sy-subrc <> 0.
      128       continue.
      129     endif.
      130
      131     read table l_h_rsbkdtp with table key
      132          dtp = l_s_req-dtp.
      133     if sy-subrc <> 0.
      134       l_h_rsbkdtp-dtp = l_s_req-dtp.
      135       insert table l_h_rsbkdtp.
      136     endif.
    This issue only exists in Production system not QTY or development thr Cube deletion is working fine.
    So far I have tried Deleting Index's and then deleting the Cube Contents & Run Elementary Checks from RSRV but not find any lead yet.Also unable to find appropriate notes for this issue aswell I am using SAP_Bw comp 700 with SP26.
    Any suggestion  would be of great help .
    Thanks & Regards
    Aman

    Hi Ap_SAP & Arvind,
    Any recent upgrades or system refresh done?
    In recent update just from SP24 to SP26 was updated and a DB stats Referesh was carried on.But this proublem existed before these activities.
    Except deleting can you able to perform all other operations like loading data..etc?
    Other than deletion I am able to do load data into cube extract from R3 and also i can delete data from PSA.Only deletion giving dump.
    You are trying to delete transactional or master data.
    I am tring for transaction data.
    WHen I try to delete request by request it also lead to the same short dump.
    @ arvind : I checked Sm12 there i see not table which has been locked.
    Thanks
    Aman

  • While posting the Doc thru GM_CREATE_BUDGET taking to short dump

    while posting the Doc thru GM_CREATE_BUDGET taking to short dump
    giving the message:-
    Runtime Errors         MESSAGE_TYPE_X
    Error analysis
        Short text of error message:
        System error during characteristic derivation maintenance
        Long text of error message:
        Technical information about the message:
        Message class....... "ABADR"
        Number.............. 599
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLABADR
        Include                                 LABADRF01
        Row                                     255
        Module type                             (FORM)
        Module Name                             WORK_AREA  PUT
    225       EXPORTING
    226         i_write_to_tabadrx = 'X'
    227         i_list_access      = buttons-list_access.
    228   ENDIF.
    229 * test mode: spool trace results
    230   IF NOT debug-print_trace IS INITIAL.
    231     CALL FUNCTION 'ABADR_TRACE_WRITE'
    232       EXPORTING
    233         i_write_to_spool = 'X'
    234         i_list_access    = buttons-list_access.
    235   ENDIF.
    236 ENDFORM.                    "trace--show
    237
    238 ----
    239 *       FORM WORK_AREA_DIR--ADD                                       *
    240 ----
    241 *       ........                                                      *
    242 ----
    243 *  ---  I_IDENTIFIER                                                  *
    244 ----
    245 FORM work_area--put USING i_identifier TYPE t_identifier
    246                           i_work_area TYPE any.
    247   DATA: name TYPE t_name.
    248   FIELD-SYMBOLS: <l_work_area> TYPE ANY.
    249
    250   CHECK NOT i_identifier IS INITIAL.
    251 * put item to work area
    252   READ TABLE <strategy>-tab_func_parameters INTO name
    253                          WITH KEY identifier = i_identifier.
    254   IF sy-subrc <> 0.
    >>>     MESSAGE x599(abadr).256   ENDIF.
    257   PERFORM namework_areaassign USING name.
    258 * unicode
    ..........................contd...
    Pls help.

    Hi Victor,
    this is due to the Config issues, just check the config related to the "Settings for Availability Control Ledger" in the Grantee Managment

  • Shot Dump while updating record in ETTIFN using the FM ISU_DB_ETTIFN_UPDATE

    Hi All,
    Am getting shot dump while trying to update an entry in ETTIFN database table using the FM ISU_DB_ETTIFN_UPDATE.
    If this FM fails to update then it tries to  raise error message using the macro 
    MAC_MSG_PUTX CO_MSG_PROGRAMMING_ERROR '016' 'E9'
           'ETTIFN' SPACE SPACE SPACE
           SPACE .
    Runtime Errors         MESSAGE_TYPE_X
    Error analysis
        Short text of error message:
        Error in changing table ETTIFN
        Long text of error message:
         Diagnosis
             An error occurred when one or more table entries were being
             changed. This error was reported by the database system.
         System Response
             The system does not permit changes to one or more table entries.
             It is possible that an SAP short dump has been written from the SAP
             basis system.
         Procedure
             Find out if the SAP short dump provides additional information.
             You can view SAP short dumps using Transaction SM21.
        Technical information about the message:
        Message class....... "E9"
        Number.............. 016
        Variable 1.......... "ETTIFN"
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    Please advice inorder to fix the same.
    Regards,
    Deepthi

    Hi Deepthi,
    Updating database using statement update can give dumps because of below issues:
    "At least one line was not able to be changed, either because no appropriate line was found, or because the change would generate a line that leads to double entries in the primary key or a unique secondary index in the database table."
    I would rather suggest you to call the FM in Mode 'M', i.e. Modify so if entry in table is not there to update, it will insert that record and also won't give dump.
    Thanks.
    Ravi

  • Short Dump when clicking on Reconstruction tab in ODS.

    Hi,
    I get a short dump with 'MESSAGE_TYPE_X' error when I click on the reconstruction tab in ODS
    Error analysis
    "MESSAGE_TYPE_X" " "
      "SAPLRSS2" or "LRSS2U13"
    "RSS2_PSA_NEW_OLD_DS"
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRSS2" - in "RSS2_PSA_NEW_OLD_DS".
        The main program was "RSAWBN_START ".
        In the source code you have the termination point in line 277
        of the (Include) program "LRSS2U13".
    Code
      274             if i_only_active is initial.
      275               clear: l_s_psa_out-psa_tech, l_s_psa_out-psa_version.
      276             else.
    >>>>>               message x000.
      278             endif.
      279           endif.
      280           case l_s_isosmap-issrctype.
    Please let me know how to solve this issue.

    Try checking note 948189.

  • Authorization for RFKK_MASS_ACT_SINGLE_JOB

    Hi guys,
    We have SAP ERP 6.0, we have a mass operation in t-code FPMA (automatic clearing). We have created a role with this t-code and assigned to the user who is supposed to run this t-code. However, each time the job is failing; when we check in SM37, it says job failed...MESSAGE_TYPE_X error etc
    We are currently investigating the possibility of authorization; we believe the user does not have sufficient authorization to run the operation, because when we assign SAP_ALL to him, it works. SU53 does not give anything.
    We would like to know which additional authorization objects we need to include in his role to allow him perform this task?
    Please also note that inside the t-code, it calls the program RFKK_MASS_ACT_SINGLE_JOB.
    Please advise us. Any suggestion would do.
    regards
    BasisIS

    Hi,
    For Tcode FPMA, the objects F_KKKO_BUK, F_KKMA, F_KKSU are being checked for authorization. So, make sure you give correct values for these objects and also as you are saying that this is being scheduled in background make sure that user with whose ID job is scheduled having access to run in background. Check the objects S_BTCH_ADM, S_BTCH_JOB for the same.
    As per my knowledge, for any authorization error for a Tcode or program which is being executed in background it will not show any missing objects in SU53. So, try executing the same in front end first to find out what is missing and after everything is fine schedule the same in background. To find out the authorization issue just create one separate role with that TCode only and assign to the user and start checking with the help of SU53 till you get your desired result.
    Regards,
    Sharath

  • DTP : Moving attribute data from PSA to InfoObject

    I am loading attribute data from a flat file to InfoObject. The data gets to PSA alright but when I create and execute DTP I get an error saying
    Runtime error : MESSAGE_TYPE_X
    Error Analysis  : Join table TESTDATRNRPART0 does not exist.  read SAP note 871084.
    Can someone pls help me trace why I had this error as well as where I can  find SAP note 871084 .
    Thanks.

    Hi Anil,
    Please find  below excerpt of the SAP note you mentioned.
    The system issues a runtime error with X_MESSAGE and error message RSM 073. The message refers to this note.
    Other terms
    RSSM_CHECK_CREATE_JOINTABLES, join tables, dump, short dump, RSM 073
    Reason and Prerequisites
    The problem is caused by a program error.
    Solution
    Execute the RSSM_CHECK_CREATE_JOINTABLES report in your BW system (Transaction SA38 or SE38). The report is delivered with Support Package 5.
    BW 7.0
               Import Support Package 05 for 7.0 (BW7.0 patch 05 or SAPKW70005) into your BW system. The Support Package is available when Note 0829625 "SAPBWNews BW 7.0 Support Package 05", which describes this Support Package in more detail, is released for customers.
    Caution:
    If you have imported Support Package 6 or a higher Support Package in your system, the report is obsolete and the runtime error should no longer occur with message RSM 073 since in this case, the tables TESTDATRNRPART0 to TESTDATRNRPART9 are delivered in the DDIC.
    To provide advance information, the note mentioned above may be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".
    To be able to effect this solution, you need SP5 in BI7.0.
    To check your current system status, go to menu System--->status, on the bottom of the window, beneath the component version field you will see a box with magnifier icon, if you click on it , you will see all the software components that have been installed in your system, here in SAP_BW row you can find the current patch level of your BW component.
    eg: SAPKW70016 here 16 is the patch level. To run the above program , you need patch level above 5.
    Hope it helps,
    Regards,
    Sunmit.

Maybe you are looking for