Solved

Information Message "The Filed 'New Item' must have a value"

  • 25 February 2024
  • 6 replies
  • 64 views
zakirh
Rank

In Mixed Payment, showing an information message to tick ‘New Item’ and not allowing to save. How to solve the issue ?

 

icon

Best answer by Adam Bereda 26 February 2024, 14:22

View original

6 replies

A
Rank
Userlevel 7
Badge +16

Hello,

The field “New item” seems to be hidden behind the error message. I am not sure what is the transaction type behind. 
If this field is a checkbox, checking and unchecking it can solve the issue. But it can be a result of some other issue as well.

Regards, Adam
zakirh
Rank

Hi Adam

In case of both Transaction types “Enter Customer Payment and Enter Supplier Payment”, this is happening. And the new item filed is a Checkbox type filed.

 

Thanks

F
Rank
Userlevel 6
Badge +19

Hello @zakirh 

This could be triggered from Mandatory field setting in Properties. Click right mouse button on lump sum section and click Properties.

 

 

Go to Mandatory tab and click Default button. Then click Apply and OK.

 

Create a new record and see if still you get the same message.

Hope this helps

https://superp.solutions/
zakirh
Rank

Hi

The field is not mandatory in properties. Till the issue is coming.

Thanks.

A
Rank
Userlevel 7
Badge +16

Hi, 
Field “New item” should have default value “FALSE” - unchecked, for supplier or customer payments where no new difference item is created. 
You can manually check this field and uncheck it to force system to store FALSE value. 
If the issue is repetitive, it is of technical nature and you need a support case to be raised.

Regards, Adam
F
Rank
Userlevel 6
Badge +19

Hi again,

When I create a new record NEW_DIFF_ITEM is by default set to FALSE. I think in your case NEW_DIFF_ITEM is not set to any value. Therefore, it generates error. As @Adam Bereda  already said, if you check and uncheck the field when creating new row system will set it first to TRUE and then to FALSE so you can continue without problem.

As @Adam Bereda already said, it requires a technical investigation why the field is not completed during check insert.

 



DECLARE

   p0_ VARCHAR2(32000) := NULL;

   p1_ VARCHAR2(32000) := '';

   p2_ VARCHAR2(32000) := '';

   p3_ VARCHAR2(32000) := 
'COMPANY'||chr(31)||'XXXX'||chr(30)||
'MIXED_PAYMENT_ID'||chr(31)||'21'||chr(30)||
'LUMP_SUM_TRANS_ID'||chr(31)||'0'||chr(30)||
'LUMP_SUM_TRANS_NO'||chr(31)||'1'||chr(30)||
'PRE_ACCOUNT_STRING'||chr(31)||'^^^^^^^^^^'||chr(30)||
'MIXED_PAYMENT_TRANS_TYPE'||chr(31)||'Enter Customer Payment'||chr(30)||
'TRANSACTION_CODE_ID'||chr(31)||'*'||chr(30)||
'PARTY_TYPE'||chr(31)||'Customer'||chr(30)||
'BALANCE_METHOD'||chr(31)||'Detailed'||chr(30)||
'PARTY_TYPE_DB'||chr(31)||'CUSTOMER'||chr(30)||
'LUMP_SUM_TRANS_DATE'||chr(31)||'2024-02-26-00.00.00'||chr(30)||'CURRENCY_TYPE'||chr(31)||'1'||chr(30)||
'CURRENCY'||chr(31)||'PLN'||chr(30)||
'CURRENCY_RATE'||chr(31)||'1'||chr(30)||
'DIV_FACTOR'||chr(31)||'1'||chr(30)||
'PARALLEL_CURR_RATE'||chr(31)||'4.5'||chr(30)||
'PARALLEL_DIV_FACTOR'||chr(31)||'1'||chr(30)||
'TAX_CURR_RATE'||chr(31)||'1'||chr(30)||
'CHILD_COMPANY'||chr(31)||'XXXX'||chr(30)||
'LEDGER_ITEM_VERSION'||chr(31)||'1'||chr(30)||
'MATCHING_CANCELLED'||chr(31)||'FALSE'||chr(30)||
'COMPLETELY_MATCHED'||chr(31)||'FALSE'||chr(30)||
'MIXED_PAYMENT_DATE'||chr(31)||'2024-02-26-00.00.00'||chr(30)||
'MIXED_PAYMENT_DATE_MODIFIED'||chr(31)||''||chr(30)||
'MATCHED_SERIES_ID'||chr(31)||''||chr(30)||
'MATCHED_ITEM_ID'||chr(31)||''||chr(30)||
'NEW_DIFF_ITEM'||chr(31)||'FALSE'||chr(30)||
'TAX_DIRECTION'||chr(31)||''||chr(30)||
'MIXED_PAYMENT_ID'||chr(31)||'21'||chr(30);

   p4_ VARCHAR2(32000) := 'CHECK';

BEGIN
    IFSAPP.Log_SYS.Init_Debug_Session_('en');

IFSAPP.MIXED_PAYMENT_LUMP_SUM_API.NEW__( p0_ , p1_ , p2_ , p3_ , p4_ );


END;

 

Hope this helps

https://superp.solutions/

Reply


Terms & ConditionsCookie settings