SAP API_DOCUMENT_READ_BOM Function Module for NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern
API_DOCUMENT_READ_BOM is a standard api document read bom SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern 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 api document read bom FM, simply by entering the name API_DOCUMENT_READ_BOM into the relevant SAP transaction such as SE37 or SE38.
Function Group: CVBAPI
Program Name: SAPLCVBAPI
Main Program: SAPLCVBAPI
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function API_DOCUMENT_READ_BOM 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 'API_DOCUMENT_READ_BOM'"NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern.
EXPORTING
PF_DOKAR = "
PF_DOKNR = "
PF_DOKTL = "
PF_DOKVR = "
* PF_DATUM = "Datum gültig ab
* PF_MULTILEVEL = 'X' "
TABLES
PT_DOC_BOM = "
PT_MESSAGES = "
EXCEPTIONS
ERROR = 1 NO_DATA_FOUND = 2 NO_AUTH = 3
IMPORTING Parameters details for API_DOCUMENT_READ_BOM
PF_DOKAR -
Data type: DRAW-DOKAROptional: No
Call by Reference: No ( called with pass by value option)
PF_DOKNR -
Data type: DRAW-DOKNROptional: No
Call by Reference: No ( called with pass by value option)
PF_DOKTL -
Data type: DRAW-DOKTLOptional: No
Call by Reference: No ( called with pass by value option)
PF_DOKVR -
Data type: DRAW-DOKVROptional: No
Call by Reference: No ( called with pass by value option)
PF_DATUM - Datum gültig ab
Data type: RC29L-DATUVOptional: Yes
Call by Reference: No ( called with pass by value option)
PF_MULTILEVEL -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for API_DOCUMENT_READ_BOM
PT_DOC_BOM -
Data type: STPOXOptional: No
Call by Reference: No ( called with pass by value option)
PT_MESSAGES -
Data type: MESSAGESOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_DATA_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTH -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for API_DOCUMENT_READ_BOM 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_pf_dokar | TYPE DRAW-DOKAR, " | |||
| lt_pt_doc_bom | TYPE STANDARD TABLE OF STPOX, " | |||
| lv_pf_doknr | TYPE DRAW-DOKNR, " | |||
| lt_pt_messages | TYPE STANDARD TABLE OF MESSAGES, " | |||
| lv_no_data_found | TYPE MESSAGES, " | |||
| lv_no_auth | TYPE MESSAGES, " | |||
| lv_pf_doktl | TYPE DRAW-DOKTL, " | |||
| lv_pf_dokvr | TYPE DRAW-DOKVR, " | |||
| lv_pf_datum | TYPE RC29L-DATUV, " | |||
| lv_pf_multilevel | TYPE RC29L. " 'X' |
|   CALL FUNCTION 'API_DOCUMENT_READ_BOM' "NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern |
| EXPORTING | ||
| PF_DOKAR | = lv_pf_dokar | |
| PF_DOKNR | = lv_pf_doknr | |
| PF_DOKTL | = lv_pf_doktl | |
| PF_DOKVR | = lv_pf_dokvr | |
| PF_DATUM | = lv_pf_datum | |
| PF_MULTILEVEL | = lv_pf_multilevel | |
| TABLES | ||
| PT_DOC_BOM | = lt_pt_doc_bom | |
| PT_MESSAGES | = lt_pt_messages | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| NO_DATA_FOUND = 2 | ||
| NO_AUTH = 3 | ||
| . " API_DOCUMENT_READ_BOM | ||
ABAP code using 7.40 inline data declarations to call FM API_DOCUMENT_READ_BOM
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.| "SELECT single DOKAR FROM DRAW INTO @DATA(ld_pf_dokar). | ||||
| "SELECT single DOKNR FROM DRAW INTO @DATA(ld_pf_doknr). | ||||
| "SELECT single DOKTL FROM DRAW INTO @DATA(ld_pf_doktl). | ||||
| "SELECT single DOKVR FROM DRAW INTO @DATA(ld_pf_dokvr). | ||||
| "SELECT single DATUV FROM RC29L INTO @DATA(ld_pf_datum). | ||||
| DATA(ld_pf_multilevel) | = 'X'. | |||
Search for further information about these or an SAP related objects