SAP ISH_321_MSG_LAYOUT Function Module for









ISH_321_MSG_LAYOUT is a standard ish 321 msg layout 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 321 msg layout FM, simply by entering the name ISH_321_MSG_LAYOUT into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_321_MSG_LAYOUT 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_321_MSG_LAYOUT'"
EXPORTING
I_NC301B = "
I_NC301D = "
* I_CRLF_REQUESTED = ' ' "

TABLES
INC301M = "
* ENC301MLY = "

EXCEPTIONS
LAYOUT_CHANGE_FAILED = 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_SAPLN1C3_001

IMPORTING Parameters details for ISH_321_MSG_LAYOUT

I_NC301B -

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

I_NC301D -

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

I_CRLF_REQUESTED -

Data type: RNCOM-XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for ISH_321_MSG_LAYOUT

INC301M -

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

ENC301MLY -

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

EXCEPTIONS details

LAYOUT_CHANGE_FAILED -

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

Copy and paste ABAP code example for ISH_321_MSG_LAYOUT 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:
lt_inc301m  TYPE STANDARD TABLE OF NC301M, "   
lv_i_nc301b  TYPE NC301B, "   
lv_layout_change_failed  TYPE NC301B, "   
lv_i_nc301d  TYPE NC301D, "   
lt_enc301mly  TYPE STANDARD TABLE OF RNC301MLY, "   
lv_i_crlf_requested  TYPE RNCOM-XFELD. "   SPACE

  CALL FUNCTION 'ISH_321_MSG_LAYOUT'  "
    EXPORTING
         I_NC301B = lv_i_nc301b
         I_NC301D = lv_i_nc301d
         I_CRLF_REQUESTED = lv_i_crlf_requested
    TABLES
         INC301M = lt_inc301m
         ENC301MLY = lt_enc301mly
    EXCEPTIONS
        LAYOUT_CHANGE_FAILED = 1
. " ISH_321_MSG_LAYOUT




ABAP code using 7.40 inline data declarations to call FM ISH_321_MSG_LAYOUT

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 XFELD FROM RNCOM INTO @DATA(ld_i_crlf_requested).
DATA(ld_i_crlf_requested) = ' '.
 


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!