SAP RP_APPLICANT_VALIDITY_INTERVAL Function Module for Determines existence of applicants in period specified

Search SAP Function Modules

RP_APPLICANT_VALIDITY_INTERVAL is a standard rp applicant validity interval SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines existence of applicants in period specified 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 rp applicant validity interval FM, simply by entering the name RP_APPLICANT_VALIDITY_INTERVAL into the relevant SAP transaction such as SE37 or SE38.

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

Function RP_APPLICANT_VALIDITY_INTERVAL 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 'RP_APPLICANT_VALIDITY_INTERVAL'"Determines existence of applicants in period specified
  EXPORTING
   APLNO =  "Applicant number
   BEGDA =  "Start date (-->input)
   ENDDA =  "End date (-->input)
*  MASSN =  "

 IMPORTING
   LAST_VALID_BEGDA =  "Start date of applicant validity period
   LAST_VALID_ENDDA =  "End date of applicant validity period
   PERNR_INT_APPLICANT =  "Applicant's personnel number
   OTYPE =  "Applicant object type

TABLES
*  VALID_RECORDS =  "Applicant validity intervals

EXCEPTIONS
   NO_VALID_RECORD_IN_INTERVAL = 1    PERNR_OF_APPLICANT_EXISTS_NOT = 2    INCONSISTENCY = 3    ERROR_IN_FEATURE_PRELI = 4 

.

IMPORTING Parameters details for RP_APPLICANT_VALIDITY_INTERVAL

APLNO - Applicant number

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

BEGDA - Start date (-->input)

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

ENDDA - End date (-->input)

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

MASSN -

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

EXPORTING Parameters details for RP_APPLICANT_VALIDITY_INTERVAL

LAST_VALID_BEGDA - Start date of applicant validity period

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

LAST_VALID_ENDDA - End date of applicant validity period

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

PERNR_INT_APPLICANT - Applicant's personnel number

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

OTYPE - Applicant object type

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

TABLES Parameters details for RP_APPLICANT_VALIDITY_INTERVAL

VALID_RECORDS - Applicant validity intervals

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

EXCEPTIONS details

NO_VALID_RECORD_IN_INTERVAL - No valid record in validity period

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

PERNR_OF_APPLICANT_EXISTS_NOT - Applicant's personnel number does not exist

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

INCONSISTENCY - Inconsistency between infotypes 0001 and 4005

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

ERROR_IN_FEATURE_PRELI -

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

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

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