SAP ISH_301_UNBV02_FILL Function Module for









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

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



Function ISH_301_UNBV02_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_301_UNBV02_FILL'"
EXPORTING
FILESENDER_IK9 = "
FILERECEIVER_IK9 = "
FILE301NUMBER = "
FILE301NAME = "
CREATIONDATE = "
CREATIONTIME = "

IMPORTING
SEGMENTSTRING = "
.




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_SAPLNC301V02_003 IS-H: DE §301 User Exit for AUF Segment Version 0.2
EXIT_SAPLNC301V02_004 IS-H: DE §301 User Exit for DAU Segment Version 0.2
EXIT_SAPLNC301V02_005 IS-H: DE §301 User Exit for EAD Segment Version 0.2
EXIT_SAPLNC301V02_006 IS-H: DE §301 Fill Routine for EBG Segment Version 0.2
EXIT_SAPLNC301V02_007 IS-H: DE §301 Fill Routine for ENA Segment Version 0.2
EXIT_SAPLNC301V02_008 IS-H: DE §301 Fill Routine for ENT Segment Version 0.2
EXIT_SAPLNC301V02_009 IS-H: DE §301 Fill Routine for ETL Segment Version 0.2
EXIT_SAPLNC301V02_010 IS-H: DE §301 Fill Routine for EZV Segment Version 0.2
EXIT_SAPLNC301V02_011 IS-H: DE §301 Fill Routine for FAB Segment Version 0.1
EXIT_SAPLNC301V02_012 IS-H: DE §301 Fill Routine for FHL Segment Version 0.2
EXIT_SAPLNC301V02_013 IS-H: DE §301 Fill Routine for FKT Segment Version 0.2
EXIT_SAPLNC301V02_014 IS-H: DE §301 Fill Routine for INV Segment Version 0.2
EXIT_SAPLNC301V02_015 IS-H: DE §301 Fill Routine for NAD Segment Version 0.2
EXIT_SAPLNC301V02_016 IS-H: DE §301 Fill Routine for RBG Segment Version 0.2
EXIT_SAPLNC301V02_017 IS-H: DE §301 Fill Routine for REC Segment Version 0.2
EXIT_SAPLNC301V02_018 IS-H: DE §301 Fill Routine for RZA Segment Version 0.2
EXIT_SAPLNC301V02_019 IS-H: DE §301 Fill Routine for TXT Segment Version 0.2
EXIT_SAPLNC301V02_020 IS-H: DE §301 Fill Routine for ZLG Segment Version 0.2

IMPORTING Parameters details for ISH_301_UNBV02_FILL

FILESENDER_IK9 -

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

FILERECEIVER_IK9 -

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

FILE301NUMBER -

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

FILE301NAME -

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

CREATIONDATE -

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

CREATIONTIME -

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

EXPORTING Parameters details for ISH_301_UNBV02_FILL

SEGMENTSTRING -

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

Copy and paste ABAP code example for ISH_301_UNBV02_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_creationdate  TYPE SY-DATUM, "   
lv_creationtime  TYPE SY-UZEIT. "   

  CALL FUNCTION 'ISH_301_UNBV02_FILL'  "
    EXPORTING
         FILESENDER_IK9 = lv_filesender_ik9
         FILERECEIVER_IK9 = lv_filereceiver_ik9
         FILE301NUMBER = lv_file301number
         FILE301NAME = lv_file301name
         CREATIONDATE = lv_creationdate
         CREATIONTIME = lv_creationtime
    IMPORTING
         SEGMENTSTRING = lv_segmentstring
. " ISH_301_UNBV02_FILL




ABAP code using 7.40 inline data declarations to call FM ISH_301_UNBV02_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).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_creationdate).
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_creationtime).
 


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!