SAP UPDATE_SFLIGHT_A Function Module for BC414: Update of database table SFLIGHT









UPDATE_SFLIGHT_A is a standard update sflight a SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BC414: Update of database table SFLIGHT 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 update sflight a FM, simply by entering the name UPDATE_SFLIGHT_A into the relevant SAP transaction such as SE37 or SE38.

Function Group: BC414_DB
Program Name: SAPLBC414_DB
Main Program:
Appliation area: S
Release date: 24-Jan-2001
Mode(Normal, Remote etc): Normal Function Module
Update:



Function UPDATE_SFLIGHT_A 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 'UPDATE_SFLIGHT_A'"BC414: Update of database table SFLIGHT
EXPORTING
CARRIER = "Airline carrier
CONNECTION = "Connection number
DATE = "Date

EXCEPTIONS
UPDATE_FAILURE = 1 FLIGHT_FULL = 2 FLIGHT_NOT_FOUND = 3
.



IMPORTING Parameters details for UPDATE_SFLIGHT_A

CARRIER - Airline carrier

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

CONNECTION - Connection number

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

DATE - Date

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

EXCEPTIONS details

UPDATE_FAILURE - Error during update of table SBOOK

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

FLIGHT_FULL - Flight is fully booked

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

FLIGHT_NOT_FOUND -

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

Copy and paste ABAP code example for UPDATE_SFLIGHT_A 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_carrier  TYPE SFLIGHT-CARRID, "   
lv_update_failure  TYPE SFLIGHT, "   
lv_connection  TYPE SFLIGHT-CONNID, "   
lv_flight_full  TYPE SFLIGHT, "   
lv_date  TYPE SFLIGHT-FLDATE, "   
lv_flight_not_found  TYPE SFLIGHT. "   

  CALL FUNCTION 'UPDATE_SFLIGHT_A'  "BC414: Update of database table SFLIGHT
    EXPORTING
         CARRIER = lv_carrier
         CONNECTION = lv_connection
         DATE = lv_date
    EXCEPTIONS
        UPDATE_FAILURE = 1
        FLIGHT_FULL = 2
        FLIGHT_NOT_FOUND = 3
. " UPDATE_SFLIGHT_A




ABAP code using 7.40 inline data declarations to call FM UPDATE_SFLIGHT_A

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 CARRID FROM SFLIGHT INTO @DATA(ld_carrier).
 
 
"SELECT single CONNID FROM SFLIGHT INTO @DATA(ld_connection).
 
 
"SELECT single FLDATE FROM SFLIGHT INTO @DATA(ld_date).
 
 


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!