SAP ABI_DTL2URN_CONVERT Function Module for Obeolite: ABI_DTL2URN_Convert
ABI_DTL2URN_CONVERT is a standard abi dtl2urn convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obeolite: ABI_DTL2URN_Convert 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 abi dtl2urn convert FM, simply by entering the name ABI_DTL2URN_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ABI_EPCREF
Program Name: SAPLABI_EPCREF
Main Program: SAPLABI_EPCREF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ABI_DTL2URN_CONVERT 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 'ABI_DTL2URN_CONVERT'"Obeolite: ABI_DTL2URN_Convert.
EXPORTING
I_DTL = "
IMPORTING
E_URN = "sends back URN
E_HEADER_TEXT = "Character Field Length = 10
EXCEPTIONS
NO_VALID_HEADER = 1
IMPORTING Parameters details for ABI_DTL2URN_CONVERT
I_DTL -
Data type: AIDEPCDTLOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ABI_DTL2URN_CONVERT
E_URN - sends back URN
Data type: COptional: No
Call by Reference: Yes
E_HEADER_TEXT - Character Field Length = 10
Data type: CHAR10Optional: No
Call by Reference: Yes
EXCEPTIONS details
NO_VALID_HEADER - NO_VALID_HEADER
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ABI_DTL2URN_CONVERT 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_e_urn | TYPE C, " | |||
lv_i_dtl | TYPE AIDEPCDTL, " | |||
lv_no_valid_header | TYPE AIDEPCDTL, " | |||
lv_e_header_text | TYPE CHAR10. " |
  CALL FUNCTION 'ABI_DTL2URN_CONVERT' "Obeolite: ABI_DTL2URN_Convert |
EXPORTING | ||
I_DTL | = lv_i_dtl | |
IMPORTING | ||
E_URN | = lv_e_urn | |
E_HEADER_TEXT | = lv_e_header_text | |
EXCEPTIONS | ||
NO_VALID_HEADER = 1 | ||
. " ABI_DTL2URN_CONVERT |
ABAP code using 7.40 inline data declarations to call FM ABI_DTL2URN_CONVERT
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