SAP ISM_COA_EXPORT Function Module for IS-M: Export Contract
ISM_COA_EXPORT is a standard ism coa export 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: Export Contract 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 coa export FM, simply by entering the name ISM_COA_EXPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHWA2
Program Name: SAPLJHWA2
Main Program: SAPLJHWA2
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_COA_EXPORT 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_COA_EXPORT'"IS-M: Export Contract.
EXPORTING
PV_VTNR = "Contract Number
IMPORTING
PS_COA = "Contract
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_SAPLJHWA2_001 IS-M: Customer-Specific Fields in Assignment Overview
EXIT_SAPLJHWA2_002 IS-M: Fill Dynamic Part for View JHVGAV
IMPORTING Parameters details for ISM_COA_EXPORT
PV_VTNR - Contract Number
Data type: JHTVKO-VTNROptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_COA_EXPORT
PS_COA - Contract
Data type: JHW1_COA_STROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_COA_EXPORT 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_ps_coa | TYPE JHW1_COA_STR, " | |||
| lv_pv_vtnr | TYPE JHTVKO-VTNR. " |
|   CALL FUNCTION 'ISM_COA_EXPORT' "IS-M: Export Contract |
| EXPORTING | ||
| PV_VTNR | = lv_pv_vtnr | |
| IMPORTING | ||
| PS_COA | = lv_ps_coa | |
| . " ISM_COA_EXPORT | ||
ABAP code using 7.40 inline data declarations to call FM ISM_COA_EXPORT
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 VTNR FROM JHTVKO INTO @DATA(ld_pv_vtnr). | ||||
Search for further information about these or an SAP related objects