PC2GA SAP (Payroll results: Garnishment order) Structure details
Description: Payroll results: Garnishment order
Structure field list including key, data, relationships and ABAP select examples
PC2GA 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 "Payroll results: Garnishment order" 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_PC2GA TYPE PC2GA.
The PC2GA table consists of various fields, each holding specific information or linking keys about Payroll results: Garnishment order data available in SAP. These include JURIS (Code for jurisdiction), GCATE (Code for Garnishment Category), DFPRI (Priority of Order for Garnishment), GFCOD (Service Charge Rule).. 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: Cannot Be Enhanced
SAP PC2GA 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 |
IONUM | Case Number (Internal) for Garnishment Order | P_IONUMR | NUMC | 4 | |||||
JURIS | Code for jurisdiction | P_JURISD | CHAR | 4 | Assigned to domain | P_JURISD | |||
GCATE | Code for Garnishment Category | P_GCATG | CHAR | 1 | |||||
DFPRI | Priority of Order for Garnishment | P_DFPRO | NUMC | 3 | |||||
GFCOD | Service Charge Rule | P_GFCODE | CHAR | 3 | Assigned to domain | P_GFCODE | |||
ORDDA | Date when garnishment order is read | P_GRNORDDAG | DATS | 8 | DATUM | ||||
PAYTY | Payroll type | PAYTY | CHAR | 1 | PAYTY | ||||
PERMO | Period Parameters | PERMO | NUMC | 2 | Assigned to domain | PERMO | |||
PABRD | Payroll date for garnishment | P_GRNPABRDG | DATS | 8 | DATUM | ||||
LABRD | Last payroll date for garnishment | P_GRNLABRDG | DATS | 8 | DATUM | ||||
PABRP | Payroll Period | PABRP | NUMC | 2 | PABRP | ||||
PABRJ | Payroll Year | PABRJ | NUMC | 4 | GJAHR | GJAHR | |||
ZEINH | Payroll time units | PFREQ | NUMC | 2 | PFREQ | ||||
CMONT | Calendar month for garnishment payroll | P_GRNCMONTG | NUMC | 2 | PABRP | ||||
CYEAR | Calendar year for garnishment payroll | P_GRNCYEARG | NUMC | 4 | GJAHR | GJAHR | |||
BABRP | Begin date of payroll period for garnishment payroll | P_GRNBABRPG | DATS | 8 | DATUM | ||||
EABRP | End date of payroll period for garnishment payroll | P_GRNEABRPG | DATS | 8 | DATUM | ||||
NPPYA | Number of pay periods per year as they actually occur | P_GRNNPPYAG | INT1 | 3 | |||||
DATMO | Date modifier | DATMO | NUMC | 2 | Assigned to domain | DATMO | |||
CRETY | HR payee type | CRETY | CHAR | 1 | CRETY | CRETY | |||
CRENR | HR payee number | CRENR | NUMC | 8 | Assigned to domain | CRENR | CRENR | ||
LIFNR1 | Vendor | P_LIFNRG | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
LIFNR2 | Vendor | P_LIFNRG | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
LIFNR3 | Vendor | P_LIFNRG | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
LIFSG1 | Vendor subgroup | ACSUB | NUMC | 5 | NUMC5 | ACSUB | |||
LIFSG2 | Vendor subgroup | ACSUB | NUMC | 5 | NUMC5 | ACSUB | |||
LIFSG3 | Vendor subgroup | ACSUB | NUMC | 5 | NUMC5 | ACSUB | |||
RULNR | Remittance Rule | P_IOREMG | NUMC | 5 | Assigned to domain | RULNR | |||
EMFTX1 | Payee Text | EMFTX | CHAR | 40 | TEXT40 | ||||
EMFTX2 | Payee Text | EMFTX | CHAR | 40 | TEXT40 | ||||
EMFTX3 | Payee Text | EMFTX | CHAR | 40 | TEXT40 | ||||
PRITY1 | Transfer Priority | P_PRITY | CHAR | 1 | TEXT1 | ||||
PRITY2 | Transfer Priority | P_PRITY | CHAR | 1 | TEXT1 | ||||
PRITY3 | Transfer Priority | P_PRITY | CHAR | 1 | TEXT1 | ||||
BANKN1 | Bank account number | BANKN | CHAR | 18 | BANKN | ||||
BANKN2 | Bank account number | BANKN | CHAR | 18 | BANKN | ||||
BANKN3 | Bank account number | BANKN | CHAR | 18 | BANKN | ||||
ZLSCH1 | Payment Method | PCODE | CHAR | 1 | Assigned to domain | ZLSCH | |||
ZLSCH2 | Payment Method | PCODE | CHAR | 1 | Assigned to domain | ZLSCH | |||
ZLSCH3 | Payment Method | PCODE | CHAR | 1 | Assigned to domain | ZLSCH | |||
IOSCI | Single cheque indicator | P_IOSCIG | CHAR | 1 | XFLAG | ||||
IOSRT | Garnishment order sort date | P_IOSRTG | DATS | 8 | DATUM | ||||
IOSTS | Garnishment Order Status | P_IOSTS | CHAR | 1 | P_IOSTS | ||||
IOSHT | Hour for prioritising orders of garnishment | P_IOSHT | TIMS | 6 |
Key field | Non-key field |
How do I retrieve data from SAP structure PC2GA using ABAP code?
As PC2GA 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 PC2GA as there is no data to select.How to access SAP table PC2GA
Within an ECC or HANA version of SAP you can also view further information about PC2GA 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