ALPHA in infoobject

What does Alpha (Currency conversion) mean in an infoobject and what is it used for? I've heard that we only put ALPHA in currency conversion on general tab when we check "With Master Data" for the infoobject. I am not sure if it true but was never given any explaination. Please help.
Thanks,
RG

Hi,
Currency conversion.
Exchange rates.
Exchange rates specify the exchange/conversion rates between different currencies.
Normally exchanges are obtained from the source system.
You can maintain exchange rate factors in TCUR* tables via RSA1 > source system > context menu (transfer global settings check only currencies)/transfer exchange rates.
Select Ex rate type and Mode and execute. It will copy all the current exchange rate from the R/3 source system. This updates currency related tables.
The update of exchange rates updates tables TCURR and TCURV. If you run at the same place the transfer of global settings, the tables TCURF, TCURS, TCURT, TCURV, TCURW, TCURX, TCURC and TCURN are updated.
Also you can look into standard programs RSIMPCUST (global settings) vs. RSIMPCURR (exchange rates) to know what all currency tables will be updated.
If you want to maintain them directly in BW then go to SPRO > General settings and Currencies (SPRO -> Global Settings -> Currencies).Here you can give the USD as your reference currency and you can maintain your values. You can also see the other exchange rates type if maintained in "Check exchange rate types"
OB08 maintains the entries for currency conversion; here you can check whether the exchange rate is maintained to convert the currency from one currency to other.
All currency rates are stored in TCUR* tables
Refer
/people/rasim.manavoglu/blog/2007/04/30/currency-currency-currency
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e473ab90-0201-0010-22ac-fdd925cac167
http://help.sap.com/saphelp_nw04/helpdata/en/ec/076f3b6c980c3be10000000a11402f/frameset.htm
Thanks,
JituK

Similar Messages

Won't let me Change Conversion rouine for Infoobject

I'm having to go back to our development box and change a infoobject to "ALPHA" .
After the change the infoobject won't activate becuase it says "Sid Table /BI0/SUCTMP_AREA contains data" How do I accomplish deleting the sid data? If i use se16 its delete is greyed out.
points for any help
Thanks

Hi Richard,
it is not possible to change the conversion exit to alpha without deleting all data references. That means all transactional data that is using the infoobject as well as the master data itself. The reason for this is, that there will be no conversion of the already existing data in the master data tables (sid-, p-, q-, ... tables). Conversion to alpha means, that all number values have to be converted to the format having leading zeroes. E.g. without alpha your infoobject contains '1'. Now lets say your infoobject is of lenght 10. With alpha your infoobject will contain '0000000001'.
If it is not possible for you to delete all data, you will have to implement a routine using the fm 'CONVERSION_EXIT_ALPHA_INPUT'. But this means that you will have the same data in your infoobject with 2 different formats and this isn't nice at all.
Hope this helps!
regards
Siggi

Error: InfoObject does not contain alpha-conforming value 20030729

Hi everyone,
I got this problem, that i tried to fix yesterday, but all i did was that i got realy frustrated...
I created an infoobject which is copy of 0DOC_NUMBER and has alpha coversion routine.
Mapping field in DataSource is also type character 10(VBELN) as my infoobject.
But there are some values in this field that i am trying to load, less then 10 characters long (20030729,20051116...) and shouldn't be there, because the values are dates and not document numbers.
But anyway on R/3 side this values are in field which is defined as character 10 (VBELN), and when I am trying to load Infopackage(17500 records) I get 52 errors: InfoObject does not contain alpha-conforming value 20030729.
I don't get it, since both fields are type character 10 and the values are only digits, why do I get this error message and how can I fix it?
PS:One solution is to remove alpha conversion routine from infoobject, but i don't want that.
Regards,
Uro

hi,
sorry... correction, it's 'Exclusive attributes' that cannot be used for navigational attribute, you can set lower case to differentiate ... check the impact of lower case setting here ...
http://help.sap.com/saphelp_bw33/helpdata/en/b7/f470375fbf307ee10000009b38f8cf/frameset.htm
Lowercase letters allowed / not allowed
If this indicator is set, the system differentiates between lowercase letters and capital letters when you use a screen template to input values. If this indicator is not set, the system converts all the letters into capital letters when you use a screen template to input values.
If you choose to allow the use of lowercase letters, you must be aware of what happens when you input variables:
If you want to use the characteristic in variables, the system is only able to find the values for the characteristic if the lowercase letters and the capital letters are typed in accurately on the input screen for variables. If, on the other hand, you do not allow the use of lowercase letters, any characters that you type onto the input screen, are converted automatically into capital letters.
Exclusive attributes:
If you select Exclusively Attributes, the created characteristic can be used only as a display attribute for another characteristic, and not as a dedicated characteristic in the InfoCube. Furthermore, you then cannot transfer the characteristic into InfoCubes. However, you can use it in ODS objects or InfoSets.

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

Infoobject Conversion Routine Alpha

Hi All,
At the time of creating infoobjects under General Tab we have option Conversion Routine : Alpha (by default), can anybody put light on that what is that exactly.
Thanks and Regards
Asim.

Hi,
See the following program, and the same logic you can apply in Transfer Rules/Transformations. Take ABAPer help.
REPORT ZALPHA_INPUT.
DATA: ZI(18) TYPE C,
      ZO(12) TYPE C.
DATA: ZS(12) TYPE C,
      ZR(18) TYPE C.
      ZI = '000000099999889925'.
      ZS = '099999889925'.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      INPUT         = ZI
   IMPORTING
     OUTPUT        = ZO.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
    EXPORTING
      INPUT         = ZS
   IMPORTING
     OUTPUT        = ZR .
Write:/   ZI.
Write:/   ZO.
Write:/   ZS.
Write:/   ZR.
Thanks
Reddy

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.

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 does not contain alpha confirming values

Hi ,
I am trying to load data into the object called ZAML_CODE, the type is CHAR and Length is 3.
The characteristic is enabled with ALPHA - Conversion exit.
we are loading data to this object since 3 years successfully.
But now only it is saying that InfoObject ZAML_CODE does not contain alpha confirming values.
Especially we are getting error for numeric values like 1, 2,3 etc only.
Previously numeric values were also loaded successfully.
Now the source system is ECC6.0, previously it was 4.6C. This is the only difference.
Please respond with your suggesions.
Regards
Srinivas

Hello,
Just check if there is space in the front of these numeric values or some garbage value...if there is... then it may not be able to pad it up with zero and hence the issue...check in R/3 about how these values are stored...you can remove the space from the front and change it in PSA...and then load but first do the analysis of the source system and see why its coming up wrong.
Regards
Ajeeet

Question about Alpha option in the transfer rules for infoobject

SDN Experts,
I know that we check the Alpha conversion for only numbers like 0,1,2. this alpha option puts zeros in fornt of numbers but what happens when we get characters words for example 'Apple' does it put zeros infornt like '00Apple'?
i will assign points, Thank you.
Les

Dear Les,
Alpha Conversion is used to store the input data or incoming data in the Defined Internal Format , and it at the time of displaying it displays in the User defined format..for eg ...date field..the system stores as YYYYMMDD and it gets displayed as DD.MM.YYYY ( or any specified format by the user ) , this is usually for Numbers as the length needs to be maintained when storing at the database..
and at the time of display it pads the zero's and displays...
you can also check CONVERSION_EXIT_xxxxx_INPUT , CONVERSION_EXIT_xxxxx_OUTPUT function modules where XXXXX denotes a Conversion Routine..( Eg ALPHA ) ...
Hope it helps..
Thanks,
Krish

InfoObject does not contain alpha conforming 1

I am getting the above error message when trying to load text. I found on several posts that I should change the Conversion column of the Transfer Rules. But I am trying to determine why this is happening because when I run these loads in the DEV box, they run fine. I transport the rules to our QA box, and that is when I have the trouble loading and get the error. I check the data in RSA3 and there is no difference, so it can't be data related.
If the data is the same, and the rules are the same, what could cause it to work in one box and not the other?
Thanks, Keith j

Hi Keith,
do you know the source table for the data? Please check that if possible via se16. Sometimes, specially with alpha conversion, even a 0001 from database is displayed as 1 and may lead you to the wrong way. If all settings are the same in your systems it surely must depend on the data itself. May be the better way analyzing the data from the source table is se17.
kind regards
Siggi

Infoobject Length changes with ALPHA conversion

Hi,
I am facing a problem with changing IO length changes.I need to change the charecteristic XCUST of Length 20 with alpha conv to XCUST of Length 30 with alpha conv.
When i am trying to do that sytem is asking me to delete the master data as well as transaction data.
In the cube i have 3 yrs data,that shuld not be disturbed.
Dear experts is there any way out for this prob. Please suggest with the steps to be followed.
Thanks,
CHVR.

Hi,
As far as i know, you cannot change the settings of a characteristic without deleting the content.
I passed trought the same situation and i had to delete the master data + ods data and then change it.
Sorry.
Regards

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.

Alpha-convers. in BW but no leading zeros from source system

Hello all,
I want to load customer data via XML. The data are delivered via XI every night in a delta-queue in BW. From the delta-queue the data gets loaded into an ODS.
From the source system I get the customer number with 6 characters, but in BW I have a alpha conves.Routine in the InfoObject 0SOLD_TO and 0CUSTOMER.
How can I fill in leading zeros to the values? Do I have to do this in the InfoSource setting or in the update rule?
Any ideas would be great.
Thanks upfront and Best regards,
Stefanos from Munich/Germany

Hi,
Try checking the option in the transfer rules. Aganist the Info Object 0Customer you'll have to scroll to right then you can see the check box called conversion . Check that & try loading the data.
Other than this you'll have to go with the routine.
Regards,
SB

ALPHA in infoobject

Similar Messages

Maybe you are looking for