Please enable JavaScript.
Coggle requires JavaScript to display documents.
GRD_ER301 - Coggle Diagram
GRD_ER301
Scope
-
-
ETL for ODS
Based Create Date Time ......
Slices of One Day... Pointer table of Success and counts
Chance equists to create data in GDH ( BW ) that exists already... Especially with Target 3
-
-
-
POC
-
-
Achive
-
-
-
Using existing template either create a view or dynamic SQL to copy data for 1 day SDT / EDT from China into ????? Exisitng GDH Schema taking into account GMASITE, GMATime stamp and any oracle field inconsistency.
Imp lent Logging to capture ( Times , Volumes of data, Errors encountered ) In order to asses future sizing.
-
Need to take into account data relationships ( I.E. assembly records -> assembly data ) in one go and keep it consisted
-
The POC will probably look at multiple methods of retrieve the remote data i.e. join versus block lookup... These techniques need to be evalued for pro/cons thus arch documents and findings should be captured.
-
Sudo Two phase commit / checksum needs to be investigated.
Re-Run Query with Count(*) against wip/ods and compare.
Architecture ?'s
Current ME XSA Env
i.e. use existing GDH schema :red_flag:
Addition of new Tables.... Old way or correct way
-
-
Target 1: For each table that is already connected, the historic (old data) needs to be loaded. These tables need to have the old data replicated.
-
Target 2: For each new tables that needs to be replicated the tables must be replicated including the historical data (old data). And then the daily replication must be done. (Implementation scenario of new tables)
-
Target 3: Even if the new data replication is more and more stabilized, there will be a risk for data GAPs, what means that some data of the table in SAP ME is not available in the BW. In such a case, there has to be the possibility to reload this data. (Problem solving for daily replication incidents)