SAP ISM_PACKAGE_ELEMENT_CHECK Function Module for Check Whether a Package Can Be Modified

Search SAP Function Modules

ISM_PACKAGE_ELEMENT_CHECK is a standard ism package element check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether a Package Can Be Modified 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 ism package element check FM, simply by entering the name ISM_PACKAGE_ELEMENT_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_PACKAGE_ELEMENT_CHECK 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 'ISM_PACKAGE_ELEMENT_CHECK'"Check Whether a Package Can Be Modified
  EXPORTING
   PV_AVM_NR =  "IS-M/AM: Sales Document Number
   PV_POS_NR =  "IS-M: Order Item Number
   PS_RJHAORDER =  "IS-M/AM: Sales Document
*  PV_FLG_DIALOG = CON_ANGEKREUZT "Call in Dialog

EXCEPTIONS
   PK_ELEM_CANCELLED = 1    PK_ELEM_PROCESSED = 2    PK_ELEM_BILLED = 3    PK_ELEM_MSG_SENT = 4 

.

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_SAPLJHPA_001 IS-M/AM: Set Status Characteristics for an Ad Item
EXIT_SAPLJHPA_002 IS-M/AM: Set Status Characteristics for an Ad Insert Item
EXIT_SAPLJHPA_003 IS-M/AM: Set Status Characteristics for a Service Item
EXIT_SAPLJHPA_004 IS-M/AM: Box Number Assignment
EXIT_SAPLJHPA_006 IS-M/AM: Check Completeness and Plausibility of an Item
EXIT_SAPLJHPA_007 IS-M/AM: Define Default Item
EXIT_SAPLJHPA_008 IS-M/AM: Check Completeness and Plausibility of Date Information
EXIT_SAPLJHPA_009 IS-M/AM: Modification of F4 Help for Content Components
EXIT_SAPLJHPA_010 IS-M/AM: Modify Advertiser Assignment
EXIT_SAPLJHPA_011 IS-M/AM: Menu Exit OPM Item Details
EXIT_SAPLJHPA_012 IS-M/AM: Set Status Characteristics for a Commercial Item
EXIT_SAPLJHPA_013 IS-M/AM: Define Default Item Category
EXIT_SAPLJHPA_014 IS-M/AM: Represent Dependencies for Item Characteristics
EXIT_SAPLJHPA_015 IS-M/AM: Set Status Characteristics for a Distribution Item
EXIT_SAPLJHPA_016 IS-M/AM: Set Status Characteristics for an Online Item
EXIT_SAPLJHPA_017 IS-M/AM: Trigger Billing Dataset Generation
EXIT_SAPLJHPA_018 IS-M/AM: Check Completeness and Plausibility of an Item
EXIT_SAPLJHPA_019 IS-M/AM: Trigger Schedule Line Generation
EXIT_SAPLJHPA_020 IS-M/AM: Set Status Characteristics for a Package Item

IMPORTING Parameters details for ISM_PACKAGE_ELEMENT_CHECK

PV_AVM_NR - IS-M/AM: Sales Document Number

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

PV_POS_NR - IS-M: Order Item Number

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

PS_RJHAORDER - IS-M/AM: Sales Document

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

PV_FLG_DIALOG - Call in Dialog

Data type: XFELD
Default: CON_ANGEKREUZT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

PK_ELEM_CANCELLED -

Data type:
Optional: No
Call by Reference: Yes

PK_ELEM_PROCESSED -

Data type:
Optional: No
Call by Reference: Yes

PK_ELEM_BILLED -

Data type:
Optional: No
Call by Reference: Yes

PK_ELEM_MSG_SENT -

Data type:
Optional: No
Call by Reference: Yes

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

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