SAP OIH_J1B_CHECK_TXCOD_PURCHASE Function Module for Brazil: Check if the tax code is valid in the Purchase Order
OIH_J1B_CHECK_TXCOD_PURCHASE is a standard oih j1b check txcod purchase SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Brazil: Check if the tax code is valid in the Purchase Order 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 oih j1b check txcod purchase FM, simply by entering the name OIH_J1B_CHECK_TXCOD_PURCHASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIH_J1BR_01
Program Name: SAPLOIH_J1BR_01
Main Program: SAPLOIH_J1BR_01
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIH_J1B_CHECK_TXCOD_PURCHASE 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 'OIH_J1B_CHECK_TXCOD_PURCHASE'"Brazil: Check if the tax code is valid in the Purchase Order.
EXPORTING
ZEKPO = "EKPO structure
ZEKKO = "EKKO structure
* I_TAX_DATA = "US tax interface : Communication structure for tax calc.
* I_ACT_FLAG = "Activity category in SAP transaction
EXCEPTIONS
NOT_VALID = 1
IMPORTING Parameters details for OIH_J1B_CHECK_TXCOD_PURCHASE
ZEKPO - EKPO structure
Data type: EKPOOptional: No
Call by Reference: No ( called with pass by value option)
ZEKKO - EKKO structure
Data type: EKKOOptional: No
Call by Reference: No ( called with pass by value option)
I_TAX_DATA - US tax interface : Communication structure for tax calc.
Data type: COM_TAXOptional: Yes
Call by Reference: Yes
I_ACT_FLAG - Activity category in SAP transaction
Data type: AKTYPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_VALID - Tax code not valid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIH_J1B_CHECK_TXCOD_PURCHASE 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_zekpo | TYPE EKPO, " | |||
| lv_not_valid | TYPE EKPO, " | |||
| lv_zekko | TYPE EKKO, " | |||
| lv_i_tax_data | TYPE COM_TAX, " | |||
| lv_i_act_flag | TYPE AKTYP. " |
|   CALL FUNCTION 'OIH_J1B_CHECK_TXCOD_PURCHASE' "Brazil: Check if the tax code is valid in the Purchase Order |
| EXPORTING | ||
| ZEKPO | = lv_zekpo | |
| ZEKKO | = lv_zekko | |
| I_TAX_DATA | = lv_i_tax_data | |
| I_ACT_FLAG | = lv_i_act_flag | |
| EXCEPTIONS | ||
| NOT_VALID = 1 | ||
| . " OIH_J1B_CHECK_TXCOD_PURCHASE | ||
ABAP code using 7.40 inline data declarations to call FM OIH_J1B_CHECK_TXCOD_PURCHASE
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