user exists for edi

[Former Member]

hi,

Can u give ne the user exists for the following edi.

edi 850 Purchase order

edi 855 PO acknowledgment

edi 810 Invoices

edi 204

edi 856 ASN

Please u can give any user exist for the above.

[Former Member]

Hi

Search the Individual Fun Module programs that are related to the individual IDOC types.

In those fun module programs you will find certain customer functions like

CALL CUSTOMER-FUNCTION '0001'.

double click on 0001 and write the code

Reward points for useful Answers

Regards

Anji

[Former Member]

hI,

Are you using process code ME10 (FM IDOC_OUTPUT_ORDERS)?

If you are then there is user exits EXIT_SAPLEINM_001 that can be used to add additional information to IDoc control record.

For example you can use EDIDC-MESCOD and/or EDIDC-MESFCT to populate the mapping for your purchasing organization (EKORG).

You can code something like this inside user exits.

IF EKKO-EKORG = '0001'

CONTROL_RECORD_OUT-MESCOD = '1'.

ELSEIF EKKO-EKORG = '0002'.

CONTROL_RECORD_OUT-MESCOD = '2'.

ELSE.

...

ENDIF.

then you can use CONTROL_RECORD_OUT-MESCOD to distinguish/map purchase organization into EDI850 in the middleware system (Gentran).

EDI855:

Please check this document. This docment will guide to setup an inbound for EDI850 but you can set to be an outbound process.

http://www.erpgenie.com/sapgenie/docs/template_i850v4010_sample.xls

For EDI855, you can use logical message ORDRSP, IDoc types ORDERS01 to ORDERS04 and process code ORDR.

edi810:

What is EDI Invoicing?

An EDI 810 Invoice is an electronic version of a paper Invoice or bill. Companies use EDI to reduce the errors and costs associated with the manual keying of data, and to speed up the process of sending and receiving Invoices.

A supplier will use the 810 Invoice to communicate to a buyer the specific items, price, and quantities they have delivered and now must be paid for by the buyer. Payment terms will usually accompany the billing information.

How it used in ABAP?

Each EDI 810 Invoice document will have data organized into segments and data elements. Each segment contains at least one data element. Each data element is a data field. Examples of data elements on the Invoice include vendor number, item, quantity, price per item, street address, city, state and zip code, just like on a paper Invoice.

Prior to used in SAP, you need to have middleware i.e SAP XI, to map/translate EDI810 segment data into an IDoc format of message type INVOIC. Then you can use ALE technology to process this IDoc up to generating an invoice document in SAP.

Please check this links for more information on EDI810 and mapping.

http://www.erpgenie.com/sapgenie/docs/810.xls

http://www.erpgenie.com/sapgenie/docs/sapedi/invoicin.xls

http://www.erpgenie.com/sapgenie/docs/sapedi/invoicou.xls

http://www.erpgenie.com/sapgenie/docs/template_o810v4010_partner.xls

http://www.erpgenie.com/sapgenie/docs/template_o810v4030_partner.xls

<b>rEWARD POINTS</b>

rEGARDS

[Former Member]

skk,

thx a lot