SAP ISH_302_UNBV40_FILL Function Module for









ISH_302_UNBV40_FILL is a standard ish 302 unbv40 fill 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 302 unbv40 fill FM, simply by entering the name ISH_302_UNBV40_FILL into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_302_UNBV40_FILL 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_302_UNBV40_FILL'"
EXPORTING
FILESENDER_IK9 = "
FILERECEIVER_IK9 = "
FILE301NUMBER = "
FILE301NAME = "
INC301D = "

IMPORTING
SEGMENTSTRING = "
.



IMPORTING Parameters details for ISH_302_UNBV40_FILL

FILESENDER_IK9 -

Data type:
Optional: No
Call by Reference: Yes

FILERECEIVER_IK9 -

Data type:
Optional: No
Call by Reference: Yes

FILE301NUMBER -

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

FILE301NAME -

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

INC301D -

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

EXPORTING Parameters details for ISH_302_UNBV40_FILL

SEGMENTSTRING -

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

Copy and paste ABAP code example for ISH_302_UNBV40_FILL 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_segmentstring  TYPE RNCMAILGR, "   
lv_filesender_ik9  TYPE RNCMAILGR, "   
lv_filereceiver_ik9  TYPE RNCMAILGR, "   
lv_file301number  TYPE NC301B-LF301M, "   
lv_file301name  TYPE NC301D-FILE301, "   
lv_inc301d  TYPE NC301D. "   

  CALL FUNCTION 'ISH_302_UNBV40_FILL'  "
    EXPORTING
         FILESENDER_IK9 = lv_filesender_ik9
         FILERECEIVER_IK9 = lv_filereceiver_ik9
         FILE301NUMBER = lv_file301number
         FILE301NAME = lv_file301name
         INC301D = lv_inc301d
    IMPORTING
         SEGMENTSTRING = lv_segmentstring
. " ISH_302_UNBV40_FILL




ABAP code using 7.40 inline data declarations to call FM ISH_302_UNBV40_FILL

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 LF301M FROM NC301B INTO @DATA(ld_file301number).
 
"SELECT single FILE301 FROM NC301D INTO @DATA(ld_file301name).
 
 


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!