SAP Function Modules
META_CTR_TRANSFER SAP Function module - Change contract
META_CTR_TRANSFER 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 META_CTR_TRANSFER into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
BBP_BD_META_BAPIS_PART2
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM META_CTR_TRANSFER - META CTR TRANSFER
CALL FUNCTION 'META_CTR_TRANSFER' "Change contract
EXPORTING
* iv_logical_system = " logsys Logisches System
iv_src_guid = " bbp_guid Globally Unique Identifier
* iv_system_type = " bbp_system_type Systemart
is_header = " bbp_pds_ctr_header_d Schnittstelle Kopf-Daten Kontrakt GetDetail-Fall
it_items = " bbpt_pd_ctr_item_d Tabellentyp Positionsdaten
it_org_data = " bbpt_pds_org Tabellentyp Org-Daten
* it_text = " bbpt_pd_longtext Langtexte
it_partner = " bbpt_pd_partner Geschäftspartner
* it_attach = " bbpt_pds_att_t KW-Anlagen inkl. Dokument
it_status = " bbpt_pds_status Status
* it_dist = " bbpt_pd_dis Kontrakt Verteilungsdaten
* it_tol = " bbpt_pd_tol Toleranzen
* it_condition = " bbpt_pd_cnd_d Tabellentyp Stammkonditionen
* iv_unlock_ind = " xfeld Feld zum Ankreuzen
* iv_reconciliation_requested = " xfeld Checkbox
IMPORTING
et_messages = " bbpt_pd_messages Fehlermeldungen
TABLES
et_control_record = " bbp_control_record Steuersatz für META-BAPI-Steuerung
. " META_CTR_TRANSFER
ABAP code example for Function Module META_CTR_TRANSFER
The ABAP code below is a full code listing to execute function module META_CTR_TRANSFER 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).
| ld_et_messages | TYPE BBPT_PD_MESSAGES , |
| it_et_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD,"TABLES PARAM |
| wa_et_control_record | LIKE LINE OF it_et_control_record . |
DATA(ld_iv_logical_system) = '20210129'.
DATA(ld_iv_src_guid) = 'some text here'.
DATA(ld_iv_system_type) = '20210129'.
DATA(ld_is_header) = 'some text here'.
DATA(ld_it_items) = 'some text here'.
DATA(ld_it_org_data) = 'some text here'.
DATA(ld_it_text) = 'some text here'.
DATA(ld_it_partner) = 'some text here'.
DATA(ld_it_attach) = 'some text here'.
DATA(ld_it_status) = 'some text here'.
DATA(ld_it_dist) = 'some text here'.
DATA(ld_it_tol) = 'some text here'.
DATA(ld_it_condition) = 'some text here'.
DATA(ld_iv_unlock_ind) = 'some text here'.
DATA(ld_iv_reconciliation_requested) = 'some text here'.
"populate fields of struture and append to itab
append wa_et_control_record to it_et_control_record. . CALL FUNCTION 'META_CTR_TRANSFER' EXPORTING * iv_logical_system = ld_iv_logical_system iv_src_guid = ld_iv_src_guid * iv_system_type = ld_iv_system_type is_header = ld_is_header it_items = ld_it_items it_org_data = ld_it_org_data * it_text = ld_it_text it_partner = ld_it_partner * it_attach = ld_it_attach it_status = ld_it_status * it_dist = ld_it_dist * it_tol = ld_it_tol * it_condition = ld_it_condition * iv_unlock_ind = ld_iv_unlock_ind * iv_reconciliation_requested = ld_iv_reconciliation_requested IMPORTING et_messages = ld_et_messages TABLES et_control_record = it_et_control_record . " META_CTR_TRANSFER
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_et_messages | TYPE BBPT_PD_MESSAGES , |
| ld_iv_logical_system | TYPE LOGSYS , |
| it_et_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD , |
| wa_et_control_record | LIKE LINE OF it_et_control_record, |
| ld_iv_src_guid | TYPE BBP_GUID , |
| ld_iv_system_type | TYPE BBP_SYSTEM_TYPE , |
| ld_is_header | TYPE BBP_PDS_CTR_HEADER_D , |
| ld_it_items | TYPE BBPT_PD_CTR_ITEM_D , |
| ld_it_org_data | TYPE BBPT_PDS_ORG , |
| ld_it_text | TYPE BBPT_PD_LONGTEXT , |
| ld_it_partner | TYPE BBPT_PD_PARTNER , |
| ld_it_attach | TYPE BBPT_PDS_ATT_T , |
| ld_it_status | TYPE BBPT_PDS_STATUS , |
| ld_it_dist | TYPE BBPT_PD_DIS , |
| ld_it_tol | TYPE BBPT_PD_TOL , |
| ld_it_condition | TYPE BBPT_PD_CND_D , |
| ld_iv_unlock_ind | TYPE XFELD , |
| ld_iv_reconciliation_requested | TYPE XFELD . |
ld_iv_logical_system = '20210129'.
"populate fields of struture and append to itab
append wa_et_control_record to it_et_control_record.
ld_iv_src_guid = 'some text here'.
ld_iv_system_type = '20210129'.
ld_is_header = 'some text here'.
ld_it_items = 'some text here'.
ld_it_org_data = 'some text here'.
ld_it_text = 'some text here'.
ld_it_partner = 'some text here'.
ld_it_attach = 'some text here'.
ld_it_status = 'some text here'.
ld_it_dist = 'some text here'.
ld_it_tol = 'some text here'.
ld_it_condition = 'some text here'.
ld_iv_unlock_ind = 'some text here'.
ld_iv_reconciliation_requested = 'some text here'.
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 META_CTR_TRANSFER or its description.