Scheduling and monitoring
Job Scheduling
Brinta extractors are standard ABAP programs and can be executed manually or scheduled for automatic execution. The most common approach is to configure periodic background jobs using the SAP Job Scheduler (transaction SM36).
Typical scheduling parameters:
- Program name: ZCOI_INT_BRINTA_*
- User: System or integration user with authorization for relevant company codes
- Frequency: Daily, weekly, or aligned with tax reporting cycles
- Start condition: Specific time or event-based (for example, after financial closing)
Brinta recommends scheduling each extractor separately to simplify monitoring and reprocessing.
Example scheduling pattern:
| Extractor | Frequency | Typical Run Time |
|---|---|---|
| ZCOI_INT_BRINTA (Invoices) | Daily | End of business day |
| ZCOI_INT_BRINTA_BL (Trial Balance) | Monthly | After period close |
| ZCOI_INT_BRINTA_PC (Chart of Accounts) | On demand | When structural changes occur |
| ZCOI_INT_BRINTA_BP (Business Partners) | Weekly | Maintenance window |
| ZCOI_INT_BRINTA_PRODUCT (Assets) | Monthly | Asset reconciliation cycle |
All extractors can be combined in a single job chain if needed, but running them individually provides more granular error handling.
Execution Logs
Each extractor automatically generates entries in dedicated Brinta Z-tables for audit and traceability. These tables store both successful and failed transmissions, making it possible to monitor or reprocess data directly from SAP.
| Table | Purpose |
|---|---|
ZTBR_LOG_INVOICE | Logs outbound fiscal documents sent to Brinta |
ZTMM_INT_BRINTA | General control of document transmissions |
ZTMM_BRINTA_BL, ZTMM_BRINTA_PC, ZTMM_BRINTA_PROD | Specific control tables for accounting, chart of accounts, and assets |
ZBRINTA_KEY | Stores Brinta authentication token |
ZTMM_BRINT_TYPES | Maps SAP document types to Brinta standards |
Each record includes key fields such as:
- SAP document number
- Company code
- Extraction timestamp
- Transmission status
- API response code or message (if available)
Monitoring and Reprocessing
Developers and key users can review job results through:
- SM37 – background job logs
- SE16N – direct lookup in Z-tables for error analysis
- Brinta Support Portal – optional integration for real-time monitoring (if enabled)
If a record fails due to network interruption or data inconsistency, it can be reprocessed by executing the same extractor again for the affected period or document range. The system will automatically skip successfully processed entries and resend only pending records.
Brinta also supports optional middleware monitoring through SAP CPI dashboards, allowing technical teams to track message delivery and API responses.
Recommended Monitoring Practices
- Schedule email or SAP alert notifications for failed jobs.
- Periodically reconcile Brinta’s processed document count with SAP transmission logs.
- Retain historical log entries for audit purposes according to internal compliance policies.
- Perform a manual extraction test after any SAP transport or configuration update.
For advanced log monitoring setup or CPI message tracking templates, please contact [email protected].
Updated about 8 hours ago