Diese Seite (Version-37) wurde zuletzt am 08-Okt.-2025 10:06 von Administrator geändert.

Diese Seite wurde am 05-Okt.-2020 15:48 von Administrator erstellt.

Du bist nicht autorisiert, diese Seite umzubenennen.

Du bist nicht autorisiert, diese Seite zu löschen.

Versionsgeschichte der Seite

Version Zuletzt geändert Größe Autor Änderungen Kommentar
37 08-Okt.-2025 10:06 6 KB Administrator zur vorherigen
36 08-Okt.-2025 09:26 6 KB Administrator zur vorherigen | zur neuesten
35 08-Okt.-2025 09:24 6 KB Administrator zur vorherigen | zur neuesten
34 28-Aug.-2025 13:16 5 KB Administrator zur vorherigen | zur neuesten
33 31-März-2025 11:37 5 KB Administrator zur vorherigen | zur neuesten
32 31-März-2025 11:36 5 KB Administrator zur vorherigen | zur neuesten
31 31-März-2025 11:36 5 KB Administrator zur vorherigen | zur neuesten
30 31-März-2025 11:35 5 KB Administrator zur vorherigen | zur neuesten
29 05-März-2025 15:03 4 KB Administrator zur vorherigen | zur neuesten
28 05-März-2025 14:41 4 KB Administrator zur vorherigen | zur neuesten
27 05-März-2025 14:13 4 KB Administrator zur vorherigen | zur neuesten
26 05-März-2025 14:09 4 KB Administrator zur vorherigen | zur neuesten
25 05-März-2025 14:08 4 KB Administrator zur vorherigen | zur neuesten
24 05-März-2025 14:06 4 KB Administrator zur vorherigen | zur neuesten
23 05-März-2025 14:05 4 KB Administrator zur vorherigen | zur neuesten
22 05-März-2025 13:18 4 KB Administrator zur vorherigen | zur neuesten
21 05-März-2025 12:59 4 KB Administrator zur vorherigen | zur neuesten

Links

Eingehende Links Ausgehende Links
Infotypes
Infotypes

Versionsunterschiede

Unterschiede zwischen Version und .

Zeile 5: 5 Zeilen geändert.
!! New / Decoupled Infotype Framwork
* x.SFW5, [note 0001641394|https://me.sap.com/notes/0001641394]
* business logic is implemented ABAP objects classes instead of module pool, see [blog1|https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/de-coupled-versus-non-de-coupled-infotype-framework/ba-p/13302129], [blog2|https://community.sap.com/t5/enterprise-resource-planning-q-a/how-to-migrate-a-standard-infotype-to-decouple/qaq-p/12710421]
* SPro > Personnel Management > Personnel Administration > Customizing Procedures > Infotypes > Infotypes in Detached Infotype Framework > Use Decoupled and Not Decoupled
* classes see V_T582ITVCLAS
!! New / Decoupled Infotype Framwork (DCIF)
* business logic is implemented ABAP objects classes instead of module pool, see [blog1|https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/de-coupled-versus-non-de-coupled-infotype-framework/ba-p/13302129], [blog2|https://community.sap.com/t5/enterprise-resource-planning-q-a/how-to-migrate-a-standard-infotype-to-decouple/qaq-p/12710421], [info1|https://learnhrabap.blogspot.com/2009/03/decoupled-infotype.html], [ABAP example|https://www.sapdev.eu/hcm-modify-infotype-data-with-decoupled-framework/]
Zeile 8: 19 Zeilen hinzugefügt.
* SPro > Personnel Management > Personnel Administration > Customizing Procedures > Infotypes > Infotypes in Detached Infotype Framework > ...
* general setup in table V_T582ITVCLAS, conversion in T588UICONVCLAS
* you can enable to use BOTH via SPro > Personnel Management > Personnel Administration > Customizing Procedures > Infotypes > Infotypes in Detached Infotype Framework > Use Decoupled and Not Decoupled (T77S0 CCURE/PC_UI=X)
* Access class CL_HRPA_INFOTYPE_nnnn based on interface IF_HRPA_INFTY_BL
* conversion classes:
** CL_HRPA_UI_CONVERT_nnnn_yy (Country specific)
** CL_HRPA_UI_CONVERT_nnnn_XX (International)
* screen structure HCMT_BSP_PA_yy_Rnnnn or ZHCMT_BSP_PA_yy_R9nnn (custom)
* SAP recommends using the DCIF for any new custom infotype development
!Relation between new and old (classes and modulpool)
Example IT0001 > MP000100 > MPPERS00 > MODULE init_dialog OUTPUT. > PERFORM set_newitf(sapfp50m) > sets variable PSPAR-newITF = 'X',\\
if T77SO group CCURE and one of following switches are activated (checked at CL_HRCE_MASTERSWITCHES->CLASS_CONSTRUCTOR)
* MAINS - ce_is_active / Concurrent Employment Main Switch
* GLOPY - global_payroll_is_active / Payroll: Global Employee
* GLEMP - mngmt_global_empls_is_active / Management of Global Employees
and the infotype is enabled at T582ITVCLAS-NITF_ADM \\
and at SAPFP50M > FP50ME10 > FORM infotype_admissible_for_newitf > you see IT 0, 1, 3, 31, 200n always run in the old framework always.
Zeile 12: Eine Zeile geändert.
T77S0 CCURE/PC_UI is set to 'X', [note 1447867|https://me.sap.com/notes/1447867]
Use Decoupled AND Not Decoupled via T77S0 CCURE/PC_UI is set to 'X', [note 1447867|https://me.sap.com/notes/1447867]
Zeile 38: 43 Zeilen hinzugefügt.
!! Infotype screens
!How to find screen for a molga
# x.PE03 > feature P0002 > Molga 01 = 1234
# T588M > repna = *<infotype>*, VarKey = <feature Pxxxx> => ADYNR = screen
!Infotype field properties (mandatory, readonly, unused etc.)
see [SAP docu|https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/c6c3ffd90792427a9fee1a19df5b0925/869ee2539c70424de10000000a174cb4.html]
||Table||View||Comment
|T588M|T588M|this is for the dynpro screen (old logic)
|T588MFPROPS|V_T588MFPROPS|this is for DCIF, seems to be aligned with T588M
|T588MFPROPC|V_T588MFPROPC|this is for DCIF the "custom" one, overriding T588MFPROPS if not set FIXED there
You should make sure that all three are in sync ! \\
For DCIF the PA0003-VIEKN/MOLGA is used as variable key, see also CL_HR_T588MFPROP. \\
Fields marked as UNUSED (also in T588MFPROPC) are automatically deleted on updates with DCIF with warning "PBAS_SERVICE/067: Changes to field "FOA key", which is not designed for use, are deleted"
!How to find mandatory fields
# SM30 > T588M > double click infotype >
PA0003-VIEKN (=MOLGA) > feature IVWID
|T777D|Infotypes - Dialog/Database Assignment
|T588M|Infotype Screen Control
|T582A|Infotypes: Customer-Specific Settings
|T582S|Infotype Texts
|T588A|Transaction Codes
|T500P|Personnel Areas (relation to MOLGA)
|T500L|Personnel Country Grouping (MOLGA)
|T001p|Personnel Area/Subarea
|T582V|Assignment of Infotypes to Views
|T582C|Include Screens for Infotypes
Debug at
{{{
CL_HRPA_INFOTYPE_0002
> CL_HRPA_INFTY_NNNN->IF_HRPA_INFTY_BL~INSERT( )
f.HR_COUNTRYGROUPING_GET
}}}
!! Shared infotypes
If one person has multiple PERNRs some infotypes like 2,6 and 9 can be shared (same content for all PERNRs), but you can disable grouping, see note [3027575|https://me.sap.com/notes/3027575/E].\\
SAP recommendation for multiple employment is to use "infotype sharing", see [docu|https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYROLL/185f14fbe60d4bbb8d7d5e4f8d89b24b/290f6f83d57e492782b44aaf01cb737d.html]
!! Old Infotype Logic
Diese Seite (Version-37) wurde zuletzt am 08-Okt.-2025 10:06 von Administrator geändert.Top