SAP CV_BI_DOC_CREATE_BATCH_INPUT Function Module for Create document info record via batch input









CV_BI_DOC_CREATE_BATCH_INPUT is a standard cv bi doc create batch input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create document info record via batch input 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 cv bi doc create batch input FM, simply by entering the name CV_BI_DOC_CREATE_BATCH_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function CV_BI_DOC_CREATE_BATCH_INPUT 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 'CV_BI_DOC_CREATE_BATCH_INPUT'"Create document info record via batch input
  EXPORTING
*  BDC_FLAG = ' ' "
*  CLOSE_GROUP = ' ' "Indicator: close session
   DOCUMENT_DATA =  "Document data
   GROUP_DATA =  "Session data
*  NEW_GROUP = ' ' "Indicator: open new session
*  TCODE_MODE = 'N' "Processing mode for CALL TRANSACTION USING
*  TCODE_UPDATE = 'A' "Synchronous or asynchronous update

 IMPORTING
   MSGID =  "Message ID
   MSGNO =  "Message number
   MSGTY =  "Message type
   MSGV1 =  "Message variable 1
   MSGV2 =  "Message variable 2
   MSGV3 =  "Message variable 3
   MSGV4 =  "Message variable 4

TABLES
   DOC_CHAR_VALUES =  "Characteristic value records
   DOC_CLASSIFICATIONS =  "Document classification records
   DOC_DESCRIPTIVE_TEXTS =  "Document descriptions
   DOC_LONG_TEXTS =  "Document long texts
   DOC_OBJECT_RELATIONS =  "Document object links
*  DOC_ADDITIONAL_FILES1 =  "
*  DOC_ADDITIONAL_FILES2 =  "
.



IMPORTING Parameters details for CV_BI_DOC_CREATE_BATCH_INPUT

BDC_FLAG -

Data type: MCDOK-ACTION
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLOSE_GROUP - Indicator: close session

Data type: MCDOK-ACTION
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCUMENT_DATA - Document data

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

GROUP_DATA - Session data

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

NEW_GROUP - Indicator: open new session

Data type: MCDOK-ACTION
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCODE_MODE - Processing mode for CALL TRANSACTION USING

Data type: MCDOK-ACTION
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCODE_UPDATE - Synchronous or asynchronous update

Data type: MCDOK-ACTION
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CV_BI_DOC_CREATE_BATCH_INPUT

MSGID - Message ID

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

MSGNO - Message number

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

MSGTY - Message type

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

MSGV1 - Message variable 1

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

MSGV2 - Message variable 2

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

MSGV3 - Message variable 3

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

MSGV4 - Message variable 4

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

TABLES Parameters details for CV_BI_DOC_CREATE_BATCH_INPUT

DOC_CHAR_VALUES - Characteristic value records

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

DOC_CLASSIFICATIONS - Document classification records

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

DOC_DESCRIPTIVE_TEXTS - Document descriptions

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

DOC_LONG_TEXTS - Document long texts

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

DOC_OBJECT_RELATIONS - Document object links

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

DOC_ADDITIONAL_FILES1 -

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

DOC_ADDITIONAL_FILES2 -

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

Copy and paste ABAP code example for CV_BI_DOC_CREATE_BATCH_INPUT 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_msgid  TYPE SY-MSGID, "   
lv_bdc_flag  TYPE MCDOK-ACTION, "   SPACE
lt_doc_char_values  TYPE STANDARD TABLE OF BIAUSP, "   
lv_msgno  TYPE SY-MSGNO, "   
lv_close_group  TYPE MCDOK-ACTION, "   SPACE
lt_doc_classifications  TYPE STANDARD TABLE OF BIKSSK, "   
lv_msgty  TYPE SY-MSGTY, "   
lv_document_data  TYPE DRAW_BI, "   
lt_doc_descriptive_texts  TYPE STANDARD TABLE OF DRAT_BI, "   
lv_msgv1  TYPE SY-MSGV1, "   
lv_group_data  TYPE BGR00, "   
lt_doc_long_texts  TYPE STANDARD TABLE OF LTEXT_BI, "   
lv_msgv2  TYPE SY-MSGV2, "   
lv_new_group  TYPE MCDOK-ACTION, "   SPACE
lt_doc_object_relations  TYPE STANDARD TABLE OF DRAD_BI, "   
lv_msgv3  TYPE SY-MSGV3, "   
lv_tcode_mode  TYPE MCDOK-ACTION, "   'N'
lt_doc_additional_files1  TYPE STANDARD TABLE OF DRAZ_BI, "   
lv_msgv4  TYPE SY-MSGV4, "   
lv_tcode_update  TYPE MCDOK-ACTION, "   'A'
lt_doc_additional_files2  TYPE STANDARD TABLE OF DRAZ_BI. "   

  CALL FUNCTION 'CV_BI_DOC_CREATE_BATCH_INPUT'  "Create document info record via batch input
    EXPORTING
         BDC_FLAG = lv_bdc_flag
         CLOSE_GROUP = lv_close_group
         DOCUMENT_DATA = lv_document_data
         GROUP_DATA = lv_group_data
         NEW_GROUP = lv_new_group
         TCODE_MODE = lv_tcode_mode
         TCODE_UPDATE = lv_tcode_update
    IMPORTING
         MSGID = lv_msgid
         MSGNO = lv_msgno
         MSGTY = lv_msgty
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
    TABLES
         DOC_CHAR_VALUES = lt_doc_char_values
         DOC_CLASSIFICATIONS = lt_doc_classifications
         DOC_DESCRIPTIVE_TEXTS = lt_doc_descriptive_texts
         DOC_LONG_TEXTS = lt_doc_long_texts
         DOC_OBJECT_RELATIONS = lt_doc_object_relations
         DOC_ADDITIONAL_FILES1 = lt_doc_additional_files1
         DOC_ADDITIONAL_FILES2 = lt_doc_additional_files2
. " CV_BI_DOC_CREATE_BATCH_INPUT




ABAP code using 7.40 inline data declarations to call FM CV_BI_DOC_CREATE_BATCH_INPUT

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 MSGID FROM SY INTO @DATA(ld_msgid).
 
"SELECT single ACTION FROM MCDOK INTO @DATA(ld_bdc_flag).
DATA(ld_bdc_flag) = ' '.
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno).
 
"SELECT single ACTION FROM MCDOK INTO @DATA(ld_close_group).
DATA(ld_close_group) = ' '.
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty).
 
 
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1).
 
 
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2).
 
"SELECT single ACTION FROM MCDOK INTO @DATA(ld_new_group).
DATA(ld_new_group) = ' '.
 
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_msgv3).
 
"SELECT single ACTION FROM MCDOK INTO @DATA(ld_tcode_mode).
DATA(ld_tcode_mode) = 'N'.
 
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_msgv4).
 
"SELECT single ACTION FROM MCDOK INTO @DATA(ld_tcode_update).
DATA(ld_tcode_update) = 'A'.
 
 


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!