- Home
- Modules
- Controlling
- Assessments
Assessment, distribution and periodic reposting in SAP CO
The classic allocations of SAP Cost Center Accounting: how the costs of IT, HR or the canteen reach the departments that use them, explained from the business side and from the technical side.
Part 1 of 2: SAP ECC. Part 2 covers SAP S/4HANA.
4100430000 Salaries48,000.00466000 Licences21,000.00481000 Depreciation9,000.00943000 Building (sec.)6,000.00Total84,000.00Next: KSU5IT-OCT · headcountRKIU33,600.00Filling · 30%25,200.00Logistics · 20%16,800.00Sales · 10%8,400.00941000 IT assessment84,000.00Overview
What allocations are, if you have never run one
Some departments exist to serve the rest of the company. IT keeps the PCs running, HR hires and pays, the canteen feeds everybody, facilities heat the building. Their costs are posted where they arise: on the IT, HR or canteen cost center. Until those costs reach the departments that use the services, brewing looks cheaper than it is and IT looks like a cost nobody asked for.
SAP Cost Center Accounting solves this at month end with periodic allocations. A cycle reads the costs of a sender cost center and spreads them to receivers in proportion to a key, such as headcount, PCs or square metres. SAP ECC offers three ways to do it, and they differ in which costs they move and under which cost element the receiver sees them: distribution, assessment and periodic reposting.
- SAP R/3
- SAP ECC 6
- SAP S/4HANA, classic transactions
KSV5KSU5KSW5Use the Business | Technical switch at the top of the page to change the explanations between the business view and the technical one: cost elements, business transactions, rules, tables and messages.
Five questions every cycle answers
Whichever method you pick, an allocation cycle is these five answers. The fifth one is the method.
- 01Who sends?A cost center, and the cost elements to take from it.
- 02Who receives?Cost centers, orders, WBS elements or cost objects.
- 03How much?The sender rule: posted amounts, fixed amounts or fixed rates, and a share in %.
- 04In what proportion?The receiver rule: variable portions such as a key figure, or fixed amounts, percentages or portions.
- 05Under which cost element?The original one in distribution and reposting, an assessment cost element in assessment.
- Distribution · KSV5
Keeps the name of the cost
Debit and credit are posted under the original cost element. In SAP’s own example, utility costs on three accounts are split equally across EDP, Sales and Marketing, and each receiver is charged EUR 500 under the original accounts.
Source: SAP Help, allocation types - Assessment · KSU5
Bundles everything under one secondary cost element
Primary and secondary costs move under an assessment cost element of category 42. The receiver sees one line; SAP calls this useful when the composition of the costs is unimportant for the receiver, the classic case being the cafeteria.
Source: SAP Help, assessment - Periodic reposting · KSW5
A correction aid, not an internal charge
Telephone, postage or insurance are posted in FI to one allocation cost center and reposted at period end to the cost centers that caused them, under the original cost element. Same result as a manual reposting, stored with less data than a distribution.
Source: SAP Help, periodic reposting
This page uses one example
October IT costs of 84,000.00 on cost center 4100 IT Services
Company code 1010, the same brewery as the other pages on this site. IT’s October costs are 48,000.00 of salaries, 21,000.00 of software licences and 9,000.00 of hardware depreciation, all primary, plus 6,000.00 of building costs that facilities assessed to IT earlier in the close, a secondary cost. The receivers are Brewing 4210, Filling 4220, Logistics 4300 and Sales 4400. Accounts, cost centers and numbers are examples only.
Who takes part
- FIPosts the costsInvoices, payroll and depreciation, each with the cost center that pays.
- HR · FacilitiesSupply the keysHeadcount, square metres, PCs: entered as statistical key figures.
- Cost centersSend and receiveIT is a sender; Brewing, Filling, Logistics and Sales receive.
- ControllingOwns the cyclesBuilds the cycles, runs them at month end, checks and reverses.
- ManagementReads full costsDepartment and product costs that include the services they use.
Why allocate
Why companies allocate costs, and what they get from it
Allocation is older than SAP. Cost accounting has always assigned shared costs to the departments, products or customers that use them; AccountingTools defines it as identifying, aggregating and assigning costs to cost objects. SAP turns it into a monthly routine that runs in minutes, can be tested first and can be reversed.
- 01
Full cost of every department
A brewing cost center that carries its share of IT, HR and facilities shows what brewing really costs. And the full cost flows on: SAP’s closing list assesses primary and secondary costs before it calculates activity prices from actual costs.
Source: SAP Help, period-end closing in Overhead Cost Controlling - 02
Cost visibility and accountability
Receivers see what the services they use cost them; senders are measured on what they deliver. AccountingTools lists improved cost visibility first among the benefits of allocation.
Source: AccountingTools, cost allocation methods - 03
Better decisions
Pricing, budgets and make-or-buy decisions rest on the real cost of a product or department, overhead included. The Corporate Finance Institute puts decision support first among the reasons to allocate.
Source: Corporate Finance Institute, cost allocation - 04
Fewer postings in FI
Collecting telephone, postage or insurance on one allocation cost center saves an account assignment per invoice line. SAP says so explicitly: cost collection reduces the account assignments needed in FI.
Source: SAP Help, periodic reposting - 05
Plan and actual with the same logic
Actual and plan data can both be allocated, with separate cycles. A receiver’s budget can then already include its share of IT, and the plan/actual comparison compares like with like.
Source: SAP Help, allocation types - 06
Profitability down the line
Near the end of the close, SAP’s list assesses the under- or overabsorption of cost centers to profitability analysis, so the margins also carry the overhead nobody absorbed.
Source: SAP Help, period-end closing in Overhead Cost Controlling
What SAP adds on top
- Define once, run every month. Keys and sender/receiver relationships are usually defined only once. (SAP Help, periodic allocations)
- Test before posting. Test run is the default on the execution screen. (SAP Help, executing periodic repostings or allocations)
- Reverse and repeat. Periodic allocations can be reversed and repeated as often as needed. (SAP Learning, periodic debit postings)
- A trail in every document. Sender and receiver are recorded in the CO document. (SAP Help, assessment)
- Smoothing when the law asks for it. Cumulative processing spreads allocations over the year. (SAP Help, cumulative processing of allocation cycles)
Worth knowing
Allocations change behaviour
AccountingTools warns that a key based on headcount may push department managers to reduce headcount or to outsource functions, and that allocations used improperly can lead to incorrect management decisions. The key is a management decision, not a technical setting: agree it with the people who will receive the costs.
Source: AccountingTools, cost allocationThe three methods
Distribution, assessment and periodic reposting, one by one
Pick a method. The business view explains what it is for and what managers see; the technical view shows what SAP posts, under which cost element and business transaction, and where its limits are. On the right, what the Brewing cost center sees after the same IT costs went through it.
Distribution
German: VerteilungKSV5RKIVPasses shared primary costs on to the departments that use them, and every receiver still sees what kind of cost it was.
Business view
Splitting costs that one cost center collects for several others: energy, utilities, rent. SAP Learning describes primary postings such as energy costs collected on a cost center and allocated at period end by a user-defined key.
The same cost elements as the sender. Brewing gets salaries, licences and depreciation as separate lines, so its manager can tell people costs from software costs.
Credits on the same cost elements, receiver by receiver: IT can show who received how much of each cost.
Only primary costs move. What IT itself received from other allocations, here 6,000.00 of building costs, stays on IT.
Technical view
Primary cost elements only; secondary cost elements stay on the sender. SAP KBA 3698978 confirms that KSV5 does not pick up postings that came from an assessment.
Debit and credit under the original cost element, with sender and receiver documented in the CO document. Business transaction RKIV, Actual Overhead Distribution; RKPV in plan.
Cost centers send, and business processes in Activity-Based Costing. Cost centers, orders, WBS elements and cost objects can receive. Orders and WBS elements as senders need report RKALPSAC.
Primary costs planned as activity-dependent are not considered. Line items are written for each sender and receiver, and that cannot be restricted, so with every cost element kept, distribution writes the most records.
What Brewing 4210 sees, by headcount
| Cost element | Text | Amount | Sender in totals |
|---|---|---|---|
| 430000 | Salaries | 19,200.00 | 4100 |
| 466000 | Software licences | 8,400.00 | 4100 |
| 481000 | Hardware depreciation | 3,600.00 | 4100 |
| Total from IT | 31,200.00 |
Three cost elements from IT, each traceable to 4100 in the totals. The 6,000.00 of building costs never left IT.
ActualKSV1KSV2KSV3KSV4KSV5KSV6
PlanKSV7KSV8KSV9KSVAKSVBKSVC
Use it when
- Receivers need the cost element detail, as with energy or rent
- The sender holds only primary costs
- You want sender–receiver pairs in the reports
Think twice when
- The sender carries secondary costs that must move too
- Data volume matters more than detail
Sources: SAP Help, distribution, allocation types and defining periodic allocations; SAP Learning, performing period-end closing; SAP Help, CO business transactions; SAP KBAs 3698978 and 3731653.
Assessment
German: UmlageKSU5RKIUCharges the whole cost of a service cost center, primary and secondary, to its internal customers under one assessment cost element.
Business view
Internal service departments that charge their customers: canteen, IT, HR, facilities. SAP’s classic example is the cafeteria, allocated by the number of employees of each cost center.
One line, 941000 IT assessment, like an internal invoice. SAP calls assessment useful when the composition of the costs is unimportant for the receiver.
Its original costs stay visible, and a credit per receiver on the assessment cost element brings it to zero.
Everything moves, including the 6,000.00 of building costs IT received. Costs can cascade from service to service and down to production.
Technical view
Primary and secondary costs, assigned cumulatively or in groups to assessment cost elements of category 42. The original cost elements are not recorded on the receivers.
The sender is credited and the receivers debited with the assessment cost element; sender and receiver are in the CO document. Business transaction RKIU, Actual Overhead Assessment; RKPU in plan.
Instead of one assessment cost element per segment, an allocation structure maps cost elements, groups or intervals to several assessment cost elements, which cuts the number of segments.
No consumption quantities: activity quantities go through indirect activity allocation. In actual data, activity-dependent costs are allocated automatically.
What Brewing 4210 sees, by headcount
| Cost element | Text | Amount | Sender in totals |
|---|---|---|---|
| 941000 | IT assessment | 33,600.00 | 4100 |
| Total from IT | 33,600.00 |
One line instead of three. The receiver knows it came from IT, not what IT spent it on.
ActualKSU1KSU2KSU3KSU4KSU5KSU6
PlanKSU7KSU8KSU9KSUAKSUBKSUC
Use it when
- The receiver needs the amount, not its composition
- The sender carries secondary costs
- You want fewer data records
Think twice when
- Receivers must analyse salaries against licences
- Then use distribution, or an allocation structure
Sources: SAP Help, assessment, allocation types and defining periodic allocations; SAP Learning, performing period-end closing; SAP Help, CO business transactions; SAP Community, assessment vs distribution.
Periodic reposting
German: Periodische UmbuchungKSW5RKIBA month-end correction: costs parked on a collecting cost center move to the cost centers that caused them, as if they had been posted there from the start.
Business view
Telephone, postage, insurance: one invoice is posted in FI to an allocation cost center used only to collect costs, and reposted at period end by a key.
The original cost element, as if accounts payable had posted it there. SAP notes that the allocation cost center is of no importance to the receivers.
Accounts payable posts one line instead of one per cost center: cost collection reduces the number of account assignments when entering data in FI.
Reports based on totals do not show where the costs came from. Only the line items do.
Technical view
Primary costs, with the original primary cost element retained. Same result as a transaction-based reposting such as KB11N, but with a one-time effect on actual costs at period end.
Business transaction RKIB, Actual Periodic Reposting; RKPB in plan. The sender is not updated in the totals records, so the data uses less memory than a distribution and the origin can only be analysed from the line items.
Adjusts postings on cost centers, business processes, internal orders and WBS elements. The internal orders menu has its own cycles, KOW1 to KOW4.
SAP lists periodic reposting of costs from allocation cost centers as the second closing task, right after the transfer of statistical key figures and before distribution.
What Brewing 4210 sees, by headcount
| Cost element | Text | Amount | Sender in totals |
|---|---|---|---|
| 430000 | Salaries | 19,200.00 | — |
| 466000 | Software licences | 8,400.00 | — |
| 481000 | Hardware depreciation | 3,600.00 | — |
| Total from IT | 31,200.00 |
The same amounts as a distribution, but the totals do not name 4100. Brewing’s manager sees costs that look like its own postings.
ActualKSW1KSW2KSW3KSW4KSW5KSW6
PlanKSW7KSW8KSW9KSWAKSWBKSWC
Use it when
- The sender is only a clearing point
- Nobody needs the flow between cost centers in reports
- You want the leanest data
Think twice when
- Managers need to see who charged them
- The sender has secondary costs to pass on
Sources: SAP Help, periodic reposting and period-end closing; SAP Help, CO business transactions; SAP Learning, periodic debit postings; sapstack, KSW5 and KOW1.
Transactions
The transactions of each method
All three follow the same pattern: create, change, display and delete the cycle, execute it, look at the runs. Plan data needs its own cycles, with their own codes. A memory aid: SAP’s German texts call assessment Umlage and distribution Verteilung, hence KSU and KSV, RKIU and RKIV.
| Method | Create cycle | Change | Display | Delete | Execute | Overview |
|---|---|---|---|---|---|---|
DistributionGerman: VerteilungRKIV · Actual Overhead Distribution | KSV1 | KSV2 | KSV3 | KSV4 | KSV5 | KSV6 |
AssessmentGerman: UmlageRKIU · Actual Overhead Assessment | KSU1 | KSU2 | KSU3 | KSU4 | KSU5 | KSU6 |
Periodic repostingGerman: periodische UmbuchungRKIB · Actual Periodic Reposting | KSW1 | KSW2 | KSW3 | KSW4 | KSW5 | KSW6 |
| Method | Create cycle | Change | Display | Delete | Execute | Overview |
|---|---|---|---|---|---|---|
DistributionGerman: VerteilungRKPV · Plan Overhead Cost Distribution | KSV7 | KSV8 | KSV9 | KSVA | KSVB | KSVC |
AssessmentGerman: UmlageRKPU · Plan Overhead Cost Assessment | KSU7 | KSU8 | KSU9 | KSUA | KSUB | KSUC |
Periodic repostingGerman: periodische UmbuchungRKPB · Plan Periodic Reposting | KSW7 | KSW8 | KSW9 | KSWA | KSWB | KSWC |
Execute with Test run first: it is the default. Codes ending in N, such as KSU1N or KSV6N, are newer variants of the same functions, and SAP Fiori offers KSU5 and KSV5 as HTML apps, Execute Actual Assessment and Execute Actual Distribution Cycle. The searchable list of every code is further down, under Reference.
Plan data needs its own cycles: SAP requires a separate cycle for plan and for actual allocation of the same type. Plan allocations post on the first day of the month, actual ones on the last.
The same pattern in other components
The cycle-and-segment technique is shared, so the codes look alike well beyond Cost Center Accounting.
KEU1KEU5
Assessment to CO-PA
Cost center costs to profitability segments, credited on the sender with an assessment cost element of category 42. Business transaction KSPA.
3KE13KE5
Profit center assessment
Classic Profit Center Accounting: assessment with a special cost or revenue element, for plan and actual data.
4KE14KE5
Profit center distribution
Classic Profit Center Accounting: the original cost or revenue element is retained.
KSC5KSCB
Indirect activity allocation
Actual and plan: allocates activity quantities, which assessment cannot.
GA15FAGLGA15
FI-SL and general ledger assessment
The same cycle technique on special ledgers and on the ledgers of the new general ledger.
KOW1KOW4
Periodic reposting for orders
Create to delete periodic reposting cycles from the internal orders menu.
Sources: ERPlingo and sapstack transaction directories (KSU, KSV, KSW, KEU, 3KE, 4KE, GA and FAGLGA codes); SAP KBAs 1734931, 2007438 and 3731653; SAP Help, CO business transactions; SAP Learning, periodic credit postings; docsie, assessment cycle guide (KSC5). Projects can hide transactions, so check your own system before writing them into a manual.
Detailed comparison
Side by side, row by row
The first three rows are the short version: which costs, which cost element on the receiver, how traceable. The rest is what you need when you design, run or audit a cycle.
| Topic | Distribution | Assessment | Periodic reposting |
|---|---|---|---|
| Costs it moves | Primary costs only | Primary and secondary costs | Primary costs only |
| Cost element on the receiver | The original primary cost element | An assessment cost element, category 42 | The original primary cost element |
| Traceability of the sender | In the CO document and in the totals, by sender and receiver | In the CO document, and by sender and receiver per assessment cost element | Line items only: the totals records keep no sender |
| What it is for | Passing shared primary costs on with their detail | Charging a service cost center’s full cost to its customers | Correcting postings collected on a clearing cost center |
| Cost composition on the receiver | Kept | Lost, unless an allocation structure maps groups to several assessment cost elements | Kept |
| Credit on the sender | Original cost elements | Assessment cost element | Original cost elements |
| Data volume | Highest: a line per sender, receiver and cost element | Lower: cost elements summarized, fewer totals records | Less memory than distribution: no sender in the totals |
| Business transaction, actual · plan | RKIV · RKPV | RKIU · RKPU | RKIB · RKPB |
| Execute, actual · plan | KSV5 · KSVB | KSU5 · KSUB | KSW5 · KSWB |
| Sender and receiver rules | Posted amounts, fixed amounts or fixed rates; variable portions, fixed amounts, fixed percentages or fixed portions | The same rules | The same rules |
| Activity-dependent costs | Primary costs planned as activity-dependent are not considered | Allocated automatically in actual | Allocated automatically in actual; plan reposting can keep the sender activity type |
| SAP’s own example | Utility costs split equally across EDP, Sales and Marketing | Cafeteria allocated by number of employees | Telephone, postage, insurance from an allocation cost center |
| Place in SAP’s closing list | Task 3: distribution of primary costs | Task 9: after overhead calculation and order settlement | Task 2: right after the key figures |
| Iterative and cumulative | Both possible | Both possible | Both possible |
| Reversal | Reverse and repeat as often as needed | Reverse and repeat as often as needed | Reverse and repeat as often as needed |
| Plan data | Separate plan cycle | Separate plan cycle | Separate plan cycle |
| Posting date | Actual: last day of the month · plan: first day | Actual: last day of the month · plan: first day | Actual: last day of the month · plan: first day |
| In SAP S/4HANA | Allocation type Distribution in Manage Allocations; KSV5 remains | Allocation type Overhead Allocation; KSU5 remains | Not an allocation type in Manage Allocations; KSW5 remains |
18 rows: scroll inside the table to see them all. Sources: SAP Help, allocation types, distribution, assessment, periodic reposting, sender and receiver rules, defining periodic allocations, period-end closing, reversing periodic allocations, cumulative processing and CO business transactions; SAP Learning, performing period-end closing and periodic credit postings; SAP KBAs 3698978 and 3697722; Michael Management, universal allocations.
Decision helper
Which one fits your sender?
1Is the sender only a collecting point for costs posted there for convenience, such as telephone or postage?
2Does the sender also carry secondary costs, received from other allocations, that must move on?
3Do the receivers need to see the original cost elements, such as salaries or energy?
Our suggestion
Assessment
KSU1KSU5
Only assessment moves secondary costs. Distribution and periodic reposting would leave them on the sender.
Periodic reposting
KSW1KSW5
A clearing cost center whose costs belong elsewhere. Reposting keeps the original cost element and stores less data; the receivers see the costs as if posted to them directly.
Distribution
KSV1KSV5
Primary costs only, and the receivers keep the cost element detail, with the sender visible in the reports.
Assessment
KSU1KSU5
The receivers need the amount, not its composition: one assessment cost element, fewer records.
Receivers want detail: use an allocation structure, so each group of cost elements gets its own assessment cost element.
A rule of thumb from the rows above, not an SAP rule. Many companies run all three, one after another.
Neighbours that get mixed up with them
Four other ways of moving costs inside CO. They answer different questions.
KB11NRKU1
Manual reposting of costs
Moves primary costs between objects one posting at a time, with an immediate effect. Periodic reposting gives the same result at period end.
Source: SAP Help, periodic repostingKB15NKAMV
Manual cost allocation
Allocates primary and secondary cost element categories by hand. SAP notes the system then no longer recognises the original sender.
Source: SAP Help, manual cost allocationKSC5RKIL
Indirect activity allocation
Allocates activity quantities instead of amounts. SAP sends you here because assessment cannot allocate consumption quantities.
Source: SAP Help, assessmentCategory 21
Settlement
Orders and projects pass their costs on by settlement, with internal settlement cost elements; SAP’s closing list settles overhead orders and projects before the assessment.
Source: SAP Community, secondary cost element categories
The process
One month-end close, from the invoices to the full cost
Nine steps in the order SAP’s own period-end closing list puts them. Pick a step: the left card says what happens and why, the right card adds the transactions, settings and tables behind it.
Step 1 of 9 · Business view
Costs are posted where they arise
Invoices, payroll and depreciation are posted in FI with a cost center. IT’s salaries, licences and hardware depreciation land on 4100; the telephone bill for the whole company may land on one collecting cost center. SAP expects every relevant FI posting of the period, payroll and billing included, to be complete before the overhead close starts.
Who: Accounts payable, payroll, asset accounting
Technical view
Each posting on a P&L account that is a cost element writes a CO line item (COEP) on the cost center and updates the totals for external postings (COSP). Secondary postings, such as IT’s 6,000.00 of building costs from the facilities assessment, are totalled for internal postings (COSS).
FB50COEPCOSPCOSS
Transactions, business transactions, tables and settings for this step are in the technical view.
FB50COEPCOSPCOSS
In the exampleIT’s October costs on 4100: 78,000.00 primary, 6,000.00 secondary.
Sources: SAP Help, period-end closing in Overhead Cost Controlling and table COEP; SAP Community, COSP and COSS.
Step 2 of 9 · Business view
The keys are entered: headcount, PCs, square metres
Every split needs a key. Headcount, PCs or square metres are entered on each receiver as statistical key figures. A key that rarely changes, such as headcount, is entered once and stays valid; one that changes every month, such as PCs in use or telephone units, must be entered every month.
Who: HR, IT, facilities, controller
Technical view
Statistical key figures are created with KK01 and posted with KB31N (actual) or KP46 (plan). Category 01 Fixed values apply from the posting period to all following periods of the fiscal year; category 02 Totals values are entered per period. Transfer from the Logistics Information System is the first task in SAP’s closing list.
KK01KB31NKP46
Transactions, business transactions, tables and settings for this step are in the technical view.
KK01KB31NKP46
In the exampleHeadcount 40, 30, 20, 10 and PCs 12, 18, 25, 45 on the four receivers.
Sources: SAP Learning, performing period-end closing; SAP Help, statistical key figures and period-end closing; ERPlingo, KK01 and KP46.
Step 3 of 9 · Business view
Collecting cost centers are cleared first
Costs parked on a collecting cost center for convenience move to the cost centers that caused them, under their original cost element. Doing this first means every later step works with costs already in the right place.
Who: Controller
Technical view
KSW5 runs the periodic reposting cycles, business transaction RKIB. SAP’s closing list puts periodic reposting of costs from allocation cost centers second, right after the transfer of statistical key figures.
KSW5RKIB
Transactions, business transactions, tables and settings for this step are in the technical view.
KSW5RKIB
In the exampleTelephone and postage now sit on the cost centers that used them, IT included.
Sources: SAP Help, periodic reposting, period-end closing and CO business transactions.
Step 4 of 9 · Business view
Shared primary costs are distributed
Energy, rent or utilities collected on one cost center are passed on with their cost element, so every receiver can still compare its energy bill with last month’s.
Who: Controller
Technical view
KSV5, business transaction RKIV, moves primary cost elements only. In SAP’s closing list, distribution of primary costs is the third task, before accrual calculation and indirect activity allocation.
KSV5RKIV
Transactions, business transactions, tables and settings for this step are in the technical view.
KSV5RKIV
In the examplePrimary costs where they belong; secondary costs not touched.
Sources: SAP Help, distribution and period-end closing; SAP KBA 3698978.
Step 5 of 9 · Business view
Activities, overhead and orders add their costs
Between distribution and assessment, SAP’s list places accrual calculation, indirect activity allocation, allocation of process costs, overhead calculation and the settlement of overhead orders and projects. Each of them can add costs to the service cost centers that assessment will empty next.
Who: Controller, cost accountants
Technical view
Indirect activity allocation (KSC5, business transaction RKIL) allocates activity quantities, which assessment cannot. Settled order costs arrive under internal settlement cost elements (category 21).
KSC5RKILCategory 21
Transactions, business transactions, tables and settings for this step are in the technical view.
KSC5RKILCategory 21
In the exampleEvery cost a service cost center carries this month is now on it.
Sources: SAP Help, period-end closing, assessment and CO business transactions; SAP Community, secondary cost element categories.
Step 6 of 9 · Business view
Service cost centers are assessed
The service departments charge their internal customers. Because assessment moves secondary costs too, a canteen that received IT costs can pass them on with its own: costs cascade from service to service and down to production.
Who: Controller
Technical view
KSU5, business transaction RKIU, posts on assessment cost elements of category 42. SAP’s closing list puts assessment of primary and secondary costs ninth, after overhead calculation and settlement. Services that go both ways, IT for HR and HR for IT, need an iterative cycle.
KSU5RKIUCategory 42
Transactions, business transactions, tables and settings for this step are in the technical view.
KSU5RKIUCategory 42
In the exampleIT 4100 at zero; 84,000.00 on the four receivers.
Sources: SAP Help, assessment, period-end closing and allocation cycle.
Step 7 of 9 · Business view
Every cycle runs as a test first
Test run is the default: the cycle computes every sender and receiver without posting, so the split can be checked before the real run. Large cycles run in the background.
Who: Controller
Technical view
The execution screen asks for period or period interval, fiscal year, Test run, background processing and the cycles; entries can be saved as a variant. The basic list shows the number of senders and receivers per cycle. Actual allocations post on the last day of the month, plan allocations on the first.
KSU5KSV5KSW5
Transactions, business transactions, tables and settings for this step are in the technical view.
KSU5KSV5KSW5
In the exampleOne CO document per cycle run, dated 31 October.
Sources: SAP Help, executing periodic repostings or allocations, results lists and assessment.
Step 8 of 9 · Business view
Results are checked, and reversed if wrong
Line item reports show who sent what to whom. A run with a wrong key is reversed and run again, not fixed by hand, as often as needed.
Who: Controller, cost center managers
Technical view
KSB1 lists cost center line items with the partner object; S_ALR_87013611 compares actual and plan by cost element. Reverse from the execution transaction’s menu, for example Assessment › Reverse. A posted cycle run again for the same period gives GA517, has already run, reversal will be started. Closed periods are corrected by segment reversal and rebooking in the open one.
KSB1S_ALR_87013611GA517
Transactions, business transactions, tables and settings for this step are in the technical view.
KSB1S_ALR_87013611GA517
In the exampleAllocations you can trace and repeat.
Sources: SAP Help, reversing periodic allocations; SAP Learning, periodic debit postings and performing period-end closing; ERPlingo, GA517; docsie, S_ALR_87013611.
Step 9 of 9 · Business view
Prices, variances, CO-PA and the period lock
With full costs on the operational cost centers, SAP calculates actual activity prices and variances, assesses what was not absorbed to profitability analysis, locks the period and, if needed, reconciles CO with FI.
Who: Controller
Technical view
Actual price calculation (KSII), variance calculation, assessment to CO-PA (KEU5, business transaction KSPA), period lock (OKP1), and in the classic general ledger the reconciliation postings with KALC. With the new general ledger, real-time integration replaces the reconciliation ledger.
KSIIKEU5OKP1KALC
Transactions, business transactions, tables and settings for this step are in the technical view.
KSIIKEU5OKP1KALC
In the exampleA closed October with full costs on every cost center.
Sources: SAP Help, period-end closing, CO business transactions, CO period lock and real-time integration; SAPinsider, closing with the new G/L.
Where the three sit in SAP’s closing list
SAP Help lists sixteen period-end tasks for Overhead Cost Controlling in a logical sequence. The three methods are not neighbours: reposting and distribution open the close, assessment comes after activities, overhead and order settlement have added their costs.
SAP adds that the exact tasks and their order depend on the functions you use, and that follow-up costs are handled by repeating the flow for the period.
Source: SAP Help, period-end closing in Overhead Cost Controlling- 1Transfer of statistical key figures from LIS
- 2Periodic reposting from allocation cost centers
KSW5 · periodic reposting - 3Distribution of primary costs
KSV5 · distribution - 4Accrual calculation
- 5Indirect internal activity allocation
KSC5 - 6Allocation of process costs
- 7Overhead calculation
- 8Settlement of overhead orders and projects
- 9Assessment of primary and secondary costs
KSU5 · assessment - 10Balance-sheet settlement of orders
- 11Splitting actual costs to activity types
- 12Actual activity price calculation
- 13Target/actual variances
- 14Assessment of under- or overabsorption to CO-PA
KEU5 - 15Period lock for CO business transactions
- 16Reconciliation postings in FI
Try it: one cycle, three methods
Allocate 84,000.00 of IT costs yourself
October’s IT costs sit on cost center 4100. Pick the method, the key and how much the sender gives away, then read the CO document, what Brewing’s report shows and what stays behind. Two surprises are built in, plus three classic traps.
Your cycle IT-OCT
Example: assessment by headcount, 100 % of the sender’s costs, no trap.
Examples only. One cycle, one segment, no iteration; amounts rounded to the cent so that every cost element adds up.
The facts behind it
- Sender 4100 IT Services, company code 1010, October: 430000 Salaries 48,000.00, 466000 Software licences 21,000.00 and 481000 Hardware depreciation 9,000.00, all primary; 943000 Building assessment 6,000.00, secondary (category 42), received from facilities.
- Receivers: 4210 Brewing, 4220 Filling, 4300 Logistics, 4400 Sales.
- Keys: headcount 40, 30, 20, 10 (statistical key figure, fixed values, entered once); PCs in use 12, 18, 25, 45 (totals values, entered every month); fixed percentages 35, 25, 20, 20.
- Assessment cost element 941000 IT assessment, category 42.
1 · The key becomes shares
Headcount, statistical key figure (fixed values)
| Receiver | Tracing factor | Share |
|---|---|---|
| 4210 Brewing | 40 employees | 40.0% |
| 4220 Filling | 30 employees | 30.0% |
| 4300 Logistics | 20 employees | 20.0% |
| 4400 Sales | 10 employees | 10.0% |
| Total | 100 employees | 100.0% |
Fixed values: entered once, valid in every following period of the fiscal year until changed.
2 · What leaves cost center 4100
Primary costs, 430000 to 48100078,000.00 → 0.00
Secondary costs, 9430006,000.00 → 0.00
4100 IT Services in total84,000.00 → 0.00
Receivers 4210 to 44000.00 → 84,000.00
IT is at zero: assessment moved the primary costs and the 6,000.00 of secondary building costs.
3 · The CO document the run posts
RKIU · Actual Overhead Assessment · 8 line items · 31.10.2026| Object | Cost element | Partner object | Amount |
|---|---|---|---|
| 4100 IT Services | 941000 | 4210 | −33,600.00 |
| 4210 Brewing | 941000 | 4100 | 33,600.00 |
| 4100 IT Services | 941000 | 4220 | −25,200.00 |
| 4220 Filling | 941000 | 4100 | 25,200.00 |
| 4100 IT Services | 941000 | 4300 | −16,800.00 |
| 4300 Logistics | 941000 | 4100 | 16,800.00 |
| 4100 IT Services | 941000 | 4400 | −8,400.00 |
| 4400 Sales | 941000 | 4100 | 8,400.00 |
No CO document: nothing was posted.
Every line uses 941000: the sender is credited and the receivers are debited with the assessment cost element. One line pair per receiver.
4 · What Brewing 4210’s cost center report shows
| Cost element | Text | Actual | Sender in totals |
|---|---|---|---|
| 941000 | IT assessment | 33,600.00 | 4100 |
| Total from IT | 33,600.00 |
Brewing sees one line. What it consists of is visible only on IT’s side, unless an allocation structure splits it into several assessment cost elements.
5 · Same costs, same key, three methods
| Receiver | Distribution | Assessment | Reposting |
|---|---|---|---|
| 4210 Brewing | 31,200.00 | 33,600.00 | 31,200.00 |
| 4220 Filling | 23,400.00 | 25,200.00 | 23,400.00 |
| 4300 Logistics | 15,600.00 | 16,800.00 | 15,600.00 |
| 4400 Sales | 7,800.00 | 8,400.00 | 7,800.00 |
| Left on 4100 | 6,000.00 | 0.00 | 6,000.00 |
| Line items in the document | 24 | 8 | 24 |
| Cost elements Brewing sees | 3 | 1 | 3 |
| Sender visible in totals | Yes | Yes | No |
Surprise two: distribution and periodic reposting post exactly the same amounts. Brewing gets 31,200.00 either way, against 33,600.00 with assessment, which also moves the building costs. What separates distribution from reposting is not the money but what the reports can still tell you.
Simplified: one sender, one segment, one period, no iteration. Sources: SAP Help, allocation types, assessment, periodic reposting, sender and receiver rules, and statistical key figures; SAP Learning, performing period-end closing; SAP KBAs 1734931 and 3698978; ERPlingo, message GA517; SAP Help, CO period lock.
Inside a cycle
Cycle, segment, sender, receiver: the words you will meet
A cycle is a header plus one or more segments. The header holds what is valid for all of them; each segment groups the senders that follow the same rule. SAP Learning’s example: a telephone cost center allocated by telephone units and an energy cost center allocated by square metres need two segments.
IT-OCTStart 01.01.2026 · End 31.12.2026 · Iterative off · Cumulative off · Field group: actual valuesIT-HEADTEL-UNITSExample cycle. The four tabs of a segment are the ones SAP Help names: segment header, senders/receivers, sender values and receiver tracing factors.
In the cycle header. Valid for every segment of the cycle. Cycles are saved by time, so each needs a validity period, and the cycle must be valid in the posting period.
In the segment header. One segment for each group of senders that follow the same rules. The order of the segments within a cycle has no bearing on the result.
Sender rules. The same three for distribution, assessment and periodic reposting. Indirect activity allocation has its own: posted amounts, fixed amounts and inversely determined quantities.
Receiver rules. How the sender value is split. With variable portions the system determines the tracing factor during the run.
Under the result. What a run writes and where the cycle definition is stored.
Messages. The ones users search for most. The troubleshooting section below explains each one.
DateStart and end dateThe validity of the cycle; the end date defaults to the end of the fiscal year.IterIterativeSegments feed each other until all senders are credited. Needed when services go both ways.CumCumulativeAllocates from period 1 to the current period by cumulated tracing factors.QtyActual quantitiesField group for allocating quantities together with amounts.CurrObject or transaction currencyValid only if Customizing allows all currencies in the controlling area.VerVersion (plan)A plan cycle can run in several versions without reversing the run in another version.SSender ruleHow much each sender gives: posted amounts, fixed amounts or fixed rates.%Share in %Below 100 % a residual stays on the sender, on purpose.RReceiver ruleHow the amount is split: variable portions, fixed amounts, fixed percentages or fixed portions.42Assessment cost elementAssessment only: the category 42 cost element, or an allocation structure instead.NegScaling of negative tracing factorsSet per segment, not per cycle: no scaling, standard scaling, absolute value or set to zero.LockLock indicatorThe system ignores a locked segment when the cycle runs.1Posted amountsThe balance posted on the sender, for the cost elements in the segment, is allocated.2Fixed amountsA fixed amount per sender, whatever was posted.3Fixed ratesA price per unit of the receiver tracing factor, entered per sender.%Share in %With posted amounts, the percentage of the balance to credit.PlanPlan values in an actual cycleA segment can allocate plan values in an actual cycle, or actual values in a plan cycle.2 + 2Fixed amounts on both sidesNot advisable: the system always uses the fixed receiver amounts.1Variable portionsRead at run time, by version, cost element, activity type or statistical key figure.2Fixed amountsReceivers are debited directly; the sender is credited with their total.3Fixed percentagesA percentage per receiver; together they must not exceed 100 %.4Fixed portionsLike percentages, in portions; the sender is credited completely unless a residual is set.01Key figure, fixed valuesValid from the posting period for all following periods of the year.02Key figure, totals valuesEntered for each period, because they change from period to period.RKIVActual Overhead DistributionBusiness transaction of KSV5; RKPV in plan.RKIUActual Overhead AssessmentBusiness transaction of KSU5; RKPU in plan.RKIBActual Periodic RepostingBusiness transaction of KSW5; RKPB in plan.RRIUSegment adjustmentRRIV, RRIU and RRIB: segment adjustments of actual distribution, assessment and reposting.42Assessment cost elementThe secondary cost element category that assessment credits on the sender and debits on the receivers.T811CCyclesCycle header data; T811S holds the segments, T811K the key fields.GA733The segment contains no receiversNo receiver has a tracing factor in the period.GA714The segment does not contain any sendersRaised per segment, for example in KSU5.GA749Cycle does not include any sendersNo valid sender matches the selection.GA727Sender base in period is 0Therefore no allocation is possible.GA751Receiver allocation bases > 100%Too much in the receivers’ fixed percentages.GA517Has already run, reversal will be startedThe cycle already posted in the period.
Sources: SAP Help, allocation cycle, creating cycles, creating or changing cycles, iterative and cumulative processing.
Sources: SAP Help, allocation segment, allocation cycle, creating segments, assessment and scaling of negative tracing factors; SAP Learning, performing period-end closing.
Sources: SAP Help, sender and receiver rules, combinations of rules and creating segments; SAP Learning, performing period-end closing.
Sources: SAP Help, receiver rules, sender and receiver rules, creating a receiver tracing factor and receiver weighting factors; SAP Learning, performing period-end closing.
Sources: SAP Help, CO business transactions, assessment and table COEP; TestingBrain and leanX table pages.
Sources: SAP KBAs 1734931, 3439305, 2136107, 1898808 and 2152595; Michael Management, GA749; ERPlingo, GA517.
Four tools that get mixed up, four jobs. Periodic reposting moves primary costs as a correction and keeps no partner in the totals. Distribution moves primary costs and keeps their cost element. Assessment moves primary and secondary costs under category 42. Indirect activity allocation, KSC5, moves activity quantities, which assessment cannot do. Source: SAP Help, assessment
Iterative
When IT serves HR and HR serves IT
With Iterative set, the result of one segment is used by the others until all senders are completely credited. Without it, each segment runs on its own, which is faster and leaves the costs of a sender’s own consumption on it, as SAP’s example of an energy cost center shows. Cycles are never iterated with each other.
Sources: SAP Help, allocation cycle and iterative processing; SAP LearningCumulative
Smoothing a year that does not behave
A cumulative cycle allocates the sender amounts posted from period 1 to the current period by the cumulated tracing factors, so a month with odd key figures does not distort the split. SAP notes that in some countries smoothing is a legal requirement, and that public-sector customers may demand it to rule out manipulation. Senders and receivers must not be deleted during the fiscal year, and the indicator should not change mid-year.
Source: SAP Help, cumulative processing of allocation cyclesSegment reversal and rebooking
Fix three closed months in the open one
Cost center A distributed 100 a month equally to B and C from January to March. In April the key is corrected to 75 : 25. Reversal and rebooking post the correction in April; January to March stay closed.
Source: SAP Learning, performing period-end closingApril Reversal Rebooking A, sender +300 −300 B −150 +225 C −150 +75
Troubleshooting
Why did my cycle post nothing? Twelve classics
The messages and surprises users search for most around KSU5, KSV5 and KSW5, taken from SAP knowledge base articles, SAP Help and the SAP Community. Guess the cause, then open the card to check.
- Receivers
- Senders
- Running
- Rules
- Expected
GA733The segment contains no receiversShow the causeReceiversNo receiver has a tracing factor for the period: often a totals-value key figure nobody entered this month, or receiver selection criteria that find nothing. SAP KBAs also cover it for actual statistical key figures and for a functional area entered in the cycle.
Source: SAP KBAs 1734931, 2941081 and 2568675; SAP Community, KSU5 segment contains no receivers
GA749Cycle … does not include any sendersShow the causeSendersNo valid sender matches the selection. SAP’s long text asks you to check the cycle definition and, with GCA8, the inheritance logic for allocations.
Source: Michael Management, message GA749
GA714The segment does not contain any sendersShow the causeSendersRaised per segment in KSU5, sometimes although a sender is entered in the cycle. Two SAP KBAs cover the cases.
Source: SAP KBAs 3363483 and 3439305
GA751Receiver allocation bases > 100% for senderShow the causeRulesThe receivers’ fixed percentages add up to more than 100. SAP Help: for fixed percentages the total of the receiver tracing factors must not exceed 100 %.
Source: SAP KBA 1898808; SAP Help, creating a receiver tracing factor
GA727Sender base in period is 0; no allocation is possibleShow the causeRulesRaised by KSU5 and KSV5 when the sender base of the period is zero. SAP KBA 2136107 explains the message.
Source: SAP KBA 2136107
GA562Cycle cannot be started because run group is lockedShow the causeRunningThe run group of the cycle is locked when you start it. SAP KBAs cover the lock in KSU5, KEU5 and KSV5.
Source: SAP KBAs 2152595 and 2804840
GA517… has already run, reversal will be startedShow the causeRunningExpected when a cycle that already posted runs again for the same period: the earlier run is cancelled first. Cumulative cycles ask whether to execute the reversal.
Source: ERPlingo, message GA517; SAP KBA 2943593
GA015No valid receiver entries existShow the causeReceiversOrders or an order group set as receivers, when you open the segment header or the receiver tracing factors in KSU2 or KSV2. SAP KBA 3702265 lists maintenance and production orders among the cases.
Source: SAP KBA 3702265
KSV5Distribution ignored what the cost center receivedShow the causeExpectedExpected: KSV5 selects primary cost elements only, so postings that came from an assessment are not distributed. Assess them instead.
Source: SAP KBA 3698978
ResidualThe sender is not at zeroShow the causeExpectedThree normal reasons: a sender share below 100 % leaves the rest on purpose; fixed receiver amounts credit the sender only with their total; a non-iterative cycle leaves the costs of the sender’s own consumption on it.
Source: SAP Learning, performing period-end closing; SAP Help, creating a receiver tracing factor and iterative processing
GA776Cumulation not possible, no stable allocation networkShow the causeRulesCumulative cycles need the same network all year: senders and receivers must not be deleted within the fiscal year. SAP KBA 3773449 covers it with key figures as the receiver basis.
Source: SAP Help, cumulative processing; SAP KBA 3773449
RKALPSACMy WBS element is not offered as a senderShow the causeSendersOrders and WBS elements are enabled as senders of actual distribution and assessment with report RKALPSAC. Plan cycles do not offer them as senders or receivers.
Source: SAP KBA 3731653
Reference
Every transaction, report and table around allocations
From the key figures to the period lock, plus the Customizing, tables and messages behind them. Filter by area, then by audience; Start here shows the ones worth bookmarking. Type a code or a word to search.
| Code | Area | What it does | For | ECC / S/4HANA |
|---|---|---|---|---|
KSV1 | CO-OM-CCA · Distribution · cycle | Create an actual distribution cycle: header, segments, senders, receivers, rules. | Consultants | ECC · S/4HANA |
KSV3 | CO-OM-CCA · Distribution · cycle | Display an actual distribution cycle. | Users | ECC · S/4HANA |
KSU1 | CO-OM-CCA · Assessment · cycle | Create an actual assessment cycle, with the assessment cost element or an allocation structure in the segment header. | Consultants | ECC · S/4HANA |
KSU3 | CO-OM-CCA · Assessment · cycle | Display an actual assessment cycle. | Users | ECC · S/4HANA |
KSW1 | CO-OM-CCA · Periodic reposting · cycle | Create a periodic reposting cycle. | Consultants | ECC · S/4HANA |
KSW3 | CO-OM-CCA · Periodic reposting · cycle | Display a periodic reposting cycle. | Users | ECC · S/4HANA |
KSU4 | CO-OM-CCA · Assessment · cycle | Delete an actual assessment cycle; KSV4 and KSW4 do the same for the others. | Consultants | ECC · S/4HANA |
KSU7 | CO-OM-CCA · Plan · cycle | Create a plan assessment cycle; KSV7 and KSW7 for plan distribution and plan reposting. | Consultants | ECC · S/4HANA |
KOW1 | CO-OM-OPA · Internal orders · cycle | Create a periodic reposting cycle from the internal orders menu. | Consultants | ECC · S/4HANA |
KSV5 | CO-OM-CCA · Period-end closing | Execute actual distribution: period, fiscal year, test run, cycles. | Users | ECC · S/4HANA |
KSU5 | CO-OM-CCA · Period-end closing | Execute actual assessment. | Users | ECC · S/4HANA |
KSW5 | CO-OM-CCA · Period-end closing | Execute actual periodic reposting. | Users | ECC · S/4HANA |
KSVB | CO-OM-CCA · Planning | Execute plan distribution. | Users | ECC · S/4HANA |
KSUB | CO-OM-CCA · Planning | Execute plan assessment. | Users | ECC · S/4HANA |
KSWB | CO-OM-CCA · Planning | Execute plan periodic reposting. | Users | ECC · S/4HANA |
KSU6 | CO-OM-CCA · Overview | Actual assessment overview; KSV6 and KSW6 for the others, KSUC and KSWC in plan. | Users | ECC · S/4HANA |
KSB1 | Reporting · Line items | Cost centers: actual line items, with the partner object of every allocation. | Users | ECC · S/4HANA |
S_ALR_87013611 | Reporting · Plan/actual | Cost centers: actual/plan/variance by cost element. | Users | ECC · S/4HANA |
OKP1 | CO · Period lock | Locks CO business transactions, such as RKIU, by period, for actual or plan. | Consultants | ECC · S/4HANA |
KK01 | CO-OM-CCA · Statistical key figures | Create a statistical key figure: fixed values (01) or totals values (02). | Consultants | ECC · S/4HANA |
KB31N | CO-OM-CCA · Statistical key figures | Enter actual statistical key figures, such as headcount or telephone units. | Users | ECC · S/4HANA |
KP46 | CO-OM-CCA · Statistical key figures | Plan statistical key figures. | Users | ECC · S/4HANA |
KA06 | CO-OM-CEL · Cost elements | Create a secondary cost element, such as an assessment cost element of category 42. | Consultants | ECC |
FS00 | FI-GL · G/L accounts | In SAP S/4HANA also maintains cost elements, category 42 included, as G/L accounts. | Consultants | S/4HANA |
KB11N | CO-OM-CCA · Manual reposting | Enter manual repostings of costs, with an immediate effect; business transaction RKU1. | Users | ECC · S/4HANA |
KB15N | CO-OM-CCA · Manual allocation | Enter manual allocations of primary and secondary costs; business transaction KAMV. | Users | ECC · S/4HANA |
KSC5 | CO-OM-CCA · Indirect activity allocation | Execute actual indirect activity allocation: quantities, not amounts. | Users | ECC · S/4HANA |
KSII | CO-OM-CCA · Price calculation | Actual price calculation for cost center activities, after the assessments. | Consultants | ECC · S/4HANA |
KEU5 | CO-PA · Assessment to CO-PA | Assess cost center costs to profitability segments; business transaction KSPA. | Users | ECC · S/4HANA |
3KE5 | EC-PCA · Profit Center Accounting | Execute actual assessment between profit centers. | Users | ECC · S/4HANA |
4KE5 | EC-PCA · Profit Center Accounting | Execute actual distribution between profit centers. | Users | ECC · S/4HANA |
GA15 | FI-SL · Special ledgers | Execute FI-SL actual assessment. | Consultants | ECC · S/4HANA |
FAGLGA15 | FI-GL · New general ledger | Execute general ledger actual assessment. | Consultants | ECC · S/4HANA |
KALC | CO · Reconciliation ledger | Posts cross-entity CO allocations to FI at period end; replaced by real-time integration in the new general ledger. | Consultants | Classic G/L |
F3338 | Universal Allocation · Manage Allocations | SAP S/4HANA: cycles of type Overhead Allocation, the new name of assessment, and Distribution. | Users | S/4HANA |
F3548 | Universal Allocation · Run Allocations | SAP S/4HANA: test run, live run and reversal of allocation cycles. | Users | S/4HANA |
RKIV · RKIU · RKIB | Business transactions · Actual | Actual distribution, assessment and periodic reposting. | Consultants | ECC · S/4HANA |
RKPV · RKPU · RKPB | Business transactions · Plan | Plan distribution, assessment and periodic reposting. | Consultants | ECC · S/4HANA |
OKC1 | CO · Business transactions | Displays all CO business transactions. | Consultants | ECC · S/4HANA |
T811C | Tables · Allocation cycles | Cycle header data. | Consultants | ECC · S/4HANA |
T811S | Tables · Allocation segments | Segments of each cycle. | Consultants | ECC · S/4HANA |
T811DS | Tables · Segment reverse/rebook | Document numbers of segment reversal and rebooking. | Consultants | ECC · S/4HANA |
COEP | Tables · CO line items | CO object line items by period. | Consultants | ECC |
COSP · COSS | Tables · CO totals | Cost totals for external (primary) and internal (secondary) postings. | Consultants | ECC |
RKALPSAC | Report · Senders | Enables orders and WBS elements as senders of actual distribution and assessment. | Consultants | ECC · S/4HANA |
GA733 | Messages · Allocations | The segment contains no receivers. | Users | ECC · S/4HANA |
GA749 | Messages · Allocations | Cycle does not include any senders. | Users | ECC · S/4HANA |
GA751 | Messages · Allocations | Receiver allocation bases > 100% for sender. | Users | ECC · S/4HANA |
GA517 | Messages · Allocations | Has already run, reversal will be started. | Users | ECC · S/4HANA |
Nothing matches. Try another word, or pick All in both rows.
Codes cross-checked with SAP Help, SAP Learning, SAP KBAs, ERPlingo, sapstack, leanX and TestingBrain. Codes ending in N, such as KSU6N or KSW1N, are newer variants of the same functions. Projects can hide transactions, so check your own system before writing them into a manual.
Documented, but little known
19 tips most people never hear about
Each tip comes from SAP Help, SAP Learning, an SAP KBA or a documented article, linked under the tip.
- 01Users
Leave Test run on the first time
Test run is the default: the system executes the cycle without updating the database, so you can check the lists before you post.
KSU5KSV5
- 02Users
Run big cycles in the background
SAP recommends background processing for periodic repostings and allocations with large amounts of data.
KSU5
- 03Users
Know which keys carry forward
Fixed values (category 01) stay valid in the following periods of the year; totals values (category 02) must be entered every period, or the cycle finds no receivers.
KB31N
- 04Users
Reverse, do not patch
Choose Reverse in the execution transaction, for example Assessment › Reverse, then run again with the right key. SAP allows it as often as needed within a cycle.
KSU5
- 05Users
Look on the last day of the month
Actual allocations post on the last day of the month and plan allocations on the first, so that is where line item reports by posting date show them.
KSB1
- 06Users
Save the run as a variant
The execution screen lets you save your entries as a variant, so next month’s run repeats the same settings and cycles.
KSU5KSV5
- 07Consultants
One allocation structure instead of many segments
An allocation structure maps cost elements, groups or intervals to several assessment cost elements, so one segment keeps the cost composition visible on the receiver.
KSU1
- 08Consultants
Separate cycles for plan and actual
SAP requires one cycle for plan and one for actual allocation of the same type. A plan cycle can run in several versions without reversing the others.
KSU7KSUB
- 09Consultants
Lock a segment instead of deleting it
Set the lock indicator in the segment header and the system ignores the segment when the cycle runs.
KSU2
- 10Consultants
Iterate only where services go both ways
Without the Iterative indicator the system processes the segments in succession, which SAP says is much faster. Iteration is only needed when receivers are also senders.
KSU1
- 11Consultants
Decide on cumulative before the year starts
Do not change the cumulative indicator during the fiscal year, and do not delete senders or receivers within it.
KSU2
- 12Consultants
Scale negative tracing factors per segment
With variable portions, negative tracing factors can credit receivers or break an iteration. Scaling is set for each segment, not for the cycle.
KSU1
- 13Consultants
Orders and WBS elements as senders
For actual distribution and assessment, report RKALPSAC enables them as senders. Plan cycles do not offer orders and WBS elements as senders or receivers.
RKALPSAC
- 14Consultants
KSV5 then KSW5 after an upgrade
SAP KBA 3697722 covers amounts distributed with KSV5 that are no longer picked up as sender values by KSW5 after an upgrade to SAP S/4HANA 2023.
KSV5KSW5
- 15Consultants
Check cycles in the tables
Cycle headers are in T811C, segments in T811S and key fields in T811K; T811DS keeps the documents of segment reverse and rebook.
T811CT811S
- 16FI and HR
FI: close FI before CO
SAP expects every relevant FI posting of the period, payroll and billing included, to be complete before the overhead close starts.
FB50
- 17FI and HR
FI: allocations can create FI documents
With the new general ledger, real-time integration posts CO allocations that cross company codes, profit centers or business areas to FI immediately; the classic general ledger needs KALC at period end.
KALC
- 18FI and HR
FI: category 42 is a G/L account in SAP S/4HANA
Secondary cost elements, assessment cost elements included, are G/L accounts of type Secondary Costs, maintained in FS00.
FS00
- 19FI and HR
HR and facilities: your numbers are the keys
Headcount per cost center is SAP’s own example for assessing the cafeteria, and telephones per cost center for distributing telephone costs.
KB31N
Myths
Things people get wrong about allocations
Myth
Distribution and assessment send different amounts to the receivers.FactOn the same primary costs and key they split the same amounts: in SAP’s example both charge EUR 500 to each receiver. What differs is the cost element, and assessment also moves secondary costs.
Myth
Assessment hides who sent the costs.FactSender and receiver are recorded in the CO document, and the information system analyses assessment results by sender and receiver. What the receiver loses is the composition of the costs.
Myth
Periodic reposting is distribution under another name.FactIt is a correction aid with the result of a manual reposting. Its totals do not record the sender, so it stores less data and the origin shows only in the line items.
Myth
Distribution can pass on what a cost center received from other allocations.FactKSV5 selects primary cost elements only. Secondary costs, such as a received assessment, stay on the sender unless you assess them.
Myth
A cycle always empties the sender.FactA share below 100 %, fixed receiver amounts or a non-iterative cycle with internal consumption leave a balance, on purpose.
Myth
Once posted, an allocation is final.FactPeriodic allocations can be reversed and repeated as often as needed, and segment reversal and rebooking corrects closed periods in the open one.
Myth
The order of the segments in a cycle changes the result.FactSAP Help: the order of the allocation segments within a cycle has no bearing on the result. The order of the cycles in the close does matter.
Myth
Allocations stay inside CO; FI never sees them.FactAllocations that cross company codes, profit centers or business areas reach FI: in real time with the new general ledger, through the reconciliation ledger and KALC in the classic one.
Evolution
From the R/3 cycle to Universal Allocation
The cycle-and-segment model has hardly changed in decades. What changed around it is where the postings land and which apps run them. Gold dots mark the SAP S/4HANA era, the subject of the next page.
- R/3 4.6CSAP Help documents allocation cycles and segments, sender and receiver rules, iterative and cumulative processing, and the three methods: distribution, assessment and periodic reposting.
- R/3 4.70Executing and reversing periodic repostings and allocations online, as often as needed within a cycle, and scaling of negative tracing factors are documented step by step.
- ECC new G/LReal-time integration of CO with FI posts allocations that cross company codes, profit centers or business areas to the general ledger at once, replacing the reconciliation postings of KALC.
- Simple FinanceSecondary cost elements, assessment cost elements of category 42 included, become G/L accounts maintained in FS00; KA06 is no longer used.
- 1809Universal Allocation starts with cost center planning: separate apps for plan overhead allocation and plan distribution.
- 1909Manage Allocations and Run Allocations bring the types Overhead Allocation and Distribution for cost centers and profit centers, actual and plan.
- 2021A new type, Intercompany Allocation, sends costs from cost centers in one company code to cost centers or WBS elements in others.
- TodayKSU5, KSV5 and KSW5 still run in SAP S/4HANA on-premise, and internal orders still need them: Manage Allocations does not handle internal orders.
Coming next: part 2, SAP S/4HANA
- Assessment is called Overhead Allocation; distribution keeps its name.
- Cycles are built in Manage Allocations (F3338) and run in Run Allocations (F3548).
- Periodic reposting is not one of its allocation types; KSW5 stays.
- Existing KSU5 and KSV5 cycles can be migrated to Universal Allocation.
- Internal orders still use the classic transactions.
Sources: SAP Learning, distribution and overhead allocation and periodic credit postings; Michael Management, universal allocations; SAP KBA 2864704.
Where the cycles and postings live
| Table | Holds |
|---|---|
T811C | Cycles: header data |
T811S | Segments |
T811K | Key fields |
T811DS | Document numbers for segment reverse/rebook |
COEP | CO line items by period |
COSP · COSS | Totals: primary (external) · secondary (internal) |
SAP ECC. Sources: TestingBrain and leanX table pages; SAP Help, table COEP; SAP Community, COSP and COSS.
The questions people ask most
What is the difference between assessment and distribution in SAP?
Distribution moves primary costs only and posts them under the original cost element, so the receiver sees salaries, energy or rent. Assessment moves primary and secondary costs under an assessment cost element of category 42, so the receiver sees one line and the composition is lost. Sender and receiver are documented in both.
When should I use periodic reposting instead of distribution?
When the sender is only a collecting point for costs posted there for convenience, such as telephone or postage, and nobody needs to analyse the flow between cost centers. Reposting keeps the original cost element, has the same result as a manual reposting and stores less data than a distribution, but the totals no longer show the sender.
Which transactions run each method?
For actual data, KSV5 (distribution), KSU5 (assessment) and KSW5 (periodic reposting); for plan data, KSVB, KSUB and KSWB. The cycles are created with 1, changed with 2, displayed with 3, deleted with 4 and listed with 6, such as KSU1 to KSU6; plan cycles use 7, 8, 9, A and C.
Can distribution allocate secondary costs?
No. KSV5 selects primary cost elements only; secondary costs, such as an assessment the cost center received, stay on the sender unless you assess them.
What is cost element category 42?
The category of assessment cost elements: in an assessment, the sender is credited and the receivers are debited with it. In SAP S/4HANA it is a G/L account of type Secondary Costs, maintained in FS00.
Why does my cycle say the segment contains no receivers (GA733)?
No receiver has a tracing factor in the period: typically a statistical key figure of type totals values that was not entered this month, or receiver selection criteria that find nothing.
Can I reverse an allocation?
Yes. Choose Reverse from the menu of the execution transaction, for example Assessment › Reverse; SAP allows reversing and repeating as often as needed. Running a posted cycle again for the same period also cancels the first run (message GA517).
What does iterative mean in a cycle?
With Iterative set, the results of one segment feed the others until all senders are completely credited, which is needed when cost centers serve each other, such as IT and HR. Without it, each segment is processed on its own, which is faster.
What is a cumulative cycle?
It allocates the sender amounts posted from period 1 to the current period by cumulated tracing factors, smoothing the allocation over the year. In some countries smoothing is a legal requirement. Senders and receivers must not be deleted during the fiscal year.
In which order should the cycles run at month end?
SAP’s period-end closing list puts periodic reposting second, distribution of primary costs third and assessment of primary and secondary costs ninth, after indirect activity allocation, overhead calculation and the settlement of overhead orders and projects.
Why is the sender not credited to zero?
A sender share below 100 %, fixed amounts on the receiver side, or a non-iterative cycle that leaves the sender’s own consumption on it. Distribution and reposting also leave every secondary cost on the sender.
Can I allocate across company codes?
Yes, within one controlling area. In SAP ECC with the new general ledger, real-time integration posts such allocations to FI at once; with the classic general ledger, the reconciliation ledger does it at period end with KALC.
Do I need separate cycles for plan and actual?
Yes. SAP requires a separate cycle for plan and for actual allocation of the same type; plan cycles have their own transactions, such as KSU7 to create and KSUB to execute a plan assessment.
Are KSU5, KSV5 and KSW5 still in SAP S/4HANA?
Yes, on-premise. SAP S/4HANA adds Universal Allocation, where assessment is called Overhead Allocation and runs in Manage Allocations and Run Allocations; internal orders still use the classic transactions. Part 2 of this page covers it.
Related pages
References
Checked in November 2026. SAP knowledge base articles need an SAP for Me login. Transactions and releases change; check them in your own system.
- Allocation types: distribution and assessmenthelp.sap.com
- Distributionhelp.sap.com
- Glossary: distributionhelp.sap.com
- Assessment and allocation structureshelp.sap.com
- Periodic repostinghelp.sap.com
- Defining periodic repostings or periodic allocationshelp.sap.com
- Period-end closing in Overhead Cost Controllinghelp.sap.com
- Sender and receiver ruleshelp.sap.com
- Combinations of sender and receiver ruleshelp.sap.com
- Receiver ruleshelp.sap.com
- Creating a receiver tracing factorhelp.sap.com
- Receiver weighting factorshelp.sap.com
- Allocation cyclehelp.sap.com
- Allocation cycle: execution typeshelp.sap.com
- Creating cycleshelp.sap.com
- Creating or changing cycles (versions)help.sap.com
- Cycle header: currencieshelp.sap.com
- Iterative processing of cycleshelp.sap.com
- Dependent segments and validity periodshelp.sap.com
- Cumulative processing of allocation cycleshelp.sap.com
- Scaling of negative tracing factorshelp.sap.com
- Creating segmentshelp.sap.com
- Allocation segmenthelp.sap.com
- Executing periodic repostings or allocationshelp.sap.com
- Executing online: variantshelp.sap.com
- Reversing periodic repostings or allocationshelp.sap.com
- Results of periodic repostings or allocationshelp.sap.com
- Statistical key figureshelp.sap.com
- Periodic allocationshelp.sap.com
- Assessment to CO-PAhelp.sap.com
- Assessment and distribution in Profit Center Accountinghelp.sap.com
- CO business transactionshelp.sap.com
- CO period lockhelp.sap.com
- Manual cost allocationhelp.sap.com
- Table COEPhelp.sap.com
- Real-time integration of CO with FIhelp.sap.com
- Merge of cost elements and G/L accountshelp.sap.com
- Performing period-end closinglearning.sap.com
- Explaining periodic credit postingslearning.sap.com
- Periodic debit postingslearning.sap.com
- Differentiating between distribution and overhead allocationlearning.sap.com
- Managing master datalearning.sap.com
- Creating statistical key figures for cost allocationslearning.sap.com
- KBA 1734931: GA733 in allocationssupport.sap.com
- KBA 2941081: GA733 with actual key figuressupport.sap.com
- KBA 2568675: GA733 with functional areasupport.sap.com
- KBA 3363483: warning GA714 in KSU5support.sap.com
- KBA 3439305: GA714 in KSU5support.sap.com
- KBA 2136107: GA727 in KSU5 or KSV5support.sap.com
- KBA 1898808: GA751support.sap.com
- KBA 2152595: GA562 run group lockedsupport.sap.com
- KBA 2804840: lock error GA562support.sap.com
- KBA 3702265: GA015 with orders as receiverssupport.sap.com
- KBA 3698978: KSV5 and secondary costssupport.sap.com
- KBA 3697722: KSV5 amounts in KSW5support.sap.com
- KBA 3731653: orders and WBS elements as senderssupport.sap.com
- KBA 3773449: GA776 cumulation not possiblesupport.sap.com
- KBA 2943593: cumulative cycle allocationsupport.sap.com
- KBA 2007438: scaling negative tracing factorssupport.sap.com
- KBA 3329144: RKIU and KSUBsupport.sap.com
- KBA 2864704: migrating cycles to Universal Allocationsupport.sap.com
- Universal Allocation in SAP S/4HANA 1909blogs.sap.com
- Universal Allocation in SAP S/4HANA 2021blogs.sap.com
- Universal Allocation in SAP S/4HANA 2022community.sap.com
- S/4HANA controlling: cost elementsblogs.sap.com
- New general ledger introductionblogs.sap.com
- Assessment vs distributionanswers.sap.com
- Secondary cost element categoriesanswers.sap.com
- KSU5: the segment contains no receiversanswers.sap.com
- COSP and COSS totalscommunity.sap.com
- Cost allocation definitionaccountingtools.com
- Cost allocation methods and benefitsaccountingtools.com
- Allocation definitionaccountingtools.com
- Cost allocationcorporatefinanceinstitute.com
- Accelerate your closing with the new G/Lsapinsider.org
- Real-time FI/CO integrationmasteringsap.com
- Period closing within Controlling (OKP1)masteringsap.com
- Universal allocations in SAP S/4HANAmichaelmanagement.com
- Message GA749michaelmanagement.com
- Universal allocation in SAP S/4HANAblog.sap-press.com
- Message GA517erplingo.com
- KSWB: execute plan periodic repostingerplingo.com
- KSV4: delete actual distributionerplingo.com
- KSV6: actual distribution overviewerplingo.com
- KSUC: plan assessment overviewerplingo.com
- KB11N: manual repostings of costserplingo.com
- KB15N: manual allocationserplingo.com
- KK01: create statistical key figureerplingo.com
- KP46: plan statistical key figureserplingo.com
- 4KE5: PCA actual distributionerplingo.com
- KSU5 and related codessapstack.com
- KSU4 and related codessapstack.com
- KSW5 and KOW1sapstack.com
- Plan periodic reposting codessapstack.com
- Table T811Ctestingbrain.com
- Table T811Ktestingbrain.com
- Table T811DStestingbrain.com
- Table T811Sleanx.eu
- Creating an assessment cycledocsie.io