Attribute values on report

[erdem_sephanelioglu]

Hi gurus,

Assume Customer characteristics has two attributes: X, Y

I fill the cube and check the master data quality at the query. When I execute the report, I see the attribute values for some customer are not present(neither text nor key). What is interesting to me are some customers' while one particular attribute value of main info object Y is present other attribute's value is '#'.

Does somebody have a point on the case why I can not see some master datas' attributes values at the report level though the attirbute change run is working and the master data records are in active version. And rule type is direct assignment by the way.

Thank you for the ideas.

PS. Please find the front and back end pictures.

[Former Member]

Dear Eddy,

While populating the cube, as you say, the rule type is direct assignment, I assume the rule type for attributes of this master data in the cube should be 'Read Master Data'. Hence, you'll see correct attribute data in the report.

Hope this helps you!

-Pradnya Rane.

[erdem_sephanelioglu]

Hi Pradnya,

I am adding 0debitor as the characterisc object for which attributes to be defined at rule assignment screen. However it doesn't work.

Can you see the attached picture?

Thank you.

Eddy.

[Former Member]

Hi Eddy,

DEBITOR should be a direct assignment only. Did you do 'Attribute Change Run' after loading 0Customer?

Please try this.

Hope this helps you!

-Pradnya Rane.

[erdem_sephanelioglu]

Hi,

I did attribute change. No working.

[john_lang]

Hi Eddy,

Based upon the above attached picture:

(1) Try putting the cursor in the editable field called "IO Assignment" and then press [F1] key to get any available standard help in understanding this field better.

(2) Will putting 0DEBITOR or 0CUSTOMER in the 'IO Assignment' field make the error message go away?

Kind regards,

John.

[john_lang]

Hi Eddy,

Can you confirm that the 0DEBITOR InfoObject is a Reference Characteristic of 0CUSTOMER in your system, please?

Can you also double check the mapping assigned in the MultiProvider to confirm that the navigational attributes are correctly assigned as “straight through”. Also known as a 1:1 mapping where the 0DEBITOR__KKATR1 navigational attribute in the cube is mapped to 0DEBITOR__KKART1 in the MultiProvider.

If these navigational attributes were only just recently added … you could also use transaction RSRT to re-generate the run-time program which is the query. Use the SAP GUI and re-generate and run the query here to confirm the OLAP engine on the server side is behaving as expected.

Also some web session caches have been known to cause a delay in when the new data is reported. Obviously you have tried the usual technique of logging off web reporting session, clear browser cache and cookies, close the web browser, open web browser and log back in to force a new cache session in the web servers state-ful navigation tracking.

Hope this helps.

Kind regards,

John.

[erdem_sephanelioglu]

Hi John,

Thanks for return. 0debitor is as you said reference characteristic of 0customer. Top level Infoprovider is InfoCube by the way. As you can see the Info object transformation, the rule is direct assignment with fields and attributes.

Do you have any further idea on the issue?

Thanks.

Eddy.