Transformations (Migration)

Hi, Friends...
We have 2LIS_12_VCITM DataSource and using for Delivery Item Data DSO/Cube. Previously somebody installed and using in BW 3.5, after that we migrated DataSource to BI 7.0. using RSDS, now I created Transformations form DataSource to DSO now it is not showing any Start Routines and Update Routines for Keyfigures like BW 3.5.
Eg: we have 0QUANT_B keyfigure and it is having Upadte routine in BW 3.5, but now if I want to copy the same to migrated DS whta can I do.
Thanks
Ganga

>
Ganga wrote:
> 2. I don't want to distrub the existing one.
>
> Thanks
> ganga
If you migrate your datasource you will lose your existing update rules and transfer rules.So you can have either 3.X or 7 flow.
If you have migrated datasource with "With Export" option.
In transaction RSDS recover back your datasource to 3.X this will bring in your transfer rules and update rules.
Now you migrate your update rules next transfer rules by generating a new infosource and now migrate your datasource to 7.

Similar Messages

Update rule to transformation migration error

Error produced during update rule (BW3.5) to transformation migration. During start routine validation check it states that ' The data object 'COMM_STRUCTURE' has no component called 'BIC/ZCH_FABC1' but there is a component called 'BIC/ZCH_FAAC1'.
Even though this component is exist as part of communication structure, migration setup is producing an error.
System is BI SP 16 level. OSS message is created, if you have experienced any similar issues, pls. share and let us know.
Thanks, Vijay Rama.

Hi VJ,
The ideal best practice is to replace the Routines manually. As BI 7.0 wont hold Comm. structure, You are facing this problem.
So you replace Comm.Structure to with Source_Fields.
So while migrating the routines do it manually.
You can find a lot of info in SDN if you search using the related terms
regarding Migration.
Hope this Helps
Regards
Karthik

XML Transformation - Migration from JDK 1.4 to JDK 1.6

Hi all,
I am switching from JDK 1.4 to JDK 1.6 but my XSLT transformations are outputting different XML (although structurally sound). JDK 1.6 outputs the namespaces for each element rather than placing them at the top level node.
I've included the settings and the code below. I expect that there is a feature or a way to handle this but I have not been able to find it now for several days.
Any recommendations would be greatly appreciated.
Regards
Paul
JDK1.4
JAXP: loaded from fallback value: org.apache.xalan.processor.TransformerFactoryImpl
JAXP: loaded from fallback value: org.apache.crimson.jaxp.SAXParserFactoryImpl
<?xml version="1.0" encoding="UTF-8"?>
<ex1:IE518 xmlns:xdata="http://www.edifecs.com/xdata/100" xmlns:exe="http://test.com/schemas/ex1/elements/v1" xmlns:ext="http://test.com/schemas/ex1/extypes/v1" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:ex1="http://test.com/schemas/ex1/MSG/v1">
<ext:Common>
<exe:SyntaxID>UNOC</exe:SyntaxID>
<exe:MessageID>00000000000000</exe:MessageID>
<exe:IEMessageType>MsgType</exe:IEMessageType>
</ext:Common>
<ext:Header>
<exe:SpecificCircumstanceIndicator>B</exe:SpecificCircumstanceIndicator>
<exe:Transit>0</exe:Transit>
<exe:CommercialReferenceNumber>DHL11-7-43</exe:CommercialReferenceNumber>
</ext:Header>
</ex1:IE518>
JDK 1.6
JAXP: loaded from fallback value: com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
JAXP: loaded from fallback value: com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
<?xml version="1.0" encoding="UTF-8"?>
<ex1:IE518 xmlns:ex1="http://test.com/schemas/ex1/MSG/v1">
<ecc:Common xmlns:ext="http://test.com/schemas/ex1/extypes/v1">
<exe:SyntaxID xmlns:exe="http://test.com/schemas/ex1/elements/v1" >UNOC</ece:SyntaxID>
<exe:MessageID xmlns:exe="http://test.com/schemas/ex1/elements/v1" >00000000000000</ece:MessageID>
<exe:IEMessageType xmlns:exe="http://test.com/schemas/ex1/elements/v1" >MsgType</ece:IEMessageType>
</ecc:Common>
<ecc:Header xmlns:ext="http://test.com/schemas/ex1/extypes/v1">
<exe:SpecificCircumstanceIndicator xmlns:exe="http://test.com/schemas/ex1/elements/v1" >B</ece:SpecificCircumstanceIndicator>
<exe:CommercialReferenceNumber xmlns:exe="http://test.com/schemas/ex1/elements/v1" >DHL11-7-43</exe:CommercialReferenceNumber>
</ecc:Header>
</ex1:IE518>
try {
     byte[] transformed;
     StreamSource inputData = new StreamSource( new ByteArrayInputStream( xml_ecs.getBytes( ) ) );
     FileInputStream xsltData = new FileInputStream( xsl_file_path );
     StreamSource transformationData = new StreamSource( xsltData );
     StreamResult streamResult = new StreamResult(new ByteArrayOutputStream( ));
     //create transformer factory
     TransformerFactory tFactory = TransformerFactory.newInstance( );
     Transformer transformer = tFactory.newTransformer( transformationData );
     //perform transformation
     transformer.transform( inputData, streamResult );
     transformed = ((ByteArrayOutputStream) (streamResult.getOutputStream( )))
          .toByteArray( );
     System.out.println ("TRANSFORMED OUTPUT [" + new String(transformed) + "]");
catch (TransformerException texsc) {
     System.out.println( "TransformerException caught: "
               + texsc.getMessage() );
     throw texsc;
catch (Exception ex) {
     ex.printStackTrace();
     System.out.println(ex.getMessage());
}

Can you post relevant pieces of your input document and the xsl?

Sequence of Migration activities

Hi,
Is there a sequence that must be followed while migrating BI objects. i.e. let us say if I Migrate queries before dataflow does it make a difference.
Also kindly let me know the system requirement in terms of SP level, Java Stack or ABAP Stack requirements. I believe NetWeaver 2004s reporting tools are not compatible with Microsoft Office new version. Is that true?
Thanks a lot for help.
Regards
Pooja

Hi,
Points to be kept, (not a version migration) Migrating from one system to other
1. Review the objects in both the systems and ensure they dont clash or overlap.
2. May be they had different source systems and you need to carefully look at all the source system dependent objects and re assign the source system.
3. Performing transports will be the one of the options for the move; in that case collect the objects in logical order starting with the info objects, data targets, info sources, update rules finally queries, roles, workbooks.
4. Review the master data and also the ODS to ensure the data dont overwrite; better to have a system identifier for the master data objects.
5. For the transaction data, approach will be to go with the EDW approach
6. For the same of reconciliation purposes, suggest to keep the Regional system, if exists, within the same region system separate and for reporting purposes, use infosets and multi cubes rather than loading data to the same data targets.
For Version Migration ,Pls chk this links;
Migration of BW 3.x Dataource to BI 7.0
Migration of ECC BI Content to BW 2004s
Transformations Migration
Transformation Rules
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/f00e2696d24c5fe10000000a155369/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8d1a0a3a-0b01-0010-eb82-99c4584c6db3
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
https://websmp102.sap-ag.de/upgrade-bw
web blog ...
Rolling out the New SAP NetWeaver 2004s BI Frontend Tools
Hope this helps,
Regards
CSM Reddy

11i iSetup showing R12 request id's

Hi
We are trying to use iSEtup in 11i but what I noticed was when I run a report or load or extract, the request names are showing as follows :
Migrator UI Submitting concurrent program (iSetup R12 Transformer)
Migrator UI Submitting concurrent program (iSetup R12 Standard Reporter)
Migrator UI Submitting concurrent program (iSetup R12 Extractor)
Is this normal ? or am i doing something wrong ?
Appreciate feedback on above issue.
regards

Hello,
We are also facing the same issue? Did you get any reply or findings for this.
If yes, can you pls share the same.
Thanks,
Rohiet

Upgrading from BW 3.5 to 7

Hi:
Can anyone please let me know what are the steps that are to be followed while upgrading from BW 3.5 to 7. This is a little urgent.
Thanks for the help in advance.

Headsup..
DS = Datasource
RSDS = tcode to migrate and revert back the datasources.
Migrations..
Migration of ECC BI Content to BW 2004s
Migrate Transformations
Transformations Migration
Transformation Rules
Presentations
https://www.sdn.sap.com/irj/sdn/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e
Hope it Helps
Chetan
@CP..

Asynchronous process learnings: Why are callbacks skipped?

Just wanted to log my learnings about asynchronous processes and callbacks.
I was trying to write a .NET client to invoke an asynchronous process and was not getting anywhere. The process was being invoked successfully but the callback wasn't happening. The visual flow in the console kept saying "skipped callback x on partner y". It appears this happens when the process does not recognize that the incoming invocation is conversational - in other words it does not find the WS-Addressing headers or if present does not understand it. You would notice the same behaviour when you invoke an asynchronous process from the console. This is expected behaviour because the console does not expose a callback.
So, if you are trying to invoke an asynchronous process from another platform and see the "skipped callback" message, the first place to check is your WS-Addressing headers. Is it present and specified properly? Is the WS-Addressing namespace correct? On the BPEL 2.0.11 version I was testing, newer WS-Addressing versions would not work. I had to switch back to the older "http://schemas.xmlsoap.org/ws/2003/03/addressing" version. Another strange problem I noticed was that it was expecting some bpel attributes such as rootID, parentID in the MessageID header. Without these it would throw a server fault.
It also helps to write a sample client process in BPEL to invoke the asynchronous process and log the request and callback messages (there are technotes on OTN that show how to do this). This can be compared with the messages produced by your client to debug any problems.
Hope this information is useful for interested people. I'm yet to test the behaviour on the 10g version. Will keep this thread updated when I do that.

The migration utility only processes transforms that are created by the user. If a transform was part of the Data Quality installation, it will not be migrated because the equivalent transform will be installed as part of the Data Services installation.
Please read the manual "DS Migration Considerations > Data Quality to Data Services Migration > How transforms migrate" for more details.
Regards,
George
Edited by: George Ruan on Nov 22, 2011 9:04 PM

Error while Migrating the custom routines in Transformations

Dear All,
I am in the process of migrating BW 3.5 to BI 7.0.I migrated the Standard cubes and DSO's from BW3.5 to BI 7.0 flow successfully.
But while migrating the transformations which are having the custom routines,I am facing the below errors.
The data object "COMM_STRUCTURE" does not have a component called BIC/ZGROSSPRI".But the routine contains BIC/ZGROSSPRI.
I tried to change the BW 3.5 terminology to BI 7.0 terminology.(Like COMM_STRUCTURE replaced by SOURCE_FIELDS).But unable to solve.There are nearly 20 custome routines written in all transformations.
Can any one guide me who faced the same tyepe of problem?
Thanks & Regards,
Dinakar

HI,
We need to include Source and Target see the below article.
http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
How to Correct Routines in Transformations
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/g-i/how%20to%20correct%20routines%20in%20transformations.pdf
Thanks
Reddy

Issue with migrated transformation rule after transport

Hello all,
We have migrated couple of update rules and transfer rules to transformation rules. All the transformation rules are active in development environment.
The issue is when we transport these transformation rules to QA, one of the fields of datapacket dimension "RECORD" becomes &R1& in the global structure of start routine and therefore, transport fails in QA. Along with this we had another issue that if we add any additional fields in the cube or ODS structure, the global structure in start routine doesn't change after transport in QA. Basically, it seems like it doesn't do anything when we do transport.
We tried couple of things by transporting entire flow inclding target and source objects, we also tried transporting only transformation with overwrite mode. But none of the things worked. We also have logged the message with SAP.
SAP suggested us to open the QA environment and perform the change manually. We did it and obviously we could activate the transformation rules. But when we tried to re-transport the transformation, it is keep failing with the error "Syntax Error". My assumption has after the transport, the field has become &R1& again.
Has anybody faced such issue? We are on Ehp1 SP7.
- Danny

Thanks Murali,
Yes as I mentioned SAP suggested us to open the box and do it manually, but once we are done with the manual changes, we tried transporting the same transformation rule again, which I guess going to be the case in case of any future enhancement. Transport failed and it says "Syntax Error".
The transformations we activated manually in the target system are active, but when we try to load the data, it throws the exception error.
Any clue ?? Is it working fine in your system after you did manual changes? Did all future transport go well ?
- Danny

Error in Routine while migrating standard Transformations from 3.5 to BI7.0

Hi Experts,
We are migrating the Standard trasformations, from old version to new BI 7.0 version. when trying to create the new transformation we are getting a routine error, and unable activate the transformation.
Trasformation Name: TRCS ZCO_OM_NAE_1 -> CUBE 0PS_C08
Routine Desc.: Conversion of Actual / Commitment / Plan to Resid.Order Plan
Source Fields: 0CURRENCY & 0FISCPER
Target Fields: 0AMOUNT & 0CURRENCY
Error Message: E:Field "COMM_STRUCTURE" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement. "DATA" statement.
Routine:
PROGRAM trans_routine.
      CLASS routine DEFINITION
CLASS lcl_transform DEFINITION.
PUBLIC SECTION.
Attributs
    DATA:
      p_check_master_data_exist
            TYPE RSODSOCHECKONLY READ-ONLY,
*-    Instance for getting request runtime attributs;
    Available information: Refer to methods of
    interface 'if_rsbk_request_admintab_view'
      p_r_request
            TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
PRIVATE SECTION.
    TYPE-POOLS: rsd, rstr.
Rule specific types
$$ begin of global - insert your declaration only below this line -
... "insert your code here
$$ end of global - insert your declaration only before this line   -
ENDCLASS.                    "routine DEFINITION
$$ begin of 2nd part global - insert your code only below this line *
$$ end of rule type
    TYPES:
      BEGIN OF tys_TG_1_full,
     InfoObject: 0CHNGID Change Run ID.
        CHNGID           TYPE /BI0/OICHNGID,
     InfoObject: 0RECORDTP Record type.
        RECORDTP           TYPE /BI0/OIRECORDTP,
     InfoObject: 0REQUID Request ID.
        REQUID           TYPE /BI0/OIREQUID,
     InfoObject: 0FISCVARNT Fiscal year variant.
        FISCVARNT           TYPE /BI0/OIFISCVARNT,
     InfoObject: 0FISCYEAR Fiscal year.
        FISCYEAR           TYPE /BI0/OIFISCYEAR,
     InfoObject: 0CURRENCY Currency key.
        CURRENCY           TYPE /BI0/OICURRENCY,
     InfoObject: 0CO_AREA Controlling area.
        CO_AREA           TYPE /BI0/OICO_AREA,
     InfoObject: 0CURTYPE Currency Type.
        CURTYPE           TYPE /BI0/OICURTYPE,
     InfoObject: 0METYPE Key Figure Type.
        METYPE           TYPE /BI0/OIMETYPE,
     InfoObject: 0VALUATION Valuation View.
        VALUATION           TYPE /BI0/OIVALUATION,
     InfoObject: 0VERSION Version.
        VERSION           TYPE /BI0/OIVERSION,
     InfoObject: 0VTYPE Value Type for Reporting.
        VTYPE           TYPE /BI0/OIVTYPE,
     InfoObject: 0WBS_ELEMT Work Breakdown Structure Element (WBS Elem
*ent).
        WBS_ELEMT           TYPE /BI0/OIWBS_ELEMT,
     InfoObject: 0COORDER Order Number.
        COORDER           TYPE /BI0/OICOORDER,
     InfoObject: 0PROJECT Project Definition.
        PROJECT           TYPE /BI0/OIPROJECT,
     InfoObject: 0ACTIVITY Network Activity.
        ACTIVITY           TYPE /BI0/OIACTIVITY,
     InfoObject: 0NETWORK Network.
        NETWORK           TYPE /BI0/OINETWORK,
     InfoObject: 0PROFIT_CTR Profit Center.
        PROFIT_CTR           TYPE /BI0/OIPROFIT_CTR,
     InfoObject: 0COMP_CODE Company code.
        COMP_CODE           TYPE /BI0/OICOMP_CODE,
     InfoObject: 0BUS_AREA Business area.
        BUS_AREA           TYPE /BI0/OIBUS_AREA,
     InfoObject: 0ACTY_ELEMT Network Activity Element.
        ACTY_ELEMT           TYPE /BI0/OIACTY_ELEMT,
     InfoObject: 0STATUSSYS0 System Status.
        STATUSSYS0           TYPE /BI0/OISTATUSSYS0,
     InfoObject: 0PS_OBJ PS Object Type.
        PS_OBJ           TYPE /BI0/OIPS_OBJ,
     InfoObject: 0VTSTAT Statistics indicator for value type.
        VTSTAT           TYPE /BI0/OIVTSTAT,
     InfoObject: 0AMOUNT Amount.
        AMOUNT           TYPE /BI0/OIAMOUNT,
     Field: RECORD Data record number.
        RECORD           TYPE RSARECORD,
      END   OF tys_TG_1_full.
Additional declaration for update rule interface
DATA:
    MONITOR       type standard table of rsmonitor WITH HEADER LINE,
    MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
    RECORD_NO     LIKE SY-TABIX,
    RECORD_ALL    LIKE SY-TABIX,
    SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
global definitions from update rules
TABLES: ...
DATA:   ...
FORM routine_0001
CHANGING
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
init variables
not supported
     icube_values = g.
     CLEAR result_table. REFRESH result_table.
type-pools: PSBW1.
data: l_psbw1_type_s_int1 type psbw1_type_s_int1.
data: lt_spread_values type PSBW1_TYPE_T_ACT_SPREAD.
field-symbols: .
füllen Rückgabetabelle !
    move-corresponding to RESULT_TABLE.
    check not RESULT_TABLE-amount is initial.
    append RESULT_TABLE.
endloop.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
ENDFORM.                    "routine_0001
$$ end of 2nd part global - insert your code only before this line   *
      CLASS routine IMPLEMENTATION
CLASS lcl_transform IMPLEMENTATION.
*$*$ begin of routine - insert your code only below this line        *-*
Data:
    l_subrc          type sy-tabix,
    l_abort          type sy-tabix,
    ls_monitor       TYPE rsmonitor,
    ls_monitor_recno TYPE rsmonitors.
REFRESH:
    MONITOR.
Runtime attributs
    SOURCE_SYSTEM = p_r_request->get_logsys( ).
Migrated update rule call
Perform routine_0001
CHANGING
    l_subrc
    l_abort.
*-- Convert Messages in Transformation format
    LOOP AT MONITOR INTO ls_monitor.
      move-CORRESPONDING ls_monitor to MONITOR_REC.
      append monitor_rec to MONITOR.
    ENDLOOP.
    IF l_subrc <> 0.
      RAISE EXCEPTION TYPE cx_rsrout_skip_val.
    ENDIF.
    IF l_abort <> 0.
      RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
    ENDIF.
$$ end of routine - insert your code only before this line         -
ENDMETHOD.                    "compute_0AMOUNT
      Method invert_0AMOUNT
      This subroutine needs to be implemented only for direct access
      (for better performance) and for the Report/Report Interface
      (drill through).
      The inverse routine should transform a projection and
      a selection for the target to a projection and a selection
      for the source, respectively.
      If the implementation remains empty all fields are filled and
      all values are selected.
METHOD invert_0AMOUNT.
$$ begin of inverse routine - insert your code only below this line-
... "insert your code here
$$ end of inverse routine - insert your code only before this line -
ENDMETHOD.                    "invert_0AMOUNT
ENDCLASS.                    "routine IMPLEMENTATION
Regards
Krishanu.

Hi,
Go through the belowl link it may help you a lot
/message/7377688#7377688 [original link is broken]
Regards,
Marasa.

Error in BI at Transformation after migration from BW Rule (target :ZDTAPAK

Hello Gurus,
I have migrated datasource from BW to BI. The update rule from BW against transformation in BI has routine.
I see an error messgae in "Transformation Display"(screen). error msg is
Rule (target :ZDTAPAKID, group:01 standard Group): syntax error in routine
Rule (target :ZRECNM, group:01 standard Group): syntax error in routine
Rule (target :ZRECORDID, group:01 standard Group): syntax error in routine
Rule (target :ZREQUID, group:01 standard Group): syntax error in routine
when I double click on field/ Rule Name : ZDTAPAKID,ZRECNM,ZRECORDID & ZREQUID on all the four field / rule name and go to Rule Details and against Rule Type : Routine , go to Display Rule and land in Rule Details .
There is see routine isa defined, when I check the syntax of routine I get following error .
E:Field "G_S_MINFO-DATAPAKID" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement. "DATA" statement
Note: I get same error for all the 4 fields/rule name when I try to check the syntax ZDTAPAKID,ZRECNM,ZRECORDID & ZREQUID
can any one please guide me?
Thank you
Ashwaq

hi check note Note 1052648 - Migrating transfer rules and update rules for BW7.x
otherwise try to declare the fields in your generated coding
for example
TYPE-POOLS: RSSM.
DATA :
G_S_MINFO TYPE RSSM_S_MINFO,
ZDTAPAKID TYPE RSDATAPID,
ZRECNM TYPE rssm_s_minfo-requnr,
ZREQUID TYPE RSREQUEST.
Bye
Boujema

Error in Update Rule migration using "Create Transformation"

Hi gurus,
We are encountering errors in the migration of our 2LIS_03_BF and 2LIS_03_BX update rules into a transformation via URs Context Menu Additional functions - > Create transformation
This action creates a new transformation, but is only generating very little Routine assignements in our KF fields. That is, some KF have their old ABAP converted automatically into ABAP OO while the rest (majority) of KF fields have no rule (routine) assigned at all.
However, the most surprising thing is that after executing the "Create Transformation", the log shows everything correct and warnings (message 652 "Routine created. Verify sintax").
Have you ever faced this problem?
Is the automatic migration tool working correctly?
If not, do we need to manually create all those KF routines that have not been correctly been migrated? Even after two years since new dataflow that was released?
We are on SP 15...
Thanks and best regards,
Enric

Hi Juanjo,
In fact, if I understand you correctly, I'm facing the same situation: all FORMS based on OLD individual KFs routine are now available in the global transformation routine in ABAP OO, but what I'm missing is the individual source to target KF field mapping to routine, where the method with the perform to each coding should be done.
Shall I understand this is a common bug? Manual correction proposed?
Thanks,
Enric

Migration of Transfer Rules ( Create Transformation)

Iam loading master data using direct update through 3.5 datasource. Now i want to migrate the data-source as well as the transfer rules.
First thing i do is right click on the transfer rules Additional Functions--> Create transformation
I get the following message
" Initial error occurred during generation of the transformation "
Message no. RSTRAN667
I tried deleting the transfer rules and recreating it, i get the same problem. I think first i need to create transformation against the transfer rules then i need to migrate the datasource.
I also tried just migrating the datasource and the transfer rules are gone.
The same procedure i tried with Business Content master data datasource and that one works.
Note: we are on Suport pack 12.
Please let me know if iam missing anything.
Your suggestions are highly appreciated..
Thanks

Thanks for your message..
But the thing iam doing is Iam migrating 3.5 stuff to 7.0 iam not creating transformations on the datasource.
In order to attain that migration ,first iam migrating the transfer rules as iam using direct update for master data. While iam doing that Iam getting the error message.
Voodi I'll look at that option and see if i can accomplish my migration by first migrating DS and then transfer rules....
But did u get this message for direct update of the master data...
I tried creating a generic master datasource even for that one also iam getting the same message ...while migrating the transfer rules....

Migration of update rules to transformations

Hi Experts,
We are in process of migrating update rules to Transformations.
We have following data flow for one info cube.
*Existing*
Data source -
>transfer Rules--->info source->update rules--
>cube
New
Data source -
>transformations----
>cube
When I am trying to create transformations, I am not able to read master data properties for all info objects.
It gives error that No info object is available.
Now my question is
it is not possible to read mster data in one transformation?
If I change my new scenario to this then it workes.
Data source -
>transformations----->info source(new BI7)--
>transformations -
>cube
But then I need to convert All existing info source to new one in BI7 then only I can use read from master data functionality.
Please advice.
<removed by moderator>
Edited by: Siegfried Szameitat on Nov 25, 2008 9:05 AM

In the Transformation maintenance, open the rule details.
Here you see the source fields of the rule.
Update 'IOAssgnmnt' with the InfoObject corresponding to the field from the source system.
Example
Field PERNR
Description Personnel No.
Type NUMC
Length 8
Conversion
IOAssgnmnt 0EMPLOYEE <-- Entered manually
Then you should be able to use the 'Read master data' functionality.
Regards,
Lars

Clarifications to migrate to transformations

Dear Team,
I want some clarifications.
I am doing upgradation project. (BW 3.1 to BI7).
Customer is asking me to migrate all existing transferrules/updaterules to transformations. what needs to do ?. Is it possible to migrate all existing transfer rules/update rules at a time?. Is there any programs to achieve this?.
Best Regards,
SG

Hi SG,
some of the useful links from SDN related to migrations
Re: Datasource Identification
Strategy toward new and 3.x datasource / infosource
Replicate NEW/3.x datasource - Methodology
Replicate NEW/3.x datasource - Change back to 3.x datasource Methodology
Assessing Migration Scenario's
Re: Few questions on BC activation..
Transformation Rules
hope they help

Transformations (Migration)

Similar Messages

Maybe you are looking for