Skip to main content
Solved

ORA-06502 error on Production Receipt

  • October 23, 2024
  • 2 replies
  • 71 views

Forum|alt.badge.img+7

 

When doing a production receipt, quantity 1000 can be received while 2000 generates an error. The only difference the received quantity, no idea why it is related to characters. 

 

 

Best answer by Nikila Dis

Hi @eric.sun,

This is a generic error that could occur due to several reasons. All the scenarios are covered in the below artical:

https://community.ifs.com/technical-issues-101/error-numeric-or-value-error-character-string-buffer-too-small-8188

  1. Overflow Error: You may be trying to assign a value to a numeric variable that exceeds its maximum limit.

  2. NULL Assignment: You might be attempting to assign a NULL value to a variable that has a NOT NULL constraint, which violates the rules.

Once possible option is: can you please enable the debug window , take the server invoke from there and run it on the PL SQL Developer.  Then view the program source error stack. It will give you some hints to identify the exact place.

If not it's challenging to determine the exact cause without additional information. If you’re still unsure how to resolve the issue, raising a support case would be the best option. They can provide more targeted assistance.

Regards,

Nikila Dissanayake

View original
Did this topic help you find an answer to your question?

2 replies

Nikila Dis
Hero (Employee)
Forum|alt.badge.img+9
  • Hero (Employee)
  • 58 replies
  • Answer
  • October 23, 2024

Hi @eric.sun,

This is a generic error that could occur due to several reasons. All the scenarios are covered in the below artical:

https://community.ifs.com/technical-issues-101/error-numeric-or-value-error-character-string-buffer-too-small-8188

  1. Overflow Error: You may be trying to assign a value to a numeric variable that exceeds its maximum limit.

  2. NULL Assignment: You might be attempting to assign a NULL value to a variable that has a NOT NULL constraint, which violates the rules.

Once possible option is: can you please enable the debug window , take the server invoke from there and run it on the PL SQL Developer.  Then view the program source error stack. It will give you some hints to identify the exact place.

If not it's challenging to determine the exact cause without additional information. If you’re still unsure how to resolve the issue, raising a support case would be the best option. They can provide more targeted assistance.

Regards,

Nikila Dissanayake


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 35 replies
  • October 28, 2024

@Nikila Dis , thanks for your information.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings