DOC

MM-PUR EDI_WORKSHOP

By David Woods,2014-09-08 17:55
7 views 0
MM-PUR EDI_WORKSHOP

    78377306.doc printdate: 09/08/10

    EDI

(purchasing)

    Version 1.03

    (05-01-2000)

    Robert Behling

    Mark Ameer

    Michael Biermann

    1 / 33

78377306.doc printdate: 09/08/10

EDI, what’s this? ........................................................................................................... 3

    EDI processes................................................................................................................. 4

    Purchase order ...................................................................................................................................... 4 Distributed contracts ............................................................................................................................. 4 Scheduling agreement and delivery schedule ......................................................................................... 4

    Request for quotation ............................................................................................................................ 5 Miscelanious ........................................................................................................................................ 5 Conditions ........................................................................................................................................ 5 Purchasing info record ...................................................................................................................... 5 The PORDCR IDoc .......................................................................................................................... 5 Customizing ................................................................................................................... 6

    Output determination ............................................................................................................................ 6 Maintain Partner for EDI ................................................................................................................... 6 Message types and processing codes................................................................................................ 11

    Maintain output determination (access sequences and condition tables) ............................................ 12

    Message determination schemes ...................................................................................................... 14 Especially for releases of scheduling agreements, Processing messages (output records) ...................... 16

    Assign programs ............................................................................................................................. 16 Which fields are relevant for changes? ................................................................................................ 18 Customize which fields are relevant for printing changes ..................................................................... 20

    Tolerances (quantity, price) for order responses ................................................................................... 21 Price tolerances ............................................................................................................................... 21 Quantity tolerances ......................................................................................................................... 22 Miscelanious ................................................................................................................ 23

    Transactions and tables ....................................................................................................................... 23 Transactions.................................................................................................................................... 23 Tables ............................................................................................................................................. 23 Exits ................................................................................................................................................... 23 IDOC_OUTPUT_ORDERS in detail .................................................................................................. 25

    Debugging example ............................................................................................................................ 26 Problem description: ....................................................................................................................... 26 Ways to find a solution:................................................................................................................... 26 FAQ ................................................................................................................................................... 28 IDoc views ......................................................................................................................................... 29 Enhancements of basic types ............................................................................................................... 30 ALE ................................................................................................................................................... 32 The business connector and XML ...................................................................................................... 32 Developers of EDI .............................................................................................................................. 33 References to existing documents ........................................................................................................ 33

    2 / 33

78377306.doc printdate: 09/08/10

    EDI, what’s this?

    EDI stands for Electronic Data Interchange which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and visa versa. This mapping is not done by SAP (although the SAP Business Connector does include a mapping tool). If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).

    There are many EDI standards for data formatting including EDIFACT, ANSI X12, ODETTE, VDA, etc. The electronic documents of SAP’s EDI standard are called IDocs (Intermediate Documents). The IDoc type ORDERS, for example, is used to send a purchase order to a vendor.

Below is a screenshot of an ORDERS IDoc.

    The IDoc segment ‘E1EDP01’ is for the PO. Item. In this example there are two of these segments because the PO contains 2 items. To see the IDoc documentation for these segments, go to transaction WE60 and type in the basic type (i.e. ORDERS05).

    3 / 33

78377306.doc printdate: 09/08/10

EDI processes

    Business Processes with EDI in MM and SD

     MM MM SD SDRequest for QuotationRequest for Quotation

    OrderOrder

    Order ChangeOrder Change

    Order ResponseOrder Response

    Despatch AdviceDespatch Advice

    InvoiceInvoice

    CustomerCustomerVendor / SupplierVendor / SupplierDelivery ScheduleDelivery Schedule

    Purchase order

    EDI processing in Purchasing normally starts with the creation of a purchase order (PO) and transmission of an ORDERS IDoc to the vendor. The vendor then automatically creates a sales order. Often the vender sends back an order response via EDI (IDoc ORDRSP). After receipt of the inbound IDoc in the supplier system, the delivery date and price has been updated. It is also possible to maintain tolerances for the prices with IDocs. If changes have to be made, the changes can be sent from the supplier to the vendor using the ORDCHG IDoc. If the goods are packed and a delivery is created, vendors sometimes send dispatch advice (IDoc DESADV) to the supplier.

    Distributed contracts

    Distributed contracts are used to order materials from different plants referencing the same contract. The central contract is located in one system of the company and is distributed to the subsystems via EDI. If a subsystem (e.g. plant) orders materials with reference to this contract, release documentation is sent to the main system.

    For distributing purchasing contracts, use the logical message types BLAORD and BLAOCH (for changes). To send the conditions (i.e. prices), use the COND_A01 and COND_A02 IDocs. Keep in mind that prices are not automatically updated in the distributed contacts of the subsystem (refer to note 114159). The release documentation for distributed contracts is sent via a BLAREL IDoc from the subsystem to the main system.

    Scheduling agreement and delivery schedule

    Scheduling agreements are used for repetitive ordering of the same material. A list of delivery dates and quantities is sent to the vender. This list is called the delivery schedule.

    The scheduling agreement and the delivery schedule are sent separately. To send scheduling agreements, use the ORDERS IDoc. The delivery schedule is sent using the DELFOR IDoc. For release 4.5A, the DELFOR IDoc has been redesigned and replaced with the DELVRY IDoc.

    4 / 33

78377306.doc printdate: 09/08/10

    Request for quotation

    Using EDI, a request for quotation can be sent to a vendor. The message type for these requests is REQOTE. Because there is no inbound processing available in purchasing, it is not possible to receive the vendor’s quotation electronically. At this time, there are no plans to enhance the current functionality

    Miscelanious

    Conditions

    You can send conditions using IDoc technology. The logical message types are COND_A01 and COND_A02. You have to use these IDoc types if you want to send outline agreements or purchasing inforecords..

    Purchasing info record

    To send purchasing info records to another system, use the logical message type INFREC. As previously stated, the COND_A01 and COND_A02 IDocs can be used to send the conditions (i.e. prices) if necessary. The PORDCR IDoc

    An IDoc of logical message type PORDCR is automatically created by the interface of the function module BAPI_PO_CREATE (BAPI). When this type of inbound IDoc is processed, the interface of BAPI_PO_CREATE gets filled automatically and the function module creates a purchase order.

    5 / 33

78377306.doc printdate: 09/08/10

    Customizing

    Output determination

    To generate an EDI output record, the supplier has to be maintained for EDI. This maintenance primarily consists of two steps. The first step is to maintain an EDI partner (e.g. partner type LI). To create/change Partner Profiles use transaction WE20. The second step is to maintain access sequences and condition tables.

    Maintain Partner for EDI

    Below is an example for vendor SIEDLER, taken from the U9C system.

    6 / 33

78377306.doc printdate: 09/08/10

    The vendor SIEDLER has been maintained for outbound EDI message types DELINS, ORDERS and ORDCHG. Since this partner is defined, it is possible to send schedules (DELINS), outline agreements and purchase orders (ORDERS) as well as purchase orders changes. This partner has been maintained for inbound message types DESADV and ORDRSP. Therefore, it is possible to process to dispatch notifications (DESADV) and order responses (ORDRSP).

Below are examples of message types ORDERS, ORDCHG and ORDRSP.

ORDERS:

    7 / 33

78377306.doc printdate: 09/08/10

Message control (ORDERS):

8 / 33

78377306.doc printdate: 09/08/10

Message control (ORDCHG):

9 / 33

78377306.doc printdate: 09/08/10

ORDRSP:

10 / 33

Report this document

For any questions or suggestions please email
cust-service@docsford.com