Lookup through transformation is taking too much time to load and the job is not progressing at all.

[former_member206066]

Hello Experts,

I have created a transformation from a data source to a ADSO.

in transformation I wrote start routine and field routine to look up Material.

and for some other fields like product hierarchy , I have done lookup through transformation(target :product Hierarchy and lookup Object :material)

note: product hierarchy is navigation attribute of material.

But when I am executing DTP, it is taking too much time and the job is not progressing at all.

without this transformation lookup, this DTP take 2-3 min to load and looking up material through start and field routine properly when I am adding transformation lookup for product Hierarchy, I am getting this issue

Please help.

My assumption: we are getting material through start and field routine and material is lookup object here to get product hierarchy at the same time, so I am getting this issue.

But I am not sure, can you please help why my DTP is stuck

Thanks,

Ipsita

[Abhishek_Hazra]

Hi Ipsita,

If you’re deriving material in the field routine, for the look up function on 0material info object what source field do you pass? It needs a material number to be passed on for finding relevant attributes.

Also, if I connect all your previous questions regarding this topic, I think somehow it’s going towards a bit complicated direction & could have been addressed in easier approach. Can you explain the solution design in a little elaborating way?
Is it correctly understood that you have a calculation view -> data source -> aDSO?

& you’re trying to make these derivations between datasource & aDSO?

Regards,

Abhi

[former_member206066]

Hello Abhishek,

I have created private calculation view--> dictionary view on top of it(this dictionary view have legmaterial and material no.)

Now I have created a transformation from a data source to Planning ADSO.

The data source which have part no(same leg material) and some other key figures.

The Target ADSO ,which have material, product Hierarchy, Profit center , controlling area and some key figure.

Now I have looked up material no. using the dictionary view(comparing leg material=part no) writing code in start and field routine.

Till now it is working.

Now I need to lookup product Hierarchy which is navigation attribute of Material.

And also need to lookup profit center which is transitive attribute of Material but navigation attribute of Product Hierarchy.

(Material-->Product Hierarchy-->Profit center.)

first I thought to use lookup option through transformation but if I do that the load is stuck and the job is not progressing at all.

Material no. not available in my data source but part no is present (using this part no I am looking up material no. from dictionary view), so in source I was passing Part no.

So I thought so lookup product hierarchy from P table of material and

profit center from P table of Product Hierarchy in End Routine

Can I do it be done in this way??

can I lookup from P table ??

[Abhishek_Hazra]

Hello again,

So, you have the dictionary view for look up already where you are looking up the material number. Don’t you think it’d be a lot easier if you simply make a join with P tables of material & product hierarchy in the calculation view & regenerate the dictionary view? Then you’ll have all the necessary fields in the dictionary view to look up from in the same start/field routine.
The look up feature needs the key fields(in your case material number) in transformation to be passed on to the looked up object. You don’t have it in your source structure & it is derived in the field routine. So, ideally you can’t use it for 0material look up, & probably you’ve not assigned any source fields in the look up rule since you don’t have material in source structure, therefore it does not work.
To me, the best possible way to do this task would be to write a simple AMDP routine in your transformation.
But if you are to keep your existing solution, I would say consider enhancing your calculation view & dictionary view with all the necessary fields, it makes the whole thing a lot easier.

Best Regards,

Abhi

[former_member206066]

Hello Abhishek,

I have thought this same solution before by joining 0Material and Material Reference table in a calculation view and then creating dictionary view top of it.

But customer did not agree and wanted me to create a private calculation view only using Material Reference table , so that that dictionary view can be reusable.

Material is already looked up by using that dictionary view.

Now My doubt is: In End routine, Can I lookup Product Hierarchy from P table of Material(comparing material).

and then

Lookup Profit Center(Transitive attribute of material but navigation attribute of Product Hierarchy) from P table of Product Hierarchy

by writing lookup logic one after another in end routine ?

What's your thought?

Thanks,

Ipsita

[Abhishek_Hazra]

Yes you can do that - look up the product hierarchy & profit center information reading the P tables of material & product hierarchy respectively in end routine, but if you have this case where you are using all start, field & end routines, why not an expert routine replacing all of them then? Then you have the entire logic in one place instead of scattering the same.

Also, have you considered using AMDP logic instead of ABAP?

Regards,

Abhi

[former_member206066]

Thanks for your valuable comments but accepting answer option is not available for comment