SAP ISM_ORDER_TRANSACTION_CALL Function Module for IS-M/AM: Access Order Transaction









ISM_ORDER_TRANSACTION_CALL is a standard ism order 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 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 transaction call FM, simply by entering the name ISM_ORDER_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_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_TRANSACTION_CALL'"IS-M/AM: Access Order Transaction
EXPORTING
PV_TRTYP = "
PV_LEAVE_TO_TRANSACTION = "
* PV_SKIP_FIRST_SCREEN = "Skip Initial Screen

EXCEPTIONS
NO_AUTH = 1
.




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_TRANSACTION_CALL

PV_TRTYP -

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

PV_LEAVE_TO_TRANSACTION -

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

PV_SKIP_FIRST_SCREEN - Skip Initial Screen

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

EXCEPTIONS details

NO_AUTH -

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

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

DATA:
lv_no_auth  TYPE STRING, "   
lv_pv_trtyp  TYPE TJ180-TRTYP, "   
lv_pv_leave_to_transaction  TYPE XFELD, "   
lv_pv_skip_first_screen  TYPE XFELD. "   

  CALL FUNCTION 'ISM_ORDER_TRANSACTION_CALL'  "IS-M/AM: Access Order Transaction
    EXPORTING
         PV_TRTYP = lv_pv_trtyp
         PV_LEAVE_TO_TRANSACTION = lv_pv_leave_to_transaction
         PV_SKIP_FIRST_SCREEN = lv_pv_skip_first_screen
    EXCEPTIONS
        NO_AUTH = 1
. " ISM_ORDER_TRANSACTION_CALL




ABAP code using 7.40 inline data declarations to call FM ISM_ORDER_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.

 
"SELECT single TRTYP FROM TJ180 INTO @DATA(ld_pv_trtyp).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!