EDI/ IDOC

[Former Member]

Gurus

Can somebody answer my querries

1. What exactly is gapping and mapping in EDI/IDOC

2. Can anybody send me the functional specifications and test development for EDI! Meaning any specs as a functional consultant we provide EDI team for mapping .

My email ID is adhiasap@gmail.com

Thanks

[Former Member]

Dear Brendon,

what you map in IDOC depends on the IDOC message type.

ORDERS - creation of a sales order

ORDCHG - change of an existing sales order

ORDRSP - confirmation/replication of the sales order

DELINS - creation of a delivery schedule in scheduling agreement

DELORD - creation of a delivery order to the scheduling agreement

EDLNOT - creation of an external agent delivery to the scheduling agreement

GSVERF - creation of a credit advice

SBINV - creation of the invoice

SBWAP - creation of debit/credit memo(requests)

INVOIC - sending the invoice

In the transaction WE60 you can see the fields to every basic IDOC type. Not all fields which could be mapped via IDOC will be transfered automatically (only some ones). All other fields can be mapped to the application with the help of numerous user-exits provided.

The most important transactions:

BD87 - to apply the incoming IDOC

WE19 - to copy / to edit the IDOC and apply this copy

WE02 - to display the IDOC

WE05 - to select IDOCs

WE60 - to see the declared IDOC fields

And here is a general information about IDOC concept in SD:

The EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.

If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).

So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.

That's all concerning the SD-EDI.

Additional processes in SD, where EDI are used:

1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS

2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD

3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT

4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.

It is all processes which are realized in the SD module via EDI.

There is not so much Customizing for EDI. The most entries are required by EDI for the scheduling agreement processing (DELINS, EDLNOT, SBINV). The Customizing of these processes is located in the Customizing of scheduling agreements: SPRO => Sales and Distribution => Sales => Sales Documents => Scheduling agreements with delivery schedules => Control EDI Inbound processing.

General EDI Customizing in SD is available under: SPRO => Sales and Distribution => Electronic Data Interchange => EDI messages => ...

I hope this info helps.

Kind regards,

Akmal Vakhidov

Development Support SAP, Walldorf/Germany

[Former Member]

Brendon,

Gapping/mapping - This process is done when your client wants to send some application document (can be sales order confirmation, Purchase order, Invoice) to it's customer (or vendor). For for discussion purpose, lets say your client needs to send billing document to a customer. So one way is print it on invoice format and send it via mail or Faxing the printout or emailing it. or finally sending it via EDI.

EDI is the data exchange medium, which is going to send the data relevant for billing to the customer. Standard 810 EDI is used for invoice transaction. SAP billing document creates a IDOC which is triggered from a message type (output type at billing header level).

An IDOC contains Data records, which contain billing document data. Now not all the data on this IDOC is required to be sent to customer, only certain fields are enough to tell the customer about the bill - fields like Payer #, payment terms, Customers PO #, SO#, delivery #, line #, Material #, Net value # and overall billing document value. But on IDOC we have much more data available then this.

Now on EDI mapping we will sit with an EDI contact, and map what fields on IDOC means and where it can be put on EDI segments. Like

idoc field name EDI Field name

Purchase order # E1EDK02-BELNR BIG04

Invoice # E1EDK02-BELNR BIG02

Payer E1EDKA1-PARTN N104

Payment terms E1EDK18-PRZNT ITD01

Material E1EDP19-MATNR IT101

Like this you will have to mapp all the fields on a excel spreadsheet so EDI can have logic in their subsystem to send the invoice to customer successfully.

sample of mapping document - http://www.erpgenie.com/sapgenie/docs/template_o810v4010_partner.xls

Naren