SAP J_1B_FI_NETDUE Function Module for NOTRANSL: To calculate only net due (in contrast to J_1B_READDUEDATE

Search SAP Function Modules

J_1B_FI_NETDUE is a standard j 1b fi netdue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: To calculate only net due (in contrast to J_1B_READDUEDATE 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 fi netdue FM, simply by entering the name J_1B_FI_NETDUE into the relevant SAP transaction such as SE37 or SE38.

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

Function J_1B_FI_NETDUE 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_FI_NETDUE'"NOTRANSL: To calculate only net due (in contrast to J_1B_READDUEDATE
  EXPORTING
   ZFBDT =  "Baseline Date for Due Date Calculation
*  ZSMN3 =  "Additional Months for Special Condition (Term 3)
   ZBD1T =  "Cash Discount Days 1
   ZBD2T =  "Cash Discount Days 2
   ZBD3T =  "Net Payment Terms Period
*  ZSTG1 =  "Due Date for Special Condition
*  ZSMN1 =  "Additional Months for Special Condition (Term 1)
*  ZSTG2 =  "Due Date for Special Condition
*  ZSMN2 =  "Additional Months for Special Condition (Term 2)
*  ZSTG3 =  "Due Date for Special Condition

 IMPORTING
   DUEDATE =  "Baseline Date for Due Date Calculation

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJ1BM_001 Customer Exit for Calculating Additional Data in Boleto

IMPORTING Parameters details for J_1B_FI_NETDUE

ZFBDT - Baseline Date for Due Date Calculation

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

ZSMN3 - Additional Months for Special Condition (Term 3)

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

ZBD1T - Cash Discount Days 1

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

ZBD2T - Cash Discount Days 2

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

ZBD3T - Net Payment Terms Period

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

ZSTG1 - Due Date for Special Condition

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

ZSMN1 - Additional Months for Special Condition (Term 1)

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

ZSTG2 - Due Date for Special Condition

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

ZSMN2 - Additional Months for Special Condition (Term 2)

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

ZSTG3 - Due Date for Special Condition

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

EXPORTING Parameters details for J_1B_FI_NETDUE

DUEDATE - Baseline Date for Due Date Calculation

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

Copy and paste ABAP code example for J_1B_FI_NETDUE 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.

ABAP code using 7.40 inline data declarations to call FM J_1B_FI_NETDUE

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