The archive table contains a line for every OT document and must be populated via the OT tables. The columns XHDOC and SYSROWID are supplied with a unique ID by means of the database. The following SQL statement can be used to create a sequence of XHDOC:
CREATE SEQUENCE newxhdoc_seq
MINVALUE 1
START WITH 1
INCREMENT BY 1
CACHE 20;
lpad(to_char(newxhdoc_seq.nextval, 'FMXXXXXXXXXXXX'),12,'0') || '00000000000000000000000000000000'
The following SQL statement can be used for the SYSROWID:
UPDATE ?TABLE? SET SYSROWID = SYS_GUID() || '000000000000' WHERE SYSROWID IS NULLThe column SYSINDEXSTATE gets filled with 0. The columns XXUSER, XXLEVEL, XXFLAGS, SYSROWID, SYSACLLIST remain empty. All other columns are populated according to the list below.
| Field Name | Type | Description (OT Field Name) |
|---|---|---|
| XHDOC | VARCHAR2 (45) | |
| XXUSER | VARCHAR2 (11) | |
| XXLEVEL | NUMBER (5) | |
| XXFLAGS | NUMBER (10) | |
| SYSROWID | VARCHAR2 (45) | |
| SYSACLLIST | VARCHAR2 (111) | |
| SYSINDEXSTATE | NUMBER (10) | |
| syscreatedate | Date | Archive date (docdate) |
| systimestamp | Date | Modification date (moddate) |
| sysretentiontime | Date | Earliest deletion date (retention) |
| sysdatasize | Float | Document size (sum(ds_comp.clength)) |
| sysstoragesize | Float | Document size (sum(ds_comp.plength)) |
| sapdocid | varchar2 (40) | Document ID (docidstr) |
| attribute | varchar2 (128) | (ds_seqattrib.attribute) |
The attribute column contains the access rights (R=read, C=create, U=update, D=delete). The values are set as a string with the format “:@P=15”, where the values after the “=” are to be interpreted as a bitmask.
| 01=read |
| 02=create |
| 04=update |
| 08=delete |
For example if all values are set, the value is 15 (1+2+4+8). The value is supplied from the ds_seqattrib table, which is joined with the ds_doc table in a 1:1 correlation (docid:docidno). If document protection is specified when storing from SAP, we then have a line for this document in the ds_seqattrib table. Conversely, if document protection is not needed, no value is entered in the ds_seqattrib table, and the value in the archive table is NULL. The document is not protected and is accessible.
The OT archive server has a switch which makes it possible to ignore the ds_seqattrib table. In this case, only the access rights from the level of the logical archive are in effect and we always have full access. The access rights are stored with the document in SAPERION in the “SAPDocProt” variable. The value is a string (e.g . “RCUD”).
It is the customer’s responsibility to migrate the index information from the OT tables into the IXOS connector archive table, since without this information, no documents can be extracted from the Siemens archive. The number of columns in the archive table can be expanded as much as needed to accommodate future growth. This is done via the SAPERION DDC Designer.