The Data Model Resource Book, Volume 1: A Library of Universal Data Models for All Enterprises, Revised Edition

Len Silverston, Graeme Simsion (Foreword by)

ISBN: 978-0-471-38023-8

Paperback

560 pages

March 2001

List Price:	US $75.00
Government Price:	US $50.56
Enter Quantity: Buy

The Data Model Resource Book, Volume 1: A Library of Universal Data Models for All Enterprises, Revised Edition (0471380237) cover image

< >

Do you think you've discovered an error in this book? Please check the list of errata below to see if we've already addressed the error. If not, please submit the error via our Errata Form. We will attempt to verify your error; if you're right, we will post a correction below.

Chapter	Page	Details	Date
	10	2nd to last paragraph, last sentence Change from: For example, each INFORMATION ORGANIZATION Change to: For example, each INFORMAL ORGANIZATION
	56	2nd paragraph with the Contact Mechanism Purpose section, first sentence Change from: ... each PARTY CONTACT MECHANISM must have Change to: ... each PARTY CONTACT MECHANISM may have
	86	1st paragraph, first sentence Change from: The ITEM VARIANCE entity ... Change to: The INVENTORY ITEM VARIANCE entity ...
	110	2nd paragraph, last sentence Change from: ORDER ITEM that is for a product feature that is ordered for an ORDER ITEM that is for a product feature. Change to: ORDER ITEM that is for a product to an ORDER ITEM that is for a product feature, which is ordered for the former.
	134	First paragraph Change from: This entity would maintain which SALES ORDER ITEMs fulfilled which REQUIREMENT ITEMs ... It would also maintain which PURCHASE ORDER ITEMs are fulfilled by the REQUIREMENT ITEMs Change to: This entity would maintain which SALES ORDER ITEMs fulfilled which REQUIREMENT ... It would also maintain which PURCHASE ORDER ITEMs are fulfilled by the REQUIREMEN
	145	Third paragraph with the Agreement Definition section, first sentence Change from: ADDENDUMs modify the agreement Change to: ADDENDUMs (see Figure 4.13) modify the agreement
	171	2nd paragraph, after 4th sentence Change to: After the 4th sentence that ends with "that stores the details of the receipt.", insert the following sentence: However, the SHIPMENT PACKAGE may exist without having a SHIPMENT RECEIPT, for instance on outgoing shipments when the organization assembles something into a package. So there is only a mandatory relationship from SHIOPMENT RECEIPT to SHIPMENT PACKAGE.
	243	Model 7.4 Invoice Status and Terms In diagram 7.4 in INVOICE ITEM entity, attribute "unit price" should be changed to "amount"
	246	Model 7.5 Billing for Shipment items Billing for Shipment items, Figure 7.5 Relationship names from and to SHIPMENT ITEM BILLING should be changed. Change the relationship names: - from SHIPMENT ITEM to SHIPMENT ITEM BILLING to "billed via" - from SHIPMENT ITEM BILLING to SHIPMENT ITEM to "of" SHIPMENT ITEM BILLING to INVOICE ITEM to "for" INVOICE ITEM to SHIPMENT ITEM BILLING to "the billing for"
	250	Model 7.7 Billing for order items Billing for order items, Figure 7.7 Relationship names from and to ORDER ITEM BILLING should be changed. Changed the relationship names: - from ORDER ITEM to ORDER ITEM BILLING to "billed via" - from ORDER ITEM BILLING to ORDER ITEM to "of" ORDER ITEM BILLING to INVOICE ITEM to "for" INVOICE ITEM to ORDER ITEM BILLING to "the billing for"
	271	Accounting transaction details diagram, figure 8.3a--Relationship should be mandatory Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL shows a dotted line and therefore that it is optional. Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL should be mandatory in both directions and therefore it should be a solid line all the way across.
	271	Accounting transaction details diagram, Figure 8.3a--Recursive relationship error The recursive relationship around the TRANSACTION DETAIL is shown incorrectly as a solid line. The recursive relationship around the TRANSACTION DETAIL should be optional and therefore be a dotted line throughout the line.
	271	Accounting transaction details diagram, Figure 8.3a--Relationship name missing The relationship from ORGANIZATION GL ACCOUNT to TRANSACTION DETAIL does not have a relationship name. The relationship name from ORGANIZATION GL ACCOUNT to TRANSACTION DETAIL should be "associated with".
	277	Accounting transaction details diagram, figure 8.3b--Relationship should be mandatory Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL shows a dotted line and therefore that it is optional. Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL should be mandatory in both directions and therefore that it should be a solid line all the way across.
	277	Accounting transaction details diagram, Figure 8.3b--Recursive relationship error The recursive relationship around the TRANSACTION DETAIL is shown incorrectly as a solid line. The recursive relationship around the TRANSACTION DETAIL should be optional and therefore be a dotted line throughout the line.
	297	Overall Accounting and budgeting model, Figure 8.12--Relationship should be mandatory Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL shows a dotted line and therefore that it is optional. Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL should be mandatory in both directions and therefore that it should be a solid line all the way across.
	302	Error in Figure 9.2 Relationships from EMPLOYMENT are related to PERSON ROLE and ORGANIZATION ROLE Relationships from EMPLOYMENT should be to EMPLOYEE and INTERNAL ORGANIZATION
	444	Error in referece to table In the 2nd paragraph, first sentence, Table 15.13 should be Table 15.12
	485	Error in PRODUCT CATEGORY ROLLUP attribute names PARTY TYPE ID MADE UP OF PARTY TYPE ID PART OF Should be: PRODUCT CATEGORY ID MADE UP OF PRODUCT CATEGORY ID PART OF
Appendix A	485, 486	Errata in text - Pages 485/486 (Appendix A) Currently Reads: PRODUCT INCOMPATABILITY Should Read: PRODUCT INCOMPATIBILITY	26-Apr-16
Appendix A		Logical Data Model Entities & Attributes, BUDGET ITEM entity, BUDGET_TYPE_ID The attribute BUDGET_TYPE_ID should not be part of the BUDGET ITEM entity
Appendix A		Logical Data Model Entities & Attributes, ORDER ITEM entity, BUDGET_TYPE_ID This attribute should not be in the entity ORDER ITEM. Delete the last line in the ORDER ITEM that shows BUDGET_TYPE_ID as an attribute.
Appendix A		Logical Data Model Entities & Attributes, BUDGET SCENARIO IMPACT entity, BUDGET_TYPE_ID This attribute should not be in the entity BUDGET SCENARIO IMPACT. Delete the line in the BUDGET SCENARIO IMPACT entity that shows BUDGET_TYPE_ID as an attribute.
Appendix A		Logical Data Model Entities and Attributes, BUDGET REVISION IMPACT entity, BUDGET_TYPE_ID This attribute should not be in the entity BUDGET REVISION IMPACT. Delete the line in the POSITION entity that shows BUDGET_TYPE_ID as an attribute.
Appendix A		Logical Data Model Entities & Attributes, REQUIREMENT BUDGET ALLOCATION entity, BUDGET_TYPE_ID This attribute, BUDGET_TYPE_ID, should not be in the entity REQUIREMENT BUDGET ALLOCATION. Delete this first attribute and its associated values of "yes""yes" and "id", and move the BUDGET_ITEM up to be the first attribute in this entity.
Appendix A		Logical Data Model Entities & Attributes, BUDGET entity, BUDGET_TYPE_ID The first column for BUDGET_TYPE_ID should be "no" since it is not part of the primary key
Appendix A		Entity FACILITY has missing attribute Entity FACILITY is missing the PART OF FACILITY ID attribute which does occur in Volume 2 . Need to add PART OF FACILITY ID attribute as part of the FACILITY just after the FACILITY row and the column values are "no" "yes" "ID"
Appendix A		Logical Data Model Entities and Attributes FINANCIAL ACCOUNT should show another attribute (another row) named FINANCIAL ACCOUNT TYPE ID with values of "no" "yes" "ID"
Appendix A		Logical Data Model Entities and Attributes The first attribute in FINANCIAL ACCOUNT TYPE should be FINANCIAL ACCOUNT TYPE ID instead of FINANCIAL ACCOUNT ID
Appendix A	464	Logical Data Model Entities and Attributes The word FINANCIAL ACCOUNT TRANSACTION is repeated for the field ENTRY DATE. This is not correct. The entity name should only be printed once for the first attribute.
Appendix A	464	Logical Data Model Entities and Attributes Only the attribute FINANCIAL_ACCOUNT_TRANSACTION_ID should be marked "yes" for the PK column. The field FINANCIAL ACCOUNT ID should have "no" in the first column indicating that it is not a primary key. Also the field FINANCIAL_ACCOUNT_TRANSACTIONID should be FINANCIAL_ACCOUNT_TRANS_ID instead.
	Volume 1 CD-ROM	CD Error with "description" field REASON should have the "description" field as an attribute and not part of the primary key.
	Volume 1 CD-ROM	CD Error with key for ORDER_ITEM_ROLE ORDER_ITEM_ROLE does not contain the order_item_seq_id as part of its key. ORDER_ITEM_ROLE should contain the order_item_seq_id as part of its key.
	Volume 1 CD-ROM	CD Error: Missing attributes for AGREEMENT AGREEMENT table should have a "description" and "from date" attributes. Add "description" and "from date" attributes to AGREEMENT.
	Volume 1 CD-ROM	CD Error with relationship from ORDER ROLE to ORDER ITEM ROLE Relationship from ORDER ROLE to ORDER ITEM ROLE is incorrect and should be moved. Was changed to a relationship from ORDER ITEM to ORDER ITEM ROLE.
	Volume 1 CD-ROM	CD Error with relationship with INTERNAL ACCTG TRANS INTERNAL ACCTG TRANS should be related to INTERNAL ORGANIZATION and not PARTY ROLE. INTERNAL ACCTG TRANS should be related to INTERNAL ORGANIZATION and not PARTY ROLE.