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

Similar Messages

  • 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

  • Require Standard DataSources for Purchase Orders

    Hi,
    Please provide me the standard datasources for purchase orders to get the data updated automatically in a BI System.
    I have to display report containing the purchase orders details of each day.
    Regards
    Sunil Kumar

    Hi,
    Following link will give you complete details of purchase order deports and data sources.
    http://help.sap.com/saphelp_nw70/helpdata/en/df/cfb839f6a7a307e10000000a11402f/frameset.htm
    Regards,
    Vishnu

  • 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 Work order?

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

    Hello,
      Standard IDOC type for Work Order is LOIPRO01.
    Thanks,
    Venu

  • Standard smartform for Purchase Order

    What is the standard smartforms for purchase order?Where can i find this?Give me print program for the same.

    Hi
    Preconfigured smartforms are not available on ECC 6.0. You have to either download from service.sap.com or migrate existing script to smartforms.
    Regards,
    Vishwa.

  • Standard smartforms for purchase orders in scm server

    hi
    what are standard smartforms for purchase orders in scm server(not on R/3 server)
    in R/3 i know
    /SMB40/MMPO_UK
    /SMB40/MMPO_L
    /SMB40/MMPO_A
    but i want to know in SCM(Supply Chain Management) server
    Thanks,
    Phani

    check below may be u r looking for the same
    /SCA/ORDER_DESCRIPTION_AUTO
    /SCA/ORDER_NUMBER_AUTO
    /SCA/ORDER_NUMBER2_AUTO
    ~~Guduri

  • How to find the standard Idoc for Transfer Order (LT03)

    hi
    How to find the standard Idoc for Transfer Order (LT03)
    How to create the Idoc on LT03
    plz help me out
    Thank u
    Ram

    Someone is using FM: L_IDOC_INPUT_WMTORD, message type WMTORD and basic type WMTOID01 in doing this when trying to send an Idoc to an external system when a transfer order for a delivery note is created (LT03). Is it OK
    Please reward points

  • 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

  • Standard Datasource for Purchase Order master data

    Hi Experts,
    Is there any Standard datasource for extracting attribute information for Purchase Orders. Some master data datasources.
    Iam  particularly after the name of the person who released the PO.
    Thanks,
    DV

    Hi,
    These are standard Master Data Datasources
        0CRIT_MAIN_TEXT                   Key for Appraisal Criterion
        0CRIT_SUB_TEXT                    Subcriterion
        0CRIT_TYP_TEXT                    Scoring Method
        0DCINDIC_TEXT                     Debit/Credit Indicator
        0DISMM_ATTR                       MRP Type
        0DISMM_TEXT                       MRP Type
        0INDSPECSTK_TEXT                  Text Indicator Special Stock Valuation
        0INFO_REC_ATTR                    Number of Purchasing Info Record
        0INFO_REC_TEXT                    Number of Purchasing Info Record
        0INFO_TYPE_TEXT                   Purchasing info record category
        0MATL_CAT_TEXT                    Material Type
        0MATL_GROUP_TEXT                  Material Group
        0MAT_TYPE_VA_ATTR                 Control of Quantity/Value Update
        0MAT_VEND_ATTR                    Material Number Compounded to vendor
        0MRP_CONTRL_TEXT                  MRP controller
        0PRICE_CTRL_TEXT                  Price control indicator
        0PRICE_TYPE_TEXT                  Price type
        0PURCH_ORG_TEXT                   Purchasing Organization
        0PUR_GROUP_TEXT                   Purchasing Group
        0PUR_REASON_TEXT                  Reason for ordering
        0SERVICE_ATTR                     Service Master (Attributes)
        0SERVICE_TEXT                     Service number
        0STOCKCAT_TEXT                    Stock Category
        0STOCKTYPE_TEXT                   Text for Stock Characteristic
        0STOR_LOC_TEXT                    Storage Location
        0STRGE_SECT_TEXT                  Storage section for stock removal, placemen
        0STRGE_TYPE_TEXT                  Storage Type
        0STRGE_UNIT_TEXT                  Storage unit type
        0VENDOR_ATTR                      Vendor Number
        0VENDOR_LKLS_HIER                 Vendor number
        0VENDOR_TEXT                      Vendor Number
        0WHSE_NUM_TEXT                    Warehouse number / warehouse complex
        0WM_MVT_TYP_TEXT                  Movement type for Warehouse Management
    Regards,
    Marasa.

  • 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

  • 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

  • Error in Standard Program for Purchase Order

    Hello Everyone,
    I am getting an ABAP Dump Error while Displaying & Printing Purchase Order using TCODE : ME9F & ME23N.
    We have applied new Patches.
    for Logistics it is 26 & ABAP it is 58.
    I am getting Error in standard INCLUDE
    Program : LMEDRUCKF1K at line 64.
    The Error is :- "Field "ENJPREVIEW" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement."
    Declaration for "ENJPREVIEW" is also available in
    include LMEDRUCKTOP. still it gives an error.
    These lines of code is included by SAP note 855263.
    Before applying these Patches it was working properly, but now it gives an error.
    Please , Can anyone give solution for this.
    Regard's
    Archana.

    Hi Archana ,
    Check is there any Inactive Versions in ur Systems ?
    useful tcodes are SPAU /SPDD for tables
    Regards
    prabhu

Maybe you are looking for