Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PA-OS (Application Component) Organizational Structure⤷
PP0A (Package) HR-CA: ALE/IDOC Functionality
IMG Activity
| ID | OALE_HRDST_50 | Local validation for coding block |
| Transaction Code | S_AHR_61018747 | (empty) |
| Created on | 19990413 | |
| Customizing Attributes | OALE_HRDST_50 | Attributes of OALE_HRDST_50 |
| Customizing Activity | OALE_HRDST_50 | Maintenance Objects for OALE_HRDST_50 |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OALE_HRDST_50 |
If an HR System and AC System are both involved in a scenario, additional account assignments are usually validated synchronously in the AC System.
As an alternative, you can perform this step so that additional account assignments are validated locally in the HR System.
The local validation is to be regarded as more of an existence check. It is not possible to validate CO completely in the local validation since not all account assignment objects can be replicated in the HR system. For this reason, no other account assignment objects or properties for these objects can be derived, and no dependencies between account assignment objects can be checked. Complete validation can only be performed in the AC system since this is the only place where all account assignment objects exist. Therefore, if you want to ensure that the dependencies between account assignment objects are validated and additional information and properties of the entered objects are derived during the document entry, deactivate the local validation for these objects.
Also note that a complete CO validation is always performed when the document is forwarded to the AC system at the latest. Local validation is generally only performed when the document is entered.
Requirements
A scenario in which an HR and AC System are involved must be maintained.
Local validations are possible for account assignments (company code, business area, G/L account, cost center, and so on) that are entered in table TCOBFIELDS with an entry in the F_CHECK column.
Activities
- Use table TCOBFIELDS to determine which account assignments can be validated locally.
- Use the table included in this step to enter the account assignments for which local validation is required, and select the appropriate field. The company code and G/L account account assignments must always be entered.
Further notes
The system only performs local validations if all of the account assignments can be validated locally for each line item (that is, if they have all been entered here). If an account assignment cannot be validated, all of the account assignments for the line item in question are validated synchronously in the AC System.
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 | OALE_HRDST_50 | 0 | B200000068 | ALE Business Process Library |
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_TCOBALE | V - View | SM30 |
History
| Last changed by/on | SAP | 19990413 |
| SAP Release Created in |
