SAP J_1B_NFE_GET_NEXT_STATUS Function Module for NF-e: Determine next internal status from message type

Search SAP Function Modules

J_1B_NFE_GET_NEXT_STATUS is a standard j 1b nfe get next status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NF-e: Determine next internal status from message type 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 get next status FM, simply by entering the name J_1B_NFE_GET_NEXT_STATUS 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_GET_NEXT_STATUS 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_GET_NEXT_STATUS'"NF-e: Determine next internal status from message type
  EXPORTING
   IV_MSGTYP =  "NF-e: Type of Inbound Message
*  IV_FORM = ' ' "Form of Nota Fiscal
*  IV_AUTHCODE = ' ' "NF-e: Protocol Number

 IMPORTING
   EV_DOCSTA =  "NF-e: Document Status
   EV_SCSSTA =  "NF-e: System Communication Status

EXCEPTIONS
   AUTHCODE_REQUIRED = 1    MSG_TYPE_INVALID = 2 

.

IMPORTING Parameters details for J_1B_NFE_GET_NEXT_STATUS

IV_MSGTYP - NF-e: Type of Inbound Message

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

IV_FORM - Form of Nota Fiscal

Data type: J_1BFORM
Default: ' '
Optional: Yes
Call by Reference: Yes

IV_AUTHCODE - NF-e: Protocol Number

Data type: J_1BNFEAUTHCODE
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for J_1B_NFE_GET_NEXT_STATUS

EV_DOCSTA - NF-e: Document Status

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

EV_SCSSTA - NF-e: System Communication Status

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

EXCEPTIONS details

AUTHCODE_REQUIRED - Authorization code required

Data type:
Optional: No
Call by Reference: Yes

MSG_TYPE_INVALID - Message type is invalid

Data type:
Optional: No
Call by Reference: Yes

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

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