SAP NFE_DOCUMENT_READ_RFC Function Module for RFC module to fetch NF Document data









NFE_DOCUMENT_READ_RFC is a standard nfe document read rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RFC module to fetch NF Document data 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 nfe document read rfc FM, simply by entering the name NFE_DOCUMENT_READ_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_NFE_DOC
Program Name: SAPLCRM_NFE_DOC
Main Program: SAPLCRM_NFE_DOC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function NFE_DOCUMENT_READ_RFC 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 'NFE_DOCUMENT_READ_RFC'"RFC module to fetch NF Document data
  EXPORTING
   IV_REFKEY =  "Reference to source document
   IV_LOGSYS =  "Logical System

 IMPORTING
   EV_DOCNUM =  "Document Number
   EV_NFENUM =  "Nine-Digit Document Number
   EV_SERIES =  "Series
   EV_SUBSER =  "Sub series
   EV_CREDAT =  "Create date
   EV_CRETIM =  "Creation time
   EV_SHTEXT =  "Name of Object Type

EXCEPTIONS
   NF_DOC_NUM_NOT_FOUND = 1    NF_NINE_DIG_NUM_NOT_FOUND = 2
.



IMPORTING Parameters details for NFE_DOCUMENT_READ_RFC

IV_REFKEY - Reference to source document

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

IV_LOGSYS - Logical System

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

EXPORTING Parameters details for NFE_DOCUMENT_READ_RFC

EV_DOCNUM - Document Number

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

EV_NFENUM - Nine-Digit Document Number

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

EV_SERIES - Series

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

EV_SUBSER - Sub series

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

EV_CREDAT - Create date

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

EV_CRETIM - Creation time

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

EV_SHTEXT - Name of Object Type

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

EXCEPTIONS details

NF_DOC_NUM_NOT_FOUND - NF Document number not found

Data type:
Optional: No
Call by Reference: Yes

NF_NINE_DIG_NUM_NOT_FOUND - NF Nine digit number not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for NFE_DOCUMENT_READ_RFC 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_ev_docnum  TYPE J_1BDOCNUM, "   
lv_iv_refkey  TYPE J_1BREFKEY, "   
lv_nf_doc_num_not_found  TYPE J_1BREFKEY, "   
lv_ev_nfenum  TYPE J_1BNFNUM9, "   
lv_iv_logsys  TYPE LOGSYSTEM, "   
lv_nf_nine_dig_num_not_found  TYPE LOGSYSTEM, "   
lv_ev_series  TYPE J_1BSERIES, "   
lv_ev_subser  TYPE J_1BSUBSER, "   
lv_ev_credat  TYPE J_1BCREDAT, "   
lv_ev_cretim  TYPE J_1BCRETIM, "   
lv_ev_shtext  TYPE TEXT_TYP. "   

  CALL FUNCTION 'NFE_DOCUMENT_READ_RFC'  "RFC module to fetch NF Document data
    EXPORTING
         IV_REFKEY = lv_iv_refkey
         IV_LOGSYS = lv_iv_logsys
    IMPORTING
         EV_DOCNUM = lv_ev_docnum
         EV_NFENUM = lv_ev_nfenum
         EV_SERIES = lv_ev_series
         EV_SUBSER = lv_ev_subser
         EV_CREDAT = lv_ev_credat
         EV_CRETIM = lv_ev_cretim
         EV_SHTEXT = lv_ev_shtext
    EXCEPTIONS
        NF_DOC_NUM_NOT_FOUND = 1
        NF_NINE_DIG_NUM_NOT_FOUND = 2
. " NFE_DOCUMENT_READ_RFC




ABAP code using 7.40 inline data declarations to call FM NFE_DOCUMENT_READ_RFC

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!