| Schema Version | 5.0.6 | |
| Tablespace | CATALOG_DATA | |
| Partitioned | No | |
The WS_IDEMPOTENCY table is defined by the following columns in your back-end database. See the column details for more information.
| Name | PK | FK | IX | Uses | Used by | Definition |
|---|---|---|---|---|---|---|
| OPERATION_UID | PK_WS_IDEMPOTENCY |
|
The operation unique identifier | |||
| OPERATION_NAME | PK_WS_IDEMPOTENCY |
|
The operation name | |||
| OPERATION_DATE | IX_WS_IDPY |
|
The date of operation first execution | |||
| OPERATION_RESULT |
|
The result of the operation execution (only for operations that support response caching) |
The database schema defines the following columns. Check the definitions, types, available indexes, and formats:
| Definition | The operation unique identifier |
| Type | VARCHAR(256), NOT NULL |
| Primary Key | PK_WS_IDEMPOTENCY |
| Definition | The operation name |
| Type | VARCHAR(256), NOT NULL |
| Primary Key | PK_WS_IDEMPOTENCY |
| Definition | The date of operation first execution |
| Type | TIMESTAMP, NOT NULL |
| Available Index | IX_WS_IDPY |
| Definition | The result of the operation execution (only for operations that support response caching) |
| Type | VARCHAR(2000), NULL |
See the primary key information:
| Column(s) | OPERATION_NAME,OPERATION_UID |
| Tablespace | CATALOG_INDX |
The following database indexes are available in the WS_IDEMPOTENCY database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:
| Indexed Column(s) | OPERATION_DATE |
| Unique | No |
| Partitioned | No |
| Tablespace | CATALOG_INDX |
