Remediation_v1 To Be Done
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Remediation_v1 To Be Done as PDF for free.
More details
- Words: 2,370
- Pages: 19
Work stream Task ID
Remediation Task
Description
Benefits Category Priority Team
Benefits
ETL
1 SRC to GFIS, ETL1, ETL2 Align GFIS table structure to version 1.3
Standardization
Critical
Kavya/AAK
> Underline data structure for GFIS will be complained with latest approved version
ETL
2 ALL
Performance Tuning Critical
HCLT / FFT Team
> Data volume maintain in ETL layer will be reduced. Less overhead on database. Performance.
ETL
3 ETL -> SAP
Critical
FFT Team / HCLT
ETL
4 SRC to GFIS
Critical
Kavya/AAK
ETL
5 Portal -> ETL
Critical
ETL
6 ETL2
ETL
7 Portal -> ETL
ETL
8 ETL1, ETL2
Standardization Introduce more stable process around the communication between Portal and ETL. Swinging & Netting, RFP Derivation performance Performance Tuning tuning - Multithreading Performance Tuning Manual Adjustment validation flow to be done within 2 min Performance tuning on non-Portal components. Performance Tuning Informatica tuning : Profile all components, identify top resource consumers, optimize logging
HCLT / FFT Team FFT Team / HCLT HCLT / FFT Team HCLT / FFT Team
> Can avoid the workflow breaks, If SAP / external connection fails. Without manual interation, the next set of file will be processed. > Can avoid the workflow breaks, If any hard error happens due to source file issue, then without manual interation, the next set of files will be processed > Can avoid the missing document issues.
9 Lookup with appropriate filter 10 Lookup condition on date fields
While lookingup against RDM table appropriate Performance filter ex : SKB1.BUKRS to be applied . Suspension dates/activation dates are used Output quality instead of ValidFrom/ValidTo or in some cases dates are not being used at all. As the output will differ if there are more than one document id's.
High
ETL
11 Portal -> ETL
ETL
12 Error Handling
ETL
13 Taxonomy
ETL
14 Database
Split Portal specific rules from the core components Streamlining the Exception handling and logging mechanism for better supportability, for all the workflows > Send workflow and session logs to technical support team Rule clean-up. Verify the taxonomy rules against the implementation. Database Tuning Partitioning > review / adjust GFIS partitions > implement partitioning for message tables redesign HDR/ASN tables > create subpartition for stage in TMP table
ETL ETL
Streamlining the data interaction with intercomponents. Move the current workflow components into Mapplet to avoid the source qualifier and target update for each compoent. This lead into lot of database operations now. SAP interface failure error handling > Implement timeout control, state monitoring, persistant logging Source File hard error handling
Standardization, Transparency on Issues Standardization
Critical Critical Critical
> Targeted processing requirement > Targeted processing requirement > Targeted processing requirement
HCLT / FFT Team HCLT / FFT Team
This will reduce the full table scan.
HCLT / FFT Team HCLT / FFT Team
> Easy to add new changes.
Flexibility for Rollins High
KT Team
> Upto date taxonomy document.
Performance Tuning High
FFT Team /Kavya/AAK
> Performance
High
Flexibility for Rollins High Flexibility for Rollins High
Data anomolies can be fixed at the early stage
> Easy to maintain the new changes and technical debug issues.
ETL
15 Database
Database Cleanup > review inventory of tables, views, etc. drop unused objects > remove unused entries from setup tables
High
FFT Team /Kavya/AAK
> Removal of unwanted database objects.
ETL
16 Database 17 Informatica Server
FFT Team /Kavya/AAK HCLT / FFT Team
> Performance
ETL
Database Tuning Partitioning Performance Tuning High > create new views for GFIS lookup Standardization High Informatica Server Tuning >optimize cache file sizes (dependent on runtime stats) > "setup runtime statistics capturing processidentify top resource consumers," > optimize reusable components / consolidate in a specific folder
ETL
18 Informatica Server
Neboja
> Performance
ETL
19 Purge temp data
ETL
20 ETL1
Standardization Informatica Server Tuning > "revisit parameterization- review/optimize parameter files- introduce parameter table for Infa" Storage Automate the Purging of the temp data after 2 days CR 467: Risk of ACS duplicate files being posted
ETL
21 ETL1
ETL
22 ETL1
ETL
23 Portal -> ETL -> SAP
ETL
24 Portal -> ETL
SAP Document ID - Ack from SAP on successful Standardization posting Capture reference data error message Standardization
ETL
25 Reference data
Incremental RDM Data synchronization
Scalability
Medium
ETL
26 RTB Support
Reengineer the ETL code delivery process
Standardization
Medium
ETL
27 RTB Support
Support utilities -- Joseph will discuss
Support Tools
Medium
ETL
28 RTB Support
Medium
ETL
29 Workaround 30 Archving
Medium HCLT / FFT Team Medium HCLT / FFT Team
Flexibility for Rollins
ETL
Fit the FSR Framework processes into dbFeeds Support Tools RTB dashboard tool. Standardization RFP TLR Hard coding values col 7,8 for workaround. Final stage data is what required to be Scalablility archived, instead os multi stage data, which will reduce the table segment running out of space.
Off-Balance Sheet derivation Fixes
High
Missing Functionality build Crtical for June Month-End
On-going Devt (to be completed by 11th June) ETL 31 Missing Build Planned for 2008
Standardization
CR 467: RFP derivation for parent-child not wrking as expected CR 467: RDM refresh during feed file processing
Functionality
High
High
Kavya/AAK/B alaji High HCLT Team/Balaji High HCLT Team/Balaji High HCLT Team/Balaji Medium HCLT / FFT Team Medium HCLT / FFT Team
> Performance
> Performance > Production issue closure > Production issue closure > Production issue closure
> Transparency on the SAP process status in Portal screen > These error messages should be shown currently sent only to support users. By this enhancement ETL will sent this message to Portal. User have access to these error messages in one place. HCLT / FFT Latest refrence data availabilty for derivation and Team validation. Kavya/AAK/B Improve Quality alaji HCLT / FFT Easy to review the issue / support production env. Team Sathish Overall Feed reporting
FFT Team / HCLT
Scalability of several locations without affecting the platform
ETL
32 Hardware capability
Dedicated Server for FSR processes
Scalability
Joseph
Dependency > Approval of new field additions to the GFIS standard will be more useful do this excise once, rather than repeating every time.
> Need input from Finance on this.
> Portal have to accept this change and display. > Portal have to accept these messages.
Based on Reference data timing requirement
Task ID
Task Breakup
Effort (man-days)
Assign to Status
Stress Testing (current Design)
2 BJ
Stress Testing (with new Design)
3 Vimal
1 1 1 1 1 2 2 2
Completed
Planned Start Dt
Planned End Dt
Actual Start Dt
Actual End Dt
To improve the performance in ETL1 and 2 Major Tasks 1st level
Add more views for SAP and GFIS reference tables
Prepare statis flows like the portal 2nd level > Still the individual components will have different workflows
3rd level
Streamlining the data interaction with inter-components. Move the current workflow components into Mapplet to avoid the source qualifier and target update for each compoent. This lead into lot of database operations now.
Impact No impact. But once the all the locations are implemented the view willl have more records. This will improve the performance 10 to 15 %. But Flexibility of including compoents dynamically through database setup is not possible. Note Anyway in PROD env dynamic workflow changes is not a must requirement. This will improve the performance min 50 %. But Flexibility of including compoents dynamically through database setup is not possible. > More effort involved.
Current Targeted Interface Volume SLA Timing Timing Portal (end to end for validation / posting) 2 5 min 7 to 8 min 4 min SAC / Manual Adjustment 1000 10,000 3 x 10,000 2 3 min 7 to 8 min 2 min FLA / NFI 1000 10,000 3 x 10,000 Portal (end to end - etl validation / r3 posting / bw update / data availability for report ) After portal approval and submit, ETL1 : 5 mins R3 Posting : 2 mins R3 to BW Transfer : 15 mins (currently scheduled for eve ry 10/15 mins) BW Report cube refersh time : 5 min Note : Data availability for Report end to end 30 min should be possible, if no master bwkey data changes. 2 30 min 7 to 8 min 4 min SAC / Manual Adjustment 1000 10,000 3 x 10,000 Source to GFIS (interface processing) 1000 na 25 min CPY 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min CON 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min INS / INX 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min DDM / DDM-A / DDM-M 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min DBP 10,000 na 35 min 100,000 na na 3 x 100,000 na na ETL Layer 1 1000 15 min 25 min 15 min All interfaces 10,000 20 min 35 min 20 min 100,000 30 min na 30 min 3 x 100,000 45 min na 45 min ETL Layer 2 1000 20 min 25 min 15 min Including RFP derivation 10,000 25 min 35 min 20 min 100,000 30 min na 30 min 3 x 100,000 45 min na 45 min
Remarks 10 sec for sftp
ability for report )
f no master bwkey data changes. 10 sec for sftp
No of RML rules: 90,000 records PK table : 28,000 records
Interface Portal (end to end for validation / posting) SAC / Manual Adjustment
Volume
SLA
Current Timing
2 5 min 7 to 8 min 1000 10,000 3 x 10,000 2 3 min 7 to 8 min FLA / NFI 1000 10,000 3 x 10,000 Portal (end to end - etl validation / r3 posting / bw update / data availability for report ) After portal approval and submit, ETL1 : 5 mins R3 Posting : 2 mins R3 to BW Transfer : 15 mins (currently scheduled for eve ry 10/15 mins) BW Report cube refersh time : 5 min Note : Data availability for Report end to end 30 min should be possible, if no 2 30 min SAC / Manual Adjustment 1000 10,000 3 x 10,000 Source to GFIS (interface processing) 1000 na CPY EP 10,000 na 100,000 na 3 x 100,000 na 1000 na IDMS 10,000 na 100,000 na 3 x 100,000 na 1000 na ACS 10,000 na 100,000 na 3 x 100,000 na 1000 na CON EP 10,000 na 100,000 na 3 x 100,000 na 1000 na IDMS 10,000 na 100,000 na 3 x 100,000 na 1000 na SUMMIT 10,000 na 100,000 na 3 x 100,000 na 1000 na RMS 10,000 na 100,000 na 3 x 100,000 na 1000 na ACS 10,000 na 100,000 na 3 x 100,000 na 1000 na INS / INX EP
7 to 8 min
25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min
INS / INX
EP 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000
na na na na na na na na na na na na na na na na na na na na na na na na na na na na na na na
35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na
All interfaces
1000 10,000 100,000 3 x 100,000
15 min 20 min 30 min 45 min
25 min 35 min na na
Including RFP derivation
1000 10,000 100,000 3 x 100,000
20 min 25 min 30 min 45 min
25 min 35 min na na
ACS
DDM / DDM-A / DDM-M
EP
IDMS
ACS
DBP
EP
ACS
IDMS
ETL Layer 1
ETL Layer 2
Targeted Timing
Remarks
4 min 10 sec for sftp
2 min
y for report )
4 min 10 sec for sftp
3 min EP-636 records
2 min 44 sec 2772 records
2 min 51sec 348 records
2 min 17sec 5 records
2min 22 sec 3232 records
4 min 18 sec 568 Records
2 min 11 sec 53 records
2 min 53 sec 3616 records
5 min 3 sec 27564 records
1 min 0 records
2 min 35 sec 284 records
4 min 14684 records
5 min 20sec 8006 records
2 min 1 sec 267 records
1 min 4 records
2 min 33 sec
15 min 20 min 30 min 45 min 15 min No of RML rules: 90,000 records 20 min PK table : 28,000 records 30 min 45 min
WORKFLOW_NAME START_TIME END_TIME Duration wf_Start_WF_ETL_2_1 5/21/2007 5:27 5/21/2007 6:03 0:35 wf_Start_WF_ETL_2_1 5/21/2007 21:00 5/21/2007 21:55 0:55 wf_Start_WF_ETL_2_1 5/22/2007 6:25 5/22/2007 7:34 1:09 wf_Start_WF_ETL_2_1 5/22/2007 8:23 5/22/2007 9:37 1:14 wf_Start_WF_ETL_2_1 5/23/2007 3:34 5/23/2007 4:55 1:20 wf_Start_WF_ETL_2_1 5/24/2007 3:33 5/24/2007 5:02 1:28 wf_Start_WF_ETL_2_1 5/24/2007 20:30 5/24/2007 21:47 1:17 wf_Start_WF_ETL_2_2 5/25/2007 4:02 5/25/2007 4:44 0:42 wf_Start_WF_ETL_2_3 5/25/2007 6:00 5/25/2007 6:38 0:38 wf_Start_WF_ETL_2_4 5/25/2007 8:00 5/25/2007 8:45 0:45 wf_Start_WF_ETL_2_1 5/25/2007 20:30 5/25/2007 21:12 0:41 wf_Start_WF_ETL_2_2 5/26/2007 3:15 5/26/2007 4:01 0:46 wf_Start_WF_ETL_2_3 5/26/2007 6:00 5/26/2007 6:37 0:37 wf_Start_WF_ETL_2_4 5/26/2007 8:00 5/26/2007 8:39 0:39 wf_Start_WF_ETL_2_1 5/26/2007 20:30 5/26/2007 21:06 0:36 wf_Start_WF_ETL_2_2 5/27/2007 3:15 5/27/2007 4:37 1:22 wf_Start_WF_ETL_2_3 5/27/2007 6:00 5/27/2007 6:34 0:34 wf_Start_WF_ETL_2_4 5/27/2007 8:00 5/27/2007 8:33 0:33 wf_Start_WF_ETL_2_1 5/27/2007 20:30 5/27/2007 21:04 0:34 wf_Start_WF_ETL_2_2 5/28/2007 3:15 5/28/2007 3:49 0:34 wf_Start_WF_ETL_2_3 5/28/2007 6:00 5/28/2007 6:37 0:37 wf_Start_WF_ETL_2_4 5/28/2007 8:00 5/28/2007 8:50 0:50 wf_Start_WF_ETL_2_1 5/28/2007 20:30 5/28/2007 21:08 0:37 wf_Start_WF_ETL_2_2 5/29/2007 3:59 5/29/2007 4:42 0:43 wf_Start_WF_ETL_2_3 5/29/2007 6:00 5/29/2007 6:43 0:42 wf_Start_WF_ETL_2_4 5/29/2007 8:00 5/29/2007 8:42 0:42 wf_Start_WF_ETL_2_1 5/29/2007 20:30 5/29/2007 21:17 0:47 wf_Start_WF_ETL_2_1 5/30/2007 20:30 5/30/2007 21:06 0:36 wf_Start_WF_ETL_2_2 5/31/2007 3:15 5/31/2007 3:56 0:40 wf_Start_WF_ETL_2_3 5/31/2007 6:00 5/31/2007 6:30 0:30 wf_Start_WF_ETL_2_4 5/31/2007 8:00 5/31/2007 8:40 0:40 wf_Start_WF_ETL_2_1 5/31/2007 20:30 5/31/2007 21:02 0:31
Remediation Task
Description
Benefits Category Priority Team
Benefits
ETL
1 SRC to GFIS, ETL1, ETL2 Align GFIS table structure to version 1.3
Standardization
Critical
Kavya/AAK
> Underline data structure for GFIS will be complained with latest approved version
ETL
2 ALL
Performance Tuning Critical
HCLT / FFT Team
> Data volume maintain in ETL layer will be reduced. Less overhead on database. Performance.
ETL
3 ETL -> SAP
Critical
FFT Team / HCLT
ETL
4 SRC to GFIS
Critical
Kavya/AAK
ETL
5 Portal -> ETL
Critical
ETL
6 ETL2
ETL
7 Portal -> ETL
ETL
8 ETL1, ETL2
Standardization Introduce more stable process around the communication between Portal and ETL. Swinging & Netting, RFP Derivation performance Performance Tuning tuning - Multithreading Performance Tuning Manual Adjustment validation flow to be done within 2 min Performance tuning on non-Portal components. Performance Tuning Informatica tuning : Profile all components, identify top resource consumers, optimize logging
HCLT / FFT Team FFT Team / HCLT HCLT / FFT Team HCLT / FFT Team
> Can avoid the workflow breaks, If SAP / external connection fails. Without manual interation, the next set of file will be processed. > Can avoid the workflow breaks, If any hard error happens due to source file issue, then without manual interation, the next set of files will be processed > Can avoid the missing document issues.
9 Lookup with appropriate filter 10 Lookup condition on date fields
While lookingup against RDM table appropriate Performance filter ex : SKB1.BUKRS to be applied . Suspension dates/activation dates are used Output quality instead of ValidFrom/ValidTo or in some cases dates are not being used at all. As the output will differ if there are more than one document id's.
High
ETL
11 Portal -> ETL
ETL
12 Error Handling
ETL
13 Taxonomy
ETL
14 Database
Split Portal specific rules from the core components Streamlining the Exception handling and logging mechanism for better supportability, for all the workflows > Send workflow and session logs to technical support team Rule clean-up. Verify the taxonomy rules against the implementation. Database Tuning Partitioning > review / adjust GFIS partitions > implement partitioning for message tables redesign HDR/ASN tables > create subpartition for stage in TMP table
ETL ETL
Streamlining the data interaction with intercomponents. Move the current workflow components into Mapplet to avoid the source qualifier and target update for each compoent. This lead into lot of database operations now. SAP interface failure error handling > Implement timeout control, state monitoring, persistant logging Source File hard error handling
Standardization, Transparency on Issues Standardization
Critical Critical Critical
> Targeted processing requirement > Targeted processing requirement > Targeted processing requirement
HCLT / FFT Team HCLT / FFT Team
This will reduce the full table scan.
HCLT / FFT Team HCLT / FFT Team
> Easy to add new changes.
Flexibility for Rollins High
KT Team
> Upto date taxonomy document.
Performance Tuning High
FFT Team /Kavya/AAK
> Performance
High
Flexibility for Rollins High Flexibility for Rollins High
Data anomolies can be fixed at the early stage
> Easy to maintain the new changes and technical debug issues.
ETL
15 Database
Database Cleanup > review inventory of tables, views, etc. drop unused objects > remove unused entries from setup tables
High
FFT Team /Kavya/AAK
> Removal of unwanted database objects.
ETL
16 Database 17 Informatica Server
FFT Team /Kavya/AAK HCLT / FFT Team
> Performance
ETL
Database Tuning Partitioning Performance Tuning High > create new views for GFIS lookup Standardization High Informatica Server Tuning >optimize cache file sizes (dependent on runtime stats) > "setup runtime statistics capturing processidentify top resource consumers," > optimize reusable components / consolidate in a specific folder
ETL
18 Informatica Server
Neboja
> Performance
ETL
19 Purge temp data
ETL
20 ETL1
Standardization Informatica Server Tuning > "revisit parameterization- review/optimize parameter files- introduce parameter table for Infa" Storage Automate the Purging of the temp data after 2 days CR 467: Risk of ACS duplicate files being posted
ETL
21 ETL1
ETL
22 ETL1
ETL
23 Portal -> ETL -> SAP
ETL
24 Portal -> ETL
SAP Document ID - Ack from SAP on successful Standardization posting Capture reference data error message Standardization
ETL
25 Reference data
Incremental RDM Data synchronization
Scalability
Medium
ETL
26 RTB Support
Reengineer the ETL code delivery process
Standardization
Medium
ETL
27 RTB Support
Support utilities -- Joseph will discuss
Support Tools
Medium
ETL
28 RTB Support
Medium
ETL
29 Workaround 30 Archving
Medium HCLT / FFT Team Medium HCLT / FFT Team
Flexibility for Rollins
ETL
Fit the FSR Framework processes into dbFeeds Support Tools RTB dashboard tool. Standardization RFP TLR Hard coding values col 7,8 for workaround. Final stage data is what required to be Scalablility archived, instead os multi stage data, which will reduce the table segment running out of space.
Off-Balance Sheet derivation Fixes
High
Missing Functionality build Crtical for June Month-End
On-going Devt (to be completed by 11th June) ETL 31 Missing Build Planned for 2008
Standardization
CR 467: RFP derivation for parent-child not wrking as expected CR 467: RDM refresh during feed file processing
Functionality
High
High
Kavya/AAK/B alaji High HCLT Team/Balaji High HCLT Team/Balaji High HCLT Team/Balaji Medium HCLT / FFT Team Medium HCLT / FFT Team
> Performance
> Performance > Production issue closure > Production issue closure > Production issue closure
> Transparency on the SAP process status in Portal screen > These error messages should be shown currently sent only to support users. By this enhancement ETL will sent this message to Portal. User have access to these error messages in one place. HCLT / FFT Latest refrence data availabilty for derivation and Team validation. Kavya/AAK/B Improve Quality alaji HCLT / FFT Easy to review the issue / support production env. Team Sathish Overall Feed reporting
FFT Team / HCLT
Scalability of several locations without affecting the platform
ETL
32 Hardware capability
Dedicated Server for FSR processes
Scalability
Joseph
Dependency > Approval of new field additions to the GFIS standard will be more useful do this excise once, rather than repeating every time.
> Need input from Finance on this.
> Portal have to accept this change and display. > Portal have to accept these messages.
Based on Reference data timing requirement
Task ID
Task Breakup
Effort (man-days)
Assign to Status
Stress Testing (current Design)
2 BJ
Stress Testing (with new Design)
3 Vimal
1 1 1 1 1 2 2 2
Completed
Planned Start Dt
Planned End Dt
Actual Start Dt
Actual End Dt
To improve the performance in ETL1 and 2 Major Tasks 1st level
Add more views for SAP and GFIS reference tables
Prepare statis flows like the portal 2nd level > Still the individual components will have different workflows
3rd level
Streamlining the data interaction with inter-components. Move the current workflow components into Mapplet to avoid the source qualifier and target update for each compoent. This lead into lot of database operations now.
Impact No impact. But once the all the locations are implemented the view willl have more records. This will improve the performance 10 to 15 %. But Flexibility of including compoents dynamically through database setup is not possible. Note Anyway in PROD env dynamic workflow changes is not a must requirement. This will improve the performance min 50 %. But Flexibility of including compoents dynamically through database setup is not possible. > More effort involved.
Current Targeted Interface Volume SLA Timing Timing Portal (end to end for validation / posting) 2 5 min 7 to 8 min 4 min SAC / Manual Adjustment 1000 10,000 3 x 10,000 2 3 min 7 to 8 min 2 min FLA / NFI 1000 10,000 3 x 10,000 Portal (end to end - etl validation / r3 posting / bw update / data availability for report ) After portal approval and submit, ETL1 : 5 mins R3 Posting : 2 mins R3 to BW Transfer : 15 mins (currently scheduled for eve ry 10/15 mins) BW Report cube refersh time : 5 min Note : Data availability for Report end to end 30 min should be possible, if no master bwkey data changes. 2 30 min 7 to 8 min 4 min SAC / Manual Adjustment 1000 10,000 3 x 10,000 Source to GFIS (interface processing) 1000 na 25 min CPY 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min CON 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min INS / INX 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min DDM / DDM-A / DDM-M 10,000 na 35 min 100,000 na na 3 x 100,000 na na 1000 na 25 min DBP 10,000 na 35 min 100,000 na na 3 x 100,000 na na ETL Layer 1 1000 15 min 25 min 15 min All interfaces 10,000 20 min 35 min 20 min 100,000 30 min na 30 min 3 x 100,000 45 min na 45 min ETL Layer 2 1000 20 min 25 min 15 min Including RFP derivation 10,000 25 min 35 min 20 min 100,000 30 min na 30 min 3 x 100,000 45 min na 45 min
Remarks 10 sec for sftp
ability for report )
f no master bwkey data changes. 10 sec for sftp
No of RML rules: 90,000 records PK table : 28,000 records
Interface Portal (end to end for validation / posting) SAC / Manual Adjustment
Volume
SLA
Current Timing
2 5 min 7 to 8 min 1000 10,000 3 x 10,000 2 3 min 7 to 8 min FLA / NFI 1000 10,000 3 x 10,000 Portal (end to end - etl validation / r3 posting / bw update / data availability for report ) After portal approval and submit, ETL1 : 5 mins R3 Posting : 2 mins R3 to BW Transfer : 15 mins (currently scheduled for eve ry 10/15 mins) BW Report cube refersh time : 5 min Note : Data availability for Report end to end 30 min should be possible, if no 2 30 min SAC / Manual Adjustment 1000 10,000 3 x 10,000 Source to GFIS (interface processing) 1000 na CPY EP 10,000 na 100,000 na 3 x 100,000 na 1000 na IDMS 10,000 na 100,000 na 3 x 100,000 na 1000 na ACS 10,000 na 100,000 na 3 x 100,000 na 1000 na CON EP 10,000 na 100,000 na 3 x 100,000 na 1000 na IDMS 10,000 na 100,000 na 3 x 100,000 na 1000 na SUMMIT 10,000 na 100,000 na 3 x 100,000 na 1000 na RMS 10,000 na 100,000 na 3 x 100,000 na 1000 na ACS 10,000 na 100,000 na 3 x 100,000 na 1000 na INS / INX EP
7 to 8 min
25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min
INS / INX
EP 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000 1000 10,000 100,000 3 x 100,000
na na na na na na na na na na na na na na na na na na na na na na na na na na na na na na na
35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na 25 min 35 min na na
All interfaces
1000 10,000 100,000 3 x 100,000
15 min 20 min 30 min 45 min
25 min 35 min na na
Including RFP derivation
1000 10,000 100,000 3 x 100,000
20 min 25 min 30 min 45 min
25 min 35 min na na
ACS
DDM / DDM-A / DDM-M
EP
IDMS
ACS
DBP
EP
ACS
IDMS
ETL Layer 1
ETL Layer 2
Targeted Timing
Remarks
4 min 10 sec for sftp
2 min
y for report )
4 min 10 sec for sftp
3 min EP-636 records
2 min 44 sec 2772 records
2 min 51sec 348 records
2 min 17sec 5 records
2min 22 sec 3232 records
4 min 18 sec 568 Records
2 min 11 sec 53 records
2 min 53 sec 3616 records
5 min 3 sec 27564 records
1 min 0 records
2 min 35 sec 284 records
4 min 14684 records
5 min 20sec 8006 records
2 min 1 sec 267 records
1 min 4 records
2 min 33 sec
15 min 20 min 30 min 45 min 15 min No of RML rules: 90,000 records 20 min PK table : 28,000 records 30 min 45 min
WORKFLOW_NAME START_TIME END_TIME Duration wf_Start_WF_ETL_2_1 5/21/2007 5:27 5/21/2007 6:03 0:35 wf_Start_WF_ETL_2_1 5/21/2007 21:00 5/21/2007 21:55 0:55 wf_Start_WF_ETL_2_1 5/22/2007 6:25 5/22/2007 7:34 1:09 wf_Start_WF_ETL_2_1 5/22/2007 8:23 5/22/2007 9:37 1:14 wf_Start_WF_ETL_2_1 5/23/2007 3:34 5/23/2007 4:55 1:20 wf_Start_WF_ETL_2_1 5/24/2007 3:33 5/24/2007 5:02 1:28 wf_Start_WF_ETL_2_1 5/24/2007 20:30 5/24/2007 21:47 1:17 wf_Start_WF_ETL_2_2 5/25/2007 4:02 5/25/2007 4:44 0:42 wf_Start_WF_ETL_2_3 5/25/2007 6:00 5/25/2007 6:38 0:38 wf_Start_WF_ETL_2_4 5/25/2007 8:00 5/25/2007 8:45 0:45 wf_Start_WF_ETL_2_1 5/25/2007 20:30 5/25/2007 21:12 0:41 wf_Start_WF_ETL_2_2 5/26/2007 3:15 5/26/2007 4:01 0:46 wf_Start_WF_ETL_2_3 5/26/2007 6:00 5/26/2007 6:37 0:37 wf_Start_WF_ETL_2_4 5/26/2007 8:00 5/26/2007 8:39 0:39 wf_Start_WF_ETL_2_1 5/26/2007 20:30 5/26/2007 21:06 0:36 wf_Start_WF_ETL_2_2 5/27/2007 3:15 5/27/2007 4:37 1:22 wf_Start_WF_ETL_2_3 5/27/2007 6:00 5/27/2007 6:34 0:34 wf_Start_WF_ETL_2_4 5/27/2007 8:00 5/27/2007 8:33 0:33 wf_Start_WF_ETL_2_1 5/27/2007 20:30 5/27/2007 21:04 0:34 wf_Start_WF_ETL_2_2 5/28/2007 3:15 5/28/2007 3:49 0:34 wf_Start_WF_ETL_2_3 5/28/2007 6:00 5/28/2007 6:37 0:37 wf_Start_WF_ETL_2_4 5/28/2007 8:00 5/28/2007 8:50 0:50 wf_Start_WF_ETL_2_1 5/28/2007 20:30 5/28/2007 21:08 0:37 wf_Start_WF_ETL_2_2 5/29/2007 3:59 5/29/2007 4:42 0:43 wf_Start_WF_ETL_2_3 5/29/2007 6:00 5/29/2007 6:43 0:42 wf_Start_WF_ETL_2_4 5/29/2007 8:00 5/29/2007 8:42 0:42 wf_Start_WF_ETL_2_1 5/29/2007 20:30 5/29/2007 21:17 0:47 wf_Start_WF_ETL_2_1 5/30/2007 20:30 5/30/2007 21:06 0:36 wf_Start_WF_ETL_2_2 5/31/2007 3:15 5/31/2007 3:56 0:40 wf_Start_WF_ETL_2_3 5/31/2007 6:00 5/31/2007 6:30 0:30 wf_Start_WF_ETL_2_4 5/31/2007 8:00 5/31/2007 8:40 0:40 wf_Start_WF_ETL_2_1 5/31/2007 20:30 5/31/2007 21:02 0:31
Related Documents
Remediation_v1 To Be Done
November 2019 14
What Is To Be Done
June 2020 5
Be Be To
June 2020 25
Done
November 2019 44
To Be
May 2020 24