Mapping Freight Settlement to Materials Management

Objective

After completing this lesson, you will be able to post Freight Settlement Documents

Posting Freight Charges

This figure shows the process flow of Supplier Freight Processing.

As shown in the figure, the typical freight settlement process flow is as follows:

Based on a delivery, the planner carries out several planning steps and creates a freight order (FO) or a freight booking to calculate the charges and to subcontract to a carrier.

On settlement, the system creates a FSD. This document contains all relevant logistical data as well as the charges and other commercial data. The charges can be copied over from the freight order or freight booking (most common) or another charge calculation is triggered based on the freight agreement between the purchasing organization and the carrier. It is possible to manually change charges in the FSD. FSDs can be created online or in batch. It is possible to do a collective settlement (several freight orders or bookings are settled with one FSD). The FSD can then be posted to MM.

The FSD contains one or more charges sections that appear as PO items. In general, in the case of a stage level-based charge calculation, the PO has as many items as there are stages in the corresponding FO, and therefore more than one service entry sheets, one per PO item.

After posting, the purchase order and service entry sheet are created in MM. This constitutes the working list for invoice verification. You also have the option of self-billing.

The PO and SES can be accessed via the transaction ME23N or via the TM Document Flow.

Note

The purchase order and service entry sheet are only used for technical purposes to post accruals. The service entry sheet comprises a list of services performed by a vendor based on a purchase order, containing service descriptions and details of quantities and values. The descriptions of planned services deriving from the purchase order are used as default descriptions in the service entry sheet.

Purchase Order and Service Entry Sheet

This figure shows the PO and SES Creation.

Each service entry sheet is based on an external service order. Determining a valid purchase order is required for transfers to Financial Accounting and for settlements. You can also create the purchase order every month for the carrier. Important criteria for the service order include carrier, purchasing organization, purchasing group, plant, and item category.

When the system has automatically determined a valid purchase order, a service entry sheet is created that refers to the purchase order. During posting, you accept services and, in Financial Accounting, an accounting document for generating accruals is created.

During account assignment, the system automatically determines the correct G/L account in Financial Accounting for each cost item and the assignment for Controlling. Account assignment can be carried out at different levels, depending on the level of detail at which you want to track costs.

The transfer to Financial Accounting to establish accruals requires entering and accepting the services rendered. The system automatically creates a service entry sheet. Using the credit memo procedure, also referred to as the Evaluated Receipt Settlement (ERS) procedure, you can settle the freight costs with the carrier without having received invoices. You can choose from different settlement periods. You transfer the calculated freight costs to Financial Accounting. The invoices are verified by the carrier. If the carrier discovers variances, you can post these as subsequent debits or credits.

If you receive invoices from the carrier, you can also verify the invoices manually and create the invoices manually in logistics invoice verification.

Freight Settlement Posting Actions and Updates

This graphic shows FSD Posting Actions.

In an embedded SAP S/4HANA system landscape, the posting of the Freight Settlement Document is carried out via BgRFC (Background Remote Function Call).

There are various actions available that can be triggered directly on the FSD UI, the worklists or via background jobs:

  • Save and Post: Create PO and SES, post accruals
  • Cancel Document: Cancel posted Accruals, Cancel SES + PO (Lifecycle acruals posted)
  • Reverse Document: Create return SES for previously created PO (Carrier has to be ERS enabled)
  • Cancel PO: Cancel PO when SES creation failed for any reason, Posting must be started again after successful cancellation
  • Reprocess failed Document: Used when document creation failed, Used to continue the posting process

Post FSD Directly

This graphic shows FSD Posting Asynchronous.

Asynchronous means here, that in the backend a BgRFC unit is created, but will be executed later. At any point in time, the lifecycle status indicates the current stage of the FSD in the business process. The asynchronous job leads immediately to the following statuses:

  1. Lifecycle Status = posting started
  2. Confirmation Status = not confirmed

These statuses are updated when the BgRFC unit is executed. In addition, the user gets messages about the triggered action.

In customizing, choose Transportation ManagementBasic FunctionsUser InterfaceDefine Message Settings.

After execution of the BgRFC unit, a Refresh leads to the updated statuses:

  1. Lifecycle Status = Accruals posted
  2. Confirmation Status = confirmed

Post FSD via batch job

This image show FSD Posting Synchronous.

To post a FSD via a batch job, in the backend transaction SE38, you can set up the batch jobs:

  • /SCMTMS/SFIR_CREATE_BATCH to create an FSD with the option to "Post Immediately"
  • /SCMTMS/SFIR_TRANSFER_BATCH to post existing FSDs for accruals or to reprocess failed postings

These reports process the posting and reprocessing of FSD in a synchronous mode.

Check Results of Posting Action

After Posting, you can track and check the results if there are posting failures.

You can check in the FSD tab "Application Log" for errors or warnings.

This image shows the FSD Application Log.

In case that MM configuration is missing, this cannot be alerted upfront, but will be shown in the Application log. Example: G/L account does not match (MM configuration).

In the Application log, the Error messages are listed, and in the long text you get a procedure how to solve the issue.

After completing the missing customizing, the actions "Cancel PO" (only via UI or worklist) or "Reprocess failed documents" (only via Batch report) can be triggered. After PO cancellation, the posting action must be triggered again.

To reprocess failed documents, you must use the /SCMTMS/SFIR_TRANSFER_BATCH. This is done when, for example, the SES creation or cancellation failed due to missing MM customizing. Even for a failed reversal action, the batch report can be used.

You can also monitor the processing of the BGRFC units that will be created when an asynchronous job is triggered. This can be done via backend transaction code SBGRFCMON.

This image shows the BGRFC Monitor.

After posting, if FSD confirmation is not received for more than 2 min, go to the BGRFC Monitor and enter the data as shown in the screenshot.

After Executing, you are able to see the background processes.

  • If the background process is still processing, then you will see the status as "Unit Blocked/Locked"
  • If the background process failed due to some runtime error, then you will see the status as "Unit has errors"

Select the respective entry and click on the details button to see more information.

Note

If you are in a TM side-by-side scenario, TM and the SAP S/4HANA ERP system are connected via SAP Process Integration or Web Services.

In this case you will have to use the backend transaction SXMB_MONI (XML Monitor) to check the FSD integration for errors and to restart the respective service messages for transferring the document after the customizing has been corrected.

Automatic Change Management for Freight Settlements

There can be late changes in the freight order requiring changes to logistical data, which may result in the change in the charges (increase or decrease). These changes can occur at time when the old values are already transferred to settlement documents and / or the settlement documents have also been transferred to financials.

Accruals are posted when the financial liability is known (example: departure or confirmed pickup of the freight by the carrier). However, there can be mid execution changes (example: diversions (consignee changes), loss of cargo (in transit), unavailability of cargo, unplanned costs due to detention, demurrages, loading and unloading activities, tolls, and so on).

These changes may only be known after execution or during the invoicing process (when the carrier sends the invoice).

The system uses the automatic change management process that you specify in the relevant settlement profile. In customizing, go toTransportation ManagementSettlementDefine Settlement ProfileChange Process FSD.

TM uses the following elements to determine what approach to take with the change:

  • Change Process FSD setting in the settlement profile

  • Life cycle status of the freight settlement document

There are two different FSD Update Strategies/ Change Processes available:

This figure shows FSD Update Strategies.

When an order is changed and the invoicing status changes to Over Invoiced, the system automatically applies the reverse and repost strategy.

For applying the automatic change process, you use the background function "Creation of Freight Settlement Documents" (program: /SCMTMS/SFIR_CREATE_BATCH) to create, change, and transfer the freight settlement documents to Materials Management (MM). The freight settlement document contains the changes from the freight order.

Alternatively, you go to the impacted freight document from the personal worklist or the individual document, and you create the freight settlement document or apply changes to the charges directly on the UI in a manual way. This would trigger the relevant change process that is defined in the settlement profile, too.

Configure Freight Settlement Creation in TM

This image show FSD Creation Customizing Settings.

When the FSD creation is triggered for a freight order/freight booking (FO/FB), the corresponding document type is used to determine the FSD type used.

The purchasing organization specified in the FO/FB is used to determine the settlement profile. The system takes care of the relevant charges for the FO/FB. All of this information is then used to create FSDs for the selected FO/FB.

In SAP TM, there are some customizing steps that must be performed when configuring freight settlement:

  1. Define Settlement Profiles
  2. Assign Settlement Profile to Charges Profile and Org Unit
  3. Define Number Range Intervals for FSDs
  4. Define FSD Types
  5. Assign FSD Type to FO/FB Type

Step 1: Define Settlement Profiles

The first stage in our configuration is to define a settlement profile.

The settlement profile consists of a set of parameters with which you can control how the system creates settlement documents.

In the Define Settlement Profile customizing activity, you can define the profile for creating settlement documents.

You can specify the following activities:

  • Profile category to determine whether the system can use the profile to create freight settlements, forwarding settlements, or both freight settlements and forwarding settlements
  • Data source to determine the type of data that the system uses when creating a settlement document. You can specify planned and confirmed data from forwarding orders or planned data from freight orders
  • Split/consolidation strategy profile to split or consolidate settlement documents
  • Collective invoice to create one invoice for several orders
  • Stage split to create invoices for individual stages in a freight order or forwarding order
  • FSD Change Process for determining the FSD update strategy in the case of late changes

To define settlement profiles, in customizing, choose Transportation ManagementSettlementDefine Settlement Profile.

Step 2: Assign Settlement Profile to Charges Profile and Org Unit

The second step in our configuration is to assign the settlement profile to the charges profile.

In customizing, choose Transportation ManagementBasic FunctionsCharge CalculationBasic SettingsDefine Charges Profiles.

The assignment makes it possible to control different settlement creation settings for different organizations. It is also possible to determine the settlement profile at runtime using the BRF+ condition of type /SCMTMS/TCM_FCP_DET. For the assignment of a charges profile to the purchasing organization, see the PPOCE transaction.

Step 3: Define Number Range Intervals for FSDs

In the third step of our configuration, number range intervals are defined for the FSD.

When an FSD is created, a unique number is assigned to it, identifying the document. The number comes from the number range, which is provided for the document type.

You define number range intervals in the Define Number Range Intervals for Freight SDs customizing activity.

In customizing, choose Transportation ManagementSettlementFreight SettlementDefine Number Range Intervals for Freight SDs.

Step 4: Define Freight Settlement Document Types

You can use the freight settlement types to specify certain parameters for certain types of FSDs.

To define freight settlement document types, in customizing, choose Transportation ManagementSettlementFreight SettlementDefine Freight Settlement Document Types.

You can specify the following parameters:

  • Business partner determination profile to assign business partners to the freight settlement document.
  • Number range interval of FSDs.
  • FSD categories (to define either a freight settlement document or charge correction advice).
  • Separate categories are available to define a freight settlement document and a charge correction advice document.
  • Tracking of changes.
  • BW relevance.
  • Enable Cost Distribution.
  • Default UoMs.
  • Residence period for archiving.
  • Output profile for printing and transferring (by default, this is set to /SCMTMS/TOR_INV_PREP).
  • Default view for the charges tab.

Step 5: Assign FSD Type to FO/FB Types

The final step in our configuration is the assignment of the FSD type to freight order and freight booking types.

You can assign the FSD type to one or several freight order types in the Define Freight Order Types customizing activity.

In customizing, choose Transportation ManagementFreight Order ManagementFreight OrderDefine Freight Order Types.

You can assign the FSD type to one or several freight booking types in the Define Freight Booking Types customizing activity.

In customizing, choose Transportation ManagementFreight Order ManagementFreight BookingDefine Freight Booking Types.

Note

Both the freight order and freight booking types have to be enabled for settlement by checking the respective box during FSD Type assignment.

Configure Freight Settlement Integration to MM

This graphic shows FSD Posting Customizing.

When the FSD is posted to MM, the accruals are posted and a PO and a service entry sheet (SES) per PO line item are created. The SES serves as the basis for invoice verification.

In SAP TM and SAP MM, there are several customizing steps that must be performed when configuring freight settlement integration:

  1. Map Purchasing Organization
  2. Map FSD Type to PO Type and Plant
  3. Map Transportation Charge Types to MM Service Master
  4. Configure Automatic Determination of G/L Account
  5. Enable User for Invoice Verification

Step 1: Map Purchasing Organization

TM documents contain different information than MM documents. The TM organizational structure is different to the MM organizational structure. Therefore, the organizational units must be mapped when a MM document (PO) is created out of a TM document (FSD).

To find the Purchasing Organization in MM, in customizing, choose Enterprise StructureDefinitionMaterials ManagementMaintain purchasing organization.

Maintain the MM Purchasing Organization/group in the corresponding TM Purchasing Organizational Unit:

In the backend, go to transaction PPOME and choose your TM Purchasing Organization.

In the tab Org. Data, field BSG Org. Unit, enter the MM Purchasing Organization.

Note

In a SAP S/4HANA TM to SAP S/4HANA side-by-side deployment, the previous settings have to be applied. In a SAP S/4HANA TM to SAP ERP side-by-side deployment, the organizational unit mapping requires a slightly different set-up. Here you have to assign the TM purchasing organization to the MM purchasing organization directly in the ERP customizing:

In the customizing settings Mapping of Organizational Units, activity Assign Organizational Units for Purchasing, you assign the TM purchase organization, TM purchase group, and freight settlement document type to the MM organizational data.

In ERP, choose Integration with Other SAP Components → Transportation Management → Invoice Integration → Invoicing → Mapping of Organizational Units → Assign Organizational Units for Purchasing.

Step 2: Map FSD Type to PO Type and Plant

For each FSD type the following must be defined:

  • Purchase Order Type
  • Material Group
  • Plant
  • Purchasing Group

This mapping enables the system to find the right PO type, assigned to the responsible plant and material group to take up the settled charges and create the respective FI and material documents.

In customizing, choose Transportation ManagementSettlementFreight SettlementIntegration for Settlement PostingAssign Purchasing Information for Posting.

Step 3: Map Transportation Charge Types to MM Service Master

It is crucial to assign the transportation charge item categories, transportation charge item subcategories, and transportation charge types to MM service master records, also called activity numbers, and account assignment categories.

The account assignment category, set to "K" for the cost center, specifies which account assignment data is necessary for an item. The cost center serves as an organizational unit within a controlling area that represents a defined location of cost incurrence.

The MM Service Master Record/ Activity number represents the purchased service based on the TM Charge Type. The services are depicted in the PO Item section. In transaction AC01 the activity numbers can be set-up. Here, they are also linked to a valuation class, which enables the system to find the respective G/L accounts that are updated when services are entered.

In customizing, choose Transportation ManagementSettlementFreight SettlementIntegration for Settlement PostingAssign Service Master Record and Account Assignment Category.

Note

In a SAP S/4HANA TM to SAP ERP side-by-side deployment, at first you have to set-up the TM Charge Types, Categories, and Subcategories in the ERP system. After you have done that, you can map the Charge Types to MM Service Masters.

In SAP ERP, in customizing choose Integration with Other SAP Components → Transportation Management → Invoice Integration → Invoicing → Definition of Transportation Charges → Define Charge Type.

Step 4: Configure Automatic Determination of G/L Account

During settlement cost processing, the system can determine G/L accounts for the transportation costs automatically. This process uses the settings that you configure in the following Customizing activity to find the correct G/L accounts:

In customizing, choose Materials ManagementValuation and Account AssignmentAccount DeterminationAccount Determination without wizardConfigure Automatic Postings.

Here, you define the determination of for example, the GR/IR clearing account, which takes up the accruals for the transportation charges and is balanced when the carrier invoice is received and verified. Furthermore, you set-up the determination of material Inventory and consumption accounts as well as freight clearing accounts.

Note

This activity is performed in close corporation with the financial department of customers and demands close alignments. A further prerequisite is the complete set-up of the respective MM and FI/CO basic settings (for example, PO types, posting periods, valuation classes, movement types, and so on).

Step 5: Enable User for Invoice Verification

To enable invoice verification, set up the user parameter TM_INVOICE_CLERK in the user data. With the user parameter TM_INVOICE_CLERK, you control which tabs the user sees when entering or changing incoming invoices in the transactions MIRO and MIR7, in change mode in the transaction MIR4, and in GR/IR clearing account maintenance in the transaction MR11.

In logistics invoice verification (MIRO), the user is now able to see the TM Ref. Tab. Here, you can enter for example, the freight order ID or the carrier ID to bring up the freight settlement transportation charges for comparing them with the carrier invoice.

In transaction SU01 or SU3, enter the respective user name and maintain the parameter ID in the tab Parameters plus parameter value X.