SAP J_1B_NFE_CHECK_RFC_DESTINATION Function Module for Check connection to RFC destination

Search SAP Function Modules

J_1B_NFE_CHECK_RFC_DESTINATION is a standard j 1b nfe check rfc destination SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check connection to RFC destination 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 j 1b nfe check rfc destination FM, simply by entering the name J_1B_NFE_CHECK_RFC_DESTINATION into the relevant SAP transaction such as SE37 or SE38.

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

Function J_1B_NFE_CHECK_RFC_DESTINATION 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 'J_1B_NFE_CHECK_RFC_DESTINATION'"Check connection to RFC destination
  EXPORTING
   I_BUKRS =  "Company Code
   I_BRANCH =  "Business Place
*  I_MODEL = 0 "Model of Nota Fiscal

 IMPORTING
   E_RFCDEST =  "Logical Destination (Specified in Function Call)
   E_XNFEACTIVE =  "SAP xNFe active

EXCEPTIONS
   RFC_ERROR = 1 

.

IMPORTING Parameters details for J_1B_NFE_CHECK_RFC_DESTINATION

I_BUKRS - Company Code

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

I_BRANCH - Business Place

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

I_MODEL - Model of Nota Fiscal

Data type: J_1BMODEL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for J_1B_NFE_CHECK_RFC_DESTINATION

E_RFCDEST - Logical Destination (Specified in Function Call)

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

E_XNFEACTIVE - SAP xNFe active

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

EXCEPTIONS details

RFC_ERROR - RFC connection not available

Data type:
Optional: No
Call by Reference: Yes

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

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