Documente Academic
Documente Profesional
Documente Cultură
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 1 of 19
Table of Contents
1. PRE-REQUISITES FOR EDI.............................................................................................4
1.1. SAP R/3 system, Interfaces and EDI subsystem.............................................................4
1.2. Business Rules and Conditions........................................................................................4
1.3. Overview of Concepts.....................................................................................................5
1.3.1. Document types (IDoc):...........................................................................................5
1.3.2. Message Control.......................................................................................................5
2. ONCE-OFF CONFIGURATION PER CLIENT..............................................................7
2.1. Set-up SAP Business workflow for error handling (PPOM)...........................................7
2.1.1. Create Org Unit........................................................................................................7
2.1.2. Create Positions........................................................................................................7
2.1.3. Assign Holders.........................................................................................................7
2.1.4. Assign workflow tasks..............................................................................................7
2.2. Configure EDI inbound processing workflow.................................................................8
2.2.1. Create Batch User....................................................................................................8
2.2.2. Configure Workflow for RFC (SWUB)...................................................................8
2.2.3. Verify Workflow Customising (SWU3)...................................................................8
2.2.4. Workflow Configuration Notes................................................................................8
2.3. Cross Application /IDoc interface/EDI components: (SPRO)........................................8
2.3.1. Create IDoc number range: (OYSN)........................................................................9
2.3.2. Create Port definition number range: (OYSN) ........................................................9
2.3.3. Create IDoc type number range: (OYSN)................................................................9
2.3.4. Set-up IDoc administration: (WE46).......................................................................9
2.3.5. Convert error processes:.........................................................................................10
2.3.6. Activate event coupling for inbound processing.....................................................10
2.3.7. Authority Management .........................................................................................11
2.4. Cross Application/ ALE Components:..........................................................................11
2.4.1. PORT Definition (WE21).......................................................................................11
2.4.2. Control of EDI processes in R/3............................................................................13
2.4.2.1. Maintain: Outbound Process Code (WE41)...................................................13
2.4.2.2. Maintain: Inbound Process Code (WE42)......................................................13
2.4.2.3. Control: System Process Codes (WE40)........................................................14
2.4.2.4. Control: Status maintenance (WE47).............................................................14
2.4.2.5. Control: Partner Types (WE44).....................................................................14
2.4.2.6. Control: Forward Inbound (WE45)................................................................15
2.4.2.7. Control: Status Process code (WE56)............................................................15
3. MM IMG CONFIGURATION.........................................................................................16
3.1. Global settings (IMG):...................................................................................................16
3.1.1. Units of measure (IMG Global settings):..........................................................16
3.2. Link Schema to Purchase order.....................................................................................16
3.3. Link application to EDI interface via message control:.................................................16
3.4. Enabling Multiple Output for Purchase Orders (Optional)............................................16
3.5. Link Output type (fax=2, E-mail=7) to NEU (Purchasing)...........................................17
4. SD APPLICATION REQUIREMENTS..........................................................................18
4.1. EDI Configurations.......................................................................................................18
4.1.1. Conversion of SAP item categories to IDOC item categories (VOE1)..................18
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 2 of 19
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 3 of 19
1.
The IDoc interface, which consists of IDoc types and function modules
that form the interface to the application. There are IDocs available that
support orders and invoices. IDocs are identical for inbound and outbound
processing.
EDI: IDocs: ORDERS, ORDRSP, ORDCHG and INVOIC
The EDI subsystem, which converts the IDoc types into EDI message
types and vice versa. This component of the EDI architecture is not
supplied by SAP, thus the existing ASI EDI subsystem will be used.
EDI: Gentran PC sub-system.
EDI Interface between SAP R/3 system and EDI subsystem. For inbound
processing, this involves opening the inbound message file, and processing
the IDoc messages. For outbound processing, this involves selecting the
outbound documents, creating an outbound message file and writing this
file to the shared directory. The exact transfer times are scheduled using
batch jobs. Please refer to EDI Production Configuration Guide for
further interface details.
EDI: Make use of an NFS shared drive to share files between UNIX
and PC.
EDIFACT message type - this will link to the IDoc that will be used in
SAP R/3.
Time that the supplier will open his mailbox - this will dictate when
transmissions can take place.
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 4 of 19
Description
ORDERS01
ORDCHG
Order change
ORDERS01
ORDERS
Order
ORDERS01
ORDRSP
Order response
INVOIC01
INVOIC
Invoice
partner independent
identical for inbound and outbound processing
dependent only on message types
independent of EDI standards
independent of subsets.
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 5 of 19
Output procedure
1-many
Condition types
1-1
Access Sequence
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 6 of 19
2.
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 7 of 19
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.
Page 8 of 19
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 9 of 19
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 10 of 19
Page 11 of 19
/home/edi/<portname>/
status.idoc
Leave blank if using above
For example, the name of a port using dynamic file naming on system
F01, client 610 would be named EDIF01610A. The exchange directory
would be named edif01610a. Similarly, the name of port using static file
naming on system PG1, client 600 would be EDIPG1600B. The
exchange directory name would be edipg1600b.
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.
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 12 of 19
ComponentsALE
Extensions
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:
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 13 of 19
Page 14 of 19
RSETESTP
LOGSYS
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 15 of 19
3.
MM IMG CONFIGURATION
3.1. Global settings (IMG):
3.1.1. 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).
Page 16 of 19
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)
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 17 of 19
4.
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.
4.1. EDI Configurations
4.1.1. Conversion of SAP item categories to IDOC item categories (VOE1)
IMG S&D EDI EDI Messages Conversion of SAP item
categories to IDOC item categories
Add the following entry:
For Standard Item description :
OR
LDN
Sold-to party
Vendor
Bill-to party
Ship-to party
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 18 of 19
2
OR
DIEN
TAD
LDN
3
OR
LEIS
LDN
5.
Directory: /var/www/apps/conversion/tmp/scratch_3/205096182.doc
Doc Name: 205096182.doc
Print Date: 13/08/2000 05:06:00 PM
Version 1.1
Page 19 of 19