Data and document structures

Data and document structure configuration defines what the system processes and how order data is organized. By configuring document structures and relationships, you establish a consistent data model that supports workflows, decisions, and execution logic across order processing. A well‑defined document structure makes order processing predictable, extensible, and easier to maintain as business requirements change.

Overview

Data and document structure configuration provides the foundation for all order management behavior. It defines the document types that flow through the system, the attributes they contain, and the relationships that connect related documents. Process models, conditions, transactions, and services all rely on these definitions.

This configuration separates data modeling from process logic, allowing workflows and execution behavior to change without restructuring core document definitions.

Base document types

Base document types define the core structure and behavior for a category of documents. They establish common attributes and processing rules that apply across similar document types.

For example, a base document type for orders defines standard elements that all order documents share. Other document types can build on this foundation without redefining the common structure.

Base document types promote consistency and reuse across the system.

The following base document types are defined in IBM Sterling® Order Management System.
  • Order
  • Load
  • General
  • Count
  • Container
  • Wave
  • Work Order
  • Opportunity

Document types

Document types extend base document types to represent specific business scenarios. They inherit structure and behavior from the base type and can add or override attributes as needed.

Document types are used throughout process modeling to control how documents are processed, evaluated, and transformed. They also determine which workflows, conditions, and services apply during order processing.

The following document types are defined in Sterling™ Order Management System.
  • Sales Order
  • Planned Order
  • Return Order
  • Template Order
  • Purchase Order
  • Transfer Order
  • Master Order
  • Contract Order
  • Quote
  • Load
  • General
  • Count
  • Container
  • Outbound Picking
  • Work Order

Document relationships and hierarchy

Document relationships define how documents are connected to one another. Hierarchies describe parent‑child relationships, such as orders and related fulfillment, return, or invoice documents.

These relationships provide the following capabilities.

  • Enable coordinated processing across related documents.
  • Support lifecycle tracking across dependent documents.
  • Provide context for conditions, transactions, and services.

Clearly defined relationships help maintain consistency as documents move through different stages of processing.

Document attributes and extensions

Document attributes define the data carried by a document. Attributes can represent standard fields or custom data that is required by specific business processes.

Extensions provide a way for you to add attributes without modifying the base structure. This approach supports customization while it preserves compatibility with standard processing.

Well‑designed attributes and extensions make it easier to evaluate conditions, trigger actions, and integrate with external systems.

How this configuration is used

Data and document structures are referenced throughout order management configuration. Multiple configuration areas use these structures in the following ways.

  • Process models to control flow
  • Conditions to evaluate decision logic
  • Transactions to group execution
  • Services to perform business logic

Because of these dependencies, document structure configuration is typically defined early and refined as workflows and logic evolve.