Physical Layer Naming Convention

Hi,
I am trying to setup my physical layer and see reference to naming them properly. When I look at the sample sales examples, I see they are using A01, A02, etc.
But, I others are indicating I should name them:
fact_sales
dim_customers
Anyone have some good direction on how to setup a proper naming convention for the physical layer.
And should I just using this naming convention for the alias tables?
thanks,
Kathy

Use Like
SALES_F and CUSTOMERS_D
_F for Fact
_D for Dimensions
All in UPPER case
For Alias use CLOSING DATE (W_DAY_D)
Shud be useful

Similar Messages

Obiee - physical layer

Hi,
I'm new to obiee tool.
my dimension table have composite primary keys (3 keys - suppose employee id, employee ssn, phone no)
and my fact table have (2 keys - employee id, employee ssn )
then, how do we do physical join in physical layer ?
Do, we need to create 2 alias tables and join to my fact table ?
or, else can i use expression builder in the physical diagram..physical join ?

Hi,
This is why you go for alias tables ..
To set up multiple tables, each with different keys, names, or joins, when a single data source table needs to serve in different semantic roles. Setting up alias tables in this case is a way to avoid triangular or circular joins.
For example, an order date and a shipping date in a fact table may both point to the same column in the time dimension data source table, but you should alias the dimension table so that each role is presented as a separately labeled alias table with a single join. These separate roles carry over into the business model, so that "Order Date" and "Ship Date" are part of two different logical dimensions. If a single logical query contains both columns, the physical query uses aliases in the SQL statement so that it can include both of them.
You can also use aliases to enable a data source table to play the role of both a fact table, and a dimension table that joins to another fact table (often called a "fan trap").
To include best practice naming conventions for physical table names. For example, you can prefix the alias table name with the table type (such as fact, dimension, or bridge), and leave the original physical table names as-is. Some organizations alias all physical tables to enforce best practice naming conventions. In this case, all mappings and joins are based on the alias tables rather than the original tables.
Now for creating joins you can make use of expression builder to have Primary Key and Foreign Key Relationships OR you can also have Complex Joins here over nonforeign key and primary key columns. When you create a complex join in the Physical layer, you specify the expression for the join. Like
Employee.employeeID=Fact.EmployeeId
and Dim table.deptname <> 'ABC'
You, can also have case statements here...
Hope this clears your funda regarding Alias Tables & Joins. Expression Builder is just the utility for developers to select the table, columns, expressions, variables and may other functions available.

Looking for best practice on naming conventions

Does anyone out there have a best practice on naming conventions that they could share.
I'm starting to find the need to create objects and associated variables and actions.
I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)
Thanks
Alan

Hi Alan,
Welcome to Adobe Community.
There are couple of things that you can keep in mind while naming objects.
When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must
use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five
bitmap images that constitute the new style should be named as follows:
Brightblue1.bmp, an image with no callouts
Brightblue2.bmp, an image with a callout to the right or upper-right
Brightblue3.bmp, an image with a callout to the left or upper-left
Brightblue4.bmp, an image with a callout to the lower right
Brightblue5.bmp, an image with a callout to the lower left
Flash button-naming conventions
Each SWF button contains three layers: a button, an icon, and an action layer.
The SWF filename consists of the following elements:
Acronym for playback control (“pbc”)
Playback element identifier (“Btn” for button, “Bar” for bar, and so on)
Name of the button (“play”).
Hope this helps!
Thanks!

Naming convention best practice for PDB pluggable

In OEM, the auto discovery for a PDB produces a name using the cluster as the prefix and the database name suffix, such as:
odexad_d_alpcolddb_alpcolddb-scan_PDBODEXAD
If that PDB is moved to another cluster, I imagine that name will not change but the naming convention has been violated.
Am I wrong and does anyone have a suggestions for a best practice naming the PDB's

If the PDB moves to another cluster, OEM would auto-discover it in the new cluster. So it would "assign" it a new name.
As a separate question, would you be renaming the PDB (the physical name) when you move it to another cluster ?
Hemant K Chitale

NAMING CONVENTION OF X$ TABLES IN 10GR2

Hi All
I want to know if oracle follows any
naming convention to x$ tables ...and also for the column
names .if yes what is it.
Thanks in Advance.....

Well, I would second to Hemant that for these structures ( they are not tables exactly) , whatever convention Oracle has, its with it only. That said, the tables basically are the representations of the layers that work with the Kernel of Oracle. So the table names follow or represnt the layer on which they are based on. For example, X$KCBWDS is Kernel Cache(cache layer) Buffer Working Set Descriptor. So would be the column names within them , representing what the layer is doing .
In anyways, its not really important to know the convetion, yes to some extent meanings of these strucutres may help butthat too is limited to some extreme cases only.
HTH
Aman....

When using Creative Cloud Library assets created in Illustrator why are the naming conventions I use not being pulled over into the Photoshop layers?

I create the Creative Cloud Library asset in illustrator and give it a name such as "camera-icon". It shows up in my Creative Cloud Library pane in Photoshop as "camera-icon". When I use that asset in Photoshop the layer is randomly named "a56bd81d-d81f-4815-82b3-5795d410b527". Why is this happening? Shouldn't that layer resolve the name back to "camera-icon" so that when I extract files for use in my application the naming convention is correct. Right now I have to manually rename that layer again. Is this a bug or have I just not done something correctly?

I think you have pasted the entire crash log. In case of such issues in future, please paste the error screenshot.
Seems to be a permission issue. Lets follow the below suggestions:
Solution 1: Rename the following folders on your machine:
'/Library/ColorSync/Profiles/Profiles'
'/Library/ColorSync/Profiles/Recommended'
Solution 2: Rename the following files:
'/Library/Application Support/Adobe/caps/Media_db.db'
'/Library/Application Support/Adobe/caps/pdb.db'
Make sure you dont touch caps.db under the same folder. Now run the installer again. Let me know if you need more help.
Solution 3:
Please Run following commands on terminal on the machine (this will remove the corrupt fonts and should allow you to run the installer successfully) -
sudo mv "/Library/Fonts/ACaslonPro-Bold.otf" /tmp/
sudo mv "/Library/Application Support/Adobe/SavedFonts/current/AdobeArabic-Bold.otf" /tmp/
sudo mv "/Library/Application Support/Adobe/HelpCfg/de_DE/goURL_lr_photoshop_de.csv" /tmp/
Please feel free to respond to this thread if you have any questions about the steps listed within the document. If you could also respond with the specific error message you receive, It would be appreciated.

The naming convention of the disk device name (/dev/dsk/cXdY)

Hi All,
Please let me know the naming convention of the disk device name (/dev/dsk/cXdY) recognized on OS of a guest domain.
I found from the document of Oracle that the value specified as the id option of ldm add-vdisk command went into Y of cXdY.
However, there is no telling by what kind of rule X portion of cXdY is decided.

Hello
I have found this in the man ldm but I don't know how to related the cN, I mean I don't know where the N comes from. Still checking and trying to get more info.
vdisk
Virtual disks are generic block devices backed by different types of physical devices, volumes, or files. A virtual disk is not synonymous with a SCSI disk and, therefore, excludes the target ID (tN) in the disk name. Virtual disks in a logical domain have the following format: cNdNsN, where cN is the virtual controller, dN is the virtual disk number, and sN is the slice.
Regards
Eze

Unable to view data in Physical layer of RPD

I have OBIEE installed on my local machine using Oracle 10g as the database installed on a remote machine. I am able to create the DSN and test the connection pool on my local machine.
The Call interface is OCI 10g in the connection pool. I am able to import tables into the database in the Physical layer of the repository but when I try to VIEW Data in the physical layer, it throws me an error stating,
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor at OCI call OCILogon.
nQsError: 17014 Could not connect to Oracle Database.
I have oracle 10g client installed on my local machine. I am able to view the tables and the data from SQL PLus. In OBIEE i am able to import tables but cannot view data.
Any suggestions on what could be causing this?

Sounds like one of my common issues. After you do the import, go back and check the connection pool. What I typically run into is that it has switched to the OCI connection rather than the ODBC connection used for the import, but it is still using the name of the ODBC DSN that was used for the import. Change it to the TNS name or the host:port/service and try again.
Rgds/Mark M

How to define join in physical layer between cube and relational table

Hi
I have a aggregated data in essbase cube. I want to supplement the information in the cube with data from relational source.
I read article http://community.altiusconsulting.com/blogs/altiustechblog/archive/2008/10/24/are-essbase-and-oracle-bi-enterprise-edition-obiee-a-match-made-in-heaven.aspx which describes how to do it.
From this article I gather that I have to define a complex join between the cube imported from essbase to my relational table in physical layer.
But when I use Join Manager I am only able to define jooin between tables from relation source but not with the imported cube.
In My case I am trying to join risk dimension in the cube based on risk_type_code (Gen3 member) with risk_type_code in relation table dt_risk_type.
How can I create this join?
Regards
Dhwaj

Hi
This has worked the BI server has joined the member from the oracle database to cube. So Now for risk type id defined in the cube I can view the risk type code and risk type name from the relational db.
But now if I want to find aggregated risk amount against a risk type id it brings back nothing. If I remove the join in the logical model then I get correct values. Is there a way by which I can combine phsical cube with relational model and still get the aggregated values in the cube?
I have changed the column risk amount to be sum in place of aggr_external both in logical and phsical model.
Regards,
Dhwaj

Storage Location Naming Convention without WM!

Dear all
We are facing serious problem in our Storage Location for Raw Material.
We have 4 types of Raw Material Seating (S), Panel (P), Metal (M), Wood (W). And they are all stored under Storage Location: RWSL.
Requirement:
Although we have visual guideline as to which industrial rack will store the type of Material, it is insufficient. We need a more refined storage location down to which BIN of the rack we will put the Raw Material.
Due to limited time and resource, we cannot have WM implemented right now. Thus, we have come out with 2 alternative to overcome this problem:
Alternative 01:
We will use the Fixed Bin field in Storage Data 02 by putting the Bin number assigned to each Rack.
E.g. For Seating material code:SEAT01, we will maintain the Fixed Bin as R12A01/A02, it means this Seating material SEAT01 will be stored at Rack 12, fixed bin A01 or A02.
Question to Alternative 01: Will it cause problem in GR, GR, Transfer Posting and Stock Count?
Alternative 02:
Instead of going into details to put Fixed Bin field in Storage Data 2, we will abandan the existing Storage Location RMSL by introducing new format for Storage Location
Here is the example of Alternative 02:
For raw materials, we will use 4 digits location numbers, consistent with other Storage locations, the 4 digits storage location will start with u201CR _ _ _u201D to represent each location
And,
R _ _ _ is:
R = Raw materials
2nd digit = Division (S= Seating, P =Panel, W=Wood, M=Metal and W=Wood)
3rd digit = Rack Number (A, B, C, Du2026 and etc.)
4th digit = Rack Zone - each rack will broken down into zone, each rack can possibility have 2 to 3 zone. 1 Zone can be 1 colume of the Rack
An example of a possible location and its meaning will be
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1
RPB3 = Raw materials warehouse, Panel Division, Rack B, Zone 3
The challenge of this is that instead of having 1 Raw Material Storage Location like RMSL, we will have a lot more storage locations each for division of Raw material due to the Rack Number we have as well as the Rack Zone.
Question to Alternative 02:
If we use this alternative, will it impact our future implementation of WM? From design wise, is it feasible?
Please advise what is the best approach and the feasible design on it.
Many thanks in advance.
Edited by: Daimos on May 13, 2009 10:15 AM

Hi, here is the Pro and Co of both approaches:
Method 01: Use existing SLOC and add the Storage Bin info
e.g. SLOC: STM1
         Storage Bin: RSC3, where RS = Rack Seating, C3 = column 3
Pro 01:
It will cause less effort as we only need to use LSMW for material master to add in the Storage Bin data for all material of SCM.
Pro 02:
I have tested out that in TCode MIGO, apart from SLOC, the pertaining Storage Bin data also appear. Based on my discuss with Xian Chen, sometimes they use MB1C(GR), MB1A(GI) rather than MIGO due to speed issue, I will need to check the field status if can have Storage Bin field APPEAR, if can, it will solve the problem
Con 01:
The Storage Bin information will only appear in MMBE (Stock Overview) but will not appear in the standard SAP Inventory Report (e.g. MB52 Warehouse Stock). To view it from SAP Inventory Report, we may need to customize the standard report to show the new field Storage Bin. It needs Abap effort.
Con 02:
We must have a very good naming convention for Storage Bin. And again, in the above example, if a material is put in SLOC STM1 at Storage Bin RA A1 or C4, it will set a very rigid rule in the future if we need to change it, as I fear that one the Storage Bin has been used up. It will not allow us to change (need to do testing to find out)
Con 03:
Do we have the time to define all the Storage Bin for each SLOC? Operation wise, the store personnel needs to design it
Method 02: Use the new SLOC
Pro 01:
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1. More organized. Easy to tell the material is at which Rack and which Zone of the Rack.
Assumption:
01. we must not have too many rack for one Seating division and also not too many Zone for each
      Division, else it will cause confusion
02. 1 material should stick to 1 Rack 1 zone as much as possible, else later the PP consultant will
     have hard to to perform GI due to too many SLOC assigned to a material.
Pro 02:
In report wise, we are able to show the SLOC in inventory report. No need to enhance the existing inventory report as we do not use Storage Bin.
Con 01:
If there are too many SLOC creation due to it. It may cause problem for PP perform GI as too many selection available for a material. This can be avoided if stick to the General Rule that one material is tied with one SLOC.
Edited by: Daimos on May 16, 2009 5:07 AM

Issue while writing a query in table type select.in the physical layer

Hi gurus,
I am actually trying to create a table using select in the physical layer..... i acutally am not aware what it is called but its when i click a table in the physical layer i have an option table type and i chose select which allows me type my query..the query is
Select
coln name(which is a lengthly list of conversion) AS column_name
From Table name.
when i view the data rom the physical layer everthing seems to be fine. but when i try to view the data in the frnt end it gives me an error maximum length is too long than 128....
i am aware of this issue the sql server allows only column of length 128..but none of my column length is greater than 128..
Could you please help me in this
Many thanks in advance

hi veeravalli ,
Thanks for the reply....actually the corresponding reports for this have already been prepared...i created a view in the backend with the same select which i wrote before and and tried calling the view from her.. i have viewed the data and all is perfect...but when i try viewing it from the front end it error saying invaild object name select * from databasename.dbo.View_name...but i have checked the view exists in the backend...
Thanks in advance....

Creating views in Physical Layer of OBIEE Administration Tool

Hello,
I am doing a proof of concept of creating an OBIEE repository using the Administration Tool to make a model for an in house sandbox OLTP system. Because this POC isn't using a warehouse that is built nicely with everything I need, I am having to import the OLTP tables into the Physical Layer and then create a few extra views (by creating a new physical table object and selecting "Table Type: Select") to add some new columns I will need.
My problem is that once I have created two views 'ViewA' and 'ViewB', I want to then create a third view 'ViewC' that is the union of 'ViewA' and 'ViewB'. But when I create ViewC from these two views and try to then update row count or view data in newly created ViewC, I get an error message of the effect:
Message 208: Invalid object name 'DBO.ViewA'
Message 208: Invalid object name 'DBO.ViewB'
When I try and create ViewC with DBO.OriginalTableA and DBO.OriginalTableB, however, it works just fine. And I am also able to successfully update row count and view data in ViewA and ViewB independently. So it seems to me like a view initialization problem when trying to have ViewC be created from A and B.
Am I trying to do something that is not allowed in the Physical Layer of the BI Admin Tool? I would think that I should be able to work with views just like actual physical tables from my OLTP. Maybe not.
Any help or insight would be greatly appreciated. Many thanks.

Hi Hammett81 ,
I think, I have given configured connection pool correct. (following Oracle guidelines: 'In the Connection Pool dialog box, on the General tab, verify that the call interface is set to Default (OCI 10g) and change the data source name to the appropriate tnsnames.ora entry ( ORCL in this example). Please note that this is the TNS service name, not the ODBC DSN. ' )
I tried to give ODBC DSN (SH) as call interface, which resulted in an Error dialogue, implying, previous configuration was correct.
So, I reverted back.
Regards,
Deeba

Not able to update row count in Physical Layer..connection failed in OBIEE 11g

Hi Guys,
I am not able to do Update Row count in the Physical Layer, i am getting an error The Connection has failed. This is in OBIEE 11g Linux env.
I have put the tnsnames.ora file in the below path:
/*****/pkgs/linux/intel/OBIEE_DIT/MW_HOME/Oracle_BI1/network/admin/
I do not have admin under
/****/pkgs/linux/intel/OBIEE_DIT/MW_HOME/oracle_common/network/
But if i put the whole TNS entry in the Data Source Name i am able to connect:
(DESCRIPTION =(ADDRESS = (PROTOCOL= TCP) (HOST= xxx.xxx.com) (PORT= 1671))(CONNECT_DATA = (SERVICE_NAME = US1OBIEE)))
I am not able to understand the issue..
Thanks,
Amit

Looks like rpd is looking for local tns config... try to use as hostname:port/ServiceName
This should work, just in case not working! stop doing so since it is know issue.
If helps mark

File name naming convention in File Adapter configuration in ID

Hi All ,
I have a query related to xml filename created in IDOC-XI-FILE scenario based on value of one of IDOC field .
The scenario is like this :
I have to send one xml file per store for material master . In this case how can I define my file name with store name in File adapter configuration in ID .
Naming convention should be
<b><storename>_date_masterdataname.xml</b>where store name is one of field of IDOC .
Plz help me .
Thanks in Advance
Regards
Prabhat Ranjan

Hi Prabhat,
take a look at this weblog:
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
you have to specify variable substitution
(in the file adapter)
and give the path to the store name (in the variable sustitution table)
you <b>file name schema</b> (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

Is it possible to control the naming convention used by Aperture when importing photos? If so, how

When I import photos from my camera, I have them placed into projects based on the date the photos were taken. However, I do not like the naming convention used by Aperture as it causes the projects to sort into a non-chronologial order. The convention is MMM-DD-YYYY and I want to change it to YYYY-MM-DD. Is it possible in Aperture 3.2.4 to do this?

In the Import panel you can edit the preset for the file name format to "Image year - image month - image day - index" for example; the preset for folder names seems to be gone in Aperture 3,3 - at least I cannot find it any longer. You only seem to be able to enter the folder name manually in the Import panel.

Physical Layer Naming Convention

Similar Messages

Maybe you are looking for