TM 9.0 Configurations and Processes from BW Perspe...

Former Member · ‎08-20-2013

TM 9.0 Configurations and Processes from BW Perspective

Introduction

Integration of SAP TM with the SAP NetWeaver Business Warehouse component supports the creation of management reports and the evaluation of cost and revenue by business partners and transportation data over a period of time. The reports evaluate carriers, costs, customers, transport means, or destinations etc.

This document provides Configuration process in TM system from BW perspective for the implementation of TM 9.0 related Standard queries.

Configurations and Pre-settings required for the Processes defined in this document.

SAP NetWeaver 7.3, Business content 7.37 SP04
TM 9.0 source system has to be created in the BW system.
RFC connections have to be established between TM and BW system.
TM Datasources should be replicated in BW system.
All TM related BI objects has to be installed from Business content.

TM 9.0 Datasources and Standard Reports

The document provides us the set of TM activities to be followed for the reporting requirements mentioned in Standard Reports section further below in this document.

Datasources

Below screenshot provides few activated TM9.0 Master datasources and Transactional datasources in RSA6 in TM system.

TM Masterdatasources

TM Transactional Datasources

Standard Reports

Below table indicates the TM datasources and the associated Standard BW reports which are the part of TM 9.0 implementation process.

The Standard reports mentioned below are associated with TM datasources which are part of Business content 7.37 SP04.

Queries- Description	Technical name	Datasources	MPRO
Customer Analysis	0TMS_MP11_Q0001	0SCM_TM_TRQ, 0SCM_TM_TRQ_ITM	Transportation Request
Party/Location Analysis	0TMS_MP11_Q0002	0SCM_TM_TRQ, 0SCM_TM_TRQ_ITM	Transportation Request
Carrier Analysis	0TMS_MP12_Q0001	0SCM_TM_TOR, 0SCM_TM_TOR_ITM	Transportation Order
Discrepancy Analysis	0TMS_MP12_Q0003
Transport Analysis	0TMS_MP12_Q0002
Costs by No. of Units shipped per Period and Mode of Transp	0TMS_MP13_Q0003	0SCM_TM_TOR, 0SCM_TM_TOR_ITM, 0SCM_TM_SFIR_PTC, 0SCM_TM_SFIR, 0SCM_TM_SFIR_ITM, 0SCM_TM_SFIR_IV	TM Cost Analysis
Costs per Carrier	0TMS_MP13_Q0004
Planned / Actual Costs per Transport	0TMS_MP13_Q0001
Planned / Actual Costs per Transport - Details	0TMS_MP13_Q0002
Planned Costs on Stage Level	0TMS_MP13_Q0005
Top 5 Carrier by Transportation Mode and Costs	0TMS_MP13_Q0002_1_EXT
Top 5 Consignee by Transportation Mode and Costs	0TMS_MP13_Q0002_2_EXT
Top 5 Shipper by Transportation Mode and Costs	0TMS_MP13_Q0002_3_EXT
Overall Regions Planned / Actual Costs by Transportation Mo	0TMS_MP13_Q0001_4_EXT
Planned / Actual Costs by Carrier and Transportation Mode	0TMS_MP13_Q0001_1_EXT
Planned / Actual Costs by Consignee and Transportation Mode	0TMS_MP13_Q0001_2_EXT
Planned / Actual Costs by Shipper and Transportation Mode	0TMS_MP13_Q0001_3_EXT
Planned Revenue for Top 5 Customers	0TMS_MP16_Q0002	0SCM_TM_TRQ, 0SCM_TM_TRQ_ITM, 0SCM_TM_CFIR_PTC, 0SCM_TM_CFIR, 0SCM_TM_CFIR_ITM	TM Revenue Analysis
Planned Revenue per Customer	0TMS_MP16_Q0001		TM Revenue Analysis
Business Share by Carrier	0TMS_MP19_Q0001	0SCM_TM_BSH	Business Share
Transportation Allocations by Carrier	0TMS_MP20_Q0001	0SCM_TM_TAL	Transportation Allocation
Emissions per Trade Lane	0TMS_MP21_Q0005	0SCM_TM_TOR, 0SCM_TM_TOR_ITM, 0SCM_TM_TOR_TDL, 0SCM_TM_TOR, 0SCM_TM_TOR_ITM,0SCM_TM_TOR_STG	Trade Lane Analysis
Stage Analysis per Trade Lane	0TMS_MP21_Q0003
Trade Lane Analysis	0TMS_MP21_Q0004
Trade Lane Analysis per Transport	0TMS_MP21_Q0002
Transported Weight per Trade Lane	0TMS_MP21_Q0001
TR Based Stages Analysis	0TMS_MP22_Q0001	0SCM_TM_TRQ, 0SCM_TM_TRQ_ITM, 0SCM_TM_TRQ_STG	Transportation Request Stages
Stage Analysis	0TMS_MP23_Q0001	0SCM_TM_TOR, 0SCM_TM_TOR_ITM, 0SCM_TM_TOR_STG	Transportation Order Stages

Customization for BW Relevance and Data Transfer

Unlike the usual Cockpit activities done in the ECC system to fetch the data to the datasources of different modules like SD, MM, PP, FI etc. the TM system activities require a different set of configurations, settings to transfer data from TM to BW system with specific process to fill the setup tables of TM.

Below are the Configurations and settings in TM system for Data transfer from TM system to BW system for the first time which are part of SPRO activities.

In Customizing activities specify the status to BW relevance for the following object types:

Forwarding Order Types
Forwarding Quotation Types
Freight Order Types
Freight Booking Types
Freight Unit Types
Transportation Unit Types
Forwarding Settlement Document Types
Freight Settlement Document Types
Order-Based Transportation Requirement Types
Delivery-Based Transportation Requirement Types
Transportation Allocations and Business Shares

E.g., BW Relevance Setting for Freight Order Types, Go to SPRO and set BW Relevance.

Similarly specify the status to BW relevance for other object types mentioned above.

In the Customizing activity, the lifecycle status has to be set to Completed for extracting business documents belonging to the TOR, TRQ and FSD business object.

E.g., if a freight order is completed, the system automatically extracts the freight order data to datasources.

Step 1: Activation of TM datasources

Once the above customization are through the TM datasources have to be activated in TM system as specified in below activities.

Go to RSA5

Activate datasources related to TM. Place the cursor on the datasource and click activate datasources tab at the top of the screenshot.

Similarly activate all the TM Master datasources and Transactional data sources.

Go to RSA6 and Check for the activated datasources. The datasources once activated in RSA5 will be available in RSA6.

Step 2: Initialization and Filling setup tables

The TM datasources mentioned in initial part of this document fetches data through the standard Function modules which requires initializing and filling up the setup tables of TOR, TRQ, SFIR, CFIR, BSH and TAL datasources.

The BW analysis scenarios are based on the following main extraction objects:

Transportation Order (TOR)
Transportation Request (TRQ)
Freight Settlement (FSD i.e., SFIR)
Forwarding Settlement (FWSD i.e., CFIR)
Transportation Allocation (TAL)
Business Share (BSH)

Initializing the setup tables

Go to transaction /n /SCMTMS/BWIS for Initialization of Set Up table and execute

Filling setup tables

Ø Transportation Order (TOR)

The Transportation Order is a Freight order or Shipment created after Planning. From BW perspective the TOR data is used in the Carrier analysis, stage analysis, Trade Lane and Discrepancy analysis etc.

Go to transaction /n/SCMTMS/BWIU_TOR - to fill the Set Up table of TOR and execute

We can find the number of records filled in the TOR tables.

Similarly go to other TM transactions to fill the set up tables of TM datasources with data as mentioned in next sections.

Ø Transportation Request (TRQ)

Orders that are created in SAP ERP can be transferred to SAP TM, where they are stored as order-based transportation requirements (TRQ). The data from TRQ is used in Customer, Party/Location analysis and TR based stage analysis.

Go to transaction /n /SCMTMS/BWIU_TRQ - to fill the Set Up table of TRQ and execute.

Ø Freight Settlement (FSD i.e., SFIR)

Freight settlement is used to trigger the verification of an invoice, received from a supplier or carrier for transportation charges, against a freight settlement document.

Go to transaction /n /SCMTMS/BWIU_SFIR - to fill the Set Up table of SFIR and execute.

Ø Forwarding Settlement ( FWSD i.e., CFIR)

We can trigger the creation of an invoice to give to a customer for transportation service charges. We can also trigger the creation of a credit memo to give a credit to a bill-to party. The SAP ERP system creates the invoice and gives the credit that are relevant for accounting.

Go to transaction /n /SCMTMS/BWIU_CFIR - to fill the Set Up table of CFIR and execute

Ø Ø Business Share (BSH)

Each business share contains information about tolerances, penalty costs, and the ideal quantity to be transported by a carrier. This information is taken into account by the optimizer as a soft constraint during the planning process.

Go to transaction /n /SCMTMS/BWIU_BSH - to fill the Set Up table of BSH and execute

Ø Transportation Allocation (TAL)

A transportation allocation may specify the minimum and/or maximum quantities that a carrier can deliver within a bucket (hard constraint during automatic carrier selection).

Go to transaction /n /SCMTMS/BWIU_TAL - to fill the Set Up table of TAL and execute

Step 3: Extractor Checker

Once the setup tables are filled go to RSA3 and check for the number of records in the extractor checker for the activated datasources. Give the activated datasource name and execute.

we get the number of records available in that datasource.

To view the contents of datasource select ALV Grid highlighted above.

Similarly check the contents in other activated TM datasources.

Step 4: Scheduling full load

Once the TM datasources are filled with data in TM system go to BW system. Ensure the pre-settings mentioned at the begining of this document are fulfilled to proceed with below activities in BW.

Go to RSA1, Infoproviders and related infopackage of the TM datasource and schedule the full load.