SAP PRICING_DETERMINE_DATES Function Module for NOTRANSL: Preisfindung: Ermitteln Tage/Monate/Jahre aus Datumsintervall









PRICING_DETERMINE_DATES is a standard pricing determine dates SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Preisfindung: Ermitteln Tage/Monate/Jahre aus Datumsintervall 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 pricing determine dates FM, simply by entering the name PRICING_DETERMINE_DATES into the relevant SAP transaction such as SE37 or SE38.

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



Function PRICING_DETERMINE_DATES 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 'PRICING_DETERMINE_DATES'"NOTRANSL: Preisfindung: Ermitteln Tage/Monate/Jahre aus Datumsintervall
  EXPORTING
   DATE_BEGIN =  "Start of accounting settlement period
   DATE_END =  "Date on which services rendered
*  CAL_ID =  "Calendar for Defining Days Relevant to Billing/Invoicing
*  ANZTM =  "Number of Days in the Month
*  ANZTJ =  "Number of Days in the Year
*  ANZTBME = '  ' "Calendar for Defining Days Relevant to Billing/Invoicing
*  USE_BADI =  "

 IMPORTING
   DAYS =  "Number of Days
   MONTHS =  "Number of Months
   YEARS =  "Number of Years
   WEEKS =  "Number of Weeks
.




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_SAPLV61A_001
EXIT_SAPLV61A_002 Customer Exit : Pricing - Rounding Rule
EXIT_SAPLV61A_400 F&A Repricing controlling

IMPORTING Parameters details for PRICING_DETERMINE_DATES

DATE_BEGIN - Start of accounting settlement period

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

DATE_END - Date on which services rendered

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

CAL_ID - Calendar for Defining Days Relevant to Billing/Invoicing

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

ANZTM - Number of Days in the Month

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

ANZTJ - Number of Days in the Year

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

ANZTBME - Calendar for Defining Days Relevant to Billing/Invoicing

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

USE_BADI -

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

EXPORTING Parameters details for PRICING_DETERMINE_DATES

DAYS - Number of Days

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

MONTHS - Number of Months

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

YEARS - Number of Years

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

WEEKS - Number of Weeks

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

Copy and paste ABAP code example for PRICING_DETERMINE_DATES 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_days  TYPE ANZ_TAGE, "   
lv_date_begin  TYPE DATUM, "   
lv_months  TYPE ANZ_MONATE, "   
lv_date_end  TYPE DATUM, "   
lv_years  TYPE ANZ_JAHRE, "   
lv_cal_id  TYPE FAKCA, "   
lv_anztm  TYPE ANZTM, "   
lv_weeks  TYPE ANZ_WOCHEN, "   
lv_anztj  TYPE ANZTJ, "   
lv_anztbme  TYPE FAKCA, "   ' '
lv_use_badi  TYPE PTYP. "   

  CALL FUNCTION 'PRICING_DETERMINE_DATES'  "NOTRANSL: Preisfindung: Ermitteln Tage/Monate/Jahre aus Datumsintervall
    EXPORTING
         DATE_BEGIN = lv_date_begin
         DATE_END = lv_date_end
         CAL_ID = lv_cal_id
         ANZTM = lv_anztm
         ANZTJ = lv_anztj
         ANZTBME = lv_anztbme
         USE_BADI = lv_use_badi
    IMPORTING
         DAYS = lv_days
         MONTHS = lv_months
         YEARS = lv_years
         WEEKS = lv_weeks
. " PRICING_DETERMINE_DATES




ABAP code using 7.40 inline data declarations to call FM PRICING_DETERMINE_DATES

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_anztbme) = ' '.
 
 


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!