External field name

[Former Member]

In our implementation we have the info object for the article to be 40 as the characteristic string length, the actual length of the article is 11 digits so when we see the article in the MPOS (as a part of the CVC) in the internal format it is getting the 11 digits and adding the leading zeros for completing the 40 characteristic length.

when we look at the external format of the article it just shows me the 11 digits in the MPOS, it is not a problem when the article number is starting from a number that is non zero but it is a problem when the article number starts with 0 because then it is taking it as the leading zero and only showing the 10 digits in the external format in the MPOS.

FOR EXAMPLE:

case1:

article number is 12345600000

internal format is 00000000000000000000000000000012345600000

external format is 12345600000

case2:

article number is 01234500000

internal format is 0000000000000000000000000000001234500000

external format is 1234500000

is there a way to ensure that we can have the external field name of the article for 11 digits for sure because that would allow me to see the 01234500000 as 01234500000 and not as 1234500000

Thanks in advance

[Former Member · Accepted solution]

Hi,

This is a very common issue in BW. The solution is just to remove the alpha conversion in the info object. If you go into the info object (RSD1), along with the filed type, length, there is also "conv. routine". Just remove the alpha from there and it sets your problem straight.

Hope this helps.

[Former Member]

For Product master, we have option to configure in SPRO. Not sure which infoobject you are using for article.

[Former Member]

Hello APO APO,

I think your InfoObject was set to use conversion exit ALPHA. I believe this conversion exit is not suitable for your case (as you described). One possible solution is to create your own conversion exit which will make sure that the 11 characters in your article will be kept. You can then assign this conversion exit to your InfoObject in transaction RSD1.

To create a custom conversion exit, simply create two function modules in SE37:

1) CONVERSION_EXIT_Zxxxx_INPUT

2) 1) CONVERSION_EXIT_Zxxxx_OUTPUT

You can replace "xxxx" with any string you like. You can see some sample coding by looking at CONVERSION_EXIT_* functions in SE37.

Hope this helps.