Data model for Archive Service
The following table describes the data model for Archive Service, which stores
data in the osa_order_archive
table.
Column name | Type | Valid values | Description | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
o_id | Text | UUID or OHK of the order | Indicates a single attribute value, which uniquely identifies an order. Sterling Order Management System Software can use either the OrderHeaderKey attribute or a generated
unique value that is used across Order Search and Archive Service as the unique identifier for an order. |
||||||||||||||||||
part_name | Text | Order, orderLine, or orderAudit | Indicates what part of the order data is stored in this row. For example, if Sterling Order Management System Software sends order and order line information of an order separately, they are stored in this table in two rows against part_name=‘order’ and part_name=‘orderLine’. | ||||||||||||||||||
end_seq | Integer | 0 (zero) or a positive number. 0 (zero) for non-repeating and single data. For repeating data, it is the end sequence for that row. |
0 indicates that the data in current row is not part of a list. The end_seq
value for the partname as ‘order’ is always 0 or when an entity that contains 1:1 relationship with
an order, which is stored in a separate row.If This column is needed for
pagination purpose. Pagination is supported for entities and rows that contain
|
||||||||||||||||||
start_seq | Integer | 0 (zero) or a positive number. 0 (zero) for non-repeating and single data. For repeating data, it is the start sequence for that row. |
0 indicates that the data in current row is not part of a list. The
start_seq value for the partname as ‘order’ is always 0 or when an entity contains
1:1 relationship with an order is stored in a separate row.If |
||||||||||||||||||
format | tinyint | [1..5] | Refers to an integer value, which indicates the format in which the data is stored. The
following table describes the format in which the data is stored:
|
||||||||||||||||||
json | Text | JSON data | Stores a valid JSON document. | ||||||||||||||||||
clob | Text | Non-JSON text data | Stores plain text file data such as XML. | ||||||||||||||||||
blob | BLOB | Binary data | Data in binary form. | ||||||||||||||||||
o_dt | Date | yyyy-mm-dd format | Date to track order in Archive Service. |
- Three columns are defined to store data in three different formats, namely JSON, CLOB, and BLOB. One or more of these columns are used to store data. The format value indicates the columns that are used to store and fetch the data.
- Currently, the JSON format is supported for data.