0036853: Should not be necessary to have "Maturity Date 2" defined in Payment Terms defined as "Fixed Due date"

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0036853

Retail Modules

Web POS

public

2017-09-12 17:23

2017-09-21 07:32

Reporter

maite

Assigned To

ranjith_qualiantech_com

Priority

immediate

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

RR17Q3

Fixed in Version

RR17Q3

Merge Request Status

Review Assigned To

marvintm

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0036853: Should not be necessary to have "Maturity Date 2" defined in Payment Terms defined as "Fixed Due date"

Description

Ticket left in Errors While Importing when business partner payment terms are defined as "fixed due date" but payment term only has "maturity date 1" defined

Steps To Reproduce

0. Define new payment term named "fixed payment term" with "offset days"=30, Fixed due date=Y and "Maturity Date 1"=30
1. Access Business Partner window and set previous payment terms to VBS Customer
2. Access POS Terminal and register Credit Sales for VBS Customer
3. Realize that order is left in Errors While Importing window due to:

java.lang.NullPointerException
    at org.openbravo.retail.posterminal.OrderLoader.getCalculatedDueDateBasedOnPaymentTerms(OrderLoader.java:1955)
    at org.openbravo.retail.posterminal.OrderLoader.handlePayments(OrderLoader.java:2194)
    at org.openbravo.retail.posterminal.OrderLoader.saveRecord(OrderLoader.java:516)

Proposed Solution

Additional Information