JOB_OMS_CODIGOS_MONEDA_MASTER
| Date | 27/01/2026 |
|---|---|
| Author | Leandro Crespo |
| Version | 1.0 |
Process Definition
It is a batch integration process responsible for synchronizing currency masters. The flow extracts currency information from a source database (SGT) and replicates it in a destination database (OMS), performing insertion or update operations as appropriate.
Scope
The process encompasses the total extraction of currencies via a stored procedure in SGT, the processing of these records in batches, and their subsequent loading into the OWA_TG_Moneda master table of the OMS system.
Inputs
- SGT Database: Execution of stored procedure PA_CON_MONEDAS_3C.
- Environment Variables: Configuration parameters such as BATCH_SIZE for data volume handling.
Outputs
- OMS Database: Insertion or update of records in the OWA_TG_Moneda table.
- Notifications: Sending of a JSON via HTTP POST to a notification service (SMTP) in case of error.
Process Flow in Sensedia
The flow is divided into logical sub-stages:
-
Start: Trigger by scheduler.
-
Preparation: Initialization of control and status variables.
-
Extraction: Query to SGT database via JDBC.
-
Transformation and Loading:
- The list of currencies is divided into batches according to BATCH_SIZE.
- A bulk insertion (INSERT) is attempted.
- If the insertion fails (for example, due to duplicate key), the flow captures the exception and executes an update (UPDATE) for those records.
-
Finalization: Log registration of closure and error management.
Sensedia Configuration
- JDBC Connectors: Requires configured connections named ConexionSGT and ConexionOMS.
- Properties: Configuration of keys such as URL_NOTIFY, SENDER_EMAIL, DESTINATION_EMAIL, and ENVIRONMENT_NAME.
Scheduling and Frequency
- Current configuration: Monday through Friday at 10:30:00 PM
Notifications
- OK: The flow has success notification commented; currently only logs the end of the process.
- NOT OK: A detailed email notification is sent (via API) if an exception occurs in the main block.
- Attachments: No attachments are included (the attachment_id field in the JSON is a static placeholder).
Logs and Monitoring
The following events are logged:
- Start and end of each sub-flow.
- SQL statements generated for SGT and OMS.
- Results of JDBC executions.
- Detail of captured errors (simplified Stacktrace).
- Final payload sent to the notification service.
Logs are accessible through the “Analytics” module of the Sensedia Integrations platform.
Failure Behavior
The flow uses doTry-doCatch blocks. If an error occurs at any critical stage (read or write), the exception is captured, the process status is marked as ERROR, the detail is logged, and the external notification sub-flow is triggered.
Recovery Process
Since the process is a master synchronization based on a scheduler, recovery from connectivity failures is automatic at the next scheduled execution. If the failure is due to data, the “Execution error” log should be reviewed to identify the conflicting record or batch.
Contacts
- Technical Support: Integrations / Middleware Team.
- Process Owner: Business Continuity.
Publishing Checklist
- Validate JDBC connectivity to ConexionSGT and ConexionOMS from production environment.
- Verify that the PA_CON_MONEDAS_3C procedure exists and has execution permissions.
- Configure email environment variables (DESTINATION_EMAIL, etc.) with production accounts.
- Ensure that the notification service URL (URL_NOTIFY) is accessible.
- Validate that BATCH_SIZE is optimal to not saturate runtime memory.
