SAP J_1B_NF_DOCUMENT_LOCK Function Module for Nota Fiscal System - Lock document
J_1B_NF_DOCUMENT_LOCK is a standard j 1b nf document lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Nota Fiscal System - Lock document 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 nf document lock FM, simply by entering the name J_1B_NF_DOCUMENT_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1BA
Program Name: SAPLJ1BA
Main Program: SAPLJ1BA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1B_NF_DOCUMENT_LOCK 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_NF_DOCUMENT_LOCK'"Nota Fiscal System - Lock document.
EXPORTING
DOC_NUMBER = "
LOCK_MODE = "
EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for J_1B_NF_DOCUMENT_LOCK
DOC_NUMBER -
Data type: J_1BNFDOC-DOCNUMOptional: No
Call by Reference: No ( called with pass by value option)
LOCK_MODE -
Data type: DD26E-ENQMODEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1B_NF_DOCUMENT_LOCK 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_doc_number | TYPE J_1BNFDOC-DOCNUM, " | |||
| lv_foreign_lock | TYPE J_1BNFDOC, " | |||
| lv_lock_mode | TYPE DD26E-ENQMODE, " | |||
| lv_system_failure | TYPE DD26E. " |
|   CALL FUNCTION 'J_1B_NF_DOCUMENT_LOCK' "Nota Fiscal System - Lock document |
| EXPORTING | ||
| DOC_NUMBER | = lv_doc_number | |
| LOCK_MODE | = lv_lock_mode | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " J_1B_NF_DOCUMENT_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_NF_DOCUMENT_LOCK
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.| "SELECT single DOCNUM FROM J_1BNFDOC INTO @DATA(ld_doc_number). | ||||
| "SELECT single ENQMODE FROM DD26E INTO @DATA(ld_lock_mode). | ||||
Search for further information about these or an SAP related objects