Advice for business objects model - This is NOT for SAP Business Objects
Hi All,
I need your assistance starting a table/relationships similar to an Entity Relationship Diagram (ERD) for storing business objects. Please note this is not for SAP Business Objects.
The definition of a business object is “an entity that describes a person, place or thing that is essential to a business system, which the subject system needs to be keep track of”.
I am not really sure which tables / relationships are needed for business objects. I would appreciate your guidance or examples.
Thank you.
I need your assistance starting a table/relationships similar to an Entity Relationship Diagram (ERD) for storing business objects. Please note this is not for SAP Business Objects.
The definition of a business object is “an entity that describes a person, place or thing that is essential to a business system, which the subject system needs to be keep track of”.
I am not really sure which tables / relationships are needed for business objects. I would appreciate your guidance or examples.
Thank you.
ASKER
Thank you so much for your comment.
At this stage we do not know the business objects, but I have been asked to provide a list of tables / relationships in an ERD format for storing existing and future business objects. I am at a lost here on how I can identify tables / relationship for business objects. I have goggled for help on this but I can’t seem to find anything useful. Could you provide guidance or examples on how I can do this.
At this stage we do not know the business objects, but I have been asked to provide a list of tables / relationships in an ERD format for storing existing and future business objects. I am at a lost here on how I can identify tables / relationship for business objects. I have goggled for help on this but I can’t seem to find anything useful. Could you provide guidance or examples on how I can do this.
You can't create an ERD if you don't know the Business Objects.
An ERD represents the Business Objects in your domain. These will vary depending on your app requirements:
If you're writing an Order Processing app, then you may need Customer / Order / Order Details / Product etc.
If you're writing a Book Catalogue app, then you may need Author / Publisher / Book etc.
If you're writing an Employee Management app then you may need Employee / Department / Company etc.
The ERD is directly tied into the objects that a specific Business requirement has. You can't possible start designing an ERD (or Database) if you don't know what you want to store.
Do a Google Image search for ERD and you'll see that they all have entities relating to a specific business requirement.
An ERD represents the Business Objects in your domain. These will vary depending on your app requirements:
If you're writing an Order Processing app, then you may need Customer / Order / Order Details / Product etc.
If you're writing a Book Catalogue app, then you may need Author / Publisher / Book etc.
If you're writing an Employee Management app then you may need Employee / Department / Company etc.
The ERD is directly tied into the objects that a specific Business requirement has. You can't possible start designing an ERD (or Database) if you don't know what you want to store.
Do a Google Image search for ERD and you'll see that they all have entities relating to a specific business requirement.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
If you were writing a system for a Mail Order company for example, the Business Objects may include things like Customer, Order, Product etc. These are your entities and could be broken down further. For example, a Customer may have more than one address, so an Address would be an entity. An order will often have more than one item on it, so OrderDetail would be an entity. Your ERD then comes about from how these Business Objects (entities) relate to one another. For example - A Customer can have many Orders. An Order can have many OrderDetails. An OrderDetail may relate to one Product, a Product may have several Suppliers etc. Once you've got an idea on how your Business Objects relate to each other, then you can translate this into your DB Schema, designing the tables, indexes, relationships etc.