DOC

advanced_guide_to_edi_configuration

By Dana Anderson,2014-10-14 12:51
6 views 0
SAP IDOC

Advanced guide to EDI configuration 4.5B

    Advanced guide to EDI configuration

    4.5B

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 1 of 17

Advanced guide to EDI configuration 4.5B

    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 ............................................................................................ 4 1.3.1. Object types (IDoc): ....................................................................................... 4 1.3.2. Message Control ............................................................................................ 5 2. ONCE-OFF CONFIGURATION PER CLIENT ....................................................... 6

    2.1. Set-up SAP Business workflow for error handling (PPOM) .................................... 6 2.1.1. Create Org Unit .............................................................................................. 6 2.1.2. Create Positions ............................................................................................. 6 2.1.3. Assign Holders ............................................................................................... 6 2.1.4. Assign workflow tasks.................................................................................... 6 2.2. Configure EDI inbound processing workflow ......................................................... 6 2.2.1. Create Batch User .......................................................................................... 7 2.2.2. Configure Workflow for RFC (SWUB) .......................................................... 7 2.2.3. Verify Workflow Customising (SWU3) .......................................................... 7 2.2.4. Workflow Configuration Notes ...................................................................... 7 2.3. Cross Application /IDoc interface/EDI components: (SPRO) ................................. 7 2.3.1. Create IDoc number range: (OYSN) .............................................................. 7 2.3.2. Create Port definition number range: (OYSN) ................................................ 8 2.3.3. Create IDoc type number range: (OYSN) ....................................................... 8 2.3.4. Set-up IDoc administration: (WE46) .............................................................. 8 2.3.5. Convert error processes: ................................................................................. 9 2.3.6. Activate event coupling for inbound processing .............................................. 9 2.3.7. Authority Management ................................................................................... 9 2.4. Cross Application/ ALE Components: .................................................................... 9 2.4.1. PORT Definition (WE21) ............................................................................... 9 2.4.2. Control of EDI processes in R/3 ................................................................... 11 3. MM IMG CONFIGURATION ................................................................................. 14

    3.1. Global settings (IMG): ......................................................................................... 14 3.1.1. Units of measure (IMG Global settings): .................................................. 14

    3.2. Link Schema to Purchase order ............................................................................ 14 3.3. Link application to EDI interface via message control: ......................................... 14 3.4. Enabling Multiple Output for Purchase Orders (Optional) .................................... 14 3.5. Link Output type (fax=2, E-mail=7) to NEU (Purchasing) .................................... 15 4. SD APPLICATION REQUIREMENTS ................................................................... 16

    4.1. EDI Configurations .............................................................................................. 16 4.1.1. Conversion of SAP item categories to IDOC item categories (VOE1) .......... 16

    4.1.2. Partner functions .......................................................................................... 16 4.2. S&D Sales Configurations .................................................................................... 16 4.2.1. Maintain Item categories .............................................................................. 16 4.2.2. Assign Item categories.................................................................................. 16 4.2.3. Assign Schedule line categories .................................................................... 17 Print Date: 14/10/2010 13:35:00 Version 1.0 Page 2 of 17

Advanced guide to EDI configuration 4.5B

    4.3. S&D Pricing Configurations ................................................................................. 17

    4.3.1. EDI pricing condition types .......................................................................... 17

    4.3.2. SD Pricing procedures (V/08) ...................................................................... 17

Print Date: 14/10/2010 13:35:00 Version 1.0 Page 3 of 17

    Advanced guide to EDI configuration 4.5B

    1. PRE-REQUISITES FOR EDI

    1.1. SAP R/3 system, Interfaces and EDI subsystem

     The SAP EDI architecture consists of:

    ; EDI-enabled applications, to support the automatic processing of business

    transactions.

    ; 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.

    Eg. ORDERS02

    ; 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.

     Eg: Gentran or Mercator

    ; 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.

    1.2. Business Rules and Conditions

    In the Interchange Agreement, with each vendor, the following will be stipulated:

    ; EDIFACT / ANSI X12 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.

    ; Trading partner identification number.

    ; Version of EDIFACT / ANSI X12 that the supplier is using. 1.3. Overview of Concepts

    1.3.1. Object types (IDoc):

    IDoc type Logical message type Description

    ORDERS01 ORDCHG Order change

    ORDERS01 ORDERS Order

    ORDERS01 ORDRSP Order response

    INVOIC01 INVOIC Invoice

    IDoc types are:

    ; partner independent

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 4 of 17

    Advanced guide to EDI configuration 4.5B

; identical for inbound and outbound processing

    ; dependent only on message types

    ; independent of EDI standards

    ; independent of subsets.

    1.3.2. Message Control

    Message control is a „conditioning technique‟ used to direct output for business documents created by SAP transactions. For example, when a purchase order is created, it is the message control component that determines that the document should be sent to a printer, or alternatively via EDI or fax.

    Message control consists of a hierarchy of decision structures (called condition components) to allow for flexible output determination. Each application is associated with an output procedure, and each procedure can be made up of several condition types (for multiple output). Access sequences are used to regulate how and whether a condition type is to be processed.

     Conditioning Technique

     1-1

     Output procedure i.e.MM/SD application associated with

     1-many How to handle output

     Eg. NEU (for purchase order via EDI)

     Output Medium (EDI) Condition types Timing (Immediately etc.)

     Partner Function Output Spool 1-1

     “How and If” of Condition Types Based on run-time data

     Determines output by MM or SD Access Sequence Output at run-time General vs Specific

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 5 of 17

    Advanced guide to EDI configuration 4.5B

    2. 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.

    2.1. 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:

    2.1.1. 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.

    2.1.2. Create Positions

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

    empty.

    2.1.3. Assign Holders

    Assign holders to each position.

    2.1.4. 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

    2.2. Configure EDI inbound processing workflow

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

    methods.

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 6 of 17

    Advanced guide to EDI configuration 4.5B

2.2.1. 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

    2.2.2. 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.

    2.2.3. 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. 2.2.4. 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.

    2.3. 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

    2.3.1. Create IDoc number range: (OYSN)

    Number range for IDocs called EDIDOC.

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 7 of 17

    Advanced guide to EDI configuration 4.5B

    Will use internal numbering.

    Use only one number range.

    2.3.2. Create Port definition number range: (OYSN)

    Number range for generated port names, called EDIPORT.

    Will use internal numbering.

    Use only one number range.

    2.3.3. 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. 2.3.4. 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

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 8 of 17

    Advanced guide to EDI configuration 4.5B

    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. 2.3.5. Convert error processes:

    Information about error processes - confirm that they exist. 2.3.6. 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.

    2.3.7. Authority Management

    This is about the authority to perform a particular action in R/3, for

    example EDI Administrator. Refer to appendix A.

    2.4. Cross Application/ ALE Components:

    2.4.1. 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

    Command file parameters - mandatory

    Logical destination: SERVER_EXEC

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 9 of 17

    Advanced guide to EDI configuration 4.5B

Directory: /home/edi//

    Shell script: start_converter

    Automatic button:(1-5) Will not be used

    Outbound file parameters - mandatory

    Directory: /home/edi/

    Outbound file: edi_out

    See text below Function module:

    Inbound file parameters

    Directory: /home/edi/

    Inbound file: edi_in

    See text below. Function module:

    Status file parameters

    Directory: /home/edi//

    Outbound file: status.idoc

    Function module: Leave blank if using above

    ; Both the portname and the exchange directory should be created

    according to the same naming convention. However, the portname

    should be in upper case whereas the corresponding directory name

    should be in lower case (see examples below).

     Portname (upper case):

    

     Exchange directory name (lower case):

     /home/edi/

     where consists of:

     EDI

     is the name of system on which port exists eg.

     DEV, PRD etc.;

     is name of client on system which will use this

     port; and

     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.

    Print Date: 14/10/2010 13:35:00 Version 1.0 Page 10 of 17

Report this document

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