SAP ISM_ORDER_OBJ_TRANSACTION_CALL Function Module for IS-M/AM: Access Order Transaction for an Order Object

Search SAP Function Modules

ISM_ORDER_OBJ_TRANSACTION_CALL is a standard ism order obj transaction call 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/AM: Access Order Transaction for an Order Object 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 order obj transaction call FM, simply by entering the name ISM_ORDER_OBJ_TRANSACTION_CALL into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_ORDER_OBJ_TRANSACTION_CALL 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_ORDER_OBJ_TRANSACTION_CALL'"IS-M/AM: Access Order Transaction for an Order Object
  EXPORTING
   PV_TRTYP =  "
*  PV_POS_ART =  "IS-M: Order-Publishing-Media - Item Type
*  PV_FCODE =  "Function Code
*  PV_GPAG =  "Business Partner: Sold-to Party
*  PV_AUART =  "IS-M: Sales Document Type
*  PV_VKORG =  "Sales Organization
*  PV_VTWEG =  "Distribution Channel
*  PV_SPART =  "Division
*  PV_VKBUR =  "Sales Office
*  PV_VKGRP =  "Sales Group
*  PV_AVM_NR =  "IS-M: Order
*  PV_POS_NR =  "IS-M: Order Item Number
*  PV_UPOS_NR =  "IS-M: Order Sub-Item Number
*  PV_EIN_NR =  "IS-M: Schedule Line
*  PV_GRUPPABRNR =  "IS-M/AM: Billing Dataset
*  PV_MOTIV =  "IS-M: Order Ad Spec Number (Ad)
*  PV_DRVORL_NR =  "IS-M: Ad Spec Master
*  PV_CALL_LEVEL = CON_LEVEL_JHAK "IS-M: Order Level Accessed

EXCEPTIONS
   NO_AUTH = 1    MISSING_INPUT = 2    WRONG_CALL_LEVEL = 3 

.

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_SAPLJHA4_001 IS-M/AM: TOP_OF_PAGE Enhancement in Central Access Item Overviews
EXIT_SAPLJHA4_002 IS-M/AM: Item Data in Central Access Enhancement
EXIT_SAPLJHA4_003 IS-M/AM: Field Catalog for Item List in Central Access
EXIT_SAPLJHA4_004 IS-M/AM: Function Code Exclusion for Central Access Item List

IMPORTING Parameters details for ISM_ORDER_OBJ_TRANSACTION_CALL

PV_TRTYP -

Data type: TJ180-TRTYP
Optional: No
Call by Reference: Yes

PV_POS_ART - IS-M: Order-Publishing-Media - Item Type

Data type: RJHMEMORY-POS_ART
Optional: Yes
Call by Reference: Yes

PV_FCODE - Function Code

Data type: RJHMEMORY-FCODE
Optional: Yes
Call by Reference: Yes

PV_GPAG - Business Partner: Sold-to Party

Data type: RJHMEMORY-GPAG
Optional: Yes
Call by Reference: Yes

PV_AUART - IS-M: Sales Document Type

Data type: RJHMEMORY-AUART
Optional: Yes
Call by Reference: Yes

PV_VKORG - Sales Organization

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

PV_VTWEG - Distribution Channel

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

PV_SPART - Division

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

PV_VKBUR - Sales Office

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

PV_VKGRP - Sales Group

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

PV_AVM_NR - IS-M: Order

Data type: RJHMEMORY-AVM_NR
Optional: Yes
Call by Reference: Yes

PV_POS_NR - IS-M: Order Item Number

Data type: RJHMEMORY-POS_NR
Optional: Yes
Call by Reference: Yes

PV_UPOS_NR - IS-M: Order Sub-Item Number

Data type: RJHMEMORY-UPOS_NR
Optional: Yes
Call by Reference: Yes

PV_EIN_NR - IS-M: Schedule Line

Data type: RJHMEMORY-EIN_NR
Optional: Yes
Call by Reference: Yes

PV_GRUPPABRNR - IS-M/AM: Billing Dataset

Data type: RJHMEMORY-GRUPPABRNR
Optional: Yes
Call by Reference: Yes

PV_MOTIV - IS-M: Order Ad Spec Number (Ad)

Data type: RJHMEMORY-MOTIV
Optional: Yes
Call by Reference: Yes

PV_DRVORL_NR - IS-M: Ad Spec Master

Data type: RJHMEMORY-DRVORL_NR
Optional: Yes
Call by Reference: Yes

PV_CALL_LEVEL - IS-M: Order Level Accessed

Data type: RJHMEMORY-CALL_LEVEL
Default: CON_LEVEL_JHAK
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_AUTH -

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

MISSING_INPUT -

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

WRONG_CALL_LEVEL -

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

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

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