Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
    Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
   Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

Similar Messages

  • Need sample programs for inbound & outbound interfaces in abap hr?

    hi friends
    i need sample programs for inbound & outbound interface programs in hr abap . any one send me pls
    thanks & regards
    deepurd

    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    *& Report ZPROG65_11 *
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    REPORT zprog65_11 .
    TABLES : lfa1.
    TYPES : BEGIN OF ven ,
    lifnr LIKE rf02k-lifnr,
    bukrs LIKE rf02k-bukrs ,
    ekorg LIKE rf02k-ekorg,
    ktokk LIKE rf02k-ktokk,
    name1 LIKE lfa1-name1,
    sortl LIKE lfa1-sortl,
    land1 LIKE lfa1-land1,
    spars LIKE lfa1-spras,
    akont LIKE lfb1-akont,
    fdgrv LIKE lfb1-fdgrv,
    waers LIKE lfm1-waers,
    anred LIKE lfa1-anred ,
    END OF ven .
    DATA : t_ven TYPE TABLE OF ven WITH HEADER LINE ,
    t_bdc LIKE TABLE OF bdcdata WITH HEADER LINE .
    DATA : v_file TYPE string ,
    v_temp TYPE i ,
    v_lifnr(10) TYPE n,
    v_hdate LIKE sy-datum.
    DATA : c_tcode LIKE sy-tcode .u201Dvalue u2018XK01u2032.
    PARAMETERS : p_file(30) DEFAULT u2018c:\vendor1_11.txtu2019,
    p_group LIKE apqi-groupid.
    START-OF-SELECTION .
    MOVE p_file TO v_file .
    PERFORM file_upload TABLES t_ven USING v_file .
    v_hdate = sy-datum - 1.
    CALL FUNCTION u2018BDC_OPEN_GROUPu2019
    EXPORTING
    client = sy-mandt
    DEST = FILLER8
    group = p_group
    holddate = v_hdate
    keep = u2018Xu2019
    user = sy-uname
    IMPORTING
    QID =
    EXCEPTIONS
    client_invalid = 1
    destination_invalid = 2
    group_invalid = 3
    OTHERS = 11
    IF sy-subrc 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    LOOP AT t_ven .
    clear lfa1.
    v_temp = 0.
    MOVE t_ven-lifnr TO v_lifnr.
    SELECT SINGLE * FROM lfa1 INTO lfa1 WHERE lifnr =
    v_lifnr.
    IF sy-subrc = 0.
    WRITE :/ u2018foundu2019.
    v_temp = 1.
    else.
    write: / u2018not foundu2019.
    ENDIF.
    IF v_temp = 0.
    c_tcode = u2018xk01u2032.
    PERFORM fill_ddc_table .
    ELSEIF v_temp = 1.
    c_tcode = u2018xk02u2032.
    PERFORM fill_bdc_table .
    ENDIF.
    CALL FUNCTION u2018BDC_INSERTu2019
    EXPORTING
    tcode = c_tcode
    TABLES
    dynprotab = t_bdc
    EXCEPTIONS
    internal_error = 1
    OTHERS = 7.
    REFRESH t_bdc .
    ENDLOOP .
    CALL FUNCTION u2018BDC_CLOSE_GROUPu2019
    EXCEPTIONS
    not_open = 1
    queue_error = 2
    OTHERS = 3.
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    *& Form file_upload
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    text
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
    u2013>P_T_VEN text
    u2013>P_V_FILE text
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
    FORM file_upload TABLES p_tven STRUCTURE t_ven
    USING p_vfile.
    CALL FUNCTION u2018GUI_UPLOADu2019
    EXPORTING
    filename = p_vfile
    filetype = u2018ASCu2019
    has_field_separator = u2018Xu2019
    IMPORTING
    FILELENGTH =
    HEADER =
    TABLES
    data_tab = p_tven
    EXCEPTIONS
    file_open_error = 1
    file_read_error = 2
    OTHERS = 17
    IF sy-subrc 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. u201D file_upload
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    *& Form FILL_DDC_TABLE
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    text
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
    u2013> p1 text
    <u2013 p2 text
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
    FORM fill_ddc_table .
    SCREN 100
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180100u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-LIFNRu2019.
    t_bdc-fval = t_ven-lifnr .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-BUKRSu2019.
    t_bdc-fval = t_ven-bukrs.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-EKORGu2019.
    t_bdc-fval = t_ven-ekorg.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-KTOKKu2019.
    t_bdc-fval = t_ven-ktokk.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    110
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180110u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-NAME1u2032.
    t_bdc-fval = t_ven-name1 .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-SORTLu2019.
    t_bdc-fval = t_ven-sortl.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-LAND1u2032.
    t_bdc-fval = t_ven-land1.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-SPRASu2019.
    t_bdc-fval = t_ven-spars.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    120
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180120u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    130
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180130u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018=ENTRu2019.
    APPEND t_bdc. CLEAR t_bdc.
    210
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180210u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFB1-AKONTu2019.
    t_bdc-fval = t_ven-akont .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFB1-FDGRVu2019.
    t_bdc-fval = t_ven-fdgrv.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    215
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180215u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    220
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180220u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    310
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180310u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFM1-WAERSu2019.
    t_bdc-fval = t_ven-waers .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    320
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180320u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018=UPDAu2019.
    APPEND t_bdc. CLEAR t_bdc.
    ENDFORM. u201CFILL_DDC_TABLE
    u201D FILL_DDC_TABLE
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    *& Form FILL_BDC_TABLE
    &u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
    text
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
    u2013> p1 text
    <u2013 p2 text
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
    FORM fill_bdc_table .
    SCREN 101
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180101u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-LIFNRu2019.
    t_bdc-fval = t_ven-lifnr .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-BUKRSu2019.
    t_bdc-fval = t_ven-bukrs.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018RF02K-EKORGu2019.
    t_bdc-fval = t_ven-ekorg.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    110
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180110u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018lfa1-anredu2019.
    t_bdc-fval = t_ven-anred .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-NAME1u2032.
    t_bdc-fval = t_ven-name1 .
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-SORTLu2019.
    t_bdc-fval = t_ven-sortl.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-LAND1u2032.
    t_bdc-fval = t_ven-land1.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018LFA1-SPRASu2019.
    t_bdc-fval = t_ven-spars.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018/00u2032.
    APPEND t_bdc. CLEAR t_bdc.
    300
    t_bdc-program = u2018SAPMF02Ku2019.
    t_bdc-dynpro = u20180300u2032.
    t_bdc-dynbegin = u2018Xu2019.
    APPEND t_bdc. CLEAR t_bdc.
    t_bdc-fnam = u2018BDC_OKCODEu2019.
    t_bdc-fval = u2018=YESu2019.
    APPEND t_bdc. CLEAR t_bdc.
    ENDFORM. u201D FILL_BDC_TABLE
    Best Regards

  • How configure a Logical System (XI) as receiver for an Outbound Idoc?

    Hi all,
    How can I configure a Logical System (XI) as receiver for an Outbound Idoc?
    Points will be given,
    Regards,
    Daniela

    hi,
    it all depends on what kind of document you need to send to XI
    if you want to send some logistic documents (like orders, deliveries etc)
    have a look at my book - where you will find step by step guides
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    then you will undestand where to change to get it send via LS
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Standard program for creating outbound IDoc holding wbs+cost plan

    Hello,
    a)
    Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
    b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
    Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
    Kind regards
    Viveka Schwartz

    Hi Frank,
    Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
    Reg
    Dsk
    Edited by: DSk on Sep 14, 2010 3:44 PM

  • Standard program for creating outbound IDoc including wbs + cost planning

    Hello,
    a)
    Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
    b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
    Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
    Kind regards
    Viveka Schwartz

    Hi Frank,
    Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
    Reg
    Dsk
    Edited by: DSk on Sep 14, 2010 3:44 PM

  • AS2(SOA-B2B) Channel Setup for Inbound/Outbound

    Hi
    Can anyone share a document on how to setup AS2(SOA-B2B) Channel Setup for Inbound/Outbound? We are trying to configure AS2 (SSL), but test with partner is failing.. any document would help...
    Appreciate your help
    --Sri

    One options is to use a java callout in the inbound agreement.
    Ismail M.

  • Creation of Inbound Idoc for the Outbound Idoc in same client

    Hi,
    My requirement:
    Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
    It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
    I found there is a field for function module in WE21,can this be used to get the requirement done.
    Please suggest.
    Regards,
    Amar

    Example of a program that create and post an inbound idoc....maybe that will help you:
    report  zzinbound_idoc.
    data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
    data: g_edidd like edi_dd40 occurs 0 with header line.
    data: g_e1bpache09 like e1bpache09.
    parameter: mode type c default 'A'.
    refresh: g_idoc_control_record, g_edidd.
    clear:   g_idoc_control_record, g_edidd.
    *-Build Control Record -*
    g_idoc_control_record-mestyp  = 'ACC_DOCUMENT'.   "Message type
    g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
    g_idoc_control_record-direct  = '2'.              "Direction
    * Receiver
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
        g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-rcvprt = 'LS'.             "Partner type
    g_idoc_control_record-rcvpfc = ''.               "Partner function
    * Sender
    g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-sndprt = 'LS'.             "Partner type
    g_idoc_control_record-sndpfc = ''.               "Partner function
    g_idoc_control_record-refmes = 'Customer clearing'.
    append g_idoc_control_record.
    *-Build Idoc Segments -*
    *---E1KOMG
    clear g_edidd.
    clear g_e1bpache09.
    g_edidd-segnam               = 'E1BPACHE09'.
    g_edidd-segnum               = 1.
    move g_e1bpache09 to g_edidd-sdata.
    append g_edidd.
    *-Create idoc -*
    *-Syncronous
    if mode = 'S'.
      call function 'IDOC_INBOUND_SINGLE'
        exporting
          pi_idoc_control_rec_40              = g_idoc_control_record
    *     PI_DO_COMMIT                        = 'X'
    *   IMPORTING
    *     PE_IDOC_NUMBER                      =
    *     PE_ERROR_PRIOR_TO_APPLICATION       =
        tables
          pt_idoc_data_records_40             = g_edidd
        exceptions
          idoc_not_saved                      = 1
          others                              = 2.
      if sy-subrc <> 0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.
    *-Asynchronus
    else.
      call function 'IDOC_INBOUND_ASYNCHRONOUS'
        in background task as separate unit
        tables
          idoc_control_rec_40 = g_idoc_control_record
          idoc_data_rec_40    = g_edidd.
      commit work.
    endif.
    write: / 'Well done!'.

  • Change tax code for Inbound invoice Idoc

    Hi all,
    My requirement is to change the TAX code in INVOIC01 for inbound idoc ,Basic type in E1EDK04 segment.
    I am using exit EXIT_SAPLMRMH_012 .
    But change tax code is not refleted in IDOC segment.
    Even i put E_CHANGE = 'X'.
    Please any one who have donne this before help me its urgent.

    I got the answer. Actually I should be marking this item as Excise item in Item master which i missed out.
    Thanks.

  • Transaction codes for inbound/outbound of ALE-ITS URGENT

    Hi All,
    antbody can plz tell me the transaction codes for inbound and outbound process and also plz tell me ALE Message T-Codes.
    Thanks,
    Maheedhar.T

    Under the WEDI and BALE, area menus you will be able to find all the transaction codes pertaining to the ALE.
    SALE, WE30, WE31, WE20, WE02, WE21, WE81, WE82, WE41, WE42 etc are the transactins that will help you in configuring ALE.
    Regards,
    Ravi
    Note- Please mark all the helpful answers

  • FM for ORDERS05 Outbound Idoc.

    Hi,
    I have to post an idoc of basic type ORDERS05 from a custom program.
    I have populated the fields for control header and the data section of the idoc.I tried using the FM IDOC_OUTPUT_ORDERS to post the idoc,but when I went and checked in WE05,there were no idoc created.I don't understand why the idoc's are not been created.Could you help me in knowing how to use the FM IDOC_OUTPUT_ORDERS or if there are any other FM's to post an outbound idoc.
    Please reply asap.
    Thanks,
    Sandeep.

    Hi,
    There is a exit in the FM IDOC_OUTPUT_ORDERS line no 50... double click on the '001' it will take u to the Function Module EXIT_SAPLEINM_001... there click on the Zprogram ...
    The FM has EKKO table fields has a Impirting parameter .
    u write a code in that Z include program
    u have to call the FM MASTER_IDOC_DISTRIBUTE in the program
    which creates the IDOC
    Thanks,
    Manjunath MS

  • ALE settings for MIRO outbound IDOC

    PLz tell Output Type, Process Code etc...for MIRO outbound.
    for inbound i am using INVOIC01..
    Thanks and regards

    Hi madan,
         u can use the transaction NACE to find out the output type of MIRO.
    If u know the function module u can able to find the process code easily.
    Since function module names are based on message types.
    Regards...
    Arun.

  • Steps for configuring Outbound Idoc OILSHI01

    Hi experts,
        can anybody tell me the steps how to configure an Outbound IDOC.
        It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
        if not anything else will also do.
        Kindly give me steps in detailed. Since i have never done this. Including 
        distribution modle (BD64). in which case it generates the Automatic Partner
        profiles.?
    <REMOVED BY MODERATOR>
    Regards,
    Umesh
    Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

    Hi Umesh,
    Sorry for the late reply. Let me clear your couple of misconceptions first.
    Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
    Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
    Now the further steps:
    Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
    However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
    1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
    2. Again, ask your functional consultant, as to which output type is configured for your  business transaction. Select that output type and go to "Processing routines".
    3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
    4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
    There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc. 
    Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
         a. trigger the idoc on saving the doucment.  this triggers idoc as soon as you save the idoc.
         b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
         c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
    Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
    Hope this was helpful.
    <REMOVED BY MODERATOR>
    Cheers,
    Karan
    Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

  • BADI for PO OUTBOUND IDOC

    Hello Experts,
    Please help me out finding a suitable <b>BADI</b> for T code: ME21N
    <b>OUTBOUND IDOC</b>.
    Scenario:
    <b>I have to populate a "Z" segment while creating an IDOC in ME21N.</b> for this I require a BADI.
    I have tried using FM: <b>idoc_output_orders</b>
    Form Routine <b>fuellen_idoc_inttab.</b>
    but ME21N doesn't execute it at all !!!
    I have set my Output Type to EDI with the Valid Settings
    when ever i create a PO it creates an IDOC but it doesn't execute FM <b>idoc_output_orders</b>
    Thanks in Advance!!!
    R

    Hi,
    Below steps for your reference.
    1.M/59   Define Condition Tables
    2.M/50   Define Access Sequences
    3.NACT  Define Message Types
    4.Set up fine-tuned control for each message type
    5. NACZ  Define Message determination shemas
    6.NACR   Define Condition Records
    Regards.
    David.

  • Mandatory fields for inbound delivery idocs

    hi all
    i want to generate inbound idocs for inbound delivery ASN
    i am using message type DESADV and idoc type /AFS/DELVRY03
    in order to generate inbound idoc what are mandatory values i have to pass to the idocs
    thanks
    Anil

    HI,
    I created inbound idoc for ASN Inbound delivery in test mode we19
    i got idoc with status 62, when i am trying to process the idoc in bd87, its allowing me
    is there any other way to process the idocs , so that status will be 53
    thanks

  • Call Master_idoc_distribute for collective outbound idocs

    Hi All,
    I want to process outbound idocs (4 idocs collectively) using master_idoc_distribute FM. I am calling master_idoc_distribute inside a FM and assigned it to process code outbound. It is working for one idoc but not for 4 idocs.
    How can i call the master_idoc_distribute for sending out 4 idocs one at a time.
    Thanks

    Ok. I guess the requirement was wrongly typed. Ok here is the requirement.
    I basically want to take a collective idoc in R/3 and cal master_idoc_distribute to create and send idocs. This is my collective idoc structure.
    EDIDC
    --+ E1STZUM
    --+ E1STZUM
    where 'E1STZUM' repeats for each idocs. In the above structure, there are two idocs in one idoc which is a collective idoc.  So i want to write a logic to take the first segment E1STZUM and call master_idoc_distribute and then call the second segment E1STZUM and call master_idoc_distribute FM again and so on depends on how many segments. How can i write a logic to loop at idoc_data and call FM master_idoc_distribute. I am not a core ABAP programer. So pls do send me sample code with comments if possible.
    Thanks  a lot.

Maybe you are looking for

  • Is there a way of combining From and To columns in Mail?

    I've just tumbled to the fact that Mail displays separate From and To columns--rather than an integrated Who or Correspondent one. In Thunderbird, with the add on Show InOut, or in the venerable Eudora, by default, there is a single column that shows

  • Start a call with a list with one click

    Hello. Don't know whether this is the right place, but: i've just created a list in Skype. What i hoped to do, is start a call with all the people in that list with one click. I'm using Skype on Mac/OSX, and can't find such an option (right clicking

  • Photo set on Desktop is too zoomed in

    Hello, When I try to set a a photo as my desk top image it comes out very zoomed in...quite beyond merely fitting to screen. Is it something to do with my wide screen? It even does this with 16:9 photos. Thanks for any help in advance. W

  • Sync info and shutdown info needed, thanks

    Hello, I just purchased my first ipod touch & I love it, except for 2 problems: (1) Every time I sync it with itunes, the clock and the date always get reset/changed. When I go into settings to change it back it reads Chicago for the time zone and Se

  • What kind of cell library does opensparc T1 verilog code use?

    Hi all I am running simulations on the instruction fetching unit module of opensparc T1 recently, when I tried to simulate the module with VCS from (synopsys), it has some errors below Error-[URMI] Instances with unresolved modules remain in the desi