convergent invoicing enablement for sap transportation

© 2012 SAP AG

Dietmar-Hopp-Allee 16 D-69190 Walldorf

SAP Custom Development

Convergent Invoicing Enablement for SAP Transportation Management

Configuration Guide and Software Description

Version Status Date

1.0 Released to Customer

April 20, 2012

Customer

Configuration

Guide Customer

© 2012 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Title: Convergent Invoicing Enablement for SAP Transportation Management Version: 1.0 Date: April 20, 2012

of 24

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more

information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Configuration

Guide Customer



of 24

Table of Contents

1 About This Document ................................................................................... 4

1.1 Purpose and Scope ........................................................................................................ 4

1.2 Target Audience ............................................................................................................. 4

1.3 Glossary .......................................................................................................................... 4

1.4 Related Documents ........................................................................................................ 5

1.5 Important SAP Notes ...................................................................................................... 5

2 Software Description .................................................................................... 6

2.1 Overview ......................................................................................................................... 6

2.2 System Landscape and Prerequisites ............................................................................ 6

2.3 Integral Parts of the Software ......................................................................................... 7

2.4 Preconfiguration Steps in SAP ECC............................................................................... 7

2.5 Implementation and Configuration.................................................................................. 7

2.5.1 Basic Customizing Settings ....................................................................................... 7

2.5.2 Required Configuration Settings for Creation Service .............................................. 8

2.5.3 Sample Configuration Settings for Service Execution ............................................. 13

2.5.4 Required Configuration Settings for Cancellation Service ...................................... 17

3 Business Scenarios .................................................................................... 18

3.1.1 Overview .................................................................................................................. 18

3.1.2 Technical System Landscape ................................................................................. 18

3.1.3 Configuration Details ............................................................................................... 20

4 Security Information ................................................................................... 22

4.1 Fundamental Security Guides ...................................................................................... 22

4.2 Authorizations ............................................................................................................... 22

5 Operations Information .............................................................................. 23

5.1 Monitoring ..................................................................................................................... 23

5.1.1 Application Log ........................................................................................................ 23

5.1.2 Interface Monitoring ................................................................................................. 23

5.2 Error Handling ............................................................................................................... 24

Configuration

Guide Customer



of 24

1 About This Document

1.1 Purpose and Scope The Configuration Guide provides a central starting point for the technical implementation and configuration of convergent invoicing enablement for SAP Transportation Management. It describes all activities necessary for the implementation and configuration of this software, along with information about the components that are required during the implementation process.

Convergent invoicing enablement for SAP TM supports the following business scenarios:

● Creation of billable items based on forwarding settlement documents from SAP TM

● Cancellation of billable items based on forwarding settlement documents from SAP TM

To allow for an efficient implementation process, all the information within this document is structured according to the scenarios mentioned above.

1.2 Target Audience This document is intended for the following target audiences:

● Business consultants with FI-CA and convergent invoicing knowledge

● Technical consultants with process integration knowledge

● Partners

● Customers

● System administrators

1.3 Glossary

Abbreviation / Term Definition

BIT Billable item

Term used in Contract Accounts Receivable and Payable [FI-CA]. A billable item contains certain information needed for billing.

Business scenario A set or sequence of processes that describes the steps required to fulfill a business need.

Convergent invoicing Method of invoicing where billing data from various sources is aggregated into a single invoice and is processed together.

FI-CA Contract Accounts Receivable and Payable

A subledger of SAP Financial Accounting set up for processing a large number of postings automatically.

FWSD Forwarding settlement document

A document that is sent to SAP ERP to request the creation of an invoice to be sent to a customer.

SAP application An SAP software solution that serves a specific business area, for example, ERP.

Configuration

Guide Customer



of 24

Abbreviation / Term Definition

SAP CI SAP Convergent Invoicing

A business function that encompasses the functions of billing and invoicing in Contract Accounts Receivable and Payable.

SAP ECC SAP ERP Central Component

SAP NetWeaver PI system SAP NetWeaver Process Integration system

Enables different versions of SAP and non-SAP systems to communicate with each other.

SAP TM SAP Transportation Management

The system in which forwarding settlement documents are created.

1.4 Related Documents Solution Manager Documentation for convergent invoicing enablement for SAP Transportation Management available on SAP Service Marketplace at http://service.sap.com/swdc

1.5 Important SAP Notes

Make sure that you read the SAP Notes before you start implementing the software. The SAP Notes contain the latest information about the installation as well as corrections to the installation information.

Related SAP Notes

SAP Note Number

Title Description

1613283 FKKBIX: Selection of billable items Applies to software component FI-CA Release 605 to 605 and is included in support package SAPK-60506INFICA.

This note includes an important coding part which is relevant for this software.

1696394 Installation of TMLSPERP 100 on ERP 6.0

1696398 Release strategy for the ABAP add-on TMLSPERP 100

1696472 TMLSPERP 100: Add-On Support Packages

http://service.sap.com/swdc

Configuration

Guide Customer



of 24

2 Software Description

2.1 Overview Transportation companies need to process the billing information for their customer orders from the

transportation business. The common SD billing (sales and distribution), which is the traditional solution,

does not have the possibility to collect and aggregate billable items and cannot handle mass invoicing

(like for phone bills where all line items are accumulated in one bill). Hence, the transfer of billing data via

SD to FI-CA (Contract Accounts Receivable and Payable) is not possible, which causes delays in the

process.

However, FI-CA enables processing of a large number of postings or invoices automatically and is better

suited for automated mass invoicing than SD billing.

Convergent invoicing enablement for SAP Transportation Management, built on the ERP Central Component, bridges the gap of system communication by collecting billing data from the SAP Transportation Management system and passing it to FI-CA to enable convergent invoicing (method of invoicing where billing data from various sources is aggregated into a single invoice and is processed together). This software makes it possible that an invoice request is created in the SAP Transportation Management system and transferred to ECC, either scheduled periodically or triggered by specified events. This triggers that in FI-CA all up-to-date billing information is collected, and this data can be pulled into one billing document.

2.2 System Landscape and Prerequisites The following figure gives an overview of the system landscape for convergent invoicing enablement for SAP TM.

Figure 1: System Landscape

Forwarding settlement documents (indicated as CFIR in the figure above) are created in SAP TM and transferred to SAP ECC by means of an XML interface. Based on this data, billable items are created in the FI-CA component of SAP ECC. These billable items can be collected and aggregated for billing and invoicing according to the configuration.

If there are errors in the data from SAP TM, billable items have to be excluded, by means of an XML interface, from the billing and invoicing processes.

The XML interfaces that communicate between SAP TM and SAP ECC are termed as enterprise services. The enterprise services are used to create and cancel billable items.

Configuration

Guide Customer



of 24

Convergent invoicing enablement for SAP TM deals with the implementation of these two enterprise services in the FI-CA component of SAP ECC.

The enterprise services require as minimum the following system components:

SAP Transportation Management 8.0

SAP enhancement package 5 for SAP ECC 6.0

As a prerequisite for convergent invoicing enablement for SAP TM, the SAP ECC system needs to be set up and must include software components and business function sets as described in the Solution Manager Documentation.

2.3 Integral Parts of the Software

Scenario/Business Process Service Implementation and Configuration Process

Create billable items based on FWSD from SAP TM

Enterprise service to create billable items.

See Implementation and Configuration – Basic Settings, Section 2.5.2 in particular

Cancel billable items based on FWSD from SAP TM

Enterprise service to cancel billable items.

See Implementation and Configuration – Basic Settings, Section 2.5.4 in particular

2.4 Preconfiguration Steps in SAP ECC For successful software installation, it is required that you execute the following preconfiguration steps:

1. Create CI include CI_FKKBIXBIT_IT

Use transaction SE11 to create data type CI_FKKBIXBIT_IT C2C BIT Management

Customer Fields Main Items

Append component type /TMLSPERP/C2C_ADD_FIELDS as include toCI_FKKBIXBIT_IT

Activate CI_FKKBIXBIT_IT2. Unpack business configuration (BC) set /TMLSPERP/BC_TM_FICA_BIT_FWSD (transaction

SCPR20)

Once these steps are carried out, proceed with the settings for implementation and configuration.

2.5 Implementation and Configuration The Implementation Guide (IMG) covers all steps of the implementation process. The following chapters describe the settings to be made in Customizing for convergent invoicing enablement for SAP TM.

All Customizing activities relevant to this topic are located in the following path (transaction spro or

FICAIMG): SAP Customizing Implementation Guide Financial Accounting (New) Contract Accounts

Receivable and Payable Integration Billing in Contract Accounts Receivable and Payable. All references to Customizing paths relate to this IMG node unless indicated otherwise.

2.5.1 Basic Customizing Settings In order to use the enterprise services, you need SAP FI-CA basic Customizing, which must include the following objects:

1. Master Data

Configuration

Guide Customer



of 24

Business Partner

Contract Account

2. FI-CA objects

Company code activation for FI-CA

Set up application area

Maintenance of central settings for FI-CA postings

Set up main transactions and subtransactions for invoicing processes

3. Convergent invoicing (required only for the cancellation process)

Configuration of at least one billing process

Configuration of at least one invoicing process

2.5.2 Required Configuration Settings for Creation Service

2.5.2.1 Maintain Billable Item Class

In order to use the billable item creation service, you need a billable item (BIT) class. The BC set /TMLSPERP/BC_TM_FICA_BIT_FWSD mentioned in Chapter 2.4 already includes the BIT class “FWSD”. Manual entry is therefore not required.

To maintain a billable item class, use transaction FKKBIXBIT_CONF or choose the following path:

SAP Customizing Implementation Guide Financial Accounting (New) Contract Accounts Receivable

and Payable Integration Billing in Contract Accounts Receivable and Payable Billable Item

Classes Maintain Billable Item Classes.

The following screen appears:

Figure 2: Maintain Billable Item Class

Define Standard Interface Components

For integration between SAP TM and SAP CI, the BIT class must contain standard interface components as well as customer fields. Since the standard interface components are already included in the BC set /TMLSPERP/BC_TM_FICA_BIT_FWSD, you only need to check if the required set of interface components is activated for the BIT class. To do so, choose the Interface button from the screen above.

Configuration

Guide Customer



of 24

The required standard interface components are as follows:

Basic Data for Billing

Receivables/Payables (Extended Interface)

Assignment of External/Internal Acct Assignment

Assignment of External/Internal Tax Code

External Reference of Billable Item (32 Characters)

Billing Quantity

Basic Data for Payment Processing

Card Payment

Payment Card Data

Maintain Customer Fields

In addition to the standard interface components, the BIT class must also contain a set of customer fields. To add customer fields to the BIT class, proceed as follows:

Check SAP include CI_FKKBIXBIT_IT

Add the customer fields from CI_FKKBIXBIT_IT to the BIT class (transaction

FKKBIXBIT_CONF -> Change mode -> Customer Fields button)

Figure 3: Change Billable Item Class – Customer Fields Button

Configuration

Guide Customer



of 24

On choosing the Customer Fields button, the following screen appears:

Figure 4: Maintain Customer Fields – Status Group Billable

The screen Maintain Customer Fields shows the customer fields for status group B (Billable)

To view the customer fields for status group R (Raw), choose the Other Status Group button.

The following table provides an overview of the customer fields that need to be available in status group B (billable) as well as R (raw data) in order to use this software:

Field Name Data Type Length Short Description

ORIGIN_LAND CHAR 3 Origin Country Code

DEST_LAND CHAR 3 Destination Country Code

SHP_FR_LOC_ID CHAR 16 Ship From Location ID

SHP_FR_LOC_TY CHAR 4 Ship From Location Type Code

SHP_FR_LOC_AD CHAR 128 Ship From Location Address

SHP_TO_LOC_ID CHAR 16 Ship To Location ID

SHP_TO_LOC_TY CHAR 4 Ship To Location Type Code

SHP_TO_LOC_AD CHAR 128 Ship To Location Address

REQ_PI_DAT_FR DATS 8 Requested Pickup Date From

REQ_PI_TIM_FR TIMS 6 Requested Pickup Time From

REQ_PI_DAT_TO DATS 8 Requested Pickup Date To

REQ_PI_TIM_TO TIMS 6 Requested Pickup Time To

ACC_PI_DAT_FR DATS 8 Acceptable Pickup Date From

Configuration

Guide Customer



of 24


ACC_PI_TIM_FR TIMS 6 Acceptable Pickup Time From

ACC_PI_DAT_TO DATS 8 Acceptable Pickup Date To

ACC_PI_TIM_TO TIMS 6 Acceptable Pickup Time To

REQ_DL_DAT_FR DATS 8 Requested Delivery Date From

REQ_DL_TIM_FR TIMS 6 Requested Delivery Time From

REQ_DL_DAT_TO DATS 8 Requested Delivery Date To

REQ_DL_TIM_TO TIMS 6 Requested Delivery Time To

ACC_DL_DAT_FR DATS 8 Acceptable Delivery Date From

ACC_DL_TIM_FR TIMS 6 Acceptable Delivery Time From

ACC_DL_DAT_TO DATS 8 Acceptable Delivery Date To

ACC_Dl_TIM_TO TIMS 6 Acceptable Delivery Time To

GRO_WGTH_QTY QUAN 13 Gross Weight Transportation Quantity

GRO_WGTH_UNT UNIT 3 Gross Weight Transportation Unit

GRO_VOL_QTY QUAN 13 Gross Volume Transportation Quantity

GRO_VOL_UNT UNIT 3 Gross Volume Transportation Unit

NET_WGTH_QTY QUAN 13 Net Weight Transportation Quantity

NET_WGTH_UNT UNIT 3 Net Weight Transportation Unit

INS_DEC_AMNT DEC 17 Insurance Declared Amount

INS_DEC_CUR CUKY 3 Insurance Declared Currency

CUS_DEC_AMNT DEC 17 Customs Declared Amount

CUS_DEC_CUR CUKY 3 Customs Declared Currency

PACKAGE CHAR 16 Package

PAYTERM CHAR 4 Cash Payment Types

PACKTYPE CHAR 4 Package Type

MATNR CHAR 16 Product

SHIP_PTY_ID CHAR 10 Shipper Party ID

SHIP_PTY_AD CHAR 128 Shipper Party Address

CONS_PTY_ID CHAR 10 Consignee Party ID

CONS_PTY_AD CHAR 128 Consignee Party Address

ORD_PTY_ID CHAR 10 Ordering Party ID

ORD_PTY_AD CHAR 128 Ordering Party Adress

Configuration

Guide Customer



of 24


TEXT_HDR CHAR 128 Text Collection FWSD

TEXT_ITM CHAR 128 Text Collection Item

FWO CHAR 10 TM Forwarding Order

FWO_ITM CHAR 10 TM Forwarding Order Item ID

ACTIONCODE CHAR 2 TM Action Code

SETDOCTYP CHAR 4 TM Forwarding Settlement Document Type (FWSD Type)

PAYTERM CHAR 4 Cash Payment Types

Activate Billable Item Class

In order to use the creation service, you must ensure that the BIT class is activated (transaction

FKKBIXBIT_CONF).

2.5.2.2 Generate Interfaces for Billable Item Classes

To generate interfaces, use transaction FKKBIXBIT_GEN or choose the following path: SAP Customizing

Implementation Guide Financial Accounting (New) Contract Accounts Receivable and Payable

Integration Billing in Contract Accounts Receivable and Payable Billable Item Classes Generate Interfaces for Billable Item Classes.

The following screen appears:

Figure 5: Generate Interface for Billable Item Classes

To generate interface for the billable item class, choose the Generate button.

During the generation of the BIT class interface, the system will automatically generate the following set of data objects, which will be used during further processing:

Object Type Object Name Short Description

Function Module /1FE/FWSD_BIT_CREATE_API Generation of Billable Items for Class FWSD

Table /1FE/1FWSD0IT_API Class FWSD Structure Type API - Main Items

Configuration

Guide Customer



of 24

Object Type Object Name Short Description

Table /1FE/1FWSD0PY_API Class FWSD Structure Type API - Payment Data

Table /1FE/0FWSD0IT Items for Class FWSD - Raw Data

Table /1FE/0FWSD0PY Items for Class FWSD - Raw Data

Table /1FE/0FWSD1IT Items for Class FWSD - Raw Exceptions

Table /1FE/0FWSD1PY Items for Class FWSD - Raw Exceptions

Table /1FE/0FWSD2IT Items for Class FWSD - Billable

Table /1FE/0FWSD2PY Items for Class FWSD - Billable

Table /1FE/0FWSD3IT Items for Class FWSD - Exceptions

Table /1FE/0FWSD3PY Items for Class FWSD - Billed

Table /1FE/0FWSD4ITS0 Items for Class FWSD - Simulated Billed

Table /1FE/0FWSD4PY00 Items for Class FWSD - Billed

Table /1FE/0FWSD4PYS0 Items for Class FWSD - Simulated Billed

2.5.3 Sample Configuration Settings for Service Execution

The configuration settings described below are merely examples. These settings need to be adapted or replaced based on customer-specific business requirements.

2.5.3.1 Basic Data for Billable Item Management

To process billable items, some basic Customizing settings are required:

Subprocess of Billing

The subprocess, together with the item type, specifies the business significance of an individual billable item. Each subprocess is assigned to one or more billable item classes.

A subprocess is a self-sufficient processing branch within a billing process for the selection and grouping of billable items and forming a billing document. Billable items are immediately assigned to a subprocess when they are created. It is not possible for the system to process them together with billable items of another subprocess in a common billing document.

For integration between SAP TM and SAP CI, the following subprocesses have been defined and assigned to billable item class FWSD:

Subprocess Description of Subprocess

TM01 Final Invoice

TM99 Summary of Charges

Configuration

Guide Customer



of 24

Based on the SAP TM activity code, the SAP CI subprocess is determined. The determination takes place within event YF_BITRAW_TKF8101EV_05 for checking and enriching raw data items.

Additional subprocesses can be configured and mapped in accordance with the business requirements.

Billable Item Type

The billable item type, together with the subprocess, specifies the business significance of an individual billable item. Each item type is assigned to one or more subprocesses.

For integration between SAP TM and SAP CI, the SAP TM forwarding settlement type has been mapped 1:1 to the billable item type.

For test purposes, the item types have been set up and defined as follows:

Subprocess Item Type Name of Billable Item Type

TM01 CD01 CD Forwarding Settlement Type

TM01 OF09 Test FWSD

TM99 CD01 CD Forwarding Settlement Type

TM99 OF09 Test FWSD

Source Transaction Type

The source transaction type specifies the business meaning of the source transaction ID from the perspective of billing and from the perspective of the external system. It also defines rules for how the source transaction ID and the source transaction are interpreted in follow-on processes. The combination of a source transaction type and a source transaction ID form a source transaction.

For SAP TM – SAP CI integration, a new source transaction type has been defined with the following settings. This source transaction type should be used for any SAP TM – SAP CI integration.

Source Transaction Type

Individual Reference

Internal Source ID

Individual Processing

Short Description

FWSD X SAP TM Forwarding Settlement Document

Individual Reference: Specifies that an explicit reference to the source transaction of the billable item is entered in the billing document.

Each SAP CI billing document will have a direct reference to the FWSD from which it is created.

Internal Source Transaction ID: Specifies that the source transaction ID of a billable item is assigned internally by the system.

This is not used for SAP TM –SAP CI integration. The forwarding settlement document ID will be used as unique reference.

Individual Processing: Specifies that individual processing of billable items of a source transaction is allowed.

This is not supported for SAP TM – SAP CI integration. It needs to be ensured that all billable items assigned to one FWSD will be processed together and summarized in one billing document.

Configuration

Guide Customer



of 24

2.5.3.2 Billable Item Management

Billable Item Management defines the processing rules for uploading billable items in SAP CI.

Billable Item Management within SAP CI provides the possibility to create billable items with the following status (Customizing for each billable item class):

Raw: Raw data does not have to be complete nor does it have to be consistent. The data inthe individual fields can be changed.

Billable: Billable items must be both complete and consistent in order to be billed.

Excepted: Items that have the status “raw excepted” and “billable excepted” are excludedfrom further processing. That means that they are not considered during transfer or duringbilling.

First, the system checks the items to know if they can be processed further. If at least one item has a serious error (for example, unknown source transaction type), the system immediately terminates the processing of items. The system returns an error message.

If processing is possible, the system performs another check. The check of each item can have one of the following results:

Has Errors: The item has an error.

Incomplete: The item has no errors, but it does not have correct master data assignment.

Consistent: The item has no errors and is complete.

Within SAP CI, one of the following check options can be activated:

- space – Add all items as checked

o Items with errors are returned.

o Incomplete items are added as raw data.

o Consistent items are added as billable items.

- 0 – Add consistent items as raw data

o Items with errors are returned.

o Incomplete items as well as consistent items are added as raw data.

- 1 – Add all items as raw data

o Items with errors, incomplete items as well as consistent items are added as raw data.

- 2 – Add items with errors as raw data

o Items with errors and incomplete items are added as raw data.


- 3 – Return incomplete items

o Items with errors and incomplete items are returned.


- 4 – Add only if all items are without errors

o If all items are without errors, then these items are added as checked.

Configuration

Guide Customer



of 24

o Incomplete items are added as raw data.

o Consistent items are added as billable items. If at least one item has errors, then all itemsare returned.

There can be several items for one source transaction. The system always processes all items of a source transaction together. That means if one item of a source transaction has errors, then all of the items of the source transaction receive the same treatment.

For billable item class FWSD, the settings are as follows:

Class BW-Relevant Program Enhancements

FWSD 05 - /TMLSPERP/BITRAW_TKF8101EV_05

The program enhancement is used to enrich the FWSD data provided by SAP TM with additional information which is only available in SAP CI. For test purposes, we provide an example function module YF_BITRAW_TKF8101EV_05, which includes the following conversion rules:

Determine SAP CI subprocess from SAP TM action code

Select contract account from SAP TM business partner (always the first contract account isselected)

Set default value (A1) for tax determination code

At the time of implementation, this sample function module must be replaced with a customer-specific function module, which supports conversion rules defined by business requirements.

2.5.3.3 Billable Item Transfer

SAP CI provides the possibility to define flexible account assignment derivation rules using the following posting areas:

8120 - Account Assignments for Billable Items

8121 - Transaction Determination for Billable Items

For integration between SAP TM and SAP CI, these posting areas are used as described below:

The posting area 8120 is used to determine the following account assignments based on the sales area information provided by SAP TM.

Company code

Division

Business area

Segment

The sales area data provided in the FWSD XML file covers the following attributes:

Sales Organization ID

Sales Group ID

Configuration

Guide Customer



of 24

Sales Office ID

For test purposes, the posting area has been configured as follows:

Key 1

Sales Org.

Key 2

Sales Grp.

Key 3

Sales Off.

Key 4 Company Code

Division Business Area

Segment

50000050 00000000 00000000 0001

50000609 00000000 00000000 0001

The posting area 8121 is used to define the derivation of the main transaction and subtransaction (debit and credit) of billable items.

The interface determines the main transactions and subtransactions based on the following charge element details included in the FWSD XML file.

Charge Element – Type Code

Charge Element – Category Code

Charge Element – Sub Category Code

If required, the SAP CI subprocess (= SAP TM action code) as well as the SAP CI billable item type (= SAP TM forwarding settlement type) can be included in the determination of main transaction and subtransaction as well.

For test purposes, the posting area has been configured as follows:

Key 1

Type Code

Key 2

Cat Code

Key 3

Sub Cat

Key 4 Maintr

Debit

Subtr

Debit

Maintr

Credit

Subtr

Credit

CD_TEST01 CD1 CD_01 6000 0010 6000 0020

CD_TEST01 CD1 CD_02 6000 0010 6000 0020

CD_TEST01 CD2 CD_01 6000 0010 6000 0020

CD_TEST01 CD2 CD_02 6000 0010 6000 0020

CD_TEST02 CD1 CD_01 6000 0010 6000 0020

CD_TEST02 CD1 CD_02 6000 0010 6000 0020

CD_TEST02 CD2 CD_01 6000 0010 6000 0020

CD_TEST02 CD2 CD_02 6000 0010 6000 0020

2.5.4 Required Configuration Settings for Cancellation Service

SAP CI does not support a real cancellation of billable items; instead billable items are marked as exceptions. If a billable item has been excepted, the system moves these items to a separate table, which excludes them from billing.

Configuration

Guide Customer



of 24

For cancellations triggered by SAP TM, the exception reason needs to be set up as follows:

Reason Name of Exception Reason Status Group

TM SAP TM BIT cancellation All

When a billing document is reversed, the system automatically excepts (that is excludes) the items. In these cases, the system determines the exception reason via the reversal reason used for reversal of the billing document.

The following reversal settings have been defined for reversals triggered by FWSD cancellation from SAP TM:

Reversal Reason Exception Reason Name of Exception Reason

TM TM SAP TM BIT cancellation

3 Business Scenarios

3.1.1 Overview

The enterprise services cover two business scenarios: Creation of billable items and cancellation of billable items obtained from forwarding settlement documents from SAP TM.

3.1.2 Technical System Landscape

Three technical systems are required:

SAP TM system, which sends FWSDs

SAP ECC system, which creates or cancels billable items based on the FWSD

SAP NetWeaver PI system, which integrates the SAP ECC system and the SAP TM system

The figures below give an overview of the interaction between the systems during the creation and cancellation of billable items. The boxes in yellow indicate the offerings of convergent invoicing enablement for SAP TM, the boxes in grey show what is already available in SAP TM and SAP ECC, and the box in orange shows the configuration activity that is carried out in SAP NetWeaver PI.

Configuration

Guide Customer



of 24

Figure 6: System Interaction – Process to Create Billable Item

A customer freight invoice request (forwarding settlement document) is created in SAP TM. The outbound service for Customer Freight Invoice Request is called. The standard outbound service in SAP TM needs to be mapped to the inbound service for convergent invoicing enablement for SAP TM in SAP ECC. This is a configuration activity within SAP NetWeaver PI (Integration Builder).

The inbound service for convergent invoicing enablement for SAP TM creates a billable item. The service sends the status back to the sender system (SAP TM) by. This is done using the standard confirmation service to update the CFIR document in SAP TM (status and number of billable item).

Configuration

Guide Customer



of 24

Figure 7: System Interaction – Process to Cancel Billable Item

A customer freight invoice request (forwarding settlement document) is to be cancelled in the SAP TM system. The outbound service for Customer Freight invoice Request cancellation is called. The standard outbound service in SAP TM needs to be mapped to the inbound service for convergent invoicing enablement for SAP TM in SAP ECC. This is a configuration activity within SAP NetWeaver PI (Integration Builder).

The inbound service for convergent invoicing enablement for SAP TM cancels a billable item. The service sends the status back to the sender system (SAP TM). This is done using the standard confirmation service to update the CFIR document in SAP TM (status and number of billable item).

3.1.3 Configuration Details

The new developed services in SAP ECC do not correspond to the outbound services in SAP TM. It is therefore necessary to map the standard outbound service from SAP TM to the new service in SAP ECC. This is a configuration task, which will be done in the Integration Builder of SAP NetWeaver PI.

It is also necessary to create the end points of the new services in SAP NetWeaver PI.

Name of the standard services in the SAP TM system:

CustomerFreightInvoiceRequestSUITERequest_Out_V1

CustomerFreightInvoiceRequestSUITECancellationRequest_Out_V1

Configuration

Guide Customer



of 24

CustomerFreightInvoiceRequestSUITEConfirmation_In_V1

Name of the service in the SAP ECC system:

CustomerFreightInvoiceRequestSUITEConfirmation_Out_V1

Name of the services in the SAP ECC system which are available via convergent invoicing enablement for SAP TM:

CustomerFreightBillableItemRequest_In

CustomerFreightBillabelItemCancellationRequest

Configuration

Guide Customer



of 24

4 Security Information

4.1 Fundamental Security Guides Convergent invoicing enablement for SAP TM is based on SAP ERP 6.0, enhancement package 5. Therefore, the related guides also apply to this software.

For more information about specific security-related topics, see the following resources on SAP Service Marketplace or SDN:

Topic Quick Link on SAP Service Marketplace or SDN

Security http://service.sap.com/security

http://sdn.sap.com/irj/sdn/security

Platforms http://service.sap.com/platforms

Infrastructure http://service.sap.com/securityguide

→ Infrastructure Security

For a complete list of available SAP Security Guides, see SAP Service Marketplace at http://service.sap.com/securityguide.

4.2 Authorizations The authorization objects in FI-CA form the basis for creation or cancellation of billable items.

http://service.sap.com/security

http://sdn.sap.com/irj/sdn/security

http://service.sap.com/platforms

http://service.sap.com/securityguide

http://service.sap.com/securityguides

Configuration

Guide Customer



of 24

5 Operations Information Designing, implementing, and running your SAP applications at peak performance 24 hours a day is vital for your business success. This chapter contains important information on how to smoothly operate the software for convergent invoicing enablement for SAP TM.

This chapter does not replace the operations handbook in which the customer or the operations organization documents specific tasks, involved parties, and interaction procedures.

Convergent invoicing enablement for SAP TM is based on SAP ERP 6.0, enhancement package 5. Therefore, the operations information covered in the corresponding operations guides also applies to this software.

For more information, see the following resources on SAP Service Marketplace:

Resource Quick Link on SAP Service Marketplace

Documentation on maintaining an SAP ERP 6.0 landscape

http://service.sap.com/instguides

→ SAP Business Suite Applications → SAP ERP 6.0 → Operations

For a complete list of available Operations Guides, see http://service.sap.com/instguides.

The operations information specific to convergent invoicing enablement for SAP TM is described in the following chapters. The following areas are covered:

● Monitoring

● Error handling

5.1 Monitoring

5.1.1 Application Log

The application log records the results of billable item creation and cancellation. This includes error as well as success messages. You can monitor the application log in transaction SLG1 with the object key FKKBIX (Billing in Contract Accounts Receivable and Payable).

5.1.2 Interface Monitoring

Transaction sxi_monitor is the central tool for monitoring xml message exchange between SAP ECC and SAP TM. You can use this transaction to monitor whether the confirmation messages (processed xml messages) have been sent to the SAP TM system.



Configuration

Guide Customer



of 24

5.2 Error Handling The result of billable item creation and cancellation is shown in the application log (transaction SLG1). In case of an error, that is, if creation or cancellation fails, the SAP ECC system sends a confirmation message with status “rejected” to SAP TM (sender system). After correcting the error (for example, missing Customizing), the forwarding settlement document is sent again for processing.