SAP BAPI_CONDITION_CONTRACT_READ Function Module for Read Data for a Single Contract









BAPI_CONDITION_CONTRACT_READ is a standard bapi condition contract read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Data for a Single Contract 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 bapi condition contract read FM, simply by entering the name BAPI_CONDITION_CONTRACT_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: WCB_BAPI_METHODS
Program Name: SAPLWCB_BAPI_METHODS
Main Program: SAPLWCB_BAPI_METHODS
Appliation area:
Release date: 31-May-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_CONDITION_CONTRACT_READ 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 'BAPI_CONDITION_CONTRACT_READ'"Read Data for a Single Contract
EXPORTING
CONDITIONCONTRACTNUMBER = "Condition Contract: Key

IMPORTING
HEADDATAOUT = "BAPI: Condition Contract Header

TABLES
* ITEMDATAOUT = "BAPI: Condition Contract: Eligible Partners
* CALENDARDATAOUT = "BAPI: Condition Contract Calendar
* CONDITIONKEYDATAOUT = "BAPI Condition Contract: Condition Structure Fields
* CONDITIONITEMDATAOUT = "BAPI: Condition Contract: Item Conditions
* EXTENSIONOUT = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* HEADTEXTOUT = "Condition Contract Header Texts
* ITEMTEXTOUT = "Condition Contract: Texts for Entitled Partners
* RETURN = "Return Parameter(s)
* SCALEDATAOUT = "BAPI: Condition Contract: Conditions Scales
* BVBDATAOUT = "BAPI: Condition Contract Business Volume Base
.



IMPORTING Parameters details for BAPI_CONDITION_CONTRACT_READ

CONDITIONCONTRACTNUMBER - Condition Contract: Key

Data type: BAPICCKEY-CONDITION_CONTRACT_NUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_CONDITION_CONTRACT_READ

HEADDATAOUT - BAPI: Condition Contract Header

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

TABLES Parameters details for BAPI_CONDITION_CONTRACT_READ

ITEMDATAOUT - BAPI: Condition Contract: Eligible Partners

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

CALENDARDATAOUT - BAPI: Condition Contract Calendar

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

CONDITIONKEYDATAOUT - BAPI Condition Contract: Condition Structure Fields

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

CONDITIONITEMDATAOUT - BAPI: Condition Contract: Item Conditions

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

EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

HEADTEXTOUT - Condition Contract Header Texts

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

ITEMTEXTOUT - Condition Contract: Texts for Entitled Partners

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

RETURN - Return Parameter(s)

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

SCALEDATAOUT - BAPI: Condition Contract: Conditions Scales

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

BVBDATAOUT - BAPI: Condition Contract Business Volume Base

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

Copy and paste ABAP code example for BAPI_CONDITION_CONTRACT_READ 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_headdataout  TYPE BAPICCHEADOS, "   
lt_itemdataout  TYPE STANDARD TABLE OF BAPICCITEMO, "   
lv_conditioncontractnumber  TYPE BAPICCKEY-CONDITION_CONTRACT_NUMBER, "   
lt_calendardataout  TYPE STANDARD TABLE OF BAPICCCALO, "   
lt_conditionkeydataout  TYPE STANDARD TABLE OF BAPICCCONDITIONKEYO, "   
lt_conditionitemdataout  TYPE STANDARD TABLE OF BAPICCCONDITIONITEMO, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_headtextout  TYPE STANDARD TABLE OF BAPICCHEADTEXT, "   
lt_itemtextout  TYPE STANDARD TABLE OF BAPICCITEMTEXT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_scaledataout  TYPE STANDARD TABLE OF BAPICCSCALEO, "   
lt_bvbdataout  TYPE STANDARD TABLE OF BAPICCBVBO. "   

  CALL FUNCTION 'BAPI_CONDITION_CONTRACT_READ'  "Read Data for a Single Contract
    EXPORTING
         CONDITIONCONTRACTNUMBER = lv_conditioncontractnumber
    IMPORTING
         HEADDATAOUT = lv_headdataout
    TABLES
         ITEMDATAOUT = lt_itemdataout
         CALENDARDATAOUT = lt_calendardataout
         CONDITIONKEYDATAOUT = lt_conditionkeydataout
         CONDITIONITEMDATAOUT = lt_conditionitemdataout
         EXTENSIONOUT = lt_extensionout
         HEADTEXTOUT = lt_headtextout
         ITEMTEXTOUT = lt_itemtextout
         RETURN = lt_return
         SCALEDATAOUT = lt_scaledataout
         BVBDATAOUT = lt_bvbdataout
. " BAPI_CONDITION_CONTRACT_READ




ABAP code using 7.40 inline data declarations to call FM BAPI_CONDITION_CONTRACT_READ

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.

 
 
"SELECT single CONDITION_CONTRACT_NUMBER FROM BAPICCKEY INTO @DATA(ld_conditioncontractnumber).
 
 
 
 
 
 
 
 
 
 


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!