During the execution of the different processes handled by SAP Convergent Charging,
data files are generated for multiple purposes such as integration with third-party
systems, error management, notifications, and so on.
The metadata contained in this table is used by the "Analyze Item Files" web application
for monitoring purpose.
| Schema Version | 5.0.6 | |
| Partitioned | No | |
The FILE_METADATA 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 |
|---|---|---|---|---|---|---|
| NAME | PK_FILE_METADATA |
|
The name of the data file (without any extension) | |||
| ROOT_NAME |
|
The name of the root data file (without any extension) | ||||
| PARENT_NAME |
|
The name of the parent data file (without any extension) | ||||
| FORMAT |
|
The format of the data file | ||||
| STATUS |
|
The current status of the data file | ||||
| ITEM_TYPE |
|
The type of items contained in the data file | ||||
| PRODUCER |
|
The identifier of the instance which produced the data file, or "unknown" if the producer cannot be determined | ||||
| CONSUMER |
|
The identifier of the instance which consumed the data file | ||||
| CLASS_NAME |
|
The name of the item class related to the items contained in the data file | ||||
| WRITTEN_ITEMS_RATER |
|
The number of items written by the rater instance in the data file | ||||
| WRITTEN_ITEMS_BULKLOADER |
|
The number of items written by the bulkloader instance in the data file | ||||
| UNPROCESSED_ITEMS |
|
The number of items which have not been processed yet | ||||
| SUCCESSFUL_ITEMS |
|
The number of items which were successfully processed | ||||
| LOST_ITEMS |
|
The number of items which could not be processed | ||||
| ERRONEOUS_ITEMS |
|
The number of items which could not be sent to SAP CI while processing the data file and were written to error data files | ||||
| PENDING_ERRONEOUS_ITEMS |
|
The number of items which still need to be sent to SAP CI by processing the related error data files | ||||
| CREATION_EVENT |
|
The event which triggered the creation of the data file | ||||
| CREATION_DATE | IX_FILE_METADATA_CREATION |
|
The date and time when the data file was created | |||
| WRITING_END_DATE |
|
The date and time when the writing of the data file ended | ||||
| PROCESSING_START_DATE |
|
The date and time when the processing of the data file started | ||||
| PROCESSING_END_DATE |
|
The date and time when the processing of the data file ended | ||||
| PRODUCER_PATH_OID | FILE_METADATA_PATH (OID)
|
|
The unique identifier of the file system path where the data file was located when it was produced | |||
| CONSUMER_PATH_OID | FILE_METADATA_PATH (OID)
|
|
The unique identifier of the file system path where the data file was located when it was consumed | |||
| JCO_DESTINATION |
|
The JCo or WS destination associated to the items contained in the data file | ||||
| CHECKSUM |
|
The checksum of the data file (computed using the 'SHA-256' algorithm) | ||||
| CHECKSUM_STATUS |
|
The status of the computation and verification of the checksum of the data file | ||||
| PURGE_REFERENCE_DATE | IX_FILE_METADATA_PURGE |
|
The purge reference date of the file metadata |
The database schema defines the following columns. Check the definitions, types, available indexes, and formats:
| Definition | The name of the data file (without any extension) |
| Type | NVARCHAR(300), NOT NULL |
| Primary Key | PK_FILE_METADATA |
| Definition | The name of the root data file (without any extension) |
| Description |
The value of this field corresponds to an entry in the FILE_METADATA table. |
| Type | NVARCHAR(300), NULL |
| Definition | The name of the parent data file (without any extension) |
| Description |
The value of this field corresponds to an another entry in the FILE_METADATA table. |
| Type | NVARCHAR(300), NULL |
| Definition | The format of the data file |
| Format |
The possible values are:
|
| Type | DECIMAL(2), NOT NULL |
| Definition | The current status of the data file |
| Format |
The possible values are:
|
| Type | DECIMAL(2), NOT NULL |
| Definition | The type of items contained in the data file |
| Format |
The possible values are:
|
| Type | DECIMAL(2), NOT NULL |
| Definition | The identifier of the instance which produced the data file, or "unknown" if the producer cannot be determined |
| Type | NVARCHAR(16), NOT NULL |
| Definition | The identifier of the instance which consumed the data file |
| Type | NVARCHAR(16), NULL |
| Definition | The name of the item class related to the items contained in the data file |
| Type | NVARCHAR(256), NOT NULL |
| Definition | The number of items written by the rater instance in the data file |
| Type | DECIMAL(28), NOT NULL |
| Definition | The number of items written by the bulkloader instance in the data file |
| Type | DECIMAL(28), NOT NULL |
| Definition | The number of items which have not been processed yet |
| Type | DECIMAL(28), NOT NULL |
| Definition | The number of items which were successfully processed |
| Type | DECIMAL(28), NOT NULL |
| Definition | The number of items which could not be processed |
| Description |
The possible reasons are:
|
| Type | DECIMAL(28), NOT NULL |
| Definition | The number of items which could not be sent to SAP CI while processing the data file and were written to error data files |
| Type | DECIMAL(28), NOT NULL |
| Definition | The number of items which still need to be sent to SAP CI by processing the related error data files |
| Description |
|
| Type | DECIMAL(28), NOT NULL |
| Definition | The event which triggered the creation of the data file |
| Format |
The possible values are:
|
| Type | DECIMAL(2), NOT NULL |
| Definition | The date and time when the data file was created |
| Type | DATETIME, NOT NULL |
| Available Index | IX_FILE_METADATA_CREATION |
| Definition | The date and time when the writing of the data file ended |
| Type | DATETIME, NULL |
| Definition | The date and time when the processing of the data file started |
| Type | DATETIME, NULL |
| Definition | The date and time when the processing of the data file ended |
| Type | DATETIME, NULL |
| Definition | The unique identifier of the file system path where the data file was located when it was produced |
| Description |
|
| Type | DECIMAL(8), NOT NULL |
| Definition | The unique identifier of the file system path where the data file was located when it was consumed |
| Description |
|
| Type | DECIMAL(8), NOT NULL |
| Definition | The JCo or WS destination associated to the items contained in the data file |
| Description |
|
| Type | NVARCHAR(16), NULL |
| Definition | The checksum of the data file (computed using the 'SHA-256' algorithm) |
| Type | NVARCHAR(64), NULL |
| Definition | The status of the computation and verification of the checksum of the data file |
| Format |
The possible values are:
|
| Type | DECIMAL(2), NOT NULL |
| Definition | The purge reference date of the file metadata |
| Description |
|
| Type | DATETIME, NULL |
| Available Index | IX_FILE_METADATA_PURGE |
See the primary key information:
| Column(s) | NAME |
| Segment | MONITORING_INDX |
The following database indexes are available in the FILE_METADATA database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:
| Indexed Column(s) | CREATION_DATE |
| Unique | No |
| Partitioned | No |
| Clustered | No |
| Indexed Column(s) | PURGE_REFERENCE_DATE |
| Unique | No |
| Partitioned | No |
| Clustered | No |