Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
CNPC (Package) R/3 Customizing PP Project Management
IMG Activity
| ID | SIMG_OLPR_OPSV1 | Define Order Value Updating for Orders for Projects |
| Transaction Code | S_ALR_87005443 | IMG Activity: SIMG_OLPR_OPSV1 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_OLPR_OPSV1 | Define Order Value Updating |
| Customizing Activity | SIMG_OLPR_OPSV1 | Define Order Value Updating |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OLPR_OPSV1 |
In this step, you stipulate how the system records the planned costs for orders assigned to projects.
Orders can be apportioned or appended.
- Apportioned order update
The plan value of the order is added to the committed value of the corresponding WBS element.
- Appended order update
The plan value of the order is added to the plan value of the corresponding WBS element.
As a rule, the following applies:
- Orders for project with status "released" are always apportioned.
- Orders for project with status "technically complete", "closed", or "deleted" are never apportioned.
You can specify with the appended indicator how the plan values of the order are included in the planning value of the respective WBS element for combinations of the following:
- Order category
- Order type
- Controlling area
The following applies to the indicators:
- "Appended" indicator set
The plan value of the order is added to the plan value of the WBS element. The total is displayed as the project plan value in the information system.
- "Appended" indicator not set
The plan value of the order is not added to the plan value of the WBS element.
- "Commitment in plan" indicator set
The plan value of the order is added to the committed value of the WBS element as soon as the order has status "created".
- "Commitment in plan" indicator not set
The plan value of the order is added to the committed value of the WBS element only once the order has status "released".
Exception:
Plan values from networks used for planning are not added to the committed value of the WBS element. The network type specifies whether a network is used for planning.
Additional information about network type
SAP Default Settings
- All networks with network type 20 are appended.
- All orders with status "created" have the "commitment in plan" indicator set.
Further notes
- Only planned costs from appended orders are taken into account in project summarization.
- If you change the object indicator later, you will have to reconstruct the project information database if plan data already exists. This is necessary to avoid data inconsistencies.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_OLPR_OPSV1 | 0 | (HLA0001567 A HLA0006677 A HLA0009554) O HLA0001420 O HLA0001496 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TCJO1 | V - View | OPSV | 01 | Object Indicator for Order Value |
History
| Last changed by/on | SAP | 19990121 |
| SAP Release Created in |
