Transaction Master Data

[Former Member]

Does anyone have a view of why the following may not work?

Problem: We want additional characteristics of the Sales Order presnet in our Sales Order Cube without having to drop and reload the data.

Proposal: Store the sales order as master data and hold all the characteristics of the Sales Order as attributes. Make all the attributes line item and navigational.

Proposal explored further: Redesign the cube so that it only contains the Sales Order Number, Sales Order Item and the key figures of the Sales Order. Have all other characterics as Nav Atts from the Sales Order Item master data.

Comments would be greatly appreciated.

[Former Member]

Our feeling was this could be addressed by setting up the sales order as flexible master data fed from 2LIS_11_VAITM.

[Former Member]

Hi Mark and welcome to the SDN!

You are right. It is possible to design the document no. with attributes (I already did that a few years ago as we haven't had the lo cockpit). But in your case you need to remodel the item no. The first step is to compound it with the document no and then add the attributes you need to the item no. Activate them as nav attrs. and load data to it. But on the other hand you need to delete the content of your cube because otherwise it is not possible to remodel the dimensions.

This is a really hard change to your actual model and you might think about other scenarios. One could be to have a ods before the cube to store the item information and delete the document and item from the cube....

regards

Siggi

[Former Member]

Hi,

That depends on your design scenario. But, personally, i don't think sales order number can be maintained master data since orders numbers determine sales transactions.

You can add a new characteristic to an existing cube with data. But, you might still want to reload the data if you want historical values to be loaded for the new characteristic.

Regards