SAP J_1B_NF_OBJECT_EDIT Function Module for Nota Fiscal System - Edit object (with dialog)









J_1B_NF_OBJECT_EDIT is a standard j 1b nf object edit 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 - Edit object (with dialog) 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 object edit FM, simply by entering the name J_1B_NF_OBJECT_EDIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: J1BB
Program Name: SAPLJ1BB
Main Program: SAPLJ1BB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function J_1B_NF_OBJECT_EDIT 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_OBJECT_EDIT'"Nota Fiscal System - Edit object (with dialog)
EXPORTING
OBJ_NUMBER = "Nota Fiscal object number
* MODEF = 'CRE' "Function mode
* SCREEN_NUMBER = 200 "Number of the initial screen
* WRITER = ' ' "Writer indicator
* VALUES_INCL_TAXES = ' ' "Value and price including ICMS/ISS
* MANUAL_TAXES = ' ' "Manual taxes allowed

IMPORTING
FCODE = "Function code

EXCEPTIONS
OBJECT_NOT_FOUND = 1 SCR_CTRL_NOT_FOUND = 2 SCREEN_NOT_FOUND = 3
.



IMPORTING Parameters details for J_1B_NF_OBJECT_EDIT

OBJ_NUMBER - Nota Fiscal object number

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

MODEF - Function mode

Data type: J_1BINTERF-MODEF
Default: 'CRE'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCREEN_NUMBER - Number of the initial screen

Data type: J_1BINTERF-SCRNUM
Default: 200
Optional: Yes
Call by Reference: No ( called with pass by value option)

WRITER - Writer indicator

Data type: J_1BINTERF-WRITER
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

VALUES_INCL_TAXES - Value and price including ICMS/ISS

Data type: J_1BINTERF-INCLTX
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANUAL_TAXES - Manual taxes allowed

Data type: J_1BINTERF-MANTAX
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for J_1B_NF_OBJECT_EDIT

FCODE - Function code

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

EXCEPTIONS details

OBJECT_NOT_FOUND - Object not found in the work area

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

SCR_CTRL_NOT_FOUND - Screen control not found

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

SCREEN_NOT_FOUND - The screen does not exist

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

Copy and paste ABAP code example for J_1B_NF_OBJECT_EDIT 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_fcode  TYPE STRING, "   
lv_obj_number  TYPE J_1BINTERF-NFOBJN, "   
lv_object_not_found  TYPE J_1BINTERF, "   
lv_modef  TYPE J_1BINTERF-MODEF, "   'CRE'
lv_scr_ctrl_not_found  TYPE J_1BINTERF, "   
lv_screen_number  TYPE J_1BINTERF-SCRNUM, "   200
lv_screen_not_found  TYPE J_1BINTERF, "   
lv_writer  TYPE J_1BINTERF-WRITER, "   ' '
lv_values_incl_taxes  TYPE J_1BINTERF-INCLTX, "   ' '
lv_manual_taxes  TYPE J_1BINTERF-MANTAX. "   ' '

  CALL FUNCTION 'J_1B_NF_OBJECT_EDIT'  "Nota Fiscal System - Edit object (with dialog)
    EXPORTING
         OBJ_NUMBER = lv_obj_number
         MODEF = lv_modef
         SCREEN_NUMBER = lv_screen_number
         WRITER = lv_writer
         VALUES_INCL_TAXES = lv_values_incl_taxes
         MANUAL_TAXES = lv_manual_taxes
    IMPORTING
         FCODE = lv_fcode
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        SCR_CTRL_NOT_FOUND = 2
        SCREEN_NOT_FOUND = 3
. " J_1B_NF_OBJECT_EDIT




ABAP code using 7.40 inline data declarations to call FM J_1B_NF_OBJECT_EDIT

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 NFOBJN FROM J_1BINTERF INTO @DATA(ld_obj_number).
 
 
"SELECT single MODEF FROM J_1BINTERF INTO @DATA(ld_modef).
DATA(ld_modef) = 'CRE'.
 
 
"SELECT single SCRNUM FROM J_1BINTERF INTO @DATA(ld_screen_number).
DATA(ld_screen_number) = 200.
 
 
"SELECT single WRITER FROM J_1BINTERF INTO @DATA(ld_writer).
DATA(ld_writer) = ' '.
 
"SELECT single INCLTX FROM J_1BINTERF INTO @DATA(ld_values_incl_taxes).
DATA(ld_values_incl_taxes) = ' '.
 
"SELECT single MANTAX FROM J_1BINTERF INTO @DATA(ld_manual_taxes).
DATA(ld_manual_taxes) = ' '.
 


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!