Requirement to add 0MAT_UNIT and its attributes in the cube

[antony_xavier3]

Hi Guys,

Info obj: 0MAT_UNIT and its attributes(i.e Numerator, Denominator etc) is not available in the cube and all its lower level DSOs, DS. 0mat_unit has been compounded by 0MATERIAL, 0MATERIAL is available in the cube.

Now I want to add 0MAT_UNIT and its attributes in the cube in the cube

For this I gues solution would be to add 0MAT_UNIT as attribute to Material, but I am not sure how attributes of 0MAT_UNIT would get poupulated in the cube.

Can anyone pls suggest me step by step approach required to be carried out in order to add 0MAT_UNIT and its attributes in the cube

[former_member182516]

Master data for 0MAT_UNIT will be loaded using the data source 0MAT_UNIT_ATTR.

You Mean you want the 0MAT_UNIT attribute data in reporting level, you can simply add the 0MAT_UNIT into the IO and map the respective fields from DSO.

Attributes get data from master data data source not from transaction.

If 0MAT_UNIT is attribute of 0MATERIAL - make it to navigational attribute and enable the same in IC.

Regards

KP

[antony_xavier3]

As per your suggestion if I just add  0MAT_UNIT as navigational attribute of 0MATERIAL...then will it ensure that attributes of 0MAT_UNIT(numerator, denominator) would become available in the report

[antony_xavier3]

I mean here I dont want to map attributes of 0MAT_UNIT to respective fields of infocube...as I dont have any info objects created for mapping attributes of 0MAT_UNIT

[anshu_lilhori]

HI,

I am not sure about your exact requirement but i understand that you need to report the data in alternate unit of measurement as you are trying to pull the numerator and denominator values.

You can try this way:

Add these numerator and denominator to 0material infoobject as navigational attributes.

Load the data in those two attributes by the datasource 0MAT_UNIT_ATTR.

Check these navigational attributes in which ever provider required and then use them in reports accordingly.

Hope this gives an idea.

Regards,

AL

[former_member182516]

You can get the attributes of 0MAT_UNIT only if you add the field in the IC level for reporting.

If you add it to 0MATERIAL as Navigational attribute you can't get the attributes of 0MATERIAL.

Or try as  Anshu suggested

[Former Member]

Hi Antony,

*** As per your suggestion if I just add  0MAT_UNIT as navigational attribute of 0MATERIAL...then will it ensure that attributes of 0MAT_UNIT(numerator, denominator) would become available in the report ***

Case1: If you are reporting on top of Infoset, it is possible to report on Transitive Attributes(Attributes of Attribute).

Case1: If you are reporting on top of Infocube, add 0MAT_UNIT infoobject in Infocube and populate it using read master data from 0MATERIAL. Dont forget to check required navigational attributes in Infocube:)

Thanks
Balakrishna

[Former Member]

Hi Antony,

if you are using 0material in your infocube automatically its relvant attributes will come , just you need to enable in  at infocube level.

For this I gues solution would be to add 0MAT_UNIT as attribute to Material, but I am not sure how attributes of 0MAT_UNIT would get poupulated in the cube :

Attributes get populated by enabling in infocube.

Here above company code is enabled like that 0mat_unit will be there just enable.

Regards,

Giri

[Former Member]

if 0mat_unit is not aviable in 0material then follow Prashanth Konduru  comments.

Regards,
Giri

[former_member182470]

Attributes will be attached to the master data infoobject. You will not load attributes literaly. You can use the nav Attrs and display attrs while running queries. You can add 0MAT_UNIT as a nav attr to material. Finally you just ahve to tick navv Attr tick box under Nav attr section in the cube.

[antony_xavier3]

if I just add 0MAT_UNIT as navigation attribute to 0MATERIAL...then attributes of 0MAT_UNIT would also be available in report...right.

[RamanKorrapati]

If you add 0MAT_UNIT as navigationa attribute to 0MATERIAL, then 0MAT_UNIT only available at bex reprot level, not attributes of 0mat_unit.

[antony_xavier3]

ok..Thn in that case I need to create info objects and assign it to infocube, so that these created info objects will have "Read master data " of 0MAT_UNIT mapping in the transformation

[RamanKorrapati]

Hi,

Try this way:

if you need 0MAT_UNIT attribute at bex level, you need to make 0MAT_UNIT as navigational and that attribute also make it as navigational which you need. then you can access those at bex level.

0MATERIAL---navigational attribute 0MAT_UNIT----> navigational attributes Numerator, Denominator.

Test at dev.

Now you can access numerator/denominator at bex level. its transitive attributes.

Thanks