Navigational attribute in BW

[Former Member]

Hi,

I need to generate Equipment costing report with periodic breakdown based on 0PM_OM_OPA_1 Cube.

This cube doesn't have Equipment as one of its characteristics. But Equipment is available as Navigational attribute of PM Order characteristics.

Is that a good practice to use Equipment (navigational attribute) for Equipment costing report with periodic breakdown

Advice me on this

Thanks in advance

arun

[Former Member · Accepted solution]

Hi,

Cost and allocation analysis for internal order 0CO_OM_OPA_1 and Maintenance order 0PM_OM_OPA_1 uses the common Extract Structure "ICORDCST" and common Extractor Function module "BWOM_RS_GET_ORDCST".

This extract structure ICORDCST doesn't have Equipment and posting date field. So the business content infocube doesn't have 0EQUIPMENT and 0POSTING_DATE.

I am looking towards to perform Periodic breakdown cost based on equipemnt.

I am trying to use 0PM_ORDER_0EQUIPMENT (Navigational attribute for 0PM_ORDER) directly as one characteristics in Row and cost in columns in query design.

Is this a good design? or can we modify the extract structure ICORDCST to include 0EQUIPMENT field?

Thank you

arun

[Former Member · Accepted solution]

Using the 0EQUIPMENT navigational attribute is a good idea as long as

a) every PM order is assigned to exactly one equipment

and

b) the equipment doesn't change over time.

If b) happens at your site you should put 0EQUIPMENT into the InfoProvider and populate it from the 0PMORDER attribute.

If a) really happens you might need some ABAP in the update rules to populate the field. If you need the posting date you need to enhance the data source. But since the data source transfers cumulated records they often have more than one posting date. Why do you need this requirement?

-Best regards

Dirk

[Former Member]

Hi Arun,

before using navigation attribute you should evaluate how you'll use this attribute, because it has impact on query performance.

Lena