Skip to Content
avatar image
Former Member

Why should we check if InfoObjects are available in the ERP System before creating a new one?

Dear all,

Can you please list the reasons why we should check if an InfoObject is already available in the ERP System before creating a new one? Of course we check because we need to reuse them, but I need a list of reasons as to why we need to reuse them (and not create a new one)?

Thanks in advance!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 22 at 10:45 PM

    Hi Toni,

    The best answer is a long one. Perform a Google search on "Enterprise Data Warehouse" and read about what makes a good EDW.

    Below is a short list, off the top of my head.

    1) Consistent master data and attributes. Using one InfoObject for "material" , "customer" , "vendor" minimizes confusion (which the the "right one"

    2) Data loading. Do you really want to load the same data from the same (or similar) extractors multiple times? I don't think so.

    3) Consistant key figures (or measures). Using a consistent InfoObject can reduce confusion. Assuming the underlying data is cosistent, a consistent "Net Sales" in a single in object reduces confusion. Of course, if various groups diagree, you can use highlight that also (Net Sales - Markering, Net Sales - Finance)

    The failure to reuse prior art can degenerate your Enterprise Data Warehouse into a data lake of loosely related objects.

    John Hawk

    Add comment
    10|10000 characters needed characters exceeded