SAP J_1B_NFE_CHECK_CANCEL_STATUS Function Module for Check if NFe status allows cancellation
J_1B_NFE_CHECK_CANCEL_STATUS is a standard j 1b nfe check cancel 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 Check if NFe status allows cancellation 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 cancel status FM, simply by entering the name J_1B_NFE_CHECK_CANCEL_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_CHECK_CANCEL_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_CHECK_CANCEL_STATUS'"Check if NFe status allows cancellation.
EXPORTING
I_BUKRS = "Company Code
I_DOCNUM = "Document number
EXCEPTIONS
CANCEL_NOT_ALLOWED = 1 SCS_STATUS_NOT_ALLOWED = 2
IMPORTING Parameters details for J_1B_NFE_CHECK_CANCEL_STATUS
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
I_DOCNUM - Document number
Data type: J_1BDOCNUMOptional: No
Call by Reference: Yes
EXCEPTIONS details
CANCEL_NOT_ALLOWED - cancel is not allowed
Data type:Optional: No
Call by Reference: Yes
SCS_STATUS_NOT_ALLOWED - SCS Status not allowed in combination with document Status
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1B_NFE_CHECK_CANCEL_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.| DATA: | ||||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_cancel_not_allowed | TYPE BUKRS, " | |||
| lv_i_docnum | TYPE J_1BDOCNUM, " | |||
| lv_scs_status_not_allowed | TYPE J_1BDOCNUM. " |
|   CALL FUNCTION 'J_1B_NFE_CHECK_CANCEL_STATUS' "Check if NFe status allows cancellation |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_DOCNUM | = lv_i_docnum | |
| EXCEPTIONS | ||
| CANCEL_NOT_ALLOWED = 1 | ||
| SCS_STATUS_NOT_ALLOWED = 2 | ||
| . " J_1B_NFE_CHECK_CANCEL_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_NFE_CHECK_CANCEL_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