SAP J_1BNF_FILL_HEADER_FROM_BUPLA Function Module for Fill the additional header fields, derived from NF Type
J_1BNF_FILL_HEADER_FROM_BUPLA is a standard j 1bnf fill header from bupla SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill the additional header fields, derived from NF 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 1bnf fill header from bupla FM, simply by entering the name J_1BNF_FILL_HEADER_FROM_BUPLA into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1B_NF_ADD
Program Name: SAPLJ_1B_NF_ADD
Main Program: SAPLJ_1B_NF_ADD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1BNF_FILL_HEADER_FROM_BUPLA 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_1BNF_FILL_HEADER_FROM_BUPLA'"Fill the additional header fields, derived from NF Type.
IMPORTING
ES_ADDRESS_BUPLA = "Address of Business Place
CHANGING
CS_NFDOC = "Nota Fiscal Header
EXCEPTIONS
WRONG_BUPLA = 1 PARTNER_NOT_FOUND = 2
EXPORTING Parameters details for J_1BNF_FILL_HEADER_FROM_BUPLA
ES_ADDRESS_BUPLA - Address of Business Place
Data type: SADROptional: No
Call by Reference: Yes
CHANGING Parameters details for J_1BNF_FILL_HEADER_FROM_BUPLA
CS_NFDOC - Nota Fiscal Header
Data type: J_1BNFDOCOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_BUPLA - Wrong business place
Data type:Optional: No
Call by Reference: Yes
PARTNER_NOT_FOUND - Partner not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1BNF_FILL_HEADER_FROM_BUPLA 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_cs_nfdoc | TYPE J_1BNFDOC, " | |||
| lv_wrong_bupla | TYPE J_1BNFDOC, " | |||
| lv_es_address_bupla | TYPE SADR, " | |||
| lv_partner_not_found | TYPE SADR. " |
|   CALL FUNCTION 'J_1BNF_FILL_HEADER_FROM_BUPLA' "Fill the additional header fields, derived from NF Type |
| IMPORTING | ||
| ES_ADDRESS_BUPLA | = lv_es_address_bupla | |
| CHANGING | ||
| CS_NFDOC | = lv_cs_nfdoc | |
| EXCEPTIONS | ||
| WRONG_BUPLA = 1 | ||
| PARTNER_NOT_FOUND = 2 | ||
| . " J_1BNF_FILL_HEADER_FROM_BUPLA | ||
ABAP code using 7.40 inline data declarations to call FM J_1BNF_FILL_HEADER_FROM_BUPLA
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