Steps for EDI

[Former Member]

Hi ,

Can anybody give me step by step procedure to configure EDI?

Thanks in Advance for your time and information.

Max.Points for best answer

RamaChandra

[Former Member]

Dear Rama Chandra,

Below infirmation and links give breif idea about the EDI

The EDI interface is used to connect an EDI subsystem to the SAP system. EDI subsystems perform all EDI-related tasks such as Converting the data Handling messages or interchanges Communications Managing the partner profiles Monitoring processing. The EDI interface is based on IDoc technology. IDoc technology is independent of EDI standards. All data is exchanged via files between the SAP System and the EDI subsystem. The synchronous RFC (remote function call) is used to define the time of transfer of the files between both systems. Via the EDI interface, the following data can be exchanged:

Outbound IDocs. IDocs are transferred from the SAP System to the EDI subsystem.

Inbound IDocs. IDocs are transferred from the EDI subsystem to the SAP System.

Status report. To inform the SAP System of the progress of processing of the outbound IDocs, the EDI subsystem transfers the status report to the SAP System.

http://www.erpgenie.com/sap/sapedi/edi_subsystems.htm

See the below links

/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact

/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield

/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield

http://www.stylusstudio.com/edi/XML_to_X12.html

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2...

Check this for Conversions-

/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf

http://www.seeburger.com

http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf

http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt

http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integratio...

Cn you plz let me know ifyou have any queries

Gentran is one of the most wide used edi subsytems

What is EDI?

EDI is commonly defined as the computer-to-computer exchange of common business documents using a standardized format. It is more specifically defined as the automatic company-to-company exchange of information for common business functions such as purchasing, invoicing, remittance advises, transportation, etc. With EDI, electronically transmitted data replaces paper documents (e.g., purchase orders, invoices, purchase acknowledgment) throughout the business transaction cycle. Data is “translated” into a standard format sent most commonly through public data transmission networks.

EDI stands for ELCTRONIC DATA INTERCHANGE.

as the name specifies,it is used to transfer the data from SAP to non sap or nonsap to SAP.

with particular standards like ASNSI12,EDICFACT,etc...

Hope this helps you

Prem

[Former Member]

I got outstanding answers from outstanding people in minutes.I am really confused to whom i should give the points.any ways give me some time,i will go through all the links and will allot the points.

Please remember that points are not indicators for your help.

I owe a lotto everybody for your time and information

Thanks again

RamaChandra

[Lakshmipathi]

Hi Rama

Check the following links

http://help.sap.com/saphelp_47x200/helpdata/en/4b/ad4ba417fd11d28a360000e829fbbd/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/4c/df7e9ef0dd11d2b74b0000e8160175/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm

Thanks

G. Lakshmipathi

[Former Member]

Hi

Refer below

http://www.sap-edi.com/dnn/

http://www.erpgenie.com/sapedi/index.htm

Message was edited by:

SHESAGIRI.G

[Former Member]

Hi Rama Chandra

once-off CONFIGURATION PER CLIENT

The following transactions should be followed in sequence. Most of the data should be pre-configured by SAP, however it is important that this is confirmed by examining each entry.

Set-up SAP Business workflow for error handling (PPOM)

Purpose: A workflow organisation (e.g. “EDI Department”) may be set-up where exceptions and error-messages generated during EDI processing can be directed (instead of only to a single user).

3.1H: Transaction: PPOM (Tools -> Business Engineering -> Business Workflow -> Organisation -> Definition Tools -> Organisational plan)

Define an Organisational Structure to be used in EDI Admin set-up by following the next steps:

Create Org Unit

Create an Org Unit, e.g. EDI Dept with a long description of EDI Department - All IDoc Notifications.

Choose the Staff assignments icon and complete the details.

Create Positions

Create the 'Manager' and 'staff' positions, leaving the job descriptions empty.

Assign Holders

Assign holders to each position.

Assign workflow tasks

Assign the workflow tasks to the entire department (for our purposes).

Click on Department, select the Task profile icon, assign task.

To assign the inbound order's error task, enter a search string of OR* in the pop-up menu. Select the following:

ORDCHG_Error

ORDERS_Error

ORDSRP_Error

For Invoices use INV* as a search string and add the following:

INVCON_Error

INVOIC_FI_Er

INVOIC_MM_Er

Configure EDI inbound processing workflow

Purpose: To activate the automatic processing of inbound IDocs using workflow methods.

Create Batch User

Confirm the following details with the Basis System Administrators and/or Workflow Configuration Specialist:

A user for batch processing should be defined, typically user WF-BATCH.

The batch user should have SAP_ALL and SAP_NEW authorisations.

The batch user should be set as a background user

Configure Workflow for RFC (SWUB)

Enter the batch user name (WF-BATCH) as well as the password.

Click the “Test” button (or press the F5 key). This should result in a message “RFC Test successful”. Any other result indicates that the batch user WF-BATCH has not been set-up correctly or the password is incorrect.

The details should be saved using the “Save” button or by pressing the F11 key.

Verify Workflow Customising (SWU3)

The “Test RFC” item should have a red cross next to it.

Press the “Autocustomize” button (F6) and workflow should be re-customised.

Use the “Test RFC dest.” Button or press the F7 key to test the RFC destination. This should result in the message “Ping performed successfully”.

The red cross on the item list should now be a green tick.

Workflow Configuration Notes

If this procedure does not work as expected, it may be due a problem in the release code for V3.1H. Confirm that OSS Note 81974 has been applied by a Basis administrator. This requires a source code change to be made.

Cross Application /IDoc interface/EDI components: (SPRO)

Purpose: To enable/configure EDI parameters and configuration for entire client.

All changes to default configuration should be documented using the “Notes” facility in the IMG. (Ref. Appendix B - SAP Notes Format). This assumes that an ALE/EDI project view has been set up by the BASIS system configuration team. (Ref. Appendix A - Authorisations).

3.1H: IMG ðCross-Application Components ðIDoc interface/Electronic Data Interface ðIDoc interface

Create IDoc number range: (OYSN)

Number range for IDocs called EDIDOC.

Will use internal numbering.

Use only one number range.

Create Port definition number range: (OYSN)

Number range for generated port names, called EDIPORT.

Will use internal numbering.

Use only one number range.

Create IDoc type number range: (OYSN)

Number range for IDocs called EDIDocTYP.

Assigns numbers internally for IDoc types when they result from the automatic combination of basic IDoc types and customer extensions.

Set-up IDoc administration: (WE46)

Set up EDI client-specific system parameters:

For Rel 3.1H:

MAXSYNERR - maximum number of syntax errors that will be logged in the status records. Default is 15, for testing use 30 (maximum allowed).

EDIADMIN - IDoc administration

User to notify in case of an EDI Basis error.

Type in EDIADMIN, tab to System Parameter field, select organisational unit - SAP will insert Org structure number as created by SAP EDI workflow (refer previous point).

TESTPORT eg. SAPF01

Name of the port that will be used as a default in the IDoc turn-around utility. Type portname in, since it can't be selected.

SEGDVCLASS - Development class for segment editor.

Optional. When IDocs are extended, this is the default development class for the R/3 correction and transport system.

IDOCEDIT (Ref. Chapter 1-26)

Optional. If blank, system allows user-developed IDoc extensions.

Convert error processes:

Information about error processes - confirm that they exist.

Activate event coupling for inbound processing

Once the workflow has been set up as described in the section “Configure EDI inbound processing workflow”, the event coupling may be activated using this item. This allows inbound processing to be started when IDocs are read into the SAP system.

Dialogue box with message “Activate IDoc Inbound?” should appear.

Choose the “Yes” Button.

Message “Event-event receiver coupling activated successfully” should appear.

Authority Management

This is about the authority to perform a particular action in R/3, for example EDI Administrator. Refer to appendix A.

Cross Application/ ALE Components:

PORT Definition (WE21)

Definition of directory location and name of shell script to be executed to trigger EDI subsystem.

3.1H: IMG ð Cross-Application Components ð ALE ð Communication ð Manual maintenance of partner profile ð Define port

Under port type File create the relevant port names for example SAPF01.

The version indicator control how the control record of outbound IDocs is created - an indicator of '2' will write the control record in the format of R/3 release 3.0.

Please note that these parameters depend on the EDI sub-system features. For further details, refer to the EDI Technical Interface guide.

Enter the rest of the parameters as follows:

Parameters is a single alphabetical character such as ‘a’,’b’ etc. typically, ‘a’ will denote dynamic outbound file naming (used for testing) whereas ‘b’ will denote static outbound file naming. All ports will use static inbound filenames.

For example, the name of a port using dynamic file naming on system DEV, client 110 would be named EDIDEV110A. The exchange directory would be named edidev110a.

Note that the function “EDI_PATH_CREATE_USERNAME_DT_TM” can be used in the “Function module” field of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.

Control of EDI processes in R/3

Maintain: Outbound Process Code (WE41)

3.1H: IMGðCross-Application ComponentsðALEð Extensions ð Outbound

Check that the outbound EDI processes in the R/3 system are defined. Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.

The following assignments are available for R/3:

Maintain: Inbound Process Code (WE42)

3.1H: IMGðCross-Application Components ð ALE ð Extensions ð Inbound

Check that the inbound EDI processes in the R/3 system are defined. Indicates what kind of inbound processing to execute.

A long list of options is available under Processing by function module, relevant ones are:

INVF INVOIC FI Invoice receipt (Financial Accounting)

INVM INVOIC MM Invoice verification (Mat Management)

ORDC ORDCHG Change customer order

ORDE ORDERS Create customer order

ORDR ORDRSP Purchase order confirmation

Control: System Process Codes (WE40)

Choose Processing by task. Check that the codes indicating the type of EDI processing error are defined. The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.

Control: Status maintenance (WE47)

Check that the codes indicating status of IDoc processing are defined. The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50. These values are delivered by SAP and cannot be customised.

Control: Partner Types (WE44)

Check that the codes that identify the commercial relationships between the receiver and sender are defined. Values are delivered by SAP. Names of the programs and routines that validates the entry of the EDI trading partner ID:

Partner type Report name Form routine

B - Bank RFETESTP READ_T012

KU - customer RSETESTP READ_KNA1

LI - vendors RSETESTP READ_LFA1

LS - logical system ( ALE) RSETESTP LOGSYS

Control: Forward Inbound (WE45)

Allows for the forwarding of IDocs to a specific application. Contains the exactly defined destination of an inbound IDoc within the SAP system. Usually no changes are required.

Control: Status Process code (WE56)

Choose Processing by task: The following set-up has been provided as default:

Process code: EDIS

Identification: TS30000078

Description: EDI-IDoc status record processing

The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.

MM IMG configuration

Global settings (IMG):

Units of measure (IMG à Global settings):

The ISO code is important for EDI. It is used to convert the internal SAP units of measure into standard units.

The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).

Link Schema to Purchase order

Check the following:

3.1H: IMG ð MM ð Purchasing ð Message determination ð Message determination ð Message Schemas

Execute transaction “Define Message Schemas for Purchase Order” (M/36)

Select transaction: Assign Schema to purchase order

Add: Usage =B for output

Application = EF for purchase order

Procedure = RMBEF1 for purchase order

Link application to EDI interface via message control:

3.1H: IMG ð MM ð Purchasing ð Messages ð Output Control

Check following under Output Control:

Condition table

Access sequence

Message types

Message schema

Output control

Enabling Multiple Output for Purchase Orders (Optional)

For example: EDI & Printing

3.1H: IMG ð MM ð Purchasing ð Message determination ð Message determination ðAccess sequence

Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)

Goto Define message types à maintain message types:

Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)

Goto Message Schema à define message schema à maintain output determination procedure:

Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)

Goto Processing program à Define Processing program à Output program: Purchase Order.

Add a NEU1 record to table TNAPR. The program FORM Routine and layout must be specified. (Copy an existing NEU record). (Transaction OMTB)

Goto Processing program à Define Processing program à Output by partner type.

Add NEU1 record for VN (vendor). (Transaction OMTG)

Link Output type (fax=2, E-mail=7) to NEU (Purchasing)

3.1H: IMG ð MM ð Purchasing ð Message determination ð Message determination ðAccess sequence

Goto Processing program à Define Processing program à Output program: Purchase Order.

Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)

Goto Processing program à Define Processing program à Output by partner type.

Add NEU record for VN (vendor). (Transaction OMTG)

SD application requirements

Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.

Reference SAP Course manual Chapter 11.

EDI Configurations

Conversion of SAP item categories to IDOC item categories (VOE1)

3.1H: IMG à S&D à EDI à EDI Messages à Conversion of SAP item categories to IDOC item categories

Add the following entry:

For Standard Item description : 0 OR LDN

Typically error message: ''Transaction LDN is not defined".

Partner functions

3.1H: IMG à S&D à EDI à EDI Messages à Configure EDI Partnersà Partner à Application à Partner function

Check that the following partner functions exist: (at least)

SP Sold-to party

VN Vendor

BP Bill-to party

SH Ship-to party

Note - the German abbreviation is passed to the IDoc.

S&D Sales Configurations

Maintain Item categories

IMG à S&D à Sales à Sales document à Sales doc item à Define item categories

Add LDN for standard item:

Item type = B

Relev for billing = B

Tick following: Bus data item

Sched line allowed

Credit active

Pricing

Screen seq. grp = N

Assign Item categories

3.1H: IMG à S&D à Sales à Sales document à Sales doc item à Assign item categories

Add/Update the following entries:

1 2 3

Sales doc type OR OR OR

Item category group NORM DIEN LEIS

Item category LDN TAD

LDN

LDN

Assign Schedule line categories

3.1H: IMG à S&D à Sales à Sales document à Schedule lines à Assign Schedule line categories

Add Item category LDN to table (with no other parameters).

S&D Pricing Configurations

EDI pricing condition types

3.1H: IMG à S&D à Basic functions à Pricing à Pricing control à Define condition types à Maintain condition types

Maintain the following condition types:

EDI 1 - Calculate type =C for Quantity

EDI 2 - Calculate type = B for Fixed amount

SD Pricing procedures (V/08)

IMG à S&D à Basic functions à Pricing à Pricing control à Define & Assign pricing procedures

Maintain pricing procedure for ZVAA01 (Standard).

Select control and add EDI1 and EDI2 as steps 1 and 5 respectively with no other parameters.

Reward if useful to u

[Former Member]

hi

]

<a href="http://help.sap.com/saphelp_470/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm">http://help.sap.com/saphelp_470/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm</a>