Substitute of alpha conversion routine

Hi,
Is there any routine as a substitute for the alpha conversion routine. I am getting problem in alpha conversion and the info object is filled by routine to infocube.
I cannot overcome the problem by checking in the transfer rule.
Please provide some input to resolve the problem.
Thanks and regards,
V.Satyanathan

Write your code in start routine to convert it to upper case.
Thanks
Nilesh

Similar Messages

Removing Alpha conversion routine

Hi All,
We have an object which was created with alpha conversion routine and master data is alredy loaded to the same.
Will there be an impact if we remove the alpha routine from the object now. Will this cause any data inconsistency?
Thanks
Jeevitha

Hi,
Check with the following programand implement it in TransferRules/Transformations.
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

Give me details about conversion routine like alpha

give me details about conversion routine like alpha and how many conversion routines are ther and their uses give detail

Hi Deba,
There are many Conversion routines...
ALPHA Conversion Routine
BUCAT Conversion Routine
EAN11 Conversion Routine
GJAHR Conversion Routine
ISOLA Conversion Routine
MATN1 Conversion Routine
NUMCV Conversion Routine
PERI5 Conversion Routine
PERI6 Conversion Routine
PERI7 Conversion Routine
POSID Conversion Routine
PROJ Conversion Routine
REQID Conversion Routine
IDATE Conversion Routine
Conversion Routine RSDAT
SDATE Conversion Routine
WBSEL Conversion Routine
Check this link for conversion routines and its types...
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/frameset.htm
Hope this helps u...
Regards,
KK.

What are the commonly used conversion routines apart from alpha conversion?

hi all,
Can any one let me know the commonly used conversion routines apart from alpha conversion routines ?
thanxs ina dvance
hari

Hari
There are lot of conversion routines, like
BUCAT Conversion Routine. eg. The BUCAT conversion routine converts the internal presentation of the budget type
(0BUD_CAT) into the external presentation (0BUD_CAT_EX), using the active entries in the
master data table for the budget type InfoObject (0BUD_CAT).
see the link below for all the routines.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b9119290-0201-0010-69af-96fe3bf00243
assign points if helpful
Kalyan

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.

Conversion routine to remove leading zeros from nonnumeric values.

Hi,
Can anybody tell me any conversion routine while can remove leading zeros from a character value.
Eg :
input : asdfe
        output : 0000asdfe and vice versa
I tried with Alpha conversion routine but that is useful only with numeric values.
Please help.
Regards,
Deepti Jain.

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

PRODU Conversion Routine

Hi Experts,
We are loading data from APO to BW. However, the Material length in APO is 40 with PRODU conversion routine. In BW, the Material length is 18 with ALPHA conversion routine.
During data loading, if the value is '000000000000000000000000000000000001' in APO, it will display as '0000000000000000' in BW. Please advise on how to correct this. Thank you.

HI
first check in SPRO.. settings configures. 4.3.Specify Output Format of Product Number
IMG > Advanced Planning & Optimization>Master Data>Product> Specify Output Format of Product Number.
For example:
Product Number with Leading Zeros: 000000001234 (zeros up to defined length of product number)
Product Number without Leading Zeros: 1234 (leading zeros removed from product number)
Following the menu path or transaction code above:
u2022 Uncheck the u201Cleading zerosu201D box and save the setting.
thx
vijju

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 for 0Material

In 0Material, we had 'ALPHA' conversion routine. When we run the queries all the leading zeros are truncated .
We have a issue if a material no in R/3 is like 01123. In the query this material is shown as 1123. Users want to see it as 01123.
If we remove ALPHA conversion routine it shows all the leading Zeros and also in the selection we need to give all the leading Zeros(18 Char).
Please do advise.
Thank you,
PVK

Dear PVK,
I tried creating material with number "01123" but system truncates leading zero and gives only 1123 as material code.
And internally at sap R/3 side there is conversion routine which converts "1123" into "000000000000001123".
So i would say that you should keep on the alpha conversion routine at BW side.
Regards
Kapadia

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....

Alpha Conv Routine - IMP

Hi all
I am creating a custom ODS in which i had to use many standard infoobjects
like 0vendor , 0deliv_num etc . for each of these , i get a 'non alpha conforming' value
error during data load . for now ,i have introduced the following code (**) in the transfer rules for
each of these infoobjects . I understand that this will convert a vendor value of '7788' to '0000007788'.
We are fetching the data from a new R/3 custom table . Just wanted to know , if it is a good idea
to populate the table with '0000007788' rather than'7788' in the first place ( rather than
using the code in BW transfer rules ) .
Since this is my first implementation , i am not sure how people usually handle this .
Also , Is it always a good idea to have a conversion routine in all Custom/Z InfoObjects
that we create ??
Pls suggest !
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = RESULT
IMPORTING
OUTPUT = RESULT

Hi,
Yes it is the good practice to use this ALPHA conversion routine.
1. It will help to avoid non alpha conforming value' error. Data in source system may not be consistent. So it is better to use routine.
2. Routines add leading zeroes (according to field length) to the value. It avoids duplication of the values. Source system may have values like 07788 , 007788 and 7788.
Hope it helps.
Regards,
Aditya

Alpha Conversion in node 00000010 for info object 0COSTCENTER

Hi Masters,
I am getting the problem in process chain hirachies. Info Object 0COSTCENETER hier loading the data through process chain sucessfulyy completeed, when saving that hieracies process chain i am getting the error . the problem is " Alpha conversion in node 00000010 for info object 0COSTCENTER".
please give me some solutions
thanks in advance.....
kk

kk,
You can solve by writing an alpha conversion routine in the transfer rules for that infoobject and then load the data.
DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = TRAN_STRUCTURE-0COSTCENTER
IMPORTING
OUTPUT = RESULT.
returncode <> 0 means skip this record
RETURNCODE = 0.
abort <> 0 means skip whole data package !!!
ABORT = 0.

Alpha conversion in 0customer

Hi experts,
In my development system alpha conversion routine is deleted from 0customer.
Now I am trying to put it again but system given me follwing errors.
Follwing tables still contains data.
/BI0/PCUSTOMER
/BI0/SCUSTOMER
/BI0/TCUSTOMER
I also tried to reinstall the 0customer business content but it is not sucessfull.
Can u please help me on this ... it is very urgent.
Regards,
MVS

Hi,
this is a BAD recommendation!
If the system cannot delete this master it is most probably because it is still used in cubes/ods or as attribute of another IObj;
please check your master data deletion log by calling SLG1 with RSDMD and MD_DEL; you'll see in which IObjs your master data IDs are used; you will have first to delete the data is those objects before being able to delete 0CUSTOMER master data;
performing an SE14 will create an inconsistency in your system
hope this helps...
Olivier.

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.

Substitute of alpha conversion routine

Similar Messages

Maybe you are looking for