SAP HR_99S_BUILD_PERIOD_JOIN Function Module for Build a join between two tables of validity periods

Search SAP Function Modules

HR_99S_BUILD_PERIOD_JOIN is a standard hr 99s build period join SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Build a join between two tables of validity periods 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 hr 99s build period join FM, simply by entering the name HR_99S_BUILD_PERIOD_JOIN into the relevant SAP transaction such as SE37 or SE38.

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

Function HR_99S_BUILD_PERIOD_JOIN 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 'HR_99S_BUILD_PERIOD_JOIN'"Build a join between two tables of validity periods
  EXPORTING
   IM_BEGDA =  "Start Date
   IM_ENDDA =  "End Date
   IM_VALIDITY_TABLE1 =  "First table with validity dates to join
   IM_VALIDITY_TABLE2 =  "Second table with validity dates to join

 IMPORTING
   EX_PERIOD_JOIN_TABLE =  "Table with joined validity periods
   EX_RETURN_CODE =  "Return Value, Return Value After ABAP Statements

.

IMPORTING Parameters details for HR_99S_BUILD_PERIOD_JOIN

IM_BEGDA - Start Date

Data type: BEGDA
Optional: No
Call by Reference: Yes

IM_ENDDA - End Date

Data type: ENDDA
Optional: No
Call by Reference: Yes

IM_VALIDITY_TABLE1 - First table with validity dates to join

Data type: TABLE
Optional: No
Call by Reference: Yes

IM_VALIDITY_TABLE2 - Second table with validity dates to join

Data type: TABLE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for HR_99S_BUILD_PERIOD_JOIN

EX_PERIOD_JOIN_TABLE - Table with joined validity periods

Data type: P99SU_TAB_VALIDITY_DATES
Optional: No
Call by Reference: Yes

EX_RETURN_CODE - Return Value, Return Value After ABAP Statements

Data type: SYSUBRC
Optional: No
Call by Reference: Yes

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

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