(part 2 of 2): 3.x Dataflow migration test. Any hints on this problem?

Question

Hi Experts
You may see this link for part 1 of this question for the full details if the continuation question below is not clear :
(part 1 of 2): 3.x Dataflow migration test. Any hints on this problem?
The eventual goal here is to migrate the 3.sx dataflow so as to use the transformations, etc
4:
Instruction: After successful activation of transfer rule Right Click on Data Source and say Migrate.
i.e. I am still under InfoSource tree, I expanded transfer rule to see Data Source under itu2026
R-clk & select Migrate, WITH EXPORT
--finally got u201CDataSource 0PLANT_ATTR(E75CLNT800) was migratedu201D
5:
Instruction: To convert Update Rules to Transformation
The instructions states u201Cu2026 Now Go to Info Provider and search for 3.x old Data Source . Right click on Update rules and say Create Transformation. ..u201D
My issue:  Under InfoProvider tree, search for original datasource: 0Plant_Attr could not be found.
I then performed a FIND and checked the box for Datasources 3.x  It gave no datasource from the source system(E75CLNT800) I am dealing with.
BUT if I ignore the instruction and do a FIND for Datasources (without the 3.x), I find it for the right 0plant_Attr for my source system
The problem is that it still did not show the Update rule under itu2026
--I then went to Datasource tree, Logistics, u2026followed path to 0palnt_Attr datasource and identified the Update Rule
but it does not have an option for u201CAdditional Functionsu201D, to u201CCreate transformationu201D
I am therefore stuck on page 9 on the above link providing me the instructions. Any hints?
6.
I searched under the InfoProvider tree, found 0Plant but there were multiple Transfer rules BUT none of them showed for E75CLNT800 that I was interested.
I saw Transfer Rules and Update rules for other source systems on the IDES e.g. E69CLNT190 with the datasource etc. What happened to mine?

Answer 1

Hi,
Great, I followed the comments on the board and restored the datasource to 3.x datasource. Then contrary to the instructions in the link I was following, I migrated Transfer rule, Update rules before the datasource (0PLANT_ATTR) migration.
I am happy everything is fine but I encountered some issues, which I would like your comments on:
1.
I have access to the ECC E75CLNT800  and I saw that some developers were also loading to the same 0Plant attribute with datasource e.g. 0WS_TAROBJ_ATTR from other systems e.g. E69CLNT190
If I were to test this second option as a BI Consultant, do I need the involvement of Basis to establish a connection from BI to E69CLNT190 or, am I as a BI consultant expected to do that myself?
2.
During the migration of Transfer Rule it failed to activate with error:
u201CRule (target: 0GN_R3_SSY, group: 01 Standard Group): Syntax error in routineu201D
Later, I u201CDelete Ruleu201D for 0GN_R3_SSY (Source Systems for R3 Entity), before I was able to activate.
What is this about and what is the implication for deleting this rule? There was nothing I could map it to and was not sure why the rule was "Routine" so I changed to "No Transformation"
3.
How come that under the InfoProvider treeu2026 in the data flow for 0Plant_Attr, I donu2019t have the DTP I created under the Datasource treeu2026. Shouldnu2019t it appear at both places?
--I executed the DTP created under the Datasource tree and data went from PSA to InfoObject (0Plant) alright.
Thanks..
Edited by: AmandaBaah on Aug 11, 2011 5:43 PM