Note Page 1 of 5

SAP Note Number 178837

Number 178837
Version 0024
Processor -
Processing Status new
Impl. State Cannot be implemented
Language E
Short Text Availability control: Incorrect assigned value?
Component -

Long Text

Symptom
When you try to post costs to a budget object (internal order, WBS element or others), the system
displays an availability control warning or error message. The message states that the assigned value
exceeds the current budget (or the release).
Or:
If you post costs to a budget object (internal order, WBS element or others), the system should issue a
warning or error message. Availability control does not respond as you expect.

It is not clear how the system determined the assigned value displayed in the budget transaction (for
example CJ31, KO23).

Other Terms
Budget, assigned, available, tolerance limits, exceeded, release, supplement, reposting, return, original
budget, exempt cost element, anticipated, CJ30, CJ31, CJ32, CJ33, CJ34, CJ35, CJ36, CJ37, CJ38,
KO22, KO23, KO24, KO25, KO26, KO27, 12KST1A, PS report

Reason and Prerequisites

Availability control compares the current distributable budget (or release) with the assigned value.
Due to the complex business background and the individual settings in Customizing, the calculation
of the assigned value may be very difficult to reproduce.

Solution
You can display the assigned value relevant for active availability control in the budget transactions
(for example, CJ31, KO23: Views -> Assigned). (Caution: The assigned value that is displayed in the

saphtmlp://htmlviewer.sap.com/1gheAjjz7jYDocTPxGdU7W/HTML000001.htm 02-Apr-18
Note Page 2 of 5

cost reports (for example, 12KST1A) (passive availability control) very often does not match the
assigned value of the active availability control, because all costs are listed in the cost reports without
taking into account the logic of the active availability control, which is described below in more
detail. Only the assigned value that is displayed in the budget transactions is relevant for the active
availability control.)

The following explains in more detail the logic used to calculate the assigned value of the availability
control. You must also note the business scenario and the settings in Customizing. For the analysis,
you can use the programs BPFCTRA0 (Note 196149) for projects and BPFCTRA1 (Note 392730) for
orders. R/3 Enterprise allows you to perform the analysis from the budgeting transactions using
Extras > Availability control > Analysis.

1. Internal orders:

• Assigned value is calculated from:

◦ Actual costs and statistical actual costs

◦ Commitment (value types 21, 22), funds reservation (value type 2A), funds
precommitment (value type 2B), funds commitment (value type 24)

◦ Debit through settlement on the internal order

◦ Credit through settlement to an object with (actual or potential) budget control (WBS
element, orders, networks and network activities). (Note 159850)

◦ Parked documents (value type 60), as of Release 4.6B

• The following does not contribute to the assigned value:

◦ Actual costs with a cost element that was defined as an exempt cost element in
Customizing for availability control (transaction OPTK).

◦ Credits through settlement to a non-budget controlled object (for example, the cost
center). (Note 159850)

◦ Revenues

◦ Plan values

◦ Down payments (exception in statistical auxiliary account assingment to asset under

construction: Note 50785)

◦ Remark: One part of the SAP documentation suggests that postings are not used in the
assigned values if no tolerance limit is defined in Customizing for the availability control
for the relevant transaction group. However, this is not the case! You can use the
transaction groups to control the activities of the availability control if the budget has
been exceeded. However, the update of the assigned value cannot be influenced in this
way.

saphtmlp://htmlviewer.sap.com/1gheAjjz7jYDocTPxGdU7W/HTML000001.htm 02-Apr-18
Note Page 3 of 5

If the displayed assigned value does not correspond to this logic, then the assigned value is probably
incorrect. In this case, it may be helpful to reconstruct the availability control (transaction KO31). If
the problem occurs repeatedly or a reconstruction does not help, contact SAP Support.

2. Projects:

• The assigned value is calculated from:

◦ Actual costs and statistical actual costs on the WBS element in question

◦ Actual costs and statistical actual costs of subordinate WBS elements if these do not have
a budget, that is, if they do not have the status 'budgeted'.

◦ Commitment (value types 21, 22), funds reservation (value type 2A), funds
precommitment (value type 2B), funds commitment (value type 24) on the WBS element
in question

◦ Commitment (value types 21, 22), funds reservation (value type 2A), funds
precommitment (value type 2B), funds commitment (value type 24) of subordinate WBS
elements if they have no budget, that is to say if they do not have the status "budgeted"

◦ Residual order plan: Planned costs that exceed the total of actual costs and commitment
for assigned networks, network activities or orders. (The plan value "reserves" the budget
on the WBS element. Therefore this budget cannot be consumed by another network,
network activity, order or WBS element). The residual order plan is calculated depending
on the assigned network, network activity or order.
Here, the precise logic depends on the status of the assigned network, network activity or
order and on the Customizing settings. (You can find detailed information on this topic in
the Implementation Guide (IMG) "Define Order Value Updating": Project System->
Costs -> Planned costs -> Define Order Value Updating. See also Note 165085). In
summary:
With the status 'Released', the residual order plan is always included in the assigned
value. With the status 'Created', this applies only if the 'Assign Funds in Plan' indicator is
set (transaction OPSV) in Customizing for the network type or order type.
Exception: The residual order plan of networks or network activities that are used for
forecasts (see relevant indicator in the network type, transaction OPSC) is never included
in the assigned value.
With the status 'technically complete', 'complete' or 'deletion flag', the residual order plan
is never included in the assigned value.
The plan values of assigned networks are not taken into account for valuated project
stock.
If you set the availability control to validation against annual values, the values planned
at year level are taken into account provided there is no overall plan value.

◦ debit through settlements to the WBS element

◦ Credit through settlement to an object with (actual or potential) budget control (WBS
element, orders, networks and network activities). (Note 159850)

saphtmlp://htmlviewer.sap.com/1gheAjjz7jYDocTPxGdU7W/HTML000001.htm 02-Apr-18
Note Page 4 of 5

◦ Parked documents (value type 60), as of Release 4.6B

• The following does not contribute to the assigned value:

◦ Actual costs with a cost element that was defined as an exempt cost element in
Customizing for availability control (transaction OPTK).

Remark: If a cost element is assigned to a value category for which the 'Suppress'
indicator is set in PS Customizing, then the cost element is presumably included in the assigned value
of the availability control, but not in PS Customizing. This is because you should be able - within
availability control (using exempt cost elements) and within PS Reporting (using value categories
with the 'Suppress' indicator) - to define cost elements that should be ignored independently of one
another.
For information about this problem, see Note 777859.

◦ Credits through settlement to a non-budget controlled object (for example, the cost
center). (Note 159850)

◦ Credits of assigned production orders through delivery and debits through delivery of
production orders.

◦ Revenues

Remark: Depending on whether or not a cost element or revenue element is assigned to a

value category in PS Customizing, the value category settings determine whether it concerns costs or
revenues (see Customizing transaction OPI1).

◦ Plan values on WBS elements

◦ Plan values of attached orders to products of the sales order or project stock

◦ Funds commitment in the sales order or project stock (value type 11)

◦ Down payments (exception in statistical auxiliary account assignment to asset under

construction: Note 50785)

◦ Remark: One part of the SAP documentation suggests that postings are not used in the
assigned values if no tolerance limit is defined in Customizing for the availability control
for the relevant transaction group. However, this is not the case! You can use the
transaction groups to control the activities of the availability control if the budget has
been exceeded. However, the update of the assigned value cannot be influenced in this
way.

If the displayed assigned value does not correspond to this logic, then the assigned value is probably
incorrect. A reconstruction of availability control may be of help to you in this case (transaction
CJBN). If the problem occurs repeatedly or a reconstruction does not help, contact SAP Support.

saphtmlp://htmlviewer.sap.com/1gheAjjz7jYDocTPxGdU7W/HTML000001.htm 02-Apr-18
Note Page 5 of 5

Valid Releases

Links to Support Packages

Software Component Release Package Name

saphtmlp://htmlviewer.sap.com/1gheAjjz7jYDocTPxGdU7W/HTML000001.htm 02-Apr-18