BPC NW 7.5: use standard dimensions

[Former Member]

hi gurus:

i m reading a business blueprint for legal consolidation which was designed for a consultant who is unavailable for contact, so he suggested in the document to use Z dimensiones like: Z_COMPCODE, Z_DATASRC, Z_TIME, Z_MONEDA, but i d like to hear from ur experience, is this recommendable? Why not to use standar dimensions like: Entity, C_DataSrc, Time, RptCurrency? may be there are some advantages.

regards

jav

[former_member182766 · Accepted solution]

Hi Joseph! It's easier to distinguish your dimensions from default ones when you use prefix.

I, personally, usually leave time and currency dimensions intact and copy/create others with prefix like XX_ENTITY (where XX is short for customer name).

But it's not mandatory. You can use default dimensions. SAP BW naming rules don't apply here.

[Former Member · Accepted solution]

i m interested in knowing the advantages on using Z dimensions, are there some?

regards

jav

[former_member182766 · Accepted solution]

Nope. No advantages what so ever. Except fo the ease of distinuishing, as I mentioned before.

[raghu_ram · Accepted solution]

Hi Joseph,

In SAP we have system defined Objects starting with a prefix 0-9 and Customer defined objects with prefix A - Z. Generally In SAP BW, ABAP, etc. we will create Objects with Prefix XYZ like what your Consultant said so that they are easily distinguishable from the other Objects. This prefix can be used for creating Dimensions in BPC as well.

Please check the below SAP help file on Namespaces for your understanding.

http://help.sap.com/saphelp_nw70/helpdata/en/ba/83343ea7ff6a38e10000000a114084/frameset.htm

Hope it helps.

Regards,

Raghu

[esjewett · Accepted solution]

Hi Joseph and Raghu,

But this point from Raghu is not relevant for creating any objects in BPC administration. BPC is completely different from the traditional SAP systems.

My take: prefixes can make sense if you are using different dimensions in different applications (C_ACCOUNT for consolidations vs. P_ACCOUNT for planning). But other than that, just use names that make sense to the business users who will be using the applications. Are your reporting users really going to understand why all the dimension names start with "Z_"? I would guess you'd be better off without the prefixes in most cases.

Cheers,

Ethan

[raghu_ram · Accepted solution]

Hi Ethan,

I agree what you have said. In most of the scenarios we see that dimensions will have prefix P or C for Planning & Consolidation. I was trying to distinguish between the Customer defined objects and System defined objects.

Regards,

Raghu

[Former Member · Accepted solution]

txs all for ur responses.