Add ALPHA-conversion to existing InfoObject

I want to add ALPHA conversion to an existing InfoObject (BW7.0). However the transaction RSMDEXITON which used to perform the data conversion does not work anymore in BW7.0
Are there any alternatives?

hi,
U can define the Alpha conversion routline in Info Object Maintenance..
1. Go to the particulrt infoobject.
2.Double Click to go to Info Object Maintenance.
3. There u can find Alpha Conversion Routine..and check that box.
4. now Save and Activate.
Hope this helps u..
Assign points if needful..
Best Regards,
VVenkat.

Similar Messages

Impact of ALPHA Conversion Urgent!!

Hi,
We have a problem with some of the infoobjects during the upgrade to 3.5.
Some of the custom developed Z infoobjects do not have conversion routine in them when they were developed in 3.0B.
e.g. ZCUSTNO has two customer numbers 01 & 000001.
This is being used in infocube ZSALES & the data in the cube is
ZCUSTNO 01 ZSAL 100
ZCUSTNO 000001 ZSAL 200
We need to add ALPHA Conversion routine in ZCUSTNO.
CASE 1 : Making Customer 01 as A01 & 000001 as A000001.
In order to achieve this do we need to rotate the existing transactional data by adding 'A' in update rule & then loading master data for A01 & A000001 or how do we go about to achieve this. Please give the steps.
Also, if ZCUSTNO is "char 6" so adding 'A' to 000001 makes the length "7" so what can be done for same?
CASE 2 : If we add ALPHA routine WITHOUT adding 'A' to the customer no.
What will be the impact of this on transactional data? will it look as follows ---
ZCUSTNO 000001 ZSAL 300

Hi Vikash,
PPT was really helpful. I'll definitely reward u the points for that but it would be helpful if you could elaborate on some points mentioned in PPT.
"Conversion tables containing the old and new values are built from the SID tables"
Could you pl elaborate what exactly system does? what are conversion tables?
"Characteristics with collisions in the SID table
Marked in RED"
Could you pl give an example when a characteristic will be marked RED.

Leading zeros without ALPHA conversion

Hi all,
we had an infoobject CHAR16 with ALPHA exit, after further analysis we realized that we had to save the field without without trailing zeros so what i've done was to modify the char deleting the ALPHA exit.
I test in DEV this change and the field was populating correctly in the datastore object, for example:
Before
3455 -> 0000000000003455
After
3455 -> 3455
Now i've transported this change in production but it doesn't seem to work, after reloading a chunk of data it's still applying the ALPHA conversion to the field: i've also checked the PSA and i've got the right value.
Any thoughts?
Thanks
Stefano

Stefano,when you remove the alpha conversion from the infoobject then it might create some inconsistencies while loading data and also in reading the value.
Lets say firstly you loaded the data to object with Alpha conversion so value got stored like this :
3455 -> 0000000000003455
Now when you remove the Alpah conversion then value get stored as
3455 -> 3455
System will treat the above entries as two separate records and not single record.Check in system as well.
To display the data correctly you need to enter the value as they are like one with leading zeros and one without then you may be able to see both the records.
Hope this gives an idea.
Regards,
AL

Enable alpha conversion on infoobject, deletion of data no option

Hi SDN forum users
I have this issue where I need to enable / activate alpha conversion on an existing infoobject. The problem is that this infoobject is used in several DSO's and cubes, so many, that deletion of data and reload is not an option (It does not contain Master Data only used as transaction data). Therefore I need to find a solution, that makes activation of alpha conversion possible even though data exits. I have heard about the transaction RMSDEXITON for this, but since we are using version 7.0 this option has been removed.
So how do you guys see the possiblities for me to enable alpha conversion?

Hi.....
U can add the conversion routine for this Infoobject in three ways...
In the BW side...in the Datasource Level
In the datasource >> Go to fields tab >> there search the R/3 field which is mapped to that Infoobject in the Transformation >> Then in the Conv.Routine column select the Alpha Conversion Routine and In the Format column select External....
In the Transformation
Write a field level routine for that particular field abd call the Alpha conversion routine there...
In the R/3 side
In the Customer exit ....Go to SE37 >> EXIT_SAPLRSAP_001 >> Double click on ZXRSAU01 >> search the datasource......write the code there....
Regards,
Debjani....

InfoObject - Alpha Conversion

We have a custom InfoObject INNUM (Invoice Number) in BW 3.0B. It is defined as CHAR 10. Many of our customers send invoice numbers with leading zeros. We need to store and retrieve these invoice numbers as sent.
Unique invoice numbers are as follows:
123
00123
0000123
I have tried 2 options:
With Alpha Conversion the numbers are padded with leading zeros to length 10. They can then be retrieved and displayed as 123, without any leading zeros.
Without Alpha Conversion the numbers are padded with leading zeros to length 10 but can only be retrieved by searching with all leading zeros in the search string (0000000123).
Is the Alpha Conversion functioning as advertised? Is there a way to store, retrieve, and report on the invoice numbers as sent by our suppliers without adding leading zeros?
Best regards,
Mike

It depends on the realeases: in fact to Upgrade to 3.x it was NECESSARY to carry out a massive ALPHA Conversion (so as to remore previous conversion errors). A BW installation born in 3.x (not Upgraded from 2.x) could still have some APLHA problem.
With Aplha it seems to work right (from what you say), without NO! Without Alpha if you store the follwing values:
123
00123
0000123
each of them sholud be retrieved ONLY with the necessary leading zeros (so 123, 00123, 0000123) ... You say that "can only be retrieved by searching with all leading zeros in the search string (0000000123)": this is unusual. In fact if you store 123 on a CHAR 10 InfoObject you will see in S Table /BIC/SINNUM the same value "123" and NOT "0000000123". When attempting with NO Alpha Conversion did you deleted the InfoObjects value?
Hop it helps
GFV

When will Alpha conversion happen

Hi Gurus,
When will Alpha conversion take place if Infoobject has ALPHA as convers routine.
After loading to Infoobject right? Not in PSA.
Thanks Gurus.

Hi,
If conversion exist at definition of info object then it will hapeen at the time of extraction, else it will happen after PSA means where we definied like TR or UP.rules.
Regards
Sankar

BPS - No alpha conversion exit or similar provision?

Dear BPS Experts,
In the Flat File that we are loading to BPS Cube (using the HOW-TO Paper in SDN), if User is having a value 100000006 for Customer and value 10200058 for Material then the flat file upload exit fails. It works only when user changes the value for Customer to 000000000100000006 and value for Material to 0010200058.
I believe, you must have understood my point.
PROBLEM 1
In BW, we have Conversion Exits like ALPHA that take care of internal to external format conversion and vice-versa. Unfortunately, in BPS, it seems system expects users to enter values as they exist in the master data tables like P Tables for Characteristics.
QUE 1: Is my above understanding correct?
We have many characteristics (25-30) in our file and I do not want to write a separate Exit to do any conversion like ALPHA, that would really slow down the performance.
PROBLEM 2
We have a field in the file called 'Manager Name'. Now this field can really have any value. It is not possible for us to load master data in BW for this field. If BPS is suffering from this basic limitation then I am afraid, we can not use it for loading flat file. We have to use only BW
QUE 2: Is there any way, by which I can make BPS accept and load transaction data in BPS Cube even if some master data in that file does not exist. If so, then what is the way to go about it?
I am aware of BW means to load Flat File data to BW/BPS Cubes. But we have many compelling reasons to use Planning Folder to load Flat File. Hence, if some expert can advice about overcoming these limitations with BPS then it would be highly appreciated.
PS: I understand, functionally it does not make sense to plan for something which does not exist in master data. Having said so, there can be some exceptional situations and BPS being the sibling of BW, I expected it to have that capacity.
Regards,
Adi
Edited by: Adi Kulkarni on Aug 13, 2009 3:13 PM

Hi Deepti,
I appreciate your link. That document is very good although it does not solve my problem.
Please note that I am talking about loading a flat file to BPS Cube here and there may be hundreds of values which still do not exist in master data. Your suggested HOW-TO document will be helpful when someone tries to enter data in a planning layout as we do not expect users to enter so many records in planning layout.
I am also aware that we can simply create a Z-Transaction Code (similar to RSD1) to update master data values for a particular InfoObject and Users can be given access to this code. But that is not what I intend to do.
I am looking for a broader and generic solution.
When we load a flat file to BW, we have an option in InfoPackage "Load Transaction Data even if no Master Data exists".. that kind of option or setting really along with something similar to ALPHA Conversion Exits.
Hope my requirement is clearer.
Regards,
Adi
Edited by: Adi Kulkarni on Aug 13, 2009 3:32 PM

Error in global conversion rule for InfoObject 0PERSLANGU when activating

Dear Experts
We are working on HR in BI7.0 with Ehp1.
I am trying to Activate the Transfer Rules of 0HR_PA_PA_1 DataSource which has the BID (BW Development) as the Source System to itself in order to load 0PAPA_C02 (Headcount) InfoCube.
When trying to Activate, it gives the following error message:
Error in global conversion rule for InfoObject 0PERSLANGU
Message no. RSAR263
Diagnosis
Errors with the global conversion rule for the field 0PERSLANGU.
System Response
The function module delivers the following error message:
Incorrect statament: Expression missing Operand mi
Procedure
Check the definition of the global conversion rule for an InfoObject.
In fact, we are Re-implementing 3.0b BW System in new BI7.0 Ehp1 System. I have checked the Config of InfoObject 0PERSLANGU to the one available in existing BWP (3.0b Production) system and it's all the same.
Has anyone come across similar error message and how did you resolve. Any help is very much appreciated.
Many Thanks,
Chandu

HI Chandu ,
It is a bug in the system , can you take a look at the SAP note
Note 1070702 - RSAR 263: Error in global conversion rule for InfoObject
Hope it helps ,
Regards,'
Sathya

ALPHA conversion error in Crystal and MDXTEST

Hello Experts,
I've a BW query which is running fine without errors But when a cross tab report is created in Crystal, we get the below error upon execution:
"Characteristic value xxx of Characteristic ZXX is not ALPHA converted"
The same error when run in MDXTEST.
The InfoObject ZPRFTCTR and all its nav attribs has got ALPHA conversion enabled. Also, I am doing alpha conv in my expert routine of this infoobject.
RSRV checks show no errors.
No error while accessing data from cubes in BW.
This error is only in Q and P not in D.
I've re-activated Infoobject and transformation and transported to Q then reloaded the master data but still the same error.
Have you guys faced this issue before? What could be causing this error. Please help.

Hi,
as this error also shows up in transaction MDXTEST it clearly indicates that the issue is already happening in the BW stack without the involvement from the SAP BusinessObjects tools.
I would suggest you post your question into the SAP BW Forum.
regards
Ingo Hilgefort

Why does alpha conversion not work?

Hi guys,
I have an alpha conversion in an infoObjekt, and this infoObjekt is used in one inforsource, and I have set the check box "conversion" in the transfer rule, but the alpha conversion didn't work.
But when I call 'CONVERSION_EXIT_ALPHA_INPUT' in this field routine, it works...
I can not figur out the reason, please help me.
Any hint is apprreciated.
Regards

hi,
Did you mention conversion Rout as Alpha in the INfoobject.
RSD1 - General - Conversion Rout as Alpha
or you Use the following code at transfer routine to convert using ALPHA.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = trans_structure-<Source field>
IMPORTING
OUTPUT = RESULT.

Alpha Conversion

Hi All,
When scheduling loads in one of the Info objects in Quality, i am getting this error:
InfoObject /BIC/ZITM does not contain alpha-conforming value 90952
I get this error for some other records of the same IO. I checked in our development system in the Transfer structure for'Alpha-Conversion routine' check box of the same Info object. It is unchecked. But, we didn't face any errors while scheduling loads in development.
In the info object's definiton, entry 'Alpha' appears in the conversion routine field in both Dev. and Quality.
What is the reaon for the error durimg loads in Quality?
Thanks.

Hi Roberto,
The Info object ZITM is an attribute of 0Customer.ZITM is not checked for Alpha Conversion in the transfer structure of '0Customer_Attr' in the Development system. There is no problem when loading Customer.
In Quality, though the Transfer structure appears the same, i do get 'Alpha Conversion' error for ZITM when scheduling loads into Customer.
Thanks.

Error in ALPHA conversion while loading hierarchies

Hi,
I got the following error while loading hierarchies:
Error in ALPHA conversion in NodeId00000088 for InfoObject 0PROFIT_CTR
Message no. RH224
Diagnosis
The technical node name for node id 00000088 is not consistent for conversion exit ALPHA, which is stored with InfoObject 0PROFIT_CTR.
Possible reasons for the error:
The original consistent value returned by the DataSource was changed by a conversion routine to a non-consistent conversion exit value.
The DataSource returns a value that is not consistent in the conversion exit.
System response
Loading the hierarchy was terminated.
Procedure
Check whether the correct conversion exit was entered for the InfoObject. If necessary, change the conversion exit, conversion routine or the data to be extracted.
A further option is to activate automatic conversion in the transfer rules. Here, the system executes the conversion exit, making sure that the data is in the correct format.
If it is not hierarchies, we fix this error by prefixing the zeros (as we are working on Qbox we wont change the transfer rules to select the conversion routine) but here there is no PSA, the data is coming from ALE. Based on this please suggest me to how to fix this error?
Points will be given for any helpful suggestion

Ganesh,
Can you please check out the Alpha Conversion Routine and also nodeid for that infoobject..
There might be some inconsistencies in the code..
Hope it helps
Gattu

Alpha Conversion Issue

Hi Experts,
where we can place the ALPHA conversion of "Customer Operational Contract" instead of on InfoObject level ?
Please suggest me the other way to put alpha conversion.....

In 7.0 data source, In Convesion Routines column you can input ALPHA and in Format column, you will need to select external.
This should run the alpha converion while loading data from that data source.
But what think is that it would just convert the way data is stored in the system (same with using FM) but in the query, we will have to input the data with appropriate zeros for value selection for that characteristic.
Regards,
Gaurav

ALPHA Conversion Exit Problem

Hi,
I have an InfoObject ZPRODUCT1 with ALPHA Conversion Exit in RSD1 definition.In the Infosource and in the DataSource/Trans. Structure TAB when i check for the corresponding field it has some other Conversion exit called 'PRID1' and i couldn't change it.
When i load the data i get the error at the PSA level itself and the message is,
InfoObject /BIC/ZPRODUCT1 does not contain alpa-conforming value 80001909.
How to fix this problem?
Thank you
arun

Thanks,
I already did that and it worked properly.
Can you explain how come the conversion exit in Data source transfer structure and the InfoObject can be different?How did this worked?
Will i be able to modify the Conversion exit assignment in the infoobject or Data Source/Trans. Structure TAB? How do i do this, it looks display only in RSD1?
Thank you
arun

Adding Attribute to an Existing Infoobject

Hi All,
I Had a Info object characteristic ZXXX with relavent data in one cube BCSCUBE.
I want to reuse this Infoobject characteristic to built another Cube BPSCUBE with the same data in ZXXX and additional I want to add an attribute to this Infoobject charactersitc. How is this possible.
if I define a new infoobject ZYYY with TEMPLATE property I m not able to get the same values in ZXXX and
if I define a new infoobject ZYYY as REFERENCE I am not able to define the Attribute to this.
Clarify>>ASAP
Sunitha.

Hi Sunitha,
you are right - reference means using the existing InfoObjects and its master data without any changes. Template means you can change whatever you want, but you will have to load master data for the new InfoObject.
If you need to add an attribute that has master data tables with texts and so on I think you will have to create new InfoObject using template approach.
Best regards,
Björn

Add ALPHA-conversion to existing InfoObject

Similar Messages

Maybe you are looking for