IP Naming Convention Recommendation

[charles_soper]

Hello all!

Do any of you have a recommendation on how to name agg levels, filters, functions, sequences, and queries in IP?

Thanks

T

[Former Member]

Practice is to prefix with application area, followed by cube name ( if the naming length admits such long names) for the aggregation levels.

Queries should be like this:

Provider name _Q001 and description can be something meaningful.

Planning functions and sequences should be prefixed with the aggregation level name.

To sum up all planning objects should be named with aggregation level prefix and queries with info provider prefix.

Ravi Thothadri

[Former Member]

Hi Tim,

I have put together a naming standard for my IP project and it is approximately:

where ff is the functional area

nn is a number for cubes, aggregation level, etc.

mm is a sequential number for filter, functions, sequences, etc.

xxx os a sequential number for queries, layouts, WAD templates.

ZIPff_Cnn - basic cube

ZIPff_Pnn - Planning / Realtime Infoprovider.

ZIPff_Onn - ODS

ZIPff_Mnn - Multi-Provider

ZIPff_Ann - Aggregation Level

ZIPff_Ann_FIL_mm - Filter

ZIPff_Ann_PF_mm - Functions

ZIPff_Ann_PS_mm - Sequence

ZIPff_Ann_Qxxx or ZIPff_Cnn_Qxxx - queries / reports

ZIPff_Ann_Lxxx - input enabled query Planning query / layout

ZIPff_Ann_Wxxx or ZIPff_Cnn_Wxxx - WAD template, etc.

If you want more specifics, E-mail me.

Cheers,

Mary