0 Bewertungen0% fanden dieses Dokument nützlich (0 Abstimmungen)
59 Ansichten1 Seite
The Planning Data Collection runs contains two requests - the Planning Data Pull extracts data from EBS and inserts it into the MSC_ST_TRADING_PARTNER_SITES table, while the Planning ODS Load runs after and deletes this data; the user asks to run only the Planning Data Pull to check if the data makes it into the table and determine if any issues exist with the Pull or the Load.
The Planning Data Collection runs contains two requests - the Planning Data Pull extracts data from EBS and inserts it into the MSC_ST_TRADING_PARTNER_SITES table, while the Planning ODS Load runs after and deletes this data; the user asks to run only the Planning Data Pull to check if the data makes it into the table and determine if any issues exist with the Pull or the Load.
The Planning Data Collection runs contains two requests - the Planning Data Pull extracts data from EBS and inserts it into the MSC_ST_TRADING_PARTNER_SITES table, while the Planning ODS Load runs after and deletes this data; the user asks to run only the Planning Data Pull to check if the data makes it into the table and determine if any issues exist with the Pull or the Load.
When the Planning Data Collection runs, there are 2 request sets:
- Planning Data Pull
- Planning ODS Load The Planning Data Pull takes the data from the EBS instance and inserts it int o the MSC_ST_TRADING_PARTNER_SITES table. Once this is complete, the Planning ODS Load is run. Once the Planning ODS Load runs, the data in MSC_ST_TRADING_PARTNER_SITES is de leted. I'm asking you to run the Planning Data Pull ONLY. This will ensure that the data remains in the MSC_ST_TRADING_PARTNER_SITES tabl e, if it's making it at all. This is what we need to understand. Either there is an issue the Pull or an issue with the Load.