Conversion of 3.5 routine to 7.0 routines

Hi,
I am working on implementation project, we are installing objects from business content, all objects are from 3.5 version like infosouce communication structure, update rule data source, our standard guideline is all objects should convert into 7.0 version.
so we are creating Transformation using 3.x data source, my question is I need to convert all field level routines into 7.0 version in transformation level with reference of 3.x field routines. When I copy past getting lot of error.
I am changing DATA_PACKAGE to SOURCE_PACKAGE still getting abap error. Please let me know is there any PDF available to convert 3.x routine to 7.0 routines. Please help me out on this.
Thanks,
Manu.

Hi,
This reference documents will help you on this :
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00d94ca8-9538-2c10-9b99-859afde1fa4a]
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a05c5e57-5501-2e10-36ae-df0d96be2e5d]
Regards,
Avinash

Similar Messages

Start Routine: Syntax error in routine 2LIS_03_BF Transformations

Hi experts,
I enhanced the 2lis_03_bf data source, and replicated the data source in bw system, i have mapped the transformations and when i try to activate the transformations it is giving the below error.
Start Routine: Syntax error in routine
when i check the start routine it is giving the below error message.
E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
"SOURCE_PACKAGE" is incompatible with the formal parameter
"DATA_PACKAGE".
please provide me the solution.
Regards
venuscm

Hi Venu,
This seems to me like you have earlier migrated the update rules to transformations. We did the same earlier and faced issues whenever we add new fields/infoobjects. The error message was different, if i remember correctly.
We had to add the new field/infoobject added, to the structure '_ty_s_*****' that exists at the top of the start routine code. This was one disadvantage of migration of rules.

Start Routine or Update Rule Routine

Hello Dear Friends
I have a requirement here to create an object lets call it TYPE and i am using another infoobject called movement type.
My requirement in the cube is that TYPE should indicate A if movment type is 123 or 456 and B if movment type is 789.Anything else other than these numbers dont need to make it in the cube either for Movement type or for TYPE and needs to be deleted.I believe this will be a routine in the Start Routine.If not please let me know.Also if someone can give me the code on how to write the routine will be really appreciated.
Thanks again.

hi,
Go for an Update routine as you do not have the TYPE in the Data source.
if ( comm_structure-momenttype = '123' or
   comm_structure-momenttype = '456' ).
comm_structure-type = 'A'.
elseif comm_structure-momenttype = '789' .
comm_structure-type = 'B'.
endif.
Adn in the start routine :
delete data_package where momenttype ne '123' and
                                         momenttype ne '456' and
                                         momenttype ne '789' .
If you can add the type in the data source then write the below code.
delete data_package where momenttype ne '123' and
                                         momenttype ne '456' and
                                         momenttype ne '789' .
loop at data_package.
if ( data_package-momenttype = '123' or
   data_package-momenttype = '456' ).
data_package-type = 'A'.
elseif data_package-momenttype = '789' .
data_package-type = 'B'.
endif.
modify data_package.
endloop.
good luck

ABAP routine - Transfer rules Start routine

hello everyone,
i need some help in writin an ABAP code. Well the logic is say i have a table which sends data to BW. the data comes like :-
Order        Q1
101           50
101           20
102          10
101           60
But i want to store only 1 value for each order , i.e summarize the value so in when the data package comes , i want to check all records for one order and add the qty value for each order and store it in the ODS.
so ODS for above eg should look like
Order qty
101    130
102       10
Thanks,
Will assign points to all helpful answers.
Laura.

Hi:
If you add Order as the only Key FIELD in ODS and set the Key-figure Q1 to Aggregation, it will solve your problem. You don;t need additional code.
NOTE: If this is not the case, its not easy to write this in ABAP. because, you don't know whether all Orders (e.g., Order #101) will come in the same DATA PACKAGE. They might be split into two different DATA PACKAGES and your Start Routine will Execute ONLT ONE DATAPACKAGE at a time.
Chamarthy
Message was edited by:
        Chamarthy

How Routines works while using Routines in Data loading?

Hi Frds,
A routine how it works in background while using in data loading?
Thanks & Regards,
Laxmi.M.

Hi Suma,
This is probably the wrong area for you to post your question. While SAP has recently rebranded some of its data warehousing solutions (Business Objects is now SAP Business Objects Business Intelligence and what was SAP Business Intellgience is now SAP NetWeaver Business Warehouse), the forum categories have not changed names.
For questions regarding Data Servers (hybrid of Data Integrator and Data Quality), you will want to post to the Business Objects > Enterprise Information Management forum instead.

End routine for Currency conversion

Hi,
I have a requirement in which i have to convert sales and cost into three types of currency as GBP, INR and EUR in cube. i made 3 different fields for sales as well as for cost. But i am unable to write end routine for it.
Can anyone please help me that how can i solve this problem.
Roma

Hi,
In transformation itself you can do your currency conversion.
http://help.sap.com/saphelp_nw70/helpdata/en/de/6372426f0f9041e10000000a1550b0/content.htm
If you want to write a routine in to do conversion, you have to go for start routine instead of end routine.
Thanks
BVR

How to remove conversion routine "ABPSN"

Dear gurus,
In my transfer rules, under the tab "DataSource/Trans. Structure", I have a field PSPID whose "Conversion Routine" has the value "ABPSN". This conversion routine converts the external format to the SAP format which, however, is not what I want. I want to remain the original format so I need to remove this "ABPSN" conversion routine. When I double clicked it, it linked to the InfoObject 0PROJECT maintanace screen. On that screen, I removed the conversion routine "PROJ" for 0PROJECT, but still ABPSN remains and the data loaded into the InfoCube have been converted.
So how can I remove this ABPSN convertion routine?
Thanks in advance.
Jin Ming

Hi Jin Ming,
Conversion Exit ABSPN is related to WBS element and not project at R/3 side.
But at BW side this routine internally calls Project routine .
The Process is,
1. Delete all transactional data , from related ODS & Cube wherever 0PRoject is used .
2. Delete master data from 0Project.
3. Change object 0Project remove the conversion using Tcode RSD1.
4. Load master data for 0Project.
5. Load transaction data.
Hope that helps.
Regards
Mr Kapadia

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

ABAP Conversion Routine

HI,
I want to create Conversion Routine andI know Coversion Routine was linked with Domain,
Domain that I want to create Coversion Routine was used in serveral tables.
I want to run Coversion Routine at specific table and I doesn't want to change domain name.
Any ideas.
Regards, Arnold.

Thanks for Comments but I have basic knowledge for Converion Routine.
My question si that Can we run Conversion Routine at Specific Table ?
For example, we created Conversion Routine "A111" for domain "D111".
Domain "D111" was used at table ZT001, ZT002, ZT003.
I want to run Conversion Routine "A111" at only table ZT001 because table ZT002, ZT003 has
differenent meaning for domain "D111".
Any Ideas ?
Regards, Arnold.

Restriction of sales order conversion to billing request for projects not r

Dear all,
We have SD integrated with Project systems. Each of the sales order is linked to the WBS element of the project which has to be billed. Sometimes a project which is not released is attached to the sales order and while billing it doesnu2019t get posted to accounts because that project/WBS element is not released. Is there a way to restrict conversion of sales order to billing request if the project is not released?
Looking forward for help.
Thanks and regards,
Padmaja

Define a new condition type and assign it to the pricining procedure
In the requirement routine have a new routine and put a logic so that it compares the subtotal field A of nett price
For e.g KOMP-NTPRC
The condition type should apply when KOMP-NTPRC < =the draft amount
You have to try this
I havent done it practically
Regards
Raja

Currency Conversion for Exchange rate type "AS02"

Hi Experts,
I am gonna post the most challenging problem (regarding currency conversion) I ever faced in my 1 year of BW Carrier.Kindly provide a solution.
There are three types of currency to be used in the query for Key Figure 0NET_VALUE (so total 3 Key Figures to be created)
   1.Document currency (may be any currency)
   2.Local Currency (must be EURO)
   3.Global Currency (must be USD)
From Document currency to Local Currency(EURO) we are using Exchange rate Type "M" (in Conversion Type created in Trans RRC1) [There is no problem in this conversion]
Problem starts now--->
From Local Currency(EURO) to Global Currency(USD) we have to use Exchange rate type "AS02" (in conversion type to be created in RRC1)
but there is a Business requirement that currency rate should be as per the last day of the entered period;and this logic should work for the range of periods also.
Example :
we are executing query for the period 006/2006 (posting Period)
Last day of this period is 06/30/2006,
Currency rate would be as per 06/30/2006
And this currency rate should be same throughout the period 006/2006 in query
The example was for single period,but logic must be incorporated for the range of the periods.

Hi..
There is no corresponding source key figure in the InfoSource for the target key figureof the InfoCube.
a. A source key figure of the same type can be assigned to the target key figure
(for example, sales revenue instead of sales quantity revenue).
If the currencies of both of the key figures are the same, no currency
translation can take place.
If the currencies are different, a translation can take place either using a
currency translation type or by simply assigning a currency.
The following table provides an overview of possible combinations with different
currencies in the source and target key figures:
if Source key figure currency is fixed , Target key figure currency is variable then Currency translation (CT) No CT
if Source key figure currency is fixed , Target key figure currency is fixed then Currency translation (CT)   CT
if Source key figure currency is variable , Target key figure currency is fixed then Currency translation (CT)   CT
if Source key figure currency is variable , Target key figure currency is variable then Currency translation (CT) CT or assignment
b. If there is no corresponding source key figure of the same type, then you have
to fill the key figure for the data target from a routine.
If the target key figure has a fixed currency, no currency translation is
carried out. This means that if translation is required, you have to execute
it in the routine.
If the target key figure has a variable currency, you also have to assign
a variable source currency to the routine. Using the F4 help you can
select a currency from the variable currencies in the communication
structure. You have two options:
You can select a variable currency and assign it.
You select a currency translation type and a currency into which you
wish to translate (To currency).
The To currency is, by default, the target currency if it is included in the
communication structure.
Creating a Routine for Currency Translation:
If you want to translate currencies in the update even though the currency translation is not
available for one of the above reasons, you can create a routine. Choose Routine, set the
Unit Calculation in the Routine and choose Create Routine. In the routine editor you get
the additional return parameter UNIT, the value of which is used to determine the target
1. save the query and it under role
   see to it is in   : Restricted and calculated key figures --->   properties of k.f
2. exeute the query
3. the currency translation --> by target currency usd choose OK
conversion type : MEANTODAY Fixed target currency current date (MT)
4. Go back to the query definition by chossing chage query ( global definiton)
5. in the context menu for % share sales vouume of incoming orders, choose properties --> formula collision --> result form this formula choose OK
Note that -
your should alos set the currency translation in the properties for the two key figures sales voule EUR , choose properties ---> currency conversion key : fixed target currency , currrent date ( MT) --> target currency : American Dollar . choose   OK
<b>The translation key is a combination of different parameters that establish how the exchange rate for the translation is executed.
The parameters that determine the exchange rate are the source and the target currency, the exchange rate type and the time reference for the translation.</b>
The source currency is determined from the data record or dynamically from the master data of the specified InfoObject (currency attribute)
The target currency can either be fixed in the translation key or selected at the time of translation.
You can also use an InfoObject (currency attribute) to determine the target currency.
The exchange rate type distinguishes exchange rates that are valid in the same time frame next to each other, for example, the bid rate, ask rate or middle rate. The exchange rate types are stored and can be maintained in a central table (TCURV).
The time reference for the currency translation can be either fixed or variable
The fixed time reference can either be a fixed key date that is stored in the translation type, or be determined using the system date when executing the currency translation.
If the time reference is variable, then the point in time for the exchange rate determination comes from the value of a time characteristic (InfoObject). The reference can, for example, be the end or the start of a fiscal year or a calendar year, a period and a month or even to the exact day. It can also be determined using a customer-specific InfoObject (for example, trading day).
Currency translation in the BEx
When selecting a translation key with a fixed target currency     this currency will be added automatically to the query definition
Also, you can use translation keys selecting their target currency at the time of translation. These can be applied in two different ways:
Selection of a specific target currency in the query definition (1)
Entry by variable (2)
Dynamic translation keys require input from the InfoCube !
InfoObject value will be read during query execution
Examples:
dynamic time reference (p.eg. 0CALDAY)
      time characteristic
target currency determined by InfoObject (currency attribute)
     characteristic which contains currency in its attribute table
the corresponding InfoObject has to be part of the InfoCube
1.Define the currency attribute in the InfoObject maintenance
The currency attribute has to be a unit InfoObject of type currency
The unit InfoObject must be an attribute of the characteristic
The currency attribute should be filled in the master data table of the corresponding InfoObject (manual maintenance or upload via InfoSource)
2.Enter the InfoObject in the translation key maintenance
Only InfoObjects with a currency attribute can be used in translation keys (p.eg. 0COMP_CODE)
At the time of currency translation the value for the source currency / target currency is then derived for every record from the master data table of the specified InfoObject
All values for a query are translated ad hoc (after having executed the query) using a translation key
Depending on the translation key a fixed target currency will be used for translation or you will be able to select the target currency
The ad hoc currency translation offers only restricted functionality (selection of translation key and target currency) compared to the currency translation in the query definition
Do not forget to create your translation keys before starting your work in the Business Explorer Analyzer
Example:
You load the following record to your InfoCube:
Company Code:                1000
Amount in Source Currency:      500,-
Source Currency:                FRF
Target Currency:               ?
In the Update rules, you are now using a translation key which derives the target currency from the InfoObject 0COMP_CODE. During the Update Process the target currency will then be read for Company Code 1000 from the master date table of 0COMP_CODE.
With the currency translation in the Business Explorer, the source currency can currently only be determined from the data record.
Only translation keys with a fixed exchange rate type can be used in the BEx
Translation keys with a dynamic time reference (from an InfoObject) can only be used in the query definition. It is not possible to fill the InfoObject by a variable !
Translation keys getting their target currency from a currency attribute can only be selected in the query definition
When getting the dynamic reference from an InfoObject (p.eg. 0CALDAY) the currency translation will apply to each record read from the database. That means it will use the date in this record for the currency translation.
When using a variable you will restrict the output of your query to a certain amount of data. For example, you would translate all invoices of March 11 with the translation date March 11
This means, the requirement show me all invoices in my cube in group currency, conversion date: 14.07.2001 could not be solved by a variable input for 0CALDAY
I hope this would help...
with regards,
hari

Transformation Routine to convert single record into multiple

All,
I need your help with ABAP Syntax. My requirement is to take a single record and convert it to multiple records into a DSO with a condition to not create a record if a KF value is 0.
R/3 Data Record:
Employee | Date | Char1 | KF1 | Char2 | KF2 | Char3 | KF3 | Char4 | KF4
Conversion Result into DSO:
Employee | Date | Char1 | KF1
Employee | Date | Char2 | KF2
Employee | Date | Char3 | KF3
Employee | Date | Char4 | KF4 (This record will not be written if no value is in KF4)
I have read about the result table in update rules, however within BI 7.0 Transformations I am unfamiliar as to where the RESULT_TABLE function applies. Has this been replaced by the Expert Routine?
Could any ABAP expert provide sample code as to how I would perform this conversion in a Transformation Routine?
Thanks,
David

Thanks Alex for your response.
I did find a solution to this as it turns out to be fairly simple, however I executed the routine as an Expert Routine instead of a Start Routine. I was advised to do the transformation here.
The basic concept is defined below:
Loop at source_package assigning -kf2.
Append result_fields to result_package.
Endif.
-- Kf3u2026 and so on
Endloop.
Basically the APPEND statement is used to create the additional records.

Upper/Lower case conversion

Hi folks,
Apart from the Infoobject General tab where an infoobject can be selected to allow Lower case letters, are there any other areas where this can be done? We need to allow this for a standard infoobject and thinking is that we can change this at some other level such as do a conversion at the datasource level so only uppper cases flow through. This is a char field but can contain both Upper cases and Lower cases. Right now, with the standard infoobject the DTP load fails when trying to load the data with lower case characters.
Thanks for your help.

Hi,
As mentioned above you will have to use TRANSLATE command to do the conversion. Now you can either write a routine at Infoobject level or write a field routine for conversion. In case of infoobject routine again you might have to change the original infoobject so I would suggest you to go for Field level routine in transformation.
RESULT = source_fields-XYZ.
TRANSLATE RESULT TO UPPER CASE.
Regards,
Durgesh.

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

Diff between the Start routine and Update rules?

Hi Gurus
Diff between the Start routine and Update rules?
Thanks in advance
Raj

Hi,
Routines are like conditions or business rules that could be applied to filter the data while entering the BW system or could be used to apply certain conditions on the info objects itself.Update rule level you manipulate your data and write your start routine.
There are 4 types of routines
1. Start routine- Could be used at two levels (transfer rule level and the Update rule level)
This Start routine written at the transfer rule level helps filter the necessary data coming from the source system.
For Example: If you decide to extract data that contain only quantity greater than 500 , then you could specify the Start rouitne to achieve this.
The Start routine at the Update rule level provides similar functionality but at this point it helps direct specific data to
different data targets. For Example: If there 3 data targets being fed from the Infosource, you may want to apply some condition to each data target, like send year 2000 data ti Data target1, 2001 to data target 2 and so on. This can be achieved by using Start routine at the Update rule level
2. Transfer Routine: This feature is available at the transfer rule levels
While performing the transfer rules operation, there are 4 features available to the developers to create business rules on top pf the Infoobjects.
1. You could do a one to one mappping of the Infoobject
2. Provide a constant value
3. Include a formula
4. Write an ABAP routine.
These 4 options refers to the transfer routine
3. Update Routine:
The limitations of just having 4 options in the transfer routine is overcome at the update rule level. There are various other
sophisticated features avaialable apart from the 4 options mentioned above. These business rules could be specified pertaining to each data target.
4. Conversion Routine: It provides functionality to do Currency and unit conversion.
Regards.

Conversion of 3.5 routine to 7.0 routines

Similar Messages

Maybe you are looking for