cancel
Showing results for 
Search instead for 
Did you mean: 

quetions for conversion routine in DS

Former Member

Hello expert,

I have a few questions about PSA:

(1) if there are conversion routine for some fields in the datasource, PSA data is not same as data in the application system. why we need do such conversion in the DS? because I think we can keep PSA data intact from application data source, and do such conversion in BW transformation .

(2) if there are special requirement for the data format, can we create our own conversion routine used in the DS?

Many Thanks,

Accepted Solutions (1)

Accepted Solutions (1)

former_member210615
Contributor
0 Kudos

hi,

Conversion routines are used in SAP BW so that the characteristic values (key) of an InfoObject can be displayed or used in a different format to how they are stored in the database. They can also be stored in the database in a different format to how they are in their original form, and supposedly different values can be consolidated into one.

In SAP BW, conversion routines essentially serve to simplify the input of characteristic values for a query run time.

For example with cost center 1000, the long value with left-hand zeros 0000001000 (from the database) is not to be entered, but just 1000.

Conversion routines can also be set with data loading. Although it is important to note that conversion routine are often already defined for DataSource fields (esp in SAP source systems). The properties of the replicated DataSource fields are displayed in the transfer structure or DataSource maintenance.

When loading data you now have to consider that when extracting from SAP source systems the data is already in the internal format and is not converted. When loading flat files and when loading using a BAPI or DB Connect, the conversion routine displayed signifies that an INPUT conversion is executed before writing to the PSA.

please refer to example in above post

Conversion routines ALPHA, NUMCV, and GJAHR check whether data exists in the correct internal format before it is updated. For more on this see the extensive documentation in the BW system in the transaction for converting to conforming internal values (transaction RSMDCNVEXIT).

If the data is not in the correct internal form an error message is issued. These three conversion routines can be set in Transfer Rule Maintenance so that a check is not executed but an INPUT conversion is. Make this setting using the Optional Conversion flag in transfer rules maintenance. Both the check and the conversion are executed in the transfer rules for the target field.

Business Content objects are delivered with conversion routines if they are also used by the DataSource in the source system. The external presentation is then the same in both systems. The conversion routines used for the R/3 DataSource fields are then transferred to the BW system when the DataSources from the SAP source systems are replicated.

A conversion occurs according to the data type of the field when changing the content of a field from the display format into the SAP-internal format and vice verse,

Here in BW we have the following conversioins routines:

ALPHA ,BUCAT ,EAN11,GJAHR ,ISOLA ,MATN1 ,NUMCV ,PERI5 ,PERI6 ,PERI7 ,POSID ,PROJ ,REQID ,WBSEL SDATE IDATE

regards,

laksh

Answers (4)

Answers (4)

anindya_bose
Active Contributor
0 Kudos

Hi

Below link will give you some information on your second question..

i.e creation of user defined conversion exit.

http://help.sap.com/abapdocu_70/en/ABENCONVERSION_EXITS.htm

Regards

Anindya

former_member210615
Contributor
0 Kudos

hi,

if want to know more about conversion routines you can refer to the below document

it explains clearly about each of the following conversion routine

http://tleterme.developpez.com/bw/how/konvertierungsroutinen_en.pdf

hope it helps in resolution of your query

regards

laksh

Former Member
0 Kudos

hi ,

You can have conversion routine in BW but it depends on for which field you are using them .

In BW all that information must be available that routine is using .

ex: For WBS element we have a conversion exit that actually convert ps_pnp_pnr field to ps_posid .Whic is both WBS element but in different format .

This coversion exit uses tables on ECC side so cannot be used in BW.Such exits are good for performance if used in ECC side

So you cannot use business specific standard exits however some common exits can be used .

Regards,

Jaya Tiwari

anindya_bose
Active Contributor
0 Kudos

Hi....

one example for your first question .

Date is coming as 11/12/2011 ( via flat file) -


SAP system can not store date as this. so it needs to be converted to 20111112

i.e YYYYMMDD format.

Sometimes when connected to SAP source system conversion routines are being used to check whether the data is coming in correct Internal format.

You can check the below link for further detail .

http://help.sap.com/saphelp_nw70/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/content.htm

Regarding your second question...I think we can have our own conversion routine as these routines are basically made up of Function Module.

Regards

Anindya