Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI-GL-GL-SOA (Application Component) Provisions for Awards⤷
FI-SOA (Package) Stock Option Accounting
IMG Activity
| ID | ACE_SOP_HR_DAT_TRANS | Change Data During Transfer Using BAdI |
| Transaction Code | S_ALN_01000231 | (empty) |
| Created on | 20011125 | |
| Customizing Attributes | ACC_GL_SOA_K_K_A_152 | Stock Opt. Acc.: Optional Activtity, Critical, 152 |
| Customizing Activity | ACE_SOP_HR_DAT_TRANS | BAdI used to change data taken over from HR before saving |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FIGL_SOA_HRDATTRN_DC |
In this IMG activity, you can use the Business Add-In (BAdI) ACE_SOP_HR_DAT_TRANS to change or add to HR data during transfer to the Accounting system before is saved there. INCLUDE ACC_GL_ACE_BADI01 OBJECT DOKU ID TX LANGUAGE EN
^Information on the BAdI ACE_SOP_HR_DAT_TRANS
The BAdI uses the method MODIFY_ACCRUAL_ENGINE_DATA.
When transferring data from the HR system concerning awards that have been issued, the data is converted from HR format to a format in which the data can be stored in the Accounting system (in the Accrual Engine). The BAdI is called up separately for each waiting period for a granting of awards.
The BAdI provides you with information concerning an allocation in both HR format and in Accounting format:
In HR Format, the structures:
IS_AWARD_DATA
IS_GRANT_DATA
IS_VESTING_DATA
In Accounting (= Accrual Engine) format
CS_ACE_OBJECT_HEADER (Structure with header information concerning granting)
CT_ACE_OBJECT_ITEMS (Table with information concerning the waiting period)
CT_ACE_OBJECT_PARAMTERS (Table with other data that is required in Accounting)
Only the data in Accounting format can be modified in this BAdI.
This table can be evaluated by the accrual methods for calculating provisions. You can program the accrual methods yourself. The parameters can therefore be filled in accordance with the requirements of the accrual methods with regard to HR data and user-defined Customizing data.
The standard accrual methods use the entries in table CT_ACE_OBJECT_PARAMTERS. Entries in this table that were created in the system should only therefore be modified after serious consideration and comprehensive testing. If you use your own accrual methods for calculating provisions, you can of course change the entries created by the system as much as you like. You can always add new entries to the table: If you add fields to the table, you should also add them to the DDIC structure ACE_SOP_PARAMETERS. The customer include CI_SPECIFIC_PARAMS is provided for this purpose. You can then see the additional fields in the Accrual Engine and use them in Accrual Engine account determination. To use these fields in Accrual Engine account determination, you must have defined a DDIC structure with the fields in question in the Customer Settings for the Application Component in the Accrual Engine IMG.
CS_ACE_OBJECT_HEADER and CT_ACE_OBJECT_ITEMS, on the other hand, are used by system programs. You should only change this data in exceptional circumstances.
Data that is modified by the BAdI during data transfer is saved without checking in the Accounting system.
Business Attributes
| ASAP Roadmap ID | 152 | Design data acquisition |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020313 |
| SAP Release Created in | 110 |
