Alpha non conforming value

hi gurus,
This ramesh. Please telme anybody HOW DO WE GET ALPHA NON CONFORMING VALUE (ERROR)? WHAT IT MEANS?

HI
You may not have alpha routine exists in transfer rules,please check your transfer rules for your data source,where you getting this error...in transfer rules you will get it in reght side of the left pane..please check against your info object..
and also,Please check alpha conversion has been done or not for this object..you can run it in transaction 'RSMDCNVEXIT'
Hope it helps
Thanks
Teja

Similar Messages

Plz urgent alpha non confirmation error

I am getting this errror alpha non confirmation error
solution

Hi naresh kumar ch
Some times it happens because of Preceding Zeros
Just have a look @ the following links..
Re: Alpha non conforming value
Hope itz clear a little atleast...!
Thanks & Regards
R M K
***Assigning pointz is the only way of saying thanx in SDN ***
**Learning the thingz is never end process if u stop it will Be a devil if u continue it will be a divine***
> I am getting this errror alpha non confirmation
> error
>
> solution

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.

Alpha Conforming Values Error 5323,1461....

Hi All,
I am facing the problem with info object of vendor alpha conforming values error..
I got 53 record errors in PSA level.
Please tell me how to solve this issue.
It's very urgent . plz help to me.
I was checked the Transfer rule alphs Conv check box for vendor.But showing same errors.
Thanks & Regards,
Guna.

Hi,
i am extracting the datafrom R/3 using data source 2lis_05_q0task.
I am getting the error is:-
InfoObject VENDOR does not contain alpa-conforming value 5323.
like that i got few more values like 1461,1561,1643....
Please give me solution how to solve this issue.
Thnaks,
guna
Edited by: gunasekhar raya on Jan 23, 2008 2:25 PM

Infopack Error ( does not contain alpha conforming value 10)

When I try to run my infopack which pulla data from BW into APO, the data load fails with the error below:
"InfoObject /BIC/XXXX does not contain alpa-conforming value 10" when I click on the details icon, I get the following description.
Can somebody please throw some light on this as I am new to DP/BW. Appreciate your help if someone can help me with fixing this problem.
                                                                                Diagnosis
The system checked whether the loaded InfoObject value conforms to the
     conversion exit.The check failed.
For example:
The value '1' was loaded into an InfoObject with alpha exit, even though
     the value '0000000001' was expected.
System response
The load process has failed or the erroneous records are displayed in
     the monitor. This does not depend on how error handling is set up.
Procedure
Find out why the data does not conform to the conversion exit, and, if
     possible, correct the cause. Possible causes are errors in Business
     Content or an error in a customer exit in the source system.
If you cannot correct the problem, you have the option of removing the
     conversion exit on the InfoObject. However, since the system has already
     been converted, duplicates appear in the system again.
Thanks
Varun

Hello Varun,
BW expects your Key Figures to be stored in "alpha conforming format". This is can be roughly described as having 0s in front. For example, if your key figure value is 10, then the alpha conforming value of that is 000000000000000010 (assuming the number of chars in your KF is 18).
To correct the error do the following:
In your transfer rule in BW for InfoObject /BIC/XXXX, implement an ABAP routine that calls function module CONVERSION_EXIT_ALPHA_INPUT. Here an example of the ABAP code you should put in your transfer rule for /BIC/XXXX:
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    input         = TRAN_STRUCTURE-/bic/xxxx
IMPORTING
   OUTPUT        = RESULT.
Hope this helps. Please post again if you have questions.

Vendor non conformance not displaying green in exception

Dear All,
Vendor non conformance quality notification is not displaying green in exception even after completing well before required end date in QM10.
Can you please let me know the logic of report of QM10 for vendor non conformance notification type.
Thanks,
Naren

I assume you executed QM10 with "required start/end" for field for monitor.
-if required start is future : green
-if start is past, but end is future : yellow
-if end is past : red
Exception depends on value of field for monitor on selection screen.
Regards, DoWook KIM

Non-conforming Dimensions modelling

Hi
I am using BIEE version 11.1.1.6
I am struggling to model a situation where I do have 2 fact tables F_1 & F_2 and 3 dimensions D_1, D_2, D_3
D_3 is the only conformed dimension
D_1 is only connected to F_1, D_2 is only connected to F_2.
Content levels for measures in F_1 are set to Total for D_2.
Content levels for measures in F_2 are set to Total for D_1.
In Answers I can't create a report where I filter on one or both of the non-conformed dimensions.
I assume it's still possible to use non-conforming dimensions in analysis
and filter the analysis on values from the non-conforming dimension? (The part of the analysis that can be filtered by these values, measures not connected to the non-conforming dimension will of course not be filtered).
Are there any rules to follow in 11.1.1.6 modelling non-conforming dimensions besides setting measure content level to Total for the non-conforming dimension?
Thanks for your help
Andy

Hi Andy
Please find the blogs it will resolve ur issue.
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
http://www.kpipartners.com/blog/bid/83120/What-To-Do-When-OBIEE-Fact-Tables-Do-Not-Join-to-All-Dimension-Tables
Thanks
NK

Filters on non-conforming dimensions when fetching data from multiple facts

Hi,
I would like to confirm my understanding about how OBI fetches data from multiple facts. I have set up the BMM layer. Through Answers I am getting data from multiple facts as expected. However, is it necessary to base filters only on the conforming dimensions? If I do so, I am getting the correct data. But if I filter data on non-conforming dimensions, then I am getting more data which I am not expecting.
Suppose, Fact1, Fact2 and Fact3 share a CommonDim dimension. If I have a filter on CommonDim, then the filter is used on the three fact tables. However, if I filter data based on Fact1's DimTwo which is not shared by Fact2 and Fact3 and I have measurements from all the fact tables, then from the SQL generated, it seems that OBI is fecting all data from Fact2 and Fact3 and data from Fact1 where DimTwo = 'SomeValue'. Then it seems to be merging the data from the three result sets.
Is this expected, esp. a scenario where a filter is based on a non-conforming dimension (DimTwo in the example)? Have I missed anything? What do I need to do, if I want to return rows from Fact1 based on DimTwo's filter and then if there is data on Fact2 and Fact3 based on the value in CommonDim corresponding to DimTwo's filter?
Please let me know.
Thanks and regards,
Manoj.
PS.: I have got a link now which is http://obibb.wordpress.com/2010/06/06/multiple-fact-reporting-on-non-conforming-dimensions-part-ii/
Edited by: mandix on 25-Oct-2011 12:01

Hi
The problem you describe is similar to mine (I wrote several threads ago).
That is, if there is a non-conformed dimension in a report then the column from the fact table which is not connected with those non-conformed dimensions containes zeros or blanks.
Was this problem solved? I didn't quite catch one of previuos messages... If you can please repeat it more detailed.
What I tried to do is to set Total level in the Content tab (LTS properties). In this example - I could set Total level to JOBS in the plan type dimension. But it didn't help.
So if you know what to do then please describe it here...

Filter and non-conforming dimensions

I have a model design which includes three fact tables with non-conforming dimensions. This causes BI to create multiple queries for a report and finally bring the results together using a full outer join at the end. When I attempt to filter on a field from one of the non-conforming dimensions, that filter is not applied at the full outer join step but during an earlier step related to the chosen filter field. This results in more data returning then desired. I need to move the filter to the full outer join step. Here are two sub-optimal methods that I have found to work around the issue.
1. Build the logical query in answers. Then, wrap that query with an outer query and apply the filter to the outer query.
2. Build a minus query in answers that removes the records you don't want to see.
I have seen this issue discussed in other threads, but I haven't found a good solution. Does anyone have any recommendations?
Thank you,
Edited by: user10715047 on May 21, 2010 7:13 AM
Here is a decent description of the problem
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3297052
and this is a better solution than the two I stated above. However, even this solution is not going to be very intuitive for the users
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3298529

i know this is a bit old thread but thought it might be helpful to someone who came across the same issue...
when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion, Dim X, Measure value you will face the following issues.
when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer.
Please mark if you found this helpful.

Alpha non confirmation error

Hi,
could you help for this below error..
"ALPHA NON CONFIRMATION"give the details of errror

Hi naresh,
In Infoobject screen , we have conversion check box , there we have to give ALPHA as conversion routine. Actually when defining the length of the characteristic, we have to give this ,for example if the length of the your chact is 1(for ex: Pid is 1) , but u have given length while defining chact as 12 then , u get its value as 000000000001 in the infocube , but in the report u get 1 only .
But if u wont give ALPHA as conversion routine there in the Infoobject screen, then u will definitely get ALPHA conversion error.
I hope this will help u a lot.
Thanks& Regards,
Ravi Alakuntla.

Query only non numeric values in a column

How to query only non numeric values in a cloumn.
For example:
Table1 has a column1(col1)
Values:
Row Value
1 27376
2 47D99
3 83039
4 DKFI*
5 3J6
Query should retrieve only rows(2,4,5).
Thanks! for help
Murali

Version 2(PL/SQL) above is not clear enough, It can be tuned to the following:
-- Create a function
Create or replace function IsVARCHAR(pCol VARCHAR2) return VARCHAR2
AS
vNumber NUMBER := 0;
begin
vNumber := to_number(pCol);
RETURN NULL;
Exception
When Others Then
RETURN pCol;
End;
-- To See VARCHAR values (alpha-numeric) only!
SELECT col1 FROM tab1
WHERE IsVARCHAR(col1) IS NOT NULL;
-- To See NUMBER values only!
SELECT col1 FROM tab1
WHERE IsVARCHAR(col1) IS NULL;Versatility here with PL/SQL, but I personally like SQL versions.
Thx,
SriDHAR

Load ODS - InfoObject: InfoObject does not contain alpa-conforming value

Hello everybody,
I get following error while uploading from ODS to InfoObject.
InfoObject /BIC/ZHOUSENUM does not contain alpa-conforming value 0000000000000000004.
The data flow is as follows: Transactional InfoSource -> ODS -> InfoObject.
In the Transfer Rules before ODS I have marked the Conversion check box. The data is populated into ODS without any problems.
I can even activate the ODS, which reporting enabled.
When I browse the ODS table with the option check conversion exits unmarked, I can see the value '0000000000000000004'.
But the upload into InfoObject master data failes
Any help appreciated.
TIA
pawel

sap_all onboard.
I assume, this infosource is locked, due to the fact it was system generated.
On the other hand, there is a s-note 559763 which says:
If an InfoObject is filled with ALPHA exits from an R/3 System, the BW assumes that the data is to arrive in the internal ALPHA format and therefore does not convert the data.
I know, it is about R/3 as source system, but I assume the same would be for BW.
p.

InfoObject REQUESTER does not contain alpa-conforming value 1006152

Hello All,
I am trying to load data into ODS.
The load is failing at "Data Package 6" Record # 11140. I am getting following message at the failed record. -
"InfoObject REQUESTER does not contain alpa-conforming value 1006152".
I went ahead and checked this record # 11140, in PSA, in Package # 6. There the requester field is populated with "1006152" where it is expecting "Some description".
I went ahead and changed the START_ROUTINE. with
LOOP AT DATA_PACKAGE.
IF NOT DATA_PACKAGE-REQUESTER cs 'S'.
DELETE DATA_PACKAGE.
ENDIF.
ENDLOOP.
Expecting that these erroneous records will be removed and will get a successful load.
I am getting the same error message at the same record # and data-package number.
Any help is highly appreciated.
Thanks,
PK.

Hi
when u r having such a problem of Alpha numerical error in a particular for a particular record.Then u just write a Fomula into that Particular formula USE {TOUPPERCASE(REQUESTER)} & thenn reload to the Target...this will solve the problem...to my knowledge..
try this..
HOPE THIS HELPS
THNX
BI Learner.

InfoObject FORWAGENT does not contain alpa-conforming value 100.........

HI ALL,
Can someone through some light on resolving the issue
"InfoObject FORWAGENT does not contain alpa-conforming value 100............"
In "Details Tab" of the monitor screen
Requests (messages): Everything OK
Extraction (messages): Errors occurred --> data selection ended succesfully
T ransfer (IDocs and TRFC): Errors occurred -->some of the data packets not yet processed
Processing (data packet): Errors occurred --> while processing transaction data
InfoObject FORWAGENT does not contain alpa-conforming value 100............"
error occured
Please advice how to solve
Thanking you in advance,
Rase

Hi,
Use ALPHA conversion in the general tab of the infoobject FORWAGENT.
then load the data again.
also in the transfer strcture in the right most side tick the option " alpha....."
Thanks

Non numeric value in numeric field giving error

Hi All
I am using BAPI for creating sales order. If user is giving non numeric value in Quantity field it is giving error. Because quantity field data type is Double.
Please Help.
Thanks
Raktim

Hi Banerjee,
Create a String/int/long Context variable and point it to UI Input element.Do the validation for correct input value. once the validation is succesful assign that value to RFC BigDecimal variable by Explicit casting.
Hope this might solve your problem .
Thanks
Madhan

Alpha non conforming value

Similar Messages

Maybe you are looking for