SAP BOX

'26/11/19 UPDATE

CO / FIELD NOTES

You ran a cost center allocation. Why can't the receiver see the salary and rent accounts?

Assessment moves secondary costs too, on a category 42 account; distribution moves primary costs only, on the original accounts. Using fictional cost centers, this note works out how the receiver report differs, why a balance can stay on the sender, and how repeating a run differs between KSU5 and Run Allocations, based on the S/4HANA 2025 documents.

If a receiver asks why the salary and rent figures have vanished after a cost center allocation, or a distribution leaves a balance on the sender, check which method ran before you hunt for an error. Assessment and distribution move costs on different accounts, and they move different amounts. After this note you will be able to tell from the receiver's line items which one was posted, and decide where to look first when a balance stays behind.

The basis is the SAP Help Portal documentation for SAP S/4HANA 2025 FPS02 and public SAP Learning courses. The cost centers, accounts and amounts are invented. Nothing here was run on an SAP system; the rules are applied to fictional numbers by hand. A note on terms: SAP Learning says the type now called Overhead Allocation was called Assessment in ERP, and Help lists Overhead Allocation as a type in the Manage Allocations app. This note says assessment throughout, and screens follow your logon language.

Same amount, different receiver report

Here is a fictional case. In October, sending cost center 9100 (facilities) holds primary costs of KRW 6,000,000 on salary account 610000 and KRW 3,000,000 on rent account 620000, plus KRW 600,000 of secondary cost received through internal activity allocation. That makes KRW 9,600,000. The receivers are cost centers 4100 and 4200, and the split follows a statistical key figure, headcount of 20 and 10, so 2:1. Assume the segment's account range covers all three amounts, the sender rule is posted amounts, and the sender share is 100%.

A distribution moves only the primary costs, on their original accounts. Cost center 4100 receives KRW 4,000,000 of salaries and KRW 2,000,000 of rent; 4200 receives KRW 2,000,000 of salaries and KRW 1,000,000 of rent. The total moved is KRW 9,000,000, and the KRW 600,000 of secondary cost stays on 9100.

An assessment moves the whole KRW 9,600,000, secondary cost included, on one assessment account of cost element category 42 (fictional number 942000). Cost center 4100 receives KRW 6,400,000, 4200 receives KRW 3,200,000, and 9100 is left with KRW 0.

Three-card comparison. Before the run, sender 9100 holds primary costs of KRW 6,000,000 salaries and KRW 3,000,000 rent, and secondary cost of KRW 600,000. Distribution sends 4100 salaries 4,000,000 and rent 2,000,000, sends 4200 salaries 2,000,000 and rent 1,000,000, and leaves secondary 600,000 on 9100. Assessment sends 4100 6,400,000 and 4200 3,200,000 on account 942000 and leaves 0 on 9100.
Compare 'left on 9100' in the middle card with the single line in the bottom card. Distribution keeps the accounts but leaves KRW 600,000 of secondary cost behind; assessment moves everything but merges it onto one account. The 2:1 splits match the calculation in the text.

So the line item report of receiver 4100 (KSB1) can tell them apart. If 4100 has no other postings, as in this example, original account lines totalling KRW 6,000,000 read as a distribution, and KRW 6,400,000 on a category 42 account reads as an assessment. A real receiver may also hold its own salary postings on the same account, so don't stop at the account number: check that the line's CO document names sender 9100. Several senders, or an allocation structure (described below), can produce several assessment account lines, so the category of the account is a safer sign than the number of lines. An account's category is shown on the Control Data tab of its G/L account master.

Example SAP GUI KSB1 screen. Cost center 4100, October 2026. If distribution was posted there are two lines: 610000 salaries KRW 4,000,000 and 620000 rent KRW 2,000,000. If assessment was posted there is one line: 942000 at KRW 6,400,000. Marker 1 is on the distribution salary line and marker 2 on the assessment line.
How the line item report of receiver 4100 differs between the two cases. In this example, original account lines mean distribution and a category 42 line means assessment. Values are invented, and in this fictional case only one of the two would be posted, so they sit on one screen purely for comparison. Column names are shortened to fit.

Category 42 is why the accounts are missing

In SAP Learning's account of assessment, neither the credit to the sender nor the debit to the receiver uses the original accounts. Both go through a secondary account of category 42, so the receiver has no record of what the cost was made of. What disappears is the composition; who sent it remains visible as sender and receiver information in the CO document. SAP's own example of a good fit is cafeteria cost, where the breakdown does not matter to the receiver.

Distribution is the reverse. It suits a receiver that needs to see the composition, and SAP Learning's example is a service cost center sending to production cost centers. There is a middle path too. An allocation structure on an assessment segment assigns different assessment accounts to original accounts or account groups, so the receiver can keep a summarized breakdown, such as one group for salaries and one for rent.

Quantities differ as well. The Help documents say consumption quantities cannot be moved by assessment, while the Consumption setting in the cycle header can be used for distribution and periodic reposting. If activity quantities have to move, the same documents point to indirect activity allocation.

If a balance stays on the sender

Secondary cost left behind by a distribution, like the KRW 600,000 above, is expected. SAP Learning says distribution works only for accounts of type primary costs and that secondary costs remain on the sender. The Allocation Contexts table in the Manage Allocations documents agrees: it lists posting categories 01, 03, 04 and 22 for distribution and 42 for assessment. Help's list of cost element categories also counts 03, 04 and 22 as primary, so 'primary' here covers accrual categories 03 and 04 and external settlement category 22 as well.

If the balance is not secondary cost, look at the settings. A segment defines which accounts send which values, so first check that the account is in its sender range and whether the sender rule is a fixed amount or fixed rate rather than posted amounts. A sender share below 100% on the segment leaves the rest on the sender, and so do fixed receiver percentages that total less than 100%. SAP Learning gives the example of leaving behind the cafeteria staff's own use of the cafeteria. Finally, check statistical postings. According to the Manage Allocations documents, the Posted Amounts sender rule takes the balance from real postings to the cost center. Cases such as a posting whose original object is a WBS element, with only a statistical record on the cost center, are left out. If a cost center report and the allocated amount disagree, this is one thing to suspect.

Four-card checklist. First, secondary costs do not move in distribution. Second, a sender share below 100% may leave the rest on purpose. Third, fixed receiver percentages below 100% leave the shortfall behind. Fourth, Posted Amounts in Manage Allocations counts real postings only.
The checking order, read from top to bottom. The KRW 600,000 in the example above belongs to the top card. The order is this note's arrangement of what the documents say. Check the segment's account range and sender rule too, as the text says.

If you want the receivers to see accounts and the sender to end at zero, you could consider following a distribution cycle with an assessment cycle for the remaining secondary cost. That is this note's own reading, combining what each method is documented to allow. No public document recommending the combination turned up. SAP Learning does say that a cycle using an earlier cycle's results has to run in the right order, so the distribution would go first.

Running it again, and which tool applies

The normal path starts with a test. On the KSU5 (assessment) or KSV5 (distribution) initial screen you enter the period, the fiscal year and the cycle, which is identified by its name and start date. Test run is the default, and with it on you can see the lists while the database stays unchanged. The posting date of an assessment or distribution of actual data is always the last day of the calendar month.

Example SAP GUI KSU5 initial screen. Period 10 to 10, fiscal year 2026. Background processing is off and Test run is on. The cycle table has one row: ZFAC10, start date 1 January 2026. Marker 1 is on Test run and marker 2 on the cycle row.
Example KSU5 initial screen. Look first at the Test run box and the cycle's start date. The Reverse function mentioned in the text sits under the Assessment menu. The cycle name and values are invented, and the layout is a shortened drawing that follows the Help procedure.

Repeating a run depends on the tool. According to Help, repeating periodic reposting, distribution or assessment within a period reverses and overwrites the line items. You can also cancel with Reverse under the Assessment menu. The Run Allocations app, one of the Universal Allocation apps, works differently. A live run happens once per fiscal period, and if you want another, a reversal run for that same data set in the Allocation Results app must come first. Test runs can be repeated as often as you like, even for locked periods, and create no journal entries.

If the basis for a period already closed was wrong, there is segment reversal and rebooking, which SAP Learning describes as done in KSU5 or KSV5. It takes back the segment results of the past period and posts again in the current period with corrected values, so the current period has to be open. It works per segment and does not cover iterative relationships for you, so iterative segments should be reversed together to avoid inconsistencies.

Three-card table. In KSU5 and KSV5, a repeat in the same period reverses and overwrites the line items, and Reverse in the menu cancels a run. In Run Allocations, a live run happens once per fiscal period, a redo needs a reversal run on the same data set in Allocation Results first, and test runs are unlimited and create no journal entries. A past period is fixed with segment reversal and rebooking in KSU5 or KSV5, which works per segment so iterative segments are handled together, and the current period must not be closed.
Note 'once' in the second card. As the text says, unlike the overwrite in KSU5, Run Allocations needs a reversal run before another live run.

Which tool applies also depends on the object. SAP Learning says the Manage Allocations app cannot be used for internal orders, so if an order is the receiver, look at KSU5 and KSV5. An app for moving KSU5 and KSV5 cycles to the new apps (Monitor Cycle Migration, F8715) and a job template are also documented. The posting rules in this note follow the 2025 FPS02 Help documents and the SAP Learning pages, which carry no version number, and whether earlier releases behave the same was not checked release by release.

SAP's criterion for choosing is whether the composition matters to the receiver. One check is worth adding: before you choose distribution, see whether the sender holds secondary cost. If it does, distribution alone will not move that amount off the sender.

THE END
RSS feedBack to the library
COMMENTS BOX

Add your perspective.

Share a question, another approach, or something you have tried.

Newest first

Checking sign-in…

Loading comments…