SAP BILLING_SCHEDULE_READ Function Module for Read billing plan
BILLING_SCHEDULE_READ is a standard billing schedule 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 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 read FM, simply by entering the name BILLING_SCHEDULE_READ 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_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 'BILLING_SCHEDULE_READ'"Read billing plan.
EXPORTING
FPLNR = "Number of billing plan
* I_VFKDAT = "
* I_BFKDAT = "
TABLES
* ZFPLA = "Internal table for billing plans
ZFPLT = "Internal tables for date from billing plans
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_READ
FPLNR - Number of billing plan
Data type: FPLA-FPLNROptional: No
Call by Reference: No ( called with pass by value option)
I_VFKDAT -
Data type: FPLT-AFDATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BFKDAT -
Data type: FPLT-AFDATOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BILLING_SCHEDULE_READ
ZFPLA - Internal table for billing plans
Data type: FPLAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
ZFPLT - Internal tables for date from billing plans
Data type: FPLTVBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BILLING_SCHEDULE_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_fplnr | TYPE FPLA-FPLNR, " | |||
lt_zfpla | TYPE STANDARD TABLE OF FPLAVB, " | |||
lt_zfplt | TYPE STANDARD TABLE OF FPLTVB, " | |||
lv_i_vfkdat | TYPE FPLT-AFDAT, " | |||
lv_i_bfkdat | TYPE FPLT-AFDAT. " |
  CALL FUNCTION 'BILLING_SCHEDULE_READ' "Read billing plan |
EXPORTING | ||
FPLNR | = lv_fplnr | |
I_VFKDAT | = lv_i_vfkdat | |
I_BFKDAT | = lv_i_bfkdat | |
TABLES | ||
ZFPLA | = lt_zfpla | |
ZFPLT | = lt_zfplt | |
. " BILLING_SCHEDULE_READ |
ABAP code using 7.40 inline data declarations to call FM BILLING_SCHEDULE_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 FPLNR FROM FPLA INTO @DATA(ld_fplnr). | ||||
"SELECT single AFDAT FROM FPLT INTO @DATA(ld_i_vfkdat). | ||||
"SELECT single AFDAT FROM FPLT INTO @DATA(ld_i_bfkdat). | ||||
Search for further information about these or an SAP related objects