M:N Data relationships

Hi,
We have a data relationship which is causing headaches so any ideas how to solve this would be greatly appreciated.
Customer Dimension
Cust Code
Cust Desc
Account Dimension
Acc Code
Acc Desc
Balance Facts
Cust Code
Acc Code
Balance
Data :
Balance Facts
record 1 : Cust Code : 1
Acc Code : 1
Balance : 100
record 2 : Cust Code : 2
Acc Code : 1
Balance : 100
Problem :-
1 account owner by 2 customers (joint account holders). When I aggregate this cube the Balance = 200 when it should be 100. I need both customers in the cube because if I drilldown to individual customers each customer must show an account balance of 100.
Any suggestions welcomed.
Cheers,
Brandon

Hi there,
Are customer and account actually separate dimensions? or are they different levels of a hierarchy on the same dimension eg. customer -> account ?
If the answer is the latter, are there any other levels above account?
Stuart

Similar Messages

The best SQL query tool to visualize data relationship

Bay Breeze Software just released SQL Edge 1.4, please refer to http://www.baybreezesoft.com for product details.
SQL Edge is an Eclipse Rich Client application that allows users to execute SQL queries, browse schema information in ER diagrams, and visualize data relationships. With SQL Edge, users can use only one query to retrieve data in a master table, and then browse data in all related detail tables. Users can also insert, edit, and delete table records in the data grids.
SQL Edge has five perspectives. The "Query Perspective" allows users run any SQL queries, while the "Schema Perspective" displays table schema information.
There are two relationship perspectives. The "Relationship Table View" displays data in the master-detail style. The "Relationship Tree View" displays master table records as top-level tree nodes. The nodes can be expanded to reveal any level of related detail records. In addition, clicking any node will display the corresponding data in a detail grid.
The "Model Perspective" displays tables and their relationships in ER diagrams. The tables can be from different databases. Users can define master-detail relationships among these tables, and print or save the diagram for future reference.
The version 1.4 added following features:
(1) Added support for synonyms and CLOB data type.
(2) Added load on demand feature to support large result sets. In query perspective and relationship table view, a selection query will only fetch enough rows to populate the data grids. Users can scroll down the grids to fetch more rows if needed.
The version 1.3 added following features:
(1) Added model perspective to display tables and their relationships in ER diagrams. The tables can be from different databases. Users can define master-detail relationships among these tables, and print or save the diagram for future reference.
The version 1.2 features are:
(1) Support any JDBC compatible databases.
(2) Allow users to specify JDBC drivers at run-time, and provide wizards to help setup JDBC connections. Easy to install, and easy to setup.
(3) SQL editor with syntax highlighting based on currently connected databases.
(4) SQL edtior allows users to execute SQL queries asynchronously. Users can cancel the execution by click the "Cancel" button or just close the SQL Editor.
(5) Schema perspective displays the table schema information, including column definitions, primary key, indexes, and foreign keys.
(6) Relationship table view displays the related data in the master-detail style, with master table data shown in the top grid, and all related detail table data in a list of bottom grids.
(7) Relationship tree view displays the master table records as top-level tree nodes, and the related detail records as child nodes. Click any of these tree nodes will display the corresponding record data in a detail grid.
(8) Allow users to insert, edit, and delete records in the master and detail grids of the relationship table view and relationship tree view.
(9) Allow users to define master-detail relationships even between tables in different databases. This enables the relationship table view and relationship tree view to display data relationships between tables in different databases or without pre-defined foreign keys.

Good to know. Thank you for the information.
Bye, Aron

Difference between Oracle Customer Hub and Hyperion Data Relationship Manag

Hi,
I need integrate diferents data bases and eliminate information redundancy. I think Hyperion Data Relationship Management can help me to acomplish with the task. But i know there is another product named Oracle Customer Hub than can help me too.
Does anybody know the difference between this tools?
Which one its the more appropiate for me?
Regards

FCH was a product launched by Oracle to counter Hyperion Financial Management. However, it is not a proven tool. HFM has a very good market standing coupled with its other reporting capabilities. Also, HFM is a industry leader now.
Financial Consolidation Hub will be removed from the Oracle E-Business Suite Component. FCH will not be included with Release 12.1. This is why, customers are advised to move to Hyperion Financial Management.
An automatic migration utility from FCH to HFM has not been implemented. FCH customers who wish to implement Hyperion Financial Management will have to install the application and complete the implementation process manually.

Req. delivery date and plan order finish date relationship

Dear Experts,
I have a question on setting the req. delivery date and plan order finish date relationship. Now, I want the plan order finish date is one day before the req. delivery date, is it possible to set it in configuration? Please advised! Many thanks!
Regards,
Matt Yim

Matt,
Please use a schedule margin key(SMK) in the material master MPR2 view which has float after production defined as 1day.
If there are no SMK with that defination then you can define you own in customisation and assign the same in the material master. (SPRO--->Production ->MRP->Planning ->Scheduling and Capacity Parameters->Define Floats).
Regards,
Prasobh

MAterial Master Data Relationship

Hi ,
We want to know the table where the details about the material master data relationships (esp. Vendor) is maintained in CRM?
Regards

Hi CP,
Normally, the material relationship tables begins with prefix: COMM_IL_*
Check for example:
- for vendor relationship the table is COMM_IL_PRDVND.
- for acessories relationship the table is COMM_IL_ACCESS
- for customer relationship the table is COMM_IL_PRDCPN
...and so on...
Kind regards.

How to create Date relationship with Fact and DimDate on Tabular model?

I have two tables in SQL Server 2014 SSAS Tabular model.
DimDate(defined as data table) have date column (format is 1.7.2010 00:00:00) This table have been impoted from AdventureWorks.
FactSales have SalesDate column (format is 25.03.2015 18:08:05). This table have been imported from Excel. Colums is defined as date in Excel.
When I set Data Type as date in Tabular I get error:
"Datatype conversion failed for table...Value:'25.03.2015 18:08:05'"
I have tried to create calculated colums like =DATEVALUE([SalesDate]) and =DATE(YEAR([SalesDate]),MONTH([SalesDate]), DAY([SalesDate])), but getting error.
What should I do so that I can create relationship between Date column?
Kenny_I

Hi Kenny_l,
According to your description, you fail to convert the data type into date after creating calculated column with expression. Right?
In Analysis Services, the tabular will detect the source data type to determine which data type can be converted to. If you want to convert a data into date type, no matter this data is from database or a file, you must make sure this data can be recognized
as a date in SQL Server. In this scenario, the format '25.03.2015 18:08:05' can't be recognized as date even you apply DAX functions. So please change the format of the column in excel like "03.25.2015 18:08:05".
PS: For testing, you can create a temp table and insert sample text into a date column, because the date format in SQL Server depends on the location selection when installing.
After retrieving data from data source and all values within column are correct format, you can change the data type into Date, and select the format you expect.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

Flattening 1:m data relationship in List Format Designer

Hi all,
We're implementing Siebel Marketing, which uses OBIEE for Segmentation and List Format for the fulfilment export.
I'm trying to define a List Format that flattens out a one to many relationship in my Siebel data. For example, a Contact in Siebel has two addresses: Home and Work with respective Address Types. From within the List Format alone, I want to be able to extract on a single line for that Contact:
Contact First Name, Contact Last Name, Home Street Address, Home Postcode, Work Street Address, Work Postcode
Is it possible to flatten out 1:M data in this way in the List Format designer alone? The Edit Column Formula give me some options around filtering and transformation but I can't get my head around how I might implement the requirement.
I don't want to have to do anything in the RPD or ETL to achieve this, if I can avoid it.
Many thanks for your thoughts.
Regards,
mroshaw

Hi,
Do you have any identifier that tells you if it is a Home Address or Word Address?
If so then write CASE Statements in all the columns to pick only the home address in the Home Address column and Work Address in the work address column.
See if this helps..

0TCTBWOBJCT - Content Browser: BW Transactional Data Relationships

Hi,
Query on 0TCTBWOBJCT gives me information on Queries published according to roles menus...
Now according to SAP Documents that cube is obselete and asking us to use 0TCTBIOBJCT (infoobject)...but with that info object i can get information Queries published according to roles menus...
Is there any target avaliable in technical content that give me information
Thanks

Hi ,
You can check this document for statistics information :
[BI AdminCockpit|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90080703-4331-2a10-cd98-9c1e95acdea0?QuickLink=index&overridelayout=true]
Regards ,
Lokesh

How to print out the Forms and Table fields relationship, data mapping?

I create a forms and tables relationship inside the Form Developer 11g, once I created the Data relationships between the form data field and the Table column name. I don't have any command to print it out, such as Layout Wizard.
Are there any programs on Windows platform can print it out?

hi all,
i have try to do this
public static void Readbinary() throws Exception
          String file = "D:\\05-09.190501+0800";
          DataInputStream dis = new DataInputStream(new FileInputStream(file));
          //but then how to read the content ??????can you give me more hint ?????
i have find the netflow v5 structure by C
struct NFHeaderV5{
uint16_t version; // flow-export version number
uint16_t count; // number of flow entries
uint32_t sysUptime;
uint32_t unix_secs;
uint32_t unix_nsecs;
uint32_t flow_sequence; // sequence number
uint8_t engine_type; // no VIP = 0, VIP2 = 1
uint8_t engine_id; // VIP2 slot number
uint16_t reserved; // reserved1,2
struct NFV5{
ipv4addr_t srcaddr; // source IP address
ipv4addr_t dstaddr; // destination IP address
ipv4addr_t nexthop; // next hop router's IP address
uint16_t input; // input interface index
uint16_t output; // output interface index
uint32_t pkts; // packets sent in duration
uint32_t bytes; // octets sent in duration
uint32_t first; // SysUptime at start of flow
uint32_t last; // and of last packet of flow
uint16_t srcport; // TCP/UDP source port number or equivalent
uint16_t dstport; // TCP/UDP destination port number or equivalent
uint8_t pad;
uint8_t tcp_flags; // bitwise OR of all TCP flags in flow; 0x10
// for non-TCP flows
uint8_t prot; // IP protocol, e.g., 6=TCP, 17=UDP, ...
uint8_t tos; // IP Type-of-Service
uint16_t src_as; // originating AS of source address
uint16_t dst_as; // originating AS of destination address
uint8_t src_mask; // source address prefix mask bits
uint8_t dst_mask; // destination address prefix mask bits
uint16_t reserved;
but how to translate the structure to java,then get the data from the file ?
Edited by: 903893 on Dec 21, 2011 10:52 PM

Unknown Mask relationships appearing in data

Dear all
I have entered some data in MapInfo and then copied the geometries to other rows using Oracle 10.2. Whilst checking the data relationships I came across the following relationship types, amongst others, in my data:
UNKNOWN MASK: 001001001
UNKNOWN MASK: 000000111
UNKNOWN MASK: 000000001
These must be data errors of some sort but I am not certain what they might be. When I made the table mappable in MapInfo, I set it up so that only regions could be created. This corresponds to SDO_GTYPE 2003 and 2007. All my data is of those types in my table.
I have checked some of the data in MapInfo, and it states that the regions have no problems. I have even attempted to convert a selected geometry to a region but still no luck. I even tried to see if SDO_UTIL.RECTIFY_GEOMETRY would work resolve the problem but it make no difference.
If anyone has any ideas I would be grateful.
Kind regards
Tim

Hi Silva
It looks like I have hit the Oracle Bug 6011024, which you refer to. I am not certain which version of Oracle 10.2 I am using but it is earlier than patch 10.1.2.4. I have left this with my university supervisors.
I will of course look into the sdo_geom.validate_geometry_with_context() routine, as I had been trying to locate something like that, just to be certain I do not have any other unknown issues.
Kind regards
Tim

Relationship of Data

Why is data relationship (1:M and/or M:N) necessary when it comes to data modeling?
Thanks,
RG

Hi,
The cardinality (n : m) describes the relationship with respect to the number of dependent entities (entities of the target entity type of the relationship) and referenced entities (entities of the source entity type) allowed for the relationship.
With Line Item Dimension, you can assign ONE Dimension to only one characteristic.
With Cardinality, you can assign a Dimension containing Multiple Characteristics.
The possible values for the left and right sides of the cardinality have the following significance:
n = 1
Each dependent entity has one referenced entity.
n = C
Dependent entities can exist that do not refer to an entity of the source entity type.
m = 1
Each entity of the source entity type has one dependent entity.
m = C
Each entity of the source entity type has a maximum of one dependent entity.
m = N
Each entity of the source entity type has at least one dependent entity.
m = CN
Each entity of the source entity type can have any number of dependent entities.
The cardinality C:x (x = 1, C, CN, N) should be used only for relationships of the category 'referential'. (However, it can also be used for relationships of the category 'aggregating'.)
Hierarchical relationships do not allow this cardinality, since all dependent entities must refer to an entity of the source entity type.
also chk
cardinalityRegards
Remya
Edited by: Remya Chandran on Mar 31, 2008 5:03 AM

BI IP-Characteristic Relationship- invalid combinations are shown

Dear all,
we need to create a query ready for input but we need to avoid that the invalid combinations of two characteristic on wors are shown.
In fact the system presents the inconsistent combination as not editable.
Could you please suggest how to avoid this?
Many thanks in advance for help!
Stefania

Hi
the link is ueseful, but I try to explane what we really need.
We have in the level two chars (ZC1 and ZC2; ZC2 is attribute of ZC1) and here you can see the values
ZC1               ZC2
PREVAI     AI
GUASAI     AI
PREVBT     BT
GUASBT     BT
The requiremet is that the user can plan by ZC1 and ZC2, but that he has a total row by ZC2 (not editable).
That's why I defined a structure on the rows with restrictions for ZC1 and ZC2, according to the master data relationship, and put the structure on the rows.
I defined a hierarchy for ZC1 where nodes are values of char ZC2 and I set this in the characteristic relationship for the provider. here is the hierarchy.
AI
    PREVAI
    GUASAI
BT
    PREVBT
    GUASBT
The result is that in the best option I see in the query invalid combinations such as BT PREVAI.
Any suggestion?

Having trouble with a one to many relationship in Crystal reports 11

I have an old report that I inherited. I have two main tables from which I draw data into this report: QAmonitortrack and monitorsperfm. I am correctly getting my data out of the QAmonitortrack table as the data relationships are one to one, but when I try to retrive data from the monitosperfm table, I only get one record back for each csrid. I am trying to calculate the number of [callid] in the monitosperfm table for the fiscal month. I have been through almost all of the table links and tried changing the link properties to give me more than one callid for each csrid I pulled out of qamonitortrack table.
Any suggestions?
Thanks...sql listed below:
SELECT "tblSupervisors"."LastName", "tblSupervisors"."FirstName", "tblCSR"."LastName", "tblCSR"."FirstName", "tblDirectors"."LastName", "tblDirectors"."FirstName", "tblSupervisors"."SupervisorID", "tblQAMonitorTrack"."CSR_ID", "tblQAMonitorTrack"."FiscalYear", "tblQAMonitorTrack"."FW_Month", "tblQAMonitorFWCalendar"."FiscalYear", "tblQAMonitorFWCalendar"."Fiscal_Month", "tblFM_BeginEndDates"."fm_start_date", "tblQAMonitorTrack"."FiscalWeek", "tblFM_BeginEndDates"."fm_end_date", "tblQAMonitorFWCalendar_1"."FiscalWeek", "tblQAMonitorFWCalendar_2"."FiscalWeek", "tblMonitorsPerFM"."callid", "tblMonitorsPerFM"."score", "tblQAMonitorFWCalendar"."FW_Start_Date", "tblQAMonitorFWCalendar"."FW_End_Date", "tblQAMonitorFWCalendar"."FW_Week_of_Month", "tblQAMonitorTrack"."CallsHandled", "tblCSR"."Group_ID", "tblPosition"."PositionDesc", "tblMonitorsPerFM"."dateofmonitor"
FROM ((((((((("SMG_APPS"."dbo"."tblQAMonitorTrack" "tblQAMonitorTrack" INNER JOIN "SMG_APPS"."dbo"."tblManagers" "tblManagers" ON "tblQAMonitorTrack"."Mgr_id"="tblManagers"."ManagerID") INNER JOIN "SMG_APPS"."dbo"."tblSupervisors" "tblSupervisors" ON ("tblQAMonitorTrack"."Sup_Id"="tblSupervisors"."SupervisorID") AND ("tblManagers"."ManagerID"="tblSupervisors"."ManagerID")) INNER JOIN "SMG_APPS"."dbo"."tblCSR" "tblCSR" ON "tblQAMonitorTrack"."CSR_ID"="tblCSR"."CSRID") INNER JOIN "SMG_APPS"."dbo"."tblFM_BeginEndDates" "tblFM_BeginEndDates" ON ("tblQAMonitorTrack"."FiscalYear"="tblFM_BeginEndDates"."fiscalyear") AND ("tblQAMonitorTrack"."FW_Month"="tblFM_BeginEndDates"."fiscal_month")) INNER JOIN "SMG_APPS"."dbo"."tblMonitorsPerFM" "tblMonitorsPerFM" ON ((((("tblQAMonitorTrack"."FiscalYear"="tblMonitorsPerFM"."fiscalyear") AND ("tblQAMonitorTrack"."FW_Month"="tblMonitorsPerFM"."fiscal_month")) AND ("tblQAMonitorTrack"."CSR_ID"="tblMonitorsPerFM"."csrid")) AND ("tblQAMonitorTrack"."Sup_Id"="tblMonitorsPerFM"."supervisorid")) AND ("tblQAMonitorTrack"."Process_Order"="tblMonitorsPerFM"."Process_Order")) AND ("tblQAMonitorTrack"."Mgr_id"="tblMonitorsPerFM"."managerid")) LEFT OUTER JOIN "SMG_APPS"."dbo"."tblQAMonitorFWCalendar" "tblQAMonitorFWCalendar" ON "tblQAMonitorTrack"."FiscalWeek"="tblQAMonitorFWCalendar"."FiscalWeek") LEFT OUTER JOIN "SMG_APPS"."dbo"."tblQAMonitorFWCalendar" "tblQAMonitorFWCalendar_1" ON "tblFM_BeginEndDates"."fm_start_date"="tblQAMonitorFWCalendar_1"."FW_Start_Date") LEFT OUTER JOIN "SMG_APPS"."dbo"."tblQAMonitorFWCalendar" "tblQAMonitorFWCalendar_2" ON "tblFM_BeginEndDates"."fm_end_date"="tblQAMonitorFWCalendar_2"."FW_End_Date") INNER JOIN "SMG_APPS"."dbo"."tblDirectors" "tblDirectors" ON "tblManagers"."DirectorID"="tblDirectors"."DirectorID") LEFT OUTER JOIN "SMG_APPS"."dbo"."tblPosition" "tblPosition" ON "tblDirectors"."PositionID"="tblPosition"."PositionID"
WHERE NOT ("tblSupervisors"."SupervisorID"=0 OR "tblSupervisors"."SupervisorID"=17 OR "tblSupervisors"."SupervisorID"=19 OR "tblSupervisors"."SupervisorID"=20 OR "tblSupervisors"."SupervisorID"=33 OR "tblSupervisors"."SupervisorID"=35) AND ("tblFM_BeginEndDates"."fm_end_date">={ts '2010-11-27 00:00:00'} AND "tblFM_BeginEndDates"."fm_end_date"<{ts '2010-11-28 00:00:00'}) AND "tblQAMonitorTrack"."FiscalYear"="tblQAMonitorFWCalendar"."FiscalYear" AND "tblQAMonitorTrack"."FW_Month"="tblQAMonitorFWCalendar"."Fiscal_Month" AND "tblQAMonitorTrack"."FiscalWeek">="tblQAMonitorFWCalendar_1"."FiscalWeek" AND "tblQAMonitorTrack"."FiscalWeek"<="tblQAMonitorFWCalendar_2"."FiscalWeek" AND ("tblCSR"."Group_ID"=1 OR "tblCSR"."Group_ID"=10 OR "tblCSR"."Group_ID"=15)
ORDER BY "tblSupervisors"."SupervisorID", "tblQAMonitorTrack"."CSR_ID"

If the db is huge, you may want to copy it, and delete all but a few hundred rows.
Then you can play with the copy till you get the query doing what you want.
You might try changing this section
"tblQAMonitorTrack"."CSR_ID"="tblCSR"."CSRID") INNER JOIN "SMG_APPS"."dbo"."tblFM_BeginEndDates" "tblFM_BeginEndDates" ON ("tblQAMonitorTrack"."FiscalYear"="tblFM_BeginEndDates"."fiscalyear") AND ("tblQAMonitorTrack"."FW_Month"="tblFM_BeginEndDates"."fiscal_month")) INNER JOIN "SMG_APPS"."dbo"."tblMonitorsPerFM" "tblMonitorsPerFM" ON
To left outer joins.
Also, just create a connection to the tblMonitorsPerFM all by itself, run a query and see if you get multiple results directly from the DB...

MinList function is not working in Date or datetime values in DRM

Hi,
We have a custom property End Date with data type as Date. We want to calculate the minimum end date across all the children of a particular node.
While using the below function it is giving blank value as output.
MinList(ReplaceStr(ListNodePropValues(ListChildren(SortOrder),[comma],Custom.NO_ALL_ALL_ENDDATE),[comma],#,true),#,date)
If we remove the MinList part and only evaluate ReplaceStr(ListNodePropValues(ListChildren(SortOrder),[comma],Custom.NO_ALL_ALL_ENDDATE),[comma],#,true), we are getting an output like 12/31/2019#12/31/2018.
Why DRM is not able to extract the min value? Does DRM not support this kind of use of this function?
We have even tried with a date time property, but the result is same.
If by using the above mentioned method it is not possible to get the min date value, what alternative approach can be taken for achieving this?
Any help on this is much appreciated.
Thanks
Sudipta

I found this useful, check if it helps,
Using MinList and MaxList with Date Or DateTime Values In DRM (Doc ID 1967005.1)
Hyperion Data Relationship Management - Version 11.1.2.3.000 and later
Information in this document applies to any platform.
GOAL
Example: How can we calculate the minimum end date across all the children of a particular node?
You have a custom property End Date with data type as Date. You have tried using MinList in conjunction with ListNodePropValues thus:
MinList(ReplaceStr(ListNodePropValues(ListChildren(SortOrder),[comma],Custom.EndDate),[comma],#,true),#,date)
This gives a blank value as output.
SOLUTION
The most robust way of doing this using formulas is to format the date property as a string in ISO 8601 format. In yyyy-mm-dd format, alphabetic order is also date order. Add a helper String property like this:
FormattedDate(Custom.EndDate),yyyy-mm-ddThh:mm:ss) -- omit the time from the 'T' on if desired. Note that the format string is case sensitive.
Then the MinList function
MinList(ReplaceStr(ListNodePropValues(ListChildren(SortOrder),[comma],Custom.Helper),[comma],#,true),#,string)
will work.
Note that the functions MinList and MaxList return a blank value if the list contains any members that are not of the specified data type. Using ReplaceStr will implicitly convert the dates into strings, causing MinList and MaxList to fail if you specify DateTime.

M:N Relationships

Hi,
We have a data relationship which is causing headaches so any ideas how to solve this would be greatly appreciated.
Customer Dimension
Cust Code
Cust Desc
Account Dimension
Acc Code
Acc Desc
Balance Facts
Cust Code
Acc Code
Balance
Data :
Balance Facts
record 1 : Cust Code : 1
Acc Code : 1
Balance : 100
record 2 : Cust Code : 2
Acc Code : 1
Balance : 100
Problem :-
1 account owner by 2 customers (joint account holders). When I aggregate this cube the Balance = 200 when it should be 100. I need both customers in the cube because if I drilldown to individual customers each customer must show an account balance of 100.
Any suggestions welcomed.
Cheers,
Brandon

Sorry for making this confusing -- even simple answers can get complicated quickly if you don't have a good model to work with.
I would therefore suggest that you take the accounts/customers and create a simple spreadsheet. If you follow the logic that formulas must be applied to all elements of a given row OR column within the "grid" that is created, you can ultimately diagram the totals for the columns and rows. The formulas would obviously not be simple sums, but they would be close to that. After you model this "roll-up" that way, you only have to translate it into member formulas and ensure the calc order is appropriate (rows then columns or columns then rows). Keep it simple, and eventually you will hit on the formula/model that works for you. Then it's just a matter of translation.
As for my suggestions, I doubt that I coudl make it much more meaningful (it is hard to translate the relatively simple pictures in my mind into simple sentences in a forum). This is the kind of thing you either did before or not, and working through it is a non-trivial task even when you have a firm grasp of the goals (but something that a clear picture makes a lot easier, nonetheless).
What a) and b) are really saying is that reporting on non-input level data can only be done for 1 of the 2 dimensions, so that selecting a non-input account implies an input level customer (and vice versa). Each accomplishes this in a slightly different way. A) does this by creating a customer relationship for each combination of customers and B) does this by entering data at the "Customer Total" level and then replicating this to the associated customers as "memo items" (non-contributory members). Using these memo items at non-input account levels would result in "wrong" values.
Essentially, approach b) uses the "Customer Total" value is the only valid roll-up for any account total. You eliminate the need for customer totals because the individual account value is stored there, and the customers have to be populated with a copy of this data for any accounts they are attached to. The totals by customer are the sum of the accounts, while the sum for the accounts is only taken by the "Customer Total" member so there is no double-counting.
Approach a) is a similar scheme but has an account total value that allows the customers to have a hierarchy (approach b denied this ability).
Approach c) is a simple allocation scheme that combines approach b) with an input member for each account which is allocated to the "Customer Total" and to the attached customers. This is a logical next step from approach b (which is more of a proof of concept then a final solution).

M:N Data relationships

Similar Messages

Maybe you are looking for