SAP DOCB_DOCUMENT_SAVE Function Module for Save Document

Search SAP Function Modules

DOCB_DOCUMENT_SAVE is a standard docb document save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save Document 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 docb document save FM, simply by entering the name DOCB_DOCUMENT_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /IPRO/BUSINESS_OBJECT
Program Name: /IPRO/SAPLBUSINESS_OBJECT
Main Program: /IPRO/SAPLBUSINESS_OBJECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DOCB_DOCUMENT_SAVE 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 'DOCB_DOCUMENT_SAVE'"Save Document
  EXPORTING
   PIV_DOC_BINARY =  "The WML
   PIV_DOC_XML =  "XML representing the document data
*  PIT_AUTH_USERS =  "Authorized users
*  PIT_AUTH_ORGS =  "Authorized organizations
   PIV_ACTION =  "3-Byte field
*  PIT_REVIEWERS =  "WF reviewers
*  PIT_APPROVERS =  "WF Approvers

 IMPORTING
   PEV_DOC_ID =  "Globally Unique Identifier
   PET_MESSAGE =  "Return Parameter

CHANGING
   PCV_DOCHDR =  "Document Details

.

IMPORTING Parameters details for DOCB_DOCUMENT_SAVE

PIV_DOC_BINARY - The WML

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

PIV_DOC_XML - XML representing the document data

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

PIT_AUTH_USERS - Authorized users

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

PIT_AUTH_ORGS - Authorized organizations

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

PIV_ACTION - 3-Byte field

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

PIT_REVIEWERS - WF reviewers

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

PIT_APPROVERS - WF Approvers

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

EXPORTING Parameters details for DOCB_DOCUMENT_SAVE

PEV_DOC_ID - Globally Unique Identifier

Data type: /IPRO/TDOCMNT-DOCMNT
Optional: No
Call by Reference: No ( called with pass by value option)

PET_MESSAGE - Return Parameter

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

CHANGING Parameters details for DOCB_DOCUMENT_SAVE

PCV_DOCHDR - Document Details

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

Copy and paste ABAP code example for DOCB_DOCUMENT_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM DOCB_DOCUMENT_SAVE

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