Database Design Input -
information bits here and collect it and see:
It is proposed design
1 Chartankrt chart AccountID INT TenantID INT chart Adikarikod VARCHAR (256) dimension 1 CODA VARCHAR (16) Ayansikod VARCHAR (16) dimensions 3 Koda VARCHAR (16) dimensions 4 code VARCHAR (16) dimensions 5 Kode VARCHAR ( 16) dimensions 6 coda VARCHAR (16) dimensions 7 coda VARCHAR (16) dimensions 8 Coda VARCHAR (16) IsExpired BIT ExpiredDate DATETIME note: I can see that dimension / segment only Limited to 8, take Follows me will not think 8. More than any other company I'm open to suggestions with this approach. We put tenantID for many clients / organizations because we store in this application
Sample data:
1 | 310-01-4000. 310 | 01 | 4000 || |||| 2 | 310-02-4000 | 310 | 02 | 4000 ||||||| 3 | 310-03-4000 | 310 | 03 | 4000 ||||||| 4 | 320-01-4000 | 320 01 | 4000 ||||||| 5 | 320-02-4000 | 320 02 | 4000 ||||||| 6 | 320-03-4000 | 320 03 | 4000 ||||||| 7 | 200-01-5000 | 200 | 01 | 5000 ||||||| ...
2 dimensions DimensionID INT ParentDimensionID INT TenantID INT DimensionTypeID INT DimensionCode VARCHAR (16) DimensionName VARCHAR (128) DimensionDescription VARCHAR (256) < / Code> Sample data:
1 | 0 | 1 | 1 | 100 | Corporate Corporation | 2 | 1 | 1 | 1 | 300 Marketing | 3 | 2 | 1 | 1 | 310 | USA Marketing | 4 | 2 | 1 | 1 | 320 Europe Marketing | 5 | 2 | 1 | 1 | 330 | Canada Marketing | 6 | 1 | 1 | 1 | 200 | Production | 7 | 1 | 1 | 1 | 900 Corporate Overhead | 8 | 0 | 1 | 2 | 00 | All lines | 9 | 8 | 1 | 2 | 01 | Line 1 | 10 | 8 | 1 | 2 | 02 | Line 2 | 11 | 8 | 1 | 2 | 03 | Line 3 12 | 0 | 1 | 3 | 4000 0 | | 1 | Expenditure on phone 13 5000 | Statistics on expenditure 3. DimensionTypes DimensionTypeID INT TenantID INT DimensionTypeCode VARCHAR (32) DimensionTypeName VARCHAR (128) DimensionTypeDescription VARCHAR (512) ChartAccountSequence INT length INT Sample data:
1 | 1 | Department | Department | | 1 | 5 2 1 | Line || Line | | 2 | 5 3 1 | NatriacCount | Natural Account | | 3 | 5 4. transactions TransID INT TransDate DATETIME PhoneNo VARCHAR (32) CostDescription VARCHAR (128) Amount Value ChartAccountID INT Sample data:
1 | 2009-05-01 17:00 AM | 0290000000 | Local Call | 30.00 | 1 2 | 2009-05-01 18:01 AM | 0390000000 | Local Call | 25.50 | 2 ...
Any thoughts about this? Especially for the chart account table? As you can see, this set is 8 (dimension 8 cod) which is a negative part of this but I do not think any company will have multiple dimensions?
Within the dimension table is the dimension / parent DimaNIDID relationship to complete the structure within the dimension or do you have a better idea?
I appreciate your comments and then this is not an accounting system .. It is just a simple allocation cost using the chart. Note: I can see that the dimensions / segments are limited to only 8 but I do not have to. Thinks that the other company would be more than 8. I am an open suggestion with this approach.
Bad odor make one-to-many relationships with a table of dimension_sections.
Or maybe it's many-to-many between chart-exchanges and dimensions, because I do not know what "dimension" is.
Explain better yet, why not are you trying to model;
Comments
Post a Comment