Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
IS-PRS-LS (Application Component) Lean Staffing⤷
PSAWE_WE_BL (Package) Work Engagement Business-Layer
IMG Activity
| ID | SIMG_OLPR_CRSA | Create Service Attributes |
| Transaction Code | S_EE5_50000236 | (empty) |
| Created on | 20091008 | |
| Customizing Attributes | SIMG_OLPR_CRSA | Create Service Attributes |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OLPR_CRSA |
Use
Service attributes are customer-specific attributes that you can use to extend your record structure and reporting functions, and to define selected key fields.
Service attributes can be used in the following situations during the staffing and billing process:
- In staff assignments, service attributes are used to store additional information about assignments. The service attributes can be declared as key fields to create two otherwise identical assignments, for example, an 'onshore' and an 'offshore' assignment.
- Forecasting makes use of service attributes that are declared to be relevant for forecasting. For example, you can provide separate forecasts for onshore and offshore assignments.
- Time recording makes use of service attributes that are assigned to CATS fields. CATS entries are validated against the staff assignments that have the same service attributes (for example, the maximum number of days maintained in the onshore assignment must not be exceeded by the number of days recorded for onshore work).
- In Controlling, values maintained in transaction CATS are used to populate service attributes during the transfer/aggregation from CATS to CO (transaction code CAT7).
- In resource-related billing, service attributes are available as characteristics in the DIP profile.
- The SD credit/debit memo requests that result from the resource-related billing receive the service attributes. The service attributes are also available in the SD pricing interface and are copied into the subsequent SD billing documents. In the example, onshore and offshore work could be represented by separate items that are priced at different rates.
Requirements
Standard settings
Activities
SAP delivers CI_PRS_CPILS_1 and CI_PRS_CPILS_2 as includes. To physically generate an include in the DB, go to the relevant table, for example, CATSDB or COEP, and double click on the include. You can also create them using transaction SE11.
To define a service attribute, create a data element using transaction SE11 and use the data element to create an element in one or both customer includes CI_PRS_CPILS_1 and CI_PRS_CPILS_2. If the same element appears in both customer includes, it must be given the same name.
The service attributes in CI_PRS_CPILS_1 are relevant for steps 1-3 above. The service attributes in CI_PRS_CPILS_2 are relevant for steps 4-6 above. A service attribute is transferred from CATS to CO if it is contained in both customer includes. Note that service attributes in CI_PRS_CPILS_2 occupy more database space because they are stored in CO and SD tables that generally have a large number of entries.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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_CRSA | 0 | BTD0000182 | Lean Staffing |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20091125 |
| SAP Release Created in | 605 |
