13
Settings for ERP-TM Integration via esa-Services History Author Regina Braniek, Giovanni Olivieri Version 01 Date 21.10.2008

Settings for ERP-TM Integration via Esa-Services

  • Upload
    h240488

  • View
    49

  • Download
    0

Embed Size (px)

DESCRIPTION

Settings for ERP-TM Integration via Esa-Services

Citation preview

Page 1: Settings for ERP-TM Integration via Esa-Services

Settings for ERP-TM Integration via esa-Services

History Author Regina Braniek, Giovanni Olivieri Version 01 Date 21.10.2008

Page 2: Settings for ERP-TM Integration via Esa-Services

1 REQUIREMENTS ...................................................................................................................................... 3 1.1 SYSTEM REQUIREMENTS....................................................................................................................... 3 1.2 MASTER DATA REQUIREMENTS............................................................................................................ 3

2 SETTINGS IN ERP..................................................................................................................................... 3 2.1 MAINTAIN OUTPUT TYPES.................................................................................................................... 3 2.2 MAINTAIN OUTPUT DETERMINATION PROCEDURE............................................................................... 5 2.3 ASSIGN OUTPUT DETERMINATION PROCEDURES.................................................................................. 5 2.4 ASSIGN SERVICE OUTPUT CONTROL FOR DELIVERIES .......................................................................... 5 2.5 DEFINE NEW ENTRY FOR CONDITION TYPE TMS0:............................................................................... 6 2.6 TRANSPORTATION PLANNING POINT DETERMINATION......................................................................... 6 2.7 CREATE CONDITION RECORD ............................................................................................................... 7 2.8 MASTER DATA...................................................................................................................................... 7 2.9 BASIC SETTINGS BETWEEN ERP AND PI ............................................................................................... 7

3 PI SETTINGS .............................................................................................................................................. 8 3.1 SERVICES WITHOUT PARTY................................................................................................................... 8 3.2 RECEIVER DETERMINATION.................................................................................................................. 9 3.3 RECEIVER AGREEMENT ...................................................................................................................... 10

4 TM SETTINGS.......................................................................................................................................... 11 4.1 DEFINE SHIPMENT REQUEST TYPE AND CATEGORY ........................................................................... 11 4.2 DEFINE DEFAULT TYPE FOR SRQ CATEGORY .................................................................................... 12 4.3 CONDITIONS ....................................................................................................................................... 12

5 FAQ ............................................................................................................................................................ 13

Page 3: Settings for ERP-TM Integration via Esa-Services

1 Requirements

1.1 System Requirements Transportation Management: TM6.0 or higher ERP: ECC-SE 603 SP01 + note 1228329, or ECC-SE 604 Process Integraion: PI 7.0

1.2 Master Data Requirements Master data has to be created in the ERP system and ciffed to the TM system:

- product master data - customer master data: when ciffing, make sure locations are being created

automatically for the customer

2 Settings in ERP

2.1 Maintain Output Types In the ERP customizing create a new output type TMS0 or make sure that it already exists with data maintained as visible on the screenshot.

Page 4: Settings for ERP-TM Integration via Esa-Services

No Partner Function!

Page 5: Settings for ERP-TM Integration via Esa-Services

2.2 Maintain Output Determination Procedure Define a new entry to a new or already exisiting procedure for Condition Type TMS0:

2.3 Assign Output Determination Procedures Assign deliveries (header)

2.4 Assign Service Output Control for Deliveries

Page 6: Settings for ERP-TM Integration via Esa-Services

2.5 Define new entry for Condition Type TMS0:

2.6 Transportation Planning Point Determination

Page 7: Settings for ERP-TM Integration via Esa-Services

Make new entries for your Shipping Point (and Shipping Type):

2.7 Create Condition Record Tx VV22 Output Type: TMS0 press button ‘Key Combination’ and choose ‘Delivery Type’ Make a new entry:

2.8 Master Data Be aware that all master data must be ciffed from ERP to TM:

- customers and vendors (create also locations during ciffing) - Materials (products and handling units)

2.9 Basic Settings between ERP and PI Make sure the integration between ERP and PI is set up. This contains following settings:

1. Integration Engine Configuration in the ERP system:

Page 8: Settings for ERP-TM Integration via Esa-Services

2. RFC connestion as maintained above (INTEGRATIONSERVER_X7T of type H (HTTP Connection to ABAP System)

3. RFC connestions SLDAPICUST and LCRSAPRFC of type T must be set up (connections to the SLD on the PI system)

4. System Landscape Settings: the ERP system needs to be defined in the PI 5. in table LCRT_CLNTCACHE all business systems as defined in the SLD on PI must

be visible

3 PI Settings In the Process Integration the whole scenario will look like this:

3.1 Services without Party Define your ERP and TM systems as business systems with communication channels:

Page 9: Settings for ERP-TM Integration via Esa-Services

3.2 Receiver Determination

Page 10: Settings for ERP-TM Integration via Esa-Services

3.3 Receiver Agreement

Page 11: Settings for ERP-TM Integration via Esa-Services

4 TM Settings

4.1 Define Shipment Request Type and Category

Page 12: Settings for ERP-TM Integration via Esa-Services

4.2 Define Default Type for SRQ Category

4.3 Conditions

4.3.1 SRQ type determination Maintain condtion /SCMTMS/SRQ_TYPE, e.g. for user defined in the RFC connection from PI to TM:

4.3.2 SRQ organization units determination Maintain condition /SCMTMS/SQR_ORGUNITS, e.g. for the user defined in the RFC connection from the PI to TM system:

Page 13: Settings for ERP-TM Integration via Esa-Services

5 FAQ Question: Error occurred during back-routing Error in communication channel in XI. But the SRQ was created successfully. Answer: This error can be ignored. Please see note 832965. Question: Error during proxy processing an exception with the type /SCMTMS/CX_CPX_SHIPMENT_RQ occurred, but was neither handled locally, nor declared in a RAISING clause Application Error in TM. Answer: Check if the Shipment Request Type 0001 is created in customizing. Question: Locations, Business Partners and Quantity are not displayed correctly? Answer: Please apply the latest SP for the PI and TM System. Check Table /SCMTMS/C_CD_IE, this should not be empty. Check that the locations exist in the TM System. Check that table /SCMB/TBUSSYS contains an entry for the ERP and TM System. The field BSKEY in table /SCMB/TBUSSYS for the ERP System should be the sender port, this can be seen in TA WE19 by double clicking on the first row.