SAP J_1B_NF_PARTNER_READ Function Module for Nota Fiscal System - Read partner utility









J_1B_NF_PARTNER_READ is a standard j 1b nf partner 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 partner utility 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 partner read FM, simply by entering the name J_1B_NF_PARTNER_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_PARTNER_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_PARTNER_READ'"Nota Fiscal System - Read partner utility
EXPORTING
PARTNER_TYPE = "Partner type
PARTNER_ID = "Partner ID
* DOC_NUMBER = "NF document number (for one-time accounts)
* PARTNER_FUNCTION = "Partner function (for one-time accounts)
* OBJ_ITEM = "Nota Fiscal line items
* READ_ADDRESS = ' ' "Single-Character Indicator

IMPORTING
PARNAD = "Partner name and address

EXCEPTIONS
PARTNER_NOT_FOUND = 1 PARTNER_TYPE_NOT_FOUND = 2
.



IMPORTING Parameters details for J_1B_NF_PARTNER_READ

PARTNER_TYPE - Partner type

Data type: J_1BNFNAD-PARTYP
Optional: No
Call by Reference: No ( called with pass by value option)

PARTNER_ID - Partner ID

Data type: J_1BNFNAD-PARID
Optional: No
Call by Reference: No ( called with pass by value option)

DOC_NUMBER - NF document number (for one-time accounts)

Data type: J_1BNFDOC-DOCNUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARTNER_FUNCTION - Partner function (for one-time accounts)

Data type: J_1BNFDOC-PARVW
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJ_ITEM - Nota Fiscal line items

Data type: J_1BNFLIN
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_ADDRESS - Single-Character Indicator

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for J_1B_NF_PARTNER_READ

PARNAD - Partner name and address

Data type: J_1BINNAD
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PARTNER_NOT_FOUND - Partner not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARTNER_TYPE_NOT_FOUND - Partner type not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for J_1B_NF_PARTNER_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_type  TYPE J_1BNFNAD-PARTYP, "   
lv_partner_not_found  TYPE J_1BNFNAD, "   
lv_partner_id  TYPE J_1BNFNAD-PARID, "   
lv_partner_type_not_found  TYPE J_1BNFNAD, "   
lv_doc_number  TYPE J_1BNFDOC-DOCNUM, "   
lv_partner_function  TYPE J_1BNFDOC-PARVW, "   
lv_obj_item  TYPE J_1BNFLIN, "   
lv_read_address  TYPE CHAR1. "   ' '

  CALL FUNCTION 'J_1B_NF_PARTNER_READ'  "Nota Fiscal System - Read partner utility
    EXPORTING
         PARTNER_TYPE = lv_partner_type
         PARTNER_ID = lv_partner_id
         DOC_NUMBER = lv_doc_number
         PARTNER_FUNCTION = lv_partner_function
         OBJ_ITEM = lv_obj_item
         READ_ADDRESS = lv_read_address
    IMPORTING
         PARNAD = lv_parnad
    EXCEPTIONS
        PARTNER_NOT_FOUND = 1
        PARTNER_TYPE_NOT_FOUND = 2
. " J_1B_NF_PARTNER_READ




ABAP code using 7.40 inline data declarations to call FM J_1B_NF_PARTNER_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 PARTYP FROM J_1BNFNAD INTO @DATA(ld_partner_type).
 
 
"SELECT single PARID FROM J_1BNFNAD INTO @DATA(ld_partner_id).
 
 
"SELECT single DOCNUM FROM J_1BNFDOC INTO @DATA(ld_doc_number).
 
"SELECT single PARVW FROM J_1BNFDOC INTO @DATA(ld_partner_function).
 
 
DATA(ld_read_address) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!