on 05-31-2018 11:16 AM
Below is our data flow for client systems
EDW table Data->CDS Views -> BODS-> Client local system
BODS jobs getting triggered in cyclic manner to send data to client source systems.
Issue:Delta records are missing in the client source system through BODS.
Reason: Because of bods delta job failure with connection issues records transferred but did not update in client source system.
Question: As the Bods jobs triggerd for every few minutes Can we put a filter in where condition for delta job to pull delta records from sytem date-2?
Will it pull all the delta records from last two days every time it run delta job on the current day?
Please provide a solution to not loose delta records through BODS.
Hi.
First of all would suggest you to troubleshoot with your networks and target system teams.
Now via DS you can build 2 types of delta capture mechanism.
1. Source CDC : https://blogs.sap.com/2014/01/07/source-versus-target-based-change-data-capture/
2. Custom CDC: https://blogs.sap.com/2014/12/04/bods-recovery-and-delta-logic-template-job-creation-guidelines/
With respect to your question about
Will it pull all the delta records from last two days every time it run delta job on the current day?
The answer is 'Yes' and unless your target system is not able to identify the duplicates coming in this is not a good solution. Apart from this the other constraint is what if your job is in a failed state say for more than 2 days (over a long weekend) hence a more robust custom CDC should be designed and developed.
Hope this helps.
Best Regards. S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.