PO and SO IDoc Type

Hi,
I understand that the IDoc type ORDERS05 can be used for Sales Order as well as Purchase Order. My requirement is to receive Order IDoc and create the sales order and send the PO details to a partner. Please let me know whether I can use the IDoc ORDERS05 for both these cases.
Also I found that IDoc type PORDCR04 is available for PO. Can we use this IDoc type for sending Purchase order details.
Thanks
N

Hello Nanditha,
Yes you can do that.
Also go to WE60 and put in PORDCR04 and downloadd to your PC if needed.
Then search if all the fields you need are in that Idoc type.
There are no rules as to which Idoc type you have to use, but you should try your best to stick to SAP recommended one's.
Hope this helps.

Similar Messages

  • EDI ANSI X12 and relavent IDOC types and messages...

    Hi ,
        Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
    210 -Motor Carrier Freight Details and Invoice
    240 -Motor Carrier Package Status
    753 -Request for Routing Instructions
    754 -Routing Instructions
    816-ORGANIZATIONAL RELATIONSHIPS
    828-Debit Authorization
    846- Inventory Inquiry/Advice
    870-Order Status Report
    Could you please help me?
    Thanks and regards,
    gowri

    EDI ANSI X12 and relavent IDOC types and messages...
    Posted: May 25, 2006 8:44 PM        Reply      E-mail this post 
    Hi Ravi,
         Thanks a lot for the reply. I have already checked this. In the ittoolbox.com is having some info about 214 but not about 210 and 240. I have already gone through the sapgenie.com but could able to get the relevant info on below transactions.I am basically looking for relevant idoc types and messages  in SAP for the below ansix12 transactions .
    Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
    210 -Motor Carrier Freight Details and Invoice
    240 -Motor Carrier Package Status
    753 -Request for Routing Instructions
    754 -Routing Instructions
    816-ORGANIZATIONAL RELATIONSHIPS
    828-Debit Authorization
    846- Inventory Inquiry/Advice
    870-Order Status Report

  • EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

    Hi All,
    We are facing some issues regarding EDI 821 and EDI 823 file mappings.
    We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
    EDI 823 - Lock Box
    Basic IDOC type - FINSTA01
    Message type - FINSTA
    Process Code  - FINS
    The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
    EDI 821 -
    Basic IDOC type - PEXR2002
    Message type - PAYEXT OR REMADV
    Process Code  - PEXC OR REMA
    We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
    We are trying different combinations but nothing is working so far.
    I need the following things to proceed furthur.
    1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
    2)If those are not correct, can you please let me know the correct entries
    3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then  I can re check it.
    4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
    thanks in advance for all your help.
    Please let me know if my question is not clear.
    Thanks,
    Ramesh.

    Hi Ramesh,
    I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
    First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
    Are you can give me the exact error and i can help you as well.
    Thanks,
    Mahesh.

  • Which Idoc type for Quality release process and Inventory reconciliation/adj. with 3PL

    Dear experts,
    could you please provide your suggestion on which Idoc type to use for following two scenarios between Client and 3PL vendor (Logistic provider):
    1st scenario:
    - Products are released in QM in clients SAP. As a result of this action stock status is changed. This information should be sent to 3PL vendor. 3PL vendor receives the information, changes the inventory status in its system and sends confirmation back to the client. Is there any Idoc type that can be used?
    2nd scenario:
    - 3PL vendor sends stock reconciliation static report to the client. Client receives the report and compares it with own report. Exceptions are reviewed and adjusted upon agreement between Client and 3PL. Once 3PL adjusts the stock, this information is received in Client system and processed subsequently. Any suggestions for an Idoc with Stock reconciliation report and also for stock adjustments?
    Many thanks for each idea to everyone in advance.

    Hi Ramesh,
    thank you for this idea. Unfortunately it seems not be applicable for our system as it is ECC 5.0 and INVRPT Idoc type I can only find in ECC 6.0.
    Do you have any other idea or we have to build a new custom Idoc type?

  • Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

    Hi,
    I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
    Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
    Thanks in advance.
    Best Regards.
    Alex

    Hi Aamir,
    The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
    Thanks anyway.
    Alex

  • What is inbound XML message type and idoc type in Purchase Order response

    Hi ,
    We are on SRM 7 ECS , support pack SAPKIBKV08.
    We have a process in which vendor will send a Purchase Order response  which will be
    converted to XML format by a middleware. This XML message will come to
    SRM and post a POR. I want to do the EDI mapping for this XML message,
    but there is no message type and idoc type in SRM for Purchase Order
    response. How do I map my message type in SRM to the vendor sent fields
    in middleware .
    Please advise
    Rgds
    Sumendra

    Hi,
    You can process with XML without IDoc.
    Vendor->  (XML) -> PI -> (XML) -> SRM.
    Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
    http://esworkplace.sap.com
    Regards,
    Masa

  • Urgent - Idoc type and the Message type

    Hello
    Its very urgent. I want to know the basic idoc type and the message type used for EDI 894 transmission (Delivery / Return Base Record). Please respond at the earliest.
    Thanks in advance

    HI
    Pratibha
    How are you ?
    Please check the below links:
    http://scn.sap.com/thread/990524
    http://www.erpgreat.com/pm003.htm
    http://scn.sap.com/thread/1386811
    http://scn.sap.com/thread/1078741http://www.erpgreat.com/plant/what-is-equipment-master.htm
    http://benxbrain.com/en/index.do?onInputProcessing%28brai_object_thread%29&001_threadid=0000835100&001_boardtype=01&sysid=PI1&pgmid=R3TR&object=TABL&obj_name=EQBS&child_param=
    Mutti

  • IDOC Types for 215, 870, 852, 857, 858 and 838

    Hi,
    Can anyone let me know the IDOC types in SAP for
    215, 870, 852, 857, 858 and 838 messages (X12 Messages).
    Thanks,
    Sudheer

    Hi Sudheer
    Check these links,
    http://www.sap-edi.com/sap_r3/ansi.asp
    http://www.geocities.com/sap_edi/ANSI.htm
    http://www.sapgenie.com/sapedi/message_types.htm
    Hope they give you the required information
    Regards
    Vishnu

  • How  can create SEGMENTS and IDOC TYPE in BADI in ECC 6.0 version

    Hi All,
                Can any one help, how  to create SEGMENTS and IDOC TYPE in BADI in ECC 6.0 version.This is my task.
    Given BADI name was----VENDOR_ADD_DATA_BI .
    Thanks

    Anil,
    look at this thread ..may be this helps you.
    Re: 824 IDOC and BADI/User Exit
    sateesh.

  • Implementation of IDOC types FINSTA01 and PEXR2002

    Hi All,
    I want to implement the 2 IDOC types PEXR2002 and FINSTA01 using EDI.The requirement is like I have to generate both the inbound and outbound processing for both the IDOC types using EDI.
    I have the following queries :
    1)What are the basic fields that are required for both the inbound and outbound processing(like file format)
    2)How the inbound and outbound processing will be triggered like how can I send the file from SAP to EDI or how can I get the file from EDI to SAP and how to uplaod the record into SAP is there any SAP standard transactions or any standard reports or do I have to configure in the SPRO etc.
    3)What are the settings that I have to configure?
    Please help me out and your help will be appreciated.
    Thanks and Regards,
    Ramesh.

    Hello Ramesh,
    The answers to your questions are a few chapters in some books, meaning its quite large.
    But in short.
    1. the minimum fields are what is required by that particular transaction in SAP for inbound and for outbound you gotta check with the receiving party what they need.
    example , if you are posting a PO in SAP, then what are the mandatory fields, thats the minimum.
    With every idoc , incoming, there are a few ways to post, most common is via function modules.
    Lets say you know a partner which will communicate via EDI, you have to maintain a partner profile in WE20.
    There you define the incoming and outgoing messages.
    Every message has, idoc type.
    Transactions WE42 and WE43 are where you define a process code for attaching the message type/idoc type to a Funtion module.
    Also there is config for setting up output types, see transaction NACE.
    This is a process with lots of parameters.
    You would be better off getting a book which explains it all in a proper order.

  • Corresponding IDOC types for 816 and 824 of  X12 tranasction

    hi
    can anyone tell me corresponding IDOC types for the fallowing X12 tranasction(EDI).
    816 Organizational relationships
    824 Application Advice
       regards
        mallikarjun

    Hi Malikarjun and Ryan
    Please take a look at the following links:
    http://www.sapgenie.com/sapedi/ansi.htm
    http://www.sapgenie.com/sapedi/mapping.htm
    Hope this will help.
    Regards,
    Ferry Lianto

  • IDOC Types and their equivalent messages in EDIFACT and ANSI X12

    Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
    Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
    Regards,

    Hi,
    Please check these perhaps they may help.
    Mapping ANSI X12 to SAP Message Type and IDoc Type:
    204 Motor carrier shipment information
    The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    214 Transportation carrier shipment status message
    The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
    304 Shipping instructions
    The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
    The logical message is INVOIC, the IDoc type INVOIC01.
    812 Credit and debit advice
    The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
    820 Payment order and credit advice
    For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
    For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
    823 Lockbox
    The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
    830 Delivery schedule (LAB)
    The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
    832 Price catalog (also 879, 888, 889)
    The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
    834 Benefit enrollment and maintenance
    The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
    840 Request
    The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
    843 Quotation
    The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
    850 Purchase order or order (also 875)
    The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
    852 Stock and sale data
    The logical message is PROACT, the IDoc type PROACT01.
    855 Ordering or order response (also 865)
    The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
    856 Transport and shipping notification (ASN - Advanced Ship Notification)
    For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
    For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
    860 Ordering or order modification (also 876)
    The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
    861 Credit advice (ERS - Evaluated Receipt Settlement)
    The logical message is GSVERF, the IDoc type GSVERF01.
    862 delivery schedule (FAB)
    The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
    864 Text message
    The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
    940 Shipping order and stock order
    The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
    945 Shipping confirmation and stock confirmation
    The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
    997 Functional Acknowledgment
    This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
    "22" Shipping OK, acknowledgment has yet to come
    "16" Functional Acknowledgment positive
    "17" Functional Acknowledgment negative
    The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
    Regards,
    Ferry Lianto

  • Idoc types and message types we use in IS-Retail

    hi gurus,
                 can anyone tell me what are the idoc types and their message types that we use in SAP IS-Retail .
    Thanks in advance
    regards
    gopal

    Hello, these are the main idoc types used in sap retail:
    'WPDBBY01' POS outbound: bonus buy conditions
    'WPDCUR01' POS interface: Download exchange rates
    'WPDNAC01' POS interface: Download products
    'WPDSET01' POS interface: Download set assignments
    'WPDTAX01' POS interface: Download tax rates
    'WPDWGR01' POS interface: Download material group master
    'WPUBON01' POS interface: Upload sales docs (trnsctns), non-aggregated
    'WPUERR01' POS interface: Upload messages SRS/POS/SCS
    'WPUFIB01' POS interface: Upload Fin.Acc. interface SRS/POS
    'WPUKSR01' POS Interface: Inbound processing cashier data for POS stats
    'WPUTAB01' POS interface: Upload day-end closing POS
    'WPUUMS01' POS interface: Upload sales data (compressed)
    'WPUWBW01' POS interface: Upload goods movements
    'WP_EAN01' POS interface: Upload/Download EAN assignments
    'WP_PER01' POS interface: Upload/Download person data
    'WP_PLU01' POS interface: Upload/Download article master
    'WP_PLU02' POS interface: material and condition (inbound and outb.)
    'WTADDI01' Additionals
    'WVINVE01' Store phy.inv.: phy.inv. docs outbound; count data inbound
    'WVINVE02' Store phy.inv.: phy.inv. docs outbound; count data inbound
    'W_WGRP01' Distribution of material groups
    Regards,
    Juan Carlos

  • Idoc types and message types

    Hi ,
    Anyone can send what are all the std idoc types and message types are there in SAP?
    Coz i dnt have SAP.
    Please let me know

    The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
    An IDoc type consists of the following components:
    ·       a control record
    This is identical for each IDoc type.
    ·       several data records
    One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
    ·       several status records
    These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
    You find various IDOC / Message types in SAP -
    http://www.erpgenie.com/sapedi/message_types_masterdata.htm
    IDoc Types - Message Types -Accounting Business Processes
    IDoc Types - Message Types - HR Business Processes
    IDoc Types - Message Types - Logistics Business Processes
    Eg.
    General       Message types / IDoc types / BAPI
    Vendor        CREMAS / CREMAS02
    Customer      DEBMAS / DEBMAS03
    Accounting   Message types / IDoc types / BAPI
    G/L account   GLMAST / GLMAST01
    Cost center     COSMAS / COSMAS01
    Cost element  COELEM / COELEM01

  • Message types and idoc types

    hi,
         i need the list of message types and idoc types for edi.
          can any one of u pls send it.

    Hi,
    Check the OSS notes 104606.
    The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
    204 Motor carrier shipment information
               The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    214 Transportation carrier shipment status message
               The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
    304 Shipping instructions
               The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    810 Invoice or billing document (also 880)
               The logical message is INVOIC, the IDoc type INVOIC01.
    812 Credit and debit advice
               The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
    820 Payment order and credit advice
               For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
               For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
    823 Lockbox
               The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
    830 Delivery schedule (LAB)
               The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
    832 Price catalog (also 879, 888, 889)
               The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
    834 Benefit enrollment and maintenance
               The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
    840 Request
               The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
    843 Quotation
               The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
    850 Purchase order or order (also 875)
               The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
    852 Stock and sale data
               The logical message is PROACT, the IDoc type PROACT01.
    855 Order confirmation (also 865)
               The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
    856 Transport and shipping notification (ASN - Advanced Ship Notification)
               For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
               For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
    860 Ordering modification (also 876)
               The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
    861 Credit advice (ERS - Evaluated Receipt Settlement)
               The logical message is GSVERF, the IDoc type GSVERF01.
    862 Delivery schedule (FAB)
               The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
    864 Text message
               The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
    940 Shipping order and stock order
               The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
    945 Shipping confirmation and stock confirmation
               The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
    997 Functional acknowledgment
               This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
               "22" Shipping OK, acknowledgment has yet to come
               "16" Functional acknowledgment positive
               "17" Functional acknowledgment negative
               The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
    Cheers
    VJ

Maybe you are looking for