Error Message types

Hi All,
I have used "Message e000(38) with 'Please Enter valid No'." , Once entered wrong parameter value it used to exit and not again going to selection screen for value reenter. which error messae will go to selection screen again once entered wrong value.

Try syntax:
MESSAGE ID .. TYPE 'S' NUMBER .. DISPLAY LIKE 'E'

Similar Messages

  • Error message type V1212.

    Error message type V1212.
    Please tell me the TCODE where I can see the Error or warnning assigned to this message

    Dear rajsuhas
    Go to SE91, input V1 in "Message class" and 212 in "Number" and execute.
    Now block the first line and press "CntrlShiftF3",  check only  for "Programe" and execute.  Double click on the blank field under the tab "short description".  You can see the codings written there but you are not suppose to change anything there
    thanks
    G. Lakshmipathi

  • Error message type M7093-While posting to Cost center

    Hi All,
    While posting the material to cost center in MB21 201 movement i am getting the following error message :
    Fld selectn for mvmt type /  acct  (G/L accnt no) differs for Business Area
    Message No M7093
    Please help me.
    I am not able to post this document.
    Regards,
    Nagaraj S

    Hi
    Check the field status group assigned to GL account in FS00 and check its assignments in OBC4.
    Also check mvt type settings in OMJJ transaction - 201 mvt - field selelction - additional account assignment (here business area is optional.)
    You need to change either of them. Take help of FI consultant.
    Thanks

  • Error Message type ARTMAS belongs to BAPI in BD64?

    Hi,
    when i want to send ARTICLES using ARTMAS Message Type in BD64 ( Customer Distribution Model ) it shows an error message like below
      " Message type ARTMAS belongs to BAPI
        RetailMaterial.Clone: Use the BAPI in the model "
    but i want use ARTMAS Message Type in BD64.
    Please can anyone tell me how solve this issue.

    I found the sloution.
    First, for our distribution model we add message type still is "MATMAS", and then we should add BAPI as fllow:
    Obj. name/interface:  BUS1001001
    Method: Clone
    We can find these information from table TBDBE.
    Try BD10, it can work.
    I hope it can help other people.

  • IDoc transfer error - Message Type Conversion

    Hi,
    While trying to transfer an IDocs from a 46C system, i get the following STATUS message in transaction BD87
    Message type RPM_TIME could not be converted
    Message no. EA 694
    Diagnosis
    Conversion entry between long and short names missing.
    System Response
    IDoc cannot be processed without this entry.
    Procedure
    Create an appropriate entry for logical message RPM_TIME.
    Could you anyone let me know the reason as to why it occurs.
    Regards,
    Roshith

    The problem is the FM for that action is trying to use a material movement to make the transfer.  You can't use standard material movements to transfer into QI once you have activated any of the materials inspection types.
    What inspection lot is generated by your current action box?  I'm guessing an 89.  I can't remember.
    Have an ABAP'er trace the FM and determine how it is doing the stock transfer.  If it is using a 322 it won't work with QM active.  You will have to have you ABAP'er modify it to use a 311 or 411 which will then use the 08 inspection type.  I suggest you use a copy of 411 or 311 for this.
    Craig

  • It is possible to change any warning message type to error message type?

    Dear All,
    Kindly do your need full efforts to solve this problem;
    For T code iw32, material avaibility checks works but it gives warning message as per error message required at this point.
    It is possible to change that message 281 i.e. Order & has missing parts to an error message rather than a warning message.
    Kindly provide your valueable suggestions regarding it.
    Do tell about any badi or echancement spot or user exits where error message can be incooperated.
    Thanks in advance.
    Regards,
    MAA

    Dear Rohan,
    Problem not facing problem due to any code, i think u r not getting wht i am saying.
    Let me explain in detail.
    While creating order from t code iw31, material avability checks works and it is working fine and generating a warning mess in case of out of stock case. Requirement is to transform that warning mess to error mess.
    Just need to know how can i change standard warning mess to error mess so that error mess displays in place of that warning mess.
    Kindly suggest its solution for it .
    For any query free feel to contact.
    Thanks.
    Regards,
    MAA

  • VF04 - error message types

    Good Afternoon all,
    hopefully i have posted this question in the right section..
    i am trying to comply a list of all the error codes with in the VF04 Function, and was wondering if there is an easier way of getting this information, as currenly i am having to run the report, then go onto each order, to find the code, and the reason, and then log it down.
    if there is away of finding this with in SAP, or does anyone here have a list they could show me.
    your help will be greatfully recieved
    regards
    Jonathan

    Let me start with saying that this requirement is, well, stupid. Even if it was possible to find all possible error messages, 99% of the errors most likely would not even apply to your business.
    Technically, if you've gotten to billing (VF04), there should be no errors at all at that point. I would rather concentrate on refining the process, configuration, etc. to prevent any error, than trying to figure out all "what ifs".
    If you still would like to oursue this meaningless, in my opinion, task, you might want to look at the message class VF in SE91 transaction. Also, you can try searching for MESSAGE command in the main billing program and all sub-programs. Good luck with that.

  • Error message when doing SUBMIT

    Hello there,
    i am just working on BSP pages that call ABAP Reports with "Submit" and display the Results within the BSP.
    My Problem now is that some reports may come up with an Error message (type 'E') that stops the report and the processing of the BSP Page. The page displays then a "500 internal SAP Error".
    I found a good weblog here: /people/mark.finnern/blog/2003/09/16/bsp-in-depth-message-statement-handling but also to encapsulate the Submit by a function call does not help here. The page stops when calling the submit.
    Is it somehow possible to prevent the BSP-Page from terminating and catch the error message from the Report? I can not modify the Reports that are called.
    Thanks for any help,
    Stefan
    6.20 SP49

    Hi Stefan,
    If your report returns the error message or message id, you could pass this on as an export parameter in your wrapping function back to your BSP event.
    To display the error message on the same BSP page, include the following code in the event where err_msg is the error message from your report passed on to the function:
    page->messages->add_message(
    condition = 'REPORTERROR'
    message = err_msg
    severity = page->messages->CO_SEVERITY_ERROR ).
    In the layout of the BSP page include the following code where you want the error message to be displayed:
    <font color="red"><%= page->messages->assert_message( 'REPORTERROR' ) %></font>
    Make sure the condition has exactly the same name in the event and the layout.
    Additionally you could also use the SY-SUBRC after your SUBMIT statement and display a generic message for an internal error if the SUBMIT statement itself fails.
    Regards,
    Rohini.

  • ERROR MESSAGES IN MODULE POOL

    hi experts,
    i ve a query.
    say i am getting an error messages in modulepool, u all knw that if an eeror  occurd flow halt in that particular screen
    nw hw can i get exit from transaction without using, chain-endchain, at exit command, leave prog etc
    plz help, thnx in advance

    hi,
    if you are writing message statement with  type 'E' the write the message statement with  type 'S' display like 'E'. this will display the status messgae as error message and the flow will continue........
    "  for ex.
    " if you write....
    MESSAGE 'ERROR MESSAGE' TYPE 'E'.
    " THEN CHANGE IT TO.....
    MESSAGE 'ERROR MESSAGE' TYPE 'S' DISPLAY LIKE  'E'.
    Regards,
    Siddarth

  • Calc manager: @RETURN function with WARNING as message type issue

    Hi Gurus,
    I m working in version 11.1.2.2 in IE 9. I have created a simple calculation script as below to test the @Return essbase function.
    function
    FIX ( .....)
    "502100"(
    IF( ("YearTotal" > 50000))
    @RETURN("True:test message" , WARNING);
    ELSE
    @RETURN("False:test message" , WARNING);
    ENDIF
    This script validates fine , however when executed on Save of Data Form gives a Job console error with no error code but message as below
    Invalid network data. Type is matched but length is zero. An application protocol error might exist between server and client processes..
    The same script executed using error message type as *"ERROR"* executes successfuly on save of data form and gives exepected custom error message.
    I read a thread in forum saying the @Return function works only with ERROR as message type for vesrion 11.1.2.1
    How to use Essbase @RETURN function to displayed messages in 11.1.2.1
    I have tried using WARNING and INFO , both doesnt seem to work even in 11.1.2.2, Only ERROR as message type works.
    Has anyone experienced the same with version 11.1.2.2 as well? Is this still a bug?
    Please let me know your inputs.
    Thanks
    SN

    Hi,
    I am sorry for the late response!
    Thank you for all your suggestions!
    I had used in the followng way and it resolved my issue.
    SELECT GUID_PRGEN  "Primary Key as GUID in "RAW" Format
             GUID_PR     "Primary Key as GUID in "RAW" Format
             ATTR20A     "SUBSTANCE ID
             ATTR05A     "Materail Type
             ATTR10A     "Materail Group
             ATTR05B     "Sub-Family
             FROM /SAPSLL/PRGEN
             INTO TABLE T_PRGEN
             WHERE ATTR20A IN S_AT20A.
      IF T_PRGEN IS INITIAL.
        MESSAGE : I007(ZMSSG) WITH 'Data not available for this entry'.
        STOP.
      ENDIF.
    Regards,
    Kittu

  • Caller 09 contains an error message

    when i try to load data(full up load) from ODS  to CUBE  i am getting error .Error mesage is the followed,pls suggest me
    The error occurred in Extractor
    Refer to the error message
    Type of error mesage
    You do not have authorization to extract from DataSource 80FIGL_O10, comp. DM
    Message no. R8073
    Diagnosis
    You are not authorized to extract from DataSource 80FIGL_O10 in application component: DM .
    System Response
    The authorization check was performed with the following field values:
    u2022     DataSource: 80FIGL_O10
    u2022     Application component: DM
    u2022     Subobject: DATA
    u2022     Activity: 03
    Procedure
    To be able to extract from the DataSource, you need authorization for authorization object S_RO_OSOA (authorizations SAPI-DataSource) with the field values specified above.
    Procedure for System Administration
    There is a role template S_RO_OSOA_TMPL (DataSource (OSOA) Display/Maintain/Extract) available that contains the authorizations to display, change and extract all DataSources.
    Thanks
    chandra

    Hi Chandra Obula Reddy,
    The message clearly showing you are not authorized to do extraction.in that message only given procedure to do that.
    Procedure for System Administration
    There is a role template S_RO_OSOA_TMPL (DataSource (OSOA) Display/Maintain/Extract) available that contains the authorizations to display, change and extract all DataSources.
    Try this otherwise take help from BASIS people.
    Regards
    Pcrao.

  • Message type " " is unknown

    Hi Masters
               When i try to cancel the subcontracting challan in T code J1IF13, it throws a run time error "Message type " " is unknown" .We discussed with the ABAPer regarding this error.He told that we have to maintain the message type in configuration.  Where to maintain the message type for subcontracting challan?
    Regards
    Mohanraj.C

    Use
    The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
    The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
    Requirements
    Before you continue with this activity, work through the following activities:
    Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
    For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
    Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Maintain Output Types.
    Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
    Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Assign Forms and Programs.
    Maintain the Program, FORM routine, and the form for the output type.
    Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Printer Determination -> Printer Determination by Plant / Storage Location.
    Enter the output device that you use.

  • Distributing message type MATQM using ALE

    Hi everybody!
    I am using ALE to distribute material data. This already works. Now I also want to distribute material data for quality management.
    When I try to distribute materials using BD10 I get this message:
    Could not determine recipients for message type MATQM
    So I tried to create a new distribution model for MATQM using BD64. Unfortunately I could not choose MATQM or MATQM01 as the message type. (Error: Message type MATQM01 unknown)
    However, in transaction WE60 I can display message type MATQM01.
    What is the problem?
    best regards
    Roland

    Hi Roland,
    BD10 only can be used with message type MATMAS.
    If you want to send message type MATQM and IDoc type, please use this FM <b>MASTERIDOC_CREATE_SMD_MATQM</b>. You still need to maintain partner profile (WE20) and IDoc Port (WE21).
    Other you can use <b>Change Pointer</b> (BD21) to send out and ensure you have activated the change pointer for message type MATQM (BD50).
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • RFC dump : 'Message type " " is unknown.'

    Hi everyone,
    I am calling an RFC from one system to another and i am getting a dump with error :
    Message type " " is unknown.
    When i debugged the program the found that nothing is returned for " MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. "
    What should i do to rectify the problems? Please do help.
    Thanks In Advance.
    Regards,
    Heera

    ABAP runtime errors    MESSAGE_TYPE_UNKNOWN
           Occurred on     03/05/2008 at 21:56:28
    Message type " " is unknown.
    What happened?
    The current ABAP/4 program "Y_MM_C_CICS_MAT_RECON " h
    because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 progra
    What can you do?
    Print out the error message (using the "Print" functi
    and make a note of the actions and input that caused
    error.
    To resolve the problem, contact your
    SAP system administrator.
    You can print this message by choosing "Print".
    Transaction ST22 allows you to display and manage sho
    is especially useful if you want to keep a particular
    Error analysis
    Only message types A, E, I, W, S and X are allowed.
    How to correct the error
    If the error is in one of your own ABAP programs or an SAP program that
    you have modified, try to correct it.
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "MESSAGE_TYPE_UNKNOWN"
    "Y_MM_C_CICS_MAT_RECON " bzw. "Y_MM_C_CICS_MAT_RECON "
    "START-OF-SELECTION"
    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.............. "46B"
    Application server....... "fmsap591"
    Network address.......... "10.19.196.114"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "2x IA64 Level 3"
    Database server.......... "FMSAP591"
    Database type............ "ORACLE"
    Database name............ "AI0"
    Database owner........... "SAPR3"
    Character set............ "English_United State"
    SAP kernel............... "46D"
    Created on............... "Jul 30 2007 00:11:29"
    Created in............... "NT 5.0 2195 Service Pack 2 x8
    Database version......... "OCI_920_SHARE__OCI_7_API "
    Patch level.............. "2335"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.0.5.., ORACLE 8.0.
    8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 1
    SAP database version..... "46D"
    Operating system......... "Windows NT 4.0, Windows NT 5.
    Windows NT 5.2, , System build information:,
                                          , LCHN : 921411"
    User, transaction...
    Client.............. 250
    User................ "HPRAMANX"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "Y_MM_C_CICS_MAT_RECON "
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "Y_MM_C_CICS_MAT_RECON " in
    "START-OF-SELECTION".
    The main program was "Y_MM_C_CICS_MAT_RECON ".
    The termination occurred in line 371
    of the source code of program "Y_MM_C_CICS_MAT_RECON " (when calling the editor
    3710).
    Source code extract
    003410       r_lgort-sign = 'I'.
    003420       r_lgort-option = 'EQ'.
    003430       r_lgort-low = x_storeloc_wa-ecc_st_locn.
    003440       APPEND r_lgort.
    003450     ENDLOOP.
    003460
    003470
    003480   *CALL RFC TO GET MATERIAL DATA FROM F PIPE BY PASSING S_MATNR r_werks
    003490   *r_lgort S_CHARG AND GETTING THE REQUIRED DATA BACK IN THE TABLE
    003500   *I_MCHBF
    003510
    003520     CALL FUNCTION 'YCICS_MATERIALDATA'
    003530     DESTINATION 'FI0250'
    003540          TABLES
    003550               i_matnr                        = s_matnr
    003560               i_werks                        = r_werks
    003570               i_lgort                        = r_lgort
    003580               i_charg                        = s_charg
    003590               i_mchb                         = i_mchbf
    003600          EXCEPTIONS
    003610               no_data_found                  = 1
    003620               material_not_of_type_fert      = 2
    003630               invalid_plant_entry            = 3
    003640               invalid_stloc_entry            = 4
    003650               invalid_plnt_matnr_combi       = 5
    003660               invalid_plnt_matnr_batch_combi = 6
    003670               invalid_plnt_matnr_batch_stloc = 7
    003680               OTHERS                         = 8.
    003690     IF sy-subrc <> 0.
    003700    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         >            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    003720     ENDIF.
    003730
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 1                             SY-INDEX 0
    SY-TABIX 1                             SY-DBCNT 31
    SY-FDPOS 0                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1
    Chosen variables
    Name.......................... Contents.1........2........3....+....4
    VARI
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40                                          ####00000000000000
                                   2222222222222222222200003333333333333322
                                   0000000000000000000000000000000000000000
    ... +  80                          ####################################
                                   2222000000000000000000000000000000000000
                                   0000000000000000000000000000000000000000
    ... + 120                      ########################################
                                   00000000
                                   0000000
    SY-MSGV1
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222
                                   0000000000
    SY-MSGV2
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222
                                  0000000000
    Y-MSGV3
                                  2222222222222222222222222222222222222222
                                  0000000000000000000000000000000000000000
    .. +  40
                                  2222222222
                                  0000000000
    Y-MSGV4
                                  2222222222222222222222222222222222222222
                                  0000000000000000000000000000000000000000
    .. +  40
                                  2222222222
                                  0000000000
    _MCHB                         ####################################‘###
                                  0000000000000000000000000000900000009000
                                  0000000000000000000000004000060000001000
    .. +  40                      ####0###0#######ÿÿÿÿ:###########è ƒ####
                                  1000300030000000FFFF300000000000EA280000
                                  0000020001000000FFFFA000200043008D030000
    .. +  80                      x> ƒ####################################
                                  7328000000000000000000000000000000000000
                                  8E03000000000000000000000000000000000000
    .. + 120                      ########################(#######
                                  00000000
                                  0000000
    MCHBWA                      000000000000895405CR01CRA10001    CR01TE
                                  3333333333333333334533454333332222453354
                                  0000000000008954053201321100010000320145
    .. +  40                      ST05####e#########
                                  553300006000000000
                                  3405000150C000000C
    SCHARG_%_APP_%              S_CHARG S_CHARG                       to
                                  5544454255444542222222222222222222222276
                                  3F3812703F38127000000000000000000000004F
    .. +  40
                                  2222222222222222222222222222222222222222
                                  0000000000000000000000000000000000000000
    .. +  80                         @1FQMultiple selection@
                                  2224345547676766276666766642222222222222
                                  000016C1D5C490C5035C5349FE00000000000000
    .. + 120
                                   222
                                   000
    X_MCHBF_WA
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40                      00000000            00000000
                                   3333333322222222222233333333222222222222
                                   0000000000000000000000000000000000000000
    ... +  80                      000000 #################################
                                   3333332000000000000000000000000000000000
                                   0000000000000C000000C000000C000000C00000
    ... + 120                      ########################################
                                   00000000
                                   0C00000
    I_MCHBF                        ################@#######################
                                   0000000000000000400000000000100000000000
                                   1000400040004000080050004000080000000000
    ... +  40                      ################ÿÿÿÿÓ###################
                                   1000000000000000FFFFD0000000000000000000
                                   0000000000000000FFFF30007000630000000000
    ... +  80                      ########################################
                                   0000000000000000000000000000000000000000
                                   0000000000000000000000000000000000000000
    ... + 120                      ########################8#######
                                   00000000
                                   0000000
    SYST                           ########################################
                                   0000000000000000000000000000000000000000
                                   0000000010000000000000000000000000000000
    ... +  40                      ####################ã###################
                                   10000000000000000000E0000000000000000000
                                   F00000001000000010003000000000000000F000
    ... +  80                      ########################################
                                   0000000000000000000000000000000000000000
                                   0000000000001000800000000000000000000000
    ... + 120                      ####################################š###
                                   00000000
                                   0000000
    X_MKPFMSEG_WA-BKTXT
                                   2222222222222222222222222
                                   0000000000000000000000000
    %_SPACE
                                   0
                                   0
    X_OUTPUT_WA-BTEXT
                                   22222222222222222222
                                   00000000000000000000
    X_MCHB_WA-MATNR                000000000000895405
                                   333333333333333333
                                   000000000000895405
    X_MKPFMSEG_WA-WERKS
                                   2222
                                   0000
    X_MCHB_WA-WERKSF               CRA1
                                   4543
                                   3211
    X_OUTPUT_WA-WERKS
                                   2222
                                   0000
    X_MCHB_WA-LGORTF
                                   2222
                                   0000
    X_MKPFMSEG_WA-LGORT
                                   2222
                                   0000
    X_MCHB_WA-CHARG                CR01TEST05
                                   4533545533
                                   3201453405
    Active calls / events
    No.... Type........ Name..........................
           Programm
           Include                                  Line
         1 EVENT        START-OF-SELECTION
           Y_MM_C_CICS_MAT_RECON
           Y_MM_C_CICS_MAT_RECON                      371
    Internal notes
    The termination occurred in the function "ab_jmess" of the SAP
    Basis System, specifically in line 1083 of the module
    "//bas/46D/src/krn/runt/abdynpro.c#22".
    The internal operation just processed is "MESS".
    The internal session was started at 20080305215621.
    Active calls in SAP kernel
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=24072)
    When      : 3/5/2008 21:56:28.0
    Threads   : 2
    Computer Name       : FMSAP591
    User Name           : ai0adm
    Number of Processors: 2
    Processor Type: ia64 Family 31 Model 1 Stepping 5
    Windows Version     : 5.2 Current Build: 3790
    Stack Dump for Thread Id 56f4
    FramePtr         ReturnAd         Param#1          Function Name
    00000000083a0c00 0000000076eab530 00000000000024f4 kernel32!GetDateFormatW
    00000000083a0bd8 000000000215a7c0 00000000000024f4 kernel32!GetDateFormatW
    00000000083a0b88 000000000067fe80 0000000000000080 disp+work!
    000000001c1b0040 0000000076ea7420 0000000000212e50 MSVCRT!tanhf
    000000001c1b0000 0000000000000000 000006fb7eb36e88 kernel32!GetDateFormatW

  • Message type " " is unknown. Transaction J1IF13

    Dear all,
    When i am executing transaction J1IF13 for Subcontracting i am getting this error "Message type " " is unknown."
    i want to cancel the transaction
    Regards
    Amey

    Closed

Maybe you are looking for