178837 - Availability Control, Incorrect Assigned Value

8/16/2019 178837 - Availability Control, Incorrect Assigned Value

http://slidepdf.com/reader/full/178837-availability-control-incorrect-assigned-value 1/4

SAP Note

Header Data

Symptom

When you try to post costs to a budget object (internal order, WBS element or others), the systemdisplays an availability control warning or error message. The message states that the assignedvalue exceeds the current budget (or the release).Or:If you post costs to a budget object (internal order, WBS element or others), the system shouldissue 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 budgettransactions (for example, CJ31, KO23: Views -> Assigned). (Caution: The assigned value that isdisplayed in the cost reports (for example, 12KST1A) (passive availability control) very often doesnot match the assigned value of the active availability control, because all costs are listed in thecost reports without taking into account the logic of the active availability control, which isdescribed below in more detail. Only the assigned value that is displayed in the budget transactionsis relevant for the active availability control.)

The following explains in more detail the logic used to calculate the assigned value of theavailability control. You must also note the business scenario and the settings in Customizing. Forthe 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 budgetingtransactions using Extras > Availability control > Analysis.

1. Internal orders:

l 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 (WBSelement, orders, networks and network activities). (Note 159850)

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

l The following does not contribute to the assigned value:

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

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

178837 - Availability control: Incorrect assigned value?

Version 24 Validity: 24.09.2014 - active Language English

Released On 24.09.2014 09:45:36

Release Status Released for Customer

Component CO-OM-OPA-C Budgeting

PS-COS-BUD BudgetPriority Recommendations / Additional Info

Category Consulting

Other Components



(Note 159850)

¡ Revenues

¡ Plan values

¡ Down payments (exception in statistical auxiliary account assingment to asset underconstruction: Note 50785)

¡ Remark: One part of the SAP documentation suggests that postings are not used in theassigned values if no tolerance limit is defined in Customizing for the availability controlfor the relevant transaction group. However, this is not the case! You can use thetransaction groups to control the activities of the availability control if the budget hasbeen 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 isprobably 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 SAPSupport.

2. Projects:

l 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 abudget, 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 haveno 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 forassigned networks, network activities or orders. (The plan value "reserves" the budget onthe WBS element. Therefore this budget cannot be consumed by another network, networkactivity, order or WBS element). The residual order plan is calculated depending on theassigned network, network activity or order.Here, the precise logic depends on the status of the assigned network, network activity ororder and on the Customizing settings. (You can find detailed information on this topic inthe 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 assignedvalue. With the status 'Created', this applies only if the 'Assign Funds in Plan' indicatoris 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 forforecasts (see relevant indicator in the network type, transaction OPSC) is never includedin the assigned value.With the status 'technically complete', 'complete' or 'deletion flag', the residual orderplan 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 plannedat 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 (WBSelement, orders, networks and network activities). (Note 159850)

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

l The following does not contribute to the assigned value:

¡ Actual costs with a cost element that was defined as an exempt cost element in Customizingfor 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 theassigned value of the availability control, but not in PS Customizing. This is because you should beable - within availability control (using exempt cost elements) and within PS Reporting (using valuecategories with the 'Suppress' indicator) - to define cost elements that should be ignoredindependently 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 ofproduction orders.

¡ Revenues

Remark: Depending on whether or not a cost element or revenue element isassigned to a value category in PS Customizing, the value category settings determine whether itconcerns 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 underconstruction: Note 50785)

¡ Remark: One part of the SAP documentation suggests that postings are not used in theassigned values if no tolerance limit is defined in Customizing for the availability controlfor the relevant transaction group. However, this is not the case! You can use thetransaction 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 isprobably 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 SAPSupport.

Other Attributes

Validity

This document is not restricted to a software component or software component version

ReferencesThis document refers to:

SAP Notes

CJ30

CJ31

CJ32

CJ33

CJ34

CJ35

CJ36

CJ37

CJ38

CJBN

KO22

KO23

KO24

KO25

KO26

KO27

KO31

OPTK

1777489 Error from av. check for scheduling of network/maint. order

1424698 Budget overrun despite active availability control

1414563 Different assigned values in availability control/reporting

1118333 Assigned value for goods receipt in valuated project stock

821155 Projects: Value category customizing not taken into account

797046 Prevent GPDS/P entries from contributing to assigned values

793125 GPD: Availability Control with GPD

783161 Availability control check only if assigned value increases

668240 FAQ 2: Hierarchy reports 574187 Budget overrun in spite of error message

551506 FAQ note Overhead Cost Controlling

537416 Drilldown reporting: "Assigned" column in budget report

524498 PS-IS: Excluding network from assigned value

520717 Budget check in EBP

397799 INFORMATION: CO-OM-OPA (Order & Project Accounting)

392730 BPFCTRA1: analysis prgrm active availability control orders

Transaction codes



This document is referenced by:

SAP Notes (21)

352584 Composite note 'Applicatn-specifc special features'

320470 CJCO, KOCO: Which costs are used for the budget carryforward

319525 BPCARRYF:Analysis program budget carryforward - projects

196149 BPFCTRA0: Analysis program active availabil.control projects

166394 Tolerance limits of active availability control

574187 Budget overrun in spite of error message

551506 FAQ note Overhead Cost Controlling

797046 Prevent GPDS/P entries from contributing to assigned values

793125 GPD: Availability Control with GPD

537416 Drilldown reporting: "Assigned" column in budget report

783161 Availability control check only if assigned value increases

1118333 Assigned value for goods receipt in valuated project stock

668240 FAQ 2: Hierarchy reports

1414563 Different assigned values in availability control/reporting

524498 PS-IS: Excluding network from assigned value

520717 Budget check in EBP

1424698 Budget overrun despite active availability control

1777489 Error from av. check for scheduling of network/maint. order

821155 Projects: Value category customizing not taken into account

320470 CJCO, KOCO: Which costs are used for the budget carryforward

319525 BPCARRYF:Analysis program budget carryforward - projects 352584 Composite note 'Applicatn-specifc special features'

392730 BPFCTRA1: analysis prgrm active availability control orders

397799 INFORMATION: CO-OM-OPA (Order & Project Accounting)

166394 Tolerance limits of active availability control

196149 BPFCTRA0: Analysis program active availabil.control projects

Documents

178837 - Availability Control, Incorrect Assigned Value