SAP J_1B_NF_CUSTOMER_READ Function Module for Nota Fiscal System - Read Customer (use only in read partner)
J_1B_NF_CUSTOMER_READ is a standard j 1b nf customer read 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 - Read Customer (use only in read partner) 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 customer read FM, simply by entering the name J_1B_NF_CUSTOMER_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1BE
Program Name: SAPLJ1BE
Main Program: SAPLJ1BE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1B_NF_CUSTOMER_READ 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_CUSTOMER_READ'"Nota Fiscal System - Read Customer (use only in read partner).
EXPORTING
PARTNER_ID = "Partner ID
* PARTNER_FN = "Nota Fiscal Partner Function
* DOC_NUMBER = "Document Number
* READ_ADDRESS = ' ' "Single-Character Indicator
IMPORTING
PARNAD = "Partner name and address
ADDRESS = "Address Management: Company Data
ADDRESS1 = "Address return structure
EXCEPTIONS
PARTNER_NOT_FOUND = 1 ADDRESS_NOT_FOUND = 2
IMPORTING Parameters details for J_1B_NF_CUSTOMER_READ
PARTNER_ID - Partner ID
Data type: J_1BNFNAD-PARIDOptional: No
Call by Reference: No ( called with pass by value option)
PARTNER_FN - Nota Fiscal Partner Function
Data type: J_1BNFNAD-PARVWOptional: Yes
Call by Reference: No ( called with pass by value option)
DOC_NUMBER - Document Number
Data type: J_1BNFDOC-DOCNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
READ_ADDRESS - Single-Character Indicator
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for J_1B_NF_CUSTOMER_READ
PARNAD - Partner name and address
Data type: J_1BINNADOptional: No
Call by Reference: No ( called with pass by value option)
ADDRESS - Address Management: Company Data
Data type: SADROptional: No
Call by Reference: Yes
ADDRESS1 - Address return structure
Data type: ADDR1_VALOptional: No
Call by Reference: Yes
EXCEPTIONS details
PARTNER_NOT_FOUND - Partner not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ADDRESS_NOT_FOUND - Address not maintained
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1B_NF_CUSTOMER_READ 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_parnad | TYPE J_1BINNAD, " | |||
| lv_partner_id | TYPE J_1BNFNAD-PARID, " | |||
| lv_partner_not_found | TYPE J_1BNFNAD, " | |||
| lv_address | TYPE SADR, " | |||
| lv_partner_fn | TYPE J_1BNFNAD-PARVW, " | |||
| lv_address_not_found | TYPE J_1BNFNAD, " | |||
| lv_address1 | TYPE ADDR1_VAL, " | |||
| lv_doc_number | TYPE J_1BNFDOC-DOCNUM, " | |||
| lv_read_address | TYPE CHAR1. " ' ' |
|   CALL FUNCTION 'J_1B_NF_CUSTOMER_READ' "Nota Fiscal System - Read Customer (use only in read partner) |
| EXPORTING | ||
| PARTNER_ID | = lv_partner_id | |
| PARTNER_FN | = lv_partner_fn | |
| DOC_NUMBER | = lv_doc_number | |
| READ_ADDRESS | = lv_read_address | |
| IMPORTING | ||
| PARNAD | = lv_parnad | |
| ADDRESS | = lv_address | |
| ADDRESS1 | = lv_address1 | |
| EXCEPTIONS | ||
| PARTNER_NOT_FOUND = 1 | ||
| ADDRESS_NOT_FOUND = 2 | ||
| . " J_1B_NF_CUSTOMER_READ | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_NF_CUSTOMER_READ
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 PARID FROM J_1BNFNAD INTO @DATA(ld_partner_id). | ||||
| "SELECT single PARVW FROM J_1BNFNAD INTO @DATA(ld_partner_fn). | ||||
| "SELECT single DOCNUM FROM J_1BNFDOC INTO @DATA(ld_doc_number). | ||||
| DATA(ld_read_address) | = ' '. | |||
Search for further information about these or an SAP related objects