Ansicht
Dokumentation
OHIX_DECOUPLED_ITFW - Configure Infotypes for HR Master Data Maintenance
PERFORM Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
HR master data maintenance (PA30) was enhanced so that it supports the new decoupled infotypes as well as the infotypes that are not decoupled.
- If an infotype is completely decoupled (all existing infotype versions are decoupled) and the permitted in all circumstances indicator is set for the infotype in the Assign Check Classes and Define Permissibility IMG activity, it is also decoupled in HR master data maintenance.
- If however, the permitted in certain circumstances indicator is set for the infotype because some but not all infotype versions are decoupled, the system responds as follows:
- The infotype versions that are not decoupled run on the old technology
- The decoupled infotype versions run on either the old or new technology, depending on the configuration
Infotypes that have the impermissible indicator set, or that do not have an entry in the Assign Check Classes and Define Permissibility IMG activity always run on the old technology.
For an overview of the various configurations, see the "System Response for Infotypes in HR Master Data Maintenance" section.
As with HR master data maintenance, the decoupled infotype framework also has BAdIs or enhancement spots. For applications that directly use the decoupled infotype framework (such as Employee Self-Services and HR Administrative Services), only the new enhancement spots are accessed. If you have implemented the old BAdIs or enhancements (enhancement PBAS0001 with the exits EXIT_SAPFP50M_001 and EXIT_SAPFP50M_002 and/or BAdI HRPAD00INFTY) and want the infotype to behave in the same way in the new applications, you must also implement the new enhancement spots of the decoupled infotype framework. (For information about the old enhancements, see Define Enhancements for Information Types.)
The decoupled infotype framework provides the following enhancement spots:
- Enhancement spot HRPAD00INFTYBL
- Contains the HRPAD00INFTYBL BAdI with the same name for enhancing the business logic of standard infotypes and the HRPAD00INFTYDB BAdI for performing actions after updating.
- For more information, see Business Logic Enhancements and Updating.
- Enhancement spot HRPAD00INFTYUI
- Contains the HRPAD00INFTYUI BAdI with the same name for enhancing the UI logic of standard infotypes.
- For more information, see UI Logic Enhancements.
As described above, in HR master data maintenance, depending on infotype configuration and global switch settings, there are different configurations. This also effects accessing the BAdIs.
The following overview documents the different system response, depending on the infotype configuration and the activation of the decoupled infotype framework.
- Active/Not Active
- The decoupled infotype framework is Active if functions in the Concurrent Employment, Management of Global Employees, orPayroll for Global Employees areas are activated. In all other cases, the decoupled infotype framework is formally Not Active, even if parts of it are still accessed.
- Infotype Checks
- Under "Infotype Checks" the system specifies whether the check class methods (decoupled check logic) are run for the infotype in the respective configuration, or whether validation takes place using the old technology in the module pools.
- Updating
- "Updating" specifies whether the system writes to the database using the old infotype framework or the decoupled infotype framework.
- Exits/Methods
- The system specifies the exits and methods of the old and new BAdIs that are accessed in the respective configuration.
- Infotypes that have the not permitted indicator set in the Assign Check Class and Define Permissibility IMG activity and infotypes that are not enter there.
| Decoupled Infotype Framework: | Not Active |
|---|
| Infotype checks | Module pool |
| Updating | Old infotype framework (SAPFP50P/SAPUP50R) |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods BEFORE_OUTPUT and AFTER_INPUT |
| BAdI - Updater | HRPAD00INFTY - Method IN_UPDATE |
| Decoupled Infotype Framework: | Active |
|---|
| Infotype checks | Module pool |
| Updating | Old infotype framework (SAPFP50P/SAPUP50R) |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods BEFORE_OUTPUT and AFTER_INPUT |
| BAdI - Updater | HRPAD00INFTY - Method IN_UPDATE |
- Infotypes that have the permitted in all circumstances indicator set
| Decoupled Infotype Framework: | Not Active |
|---|
| Infotype checks | Check class |
| Updating | Old infotype framework (SAPFP50P/SAPUP50R) |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods BEFORE_OUTPUT and AFTER_INPUT and HRPAD00INFTYBL - Method depending on infotype operation |
| BAdI - Updater | HRPAD00INFTY - IN_UPDATE |
| Decoupled Infotype Framework: | Active |
|---|
| Infotype checks | Check class |
| Updating | Decoupled infotype framework |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods BEFORE_OUTPUT and AFTER_INPUT and HRPAD00INFTYBL - Method depending on infotype operation |
| BAdI - Updater | HRPAD00INFTYDB - Method DB_UPDATE |
- Country version of infotypes that have the permitted in some circumstances indicator set and that have an entry in the Assign Dialog Modules for HR Master Data Maintenance IMG activity
| Decoupled Infotype Framework: | Not Active |
|---|
| Infotype checks | Module pool |
| Updating | Old infotype framework (SAPFP50P/SAPUP50R) |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods BEFORE_OUTPUT and AFTER_INPUT |
| BAdI - Updater | HRPAD00INFTY - IN_UPDATE |
| Decoupled Infotype Framework: | Active |
|---|
| Infotype checks | Check class |
| Updating | Decoupled infotype framework |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods BEFORE_OUTPUT and AFTER_INPUT and HRPAD00INFTYBL - Method depending on infotype operation |
| BAdI - Updater | HRPAD00INFTYDB - Method DB_UPDATE |
- Country version of infotypes that have the permitted in some circumstances indicator set and that have no entry in the Assign Dialog Modules for HR Master Data Maintenance IMG activity:
| Decoupled Infotype Framework: | Not Active |
|---|
| Infotype checks | Module pool |
| Updating | Old infotype framework (SAPFP50P/SAPUP50R) |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods: BEFORE_OUTPUT / AFTER_INPUT |
| BAdI - Updater | HRPAD00INFTY - IN_UPDATE |
| Decoupled Infotype Framework: | Active |
|---|
| Infotype checks | Module pool |
| Updating | Old infotype framework (SAPFP50P/SAPUP50R) |
| Enhancement PBAS0001 | EXIT_SAPFP50M_001 (PBO) and EXIT_SAPFP50M_002 (PAI) |
| BAdI - Infotype maintenance | HRPAD00INFTY - Methods: BEFORE_OUTPUT / AFTER_INPUT |
| BAdI - Updater | HRPAD00INFTY - IN_UPDATE |
If the decoupled infotype framework is not active (in the sense mentioned above), in certain circumstances it may be necessary to use both the infotype framework that is not decoupled and the decoupled infotype framework. For detailed information and for how to proceed, see Using the IT Framework That Is Not Decoupled and the Decoupled IT Framework.
rdisp/max_wprun_time - Maximum work process run time rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 13245 Date: 20240524 Time: 011731 sap01-206 ( 128 ms )
