COND_COUNT - Cannot convert 123 into NUM: loss of significant digits. SAP NCo issue.

[dmko]

Hello,

Recently we started getting "Cannot convert 123 into NUM: loss of significant digits." error from NCo library for the specific field - COND_COUNT from BAPICOND structure. 

By default the length of this field is 2 digits, but the thing is we have some cases when amount of price conditions is more then 99 and that's why it fails now.

As I understood this field controls the order of price conditions and quite important to get a correctly price calculated.

We are using: BAPI_QUOTATION_CREATEFROMDATA2 function to create quote and one of the input parameter there is COND_COUNT.

Can someone please advice what is possible solution here if you faced this issue also?
I'm wondering is it possible to increase COND_COUNT length to 3 or 4 digits and what is the impact of this change on SAP system?

Maybe there is another way how to make it work with the default field length, what is the general/suggested approach in this type of issue?

Sap NCo version is - 3.1.0.42.

Thanks in advance,

Best regards,

Dmitriy

[RaymondGiuseppi · Accepted solution]

Check in your system for status of Note 2271617 - BAPI incompatibilities with respect to pricing field length extension (which added field COND_COUNT_LONG to some BAPI parameters)

[dmko · Accepted solution]

ohh this looks like a solution for us! Thanks!

[dmko · Accepted solution]

Hi raymond_giuseppi, just got a question from our customer, that looks like 2271617 is a note only for SAP S/4, but they have SAP ECC 6.0 EHP7 instance. Do you know is there any alternative for this Note for ECC?

[RaymondGiuseppi · Accepted solution]

The long field is available on my S/4HANA systems, but not on my ECC EHP7 (both were SP upgraded last year), and I haven't found any ECC-related notes.

• So raise an issue with sap support with SD-SLS and mention the S/4HANA notes 
• If unsuccessful, consider using Customer Influence to request this development to be downgraded to ECC

[dmko · Accepted solution]

Ok, I see. Thank you for the information!