SAP ABAP IMG Activity PBC_FTE_0410 (Define Error Category)
Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   PA-PM-PB (Application Component) Position Budgeting and Control
     PAOC_FPM_FTE_CUSTOMIZING (Package) Position Management: Customizing FTEs
IMG Activity
ID PBC_FTE_0410 Define Error Category  
Transaction Code S_ALN_01002206   (empty) 
Created on 20030408    
Customizing Attributes PBC_FTE_0010   General Settings 
Customizing Activity PBC_FTE_0410   Define Error Category 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PBC_FTE_0410    

Use

Financing rules form the relationship between budget structure elements and the positions/person from the perspective of pay scale classification. Since this relationship can have multiple forms, there are a number of IMG activities in Customizing for Position Budgeting and Control in which you can define financing rules.

If you want rule infringements to be reported in categories, you must use error categories. If the error categories delivered by SAP in the standard system do not meet your requirements, you can define your own error categories in this IMG activity.

The system reports infringements of financing rules in multiple views for personnel budget plan editing and in the report Check Financing Rules. When you work with error categories, infringements are displayed in the relevant category, and otherwise in the category "not categorized".

You can use error codes to assign rule infringements and the corresponding messages to a specific category. When you create an error code, you assign an error category to it. The advantage of using error codes is that you only have to define the error code as the return value in the implementation. This ensures that a given rule infringement always triggers the same error message. Alternatively, you can store the error category directly in the BAdI implementation for checking financing rules. You can find more information about error codes in the documentation for the IMG activity Define Error Codes.

Requirements

To map financing rules that can be checked by the system, you must implement the Business Add-In (BAdI) for checking financing rules when a budget structure element is staffed by a position/person. For more information about this, see BAdI: Check of Financing Rules.

Standard settings

The standard system contains the following categories:

Category    Meaning

A    Other classification

E    Staffed accordingly

F    Incorrectly staffed

U    Under classified

N    Not staffed

X    Not categorized

Activities

To define your own error categories:

  1. Enter a code with a maximum of 8 characters starting with Y or Z.
  2. Enter a descriptive text.
  3. To ensure that the error category appears in the check report and in the relevant views for personnel budget plan editing:
    1. Define your own column. To do this, switch to the IMG activity Define Own Columns and copy the column PBC_ASSCTG_A.
    2. Assign the new column to the existing column groups PBC_CHK_OV (for view Check Financing Rules (summarized)) and PBC_CHK_OV_EXT (for report Check Financing Rules) and PBC_CHK_OV_FLAT (for view Check of Financing Rules (not summarized). You do this in the IMG activity Adjust Existing Column Groups.
    3. You must now create an append structure for the report Check Financing Rules in the structure HRFPM_S_FIN_CHK_ALV_ERR_CATG. The append structure must contain a field with the same name as the column key. Define this field with reference to the data type HRFPM_FTE_TEXT.

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 
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_HRFPM_ERRCATG V - View SM30  
History
Last changed by/on SAP  20031120 
SAP Release Created in 200