Alpha Conversion

[Former Member]

Hi,

I would be very thankful to you , If you give the solution to my problem.

When data is loaded, an error message like the following is issued:RSAR 196: The InfoObject 'X' contains the non alpha-compliant value 4434.

The error message should not occur, since the conversion exit was deleted from the InfoObject.

In the view RSAR_ALPHA_CHECK , I found few records with this Infoobject 'x' having conversion routine "ALPHA'.

As per my knowledge the system sholuld not give any records in above view with this infoobject, after removing the alpha conversion routine at the infoobject.

With rgds,

Anil

[Former Member · Accepted solution]

Hi Anil,

Please look at the OSS Note 486888 "Termination when data is loaded (RSAR196)".

As a workaround, you can delete the InfoObject from the communication structure and then add it again. When you subsequently save or activate the communication structure, the attributes of the InfoObjects are updated.

Best regards,

Eugene

Message was edited by: Eugene Khusainov

[Former Member · Accepted solution]

Hi Eugene,

Right now we are at BW 3.1 .SO is it necessary to do that manually?

Actauly I am doing upload of transaction data. The records i have seen in the view RSAR_ALPHA_CHECK are all the transfer structures for uploading of that infoobject's master data. I did not find the transfer structure of the Transaction data( in which data load the problem is ariasing) in the view.

So There is no problem with our transfer structure .i.e no alpha routine at this infooblect in this transfer structure. But In data loading I am getting problem.

With rgds,

Anil

[Former Member · Accepted solution]

Hi Anil,

Have you read the note?

It says:

Symptom

When data is loaded, an error message like the following is issued:RSAR 196: The InfoObject & contains the non alpha-compliant value &.

Other terms

Monitor InfoSource, RSAR196, ALPHA

Reason and Prerequisites

Prerequisites

The system was already converted with regard to conversion exits.

The error message should not occur, since the conversion exit was deleted from the InfoObject.

Cause

After the InfoObject is reactivated, the conversion exit remains in the communication structure.When the transfer rules are activated, the transfer program is then generated in the same way as if the InfoObject still contained a conversion exit.

This is a program error.

Solution

Depending on your BW system release, you can eliminate the problem as follows:

BW 2.0B

Import Support Package 21 for 2.0B (BW2.0B-Patch21 or SAPKW20B21) into your BW system. The Support Package will be available once note456548 with short text "SAPBWNews BW 2.0B Support Package 21" has been released for customers.

BW 2.1C

Import the Support Package 13 for 2.1C (BW2.1C-Patch13 or SAPKW21C13) into your BW system. The Support Package will be available once note 456561 with short text "SAPBWNews BW 2.1C Support Package 13" has been released for customers.

BW 3.0A

Import the Support Package 4 for 3.0A (BW3.0A-Patch04 or SAPKW30A04) into your BW system. The Support Package will be available once note 425997 with short text "SAPBWNews BW 3.0A Support Package 04" has been released for customers.

As a workaround, you can also delete the InfoObject from the communication structure and then add it again. When you subsequently save or activate the communication structure, the attributes of the InfoObjects are updated.

Refer to note 110934 which contains information on BW Support Package.

[Former Member · Accepted solution]

Hi,

With regarding to this note only i posted last message.

1)The note does not have any information for BW 3.1

2) And In my communication structure , there is a balnk for the last but one column(i.e Conversion exit)of our problem creating infoobject

3)Similarly in the 9 th line of the datasource/transfer structure there is a blnak.

But Still I am getting error.

The workround, provided in the note, can be useful if we are still able to find the conversion routine in communication strucuture, even after the deletion of conversion routine at infoobject defination. ( i.e not in my case).

With rgds,

Anil

[Former Member · Accepted solution]

Anil,

As far as I understand, when you had an ALPHA conversion in your routine, puting your IO into communication structure created transfer programs with this conversion. But even after deleting ALPHA from the definition of your IO transfer programs (for TRs) are still generated with this conversion. According to note's workaround you need:

1. Delete URs for your data target where this IO resides.

2. Delete your IO from TRs.

3. Delete your IO from communication structure.

4. Save and probably activate TRs.

5. Open communication structure again, put there your IO, define a transfer rules, activate them.

6. Create URs for your data target.

7. Load data.

Try it. Hopefully, it should work.

Best regards,

Eugene

[Former Member]

Hi guys,

may be there is a issue with upper/lower case letters. Alpha conversion is only useful for adding the leading zeroes to numeric contents. If you have lower case letters you need to translate them into upper case letters using a routine.

regards

Siggi