SAP BILLING_SCHEDULE_DELETE Function Module for Delete billing plan

Search SAP Function Modules

BILLING_SCHEDULE_DELETE is a standard billing schedule delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete billing plan 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 billing schedule delete FM, simply by entering the name BILLING_SCHEDULE_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: V60F
Program Name: SAPLV60F
Main Program: SAPLV60F
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BILLING_SCHEDULE_DELETE 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 'BILLING_SCHEDULE_DELETE'"Delete billing plan
  EXPORTING
*  I_FPLNR = ' ' "
*  I_FPLTR = ' ' "
*  I_UPD_FPLA = ' ' "
*  I_UPD_FPLT = ' ' "
*  I_DEL_ALL = ' ' "

 IMPORTING
   E_UPD_FPLA =  "
   E_UPD_FPLT =  "
   E_FPLNR =  "

TABLES
   FPLA_NEW =  "
   FPLA_OLD =  "
   FPLT_NEW =  "
   FPLT_OLD =  "

EXCEPTIONS
   DELETE_NOT_POSSIBLE = 1 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV60F_001 Editing the Proposed Different Billing Date

IMPORTING Parameters details for BILLING_SCHEDULE_DELETE

I_FPLNR -

Data type: FPLA-FPLNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FPLTR -

Data type: FPLT-FPLTR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_UPD_FPLA -

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

I_UPD_FPLT -

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

I_DEL_ALL -

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

EXPORTING Parameters details for BILLING_SCHEDULE_DELETE

E_UPD_FPLA -

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

E_UPD_FPLT -

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

E_FPLNR -

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

TABLES Parameters details for BILLING_SCHEDULE_DELETE

FPLA_NEW -

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

FPLA_OLD -

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

FPLT_NEW -

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

FPLT_OLD -

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

EXCEPTIONS details

DELETE_NOT_POSSIBLE -

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

Copy and paste ABAP code example for BILLING_SCHEDULE_DELETE 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.

ABAP code using 7.40 inline data declarations to call FM BILLING_SCHEDULE_DELETE

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