SAP BAPI_WELLCOMP_CHANGE Function Module for Changes a Well Completion Record









BAPI_WELLCOMP_CHANGE is a standard bapi wellcomp change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Changes a Well Completion Record 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 wellcomp change FM, simply by entering the name BAPI_WELLCOMP_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIU_WELL_COMPLETION
Program Name: SAPLOIU_WELL_COMPLETION
Main Program: SAPLOIU_WELL_COMPLETION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_WELLCOMP_CHANGE 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_WELLCOMP_CHANGE'"Changes a Well Completion Record
  EXPORTING
   WCDETAIL =  "
   WCENGINEERING =  "
   WCHEADER =  "
   WCLOCATION =  "
   WCRELATED =  "

 IMPORTING
   WCDETAIL =  "
   WCENGINEERING =  "
   WCHEADER =  "
   WCLOCATION =  "
   WCRELATED =  "

TABLES
   RETURN =  "
*  WC_READINGS =  "Measurement send
.



IMPORTING Parameters details for BAPI_WELLCOMP_CHANGE

WCDETAIL -

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

WCENGINEERING -

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

WCHEADER -

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

WCLOCATION -

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

WCRELATED -

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

EXPORTING Parameters details for BAPI_WELLCOMP_CHANGE

WCDETAIL -

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

WCENGINEERING -

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

WCHEADER -

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

WCLOCATION -

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

WCRELATED -

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

TABLES Parameters details for BAPI_WELLCOMP_CHANGE

RETURN -

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

WC_READINGS - Measurement send

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

Copy and paste ABAP code example for BAPI_WELLCOMP_CHANGE 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_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_wcdetail  TYPE BAPI_OIU_WC_1, "   
lv_wcdetail  TYPE BAPI_OIU_WC_1, "   
lt_wc_readings  TYPE STANDARD TABLE OF BAPI_OIU_MEAS_SEND, "   
lv_wcengineering  TYPE BAPI_OIU_WC_4, "   
lv_wcengineering  TYPE BAPI_OIU_WC_4, "   
lv_wcheader  TYPE BAPI_OIU_WC, "   
lv_wcheader  TYPE BAPI_OIU_WC, "   
lv_wclocation  TYPE BAPI_OIU_WC_2, "   
lv_wclocation  TYPE BAPI_OIU_WC_2, "   
lv_wcrelated  TYPE BAPI_OIU_WC_3, "   
lv_wcrelated  TYPE BAPI_OIU_WC_3. "   

  CALL FUNCTION 'BAPI_WELLCOMP_CHANGE'  "Changes a Well Completion Record
    EXPORTING
         WCDETAIL = lv_wcdetail
         WCENGINEERING = lv_wcengineering
         WCHEADER = lv_wcheader
         WCLOCATION = lv_wclocation
         WCRELATED = lv_wcrelated
    IMPORTING
         WCDETAIL = lv_wcdetail
         WCENGINEERING = lv_wcengineering
         WCHEADER = lv_wcheader
         WCLOCATION = lv_wclocation
         WCRELATED = lv_wcrelated
    TABLES
         RETURN = lt_return
         WC_READINGS = lt_wc_readings
. " BAPI_WELLCOMP_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_WELLCOMP_CHANGE

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!