Skip to main content
Question

not able to create sales quotation due to error message in opportunity

  • March 29, 2022
  • 3 replies
  • 130 views
M
Sidekick (Partner)
Forum|alt.badge.img+6

not able to create a sales quotation for following opp because of this error message. We already deleted some notes but this doesn´t help.

 

the error is: 

Server error messages:
86c77f28-8f36-489a-b91c-eb8531d13707

Ifs.Fnd.FndSystemException: Unexpected error while calling server method AccessPlsql/Invoke ---> Ifs.Fnd.FndServerFaultException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small

Failed executing statement (ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 20)

 

Any ideas/suggestions on the cause and how to resolve please

    This topic has been closed for replies.

    3 replies

    B
    Superhero (Employee)
    Forum|alt.badge.img+13

    Hi @mick.colpitts,

    Do u have access to PLSQL developer?

    If yes, can you open up a debug console.
    When you get this error, it will be visible in RED , copy that block and execute it in PLSQL via a TEST BLOCK.

    From there you can trace the full path of the error.

    Best Regards,
    Bhagya

     

     

    Pedro Gutiérrez
    Do Gooder (Employee)
    Forum|alt.badge.img
    • Pedro Gutiérrez
    • Do Gooder (Employee)
    • 4 replies
    • March 29, 2022

    Hi @mick.colpitts ,

    That issue most of the times is due to trying to assign a large value to a smaller variable, perhaps a text note with more than 2000 characters into a VARCHAR2(2000) field.

    As Bhagya suggests, open Debug Console, if you have access use PLSQL Develpover and copy the trace to a TEST Window, execute the TEST and the error trace show you which field/variable is the cause of the error.

    Regards,
    Pedro

    Charith Epitawatta
    Ultimate Hero (Employee)
    Forum|alt.badge.img+31
    • Charith Epitawatta
    • Ultimate Hero (Employee)
    • 1094 replies
    • March 29, 2022

    Hi @mick.colpitts,

    In addition to what Pedro and Bhagya has mentioned above, this could also be caused when the relevant database objects are compiled as BYTE instead of CHAR. Please go though the following post and the response marked as answer for details on how to check and fix it if that is the issue.

     

    Hope this helps!

    Charith - https://charith.pro
    Terms & ConditionsCookie settingsAccessibility statement