SAP ISH_N2_PMDCALL_EDIT Function Module for









ISH_N2_PMDCALL_EDIT is a standard ish n2 pmdcall edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ish n2 pmdcall edit FM, simply by entering the name ISH_N2_PMDCALL_EDIT into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_N2_PMDCALL_EDIT 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 'ISH_N2_PMDCALL_EDIT'"
EXPORTING
* P_FUNCTION = 'DIS' "ABAP Program, Current Transaction Code
P_DOC_KEY = "IS-H*MED: Key for a Document
* P_DOC_KEY_OLD = "IS-H*MED: Key for a Document
P_DOC_CONTEXT = "Context Information for the Document

IMPORTING
P_RESULT = "Screens, Function Code that Triggered PAI
P_WORST_MSGTY = "IS-H: Most Severe Message Type Generated
P_BAPIRET = "IS-H: Table Type for Structure BAPIRET2
.



IMPORTING Parameters details for ISH_N2_PMDCALL_EDIT

P_FUNCTION - ABAP Program, Current Transaction Code

Data type: SY-TCODE
Default: 'DIS'
Optional: Yes
Call by Reference: Yes

P_DOC_KEY - IS-H*MED: Key for a Document

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

P_DOC_KEY_OLD - IS-H*MED: Key for a Document

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

P_DOC_CONTEXT - Context Information for the Document

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

EXPORTING Parameters details for ISH_N2_PMDCALL_EDIT

P_RESULT - Screens, Function Code that Triggered PAI

Data type: SY-UCOMM
Optional: No
Call by Reference: Yes

P_WORST_MSGTY - IS-H: Most Severe Message Type Generated

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

P_BAPIRET - IS-H: Table Type for Structure BAPIRET2

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

Copy and paste ABAP code example for ISH_N2_PMDCALL_EDIT 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_p_result  TYPE SY-UCOMM, "   
lv_p_function  TYPE SY-TCODE, "   'DIS'
lv_p_doc_key  TYPE RN2DOC_KEY, "   
lv_p_worst_msgty  TYPE ISH_BAPIRETMAXTY, "   
lv_p_bapiret  TYPE ISH_BAPIRET2_TAB_TYPE, "   
lv_p_doc_key_old  TYPE RN2DOC_KEY, "   
lv_p_doc_context  TYPE CL_ISHMED_PMD_CONTEXT. "   

  CALL FUNCTION 'ISH_N2_PMDCALL_EDIT'  "
    EXPORTING
         P_FUNCTION = lv_p_function
         P_DOC_KEY = lv_p_doc_key
         P_DOC_KEY_OLD = lv_p_doc_key_old
         P_DOC_CONTEXT = lv_p_doc_context
    IMPORTING
         P_RESULT = lv_p_result
         P_WORST_MSGTY = lv_p_worst_msgty
         P_BAPIRET = lv_p_bapiret
. " ISH_N2_PMDCALL_EDIT




ABAP code using 7.40 inline data declarations to call FM ISH_N2_PMDCALL_EDIT

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 UCOMM FROM SY INTO @DATA(ld_p_result).
 
"SELECT single TCODE FROM SY INTO @DATA(ld_p_function).
DATA(ld_p_function) = 'DIS'.
 
 
 
 
 
 


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!