SAP ISM_ADDRESS_OUTPUT_FIND Function Module for IS-M: Output Determination
ISM_ADDRESS_OUTPUT_FIND is a standard ism address output find 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: Output Determination 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 address output find FM, simply by entering the name ISM_ADDRESS_OUTPUT_FIND into the relevant SAP transaction such as SE37 or SE38.
Function Group: JGAD1
Program Name: SAPLJGAD1
Main Program: SAPLJGAD1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_ADDRESS_OUTPUT_FIND 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_ADDRESS_OUTPUT_FIND'"IS-M: Output Determination.
EXPORTING
IV_OBJKY = "Object Key
IV_TRTYP = "Transaction Type
IV_JPARVW = "IS-M: Business Partner Role
IV_WDAT1 = "Valid From Date
IV_WDAT2 = "Valid to Date
IV_WDAT1_OLD = "Valid From Date
IV_WDAT2_OLD = "Valid to Date
IS_JGTSADR = "IS-M: Extended Address Management
IS_JGTSADR_OLD = "IS-M: Extended Address Management
* IV_KALSM = "Procedure (Pricing, Output Control, Acct. Det., Costing,...)
IMPORTING
ET_PART = "IS-M/SD: Table - Output Partners
EXCEPTIONS
NO_PROCEDURE = 1
IMPORTING Parameters details for ISM_ADDRESS_OUTPUT_FIND
IV_OBJKY - Object Key
Data type: NAST-OBJKYOptional: No
Call by Reference: Yes
IV_TRTYP - Transaction Type
Data type: TRTYPOptional: No
Call by Reference: Yes
IV_JPARVW - IS-M: Business Partner Role
Data type: JPARVWOptional: No
Call by Reference: Yes
IV_WDAT1 - Valid From Date
Data type: JGTADRA-WDAT1Optional: No
Call by Reference: Yes
IV_WDAT2 - Valid to Date
Data type: JGTADRA-WDAT2Optional: No
Call by Reference: Yes
IV_WDAT1_OLD - Valid From Date
Data type: JGTADRA-WDAT1Optional: No
Call by Reference: Yes
IV_WDAT2_OLD - Valid to Date
Data type: JGTADRA-WDAT2Optional: No
Call by Reference: Yes
IS_JGTSADR - IS-M: Extended Address Management
Data type: JGTSADROptional: No
Call by Reference: Yes
IS_JGTSADR_OLD - IS-M: Extended Address Management
Data type: JGTSADROptional: No
Call by Reference: Yes
IV_KALSM - Procedure (Pricing, Output Control, Acct. Det., Costing,...)
Data type: T683-KALSMOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISM_ADDRESS_OUTPUT_FIND
ET_PART - IS-M/SD: Table - Output Partners
Data type: ISM_MSGPA_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_PROCEDURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_ADDRESS_OUTPUT_FIND 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_et_part | TYPE ISM_MSGPA_TAB, " | |||
| lv_iv_objky | TYPE NAST-OBJKY, " | |||
| lv_no_procedure | TYPE NAST, " | |||
| lv_iv_trtyp | TYPE TRTYP, " | |||
| lv_iv_jparvw | TYPE JPARVW, " | |||
| lv_iv_wdat1 | TYPE JGTADRA-WDAT1, " | |||
| lv_iv_wdat2 | TYPE JGTADRA-WDAT2, " | |||
| lv_iv_wdat1_old | TYPE JGTADRA-WDAT1, " | |||
| lv_iv_wdat2_old | TYPE JGTADRA-WDAT2, " | |||
| lv_is_jgtsadr | TYPE JGTSADR, " | |||
| lv_is_jgtsadr_old | TYPE JGTSADR, " | |||
| lv_iv_kalsm | TYPE T683-KALSM. " |
|   CALL FUNCTION 'ISM_ADDRESS_OUTPUT_FIND' "IS-M: Output Determination |
| EXPORTING | ||
| IV_OBJKY | = lv_iv_objky | |
| IV_TRTYP | = lv_iv_trtyp | |
| IV_JPARVW | = lv_iv_jparvw | |
| IV_WDAT1 | = lv_iv_wdat1 | |
| IV_WDAT2 | = lv_iv_wdat2 | |
| IV_WDAT1_OLD | = lv_iv_wdat1_old | |
| IV_WDAT2_OLD | = lv_iv_wdat2_old | |
| IS_JGTSADR | = lv_is_jgtsadr | |
| IS_JGTSADR_OLD | = lv_is_jgtsadr_old | |
| IV_KALSM | = lv_iv_kalsm | |
| IMPORTING | ||
| ET_PART | = lv_et_part | |
| EXCEPTIONS | ||
| NO_PROCEDURE = 1 | ||
| . " ISM_ADDRESS_OUTPUT_FIND | ||
ABAP code using 7.40 inline data declarations to call FM ISM_ADDRESS_OUTPUT_FIND
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 OBJKY FROM NAST INTO @DATA(ld_iv_objky). | ||||
| "SELECT single WDAT1 FROM JGTADRA INTO @DATA(ld_iv_wdat1). | ||||
| "SELECT single WDAT2 FROM JGTADRA INTO @DATA(ld_iv_wdat2). | ||||
| "SELECT single WDAT1 FROM JGTADRA INTO @DATA(ld_iv_wdat1_old). | ||||
| "SELECT single WDAT2 FROM JGTADRA INTO @DATA(ld_iv_wdat2_old). | ||||
| "SELECT single KALSM FROM T683 INTO @DATA(ld_iv_kalsm). | ||||
Search for further information about these or an SAP related objects