For each customer interface record, a new instance of Workflow main process is kicked off, as below Click to proceed…………

Same customer can be updated very frequently in 3 rd party system. Hence the workflow should be able to manage ongoing duplicates in process.

Additional validation of address using a Workflow SubProcess Workflow notification can be used to update/correct staging tables based on user corrections. This will happen during exceptional circumstances.

3 rd Party System 1 3 rd Party System 2 Flat FileRA_CUST_INTShadow Tables Bespoke Routine is submitted instead Of Std Cust Interface Workflow For each Customer Record, one Workflow Process is Kicked off. This is similar to what happens for PO Approval Loops for each Valid Record in RA_CUST_INT to Submit Workflow Transform and Copy to Staging Table Correct NameCorrect Country Optionally, get response from User when Name/Country not automatically derived Optionally, update Transformed table with Users Notification Response Errors Logged in Error Table And Workflow will be Stuck with Errored Flag Update or Insert TCA API for Creating Customer TCA API for Updating Customer

1.Existing Mechanism to receive the Data remains the same 2.All Customers interfaces will use Common Set of Transformed Staging Table 3.If 9iAS interconnect is used in future, Messages can be Dequeued and transferred to Transformed Staging tables. Same workflow can be used with some modifications. 4.If TCA API returns error, then workflow will error, hence will get picked up in Daily morning Workflow Monitoring Checks. 5.After the data fix has been made or setup is done, Retry workflow process can be run again to ReTry all the stuck workflows. Effectively that will ReSubmit the TCA API step in the workflow. Click to proceed

1.Oracle will DeSupport Customer Interface tables in foreseen future. This approach uses TCA API’s. 2.If we use a Connection Tool in future, this workflow can be ReUsed. 3.Correcting of Names and Country Code Address can be made interactive with the users using Workflow Notifications. 4.ReSubmission of interfaced Customer Data with Incorrect information will be possible via standard Workflow mechanism. 5.We have already developed tools to monitor Stuck workflows on a daily basis. This tool can be used to monitoring API errored Customer Data. Click to proceed Benefits of new Approach