Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Problem with changing the Standard Price using MR21

Former Member

‎2009 Mar 04 12:06 PM

0 Likes
500

I'm upgrading the system from 4.6C to ECC6.

Upgrading the Standard Price works normally in 4.6C. However, in ECC6, I notice that the data saved to CDPOS table is wrongly formatted. Therefore the other programs fail to read from this table.

Standard price is supposed to be right-justified. But it not like that in ECC6.

Can anyone tell me we should I look into to control the process of saving the data to CDPOS?

Thanks.

Han

I'm upgrading the system from 4.6C to ECC6.

Upgrading the Standard Price works normally in 4.6C. However, in ECC6, I notice that the data saved to CDPOS table is wrongly formatted. Therefore the other programs fail to read from this table.

Standard price is supposed to be right-justified. But it not like that in ECC6.

Can anyone tell me we should I look into to control the process of saving the data to CDPOS?

Thanks.

Han

Reply
2 REPLIES 2
Read only

Former Member

‎2009 Mar 04 12:12 PM

0 Likes
461

Hi Han,

Check this link.

https://wiki.sdn.sap.com/wiki/x/KwOmB

Much Regards,

Amuktha.

Read only

Former Member
In response to Former Member

‎2009 Mar 05 8:25 AM

0 Likes
461

Thanks Amuktha.

The link doesn't seem to help resolving my problem.

The changes is saved into CDPOS in the field Value_New (CHARACTER 254) in the way that the actual data can be retrieved by:

value_new+238

But any update to the standard price using MR21 now result in the value of Value_New that require:

value_new+7

to get the actual data.

Further more, in the old system, the standard price value in the decimal form like: "55.66" will be save to VALUE_NEW as "5566". So to get the real value, the system need to devide the value by 100 to get the actual new price.

In the ECC6 system, it is exactly the same as what we input: "55.66".

My question is: Is there an user exit, BADI or any way that can interfere the process of saving the data to CDPOS so that I can ensure the new Price will be save as "5566" and can be extracted using VALUE_NEW+238?

Thanks.

Han