cancel
Showing results for 
Search instead for 
Did you mean: 

"API_SEMBPS_GETDATA" and Decimal Notation

Former Member
0 Kudos

Hi,

During the upload of transaction data, we use the function module "API_SEMBPS_GETDATA" to get some reference data. Unfortunately, this function module applies the decimal notation from the user record before returning the data, rather than using SAP's internal format. This leads to short-dumps in the upload process if the user who is executing the upload uses a comma as the decimal separator (which is not unusual in The Netherlands).

So my questions are:

1. Is it intentional that the setting from the user record is applied or could this be a bug?

2. Is there a way of circumventing this, other than using the ABAP statement "translate ',.'" each time we read BPS data?

Kind regards,

Sascha Zevenhuizen

Message was edited by: Sascha Zevenhuizen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sascha,

You can change user record data: menu option System/User profile/Own data.

Best regards,

Eugene

Former Member
0 Kudos

Hi Eugene,

Thanks for your reply. I should have mentioned that we want to solve it regardless the setting in the user profile. Since my client is an international organization, we do not want to impose the decimal point on the user organization.

Kind regards,

Sascha.

Former Member
0 Kudos

Hi Sascha,

I tought it would be more logical to use a user locales customuzing. User profile data should be configured as Excel locales.

Otherwise how would you distinguish between '123,456.78' and '123.456,78' user formats?

But anyway, if you want to unify the settings right now I cannot propose something suitable for you. Sorry.

Best regards,

Eugene

Former Member
0 Kudos

Hi Eugene,

I'm not sure I understand your answer: What do you mean by a user locales customizing?

The problem you describe, distinguishing between

'123,456.78' and '123.456,78', is precisely what I'm trying to overcome.

Regards,

Sascha.

Former Member
0 Kudos

Hi,

One roundabout option could be to call this function with RFC Destination option. Define a dummy destination to same SEM client/system with a dialog user. Now call the function at this destination. This common RFC dest userid will always be used while calling this function, so you will be sure as to which format the data is to be expected.

cheers,

Former Member
0 Kudos

Hi Ajay,

This could be a useful work-around. I think I will try this one, so thanks. In the mean time I'm open to any new ideas.

In my opinion what goes wrong here with this API is that the application (read the data from BPS) and presentation (decimal point or comma) layers are not separated.

Best regards,

Sascha.

Former Member
0 Kudos

Hi Sacha,

I am also from Holland (groeten)

I do not completely understand the solution.

I have the same problem RFC Query call, A very powerfull function.. except for the comma/point problem.

Any information would be appreciated.

Answers (1)

Answers (1)

former_member93896
Active Contributor
0 Kudos

Hi Sascha,

why do you write "unfortunately"? I would say it is nice that the BPS APIs work with the user setting since that is exactly what the user expects.

The problem is in the implementation of your upload program. You could use the API again to write back the data (which would take care of the decimal notation for you) or your program should read the user master settings and react accordingly.

Regards

Marc

SAP NetWeaver RIG