SAP Function Modules

comments icon Comments

J_1B_NFE_CONTINGENCY SAP Function module - Switch document to contingency







J_1B_NFE_CONTINGENCY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name J_1B_NFE_CONTINGENCY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: J_1B_NFE
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM J_1B_NFE_CONTINGENCY - J 1B NFE CONTINGENCY 





CALL FUNCTION 'J_1B_NFE_CONTINGENCY' "Switch document to contingency
  EXPORTING
    i_docnum =                  " j_1bdocnum    Document number
*   is_reason_conting =         " j_1bnfe_continrt  NFe: Reason for Contingency - Description
*   iv_check_only = SPACE       " flag          Value 'X' is set for test run
  IMPORTING
    es_active_mod =             " j_1bnfe_active  Electronic Nota Fiscal: Actual Status
  EXCEPTIONS
    PROCESS_ERRORS = 1          "               Errors occured during process
    CANCEL_ERROR = 2            "               Error occured during automatic cancellation
    .  "  J_1B_NFE_CONTINGENCY

ABAP code example for Function Module J_1B_NFE_CONTINGENCY





The ABAP code below is a full code listing to execute function module J_1B_NFE_CONTINGENCY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_es_active_mod    TYPE J_1BNFE_ACTIVE
.




DATA(ld_i_docnum) = 'Check type of data required'.

DATA(ld_is_reason_conting) = 'Check type of data required'.

DATA(ld_iv_check_only) = 'Check type of data required'.
.

CALL FUNCTION 'J_1B_NFE_CONTINGENCY'
  EXPORTING
    i_docnum =                   ld_i_docnum
*   is_reason_conting =          ld_is_reason_conting
*   iv_check_only =              ld_iv_check_only
  IMPORTING
    es_active_mod =              ld_es_active_mod
  EXCEPTIONS
    PROCESS_ERRORS =             1
    CANCEL_ERROR =               2
    .  "  J_1B_NFE_CONTINGENCY

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_es_active_mod  TYPE J_1BNFE_ACTIVE ,
ld_i_docnum  TYPE J_1BDOCNUM ,
ld_is_reason_conting  TYPE J_1BNFE_CONTINRT ,
ld_iv_check_only  TYPE FLAG .




ld_i_docnum = 'Check type of data required'.
ld_is_reason_conting = 'Check type of data required'.
ld_iv_check_only = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name J_1B_NFE_CONTINGENCY or its description.


   
 

J_1B_NFE_CONTINGENCY - Switch document to contingency
J_1B_NFE_CHECK_TPEMIS - Check issuing type and determine contingency flag
J_1B_NFE_CHECK_RFC_DESTINATION - Check connection to RFC destination
J_1B_NFE_CHECK_NEXT_STATUS - Check if NFe status allows cancellation
J_1B_NFE_CHECK_NEXT_SCSSTATUS - Check if NFe status allows cancellation
J_1B_NFE_CHECK_DOCUMENT_FLOW - Check document flow for stock transfer