SAP META_CTR_CHECK Function Module for Kontrakt: Prüfung ob vollständig angelegt









META_CTR_CHECK is a standard meta ctr check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Kontrakt: Prüfung ob vollständig angelegt 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 check FM, simply by entering the name META_CTR_CHECK 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_CHECK 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_CHECK'"Kontrakt: Prüfung ob vollständig angelegt
  EXPORTING
   IV_SRM_CONTRACT_NUMBER =  "Globally Unique Identifier
   IV_LOGICAL_SYSTEM =  "Logisches System
*  IV_PORG_PARTNER_ID =  "Einkaufsorganisation
*  IV_LOCATION_PARTNER_ID =  "Standort
*  IV_BE_LOGSYS =  "Logisches System
*  IV_BE_OBJTYPE =  "Objekttyp im Zielsystem
*  IV_PMNTTRMS =  "Terms of payment key
*  IV_CURRENCY =  "Currency Key

 IMPORTING
   EV_CTR_CREATION =  "P = in process, O = OK, E = Error
   EV_CND_CREATION =  "P = in process, O = OK, E = Error
   ET_CTR_MM_ITEM_MAP =  "Mapping information for the contract item
   ET_CTR_DISTR_MESSAGES =  "Messages from the backend system

TABLES
   ET_MESSAGES =  "Returnparameter
   ET_CONTROL_RECORD =  "Steuersatz für META-BAPI-Steuerung
.



IMPORTING Parameters details for META_CTR_CHECK

IV_SRM_CONTRACT_NUMBER - Globally Unique Identifier

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

IV_LOGICAL_SYSTEM - Logisches System

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

IV_PORG_PARTNER_ID - Einkaufsorganisation

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

IV_LOCATION_PARTNER_ID - Standort

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

IV_BE_LOGSYS - Logisches System

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

IV_BE_OBJTYPE - Objekttyp im Zielsystem

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

IV_PMNTTRMS - Terms of payment key

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

IV_CURRENCY - Currency Key

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

EXPORTING Parameters details for META_CTR_CHECK

EV_CTR_CREATION - P = in process, O = OK, E = Error

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

EV_CND_CREATION - P = in process, O = OK, E = Error

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

ET_CTR_MM_ITEM_MAP - Mapping information for the contract item

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

ET_CTR_DISTR_MESSAGES - Messages from the backend system

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

TABLES Parameters details for META_CTR_CHECK

ET_MESSAGES - Returnparameter

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

ET_CONTROL_RECORD - Steuersatz für META-BAPI-Steuerung

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

Copy and paste ABAP code example for META_CTR_CHECK 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_et_messages  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_ev_ctr_creation  TYPE C, "   
lv_iv_srm_contract_number  TYPE CRMT_OBJECT_ID_DB, "   
lv_ev_cnd_creation  TYPE C, "   
lt_et_control_record  TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, "   
lv_iv_logical_system  TYPE LOGSYS, "   
lv_et_ctr_mm_item_map  TYPE BBPT_CTR_BE_ITEM_MAP, "   
lv_iv_porg_partner_id  TYPE BU_PARTNER, "   
lv_et_ctr_distr_messages  TYPE BBPT_CTR_DISTR_MESSAGES, "   
lv_iv_location_partner_id  TYPE BU_PARTNER, "   
lv_iv_be_logsys  TYPE LOGSYS, "   
lv_iv_be_objtype  TYPE BBP_TRGT_OBJTYP, "   
lv_iv_pmnttrms  TYPE DZTERM, "   
lv_iv_currency  TYPE WAERS. "   

  CALL FUNCTION 'META_CTR_CHECK'  "Kontrakt: Prüfung ob vollständig angelegt
    EXPORTING
         IV_SRM_CONTRACT_NUMBER = lv_iv_srm_contract_number
         IV_LOGICAL_SYSTEM = lv_iv_logical_system
         IV_PORG_PARTNER_ID = lv_iv_porg_partner_id
         IV_LOCATION_PARTNER_ID = lv_iv_location_partner_id
         IV_BE_LOGSYS = lv_iv_be_logsys
         IV_BE_OBJTYPE = lv_iv_be_objtype
         IV_PMNTTRMS = lv_iv_pmnttrms
         IV_CURRENCY = lv_iv_currency
    IMPORTING
         EV_CTR_CREATION = lv_ev_ctr_creation
         EV_CND_CREATION = lv_ev_cnd_creation
         ET_CTR_MM_ITEM_MAP = lv_et_ctr_mm_item_map
         ET_CTR_DISTR_MESSAGES = lv_et_ctr_distr_messages
    TABLES
         ET_MESSAGES = lt_et_messages
         ET_CONTROL_RECORD = lt_et_control_record
. " META_CTR_CHECK




ABAP code using 7.40 inline data declarations to call FM META_CTR_CHECK

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!