SAP ISH_301_ORDERFILE_WRITE_UE Function Module for

Search SAP Function Modules

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

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

Function ISH_301_ORDERFILE_WRITE_UE 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_ORDERFILE_WRITE_UE'"
  EXPORTING
   I_PROCEDURE =  "
   I_NC301D =  "
   I_SAPCONTENT =  "
   I_SAPLENGTH =  "
   I_FILENAME =  "
   I_FULLFILENAME =  "
   I_FULLORDERFILENAME =  "
   I_FILELENGTH =  "
   I_NC301P =  "
   I_NC301B =  "

 IMPORTING
   E_CUSTOMERCONTENT =  "
   E_CUSTOMERLENGTH =  "

EXCEPTIONS
   FILECREATION_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_SAPLNC12_001 IS-H: User Exit for Case Exclusions
EXIT_SAPLNC12_002 IS-H: User Exit for Patient Exclusion
EXIT_SAPLNC12_003 IS-H EDI User Exit Order File Name in EDI Procedure
EXIT_SAPLNC12_004 IS-H §301 User Exit Write Order File (Outbound)

IMPORTING Parameters details for ISH_301_ORDERFILE_WRITE_UE

I_PROCEDURE -

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

I_NC301D -

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

I_SAPCONTENT -

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

I_SAPLENGTH -

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

I_FILENAME -

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

I_FULLFILENAME -

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

I_FULLORDERFILENAME -

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

I_FILELENGTH -

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

I_NC301P -

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

I_NC301B -

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

EXPORTING Parameters details for ISH_301_ORDERFILE_WRITE_UE

E_CUSTOMERCONTENT -

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

E_CUSTOMERLENGTH -

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

EXCEPTIONS details

FILECREATION_FAILED -

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

Copy and paste ABAP code example for ISH_301_ORDERFILE_WRITE_UE 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.

ABAP code using 7.40 inline data declarations to call FM ISH_301_ORDERFILE_WRITE_UE

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