Scheduled Content Synchronization Across CMS-Linked Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Moving complex data structures across different computer systems is challenging and requires manual intervention, leading to inefficiencies and potential human errors.

Innovation Solution

Automated data movement techniques using scheduling definitions that specify a source, target, and time or event to synchronize content across computer systems, leveraging content management systems to transport content packages efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual intervention is used to move complex data structures across computer systems, then flexibility and control are maintained, but human errors increase and efficiency decreases

Engineering Contradiction:
Improvereduction of human errorVSAvoidautomation of data movement
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system enables self-service automation where the data movement process automatically identifies, packages, and transfers complex data structures between systems without human intervention. The scheduling definition and content management system work autonomously to execute data synchronization tasks, eliminating manual operations and associated human errors.

Inventive Principle:
Principle #25Self-service

2Productivity

If manual processes are used for data synchronization, then resource usage is lower, but productivity and efficiency are reduced

Engineering Contradiction:
Improvecontent distribution efficiencyVSAvoidresource usage
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system implements periodic action through scheduled data synchronization operations. The scheduling definition specifies time-based triggers that automatically initiate data movement at optimal intervals, enabling efficient batch processing that maximizes productivity while managing resource consumption through controlled, periodic execution rather than continuous operation.

Inventive Principle:
Principle #19Periodic action

3Loss of time

If complex data structures are moved manually, then control over the process is maintained, but the process becomes time consuming and error-prone

Engineering Contradiction:
Improvedata preparation and synchronization timeVSAvoidcomplexity of data movement process
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The content management system acts as an intermediary between source and target systems, automatically handling the complex task of moving complex data structures. The scheduling definition serves as a mediator that orchestrates the data movement process, translating high-level synchronization requirements into automated execution steps, thereby reducing both time and operational complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If automated scheduling is implemented, then productivity increases and manual tasks are eliminated, but system complexity increases

Engineering Contradiction:
Improveelimination of manual tasksVSAvoidcomplexity of scheduling system
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system uses copying mechanisms to replicate data structures and scheduling definitions across systems. By creating and managing copies of data packages through automated processes, the system simplifies operations while the underlying complexity is encapsulated within the content management system's copy management infrastructure, hiding complexity from users.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12603934B2Systems and methods for scheduling packages to synchronize content across computer systems
Publication Date: 2026.04.14 SAP SE
  • US12603934B2 patent drawing
  • US12603934B2 patent drawing
  • US12603934B2 patent drawing

AI summary

Embodiments of the present disclosure include techniques for moving data. In one embodiment, a schedule definition is defined on one system and sent to an associated CMS. The schedule definition may include a target, objects or packages, source, and time or event to start the transport of associated content. When the time or event occur, the associated CMS retrieves the content from the backend application server and sends an event to another CMS associated with the target backend application server. The content is transported from the associated CMS to the target backend application automatically. Content may be moved automatically between a plurality of systems to synchronize content across a content network.