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

Similar Messages

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

  • 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

  • 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

  • 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

  • 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

  • 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

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

  • Reg enhacement for purchase order?

    Hi experts, 
    if there is any open purchase order for the material   system should give pop up while saving purchase order .
    can any one provide me the solution
    Thanks

    Hi,
    You can implement BADI ME_PROCESS_PO_CUST and use method CHECK or POST for your validations.
    Alternatively you can use enhancement SAPMM06E exits EXIT_SAPMM06E_012 or EXIT_SAPMM06E_013
    Thanks,
    Vinod.

  • 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

  • ALE IDOC for Purchase order to sales order

    Hi Friends,
    I am sending P.O. from one system to other,using message  type ORDERS and basic type ORDERS05 .
    On receiving system I am using inbound process code ORDE.
    Sending is successful but on receiving side its giving me error, VKORG, VTWEG, SPART cannot be determined for customer 0000000001 .
    So please suggest me some solution on this ,,
    Proper points will be rewarded to helpful answer.
    Thanks,
    Brijesh........

    Hi brijesh,
    I am also working on  creating PO to SO . The problem you are getting is one of the problem i have faced . But we can solve this easily.
    In your outbound idoc you have 4 fields with E1EDK14.
    This segment stores the values for SPART,VTWEG,VKORG .
    So in the qualifying fields of this segment 006,007,008 should be there for the above fields respectively  and their values in the orgid field.
    I have written the coding in outbound side user exit.
    MM06E001 in the 11th function module .
    so try this it will solve the problem.
    Thanks
    vamshi

  • Extended Idoc for Purchase Order

    Hi Gurus,
    I have a requirement to extend a basic idoc type Orders. I know the process of creating a "z" segments and "z" idoc type but where should write the code to process the additional segments for ORDERS.
    ( FOR Master data i can find the Customer exit to process the "z" fields but i don't know where should i write the code to process the transactional data).
    plz let me know u'r knowledge.........
    Regards:
    TMR.

    check in orders out bound process code FM
    there you can find the exit for the smae
    Thanks and Regards
    S.Janagar

  • 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

  • Help! Inaccessible iterator when using dynamic query

    Hi! I have a problem retreiving results from a dynamic query into sqlj iterator. I consulted the Oracle App Dev Guide and Oracle SQLJ Dev Guide and wrote the following code: <PRE> package pmServer; #sql iterator LocIterator (int id, String name); pub

  • Schema level trace

    HI all, Is it possible to trace every sessions within schema in Oracle 10g R2? Thanks Ken

  • My N95 region was changed after the NSU Upgrade

    Hi folks I used to have this N95 configuration Nokia N95 v10.0.0.18 15-03-07 RM-159 (05.01). Note that I had Bulgarian language in the languages. After the update I have V 11.0.0.26 17-04-07 RM-159 Nokia N95 (66.01) and no more Bulgarian ?!?!? Any id

  • Sonata suddenly stopped working!

    Hi! I was going to change album in Sonata, so I opened the library, but suddenly it was all empty. I tried to restart the program, but now it won't start. Sonata in Terminal gives me this message: "[erlend@qweac ~]$ sonata Traceback (most recent call

  • How to find list of Info Sets

    Hi , Can you please tell me how to find out the list of Info Sets which are either active or inactive in the system. Regards, Vishnu