Conv Routin in DataSource

Gurus,
This is the generic DataSource created in R/3, and replicated into BW. In RSA1, I double-click on the DataSource. In the Field tab, I can see the list of fields used by this DataSource. However, I noticed that the Conversion Routine exist for the field PROID in this DataSource, under Column SS Conv. Rout. In the F1, it says:
Conversion Routine in Source System (Outside of BW)
Why the conversion routing is assigned to this field? What does this mean? How can I remove this?
Please help.

not answer

Similar Messages

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

Start routine update rules

Hi Gurus,
We are nw04s BI SP10 and I've completely implemented Note 981194. I can't seem to get my start routine update rules to convert using Transformation Erzeugen. I tried several scenarios, and still no success.
If somebody has code for BI 7 transformation start routine for datasources 2LIS_03_BX, BF and UM to the 0IC_C03 cube, I would greatly appreciate an email to [email protected] . Points will be assigned. I can cut/paste the routines from the update rules, I just need the start routines.
Kind Regards,
Alex

Alex
Don't trust the converter - you have to check it all from end to end anyway so might as well do it manually.
I did the whole of _BF yesterday.
Here's the start routine.
*<2004s code>
 field-symbols:
 <fs_SOURCE_PACKAGE> type tys_sc_1.
only movements from to evaluated stocks are concerned
if stock-category is not intitial -> Delete from data-packag
or Header of generic article -> Delete from data-packag
 loop at SOURCE_PACKAGE assigning <fs_SOURCE_PACKAGE>.
 if not <fs_SOURCE_PACKAGE>-bsttyp is initial
 or ( <fs_SOURCE_PACKAGE>-bwvorg = '450' and
 <fs_SOURCE_PACKAGE>-bwapplnm = 'IS-R' ) .
 delete SOURCE_PACKAGE.
 endif.
 endloop.
*</2004s code>
Cheers
Guy

Conversion Routines - R3 and BW

I need to create a custom InfoObject in BW to map to an R3 field in an InfoSource. The R3 field has the ABPSP converions routine applied to it. As a rule of thumb is it always best to apply the same conversion routine to the matching BW InfoObject?    Is there a time that I wouldn't want to match the conversion routine of the R3 field to the matching BW InfoObject? Your help is appreciated.

Hi David,
    Conversion routines in BW will aid in eliminating the technical differences of data format to be acceptable by the BW system. You cannot directly map R/3 Conversion routine to BW Conversion routine as far as my knowledge goes. Please map the infoobject in BW with the R/3 field directly and check if the converted data is directly coming into BW from the R/3 system as you said there is a conversion already existing in R/3. If this doesnot solve your problem, then you can create your own conversion routines using SM37 t.code wherein you will create your conversion rule specifying CONVERSION_EXIT_XXXXX_INPUT and CONVERSION_EXIT_XXXXX_OUTPUT. Where XXXXX is a 5 letter user-specified name of the Conversion. INPUT code is written for converting sourcesystem data to be acceptable into BW tables. OUTPUT is written to converting the BW data into acceptable reporting display. You need to activate both the function modules created in order to use them during infoobject property settings. While using them you can directly see the XXXXX (user-specific) conversion during infoobject conversion settings.
        Hope this might be helpful to you. Award points if useful.
Thanks
Kishore Kumar

Char NUMC(5) - need to store value at database level without leading Zeros.

Hi All
We have 0Mat_Item like infoobjects in SAP BI, which have data type Char NUMC(5). Here if u load value '1', it would show us '1' at front end (BI or reporting level) but at database level stores as u201800001u2019.
My requirement is to store this value without leading zeros at database level. I wrote code in transformation u201Cshift u2026 left deleting leading u20180u2019 u201C & could load the data into New data table and at database level as I was getting result without leading zero. But once I activate the request, it gives SID generation error u201CValue '1' of characteristic 0ME_XCHRATE is not a number with 000009 spaces.u201D
How to solve this issue so that I could store u20181u2019 value instead of u201800001u2019 value in the database & could able to activate in DSO.
Thanks....

Hi.....
System may be storing the data in that way to maintain consistency.
Alpha conversion is used to store data consistently. It does this by storing numeric values prefixed with 0s Eg. If you have defined a material as length 6 (of type Numc) then material number 1 is stored as 000001 but displayed as 1; this removes inconsistencies between 01 vs. 001.
U can add the conversion routine for this Infoobject in either below way...
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....
Hope below link helps you.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7108a690-0201-0010-4cbc-9bca94f9ad9c?quicklink=index&overridelayout=true
Regards,
Vinay.
Edited by: Vinay Joshi on Mar 10, 2011 4:54 AM

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

Error while loading data from a file on application server

Hi all,
Facing an error while loading data from a flat file.
Error 'The argument '##yyyymmdd;@##' cannot be interpreted as a number ' while assigning character.
I changed the format of date fields (tried with number,general,date(International))in the xls. But i still get the same error.Did check all the data types in Data source all the fields are dats.
Can you please tell me what could be the problem?
Thank you all,
Praveen

Hi all,
As far as my first question i got through it but i had one more field in my flat file while actually is a time stamp, but in my flat file i have a data in this format
10/21/2006 5:11:48 AM which i need to change to 10/21/2006
one more note is i have some of the fields as NULL in this field
Last Updated Date
10/21/2006 5:11:48 AM
10/21/2006 5:11:48 AM
NULL
NULL
10/21/2006 5:11:48 AM
NULL
I want to display the values as 10/21/2006 and NULL as it is.
Please let me know if we have a conversion routine in datasource which can solve my problem.
Regards,
Praveen

Error in Data Extraction - Urgent

Hi,
I am getting the following error while extracting master data for 0INFO_REC.
Value '000000000000101034 ' for characteristic 0MATERIAL is in
external format
Thanks

Hi Shiva,
Unfortunately I dont access to my BW system today. So I do not know the exact conv routine for 0MATERIAL.
You can instead try this: Go to the transfer rules and for the 0MATERIAL info-object check the check-box for Conversion. Then retry the load.
Hopefully it should work.
Bye
Dinesh
(Do not forget to assign points!!).

InfoObject not appearing in Formula Builder

I have an active set of ODS update rules, and am trying to use formula builder to "RIGHT 8" the values of one of the source fields. For example, my field is packed with 00000000CUSTNAME, and I want to trim right 8 to CUSTNAME.
However, when I look at the available fields in the left-hand selection table, all I can see are system fields, and nothing from my transfer structure. How can I actually manipulate my source field if I can't input it into the expression? How do I get the source fields to appear as candidates for manipulation in the formula builder expression? I can find nothing on this issue from help.sap.com itself. Thanks, Doug

Hi Doug,
Was the update rule created based on the Infosource then you should be able to find it in the formula section. Also if you want your Cust name to appear without the trailing zeroes then you dont need the formula as SAP would take care of it if you have the alpha conv routine checked for custname.
Bye
Dinesh

Conversion the land1 field

Hi,
I want to convert the land1 values 'us' to 'US'.
These values in a internal table so please tell me how to do it.
Which function module i can use for this.
I already search for conver routine but there is no conversio routine for the field land1 in tzone table. so please give me some idea....
Advance thanks,
Kumar A.

hi Anil,
Use Translate statement ..
data : v_land1(50) type c value 'us'
translate v_land1 to upper case.
write : v_land1.
Regards,
Santosh
Message was edited by:
Santosh Kumar Patha

ALV problem with zeros

Hi guys,
 I have a problem in ALV. There is character field which is company code , whenever the value is '000'or 010' it is displaying as '0' or '10'. can you please help me on this. here is the field catelog for this... it is really urgent.
CLEAR e_fieldcat.
ADD 1 TO w_col_pos.
e_fieldcat-fieldname = 'AUFNR'.
e_fieldcat-seltext_m = 'Company Code'.
e_fieldcat-col_pos = w_col_pos.
e_fieldcat-no_zero = space.
e_fieldcat-lzero = 'X'.
e_fieldcat-edit_mask = '==ALPHA'.
APPEND e_fieldcat TO t_fieldcat.
thanks.

Hi Lakshmi ,
wa_fieldcat-edit_mask = '==ALPHA'.
wa_fieldcat-edit_lzero = 'X'.
If this doesnt work.

Declare the field as type MARA-MATNR.

BCOZ conv routine for MATNR IS MATN1.
Usually, if all is well, this will be handled automatically, for example, if on a dynpro, all you need to do is set the conversion routine value to ALPHA, then the conversion will be automatic, nothing to code. If in a list display, the field should be TYPE MARA-MATNR, then the conversion will be automatic on the list display, as well as the ALV grid.
Reward points if helpful
Regards
Naresh

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

Leading zeros in report.

Hi,
I have got a char Tracking number of type numc . I have loaded the data using alpha conv routine. So when i look at cube content my char is showing leading zeroes for the values. but in reports I am not able to see leading zeroes. what setting needs to be done and wher should I do it to obtain values with leading zeroes in report??
thanks in advance.

Interesting Issue...
Jst in case are you looking at the same data/same selections ?
Any Coding/VBA used to suppress zeroes ?

When is a conversion exit triggered?

Hi,
are conversion exits only triggered via GUI:s ?

Hi
Conversion Exits will triggered when u r input/output to a perticular data element which is associated with domain which is attached with conv routine.
take an example
suppose
kunnr a domain whih is attached with ALPHA
if i am giving 80 to store it in database it will store 0000000080 as its length is 10 char
and while ouput it will show me 0000000080.
i think now u got
if helpful
Reward me points
Regs
Manas Ranjan Panda

Displaying leading zeroes

Hi,
I am facing a problem in displaying leading zeroes for a char in a BW report. This char has length 4 and it should show the value as 0ABC in the report but instead it displays just ABC. When checked the info providers, the data is right there.
Technical details: length - 4, Conv Routine - ALPHA, BEx display - Key & text
Could someone please throw some light on this?
Thanks a lot in advance.

Hi Bobs,
Here is what I understood from your query;
You have leading zeros for the char info object in the info provider but while running the query it is returning with the rest of the characters but not leading zeros?
Yes while loading in to info provider ALPHA conversion does add any leading zeros according to the char size to load in to the info provider but while reporting it does the reverse ALPHA. but you have to check the values in the master data for the char info object where the default option for query results on char objects to retrieve key and text values from char object master tables. I think the master data for the char info object might not be have leading zeros.

Conv Routin in DataSource

Similar Messages

Maybe you are looking for