Skip to Content
author's profile photo Former Member
Former Member

INCONSISTENCY WITH ALPHA CONVERSION

Hi,

I would like to get your advise on the following situation:

In order to increase the length of an infoobject (ZPACKS), i removed the alpha-conversion. After increasing the length, i tried to put alpha-conversion back. However object could not be updated.

What kind of effects could removing alpha conversion have? Any inconsistencies, or could you state any method to put the conversion rution back?

thanks in advance...

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 05, 2008 at 05:54 AM

    Hello Berna, if your object is not an R/3 related object I mean (customizable object) than you do not need alpha conversion. Alpha conversion heps you format data the way you need.

    Sarhan.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 05, 2008 at 06:25 AM

    Hi Berna,

    Let's say ZPACK was CHAR 4 and had values like '1234'. When you changed it to CHAR 6 the value stored in the DB was converted to '1234 '. Now if you try to re-store ALPHA conversion routine it should be '001234': that's the reason of the inconsistency. I'm afraid that removing ALPHA wasn't a good idea.

    Now if you can't delete ZPACK master data you should carry out APLHA conversion.

    Check out the following OSS Notes about ALPHA:

    447341 Inconsistent char. values for ALPHA conversion routine

    486888 Termination when data is loaded (RSAR196)

    495428 Error in converting inconsistent characteristic values

    543482 Lack of main memory during ALPHA conversion

    559524 Alpha: Parallel processing of the ODS converter

    573619 Test mode during alpha conversion deletes XY table

    575814 Enhancement to ALPHA conversion: runtime estimate

    584416 Guidelines for the ALPHA conversion on oracle databases

    588638 ITAB_DUPLICATE_KEY in preliminary examination of alpha-conversion

    589851 Guidelines for the ALPHA conversion (Performance)

    731140 Multi-column partitioning with ORACLE

    Hope it helps.

    GFV

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 05, 2008 at 06:28 AM

    Hi,

    well normally in your situation you cannot switch alpha conversion on again. The data in the object itself needs to be converted as well then e.g. you had it with lenght 10 so a '1' was stored in the object as '0000000001'. Now after increasing the length to 12, it is still stored as the given example but it has to be '000000000001'. So just with switching alpha on again the data is not alpha conform and you get the error. So you have 2 options: 1st --> leave old data as is and implement a transfer routine using the fm 'CONVERSION_EXIT_ALPHA_INPUT' to get all new data stored in the correct way, but remember, you will get a 1 as '0000000001' as well as as '000000000001' then. 2nd --> call transaction RSMDCNVEXIT to repair the object. For this see also oss note 447341: https://websmp104.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=447341&_NLANG=EN

    kind regards

    Siggi

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.