ATC-India-Billing

Mule Runtime Version : 4.1.5
Project Detail: The primary intent of the flows is to move the Billing data needed for Asset, Tenant, 
Site, HoldExit, EBConsumption, DGConsumption, ActualDCLoad, Outage, EBDGrates object from Tarantula to 
OBRM. Tarantula is a sql database and OBRM is an Oracle db. Tarantula generates a monthly snapshot of the 
data and Mulesoft is responsible for moving that data to OBRM based on the mapping provided. To facilitate 
the monthly data move, as well as any ad hoc batch processing (special cases of data move), the integration 
has a job that runs every 3 hours and checks the : ‘O_OPAInterface_BatchHeader’ table in tarantula for any 
new batch that have the ‘Status’ as ‘Completed’ and ‘SyncStatus’ as null. Once a batch is selected for 
processing, Mulesoft updates the ‘SyncStatus’ to ‘Processing’ and work on the updates as per the mapping 
provided. Once the batch is processed, Mulesoft comes back and update the ‘SyncStatus’ to ‘Complete’ 
indicating that the batch is processed and no further action remains for that.