Hi Everyone,
There is some healthy discussion at work currently on how we go about efficiently meeting our current legacy interface based processing whilst re-platforming in SAP technologies (using Public Sector Social services CRM/ERP/PSCD/PO/BRF+ etc).
It is expected that a number of our existing external interfaces cannot change within the timeframe for our initial SAP system deliverable. These interfaces are based on large daily files (containing up to tens of thousands of transactions each) traditionally received & processed, or generated & sent by our legacy system overnight outside of our 9AM-5PM business-facing application window.
Also the processing of the transactions in these files (3rd party customer information, re-assessments for benefits, payments, letter processing etc) can be quite complex requiring many data accesses/validations/calculations to cater for retrospective calculations and flow on affects to changes to related Business partners etc. There is also a high level of dependencies on these legacy batch processes based on a sequential style pattern of execution (i.e. batch 1 runs & complete, then batch 2 runs and completes, then batch 3 etc).
So the question is how have other organisations in similar situations tackled this problem but still performed? What sort of tips, techniques, technologies could help stand up, what problems should we aware of? We know about SAP HANA already and hope to use it to help with tuning data accesses.
Sorry its a bit of an open-ended question and we are only recently newcomers to all things SAP so open to any suggestions.
cheers
Gary