SAP ISM_PHASE_MODEL_CREATE Function Module for Create Phase Model









ISM_PHASE_MODEL_CREATE is a standard ism phase model create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Phase Model 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 phase model create FM, simply by entering the name ISM_PHASE_MODEL_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_PHASE_MODEL_CREATE 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_PHASE_MODEL_CREATE'"Create Phase Model
  EXPORTING
   IM_MODELL =  "IS-M/SD: Phase Shipping - Model
*  IM_XTEST =  "Test Mode
*  IM_AUART_TAB =  "IS-M: Range Table for AUART

 IMPORTING
   EX_FIELDNAME =  "

TABLES
*  IM_GEO_TAB =  "IS-M/SD: Phase Shipping - Geo.Units
*  IM_ISSUE_TAB =  "IS-M/SD: Phase Shipping - Media Issues
*  IM_DATE_TAB =  "IS-M/SD: Phase-Based Shipping - Dates per Media Issue
*  IM_CONTRACT_TAB =  "IS-M/SD: Phase Shipping - Contracts Assigned Explicitly
*  RETURN =  "IS-M: Internal Structure for Transferring Error Messages

EXCEPTIONS
   INVALID = 1    INSERT_ERROR = 2    EXISTING = 3    DEMAND_ERROR = 4
.



IMPORTING Parameters details for ISM_PHASE_MODEL_CREATE

IM_MODELL - IS-M/SD: Phase Shipping - Model

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

IM_XTEST - Test Mode

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

IM_AUART_TAB - IS-M: Range Table for AUART

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

EXPORTING Parameters details for ISM_PHASE_MODEL_CREATE

EX_FIELDNAME -

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

TABLES Parameters details for ISM_PHASE_MODEL_CREATE

IM_GEO_TAB - IS-M/SD: Phase Shipping - Geo.Units

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

IM_ISSUE_TAB - IS-M/SD: Phase Shipping - Media Issues

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

IM_DATE_TAB - IS-M/SD: Phase-Based Shipping - Dates per Media Issue

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

IM_CONTRACT_TAB - IS-M/SD: Phase Shipping - Contracts Assigned Explicitly

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

RETURN - IS-M: Internal Structure for Transferring Error Messages

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

EXCEPTIONS details

INVALID - Error identified

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

INSERT_ERROR - Error while adding

Data type:
Optional: No
Call by Reference: Yes

EXISTING -

Data type:
Optional: No
Call by Reference: Yes

DEMAND_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_PHASE_MODEL_CREATE 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_invalid  TYPE STRING, "   
lv_im_modell  TYPE JVTPHMODELL, "   
lt_im_geo_tab  TYPE STANDARD TABLE OF JVTPHGEO, "   
lv_ex_fieldname  TYPE FIELDNAME, "   
lv_im_xtest  TYPE XFLAG, "   
lt_im_issue_tab  TYPE STANDARD TABLE OF JVTPHISSUE, "   
lv_insert_error  TYPE JVTPHISSUE, "   
lv_existing  TYPE JVTPHISSUE, "   
lt_im_date_tab  TYPE STANDARD TABLE OF JVTPHDATE, "   
lv_im_auart_tab  TYPE RJKSD_AUART_RANGE_TAB, "   
lv_demand_error  TYPE RJKSD_AUART_RANGE_TAB, "   
lt_im_contract_tab  TYPE STANDARD TABLE OF JVTPHCONTRACT, "   
lt_return  TYPE STANDARD TABLE OF RJMSG. "   

  CALL FUNCTION 'ISM_PHASE_MODEL_CREATE'  "Create Phase Model
    EXPORTING
         IM_MODELL = lv_im_modell
         IM_XTEST = lv_im_xtest
         IM_AUART_TAB = lv_im_auart_tab
    IMPORTING
         EX_FIELDNAME = lv_ex_fieldname
    TABLES
         IM_GEO_TAB = lt_im_geo_tab
         IM_ISSUE_TAB = lt_im_issue_tab
         IM_DATE_TAB = lt_im_date_tab
         IM_CONTRACT_TAB = lt_im_contract_tab
         RETURN = lt_return
    EXCEPTIONS
        INVALID = 1
        INSERT_ERROR = 2
        EXISTING = 3
        DEMAND_ERROR = 4
. " ISM_PHASE_MODEL_CREATE




ABAP code using 7.40 inline data declarations to call FM ISM_PHASE_MODEL_CREATE

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



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!