SAP HR_GB_TAXCODE Function Module for HCM GB: Tax Code formation
HR_GB_TAXCODE is a standard hr gb taxcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HCM GB: Tax Code formation processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for hr gb taxcode FM, simply by entering the name HR_GB_TAXCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: 0PGC
Program Name: SAPL0PGC
Main Program: SAPL0PGC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_GB_TAXCODE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'HR_GB_TAXCODE'"HCM GB: Tax Code formation.
EXPORTING
TXREG = "Regional code
TXNMB = "Text number
TXLET = "Tax indicator
BEGDA = "Start date of period tax code is checked
ENDDA = "End date of period tax code is checked
IMPORTING
TXCOD = "Tax Code
EXCEPTIONS
TAXCODE_ERROR = 1 PARTLY_INVALID_TXLET = 2
IMPORTING Parameters details for HR_GB_TAXCODE
TXREG - Regional code
Data type: P08_TXREGOptional: No
Call by Reference: Yes
TXNMB - Text number
Data type: P08_TXNMBOptional: No
Call by Reference: Yes
TXLET - Tax indicator
Data type: TXLETOptional: No
Call by Reference: Yes
BEGDA - Start date of period tax code is checked
Data type: BEGDAOptional: No
Call by Reference: Yes
ENDDA - End date of period tax code is checked
Data type: ENDDAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_GB_TAXCODE
TXCOD - Tax Code
Data type: P08_TXCODEOptional: No
Call by Reference: Yes
EXCEPTIONS details
TAXCODE_ERROR - Error status for tax code formation
Data type:Optional: No
Call by Reference: Yes
PARTLY_INVALID_TXLET - Tax letter not valid in part of period checked
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_GB_TAXCODE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_txcod | TYPE P08_TXCODE, " | |||
| lv_txreg | TYPE P08_TXREG, " | |||
| lv_taxcode_error | TYPE P08_TXREG, " | |||
| lv_txnmb | TYPE P08_TXNMB, " | |||
| lv_partly_invalid_txlet | TYPE P08_TXNMB, " | |||
| lv_txlet | TYPE TXLET, " | |||
| lv_begda | TYPE BEGDA, " | |||
| lv_endda | TYPE ENDDA. " |
|   CALL FUNCTION 'HR_GB_TAXCODE' "HCM GB: Tax Code formation |
| EXPORTING | ||
| TXREG | = lv_txreg | |
| TXNMB | = lv_txnmb | |
| TXLET | = lv_txlet | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| IMPORTING | ||
| TXCOD | = lv_txcod | |
| EXCEPTIONS | ||
| TAXCODE_ERROR = 1 | ||
| PARTLY_INVALID_TXLET = 2 | ||
| . " HR_GB_TAXCODE | ||
ABAP code using 7.40 inline data declarations to call FM HR_GB_TAXCODE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects