SAP API_DOCUMENT_COPY_BOM Function Module for NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern









API_DOCUMENT_COPY_BOM is a standard api document copy 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 copy bom FM, simply by entering the name API_DOCUMENT_COPY_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_COPY_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_COPY_BOM'"NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern
  EXPORTING
   PF_DOKAR_SOURCE =  "Document Type
   PF_DOKNR_SOURCE =  "Document number
   PF_DOKTL_SOURCE =  "Document Part
   PF_DOKVR_SOURCE =  "Document Version
   PF_DOKAR_TARGET =  "Document Type
   PF_DOKNR_TARGET =  "Document number
   PF_DOKTL_TARGET =  "Document Part
   PF_DOKVR_TARGET =  "Document Version

EXCEPTIONS
   ERROR = 1    WARNING = 2
.



IMPORTING Parameters details for API_DOCUMENT_COPY_BOM

PF_DOKAR_SOURCE - Document Type

Data type: DRAW-DOKAR
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKNR_SOURCE - Document number

Data type: DRAW-DOKNR
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKTL_SOURCE - Document Part

Data type: DRAW-DOKTL
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKVR_SOURCE - Document Version

Data type: DRAW-DOKVR
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKAR_TARGET - Document Type

Data type: DRAW-DOKAR
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKNR_TARGET - Document number

Data type: DRAW-DOKNR
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKTL_TARGET - Document Part

Data type: DRAW-DOKTL
Optional: No
Call by Reference: No ( called with pass by value option)

PF_DOKVR_TARGET - Document Version

Data type: DRAW-DOKVR
Optional: 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)

WARNING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for API_DOCUMENT_COPY_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_source  TYPE DRAW-DOKAR, "   
lv_warning  TYPE DRAW, "   
lv_pf_doknr_source  TYPE DRAW-DOKNR, "   
lv_pf_doktl_source  TYPE DRAW-DOKTL, "   
lv_pf_dokvr_source  TYPE DRAW-DOKVR, "   
lv_pf_dokar_target  TYPE DRAW-DOKAR, "   
lv_pf_doknr_target  TYPE DRAW-DOKNR, "   
lv_pf_doktl_target  TYPE DRAW-DOKTL, "   
lv_pf_dokvr_target  TYPE DRAW-DOKVR. "   

  CALL FUNCTION 'API_DOCUMENT_COPY_BOM'  "NOTRANSL: Dokumentstruktur für Dokument anlegen/ändern
    EXPORTING
         PF_DOKAR_SOURCE = lv_pf_dokar_source
         PF_DOKNR_SOURCE = lv_pf_doknr_source
         PF_DOKTL_SOURCE = lv_pf_doktl_source
         PF_DOKVR_SOURCE = lv_pf_dokvr_source
         PF_DOKAR_TARGET = lv_pf_dokar_target
         PF_DOKNR_TARGET = lv_pf_doknr_target
         PF_DOKTL_TARGET = lv_pf_doktl_target
         PF_DOKVR_TARGET = lv_pf_dokvr_target
    EXCEPTIONS
        ERROR = 1
        WARNING = 2
. " API_DOCUMENT_COPY_BOM




ABAP code using 7.40 inline data declarations to call FM API_DOCUMENT_COPY_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_source).
 
 
"SELECT single DOKNR FROM DRAW INTO @DATA(ld_pf_doknr_source).
 
"SELECT single DOKTL FROM DRAW INTO @DATA(ld_pf_doktl_source).
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_pf_dokvr_source).
 
"SELECT single DOKAR FROM DRAW INTO @DATA(ld_pf_dokar_target).
 
"SELECT single DOKNR FROM DRAW INTO @DATA(ld_pf_doknr_target).
 
"SELECT single DOKTL FROM DRAW INTO @DATA(ld_pf_doktl_target).
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_pf_dokvr_target).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!