SAP BBP_CTR_UPL_CONTRACT_DATA_GET Function Module for NOTRANSL: Details zum MM Kontrakte holen
BBP_CTR_UPL_CONTRACT_DATA_GET is a standard bbp ctr upl contract data get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Details zum MM Kontrakte holen 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 bbp ctr upl contract data get FM, simply by entering the name BBP_CTR_UPL_CONTRACT_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_CTR_UPL
Program Name: SAPLBBP_CTR_UPL
Main Program: SAPLBBP_CTR_UPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_CTR_UPL_CONTRACT_DATA_GET 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 'BBP_CTR_UPL_CONTRACT_DATA_GET'"NOTRANSL: Details zum MM Kontrakte holen.
TABLES
IT_CONTRACT_IDS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
ET_HEADER = "Contract Communication Structure: Header/Org/Partner
ET_ITEMS = "Contract Communication Structure: Items/Partner
ET_TEXT = "Contract Communication Structure: Texts
ET_CONDITIONS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
ET_COND_SCALE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
ET_ATT = "Contract Attachments Structure Without PHIO Content
ET_ATT_CONT = "Contract Attachments Structure PHIO Content Only
ET_MESSAGES = "Return Parameters
TABLES Parameters details for BBP_CTR_UPL_CONTRACT_DATA_GET
IT_CONTRACT_IDS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: BBPS_CTR_MM_IDOptional: No
Call by Reference: Yes
ET_HEADER - Contract Communication Structure: Header/Org/Partner
Data type: BBPS_CTR_MM_HEADEROptional: No
Call by Reference: Yes
ET_ITEMS - Contract Communication Structure: Items/Partner
Data type: BBPS_CTR_MM_ITEMOptional: No
Call by Reference: Yes
ET_TEXT - Contract Communication Structure: Texts
Data type: BBPS_CTR_MM_TEXTOptional: No
Call by Reference: Yes
ET_CONDITIONS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: BBPS_CTR_MM_CNDOptional: No
Call by Reference: Yes
ET_COND_SCALE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: BBPS_CTR_MM_CND_SCALEOptional: No
Call by Reference: Yes
ET_ATT - Contract Attachments Structure Without PHIO Content
Data type: BBPS_CTR_MM_ATTOptional: No
Call by Reference: Yes
ET_ATT_CONT - Contract Attachments Structure PHIO Content Only
Data type: BBPS_CTR_MM_ATT_CONTOptional: No
Call by Reference: Yes
ET_MESSAGES - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CTR_UPL_CONTRACT_DATA_GET 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_it_contract_ids | TYPE STANDARD TABLE OF BBPS_CTR_MM_ID, " | |||
| lt_et_header | TYPE STANDARD TABLE OF BBPS_CTR_MM_HEADER, " | |||
| lt_et_items | TYPE STANDARD TABLE OF BBPS_CTR_MM_ITEM, " | |||
| lt_et_text | TYPE STANDARD TABLE OF BBPS_CTR_MM_TEXT, " | |||
| lt_et_conditions | TYPE STANDARD TABLE OF BBPS_CTR_MM_CND, " | |||
| lt_et_cond_scale | TYPE STANDARD TABLE OF BBPS_CTR_MM_CND_SCALE, " | |||
| lt_et_att | TYPE STANDARD TABLE OF BBPS_CTR_MM_ATT, " | |||
| lt_et_att_cont | TYPE STANDARD TABLE OF BBPS_CTR_MM_ATT_CONT, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BBP_CTR_UPL_CONTRACT_DATA_GET' "NOTRANSL: Details zum MM Kontrakte holen |
| TABLES | ||
| IT_CONTRACT_IDS | = lt_it_contract_ids | |
| ET_HEADER | = lt_et_header | |
| ET_ITEMS | = lt_et_items | |
| ET_TEXT | = lt_et_text | |
| ET_CONDITIONS | = lt_et_conditions | |
| ET_COND_SCALE | = lt_et_cond_scale | |
| ET_ATT | = lt_et_att | |
| ET_ATT_CONT | = lt_et_att_cont | |
| ET_MESSAGES | = lt_et_messages | |
| . " BBP_CTR_UPL_CONTRACT_DATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CTR_UPL_CONTRACT_DATA_GET
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