SAP BD_APS_EMAIL Function Module for Send E-Mails for Service Adjust Payment Scheme from UCES









BD_APS_EMAIL is a standard bd aps email SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Send E-Mails for Service Adjust Payment Scheme from UCES 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 bd aps email FM, simply by entering the name BD_APS_EMAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function BD_APS_EMAIL 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 'BD_APS_EMAIL'"Send E-Mails for Service Adjust Payment Scheme from UCES
EXPORTING
* I_SPRAS = SY-LANGU "Language Key of Current Text Environment
* I_SAVE = "Indicator
* I_DATUM = SY-DATUM "Date from Which a Time Slice is Valid
I_BUPA = "Business Partner Number
* I_VKONTO = "Contract Account Number
* I_CONTRACT = "Contract
* I_USER = SY-UNAME "User Name in User Master Record
I_SEL_FREQ = "Payment Frequency
I_STARTDATE = "Start of Sample Line
* I_CREATE = "Indicator

IMPORTING
RETURN = "Return Parameter(s)

TABLES
BUDBIPLAN = "Table Type for UCES_PP for Payment Plan
E_PS_PAYDATES = "Table Type for UCES_PP_PAY_DATES - Creation of Payment Plan
* XT_UCES_EXTENSION = "UCES: Display Customer-Specific Fields from JSP
.



IMPORTING Parameters details for BD_APS_EMAIL

I_SPRAS - Language Key of Current Text Environment

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SAVE - Indicator

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

I_DATUM - Date from Which a Time Slice is Valid

Data type: REGEN-AB
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUPA - Business Partner Number

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

I_VKONTO - Contract Account Number

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

I_CONTRACT - Contract

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

I_USER - User Name in User Master Record

Data type: USR04-BNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SEL_FREQ - Payment Frequency

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

I_STARTDATE - Start of Sample Line

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

I_CREATE - Indicator

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

EXPORTING Parameters details for BD_APS_EMAIL

RETURN - Return Parameter(s)

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

TABLES Parameters details for BD_APS_EMAIL

BUDBIPLAN - Table Type for UCES_PP for Payment Plan

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

E_PS_PAYDATES - Table Type for UCES_PP_PAY_DATES - Creation of Payment Plan

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

XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP

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

Copy and paste ABAP code example for BD_APS_EMAIL 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_return  TYPE BAPIRET2, "   
lv_i_spras  TYPE SPRAS, "   SY-LANGU
lt_budbiplan  TYPE STANDARD TABLE OF UCES_PS_TAB, "   
lv_i_save  TYPE KENNZX, "   
lv_i_datum  TYPE REGEN-AB, "   SY-DATUM
lt_e_ps_paydates  TYPE STANDARD TABLE OF UCES_PS_PAY_DATES_TAB, "   
lv_i_bupa  TYPE GPART_KK, "   
lt_xt_uces_extension  TYPE STANDARD TABLE OF UCES_EXTENSION, "   
lv_i_vkonto  TYPE VKONT_KK, "   
lv_i_contract  TYPE VERTRAG, "   
lv_i_user  TYPE USR04-BNAME, "   SY-UNAME
lv_i_sel_freq  TYPE E_PAYFREQ, "   
lv_i_startdate  TYPE E_BEGDAT, "   
lv_i_create  TYPE KENNZX. "   

  CALL FUNCTION 'BD_APS_EMAIL'  "Send E-Mails for Service Adjust Payment Scheme from UCES
    EXPORTING
         I_SPRAS = lv_i_spras
         I_SAVE = lv_i_save
         I_DATUM = lv_i_datum
         I_BUPA = lv_i_bupa
         I_VKONTO = lv_i_vkonto
         I_CONTRACT = lv_i_contract
         I_USER = lv_i_user
         I_SEL_FREQ = lv_i_sel_freq
         I_STARTDATE = lv_i_startdate
         I_CREATE = lv_i_create
    IMPORTING
         RETURN = lv_return
    TABLES
         BUDBIPLAN = lt_budbiplan
         E_PS_PAYDATES = lt_e_ps_paydates
         XT_UCES_EXTENSION = lt_xt_uces_extension
. " BD_APS_EMAIL




ABAP code using 7.40 inline data declarations to call FM BD_APS_EMAIL

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.

 
DATA(ld_i_spras) = SY-LANGU.
 
 
 
"SELECT single AB FROM REGEN INTO @DATA(ld_i_datum).
DATA(ld_i_datum) = SY-DATUM.
 
 
 
 
 
 
"SELECT single BNAME FROM USR04 INTO @DATA(ld_i_user).
DATA(ld_i_user) = SY-UNAME.
 
 
 
 


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!