.png)
CCH Tagetik Integration Guide
Integrate CCH Tagetik with enterprise applications through REST APIs, documented SOAP services, file-based processes, and scheduled financial data workflows.
CCH Tagetik integration options at a glance
CCH Tagetik provides REST API and web-service capabilities for accessing platform functionality and data, although available resources depend on the release, modules, and configuration. SOAP services may be available for deployments that provide suitable WSDLs. File-based imports and exports, data-management processes, batch execution, and scheduled synchronization are important patterns for financial data. Authentication is tenant-specific and may use administrator-issued credentials, sessions, tokens, or enterprise identity integration. Martini can consume documented endpoints, exchange and validate structured files, map dimensions, orchestrate long-running processes, expose controlled APIs, and apply reconciliation, retry, and error-handling logic.
| Integration point | Supported by CCH Tagetik? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Access documented CCH Tagetik functionality and data, including configured financial and planning processes. Available resources and operations depend on release, licensed modules, and tenant configuration. | Martini can consume documented REST endpoints, transform responses, apply validation and business rules, and expose controlled APIs to downstream systems. |
| SOAP APIs | Limited | Use historically available CCH Tagetik web services where the deployment provides supported SOAP operations and WSDL definitions. | Martini can consume documented SOAP services, generate or map XML payloads, and handle SOAP-specific errors and retries. |
| Bulk, async, and batch processing | Limited | Load large financial datasets through configured data-management, import, export, or batch processes. A uniform public bulk API and job model are not confirmed. | Martini can partition loads, retain process identifiers where exposed, poll status with bounded retries, and reconcile completion results. |
| File import and export | Limited | Exchange CSV, delimited text, or XML files through configured CCH Tagetik import and export processes. Layouts, headers, and conventions are implementation-specific. | Martini can retrieve or deliver files, parse and validate content, map dimensions, and invoke the relevant documented process. |
| Webhooks and outbound callbacks | Not confirmed | A general-purpose webhook framework covering changes to CCH Tagetik business objects was not verified. Scheduled extraction, files, or configured process notifications may be needed. | Martini can use scheduled triggers or other confirmed endpoints instead of assuming event delivery; it can receive callbacks only when the customer provides a supported callback source. |
| Authentication | Limited | CCH Tagetik environments use controlled authentication and authorization, but a universal OAuth 2.0, API-key, or JWT scheme was not confirmed. | Martini can store tenant-specific credentials, sessions, or tokens in environment-specific secrets and apply the confirmed authentication configuration. |
| Database access | Not confirmed | Direct access to the underlying CCH Tagetik database is implementation-specific and should not be assumed for application integration. | Martini should use documented APIs, web services, data-management processes, and files unless a supported database or reporting interface is explicitly approved. |
| Scheduled synchronization | Yes | Run recurring actuals loads, planning exports, master-data synchronization, and process-status checks when real-time events are unavailable or unsuitable. | Martini can schedule workflows, manage extraction windows and watermarks, orchestrate dependent steps, and record operational outcomes. |
How CCH Tagetik exposes data and business events
CCH Tagetik REST APIs
CCH Tagetik provides REST API and web-service capabilities for interacting with platform functionality and data. The exact resources, operations, and authentication requirements depend on the release, licensed modules, and customer configuration.
Martini implementation pattern
Martini implementation pattern: Martini authenticates using the tenant-approved method, calls documented CCH Tagetik endpoints from a workflow, validates the response, maps dimensions and financial values, and sends results to a target system or a controlled Martini API.
Implementation sequence
CCH Tagetik SOAP and web services
CCH Tagetik has historically provided web-service integration capabilities. SOAP operations and WSDL availability should be confirmed for the target deployment rather than assumed to be the preferred interface.
Martini implementation pattern
Martini implementation pattern: Martini consumes the confirmed WSDL or SOAP operation, constructs XML requests, handles namespaces and service faults, transforms XML responses into the target model, and applies bounded retry and exception routing.
Implementation sequence
CCH Tagetik batch and import processes
Configured data-management, import, export, and batch processes are important for large financial transfers. A consistent public bulk API and asynchronous job model were not verified across deployments.
Martini implementation pattern
Martini implementation pattern: Martini prepares a validated, partitioned file or API submission, invokes the documented process, retains any returned identifier, polls status where supported, and records reconciliation details without repeating a completed load.
Implementation sequence
CCH Tagetik file imports and exports
CCH Tagetik integrations commonly use CSV, delimited text, or XML files for configured import and export processes. Exact layouts, headers, decimal conventions, and process names are implementation-specific.
Martini implementation pattern
Martini implementation pattern: Martini retrieves or delivers files through the approved file endpoint, parses and validates the structure, maps dimensional codes, invokes the relevant CCH Tagetik process, and preserves rejected-row and reconciliation information.
Implementation sequence
CCH Tagetik scheduled synchronization
A general-purpose outbound webhook or event stream was not verified, so recurring workflows are a practical method for extracting changed data, loading financial batches, and checking process status.
Martini implementation pattern
Martini implementation pattern: a scheduler starts the workflow, which uses a watermark, period, category, entity, or export window to retrieve data, applies mappings and rules, writes the target result, and advances the checkpoint only after successful reconciliation.
Implementation sequence
Common CCH Tagetik integration patterns
Pattern 1: Load ERP actuals into CCH Tagetik
When to use this pattern
Use this pattern for recurring general-ledger and journal loads supporting financial close, consolidation, and reporting. It is appropriate when the source ERP provides balances, dimensions, and batch identifiers and CCH Tagetik exposes a documented API or import process.
Integration direction
Example Mapping
| CCH Tagetik Field | Canonical Field | Target Field |
|---|---|---|
| CompanyCode | entityCode | Entity |
| GLAccount | accountCode | Account |
| FiscalPeriod | periodCode | Time |
| LedgerAmount | amount | Journal or data package |
Martini implementation pattern
A scheduled workflow retrieves the ERP batch, maps accounts, entities, periods, currencies, flows, and signs, validates required members and totals, and submits a documented CCH Tagetik API request or import. Martini stores the source batch ID and process status, prevents duplicate submission, retries transient failures, and routes rejected rows for review.
Martini capabilities used
- workflows
- scheduled triggers
- API consumption
- file processing
- data mapping
- business rules
- error handling
- monitoring
Pattern 2: Distribute approved planning results
When to use this pattern
Use this pattern when approved budgets, forecasts, or scenarios must be distributed to reporting, data-warehouse, or operational applications after CCH Tagetik processing completes.
Integration direction
Example Mapping
| CCH Tagetik Field | Canonical Field | Target Field |
|---|---|---|
| Scenario | planningScenario | Scenario |
| Category | planCategory | Category |
| Entity | entityCode | Entity or organization code |
| Value | measureValue | planningValue |
Martini implementation pattern
Martini retrieves the approved Scenario and Category for the required periods, applies currency and fiscal-calendar transformations, filters the approved scope, and writes the result to the target data model. The workflow records extraction watermarks, validates row counts and totals, and retries delivery without reprocessing a completed export.
Martini capabilities used
- workflows
- API consumption
- data mapping
- transformations
- business rules
- reconciliation
- error handling
Pattern 3: Synchronize CCH Tagetik master data
When to use this pattern
Use this pattern to align Entities, Accounts, Currencies, Categories, Scenarios, and user-defined dimensions with an ERP, master-data platform, or warehouse.
Integration direction
Example Mapping
| CCH Tagetik Field | Canonical Field | Target Field |
|---|---|---|
| EntityCode | memberCode | Entity |
| ParentAccount | parentMemberCode | Account hierarchy |
| CurrencyCode | currencyCode | Currency |
| EffectiveFrom | effectiveDate | member validity |
Martini implementation pattern
A workflow extracts approved master-data changes, validates stable member codes and parent-child relationships, maps environment-specific values, and submits only permitted additions, updates, or deactivations. Martini quarantines invalid hierarchy changes, records the source version, and supports controlled replay after correction.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- validation
- business rules
- environment configuration
- error handling
Pattern 4: Orchestrate financial close processes
When to use this pattern
Use this pattern when close activities require coordinated extraction, import, validation, status checks, exception routing, and notifications across several systems.
Integration direction
Example Mapping
| CCH Tagetik Field | Canonical Field | Target Field |
|---|---|---|
| SourceBatchId | closeBatchId | CCH Tagetik process identifier |
| ProcessStatus | processingStatus | close task status |
| RejectedRows | exceptionCount | exception task |
| ReconciliationTotal | controlTotal | close evidence |
Martini implementation pattern
Martini coordinates dependent workflow steps, submits the CCH Tagetik import or validation process, polls a supported status endpoint when available, and routes timeouts or failures to an exception process. It retains audit metadata, avoids duplicate submissions, and can expose status through a controlled API or deliver it to an operational application.
Martini capabilities used
- workflow orchestration
- conditional routing
- API consumption
- scheduling
- polling
- business rules
- error handling
- audit logging
Applications commonly integrated with CCH Tagetik
CCH Tagetik commonly participates in enterprise finance, planning, reporting, and master-data architectures. The following applications represent practical integration targets; the patterns should be validated against the customer’s modules, data model, and approved interfaces.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Load general-ledger balances, company codes, cost centers, and master data for consolidation, planning, and reporting. | SAP S/4HANA → Martini → CCH Tagetik | A scheduled Martini workflow retrieves financial data, maps company codes and dimensions to CCH Tagetik members, validates periods and totals, and submits an API request or import file with durable batch tracking. |
| Oracle Fusion Cloud ERP | Synchronize ledgers, accounts, legal entities, and financial actuals with the CCH Tagetik CPM model. | Oracle Fusion Cloud ERP → Martini → CCH Tagetik | Martini consumes approved Oracle data, applies account, entity, currency, and fiscal-period mappings, partitions the load where required, and routes rejected rows to an exception workflow. |
| Microsoft Dynamics 365 Finance | Transfer financial balances, dimensions, budgets, and organizational structures into CCH Tagetik. | Microsoft Dynamics 365 Finance → Martini → CCH Tagetik | A scheduled workflow retrieves source batches, validates dimensional membership and sign conventions, transforms the payload or file, and records CCH Tagetik process status and reconciliation results. |
| Workday | Combine workforce, organization, and cost-center data with planning and workforce-cost models. | Workday → Martini → CCH Tagetik | Martini retrieves approved organizational and workforce data, maps effective dates and cost centers, validates required members, and loads the resulting structure or planning inputs through the supported CCH Tagetik process. |
| Salesforce | Use bookings, pipeline, revenue, and customer information in forecasting or management reporting. | Salesforce → Martini → CCH Tagetik | Martini extracts selected Salesforce data on a schedule, normalizes fiscal periods and commercial dimensions, applies inclusion rules, and delivers an auditable forecast input or reporting dataset to CCH Tagetik. |
| ServiceNow | Incorporate IT spend, project, asset, or operational cost information into planning and performance reporting. | ServiceNow → Martini → CCH Tagetik | A Martini workflow retrieves approved ServiceNow cost information, maps organizational and category values, validates completeness, and submits a controlled import or API request to CCH Tagetik. |
| Snowflake | Consolidate analytical, operational, or historical data for reporting and planning processes. | Snowflake → Martini → CCH Tagetik | Martini coordinates extracts between Snowflake and CCH Tagetik, applies dimensional and period mappings, partitions large transfers, and records row counts and reconciliation totals. |
| Microsoft Power BI | Publish CCH Tagetik planning, consolidation, and reporting outputs for broader analytical consumption. | CCH Tagetik → Martini → Microsoft Power BI | Martini retrieves approved CCH Tagetik results, transforms them into the reporting model, applies scenario and currency filters, and delivers data to the approved reporting or data-platform interface. |
How to build a CCH Tagetik integration in Martini
Objective
Confirm the CCH Tagetik release, modules, endpoints, supported processes, and tenant-specific authentication method before building the workflow.
Instructions in Martini
- Use the approved HTTPS endpoint, credentials, session, or token method.
- Store credentials, tokens, and environment-specific URLs in Martini secrets or configuration.
- Request least-privilege CCH Tagetik roles for the required applications, models, processes, and data views.
- Document whether the integration uses REST, SOAP, files, or a configured batch process.
Objective
Select a trigger that matches the confirmed CCH Tagetik capability and required freshness of the data.
Instructions in Martini
- Use a scheduler for recurring extracts, imports, and process-status checks.
- Use a source-system API or approved file arrival as the trigger for inbound financial batches.
- Do not assume that CCH Tagetik object changes generate webhooks.
- Partition schedules by period, entity, scenario, or another supported scope when appropriate.
Objective
Acquire CCH Tagetik data or source-system data using a documented endpoint, export, or file process.
Instructions in Martini
- Apply confirmed filters, extraction windows, or watermarks.
- Handle pagination or process-generated files according to the specific interface.
- Retain source batch IDs, CCH Tagetik process IDs, and extraction timestamps.
- Treat long-running operations as asynchronous when the deployment exposes status information.
Objective
Coordinate calls, file handling, validation, process submission, status checks, and dependent target operations in one maintainable workflow.
Instructions in Martini
- Separate retrieval, transformation, submission, reconciliation, and exception branches.
- Use conditional routing for process status, missing members, rejected rows, and partial failures.
- Use bounded polling and retries for long-running or transient operations.
- Persist checkpoints only after the intended step succeeds.
Objective
Translate source financial structures into CCH Tagetik dimensions and target-system models without losing financial context.
Instructions in Martini
- Map Entity, Account, Category, Time, Scenario, Currency, Flow, and user-defined dimensions.
- Normalize fiscal calendars, decimal precision, sign conventions, and currency codes.
- Validate required members, parent-child relationships, and permitted combinations.
- Version crosswalks when development, test, and production codes differ.
Objective
Apply financial business rules and duplicate-prevention controls before writing data or advancing a checkpoint.
Instructions in Martini
- Validate period, entity, scenario, category, and account scope.
- Track deterministic batch identifiers and load-status keys.
- Compare row counts and debit, credit, or other applicable control totals.
- Quarantine invalid rows and route them to an exception workflow.
Common CCH Tagetik data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Entity | Represents legal entities, subsidiaries, business units, or reporting units used in consolidation and planning. | ERP, master-data platforms, data warehouses, reporting platforms | Martini maps entity codes and hierarchies, validates parent-child relationships, and synchronizes changes through documented APIs or import processes. |
| Account | Represents chart-of-accounts members used for financial and management reporting. | ERP, data warehouses, reporting and planning systems | Martini applies account crosswalks, validates required members and sign conventions, and includes account values in controlled financial loads. |
| Category | Identifies data classifications such as actual, budget, forecast, or plan. | ERP, planning applications, reporting platforms | Martini maps source classifications to configured Category members and applies business rules for permitted load and reporting combinations. |
| Time | Represents fiscal years, periods, quarters, and other time members. | ERP, data warehouses, planning and reporting systems | Martini converts source calendars to the CCH Tagetik fiscal model and validates period availability before submitting data. |
| Scenario | Represents planning, forecasting, or alternative-analysis scenarios. | Planning applications, reporting platforms, data warehouses | Martini selects and maps Scenario values, applies scenario-specific routing rules, and prevents accidental writes to the wrong planning context. |
| Currency | Represents local, transaction, reporting, or consolidation currencies. | ERP, treasury systems, reporting and planning platforms | Martini maps currency codes, validates conversion conventions, and preserves currency context during extraction and loading. |
Authentication and security considerations
Tenant-specific authentication
CCH Tagetik authentication options depend on the release, deployment model, and tenant configuration. Public research did not confirm a universal OAuth 2.0, API-key, or JWT scheme, so the customer should verify whether the environment uses administrator-issued credentials, sessions, tokens, or enterprise identity integration.
Secure workflow configuration
- Store credentials, sessions, tokens, and endpoints in Martini secrets or environment configuration.
- Use TLS and least-privilege CCH Tagetik roles for APIs, applications, models, data views, and import processes.
- Separate credentials across development, test, and production environments.
- Avoid logging financial payloads and authentication material.
Operational considerations for CCH Tagetik integrations
Process limits and long-running work
Confirm request limits, payload sizes, timeout behavior, concurrent-processing restrictions, and the handling of long-running imports, validations, calculations, and consolidations. Where status identifiers are available, Martini should poll with bounded retries.
Pagination and extraction
Do not assume a common pagination model across CCH Tagetik endpoints. Verify page, offset, continuation-token, filter, or export behavior and use controlled period, entity, category, or scenario partitions when incremental extraction is unavailable.
Idempotency and reconciliation
Track source batch IDs, CCH Tagetik process IDs, scope, timestamps, status, row counts, and financial control totals. A retry must not duplicate journals or reload a completed batch without an explicit replacement strategy.
Configuration change
CCH Tagetik models are configurable. New dimensions, changed member codes, altered hierarchies, and modified import layouts require schema validation, contract testing, controlled deployment, and monitoring for missing required members.
Why use Martini instead of scripts or point-to-point integrations?
Reusable orchestration
Martini separates endpoint access from workflow orchestration, mapping, validation, reconciliation, and exception handling. This makes recurring financial integrations easier to maintain than isolated scripts.
Controlled integration layer
Martini can consume CCH Tagetik APIs and files while exposing controlled APIs to downstream applications. Common authentication, environment configuration, business rules, and error paths can be reused across integrations.
Operational reliability
Scheduled execution, bounded retries, process polling, checkpoints, durable identifiers, and workflow logs provide a more consistent operating model for batch and long-running financial processes than point-to-point code.
Adaptable data transformation
Configurable mappings and transformations accommodate account, entity, currency, fiscal-period, scenario, category, flow, and user-defined-dimension differences without requiring every target system to implement CCH Tagetik-specific logic.
Frequently asked questions
CCH Tagetik can be integrated through its documented REST APIs, supported web services, configured data-management and import/export processes, structured files, and scheduled batch workflows. The appropriate mechanism depends on the release, licensed modules, deployment configuration, and required data volume.
Yes. Martini can integrate with CCH Tagetik by consuming documented REST APIs, using supported SOAP services where available, exchanging configured import and export files, and orchestrating scheduled workflows for financial data, planning results, master data, and process status.
No. A dedicated CCH Tagetik connector is not required. Martini can use CCH Tagetik’s confirmed native integration mechanisms, including REST APIs, documented SOAP services, file-based processes, batch operations, and tenant-specific authentication.
Lonti does not charge an additional per-connector or per-vendor fee to integrate CCH Tagetik. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from CCH Tagetik, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Documented REST APIs are the primary option where the required resources are available. Configured import, export, data-management, and batch processes are important for larger financial loads. SOAP should be used only where the target deployment provides a supported service and WSDL, while direct database access should not be assumed.
A general-purpose webhook framework or outbound event stream covering CCH Tagetik business objects was not confirmed. Integrations should generally use scheduled extraction, file exports, configured workflow or batch processes, or customer-provided middleware and messaging infrastructure instead of assuming callbacks for every change.
Martini can use schedules, extraction windows, process identifiers, or approved watermarks to retrieve data and prevent uncontrolled reprocessing. Workflows map Entity, Account, Category, Time, Scenario, Currency, Flow, and user-defined dimensions, then apply fiscal-calendar, sign, precision, hierarchy, and reconciliation rules before delivery.
Martini can validate payloads, apply bounded retries for transient failures, poll supported long-running processes, and route rejected rows or timeouts to exception workflows. Durable source batch IDs, process identifiers, scope keys, and reconciliation totals help determine whether a retry is safe and prevent duplicate financial submissions.
Yes. Martini can expose controlled REST APIs that standardize access to CCH Tagetik data or orchestrate CCH Tagetik processes behind a separate integration endpoint. This can provide consistent validation, authorization, transformation, and error handling for downstream applications.
Related Martini documentation
API integration
Workflows
Data processing
Connect CCH Tagetik with your enterprise systems
Use Martini to build maintainable CCH Tagetik integrations across APIs, SOAP services, files, batch processes, and scheduled financial workflows.