HCMT_BSP_PA_CA_R0066 SAP (Dynpro Infotyp 0066) Structure details
Description: Dynpro Infotyp 0066
Related tables to HCMT_BSP_PA_CA_R0066
Access table HCMT_BSP_PA_CA_R0066
Structure field list including key, data, relationships and ABAP select examples
HCMT_BSP_PA_CA_R0066 is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Dynpro Infotyp 0066" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_HCMT_BSP_PA_CA_R0066 TYPE HCMT_BSP_PA_CA_R0066.
The HCMT_BSP_PA_CA_R0066 table consists of various fields, each holding specific information or linking keys about Dynpro Infotyp 0066 data available in SAP. These include PERNR (Personnel Number), AEDTM (Changed On), UNAME (Name of Person Who Changed Object), SPRPS (Lock Indicator for HR Master Data Record).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP HCMT_BSP_PA_CA_R0066 structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| OBJECT_KEY | HCM Object Key | HCM_OBJECT_KEY | CHAR | 100 | |||||
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| AEDTM | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| UNAME | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| SPRPS | Lock Indicator for HR Master Data Record | SPRPS | CHAR | 1 | SPRPS | ||||
| SPRTX | Lock indicator for HR master record (text) | SPRPSTEXT | CHAR | 40 | SPRPSTEXT | ||||
| ITBLD | Infotype Screen Control | ITBLD | CHAR | 2 | CHAR2 | ||||
| BEGDA | Valid-From Date | PAD_BEGDA | DATS | 8 | DATUM | ||||
| ENDDA | Valid To Date | PAD_ENDDA | DATS | 8 | DATUM | ||||
| IOCN1 | Case number | PCA_IOCN1 | CHAR | 25 | PCA_IOCN1 | ||||
| IOCN2 | Case file number | PCA_IOCN2 | CHAR | 25 | PCA_IOCN1 | ||||
| IONUM | Internal order number | P07_UI_IONUM | NUMC | 4 | P_IONUM | ||||
| IOSTS | Garnishment order status | PCA_IOSTS | CHAR | 1 | PCA_IOSTS | ||||
| IORCD | Received date | PCA_IORCD | DATS | 8 | DATUM | ||||
| PREAS | Reason for Changing Master Data | PREAS | CHAR | 2 | T530E | PREAS | |||
| IOCTD | Court order date | PCA_IOCTD | DATS | 8 | DATUM | ||||
| JURIS | Code for jurisdiction | P_JURIS | CHAR | 4 | T52G0 | P_JURIS | |||
| IORLD | Release date | PCA_IORLD | DATS | 8 | DATUM | ||||
| GCATE | Code for category | P_GCATE | CHAR | 1 | T52G2 | P_GCATE | |||
| IOPRI | Order priority | P_IOPRI | NUMC | 3 | P_IOPRI | ||||
| LIFNR | Vendor | P_LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
| AGCOD | Code for agency | P_AGCOD | CHAR | 1 | T52G4 | P_AGCOD | |||
| NAME | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| IOANM | Agency name | PCA_IOANM | CHAR | 40 | TEXT40 | ||||
| STREET | House number and street | STRAS_GP | CHAR | 35 | TEXT35 | ||||
| IOAST | Agency street | PCA_IOAST | CHAR | 35 | TEXT35 | ||||
| CITY | City | ORT01_GP | CHAR | 35 | TEXT35 | ||||
| IOACI | Agency city | PCA_IOACI | CHAR | 35 | TEXT35 | ||||
| POSTL_CODE | Postal Code | PSTLZ | CHAR | 10 | PSTLZ | ||||
| REGION | Province | P07_UI_REGIO | CHAR | 3 | T005S | REGIO | |||
| COUNTRY | Country Key | LAND1_GP | CHAR | 3 | T005 | LAND1 | C_LAND1 | ||
| IOAPC | Agency postal code | PCA_IOAPC | CHAR | 10 | PSTLZ | ||||
| IOAPR | Agency province | PCA_IOAPR | CHAR | 3 | T005S | REGIO | |||
| IOACO | Agency country | PCA_IOACO | CHAR | 3 | T005 | LAND1 | |||
| IOAPH | Agency phone number | PCA_IOAPH | CHAR | 16 | TEXT16 | ||||
| IOPLN | Plaintiff | PCA_IOPLN | CHAR | 40 | TEXT40 | ||||
| IOCOL | Correspondence language | PCA_IOCOL | LANG | 1 | T002 | ISOLA | SPRAS | ||
| IOPAY | Make cheque payable to plantiff | P07_UI_IOPAY | CHAR | 1 | XFELD | ||||
| GFCOD | Garnishee fee rule | P07_UI_GFCOD | CHAR | 1 | T52GI | P_GFCOD | |||
| GFTXT | Description of garnishee fee rule | P_GFTXT | CHAR | 40 | P_GATXT | ||||
| IOSCI | Single cheque indicator | P07_UI_IOSCI | CHAR | 1 | XFLAG | ||||
| IOGFA | Garnishee fee | PCA_IOGFA | CURR | 9(2) | PCA_GFCUR | ||||
| WAE01 | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
| GFUNT | Garnishee fee unit text | PCA_GFUTX | CHAR | 60 | AS4TEXT | ||||
| RULNR | Remittance rule | P07_UI_IOREM | NUMC | 5 | T51RK | RULNR | |||
| INFTY | Infotype | INFTY | CHAR | 4 | INFOTYP | ITP | |||
| MOLGA | Country Grouping | MOLGA | CHAR | 2 | Assigned to domain | MOLGA | MOL |
| Key field | Non-key field |
How do I retrieve data from SAP structure HCMT_BSP_PA_CA_R0066 using ABAP code?
As HCMT_BSP_PA_CA_R0066 is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on HCMT_BSP_PA_CA_R0066 as there is no data to select.How to access SAP table HCMT_BSP_PA_CA_R0066
Within an ECC or HANA version of SAP you can also view further information about HCMT_BSP_PA_CA_R0066 and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects