SAP AIN_EPC_URI_TO_EPC Function Module for Convert URI Format to EPC
AIN_EPC_URI_TO_EPC is a standard ain epc uri to epc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert URI Format to EPC 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 ain epc uri to epc FM, simply by entering the name AIN_EPC_URI_TO_EPC into the relevant SAP transaction such as SE37 or SE38.
Function Group: AIN_EPC_CONVERT
Program Name: SAPLAIN_EPC_CONVERT
Main Program: SAPLAIN_EPC_CONVERT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function AIN_EPC_URI_TO_EPC 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 'AIN_EPC_URI_TO_EPC'"Convert URI Format to EPC.
EXPORTING
IT_URI = "Electronic Product Code
IMPORTING
ET_EPC_DETAIL = "Tabletype: EPC
ET_RET_MSG = "Table with BAPI Return Information
IMPORTING Parameters details for AIN_EPC_URI_TO_EPC
IT_URI - Electronic Product Code
Data type: AIN_EPC_URI_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for AIN_EPC_URI_TO_EPC
ET_EPC_DETAIL - Tabletype: EPC
Data type: AIN_EPC_DTL_TABOptional: No
Call by Reference: Yes
ET_RET_MSG - Table with BAPI Return Information
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for AIN_EPC_URI_TO_EPC 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_it_uri | TYPE AIN_EPC_URI_TAB, " | |||
lv_et_epc_detail | TYPE AIN_EPC_DTL_TAB, " | |||
lv_et_ret_msg | TYPE BAPIRET2_T. " |
  CALL FUNCTION 'AIN_EPC_URI_TO_EPC' "Convert URI Format to EPC |
EXPORTING | ||
IT_URI | = lv_it_uri | |
IMPORTING | ||
ET_EPC_DETAIL | = lv_et_epc_detail | |
ET_RET_MSG | = lv_et_ret_msg | |
. " AIN_EPC_URI_TO_EPC |
ABAP code using 7.40 inline data declarations to call FM AIN_EPC_URI_TO_EPC
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