SAP ISP_JHEA_GET_UPOS_FOR_EINT Function Module for IS-M: Define Sub-Items for Schedule Lines

Search SAP Function Modules

ISP_JHEA_GET_UPOS_FOR_EINT is a standard isp jhea get upos for eint SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Define Sub-Items for Schedule Lines 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 isp jhea get upos for eint FM, simply by entering the name ISP_JHEA_GET_UPOS_FOR_EINT into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_JHEA_GET_UPOS_FOR_EINT 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 'ISP_JHEA_GET_UPOS_FOR_EINT'"IS-M: Define Sub-Items for Schedule Lines
  EXPORTING
*  PT_RJHAUA =  "
*  PT_RJHAUSI =  "
*  PT_RJHAUW =  "
*  PT_RJHAUV =  "
*  PT_RJHAUO =  "
   PT_RJHAE =  "
   PV_POS_ART =  "

 IMPORTING
   PT_FND_RJHAUA =  "
   PT_FND_RJHAUSI =  "
   PT_FND_RJHAUW =  "
   PT_FND_RJHAUV =  "
   PT_FND_RJHAUO =  "

.

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_SAPLJHEA_001 IS-M/AM: Set Status Characteristics for Item Schedule Lines
EXIT_SAPLJHEA_002 IS-M/AM: Check Completeness and Plausibility of a Schedule Line
EXIT_SAPLJHEA_003 IS-M/AM: Check Completeness and Plausibility of a Sub-Item

IMPORTING Parameters details for ISP_JHEA_GET_UPOS_FOR_EINT

PT_RJHAUA -

Data type: JHA1_RJHAUA_TAB
Optional: Yes
Call by Reference: Yes

PT_RJHAUSI -

Data type: JHA1_RJHAUSI_TAB
Optional: Yes
Call by Reference: Yes

PT_RJHAUW -

Data type: JHA1_RJHAUW_TAB
Optional: Yes
Call by Reference: Yes

PT_RJHAUV -

Data type: JHA1_RJHAUV_TAB
Optional: Yes
Call by Reference: Yes

PT_RJHAUO -

Data type: JHA1_RJHAUO_TAB
Optional: Yes
Call by Reference: Yes

PT_RJHAE -

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

PV_POS_ART -

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

EXPORTING Parameters details for ISP_JHEA_GET_UPOS_FOR_EINT

PT_FND_RJHAUA -

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

PT_FND_RJHAUSI -

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

PT_FND_RJHAUW -

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

PT_FND_RJHAUV -

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

PT_FND_RJHAUO -

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

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

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