SAP META_CTR_INIT_UPLOAD Function Module for Meta BAPI for Initial Upload of Contracts









META_CTR_INIT_UPLOAD is a standard meta ctr init upload SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Meta BAPI for Initial Upload of Contracts 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 meta ctr init upload FM, simply by entering the name META_CTR_INIT_UPLOAD into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_BD_META_BAPIS_PART2
Program Name: SAPLBBP_BD_META_BAPIS_PART2
Main Program: SAPLBBP_BD_META_BAPIS_PART2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function META_CTR_INIT_UPLOAD 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 'META_CTR_INIT_UPLOAD'"Meta BAPI for Initial Upload of Contracts
  EXPORTING
   IV_LOG_SYS =  "Logical system
   IV_CTR_RELEASE =  "Checkbox
   IV_SIMULATION =  "Checkbox
   IV_NO_DUPLICATES =  "Checkbox
   IV_THRESHHOLD =  "2 byte integer (signed)
*  IV_LOSE_HIER_DATA =  "Value control record

TABLES
   IT_RANGE_BE_OBJECT_ID =  "
*  IT_RANGE_PROCESS_TYPE =  "Interface Structure for Ranges of the Process Type
*  IT_RANGE_VENDOR =  "Interface Structure for Ranges for Business Partner
*  IT_RANGE_PORG =  "Interface Structure for Ranges via Purchasing Organization
   ET_MESSAGES =  "Context and Message data
.



IMPORTING Parameters details for META_CTR_INIT_UPLOAD

IV_LOG_SYS - Logical system

Data type: LOGSYS
Optional: No
Call by Reference: Yes

IV_CTR_RELEASE - Checkbox

Data type: XFELD
Optional: No
Call by Reference: Yes

IV_SIMULATION - Checkbox

Data type: XFELD
Optional: No
Call by Reference: Yes

IV_NO_DUPLICATES - Checkbox

Data type: XFELD
Optional: No
Call by Reference: Yes

IV_THRESHHOLD - 2 byte integer (signed)

Data type: INT2
Optional: No
Call by Reference: Yes

IV_LOSE_HIER_DATA - Value control record

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

TABLES Parameters details for META_CTR_INIT_UPLOAD

IT_RANGE_BE_OBJECT_ID -

Data type: BBPT_PDS_RANGE_OBJECT_ID
Optional: No
Call by Reference: Yes

IT_RANGE_PROCESS_TYPE - Interface Structure for Ranges of the Process Type

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

IT_RANGE_VENDOR - Interface Structure for Ranges for Business Partner

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

IT_RANGE_PORG - Interface Structure for Ranges via Purchasing Organization

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

ET_MESSAGES - Context and Message data

Data type: BBPT_CTR_LOG_MSG_CONTEXT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for META_CTR_INIT_UPLOAD 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_iv_log_sys  TYPE LOGSYS, "   
lt_it_range_be_object_id  TYPE STANDARD TABLE OF BBPT_PDS_RANGE_OBJECT_ID, "   
lv_iv_ctr_release  TYPE XFELD, "   
lt_it_range_process_type  TYPE STANDARD TABLE OF BBPT_PD_RANGE_PROC_TYPE, "   
lv_iv_simulation  TYPE XFELD, "   
lt_it_range_vendor  TYPE STANDARD TABLE OF BBPT_PD_RANGE_BU_PARTNER, "   
lt_it_range_porg  TYPE STANDARD TABLE OF BBPT_PDS_RANGE_PROC_ORG, "   
lv_iv_no_duplicates  TYPE XFELD, "   
lt_et_messages  TYPE STANDARD TABLE OF BBPT_CTR_LOG_MSG_CONTEXT, "   
lv_iv_threshhold  TYPE INT2, "   
lv_iv_lose_hier_data  TYPE BBP_CONTROL_VALUE. "   

  CALL FUNCTION 'META_CTR_INIT_UPLOAD'  "Meta BAPI for Initial Upload of Contracts
    EXPORTING
         IV_LOG_SYS = lv_iv_log_sys
         IV_CTR_RELEASE = lv_iv_ctr_release
         IV_SIMULATION = lv_iv_simulation
         IV_NO_DUPLICATES = lv_iv_no_duplicates
         IV_THRESHHOLD = lv_iv_threshhold
         IV_LOSE_HIER_DATA = lv_iv_lose_hier_data
    TABLES
         IT_RANGE_BE_OBJECT_ID = lt_it_range_be_object_id
         IT_RANGE_PROCESS_TYPE = lt_it_range_process_type
         IT_RANGE_VENDOR = lt_it_range_vendor
         IT_RANGE_PORG = lt_it_range_porg
         ET_MESSAGES = lt_et_messages
. " META_CTR_INIT_UPLOAD




ABAP code using 7.40 inline data declarations to call FM META_CTR_INIT_UPLOAD

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



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!