Alpha confirming value

while I am doing a load i am getting a Alpha-confirming value 6019999 RSAR 196 error message in Master data. But i have seen the info object setting it has got the alpha setting in it.
But what is the real problem does any can help.Pease...

Hi ,
Said error occurs due to the insufficient length of the data.
Use following function module in the transfer routine of the characteristic.
FM : CONVERSION_EXIT_ALPHA_INPUT.
Pass the characteristic object as input and collect the output in the resulting variable.
It will add required zeros before the 6019999 .
It will solve the problem.
Regards,
Aditya

Similar Messages

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

Alpha confirming in master data

Hi Exprets,
I am having a regular loading issue like one load is getting failed due to Alpha confirming value. we are padding zeros to that data and pushing from PSA to Target. It was solved temporarily. But I required permanent solution to fix it. I written a transfer routine to that info object and then loaded it got successed but in the PSA data is available and in the target level it is not holding the data.
I written the ABAP like this in the Transfer rules.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    INPUT         = TRAN_STRUCTURE-ZZMATGRP
IMPORTING
   OUTPUT        =   RESULT.
Is there any error in coding part please let u throw light on this
Thanks in advance,
Krishna

Hi,
Check the code, just copy and past in SE38 and check.
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

BEx report hangs- selecting Alpha numeric values

I am working on the existing customer report
customer is the selection parameter for my report.
Issue is Customer has numerical and alpha numerical values.
If i give parameter rangs of value is numerical
01 - 500 query works fine
01-50cust1
50 cust1 - 195 cust2
query hangs.
Is their any way we can improve the query performance .
for searching alphanumerica values.
I have a workbook is built based on the query.
morethan 6 queries attached in the sheet 1....sheet2
each sheet has it is own query with values.
when I refresh and execute the workbook with the customer alphanumerica values it hangs.
Query is built based on the multiprovider.
Please help me onthis

Hello,
Try exporting in the 'fully formated grids and text'. It shouldl give you the 'member alias' used in the report.
Looks like if you export in the 'querry ready grids and text' it will show the 'member name' as in database although the report may have used the 'member alias'.
Regards

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.

How do I copy/paste full numerical-only account strings into the Projects WebADI template when the account segment fields in the template require use of the dropdown because they're formatted as alpha-numeric values?

How do I copy/paste full numerical-only account strings into the Projects WebADI template when the account segment fields in the template require use of the dropdown because they're formatted as alpha-numeric values? I'm using the Integrator named "Projects - Transaction Import" and a custom Layout created based on the seeded Layout named "Transaction Import - Accounted". Do I need to somehow change my Layout to make the Document accept numerical values instead of requiring alpha-numeric values? I need to be able to populate the Document with a large amount of transactions and cannot feasibly go through every transaction to add the alpha-valued name of the account segment to every segment that requires it. The segments in particular causing the problem are "Expnd Type" and "Organization Name" which are both alpha-numeric and as such contain the segment number and name; I need to be able to only have to enter the Natural Account Number (6-digit number only) and the Organization Number (5-digit number only).

How do I copy/paste full numerical-only account strings into the Projects WebADI template when the account segment fields in the template require use of the dropdown because they're formatted as alpha-numeric values? I'm using the Integrator named "Projects - Transaction Import" and a custom Layout created based on the seeded Layout named "Transaction Import - Accounted". Do I need to somehow change my Layout to make the Document accept numerical values instead of requiring alpha-numeric values? I need to be able to populate the Document with a large amount of transactions and cannot feasibly go through every transaction to add the alpha-valued name of the account segment to every segment that requires it. The segments in particular causing the problem are "Expnd Type" and "Organization Name" which are both alpha-numeric and as such contain the segment number and name; I need to be able to only have to enter the Natural Account Number (6-digit number only) and the Organization Number (5-digit number only).

Alpha Numeric Values

Hi
IS it supported in GL code combinations to have a alpha numeric values in key segment values .. we have a project segment in our chart of accounts and need the aplpha numeric values eg PRT001 , ADT001 etc . We do have some customizations and wondering if code combinations would have any impact
Thanks
Veda

Yes you can have alpha numerics.
Regards,
Gareth

How to display 'Alpha numeric values' in lower character?

Hi,
We have 'Alpha numeric value' in one column and i need to display alphabets in lower character.
I tried but throwing error.
SQL> select * from a439487.ora_dev_inventory;
HOST_NM HA INV_DT
SMMK94 - 21-AUG-08
SQL> select to_lower(HOST_NM) from a439487.ora_dev_inventory;
select to_lower(HOST_NM) from a439487.ora_dev_inventory
ERROR at line 1:
ORA-00904: "TO_LOWER": invalid identifier
I want 'HOST_NM' to be displayed in lower value.
I need o/p like 'smmk94'.
Any idea?

Where did you find the TO_LOWER function? Can you
show us?I would guess it was just an assumption based on the fact we have to_char, to_date, to_number...
;)

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.

No Value in Confirmation Value Column in Confirmation

Dear Gurus,
                    Mine is SRM 5.0 Version and we are using Extended Classic Scenario. I am able to create a Shopping cart and also approve it.
1.   After Approval the Purchase order is getting held with an Error called "<b>Output: No details for medium PRN im vendor master record</b>", But when i manually go to it and in change option when i go to purchase order and to the sub option Output, there the Printer radio button is clicked and the field is blank, but the Fax and the Email has an entry. So after i click the Email radio button and order, the PO gets order and also created in the Backend. So i want to get rid of this error.
2.   After that when i go the confirmation through the option Confirm Goods/Services and then check the confirmation the Confirmation value is 0.00, which is error. Due to it when i confirm the Confirmation, the confirmation comes in "Error in Process" state and the Service entry sheet is not getting created.
Please Gurus help me in this issue ASAP.
Thanks in Advance,
Mohit.

Hi,
1.See the solution in the foll threads:
Reg Output medium in Purchase order.
Please refer the foll related threads:
Re: Setting the PO output type
Re: PO output (classic scenario)
Re: MySAP SRM Portal Settings
Trigger PO output
BR,
Disha.
<b>Pls reward points for useful answers.</b>

Target finish value and Actual confirmed value for the header material

Hi guys,
For a given production order, I need to get the below mentioned two values for the header material of the production order:
1. Planned or Target finish value
2. Actual confirmed value
will this value be calculated like:
Target finish quantity x standard price of the material (maintained in MBEW-STPRS) = Target Finish Value
Actual confirmed quantity x standard price of the material (maintained in MBEW-STPRS) = Actual confirmed Value
OR
I can get these required value directly in DB table.
Please guide here.
Thanks & regards,
Ravish
Edited by: Ravish Kumar Ojha on Oct 28, 2009 5:41 AM
Edited by: Ravish Kumar Ojha on Oct 28, 2009 5:41 AM

CO03- go to Costs-- Analysis should give you these details.
if you are not OK with the columns appearing, you can change by selecting the change Layout and selecting the required options.
Regards
Ratan

Upgrade to BI 7.0 with non-ALPHA converted values in 0MATERIAL

We are upgrading from BW 3.1C to NW2004s / BI 7.0.
While performing our pre-upgrade checks using RSRV, we found 93,000 of 1.7 million material records which have not been ALPHA converted. This may be a legacy from an earlier 2.0 to 3.1C upgrade where the ALPHA conversion was skipped because the ALPHA conversion would a take "too long"
Our client currently has 500InfoProviders and 500 Aggregates in a 20 terabyte database.
All of SAP's documention for BW upgrades insists upon ALPHA conversion prior to upgrade.
1. Has anyone experience upgrading without ALPHA conversion? I would like to have a chat with you.
2. Does anyone have an easy techinque for detminining if these values are used in InfoProviders? These values are invisible through "Maintain Master Data" This would helps us determine if ignoring or deleting the values is a viable option.
Thank you for your help,
John Hawk

Hi,
As per the standared upgarde guide ALPHA convertion check is not necessary for Upgrade from BW 3.1 to BI7.0.
Note 447341 specifies as shown bellow:
Upgrade from BW >= 3.0B to BW >= 3.1 Content.
In this case, the consistency of the data should be already be ensured by a previous upgrade. As a precaution, a check is carried out in the upgrade PREPARE.
Do not, therefore, implement the solution described under Section 2.1 in this case. In particular, it is not necessary to export a transport created from the BOM RSMD_ALPHA and would in any case result in errors (unknown syntax "R3TR" "TABL" "RSMDCONTCONVEXIT" or "Object R3TR TABL RSMDCONTCONVEXIT requires a catalog entry") because some of the objects no longer exist.
Check weather the error messages that you get is of type(R3TR" "TABL" "RSMDCONTCONVEXIT" or "Object R3TR TABL RSMDCONTCONVEXIT ). then you can ignore thouse error messages.
Refer to 447341.
Regards,
Srinivas.

How to Return only alpha-numeric Values

In my query, I want to return only records for which data in a specific column is alpha-numeric. Any records having this field as NULL, or containing symbols, I want to exclude. What's the best way to do this?
Thanks,
Brice

select str from tab1
where str is not null
and translate(str, '_0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ','_') is null
/Regards
Dmytro

How to generate password alpha numeric value

dear friends,
i have written a simple pl/sql to generate a password.
declare
cursor c1 is select * from passwd;
begin
for I in c1
loop
if I.pfno < 3000 then
update passwd set pwd=I.pfno where i.pfno=pfno;
ELSe
update passwd set pwd=lpad(round(I.pfno/20520),4,'0') where i.pfno=pfno;
commit;
end if;
end loop;
end;
In this the pfno is 8 digit alpha numeric. I get password generated when it is only numeric but how could i get if pfno is like 04MAS155.
Kindly help as i have to generate the same as early as possible. I have already been given with procedure to generate random password by our guys but still as i had already generated password to some employees in my concern based on querries like above i request your help to generate for alpha numeric 8 digit number.

-- get a random string
    FUNCTION string (opt char, len NUMBER)
          /* "opt" specifies that the returned string may contain:
             'u','U' : upper case alpha characters only
             'l','L' : lower case alpha characters only
             'a','A' : alpha characters only (mixed case)
             'x','X' : any alpha-numeric characters (upper)
             'p','P' : any printable characters
        RETURN VARCHAR2; -- string of <len> characters (max 60)
    PRAGMA restrict_references (string, WNDS);

Alpha confirming value

Similar Messages

Maybe you are looking for