SAP BAPI_BUS2167_DOCUMT_UPDATE Function Module for BAPI Phase in Template: Change Assignment of Document or URL









BAPI_BUS2167_DOCUMT_UPDATE is a standard bapi bus2167 documt update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI Phase in Template: Change Assignment of Document or URL 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 bapi bus2167 documt update FM, simply by entering the name BAPI_BUS2167_DOCUMT_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DPR_BUS2167
Program Name: SAPLDPR_BUS2167
Main Program: SAPLDPR_BUS2167
Appliation area:
Release date: 20-Feb-2007
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_BUS2167_DOCUMT_UPDATE 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 'BAPI_BUS2167_DOCUMT_UPDATE'"BAPI Phase in Template: Change Assignment of Document or URL
  EXPORTING
   PHASE_TMPL_GUID =  "GUID for Phase in Template in BAPI Interface
   IV_DOCUMENT_GUID =  "GUID for Document in BAPI Interface
*  IV_MIMETYPE =  "Mime Type of Document to Be Assigned
*  IV_SAVE_AS_URL =  "Store Document to Be Assigned as URL
*  IV_NEW_VERSION =  "Change Document Assignment (EDMS): New Version

TABLES
*  IT_URL =  "BAPI UPDATE: URL Portion of URL to Be Used
*  IT_FILE_CONTENT =  "RAW Portion of Length 255 for File Content of a Document
*  RETURN =  "Return Parameter Table
.



IMPORTING Parameters details for BAPI_BUS2167_DOCUMT_UPDATE

PHASE_TMPL_GUID - GUID for Phase in Template in BAPI Interface

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

IV_DOCUMENT_GUID - GUID for Document in BAPI Interface

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

IV_MIMETYPE - Mime Type of Document to Be Assigned

Data type: BAPI_TS_DOCUMENT_ADD-MIMETYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SAVE_AS_URL - Store Document to Be Assigned as URL

Data type: BAPI_TS_DOCUMENT_ADD-SAVE_AS_URL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NEW_VERSION - Change Document Assignment (EDMS): New Version

Data type: BAPI_TS_DOCUMENT_ADD-NEW_VERSION
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_BUS2167_DOCUMT_UPDATE

IT_URL - BAPI UPDATE: URL Portion of URL to Be Used

Data type: BAPI_TS_URL
Optional: Yes
Call by Reference: Yes

IT_FILE_CONTENT - RAW Portion of Length 255 for File Content of a Document

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

RETURN - Return Parameter Table

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

Copy and paste ABAP code example for BAPI_BUS2167_DOCUMT_UPDATE 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:
lt_it_url  TYPE STANDARD TABLE OF BAPI_TS_URL, "   
lv_phase_tmpl_guid  TYPE BAPI_TS_GUID-PHASE_TEMPLATE_GUID, "   
lt_it_file_content  TYPE STANDARD TABLE OF BAPI_TS_RAW_CONTAINER, "   
lv_iv_document_guid  TYPE BAPI_TS_GUID-DOCUMENT_GUID, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_mimetype  TYPE BAPI_TS_DOCUMENT_ADD-MIMETYPE, "   
lv_iv_save_as_url  TYPE BAPI_TS_DOCUMENT_ADD-SAVE_AS_URL, "   
lv_iv_new_version  TYPE BAPI_TS_DOCUMENT_ADD-NEW_VERSION. "   

  CALL FUNCTION 'BAPI_BUS2167_DOCUMT_UPDATE'  "BAPI Phase in Template: Change Assignment of Document or URL
    EXPORTING
         PHASE_TMPL_GUID = lv_phase_tmpl_guid
         IV_DOCUMENT_GUID = lv_iv_document_guid
         IV_MIMETYPE = lv_iv_mimetype
         IV_SAVE_AS_URL = lv_iv_save_as_url
         IV_NEW_VERSION = lv_iv_new_version
    TABLES
         IT_URL = lt_it_url
         IT_FILE_CONTENT = lt_it_file_content
         RETURN = lt_return
. " BAPI_BUS2167_DOCUMT_UPDATE




ABAP code using 7.40 inline data declarations to call FM BAPI_BUS2167_DOCUMT_UPDATE

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 PHASE_TEMPLATE_GUID FROM BAPI_TS_GUID INTO @DATA(ld_phase_tmpl_guid).
 
 
"SELECT single DOCUMENT_GUID FROM BAPI_TS_GUID INTO @DATA(ld_iv_document_guid).
 
 
"SELECT single MIMETYPE FROM BAPI_TS_DOCUMENT_ADD INTO @DATA(ld_iv_mimetype).
 
"SELECT single SAVE_AS_URL FROM BAPI_TS_DOCUMENT_ADD INTO @DATA(ld_iv_save_as_url).
 
"SELECT single NEW_VERSION FROM BAPI_TS_DOCUMENT_ADD INTO @DATA(ld_iv_new_version).
 


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!