Suppressing Output for Purchase Order changes to Vendors

Hi There,
Can someone please advice what is the best way to supress an output to a vendor that only relates to changes made to a Purchase Order. We need to limit this suppression to one document type.
Any help appreciated.
Many Thanks
Uzzy

Normally you can define requirements routines. There you could e.g. check for document type and for the transaction code (SY-TCODE). From the transaction code it should be possible to see if the documnet is created or changed.

Similar Messages

  • Incorrect message type in IDOC for Purchase order change

    Hi Gurus.
    Please advise on below.
    We have several purchase orders that are configured to trigger IDOC upon change. But accidentally, someone has deactiveted the automatic proposal of EDI message type for these Purchase orders which resulted to not transmitting purchase order change documents automatically.
    As a workaround, we have proposed to create EDI message manually during Purchase order change. But upon checking in tcode WE09, message type is ORDERS which is PO create instead if ORDCHG for purchase order change.
    Please kindly advice on why it is behaving like this for purchase orders with EDI message previously deactivated.
    Thanks in advance.
    Acel.
    To simulate.
    Create PO. go to messages, select EDI message then deactivate permanently. Save PO. Release PO if needed. Change PO. go to messages, EDI is not automatically proposed. create EDI message mamanually. Save PO. Release PO id needed. check tcode WE09, for PO create, no IDOC since it was deactivated permanently. For PO change, IDOC was triggered but with incorrect message type ORDERS instead of ORDCHG.

    Hi Acel,
    You will need to check the settings in transaction WE20 - You will be using a Partner Profile to determine the outbound message, either for each vendor or a generic one.
    on the outbound parameters, you will need to ensure that ORDCHG is set up as a message type. If not, add it, ensuring that you use the message ORDCHG, the basic type (or extension) that you are using, usually ORDERS05 and make sure that in message control, you have process code ME02 set up. This should enable the correct message type to be determined.
    Regards,
    Rob

  • What Message type and Process Code to use for Purchase Order Change in 4.6C

    I like to implement in SAP R/3 4.6C a scenario for Purchase Order Change, via inbound IDoc.
    I have been searching, but could not find what Message Type, Idoc Basic Type and Process Code to use.
    I can not imagine this functionality does not exist in 4.6C.
    Any suggestions for my problem are welcome.

    Hello,
    In this case you should use the message PORDCH and BAPI method BAPI_PO_CHANGE but only exist as of release 4.7.
    Function module    BAPI_IDOC_INPUT1
    Idoc Type              PORDCH01
    Message Type      PORDCH
    So check carefully the following OSS notes:
      [Notes 589066 - BAPI_PO_CHANGE: Incorrect account assignment to network |https://service.sap.com/sap/support/notes/589066] (not be fooled by the description)
    [ Notes 197958 - BAPIs for purchase orders - Missing Functions|https://service.sap.com/sap/support/notes/197958]
    Regards,
    Andrea
    Edited by: Andrea Olivieri on Sep 3, 2009 10:17 AM

  • Is there any function module for purchase order change

    Hi Experts,
    Is there any function module for purchase order change or i need to do new recording in me22n.
    Thanks,
    Senthil

    Hi
    Function module <b>BAPI_PO_CHANGE</b> enables you to change purchase orders. The Change method uses the technology behind transaction ME22N.
    Regards,
    Viven

  • Processing log output for Purchase order

    Dear All,
    Iam getting some problem when iam creating an IDOC and checking in the Processing log for IDOC number.
    Actually i had created one custom idoc for Purchase order since my client need only some field and in one line for header and line item, I had done it and i can see it in sdata of EDIDD structure. When i create a Purchase order and save it an idoc number is posting and I can see this file in my physical directory indeed.
    Now when iam going into change mode of PO ME22n to see the Processing LOG, It is not showing the IDOC Number in Purchase order output processing log popup.

    The processing log will only show output based standard output control (Table NAST).
    How is your IDoc being created. Via a user exit, BADI. If so then they will not appear on the processing log.
    It is being created as a custom IDOC for which i had written a Z function module and given that in PO processing code which is ME10. When iam checking the standard IDOC for PO it is generating the IDOC in processing log as well.
    Iam just placing my code just have a look at it and suggest if any thing needs to be done.
    FUNCTION Z_IDOC_OUTPUT_ORDERS.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(OBJECT) LIKE  NAST STRUCTURE  NAST
    *"     VALUE(CONTROL_RECORD_IN) LIKE  EDIDC STRUCTURE  EDIDC
    *"  EXPORTING
    *"     VALUE(OBJECT_TYPE) LIKE  WFAS1-ASGTP
    *"     VALUE(CONTROL_RECORD_OUT) LIKE  EDIDC STRUCTURE  EDIDC
    *"  TABLES
    *"      INT_EDIDD STRUCTURE  EDIDD
    *"  EXCEPTIONS
    *"      ERROR_MESSAGE_RECEIVED
    *"      DATA_NOT_RELEVANT_FOR_SENDING
    DATA: xdruvo.                          "Druckvorgang
    DATA: neu  VALUE '1',                  "Neudruck
          h_kappl LIKE nast-kappl,         "Hilfsfeld Applikation
          h_parvw LIKE ekpa-parvw,         "Hilfsfeld Partnerrolle
          h_ebeln LIKE ekko-ebeln.         "Hilfsfeld Belegnummer
      CLEAR control_record_out.
       xdruvo = neu.
      h_kappl = object-kappl.
      h_ebeln = object-objky.
      h_parvw = object-parvw.
      DATA:
           LT_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
             L_EDIDC LIKE EDIDC,
             L_SEND_FLAG,
             W_SDATA LIKE EDIDD-SDATA.
      DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.
      DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
      DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
      DATA: C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'ZORDER'.
    *- Call function module to determine if message is to be distributed
    OBJECT_TYPE = 'BUS2012'.
      MOVE control_record_in TO control_record_out.
      CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'
        EXPORTING
          MESSAGE_TYPE           = C_MESSAGE_TYPE
        IMPORTING
          IDOC_MUST_BE_SENT      = L_SEND_FLAG.
       EXCEPTIONS
         OWN_SYSTEM_NOT_DEFINED = 1
         OTHERS                 = 2.
      DATA : BEGIN OF EKKO_tAB OCCURS 0,
      EBELN LIKE EKKO-EBELN,
      F1 TYPE C VALUE ',',
      BUKRS LIKE EKKO-BUKRS,
      F2 TYPE C VALUE ',',
      BSART LIKE EKKO-BSART,
      F3 TYPE C VALUE ',',
      LIFNR LIKE EKKO-LIFNR,
      F4 TYPE C VALUE ',',
      WAERS LIKE EKKO-WAERS,
      F5 TYPE C VALUE ',',
      BEDAT LIKE EKKO-BEDAT,
      F6 TYPE C VALUE ',',
      WERKS LIKE EKPO-WERKS,
      F7 TYPE C VALUE ',',
      PLIFZ LIKE EKPO-PLIFZ,
      F8 TYPE C VALUE ',',
      EBELP LIKE EKPO-EBELP,
      F9 TYPE C VALUE ',',
      MATNR LIKE EKPO-MATNR,
      F10 TYPE C VALUE ',',
      MENGE LIKE EKPO-MENGE,
      F11 TYPE C VALUE ',',
      MEINS LIKE EKPO-MEINS,
      F12 TYPE C VALUE ',',
      END OF EKKO_TAB.
      DATA SDATA1 LIKE EKKO_tAB OCCURS 0 WITH HEADER LINE.
      DATA EBELN LIKE EKKO-EBELN.
      WRITE OBJECT-OBJKY TO EBELN.
      SELECT T1EBELN T1BUKRS BSART LIFNR WAERS BEDAT  WERKS PLIFZ EBELP MATNR MENGE MEINS
      FROM EKKO AS T1
      INNER JOIN EKPO AS T2 ON T2EBELN = t1EBELN
      INTO CORRESPONDING FIELDS OF TABLE EKKO_tAB
      WHERE
    *T1~KAPPL = 'EF' AND
      T1~EBELN = EBELN.
    *T1~KSCHL = 'YEDI' .
      DATA SDATA LIKE EDIDD-SDATA.
      DATA NDATE LIKE SY-DATUM.
      DATA NMENGE(17) TYPE C.
      LOOP AT EKKO_tAB.
        WRITE EKKO_TAB-MENGE TO NMENGE.
        NDATE = EKKO_tAB-BEDAT + EKKO_tAB-PLIFZ.
        CONCATENATE  EKKO_tAB-EBELP ',' EKKO_tAB-BUKRS ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-LIFNR ',' EKKO_tAB-BEDAT ','
        NDATE ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-EBELN ', 0,' EKKO_tAB-MATNR ','
        NMENGE ',' EKKO_tAB-MEINS ',' EKKO_tAB-WERKS INTO SDATA.
        MOVE SDATA TO: W_SDATA, T_EDIDD-SDATA.
        MOVE 'ZORDERS' TO T_EDIDD-SEGNAM.
        APPEND T_EDIDD.
      ENDLOOP.
    *call function 'L_IDOC_SEGMENT_CREATE'
        exporting
             i_segnam = 'ZORDERS'
             i_sdata  = w_sdata
        exceptions
             others   = 1.
    *LT_EDIDC
    call function 'L_IDOC_SEND'
         tables
              t_comm_idoc           = LT_EDIDC
         exceptions
              error_distribute_idoc = 1
              others                = 2.
    *DATA T_BDI_MODEL LIKE BDI_MODEL.
    WRITE OBJECT-OBJKY TO T_BDI_MODEL.
    READ TABLE T_BDI_MODEL INDEX 1.      " maximum 1 recipient
    L_EDIDC-DIRECT = 1.
      L_EDIDC-DOCNUM = DOCNUM. "***
      L_EDIDC-RCVPRN = 'HCM_00_785'.
      L_EDIDC-RCVPOR = 'MM_PO_FILO'.
      MOVE 'ZORDER'   TO L_EDIDC-MESTYP.
      MOVE 'ZPURIDOC' TO L_EDIDC-IDOCTP.
      MOVE 'LS'      TO L_EDIDC-RCVPRT.
    MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.
    *MOVE-CORRESPONDING L_EDIDC TO W_EDIDC.
    *- Distribute the iDoc
    BREAK-POINT.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' "IN UPDATE TASK
        EXPORTING
          MASTER_IDOC_CONTROL            = L_EDIDC
        TABLES
          COMMUNICATION_IDOC_CONTROL     = LT_EDIDC
          MASTER_IDOC_DATA               = T_EDIDD
        EXCEPTIONS
          ERROR_IN_IDOC_CONTROL          = 01
          ERROR_WRITING_IDOC_STATUS      = 02
          ERROR_IN_IDOC_DATA             = 03
          SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    READ TABLE LT_EDIDC INDEX 1.
      control_record_out-direct = '1'.
      CONTROL_RECORD_OUT-DOCNUM = DOCNUM. " ***
      control_record_out-serial = sy-datum.
      control_record_out-serial+8 = sy-uzeit.
      control_record_out-mestyp = LT_EDIDC-mestyp.
      control_record_out-idoctp = LT_EDIDC-idoctp.
      control_record_out-SNDPRN = 'HCM_00_786'.
      MOVE 'MM_PO_FILO' TO control_record_out-RCVPOR.
      MOVE 'LI'      TO control_record_out-SNDPRT.
      MOVE 'SAPQIS' TO control_record_out-SNDPOR.
    ENDFUNCTION.

  • Message Output for purchase order

    Dear SAP Expert,
    We have defined the message output type for purchase order document type XX with special function. We have maintained condition record for the same. It is working fine.
    Now we have defined another output type for another PO document type YYwith special function by copying earlier one.
    But message output is not genarated in case of YY document type.
    Please tell us what we have missed out.
    Thanks & Regards,
    Reva.

    Hi Reva,
    In ME22N for your PO, click on the Messages button. Then click on the blue information button - this should display the output determination analysis for the order, and will show you which output determination procedure was used, which output type and access sequence was processed and whether the system was able to find a matching record. At the lowest level of detail it will show you the keys that were used to read the condition records. All this information should help you to determine why a condition record could not be found for the purchase order.
    Regards,
    Monika

  • Searching for Workflow for Purchase Order Change

    Hi experts!
    We are using SRM5.0 / extended classic scenario and backend R/3 4.7 Enterprise.
    We should implement an approver process for the purchase order changes. Does any one of you know whether there exists a standard SAP workflow?
    Many thanks for your help.
    Regards,
    Corinne

    Hi
    <i>Please refer to the following links for detailed step-by-step details.</i>
    <u>Workflows for Purchase Orders - n-step approval workflow ( WS14000145 )... Start WS14000075, WS14000089 or WS14000145...-step approval workflow ( WS14000145 )</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/5a/c5173f5ff48443e10000000a114084/frameset.htm
    <u>Authorization - Purchase orders ( WS14000145 )</u>  
    http://help.sap.com/saphelp_srm50/helpdata/en/f7/a6a3415e34b05fe10000000a1550b0/frameset.htm
    <u>Setting Up SAP Business Workflow - WS14000145 ( n-step approval )... WS14000145... WS14000145 – N-step approval PO WS14000145 – N-step approval of contract</u>  
    http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
    <u>Dynamic Modification - Purchase orders ( WS14000145 )</u>  
    http://help.sap.com/saphelp_srm50/helpdata/en/84/dda441e79ead5fe10000000a1550b0/frameset.htm
    <u>Back & Forth Processing and the Retain Function - Purchase orders ( WS14000145 ) </u> 
    http://help.sap.com/saphelp_srm50/helpdata/en/6b/eca441eea7ef0be10000000a1550b0/frameset.htm
    <u>Approval Workflows for Purchase Orders and Change Versions</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/ec/fe163ff8519a06e10000000a114084/frameset.htm
    <u>Workflow for Contracts - Workflow for Purchase Orders ( WS14000145 )</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/26/0f8b41ed891609e10000000a155106/frameset.htm
    <u>SRM Business Workflow - One-step Approval</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
    <u>WS14000089</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/5a/c5173f5ff48443e10000000a114084/frameset.htm
    <u>WS14000075</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/5a/af5efc85d011d2b42d006094b92d37/frameset.htm
    Regards
    - Atul

  • Tcode for Purchase order Changes

    Hello Expert
    I Know there is one Tcode from which we could find changes happen in Purchase order at item level . Can any one let me know on the same which Tcode.
    I know the regular option by selecting the line item Environment->Item changes
    thanks
    Abhi

    Hi,
    You have to develope an own ABAP report for this, based on the change tables CDHDR and CDPOS
    CDHDR - Header Change
    CDPOS - Item Change
    EREV - Version Change
    Go to SE11 / SE16 / SE16N, here enter Object value as "PO No" in Table CDHDR and get the Document No and then input this in CDPOS and get the changes details. You can also enter EKKO and EKPO tables and see the whole list.
    Check the link
    Purchase order change log
    SAM
    Edited by: Saminathan Gopalan on Jun 3, 2010 12:35 PM
    Edited by: Saminathan Gopalan on Jun 3, 2010 12:37 PM

  • BAPI for Purchase order change

    Hi experts,
      I just want to change PO quantity by BAPI function module: BAPI_PO_CHANGE, I fill in PO number, Item number, material number and PO quantity to parameters, but result is not well. it shows a message below and the purchase order is not changed.
    message:
    For the currency code  ALE communication is not allowed
    Message no. B1889
    Diagnosis
    The ISO code assigned to the current currency code is not unique and the primary flag is NOT set. This currency code can therefore not be used for external communication.
    I checked currency config in SPRO and the assignment of ISO code is unique and the primary flag is setted actually.
    so what else can I do to solve this problem.
    thanks in advance.
    jack

    The B1889 message has the following reasons:
      -> The primary flag of the found ISO code is assigned more than once.
      -> The ISO code is not unique and the primary flag is not assigned
         for associated SAP currency codes.
      -> The ISO code is not unique and the current SAP currency code has
         NOT assigned the primary flag.
    First case: CC   ISOCD  XPRIMARY
                CNY   CNY      X
                RMB   CNY
    Your ISO code is not unique, therefore you are using the primary flag.
    If a dataset wich currency code CNY is encountered, everything is ok
    because none of the 3 rules mentioned above can be applied.
    If a dataset contains currence code  RMB, rule (3) will be applied.
    Therefore, you get the following output in this case:
      "For curreny code  RMB  ALE Communication is not allowed"
    Second case: CC   ISOCD  XPRIMARY
                 CNY   CNY
                 RMB   CNY    X
    If a dataset contains currency code RMB, everything is ok because it is
    flagged as primary. Like in the first case, if CNY is encountered,
    rule (3) will be applied and you will get the output:
      "For curreny code CNY ALE Communication is not allowed"
    If you are using both CNY  and RMB together, it is not possible to avoi
    the B1889 message beause there will be always the case that your ISO
    code is not unique AND that one currency code is not flagged as primary,
    which is summed up in rule (3).
    Please see information in attached note  "144349 ALE: Problems with
    currency conve".

  • Report for Purchase Order Changes

    Hi all,
    Is there any report that record changes in purchase order?
    Please respond.
    Best Regards,
    AI.

    Hi
    Go to ME23N or ME22N.. Choose Environment - Header Changes or Item changes(for item changes select the item first). You can see all the changes made.
    OR
    Changes to a lot of SAP documents are stored in table CDHDR and table CDPOS. This include changes such as: change data in Material Master, changes to Purchase Req (PR), Purch Orders, Contracts, Sales Orders, and many more.
    Put the PO number in CDHDR table OBJECTID table and get the change numbers.
    Put the change numbers in CDPOS and get the details.
    You can get the ABAPer to write a simple report.....
    Cheers
    JOJI

  • Repeat email output for purchase order

    Hi all,
        I have an email output (ZMAL)) that sends a notification from purchase order when the total value exceed $50,000 at creation of PO.  This works fine.  However, during ME22N, when the total po value goes from  intial $30,000 to $60,000, at saving, it should email out a notification but it does not as initial output ZMAL was created at po creation.
    Q:  How can i get the notification to send out automatically the second time or third time when the condition exceeding $50,000 
         is   met ?
    If i create another output ZMAL manually in PO, then i can resend ZMAIL. 
    The condition checking is made in   'EXIT_SAPMM06E_012 in Include ZXM06U43.
    Pls provide any suggestions you have.
    thanks
    Joyce

    Hi,
    Does the output type get triggered for the first time automatically?  Instead of writing the condition in enhancement, it is recommended to write the output type determining conditions in Output type Requirement routine.
    NACE -> Select application -> Click on Procedures -> select procedure -> Click on Control -> Insert record for the output type -> Create routine and assign .
    Check standard output procedure of Purchase order "RMBEF1" to get an idea.
    Regards
    Vinod

  • How to see the changed output for purchase order

    Hi..
    I have zmedruck. i need to increse item text lengh. i done this in editor. how to see the changed output now...I increased the length of text to be displayed. I checked the print preview in me23n. i cant see the increased length. Guide me where i am wrong.
    Edited by: Meena 303 on May 1, 2008 6:24 PM

    Hi
      In ME22N go to message -
    > select old message -
    >click change OutPut button -
    > Save
    then see print priview  through ME9F or ME22N it sself.
    regards
    Sachin

  • Debugging EDI output (IDOC creation) for purchase order...

    Hi,
    We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
    Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
    Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
    Regards,
    Rajesh

    Hi
    Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
    Save.
    Set the break point in your user exit.
    Go to se 38 -> Run RSNAST00,
    Give the object id (Your PO #)
    Give the output type  and execute, the control will stop at break point.
    Regards,
    Baburaj

  • SRM: "Purchase Order Change Approval " and "Invoice Approval"

    Hi,
    I would like to know the availability and details of the backend services for "Purchase Order Change Approval " and "Invoice Approval".
    Any pointers ?
    regards
    Sachin

    I want to know what are the Backend services exposed for the following processes :
    Purchase Order Change Approval in MM
    and Invoice Approval.

  • Problem in using output type for purchase order

    Hi experts,
         I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :-
    1) Going to  tcode NACE->Selected  the row u201CEF Purchase Orderu201D and clicked on u201CProcedures".
    2) In procedures there are 2 procedures for the application EF (Purchase Order). To proceed further, we would need to find out the procedure that is currently active.Gone to transaction SPRO. In this, navigate as Materials management -> Purchasing ->Messages -> Output control -> Message Determination Schemas ->Define Message Schema for Purchase Order
    3) Clicking on u201CAssign Schema to Purchase Orderu201D. So, the procedure RMBEF1 is active for EF (Purchase Order) . 
    4) Go back to transaction NACE. Select u2018EFu2019 and click on u201COutput typesu201D.
    5)  Let us use the output type u201CNEU name purchase orderu201D for this purpose. Double-click on NEU.
    6) Ensured  that the checkboxes u201CAccess to conditionsu201D and u201Cmultiple issuingu201D are checked and the access sequence is 0001(DocType/PurchOrg/Vendor).Only 0001 and 0002 is available in f4 help for this.
    7) Now clicked on u201CProcessing Routinesu201D on the left hand side. Ensured that there is an entry for Medium u2018Au2019 (Distribution ALE).
    8) After that going back to the main screen of NACE. Select EF (Purchase Order) and clicked on u201CCondition Recordsu201D.
    Select NEU and clicked on u201CCondition recordsu201D. The pop-up box appears that gives three radio button option :-
      1) Purchasing output determination :purchasing org / vendor for EDI
      2) Purchasing output determination :doc. type / purchasing org /vendor
      3) Purchasing output determination :document type
          but it is not having option only for purchasing organisation through which we can send idoc for changes or creation of PO in that particular pur.org now if i choose 2) i have to give doc type and purchasing org both bcoz they are mandatory fields and value for vendor.
    9)  Also i  have done the necessary ALE configuration (not covered in this document). In the partner profiles, use the message type u201CORDERSu201D and the IDOC type u201CORDERS05u201D.In the tab u201CMessage Controlu201D, used the process codes u201CME10u201D and u201CME11u201D for u201CPO Createu201D and u201CPO Changeu201D respectively.
    but the idoc is not generated many times when po is changed and when once it is generated it is giving error
    Please suggest solution.
    Thanks in advance
    nehavt

    In me22n in messages tab after looking into  processing log it is giving->No recipient found for message type ORDCHG in the
    ALE model ,next time giving error as no idoc items belonging to purchasing document found,when i changed message type to ORDCHG the  status is green in messages tab it is giving-> error occured while idoc xyz is sent and in WE02 status is red 02
    error passing data to port(could not find code page for receiving system)

Maybe you are looking for