SAP PTRV_DETERMINE_ANSTD_AT_DATE Function Module for
PTRV_DETERMINE_ANSTD_AT_DATE is a standard ptrv determine anstd at date SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ptrv determine anstd at date FM, simply by entering the name PTRV_DETERMINE_ANSTD_AT_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRTRV_UTIL
Program Name: SAPLHRTRV_UTIL
Main Program: SAPLHRTRV_UTIL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PTRV_DETERMINE_ANSTD_AT_DATE 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 'PTRV_DETERMINE_ANSTD_AT_DATE'".
EXPORTING
DATE = "
ERGRU = "
P_ZIEL = "
P_ABZUG = "
P_BELEG = "
P_EXBEL = "
* TIME = "
HEAD = "
PERIO = "
HOME_LAND = "
MOLGA = "
ASSIGNMENT = "
BUKRS = "
ERKLA = "
IMPORTING
PFALZ_ZUSCHUSS = "
CHANGING
ANSTD = "
ANSTD_FZ = "
* ZLAND_VP = "
* ZLAND_VP_FZ = "
* REINR = "
H_SUBRC = "
* PT_HEAD = "
* RGION_VP = "
* RGION_VP_FZ = "
IMPORTING Parameters details for PTRV_DETERMINE_ANSTD_AT_DATE
DATE -
Data type: PTP02-DATV1Optional: No
Call by Reference: Yes
ERGRU -
Data type: ERGRUOptional: No
Call by Reference: Yes
P_ZIEL -
Data type: PTK05_ITABOptional: No
Call by Reference: Yes
P_ABZUG -
Data type: PTK04_ITABOptional: No
Call by Reference: Yes
P_BELEG -
Data type: PTK03_ITABOptional: No
Call by Reference: Yes
P_EXBEL -
Data type: PTK33_ITABOptional: No
Call by Reference: Yes
TIME -
Data type: PTP02-UHRV1Optional: Yes
Call by Reference: Yes
HEAD -
Data type: PTRV_HEADOptional: No
Call by Reference: Yes
PERIO -
Data type: PTRV_PERIOOptional: No
Call by Reference: Yes
HOME_LAND -
Data type: T706V-LNDGROptional: No
Call by Reference: Yes
MOLGA -
Data type: T500P-MOLGAOptional: No
Call by Reference: Yes
ASSIGNMENT -
Data type: COptional: No
Call by Reference: Yes
BUKRS -
Data type: BUKRSOptional: No
Call by Reference: Yes
ERKLA -
Data type: ERKLAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PTRV_DETERMINE_ANSTD_AT_DATE
PFALZ_ZUSCHUSS -
Data type: BOOLEANOptional: No
Call by Reference: Yes
CHANGING Parameters details for PTRV_DETERMINE_ANSTD_AT_DATE
ANSTD -
Data type: T706V-ANSTDOptional: No
Call by Reference: Yes
ANSTD_FZ -
Data type: T706V-ANSTDOptional: No
Call by Reference: Yes
ZLAND_VP -
Data type: PTP02-ZLANDOptional: Yes
Call by Reference: Yes
ZLAND_VP_FZ -
Data type: PTP02-ZLANDOptional: Yes
Call by Reference: Yes
REINR -
Data type: PTP02-REINROptional: Yes
Call by Reference: Yes
H_SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
PT_HEAD -
Data type: PTRV_HEAD_ITABOptional: Yes
Call by Reference: Yes
RGION_VP -
Data type: PTP02-HRGIOOptional: Yes
Call by Reference: Yes
RGION_VP_FZ -
Data type: PTP02-HRGIOOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for PTRV_DETERMINE_ANSTD_AT_DATE 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_date | TYPE PTP02-DATV1, " | |||
| lv_anstd | TYPE T706V-ANSTD, " | |||
| lv_pfalz_zuschuss | TYPE BOOLEAN, " | |||
| lv_ergru | TYPE ERGRU, " | |||
| lv_p_ziel | TYPE PTK05_ITAB, " | |||
| lv_p_abzug | TYPE PTK04_ITAB, " | |||
| lv_p_beleg | TYPE PTK03_ITAB, " | |||
| lv_p_exbel | TYPE PTK33_ITAB, " | |||
| lv_time | TYPE PTP02-UHRV1, " | |||
| lv_anstd_fz | TYPE T706V-ANSTD, " | |||
| lv_head | TYPE PTRV_HEAD, " | |||
| lv_zland_vp | TYPE PTP02-ZLAND, " | |||
| lv_perio | TYPE PTRV_PERIO, " | |||
| lv_zland_vp_fz | TYPE PTP02-ZLAND, " | |||
| lv_reinr | TYPE PTP02-REINR, " | |||
| lv_home_land | TYPE T706V-LNDGR, " | |||
| lv_molga | TYPE T500P-MOLGA, " | |||
| lv_h_subrc | TYPE SY-SUBRC, " | |||
| lv_pt_head | TYPE PTRV_HEAD_ITAB, " | |||
| lv_assignment | TYPE C, " | |||
| lv_bukrs | TYPE BUKRS, " | |||
| lv_rgion_vp | TYPE PTP02-HRGIO, " | |||
| lv_erkla | TYPE ERKLA, " | |||
| lv_rgion_vp_fz | TYPE PTP02-HRGIO. " |
|   CALL FUNCTION 'PTRV_DETERMINE_ANSTD_AT_DATE' " |
| EXPORTING | ||
| DATE | = lv_date | |
| ERGRU | = lv_ergru | |
| P_ZIEL | = lv_p_ziel | |
| P_ABZUG | = lv_p_abzug | |
| P_BELEG | = lv_p_beleg | |
| P_EXBEL | = lv_p_exbel | |
| TIME | = lv_time | |
| HEAD | = lv_head | |
| PERIO | = lv_perio | |
| HOME_LAND | = lv_home_land | |
| MOLGA | = lv_molga | |
| ASSIGNMENT | = lv_assignment | |
| BUKRS | = lv_bukrs | |
| ERKLA | = lv_erkla | |
| IMPORTING | ||
| PFALZ_ZUSCHUSS | = lv_pfalz_zuschuss | |
| CHANGING | ||
| ANSTD | = lv_anstd | |
| ANSTD_FZ | = lv_anstd_fz | |
| ZLAND_VP | = lv_zland_vp | |
| ZLAND_VP_FZ | = lv_zland_vp_fz | |
| REINR | = lv_reinr | |
| H_SUBRC | = lv_h_subrc | |
| PT_HEAD | = lv_pt_head | |
| RGION_VP | = lv_rgion_vp | |
| RGION_VP_FZ | = lv_rgion_vp_fz | |
| . " PTRV_DETERMINE_ANSTD_AT_DATE | ||
ABAP code using 7.40 inline data declarations to call FM PTRV_DETERMINE_ANSTD_AT_DATE
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 DATV1 FROM PTP02 INTO @DATA(ld_date). | ||||
| "SELECT single ANSTD FROM T706V INTO @DATA(ld_anstd). | ||||
| "SELECT single UHRV1 FROM PTP02 INTO @DATA(ld_time). | ||||
| "SELECT single ANSTD FROM T706V INTO @DATA(ld_anstd_fz). | ||||
| "SELECT single ZLAND FROM PTP02 INTO @DATA(ld_zland_vp). | ||||
| "SELECT single ZLAND FROM PTP02 INTO @DATA(ld_zland_vp_fz). | ||||
| "SELECT single REINR FROM PTP02 INTO @DATA(ld_reinr). | ||||
| "SELECT single LNDGR FROM T706V INTO @DATA(ld_home_land). | ||||
| "SELECT single MOLGA FROM T500P INTO @DATA(ld_molga). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_h_subrc). | ||||
| "SELECT single HRGIO FROM PTP02 INTO @DATA(ld_rgion_vp). | ||||
| "SELECT single HRGIO FROM PTP02 INTO @DATA(ld_rgion_vp_fz). | ||||
Search for further information about these or an SAP related objects