Hierarchy

⤷

⤷

IMG Activity
ID | PRS_DEF_CATEGORIES | Define Categories |
Transaction Code | S_E38_98000113 | (empty) |
Created on | 20070817 | |
Customizing Attributes | PRS_DEF_CATEGORIES | Define Categories |
Customizing Activity | PRS_DEF_CATEGORIES | Define Categories |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PRS_DEF_CATEGORIES |
Use
You can use this IMG activity to define categories. Categories are used in billing request editor to combine items of similar nature together so that same rules are applied to these items. For example, different materials used in DMR to differentiate between junior consultant and senior consultant are grouped together in one category time.
Requirements
Standard settings
Activities
Create new categories
- Enter the key for the category
- Enter the description
- Assign each category to a usage
Each category is assigned to one usage. The following rules apply:
- Categories for DMR lines originally created in resource related billing are mapped to 00030 Original
- Categories for different accrual types created in Accrual screen are mapped to usage 00040 Accrual
- Categories used in Bill screen are mapped according to usage 50 to 62
- Mark categories as changeable or not. Changeable means that the value of the related DMR lines can be changed in value screen. Typical examples for non changeable categories would be category for on-account
- For accrual categories the option exists to maintain a second Category ID. This would be used to group different categories together. Example would be that you want to group time entries and accrual for time together in value screen. To do this you have to create two categories, one for time and one for accrual time. To allow the accrual time to be grouped together with time, you have to maintain on accrual time a second category ID (here= time)
- Flag category for relevance of Unit of Measure. If a category is relevant for unit of measure, certain transaction can be done based on qty, if not the transactions can only be performed based on value or percentage. Example on time unit of measure is relevant (days or hours) and it makes sense to postpone 10 h, but on expense entries UoM is normally not relevant
- For accruals maintain the relevant UoM (This ensures that the right UoM is either defaulted or that the user is restricted to the listed UoM)
- Save the new category.
Note
Categories are subsequently used to group materials found in DMR together. Here you will normally have a mapping of n materials to one grouping. On the other side they are used to find the materials used by the billing request editor to create additional DMR lines. Here one category needs to be mapped to one material. Therefore for these type of categories the number of necessary materials to update DMR need to be determined first (for example based on reporting and taxation requirements) and then they determine the number of required categories.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory 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 | PRS_DEF_CATEGORIES | 0 | HLA0100736 | Expense-Related Billing |
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 |
PRSVC_CAT | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20080328 |
SAP Release Created in | 603 |