SAP Function Modules

comments icon Comments

CS_BI_ECR_CREATE_BATCH_INPUT SAP Function module







CS_BI_ECR_CREATE_BATCH_INPUT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CS_BI_ECR_CREATE_BATCH_INPUT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CSBI
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CS_BI_ECR_CREATE_BATCH_INPUT - CS BI ECR CREATE BATCH INPUT 





CALL FUNCTION 'CS_BI_ECR_CREATE_BATCH_INPUT' "
  EXPORTING
*   bdc_flag = SPACE            "
    change_no_data =            " rc29a         Data for ECR
    group_data =                " bgr00         Folder Data
*   tcode_mode = 'N'            "               Processing mode for CALL TRANSACTION USING
*   tcode_update = 'S'          "               Synchronous or asynchronous update
*   change_no_datax =           " ccdokustru    Engin. Change Mgmt Structure for Docu Data Elements
  IMPORTING
    msgid =                     " t100-arbgb    Message ID
    msgno =                     " t100-msgnr    Message number
    msgty =                     " sy-msgty      Message type
    msgv1 =                     " sy-msgv1      Message variable 1
    msgv2 =                     " sy-msgv2      Message variable 2
    msgv3 =                     " sy-msgv3      Message variable 3
    msgv4 =                     " sy-msgv4      Message variable 4
  TABLES
    change_no_object_types =    " aenv          Object Identifier
    .  "  CS_BI_ECR_CREATE_BATCH_INPUT

ABAP code example for Function Module CS_BI_ECR_CREATE_BATCH_INPUT





The ABAP code below is a full code listing to execute function module CS_BI_ECR_CREATE_BATCH_INPUT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_msgid    TYPE T100-ARBGB
,
ld_msgno    TYPE T100-MSGNR
,
ld_msgty    TYPE SY-MSGTY
,
ld_msgv1    TYPE SY-MSGV1
,
ld_msgv2    TYPE SY-MSGV2
,
ld_msgv3    TYPE SY-MSGV3
,
ld_msgv4    TYPE SY-MSGV4
,
it_change_no_object_types    TYPE STANDARD TABLE OF AENV,"TABLES PARAM
wa_change_no_object_types  LIKE LINE OF it_change_no_object_types
.




DATA(ld_bdc_flag) = 'some text here'.

DATA(ld_change_no_data) = 'Check type of data required'.

DATA(ld_group_data) = 'Check type of data required'.

DATA(ld_tcode_mode) = 'some text here'.

DATA(ld_tcode_update) = 'some text here'.

DATA(ld_change_no_datax) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_change_no_object_types to it_change_no_object_types.
.

CALL FUNCTION 'CS_BI_ECR_CREATE_BATCH_INPUT'
  EXPORTING
*   bdc_flag =                   ld_bdc_flag
    change_no_data =             ld_change_no_data
    group_data =                 ld_group_data
*   tcode_mode =                 ld_tcode_mode
*   tcode_update =               ld_tcode_update
*   change_no_datax =            ld_change_no_datax
  IMPORTING
    msgid =                      ld_msgid
    msgno =                      ld_msgno
    msgty =                      ld_msgty
    msgv1 =                      ld_msgv1
    msgv2 =                      ld_msgv2
    msgv3 =                      ld_msgv3
    msgv4 =                      ld_msgv4
  TABLES
    change_no_object_types =     it_change_no_object_types
    .  "  CS_BI_ECR_CREATE_BATCH_INPUT

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_msgid  TYPE T100-ARBGB ,
ld_bdc_flag  TYPE STRING ,
it_change_no_object_types  TYPE STANDARD TABLE OF AENV ,
wa_change_no_object_types  LIKE LINE OF it_change_no_object_types,
ld_msgno  TYPE T100-MSGNR ,
ld_change_no_data  TYPE RC29A ,
ld_msgty  TYPE SY-MSGTY ,
ld_group_data  TYPE BGR00 ,
ld_msgv1  TYPE SY-MSGV1 ,
ld_tcode_mode  TYPE STRING ,
ld_msgv2  TYPE SY-MSGV2 ,
ld_tcode_update  TYPE STRING ,
ld_msgv3  TYPE SY-MSGV3 ,
ld_change_no_datax  TYPE CCDOKUSTRU ,
ld_msgv4  TYPE SY-MSGV4 .




ld_bdc_flag = 'some text here'. 

"populate fields of struture and append to itab
append wa_change_no_object_types to it_change_no_object_types.
ld_change_no_data = 'Check type of data required'.
ld_group_data = 'Check type of data required'.
ld_tcode_mode = 'some text here'.
ld_tcode_update = 'some text here'.
ld_change_no_datax = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CS_BI_ECR_CREATE_BATCH_INPUT or its description.


   
 

CS_BI_ECR_CREATE_BATCH_INPUT - 
CS_BI_ECR_CHANGE_BATCH_INPUT - 
CS_BI_CHG_CREATE_BATCH_INPUT - 
CS_BI_CHG_CHANGE_BATCH_INPUT - 
CS_BI_BOM_CREATE_WITH_LONGTEXT - 
CS_BI_BOM_CREATE_BATCH_INPUT1 - Create BOM Via Batch Input (Corrected Session Handling)