Problem in triggerring EDI idoc for Purchase order..

Hi experts,
I am trying to create an outbound EDI IDOC for a PO.
I have configured the partner profile in partner type LI with message type ORDERS in outbound parameters. I have created a new output type ZEDI for EDI, and entered in a message control, as application EF, message type ZEDI and process code ME10.
But when i go to the me23n and goto--> messages, but when i click F4 for output type i am not able to see the new output type ZEDI i have created.
And if i also enter NEU with medium EDI, and Partner function VN, and partner 3000(where i configured the parnter profiles), its giving an error as, "maintain outgoing EDI-connection data for partner 3000".
Kindly help me out. please experts reply me..
Nithin

Hi
<b>In the transaction NACE</b>
you need to maintain the necessary 'Z' output type, in your case.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Similar Messages

  • Creating an IDOC for purchase order

    Hello gurus,
    I want to generate an IDOC for purchase order.
    The Logical System, RFC connection, ports definition is already defined.
    In my system i have 800 client as source/sender and 100 client as target/reciever.
    On Outbound side-> In Partner profile
    I defined-
    1. Partner No.- devclnt100
    2.Type- US (User)
    3. Agent - SAPUSER
    In Outbound parameters-
    I created message type as Orders.
    One thing to note that my partner system is LS i.e. Logical System
    Then in Outbound Options-
    I mentioned Reciver Port - 800Port
    Output Mode- I selected "Transfer Idocs immediately"
    & "Do not start subsystem"
    In Idoc type-
    I gave following information-
    Basic Type - Orders05
    In Message Control tab i mentioned-
    Application - EF
    Message Type - NEU
    Process Code - ME10
    In NACE Transaction Code-
    I selected EF Purchase Order as my condition for output control
    In that- In output types-
    I selecte NEU and double clicked. I checked whether Access to Conditions check box is checked and multiple issuing is checked.
    In Dialog structure-Processing routines I checked that -
    For Output type - NEU
    Application - EF
    Processing routines are defined-
    medium-Distribution ALE
    Program -RSNASTED
    Form Routine - ALE_PROCESSING
    I think these are the very basic settings that need to be done for creation of Idoc.
    Now when i create a PO and then SAVE it an IDOC must be generated.
    But when i go to transaction Code WE02. It shows me message "No Idocs genereated".
    What is the problem? Where am i going wrong?

    Hi Yayati,
    Here are all the settings that you need to do. I am not sure which all settings are present so kindly confirm.
    Sending side Client800:
    1. WE20 - under LS - Outbound parameters - message type = Orders , basic type = Orders05
    2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
    3. NACE - App = EF - Output Types - Processing Routines - Add medium = A (Distribution (ALE)) , Program = RSNASTED, Routine = ALE_PROCESSING.
    4.  NACE - App = EF - Output Types - Partner Functions - Add medium = Distribution (ALE), Funct = VN.
    5. Name - App = EF - Condition Records - Output type = NEU , Choose ur combination (Mine is DocType/Purc Grp)
         Pur.Doc Type = NB (Execute) , Add row Medium = A ,Function = VN and other details u choose.
    Receiving side Client100:
    1. WE20 - under LS - Inbound parameters - message type : Orders ; Process Code : ORDE
    2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
    For the PO which you have created, go to the PO in ME23N, click on messages .
    There should be a line : Output = NEU, Medium = Distribution (ALE)... etc.
    If its present then the configuration was correct.
    If it has a yellow triangle means it was not processed.
    Regards,
    Jovito.
    Edited by: dsouzajovito on Dec 30, 2010 10:24 AM

  • Generating idoc for Purchase orders - ORDERS05

    Hi,
    Can you please let me know how to generate idoc for Purchase orders - ORDERS05-manually, not by activating change pointers.

    hi
    i believe u wont have this functionality as it is a transcational data and the one way of doing it by configuring output types only.

  • Standard Idoc for Purchase order?

    Hi,
    Can you please let me know what is the Standard Idoc for Purchase order?
    POINTS WILL BE AWARDED

    Hi Guest
    You can use it, if all your required field are in that Idoc basic type.
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://abapprogramming.blogspot.com/2007/11/abap-idocs-basic-tools.html
    Award points for helpful answers

  • Standard Idoc for Purchase Order Receipt?

    Hi Experts,
    Is there a standard idoc for Purchase Order Receipt?
    Please let me know.
    Thanks,
    Rakesh.

    here we go:
    Goods Receipt MIGO IDOC

  • 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

  • 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)

  • Problem in creating a SyncBo for Purchase Order BAPIs

    Hello Everybody,
    I am trying to create a smart sync application for Purchase Orders.
    I have used standard bapis like BAPI_PO_GETDETAIL AND BAPI_PO_CREATE1.
    I have developed my own wrapper functions using these std bapis. For the PO creation i only plan to insert the necessary and mandatory data. The problem i face is that some of the tables in the create bapi which are mandatory for a PO creation are freezed in the SyncBo.
    Tables like POITEMX, POADDRDELIVERY, POSCHEDULE and structure POHEADERX are all required for the creation of a PO. Without this minimum data a PO cannot be created.
    After i have created the syncBo, on the mapping screen i can only see these tables under the create BAPI. But i am not able to perform the mapping of their fields. These are non-editable or i must say that they are freezed.
    And if i cannot map them then i cannot pass data for them from the client. Although i can do the mapping for the table PO_ITEM and the structure PO_HEADER.
    I hope i am able to expplain my problem. Kindly get back to me if i am not clear. Any sort of help is welcome.
    Thanking in advance,
    Saurabh.

    Hi Saurabh,
    Hope you are aware of the prerequisites for creating the BAPI Wrappers.
    If you want to insert some data into the Business Object, then you have to include
    GETLIST, GETDETAIL and CREATE Bapi Wrappers.
    I think in your case,
    You might not have mapped those fields in your GETLIST Bapi Wrapper.Just check whether you have mapped those fields that are necessary for PO creation in your GETLIST and GETDETAIL BApi wrapper mapping screen.
    Those fields you have mapped in the GETLIST and GETDETAIL BAPI wrappers will be visible (for selection - checkboxes will be editable) in the mapping screen for CREATE BAPI Wrapper.
    So first of all, you have to map fields there in the mapping screens for GETLIST and GETDETAIL Bapi Wrappers...
    check this thing...
    refer these links..
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/library/mobile/mobile%20infrastructure/mobile%20development%20kit%202.5/content/appdev/smartsync/introduction.html
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/library/mobile/mobile%20infrastructure/mobile%20development%20kit%202.5/content/appdev/smartsync/bapi_wrapper_types.html
    In the second link, you can see one figure, which is explaining the things that are to be satisfied by the BAPI Wrappers for SyncBO creation...
    Let me know If you have doubts in the prerequisite section itself...
    Regards,
    Kishor Gopinathan

  • Idoc for purchasing order

    can any1 explain the steps needed to send a purchase order through ALE/IDOCS
    pls explain it with reference to PURCHASE ORDER

    Hi,
    cehck the same...
        This method is used for distributing transaction data like purchase order, sales order etc.
        In this method the extra transaction code that we use is we41 (outbound process code) and we use this in the message control tab in the partner profiles. 
    The transaction codes that are required for this method are
    We81
    We30
    We31
    We82
    We21
    We20
    Bd64
    Nace
    Me22n (purchase order), va02 (sales order) etc.
    Ex: purchase order.
    Message type: ORDERS
    Idoc type: ORDERS05
    Outbound process code for purchase order: me10
    The steps that are to be followed are:
    Check for the message type in the transaction in we81.
    check for the idoc type in the transaction we30.
    check we82 in which the link between message type and idoc type is there.
    create the port in we21.
    Configure the partner profiles in we20.
    Click on the + button outbound parameters and give the message type, receiver port
    Idoc type.
    Now press on the message control tab, this is the place where u give the outbound process code. The message type in the message control is the output type that is used in the nace transaction.
    Create a distribution model in bd64.
    Go to purchase order transaction (me22n).and press the messages tab
    In the messages tab give the output type and the distribution medium as distribution-ale and then save it.
    Reward if helpful.
    Regards,
    Nagaraj

  • EDI Confirmation for Purchase Order

    Hi All,
    Scenario : Our vendor is located abroad. The Purchase order is transmitted to the vendor via EDI. The vendor sends a confirmation for the PO as an IDOC via EDI. The suitation we have is that there are instances where there is a miss match( Requested item doesn't match the confirmed item) between the item in the PO and the IDOC received from the vendor as confirmation. But the PO is still confirmed. Is there a method where we identify when there is a miss match in the item.
    Any input on the above would be appreciated.
    Thanks
    Nigel

    Hi Nigel,
    You could control this via customizing purchasing->Confimrations->Setup confirmation using SPRO.
    here ,you can specify the tolerance for price quantity and material.
    The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
    If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
    Regards,
    Karuna

  • Idocs for purchase order in SAP to SAP

    Hi
    I have to send purchase order from a SAP system to a SAP system, creation and modification both.
    I found these Idocs:
    ORDER in sender SAP
    PORDCR for creation in destination SAP
    PORDCH for update in destinaton SAP
    My problem is that all of three idoc have different segments, so i have to map field by field: is there a different solutions, always using idocs and not BAPI directly?
    Thanks lot.
    Matteo Vernile.

    Hi Matteo,
    To send purchase orders you can use next Idocs:
    1. Creation -->Idoc type: PORDCR102 Message: PORDCR1 This Idoc is based on BAPI_PO_CREATE1
    2 Modification --> Idoc type PORDCH02 Message: PORDCH This Idoc is based on BAPI_PO_CHANGE
    Using standard boldSAP message determinationbold  you can create these Idocs without create any ABAP program.
    If you are not creating the Idoc using the standard Message Determination, you should obtain the data using the bapi BAPI_PO_GETDETAIL.
    Reward points if helps.
    Regards,
    Roger

  • Issue with ALE configuration for creating the idoc for Purchase orders

    Hello,
            I am trying to send the purchase order through message type configuration using ALE.
    I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
    In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
    I have done ALE distribution using BD64.
    Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
    In NAST table, the entry is there but on executing RSNAST00 nothing happens.
    Please provide me the pointers to solve the given problem.
    Regards,
    Mayank

    Hi,
    Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
    It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
    Check and let me know if all is fine at the output type configuration.
    Cheers
    VJ

  • Reg idoc for purchase order

    Dear  Friends,
    I am trying to transfer data of purhcase order (ME21) (with header and item details) from one client to another client.
    I am using idoc ORDERS05 for updating the data.
    But i am unable to map the fields of the ME21 to the fields of segments of the idoc ORDERS05.
    Note:  I am using these fields of me21.
    *header details
        ekko-ebeln.                             "Purchasing document
        ekko-bukrs.                             "company code
        ekko-bsart.                             " Purchasing Document Type
        ekko-ekgrp.                             " Purchasing Group
        ekko-ekorg .                             " Purchasing Organization
        ekko-lifnr.                              " Vendor Account Number
        ekko-aedat.                            "date on Which Record Was Created
        ekko-pincr.                            "Item Number Interval
        ekko-spras.                            "language
        ekko-zterm.                             "Terms of Payment Key
        ekko-waers.                              "Currency Key
    *item fields
        ekpo-ebelp.                             "Item Number of Purchasing Document
        ekpo-ematn.                            " Material Number
        ekpo-txz01.                            " Long Material Number for MATERIAL Field
        ekpo-werks.                          "Plant
        ekpo-lgort.                           " Storage Location
        ekpo-matkl.                          " Material Group
        ekpo-menge.                         " Purchase Order Quantity
        ekpo-meins.                           " Purchase Order Unit of Measure
        ekpo-netpr.                         "Currency amount
    pls help.
    Regards,
    Vinod Kumar.

    Hi
    chek with currect version of Message  type,if it's not in message type do customise segement's.
    cheers
    venu

  • IDOC for purchase order

    Hi,
      I created an IDOC using the basic type orders04 , i populated all the required fields and tried to run the idoc through WE20 .The idoc got generated but with an error saying "Purchasing document & does not exist"..I am not able to see which part of the segment this error is getting popped up.Please help me.
    Thanks & Regards
    Abhishek

    Hi Abhishek,
    In your header you suggest that you want to create a purchase order using ORDERS04; however this message can't be used to create purchase orders. You should use message PORDCR instead.
    In case you do want to create a sales order, you could set a break point in function module IDOC_INPUT_ORDERS at the call of transaction VA01, switch MODE to 'A' and the sales order is created in dialog mode. Perhaps you might then find out what the cause of the error is.
    Hope this is of any help.
    Regards,
    John.

  • E1EDKA1 WE missing in IDOC for purchase orders

    Hi,
    We have an issue where our users create a PO by following the steps below.
    1. In ME21N screen, Pull up document overview and from there display the materials listed in each contract.
    2. Drag and drop the materials into "shopping cart" , enter qty. and change the delivery dates and save the PO.
    An idoc is created upon saving the PO.
    The problem is that the idoc generated is missing E1EDKA1 WE segment.
    We checked the vendor master (XK03) and the contract (ME33k) but they have the right delivery address.
    Can some body help me understand where in SAP data from the E1EDKA1 WE segment is populated in the first place and what could be the reason for missing E1EDKA1 WE segment?
    Thanks.

    Dear Kinapo,
    If the delivery address for all items is the same, the segment E1EDPA1 with
    qualifier WE will be not populated. Instead of generating E1EDPA1 the
    system will create one E1EDKA1 segment with qualifier WE.
    Regards,
    ian Wong

Maybe you are looking for