1 Bakus

Sap Settlement Source Assignment Discovery


This content was created to clarify the customizing of settlement of internal orders.


 All the costs of an internal order can be allocated to one or more receivers, this can be done by individual orders (KO88) or collective group of orders (KO8G).
Reason: Analysis of costs for one job (Example: marketing campaign, production order), settlement serves to post the costs from the job to the responsible objects.
Statistical orders cannot be settled.

Settlement Customizing

To create a settlement rule you must define a settlement profile and assign it to the order type (KOT2). Each Internal order has an order type

Transaction KO03

Transaction KOT2 

In the settlement profile you define parameters such as receivers, valid receivers and default values. You can check the settlement profile in transaction OKO7.

Distribution Rules

To create the rules you can go to KO02, enter the order and then click on settlement rule. 

Each line of the distribution rule specifies the percentage, equivalence number or amount of the orders costs to be settled to a particular receiver.
You can't create a rule containing both an amount as well as an equivalence number or a percentage,
if you need to change or delete a rule you need to reverse all the settlements that used this rule.

There is two settlement types :

- PER : Settles the cost of the period specified
- FUL : Settles all the costs of the sender object until the period specified

Double-click on the line to check all the valid receivers, to maintain the valid receivers go to transaction OKO7.

You can use Valid-from period to limit the validity of a distribution rule.
After you save it the system status of the order will have SETC status.

Allocation Structure

The Allocation structure allows you to define which cost elements should be settled using a settlement cost element or the original cost element.

 - Settlement Assignment  

  - Source : You can specify a range of cost elements or a cost element group for a settlement assignment in transaction OKO6. If you execute a settlement and the sender object contains a cost element that is not on the source of any assignment you will receive error KD503 (Complete allocation structure).

  - Settlement Cost Element : Each settlement cost element must belong to one of the following categories:
    -> Internal settlement: Cost element category 21 (secondary).
    -> External settlement: Cost element category 22 (primary).

The Receiver category specifies the object type for the settlement receiver.

Flow Trace

To analyze a settlement you can use the tool Flow Trace. To active it go to KO88/KO8G, Extras -> Activate Flow trace.

This will show exactly what’s happening in the settlement :

- Settlement Profile
- Allocation Structure
- Distribution Rule
- Costs/revenues read-
- Distribute costs/revenues to the receivers 

 Main Tables

COBRA : Settlement Rule for Order Settlement
COBRB : Settlement Rules (especially ERSJA, ERSPE, LETJA, LETPE)
AUAK   : Settlement documents
              - AUAK Settlement document header
              - AUAV Settlement transactions
              - AUAA  Sender and receivers
              - AUAS   Settled costs

COSS, COSP, COSL, COSB : costs posted to the object
COEP : Lines items posted to the object
JEST, JCDS : System status and change documents

Related Content

Related Documents 

Internal Order Settlement
Automatic Generation of Settlement Rules
Checking Value Flows from Order/Project Settlement
Automatic Generation of Settlement Rules
Maintain Settlement Cost Elements

Related SAP Notes/KBA

SAP Note 173909  : info. Costs should not be settled
SAP Note 193586  : Analysis program for settlement (rka_settle_tables_compare)

  1. Reduce Revenue Loss Due To Stock-outs

    Real-time alerts based on current stock requirements with integrated decision support. Significantly improved ATP via fast mass product availability checks for sales, planned and production-orders (all items of an order at once, releasing large production orders). Enhance on-time delivery performance by integrating pick, pack, and ship processes.

  2. Reduce Days in Inventory

    Increase inventory turnover by making informed decisions based on accurate demand and supply data. Simplified data model resulting in increased throughput, flexible analytics at the most granular level and accuracy based on primary data.

  3. Reduce Inventory Carrying Cost

    Leverage mobile inventory management and warehouse applications via SAP Fiori apps

  4. Reduce Inventory Obsolescence

    Get the ability to automate warehouse operations with RFID and sensors with IoT framework for integration to manage just-in-time availability, unit handling, serial numbers, electronic data interchange, and proof of delivery.

  5. Enhance Supply Chain Planning Productivity

    Enable personalized views for Planners with relevant analytics

  6. Reduce Total Logistics Cost

    Leverage new planning algorithms - leveraging predictive analytics (e.g. demand sensing) algorithm in combination with optimization. Increase process flexibility through optimized logistics processes.

  7. Leave a Comment


    Your email address will not be published. Required fields are marked *