Hierarchy
BBPCRM (Software Component) BBPCRM⤷
PS-IS-REP-ACC (Application Component) Accounting⤷
KAP0 (Package) RPSCO recording and infrastructure for this
Basic Data
| Data Element | TCJO1PLAN |
| Short Description | Order values for orders in planning phase |
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 | Plan |
| Medium | 15 | Plan |
| Long | 20 | Plan |
| Heading | 0 |
Documentation
Definition
In the Project System, you can assign orders/networks to WBS elements. The costs planned or posted in the orders/networks represent funds commitments against the budget of the WBS element in question. In the standard, the assigned amount for a combination of:
- order category
- order type
- controlling area, and
- system status
is dependent on the order phase, according to the following rule:
Example:
System status Order phase ,Indicator
Plan Rlsd Clsd Deleted ,Appended
Created ,X
Released X
Closed ,X
Deleted ,X
Order phase "Planning":
Plan value (=order request commitment) represents funds commitment.
From the point of view of project controlling, a project order in the planning phase represents an internal purchase requisition. In the same way as a purchase requisition generates the purchase requisition commitment, the order plan value is included in availability control, and displayed in the information system, as an order request commitment.
Order phase "Released" (Execution):
From the point of view of project controlling, a project order in the planning phase represents an internal purchase order. In the same way as a purchase order generates the purchase order commitment, the order plan value is included in availability control, and displayed in the information system, as an order commitment.
If you change the order phase from "Created" to "Released" (that is, from planning to execution), the order request commitment is reduced, and the order commitment correspondingly increased.
If actual costs and commitments arise in the order, due to purchase requisitions and purchase orders, the order commitment is determined as follows:
Plan value for an order network in the "Released phase"
- actual costs
- commitment from purchase requisitions and purchase orders
----------------------------------------------------------
Order commitmment, or remaining plan value
- Remaining plan value (=order commitment) > actual + commitment -> Plan value represents funds commitment
- If the remaining plan value for the orders is more than the total of actual plus "external" commitments (the commitments in the order arising from purchase requisitions/orders), the remaining plan value is subject to availability control.
- Remaining plan value < actual + commitment -> actual + commitment represents funds commitments
- If the actual + commitment total is more than the remaining plan value, this value is reset to zero and the actual + commitment total is valued as the funds commitment.
Order phase "Closed": actual + commitment represents funds commitment
From this phase, the plan value of the order for the project is no longer relevant to project controlling.
Order phase "Deleted": Actual + commitment represents funds commitment
In exception circumstances, you can change this rule.
Appended order plan values
You can use the "Appended" indicator to determine how the plan values for the order 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 WBS element. The total is displayed in the information system as the project plan.
- "Appended indicator" not set
The plan values for the order are not added to the plan value for the WBS element.
History
| Last changed by/on | SAP | 19950606 |
| SAP Release Created in |
