SAP IDMX_DI_SD_DATA_EXTRACT Function Module for Generate Extract for SD digital invoice
IDMX_DI_SD_DATA_EXTRACT is a standard idmx di sd data extract SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate Extract for SD digital invoice 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 idmx di sd data extract FM, simply by entering the name IDMX_DI_SD_DATA_EXTRACT into the relevant SAP transaction such as SE37 or SE38.
Function Group: IDMX_DI_SIGNATURE
Program Name: SAPLIDMX_DI_SIGNATURE
Main Program: SAPLIDMX_DI_SIGNATURE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function IDMX_DI_SD_DATA_EXTRACT 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 'IDMX_DI_SD_DATA_EXTRACT'"Generate Extract for SD digital invoice.
EXPORTING
IS_XVBRK = "Reference Structure for XVBRK/YVBRP
IT_XVBRP = "Billing Item Data
IT_XKOMV = "Table for structure KOMV
IT_XVBPA = "Table for structure VBPAVB
* IV_TEXT_READ_FLAG = ' ' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IV_TEXT_BADI_FLAG = ' ' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING
ES_DATA_EXTRACT = "Digital invoice Mexico: data for Original input message
EV_STRING_ADDENDA = "
EV_STRING_HEADER_COMPL_XML = "
ET_ITEM_COMPL_XML = "Supplement Text of Line Items
ET_XVBRP_REF = "Billing Item Data
EV_STRING_CUSTOMS = "Customs Data for Reporting
EV_REQUEST_CERTIFICATE = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for IDMX_DI_SD_DATA_EXTRACT
IS_XVBRK - Reference Structure for XVBRK/YVBRP
Data type: VBRKVBOptional: No
Call by Reference: Yes
IT_XVBRP - Billing Item Data
Data type: VBRPVB_TOptional: No
Call by Reference: Yes
IT_XKOMV - Table for structure KOMV
Data type: VA_KOMV_TOptional: No
Call by Reference: Yes
IT_XVBPA - Table for structure VBPAVB
Data type: VA_VBPAVB_TOptional: No
Call by Reference: Yes
IV_TEXT_READ_FLAG - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ' '
Optional: No
Call by Reference: Yes
IV_TEXT_BADI_FLAG - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ' '
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for IDMX_DI_SD_DATA_EXTRACT
ES_DATA_EXTRACT - Digital invoice Mexico: data for Original input message
Data type: IDMX_DI_ORI_IN_MSG_TYPEOptional: No
Call by Reference: Yes
EV_STRING_ADDENDA -
Data type: STRINGOptional: No
Call by Reference: Yes
EV_STRING_HEADER_COMPL_XML -
Data type: STRINGOptional: No
Call by Reference: Yes
ET_ITEM_COMPL_XML - Supplement Text of Line Items
Data type: IDMX_DI_T_ITEM_COMPLEMENTOOptional: No
Call by Reference: Yes
ET_XVBRP_REF - Billing Item Data
Data type: VBRPVB_TOptional: No
Call by Reference: Yes
EV_STRING_CUSTOMS - Customs Data for Reporting
Data type: STRINGOptional: No
Call by Reference: Yes
EV_REQUEST_CERTIFICATE - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error occured
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IDMX_DI_SD_DATA_EXTRACT 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_error | TYPE STRING, " | |||
lv_is_xvbrk | TYPE VBRKVB, " | |||
lv_es_data_extract | TYPE IDMX_DI_ORI_IN_MSG_TYPE, " | |||
lv_it_xvbrp | TYPE VBRPVB_T, " | |||
lv_ev_string_addenda | TYPE STRING, " | |||
lv_it_xkomv | TYPE VA_KOMV_T, " | |||
lv_ev_string_header_compl_xml | TYPE STRING, " | |||
lv_it_xvbpa | TYPE VA_VBPAVB_T, " | |||
lv_et_item_compl_xml | TYPE IDMX_DI_T_ITEM_COMPLEMENTO, " | |||
lv_et_xvbrp_ref | TYPE VBRPVB_T, " | |||
lv_iv_text_read_flag | TYPE BOOLE_D, " ' ' | |||
lv_ev_string_customs | TYPE STRING, " | |||
lv_iv_text_badi_flag | TYPE BOOLE_D, " ' ' | |||
lv_ev_request_certificate | TYPE BOOLE_D. " |
  CALL FUNCTION 'IDMX_DI_SD_DATA_EXTRACT' "Generate Extract for SD digital invoice |
EXPORTING | ||
IS_XVBRK | = lv_is_xvbrk | |
IT_XVBRP | = lv_it_xvbrp | |
IT_XKOMV | = lv_it_xkomv | |
IT_XVBPA | = lv_it_xvbpa | |
IV_TEXT_READ_FLAG | = lv_iv_text_read_flag | |
IV_TEXT_BADI_FLAG | = lv_iv_text_badi_flag | |
IMPORTING | ||
ES_DATA_EXTRACT | = lv_es_data_extract | |
EV_STRING_ADDENDA | = lv_ev_string_addenda | |
EV_STRING_HEADER_COMPL_XML | = lv_ev_string_header_compl_xml | |
ET_ITEM_COMPL_XML | = lv_et_item_compl_xml | |
ET_XVBRP_REF | = lv_et_xvbrp_ref | |
EV_STRING_CUSTOMS | = lv_ev_string_customs | |
EV_REQUEST_CERTIFICATE | = lv_ev_request_certificate | |
EXCEPTIONS | ||
ERROR = 1 | ||
. " IDMX_DI_SD_DATA_EXTRACT |
ABAP code using 7.40 inline data declarations to call FM IDMX_DI_SD_DATA_EXTRACT
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.DATA(ld_iv_text_read_flag) | = ' '. | |||
DATA(ld_iv_text_badi_flag) | = ' '. | |||
Search for further information about these or an SAP related objects