Hierarchy
⤷ PS-IS-REP-ACC (Application Component) Accounting
⤷ KAP0 (Package) RPSCO recording and infrastructure for this
Basic Data
Data Element | TCJO1ABGL |
Short Description | Order value for closed orders |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Closed |
Medium | 15 | Closed |
Long | 20 | Closed |
Heading | 0 |
Documentation
Definition
In the Project System, you can assign orders/networks to WBS elements. The costs planned or posted in these orders/networks then represent assignments against the budget for the relevant WBS element. In the standard system, the amount assigned for a combination of
- order category
- order type
- controlling area, and
- system status
depends on the order phase, according to the following rule:
Example:
System status, order phase Indicator
Plan Reld Clsd Deltd ,Appended
Opened X
Released X
Closed ,X
Deleted ,X
Order phase "Planning":
The plan value (order request commitment) represents a funds commitment.
From the point of view of project controlling, an order for a project in the planning phase represents an internal purchase requisition. In the same way as the purchase requisition value generates a purchase requisition commitment, the plan value for the order is regarded as an order request commitment, and, as such, is subject to availability control and displayed in the information system.
Order phase "Released" (Execution):
An order for the project in this phase represents an eine internal purchase order, whose value is regarded as an order commitment, and, as such, is subject to availability control and displayed in the information system.
If you change the phase of an order for the project from "Created" to "Released" (that is, from planning to execution), the system reduces the order request commitment and sets up an order commitment accordingly.
If the order incurs actual costs and commitments from purchase requisitions and purchase orders, the order commitment is calculated as follows:
,Plan value from order/network in the "Released" phase
- Actual costs
- Commitment from purchase requisitions and purchase orders
----------------------------------------------------------
Order commitment or remaining plan
- Remaining plan value (=order commitment)> actual + commitment -> remaining plan vlaue is subject to availability control.
- If the remaining plan value for the order is greater than the total for actual costs and "external" commitments (that is, the commitments arising from purchase requisitions and purchase orders on the order), the remaining plan value is subject to availability control.
- If the total of actual and commitment values is greater than the remaining plan value, it is this total which is included in availability control.
Order phase "Closed": Actual + commitment represents funds commitment
From this phase onward, the plan value of an order for the project is no longer relevant for project controlling.
Order phase "Deleted": Actual + commitment represents funds commitment
In exceptional cases, you can change this rule.
Appended order plan values.
In addition, you can use the "Appended" indicator to control how the order plan values flow into the plan value for the relevant WBS element.
- "Appended" indicator set
The plan value for the order increases the plan value for the project.
The total is displayed in the information system as the project plan.
- "Appended" indicator not set
The plan value for the order is not added to the WBS element plan value.
History
Last changed by/on | SAP | 19950606 |
SAP Release Created in |