SAP J_1B_NFE_ENQUEUE_VBRK_BKPF Function Module for Set NF-e number in XBLNR of Billing and FI-Documents
J_1B_NFE_ENQUEUE_VBRK_BKPF is a standard j 1b nfe enqueue vbrk bkpf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set NF-e number in XBLNR of Billing and FI-Documents 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 enqueue vbrk bkpf FM, simply by entering the name J_1B_NFE_ENQUEUE_VBRK_BKPF into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1B_NFE_UTILITY_3
Program Name: SAPLJ_1B_NFE_UTILITY_3
Main Program: SAPLJ_1B_NFE_UTILITY_3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1B_NFE_ENQUEUE_VBRK_BKPF 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_ENQUEUE_VBRK_BKPF'"Set NF-e number in XBLNR of Billing and FI-Documents.
EXPORTING
IV_BUKRS = "Company Code
IV_REFTYP = "NF Document Number
IV_REFKEY = "Reference to source document
* IV_XBLNR = "Reference Document Number
IMPORTING
EV_FOLLOW = "Follow up activity made
EV_RBELN = "Document Number of an Invoice Document
EV_MBLNR = "Number of Material Document
EV_VBELN = "Delivery
EV_BELNR = "Accounting Document Number
EV_GJAHR = "Fiscal Year
EXCEPTIONS
BILLING_DOC_NOT_FOUND = 1 VBRK_LOCKED = 2 BKPF_LOCKED = 3 DOCUMENT_NOT_FOUND = 4 LOCK_ERROR = 5
IMPORTING Parameters details for J_1B_NFE_ENQUEUE_VBRK_BKPF
IV_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
IV_REFTYP - NF Document Number
Data type: J_1BREFTYPOptional: No
Call by Reference: No ( called with pass by value option)
IV_REFKEY - Reference to source document
Data type: J_1BREFKEYOptional: No
Call by Reference: No ( called with pass by value option)
IV_XBLNR - Reference Document Number
Data type: XBLNR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_1B_NFE_ENQUEUE_VBRK_BKPF
EV_FOLLOW - Follow up activity made
Data type: J_1BFOLLOWOptional: No
Call by Reference: Yes
EV_RBELN - Document Number of an Invoice Document
Data type: RE_BELNROptional: No
Call by Reference: Yes
EV_MBLNR - Number of Material Document
Data type: MBLNROptional: No
Call by Reference: Yes
EV_VBELN - Delivery
Data type: VBELN_VLOptional: No
Call by Reference: Yes
EV_BELNR - Accounting Document Number
Data type: BELNR_DOptional: No
Call by Reference: Yes
EV_GJAHR - Fiscal Year
Data type: GJAHROptional: No
Call by Reference: Yes
EXCEPTIONS details
BILLING_DOC_NOT_FOUND - Billing document was not found
Data type:Optional: No
Call by Reference: Yes
VBRK_LOCKED - Table VBRK is locked
Data type:Optional: No
Call by Reference: Yes
BKPF_LOCKED - Table BKPF is locked
Data type:Optional: No
Call by Reference: Yes
DOCUMENT_NOT_FOUND - Document not found
Data type:Optional: No
Call by Reference: Yes
LOCK_ERROR - Locking problem
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1B_NFE_ENQUEUE_VBRK_BKPF 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_iv_bukrs | TYPE BUKRS, " | |||
| lv_ev_follow | TYPE J_1BFOLLOW, " | |||
| lv_billing_doc_not_found | TYPE J_1BFOLLOW, " | |||
| lv_ev_rbeln | TYPE RE_BELNR, " | |||
| lv_iv_reftyp | TYPE J_1BREFTYP, " | |||
| lv_vbrk_locked | TYPE J_1BREFTYP, " | |||
| lv_ev_mblnr | TYPE MBLNR, " | |||
| lv_iv_refkey | TYPE J_1BREFKEY, " | |||
| lv_bkpf_locked | TYPE J_1BREFKEY, " | |||
| lv_ev_vbeln | TYPE VBELN_VL, " | |||
| lv_iv_xblnr | TYPE XBLNR1, " | |||
| lv_document_not_found | TYPE XBLNR1, " | |||
| lv_ev_belnr | TYPE BELNR_D, " | |||
| lv_lock_error | TYPE BELNR_D, " | |||
| lv_ev_gjahr | TYPE GJAHR. " |
|   CALL FUNCTION 'J_1B_NFE_ENQUEUE_VBRK_BKPF' "Set NF-e number in XBLNR of Billing and FI-Documents |
| EXPORTING | ||
| IV_BUKRS | = lv_iv_bukrs | |
| IV_REFTYP | = lv_iv_reftyp | |
| IV_REFKEY | = lv_iv_refkey | |
| IV_XBLNR | = lv_iv_xblnr | |
| IMPORTING | ||
| EV_FOLLOW | = lv_ev_follow | |
| EV_RBELN | = lv_ev_rbeln | |
| EV_MBLNR | = lv_ev_mblnr | |
| EV_VBELN | = lv_ev_vbeln | |
| EV_BELNR | = lv_ev_belnr | |
| EV_GJAHR | = lv_ev_gjahr | |
| EXCEPTIONS | ||
| BILLING_DOC_NOT_FOUND = 1 | ||
| VBRK_LOCKED = 2 | ||
| BKPF_LOCKED = 3 | ||
| DOCUMENT_NOT_FOUND = 4 | ||
| LOCK_ERROR = 5 | ||
| . " J_1B_NFE_ENQUEUE_VBRK_BKPF | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_NFE_ENQUEUE_VBRK_BKPF
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