Decoupled Infotype

What is this?
This is OOPS way of creating/maintaining infotypes.

What is 'decoupled' here?
Business Logic of the infotype and the user interface code are separated now.

Can you explain?
In the earlier method, the code for application/logic and code for the UI screen are in a same ABAP program. (Module pool). Now using OOPS we have a new framework, which separates Application logic and UI logic. We have separate set of classes which carry the code for validation, default values etc.

What about future?
Any new infotypes you create, automatically get created using the 'Decoupled' technology. SAP Also provides IMG tools to migrate an existing (standard or custom) infotype into 'Decoupled' framework.

Whats the use of decoupled infotypes?
Newer applications such as some ESS scenarios, HR Admin services are supported only for decoupled infotypes. That means you need to migrate these infotypes, if you need to use them in some ESS applicaitons.
Maintaining infotypes using PA30 (or PA20) is not effected by this. Both technologies are supported.

What is the advantage compared to old technology?
-> New controls, new graphic elements, visual patterns etc.
-> Improves performance for Batch data input.

I am not an 'OOPS' ABAPer. So tell me technically what has been changed?


-> Two new structures are defined. These are specific to screens.
1. HCMT_BSP_PA_yy_Rnnnn (Country specific infotypes)
2. HCMT_BSP_PA_XX_Rnnnn (International infotypes)
3. ZHCMT_BSP_PA_yy_R9nnn (Custom Country specific infotypes)
4. ZHCMT_BSP_PA_XX_R9NNN (Custom International infotypes)
Contains all PSnnnn fields and additional fields to be displayed in infotype screen.

-> Conversion Class
These are the interfaces between screen logic and application logic. It does following tasks.
1. Conversion of screen fields and providing them in a structure to the backend program.
2. Conversion of backend structure given by program into front end screen fields.
3. Setting screen (control) attributes to the screen fields.

Naming convention for conversion class
CL_HRPA_UI_CONVERT_nnnn_yy (Country specific)
CL_HRPA_UI_CONVERT_nnnn_XX (International)

Conversion classes are Infotype Specific and Country Specific. They are assigned in table V_T588UICONVCLAS

-> Check Classes
Business Logic Goes here (Validations and default values). This class has several standard methods, and custom methods also can be added here.
Check Classes are coded manually.

Entry in table V_T582ITVCLAS for the classes to determine version IDs and Infoptye containers
Naming Convention for check class:
CL_HRPA_INFOTYPE_nnnn.
ZCL_HRPA_INFOTYPE_nnnn.

Check classes for different versions are assigned in table V_T582ITVCHCK