| Name |
Groups |
Definition |
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| ACQUIRED_CI_ERR_INVALID_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| ACQUIRED_CI_ERR_INVALID_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| ACQUIRED_CI_ERR_INVALID_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| ACQUIRED_CI_ERR_INVALID_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| ACQUIRED_CI_ERR_INVALID_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| ACQUIRED_CI_ERR_INVALID_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| ACQUIRED_CI_ERR_INVALID_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| ACQUIRED_CI_ERR_INVALID_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| ACQUIRED_CI_ERR_INVALID_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| ACQUIRED_CI_ERR_INVALID_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| ACQUIRED_CI_ERR_INVALID_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| ACQUIRED_CI_ERR_INVALID_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| ACQUIRED_CI_ERR_INVALID_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| ACQUIRED_CI_READER_CHANNEL_COUNT |
Tuning: Multithreading and Concurrency, Process: Output Data Transfer (Billable Item Processing) |
The number of reading channels used per directory
|
| ACQUIRED_CI_READER_CI_BUFFER_SIZE |
Process: Output Data Transfer (Billable Item Processing) |
The size of the charged item reading buffer
|
| ACQUIRED_CI_READER_REMOVE_FILE |
Process: Output Data Transfer (Billable Item Processing) |
Whether or not to keep the completely read file
|
| ACQUIRED_CI_READER_ROOT_PATH |
Process: Output Data Transfer (Billable Item Processing), Frontends: File System |
The directory where charged item files, refill record files, and chargeable item files are read
|
| ACQUIRED_CI_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| ACQUIRED_CI_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| ACQUIRED_CI_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| ACQUIRED_CI_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| ACQUIRED_CI_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| ACQUIRED_CI_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| ACQUIRED_CI_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| ACQUIRED_CI_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| ACQUIRED_CI_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| ACQUIRED_CI_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| ACQUIRED_CI_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| ACQUIRED_CI_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| ACQUIRED_CI_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| ACTIVATION_LAST_TRIGGER |
Process: Charging and Rating, Process: Activation |
The last date when the activation process was triggered by an SAP CC user
|
| ACTIVATION_ON_SESSION_UPDATE_ENABLED |
NOT ASSIGNED
|
Whether the activation should be triggered by update rate events of a charging session |
| ACTIVATION_SCHEDULER_ENABLED |
Process: Charging and Rating, Process: Activation, Scheduling |
The enablement or disablement of the activation scheduler in the SAP CC system
|
| ACTIVATION_SCHEDULER_LAST_TRIGGER |
Process: Charging and Rating, Process: Activation, Scheduling |
The last date when a scheduled activation on subscriptions was triggered by the SAP CC system
|
| ACTIVATION_SCHEDULER_MAX_THROUGHPUT |
Process: Charging and Rating, Tuning: Throughput and Latency, Process: Activation, Scheduling |
The maximum number of subscriber accounts per second that can be activated by each rater instance
|
| ACTIVATION_SCHEDULER_RECURRENCE |
Process: Charging and Rating, Process: Activation, Scheduling |
The recurrence period of the activation scheduler
|
| ACTIVATION_SCHEDULER_SUBSCRIPTION_ENABLED |
Process: Charging and Rating, Process: Activation, Scheduling |
The inclusion or exclusion of the subscription data by the internal activation scheduler
|
| ACTIVATION_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for performing the activation process in rater instance (see recurring and one-shot rate activation)
|
| ALLOWANCE_SERVICE_MAX_THROUGHPUT |
Tuning: Throughput and Latency |
The maximum number of requests per second that can be processed by each rater instance when executing operations of the "Allowance
Management" Web service
|
| ALLOWANCE_SERVICE_QUEUE_SIZE |
Tuning: Throughput and Latency |
The maximum number of operations of the 'Allowance Management' Web service that can be queued by a rater instance
|
| ALLOWANCE_SERVICE_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for each rater instance when executing operations of the "Allowance Management" Web service
|
| ALLOWANCES_PURGE_LAST_TRIGGER |
Scheduling |
The reference date of the last manual execution of a purge operation related to allowances data |
| ALLOWANCES_PURGE_RETENTION_PERIOD |
Scheduling |
The duration (in days) of allowances retention period
|
| ALLOWANCES_PURGE_SCHEDULER_ENABLED |
Scheduling |
The enablement or disablement of the internal scheduler responsible for purging expired allowances in provider contracts
|
| ALLOWANCES_PURGE_SCHEDULER_LAST_TRIGGER |
Scheduling |
The reference date of the last execution of a purge operation performed by the dedicated scheduler
|
| ALLOWANCES_PURGE_SCHEDULER_MAX_THROUGHPUT |
Tuning: Throughput and Latency, Scheduling |
The maximum number of provider contracts per second that can be processed by each rater instance during allowance purge operations
|
| ALLOWANCES_PURGE_SCHEDULER_RECURRENCE |
Scheduling |
The recurrence period related to the execution of the scheduler in charge of purging expired allowances
|
| ALLOWANCES_PURGE_THREAD_COUNT |
Tuning: Multithreading and Concurrency, Scheduling |
The number of threads (in each rater instance) reserved to allowance purge operations
|
| AMOUNT_ALERT_NOTIF_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| AMOUNT_ALERT_NOTIF_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| AMOUNT_ALERT_NOTIF_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| AMOUNT_ALERT_NOTIF_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| AMOUNT_ALERT_NOTIF_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| AMOUNT_ALERT_NOTIF_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| AMOUNT_ALERT_NOTIF_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| AMOUNT_ALERT_NOTIF_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| AMOUNT_ALERT_NOTIF_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| AMOUNT_ALERT_NOTIF_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| AMOUNT_ALERT_NOTIF_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| AMOUNT_ALERT_NOTIF_WRITER_ROOT_PATH |
Process: Notification, Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| AMOUNT_ALERT_NOTIF_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| AUDIT_ACTIVATION |
Security Management Settings, System and Data Auditing: Data and Operation Auditing Settings, System: User Management Settings |
The enablement or disablement of the User Operation Auditing feature to conform to the required security and auditing level
|
| AUDIT_DOMAIN |
System and Data Auditing: Data and Operation Auditing Settings |
The list of audit domains that are enabled and define the categories of auditable user operations
|
| AUDIT_OBJECT_ACTIVATION |
Security Management Settings, System and Data Auditing: Data and Operation Auditing Settings |
The enablement or disablement of the Object Snapshot Recording subfeature to conform to the required security and auditing
level
|
| AUDIT_OBJECT_DOMAIN |
System and Data Auditing: Data and Operation Auditing Settings |
The list of audit domains that are enabled and define the categories of data objects that can be audited to object snapshots
|
| BATCH_RATING_GROUP_ASSIGNMENT_POLICY_CLASS |
Process: Provisioning of Provider Contracts in Master Data |
The class for the contract batch rating group assignment policy
|
| BATCH_SERVICE_BATCH_LIMIT_VALUE |
Tuning: Throughput and Latency |
The number of counters to update before to split the batch or the number of milliseconds before to split the batch
|
| BATCH_SERVICE_BATCH_MODE |
Tuning: Throughput and Latency |
The batch mode used to split the commit of the batch
|
| BATCH_SERVICE_BATCH_REPLIES |
Tuning: Throughput and Latency |
The batch reply mode for the batch services
|
| BATCH_SERVICE_QUEUE_SIZE |
Tuning: Throughput and Latency |
The maximum number of operation messages that can be queued when communicating with the Batch Message Service associated to
the offline charging operations
|
| BATCH_SERVICE_REQUEST_BATCH_SIZE |
Tuning: Throughput and Latency |
The batch size of requests processed by one thread of the batch services (offline charging services)
|
| BATCH_SERVICE_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for processing the Batch Message Service of a rater instance
|
| BIT_LOADER_AUTO_COMMIT |
Process: Output Data Transfer (Billable Item Processing) |
Indicates how the billable items sent to SAP CI must be committed or rolled-back
|
| BIT_LOADER_CLIENT |
Process: Output Data Transfer (Billable Item Processing), Backends: JCo |
The JCo client of a Billable Item Loader function
|
| BIT_LOADER_DESTINATION_NAME |
Process: Output Data Transfer (Billable Item Processing), Backends: JCo |
The JCo destination name of a Billable Item Loader function
|
| BULK_CANCEL_STOP_ITEM_COUNT |
Tuning: Bulk Operation Management |
The bulk modification count before which the operation can be canceled
|
| CACHE_COMPRESSION |
Tuning: Data Caches |
The enablement or disablement of the data compression in the caches
|
| CACHE_INVALIDATION_TIMEOUT |
Tuning: Data Caches, System: Network and Communication |
The timeout in milliseconds for waiting acknowledgments for a cache invalidation request from all the system instances except
the updater
|
| CACHE_WARMUP_THREAD_COUNT |
Tuning: Multithreading and Concurrency, Tuning: Data Caches |
The number of threads reserved for processing the cache warm-up
|
| CHARGEABLE_ITEM_UNIQUE_IDENTIFIER_TYPE |
TIF (Transaction Integration Framework) |
The type of the identifiers for the chargeable items generated by the TIF
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| CHARGED_CI_ERR_COM_EXCEPTION_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| CHARGED_CI_ERR_INVALID_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| CHARGED_CI_ERR_INVALID_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| CHARGED_CI_ERR_INVALID_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| CHARGED_CI_ERR_INVALID_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| CHARGED_CI_ERR_INVALID_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| CHARGED_CI_ERR_INVALID_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| CHARGED_CI_ERR_INVALID_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| CHARGED_CI_ERR_INVALID_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| CHARGED_CI_ERR_INVALID_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| CHARGED_CI_ERR_INVALID_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| CHARGED_CI_ERR_INVALID_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| CHARGED_CI_ERR_INVALID_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| CHARGED_CI_ERR_INVALID_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| CHARGED_CI_READER_CHANNEL_COUNT |
Tuning: Multithreading and Concurrency, Process: Output Data Transfer (Billable Item Processing) |
The number of reading channels used per directory
|
| CHARGED_CI_READER_CI_BUFFER_SIZE |
Process: Output Data Transfer (Billable Item Processing) |
The size of the charged item reading buffer
|
| CHARGED_CI_READER_REMOVE_FILE |
Process: Output Data Transfer (Billable Item Processing) |
Whether or not to keep the completely read file
|
| CHARGED_CI_READER_ROOT_PATH |
Process: Output Data Transfer (Billable Item Processing), Frontends: File System |
The directory where charged item files, refill record files, and chargeable item files are read
|
| CHARGED_CI_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| CHARGED_CI_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| CHARGED_CI_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| CHARGED_CI_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| CHARGED_CI_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| CHARGED_CI_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| CHARGED_CI_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| CHARGED_CI_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| CHARGED_CI_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| CHARGED_CI_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| CHARGED_CI_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| CHARGED_CI_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| CHARGED_CI_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| CHARGED_ITEM_SET_UNIQUE_IDENTIFIER_TYPE |
TIF (Transaction Integration Framework) |
The type of the identifiers for the charged item sets generated by the TIF
|
| CLEANUP_LAST_TRIGGER |
Process: Charging and Rating, Scheduling, Process: Session-Based Charging |
The last date when the cleanup was performed
|
| CLEANUP_SCHEDULER_ENABLED |
Process: Charging and Rating, Scheduling, Process: Session-Based Charging |
The enablement or disablement of the cleanup scheduler related to prerating/postrating
|
| CLEANUP_SCHEDULER_LAST_TRIGGER |
Process: Charging and Rating, Scheduling, Process: Session-Based Charging |
The last date when the cleanup was triggered by the scheduler
|
| CLEANUP_SCHEDULER_MAX_THROUGHPUT |
Process: Charging and Rating, Tuning: Throughput and Latency, Scheduling, Process: Session-Based Charging |
The maximum number of subscriptions per second on which the cleanup process can be applied by each rater instance
|
| CLEANUP_SCHEDULER_RECURRENCE |
Process: Charging and Rating, Scheduling, Process: Session-Based Charging |
The recurrence period of the cleanup scheduler |
| CLEANUP_THREAD_COUNT |
Process: Charging and Rating, Tuning: Multithreading and Concurrency, Scheduling, Process: Session-Based Charging |
The number of threads reserved for performing the cleanup process into each rater instance
|
| COLLECTOR_RTT |
System: Network and Communication |
The estimated network round trip time in milliseconds |
| CONNECT_DEFAULT_TIMEOUT |
System: Network and Communication |
The timeout in milliseconds for the connection with a remote instance
|
| CONNECTION_DISPATCHER_WRITE_BUFFER |
Tuning: Throughput and Latency, System: Network and Communication |
Do not use this parameter, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| CONNECTION_EXTERNAL_WRITE_BUFFER |
Tuning: Throughput and Latency, System: Network and Communication |
Do not use this parameter, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| CONNECTION_INTERNAL_WRITE_BUFFER |
Tuning: Throughput and Latency, System: Network and Communication |
Do not use this parameter, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| CONNECTION_WRITE_BUFFER |
Tuning: Throughput and Latency, System: Network and Communication |
Do not use this parameter, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| CONTRACT_PACKING_ENABLED |
Process: Provisioning of Provider Contracts in Master Data |
The enablement or disablement of the packing of provider contracts in customer master data
|
| COUNTER_PRECISION |
Process: Charging and Rating |
The precision of counter values |
| COUNTER_ROUNDING_MODE |
Process: Charging and Rating |
The method for rounding counter values |
| COUNTER_SNAPSHOT_COUNT |
Process: Charging and Rating, Process: Rerating |
The number of counter snapshots stored for each offline subscription or provider contract
|
| CURRENT_DATE |
System: Versions and Identifications, System: Host Machines |
The current date of the host for this instance
|
| DEFAULT_SUBSCRIPTION_TYPE_POLICY |
Process: Provisioning of Subscriptions |
The default policy for subscription type (compatibility with version 4.0 of SAP CC)
|
| DISPATCHER_MAX_SIMULTANEOUS_EXTERNAL_CONNECTION_COUNT |
System: Network and Communication |
The maximum number of simultaneous opened connections to the external service
|
| DISPATCHER_NETWORK_FAILURE_TIMEOUT |
System: Network and Communication |
The timeout in milliseconds for the detection of the down network
|
| DISPATCHER_SERVER_QUEUE_SIZE |
Tuning: Throughput and Latency |
The maximum number of messages that can be queued when communicating with the dispatcher service in a system instance
|
| DISPATCHER_SERVER_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for processing the dispatcher service requests
|
| DISPATCHER_STARTING_TIMEOUT |
System: Network and Communication |
The starting timeout for the dispatcher instances (in millisecond) |
| EIF_CONN_CLASS |
Backends: EIF (Exportable Item Framework) |
The identifier of the Exportable Item Connector (EIF) |
| EIF_EXTERNAL_SYSTEM_CODE_CHARGEABLE_ITEM |
Backends: EIF (Exportable Item Framework) |
The code of the external system that manages chargeable items in the EIF |
| EIF_EXTERNAL_SYSTEM_CODE_CHARGED_ITEM |
Backends: EIF (Exportable Item Framework) |
The code of the external system that manages charged items in the EIF
|
| EIF_EXTERNAL_SYSTEM_CODE_RERATING |
Backends: EIF (Exportable Item Framework), Process: Rerating |
The code of the external system that manages rerating in the EIF
|
| EXPIRATION_ALERT_NOTIF_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| EXPIRATION_ALERT_NOTIF_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| EXPIRATION_ALERT_NOTIF_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| EXPIRATION_ALERT_NOTIF_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| EXPIRATION_ALERT_NOTIF_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| EXPIRATION_ALERT_NOTIF_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| EXPIRATION_ALERT_NOTIF_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| EXPIRATION_ALERT_NOTIF_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| EXPIRATION_ALERT_NOTIF_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| EXPIRATION_ALERT_NOTIF_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| EXPIRATION_ALERT_NOTIF_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| EXPIRATION_ALERT_NOTIF_WRITER_ROOT_PATH |
Process: Notification, Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| EXPIRATION_ALERT_NOTIF_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| EXPIRATION_ALERT_PROCESS_LAST_TRIGGER |
Process: Notification, Process: Account and Balance Management |
The last date when the expiration alert mechanism was started
|
| EXPIRATION_ALERT_SCHEDULER_ENABLED |
Process: Notification, Process: Account and Balance Management, Scheduling |
The enablement or disablement of the expiration alert scheduler
|
| EXPIRATION_ALERT_SCHEDULER_LAST_TRIGGER |
Process: Account and Balance Management, Scheduling |
The last date when the expiration alert mechanism was triggered by a scheduler of the SAP CC system
|
| EXPIRATION_ALERT_SCHEDULER_RECURRENCE |
Process: Account and Balance Management, Scheduling |
The recurrence period of the scheduler in charge of expiration alerts
|
| EXTERNAL_DISCOVERY_ENABLED |
System: Network and Communication |
The enablement or disablement of the external discovery function |
| EXTERNAL_DISCOVERY_MULTICAST_ADDRESS |
System: Network and Communication |
The multicast IP address for the external discovery service
|
| EXTERNAL_DISCOVERY_PORT |
System: Network and Communication |
The port number to access to the discovery service |
| EXTERNAL_SERVICE_HOST |
System: Network and Communication |
The IP address for communicating with the stateful services of the instance via Message TCP
|
| EXTERNAL_SERVICE_PORT |
System: Network and Communication |
The port number for communicating with the stateful services of the instance via Message TCP
|
| FREE_MEMORY |
System Information: Java Virtual Machine (JVM), System Information: Memory |
The remaining free memory in the heap of the Java Virtual Machine
|
| FREE_TRANSAC_NOTIF_ENABLED |
Process: Charging and Rating |
The enablement or disablement of the return of notifications in transactions triggered by a Free Function component
|
| GUIDER_RESPONSE_HANDLER_BATCH_SIZE |
Tuning: Throughput and Latency |
The batch size of responses processed by one thread of the guider response services
|
| GUIDER_RESPONSE_HANDLER_THREAD_COUNT |
Tuning: Throughput and Latency |
The number of threads reserved for processing the guider instance responses
|
| GUIDING_CACHE_CONSISTENCY |
Troubleshooting (Advanced): Performance of Data Caches, Tuning: Data Caches |
Do not use this indicator, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| GUIDING_CACHE_FREE_MEMORY |
System Information: Memory, Tuning: Data Caches |
The remaining free memory into the guiding cache
|
| GUIDING_CACHE_INSTANCES |
Tuning: Multithreading and Concurrency, Tuning: Data Caches |
The maximum number of subcaches for the guiding cache |
| GUIDING_CACHE_SIZE |
Tuning: Data Caches |
The total memory size reserved for caching guiding information into each guider instance
|
| GUIDING_CACHE_STATUS |
Troubleshooting: Performance of Memory, Tuning: Data Caches |
The status of the guiding cache
|
| GUIDING_ENTRY_AVERAGE_SIZE |
Tuning: Data Caches |
The average memory size allocated for one entry (values and key) in the guiding cache |
| HARDWARE_KEY |
System: Versions and Identifications, System: License Keys, System: Host Machines, System: Installations, Security Management Settings |
The hardware key of the host where the specified SAP CC instance is installed. It is associated to the license. |
| HEARTBEAT_ACTIVATION_PERIOD_COUNT |
System: Network and Communication |
The number of polling periods of inactivity after which the heartbeat mechanism is activated
|
| HEARTBEAT_DEAD_CONNECTION_PERIOD_COUNT |
System: Network and Communication |
The number of polling periods after which an instance is considered as down
with the heartbeat mechanism
|
| HEARTBEAT_POLLING_PERIOD |
System: Network and Communication |
The polling period in milliseconds of the heartbeat mechanism
|
| HOSTNAME |
System: Versions and Identifications, System: License Keys, System: Host Machines, System: Installations, System: Network and Communication |
The name of the machine hosting the instance of the SAP CC system |
| HTTP_SERVER_HOST |
System: Network and Communication |
The IP address or hostname for communicating with the HTTP services of the instance
|
| HTTP_SERVER_PORT |
System: Network and Communication |
The port number for communicating with the HTTP services of the current instance
|
| HTTP_SERVER_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for processing the queued incoming HTTP requests |
| INSTALLATION_NO |
System: Versions and Identifications, System: License Keys, System: Host Machines, System: Installations, Security Management Settings |
The installation number associated to the license |
| INSTALLATION_PATH |
System: Versions and Identifications, System: Installations |
The installation directory of the corresponding SAP CC system instance in a particular host
|
| INSTANCE_ID |
System: Versions and Identifications, System: Installations, System Information: Java Virtual Machine (JVM), System: Network and Communication |
The unique ID of the corresponding instance in its SAP CC system. This ID includes the type of the instance and a digit number. |
| INSTANCE_NAME |
System: Versions and Identifications, System: Installations |
(Deprecated) The long name of the instance in the SAP CC system. It includes the instance ID and the host name.
|
| INTERNAL_DISCOVERY_ENABLED |
System: Network and Communication |
The enablement or disablement of the internal discovery function |
| INTERNAL_DISCOVERY_MULTICAST_ADDRESS |
System: Network and Communication |
The multicast IP address for the internal discovery service |
| INTERNAL_DISCOVERY_PORT |
System: Network and Communication |
The port number to access to the internal discovery service |
| INTERNAL_SERVICE_HOST |
System: Network and Communication |
The listening IP address for multicast services |
| INTERNAL_SERVICE_PORT |
System: Network and Communication |
The port number to access to the multicast services of the current instance
|
| IP_ADDRESS_VERSION |
System: Network and Communication |
The version of IP addresses which must be used when host names are resolved |
| ITEM_FILE_SEQUENCE_ENABLED |
Process: Output Data Generation |
The enablement or disablement of the use of a sequence number in the names of the data files
|
| JCO_CPIC_TRACE_LEVEL |
System: Log and Trace Settings |
Turns on the Java Connector (JCo) CPIC traces. Possible levels are 0 (trace is off) to 3 (most verbose trace).
|
| JCO_JRFC_TRACE_LEVEL |
System: Log and Trace Settings |
Turns on the Java Connector (JCo) RFC traces. Possible levels are 0 and 1.
|
| JCO_TRACE_LEVEL |
System: Log and Trace Settings |
Turns on the Java Connector (JCo) traces. Possible levels are 0 to 10
|
| JCO_TRACE_PATH |
System: Log and Trace Settings |
The location of the path for Java Connector (JCo) trace files
|
| LDC_ENABLED |
System: Log and Trace Settings |
The enablement or disablement of the system console as possible destination for log messages and trace messages |
| LDC_FORMATTER |
System: Log and Trace Settings |
The format of logs and traces printed in the console |
| LDF1_ENABLED |
System: Log and Trace Settings |
The enablement or disablement of the fileset #1 as possible destination for log messages and trace messages |
| LDF1_FILE_NAME |
System: Log and Trace Settings |
The file path, name, and extension of the files in destination fileset #1 |
| LDF1_FILE_SIZE |
System: Log and Trace Settings |
The maximum size for the files of the destination fileset #1 before rotation
|
| LDF1_FILESET_SIZE |
System: Log and Trace Settings |
The number of files for the rotations in the destination fileset #1
|
| LDF1_FORMATTER |
System: Log and Trace Settings |
The format of logs and traces generated in the destination fileset #1 |
| LDF2_ENABLED |
System: Log and Trace Settings |
The enablement or disablement of the fileset #2 as possible destination for log messages and trace messages
|
| LDF2_FILE_NAME |
System: Log and Trace Settings |
The file path, name, and extension of the files in destination fileset #2 |
| LDF2_FILE_SIZE |
System: Log and Trace Settings |
The maximum size for the files of the destination fileset #2 before rotation
|
| LDF2_FILESET_SIZE |
System: Log and Trace Settings |
The number of files for the rotations in the destination fileset #2
|
| LDF2_FORMATTER |
System: Log and Trace Settings |
The format of logs and traces generated in the destination fileset #2 |
| LDF3_ENABLED |
System: Log and Trace Settings |
The enablement or disablement of the fileset #3 as possible destination for log messages and trace messages |
| LDF3_FILE_NAME |
System: Log and Trace Settings |
The file path, name, and extension of the files in destination fileset #3 |
| LDF3_FILE_SIZE |
System: Log and Trace Settings |
The maximum size for the files of the destination fileset #3 before rotation
|
| LDF3_FILESET_SIZE |
System: Log and Trace Settings |
The number of files for the rotations in the destination fileset #3
|
| LDF3_FORMATTER |
System: Log and Trace Settings |
The format of logs and traces generated in the destination fileset #3 |
| LDF4_ENABLED |
System: Log and Trace Settings |
The enablement or disablement of the fileset #4 as possible destination for log messages and trace messages |
| LDF4_FILE_NAME |
System: Log and Trace Settings |
The file path, name, and extension of the files in destination fileset #4 |
| LDF4_FILE_SIZE |
System: Log and Trace Settings |
The maximum size for the files of the destination fileset #4 before rotation
|
| LDF4_FILESET_SIZE |
System: Log and Trace Settings |
The number of files for the rotations in the destination fileset #4
|
| LDF4_FORMATTER |
System: Log and Trace Settings |
The format of logs and traces generated in the destination fileset #4 |
| LDF5_ENABLED |
System: Log and Trace Settings |
The enablement or disablement of the fileset #5 as possible destination for log messages and trace messages |
| LDF5_FILE_NAME |
System: Log and Trace Settings |
The file path, name, and extension of the files in destination fileset #5 |
| LDF5_FILE_SIZE |
System: Log and Trace Settings |
The maximum size for the files of the destination fileset #5 before rotation
|
| LDF5_FILESET_SIZE |
System: Log and Trace Settings |
The number of files for the rotations in the destination fileset #5
|
| LDF5_FORMATTER |
System: Log and Trace Settings |
The format of logs and traces generated in the destination fileset #5 |
| LS_APP_DESTINATION |
System: Log and Trace Settings |
The destination(s) of the log messages related to the application level |
| LS_APP_SEVERITY |
System: Log and Trace Settings |
The severity threshold for the generation of log messages related to the business processing (application level) |
| LS_SYS_DESTINATION |
System: Log and Trace Settings |
The destination(s) of the log messages related to the system level |
| LS_SYS_SEVERITY |
System: Log and Trace Settings |
The severity threshold for the generation of log messages related to the system processing (system level) |
| LS_TRC_DESTINATION |
System: Log and Trace Settings |
The destination(s) of the trace messages |
| LS_TRC_DOMAIN |
System: Log and Trace Settings |
The tracing domains that will generate additional trace messages |
| LS_TRC_SEVERITY |
System: Log and Trace Settings |
The severity threshold for the generation of trace messages |
| MESSAGE_API_AUTHENTICATION_REQUIRED |
Security Management Settings, System: Network and Communication |
Specifies if the authentication of the clients that use the SAP CC Message TCP technical interface is required
|
| METRIC_RECORD_TIME_WINDOW |
System and Data Auditing: Product Usage Measurement Settings |
The number of retention days during which the metrics are recorded in the database
|
| METRIC_RECORDING_DAY_TIME |
Scheduling, System and Data Auditing: Product Usage Measurement Settings |
The time of the daily business metric recording
|
| METRIC_RECORDING_SCHEDULER_ENABLED |
Scheduling, System and Data Auditing: Product Usage Measurement Settings |
The enablement or disablement of the business metric recording (as SAP product usage information)
|
| METRIC_RECORDING_SCHEDULER_LAST_TRIGGER |
Scheduling, System and Data Auditing: Product Usage Measurement Settings |
The last date when the metric recording process was triggered by the scheduler
|
| MULTICAST_SERVER_QUEUE_SIZE |
Tuning: Throughput and Latency |
The maximum number of messages that can be queued when communicating with the multicast services in a system instance
|
| MULTICAST_SERVER_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for processing the multicast service requests
|
| NOTIF_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| NOTIF_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| NOTIF_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| NOTIF_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| NOTIF_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| NOTIF_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| NOTIF_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| NOTIF_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| NOTIF_WRITER_MANAGER_COUNT |
Process: Notification, Process: Output Data Generation |
The number of output data managers
|
| NOTIF_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| NOTIF_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| NOTIF_WRITER_ROOT_PATH |
Process: Notification, Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| NOTIF_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| OFF_CLASS |
System: Network and Communication, Backends: JCo |
The identifier of the Operation Factory Framework (OFF)
|
| ORACLE_COMMIT_WRITE |
Backends: Database Management Settings, Backends: Oracle Database Management Settings |
The commit option used within internal stateful operations performed on the Core Database
|
| ORACLE_RATING_SESSION_COMMIT_WRITE |
Backends: Database Management Settings, Backends: Oracle Database Management Settings |
The commit option used within internal stateful operations performed on the Session Database
|
| PARTITION_SWITCH_TIMEOUT |
System: Network and Communication |
The timeout in milliseconds for the detection of a failed partition switch. This timeout is for each partition.
|
| PASSWORD_HASH_ROUNDS_FOR_INDIVIDUAL_USERS |
Security Management Settings, System: User Management Settings |
The number of hash rounds applied to password hashing for an individual user |
| PASSWORD_HASH_ROUNDS_FOR_SERVICE_USERS |
Security Management Settings, System: User Management Settings |
The number of hash rounds applied to password hashing for a service user |
| PASSWORD_MANAGEMENT_CHANGE_DELAY |
System: User Management Settings |
The minimum number of days between two password modifications
|
| PASSWORD_MANAGEMENT_COMPLEXITY |
System: User Management Settings |
The password complexity rules
|
| PASSWORD_MANAGEMENT_ENABLED |
Security Management Settings, System: User Management Settings |
The advanced password management policy activated or not
|
| PASSWORD_MANAGEMENT_EXPIRATION_DELAY |
System: User Management Settings |
The number of days after which a password expires and must be changed
|
| PASSWORD_MANAGEMENT_FAIL_LIMIT |
System: User Management Settings |
The number of successive failed logon attempts before a user is locked
|
| PASSWORD_MANAGEMENT_MAX_IDLE_DELAY |
System: User Management Settings |
The number of days from which a user who has not logged in the system is locked
|
| PASSWORD_MANAGEMENT_MINIMUM_LENGTH |
System: User Management Settings |
The minimum length for a password
|
| PASSWORD_MANAGEMENT_REUSE_CYCLE |
System: User Management Settings |
The number of password modifications that must occur before a password can be reused
|
| PASSWORD_MANAGEMENT_REUSE_DELAY |
System: User Management Settings |
The number of days before a password can be reused
|
| PERIOD_LIMIT_ACTIVATION |
Process: Charging and Rating, Process: Activation |
The number of days after the current date accepted for an activation or charging; 0 deactivates the control function.
|
| PNR_BULK_MODIFICATION_FETCH_SIZE |
Tuning: Bulk Operation Management |
The maximum number of items (in the same transaction of the Core Database system) to be simultaneously modified
when a bulk modification is performed
|
| PNR_BULK_SEARCH_FETCH_SIZE |
Tuning: Bulk Operation Management |
The maximum number of bulk search enquiries that can be performed in a bulk operation
|
| PNR_BULK_THREAD_COUNT |
Tuning: Multithreading and Concurrency, Tuning: Bulk Operation Management |
The number of threads in the thread pool dedicated to the bulk modifications and deletions
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| POSTPAID_CIT_ERR_INVALID_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| POSTPAID_CIT_ERR_INVALID_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| POSTPAID_CIT_ERR_INVALID_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| POSTPAID_CIT_ERR_INVALID_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| POSTPAID_CIT_ERR_INVALID_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| POSTPAID_CIT_ERR_INVALID_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| POSTPAID_CIT_ERR_INVALID_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| POSTPAID_CIT_ERR_INVALID_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| POSTPAID_CIT_ERR_INVALID_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| POSTPAID_CIT_ERR_INVALID_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| POSTPAID_CIT_ERR_INVALID_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| POSTPAID_CIT_ERR_INVALID_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| POSTPAID_CIT_ERR_INVALID_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| POSTPAID_CIT_READER_CHANNEL_COUNT |
Tuning: Multithreading and Concurrency, Process: Output Data Transfer (Billable Item Processing) |
The number of reading channels used per directory
|
| POSTPAID_CIT_READER_CI_BUFFER_SIZE |
Process: Output Data Transfer (Billable Item Processing) |
The size of the charged item reading buffer
|
| POSTPAID_CIT_READER_REMOVE_FILE |
Process: Output Data Transfer (Billable Item Processing) |
Whether or not to keep the completely read file
|
| POSTPAID_CIT_READER_ROOT_PATH |
Process: Output Data Transfer (Billable Item Processing), Frontends: File System |
The directory where charged item files, refill record files, and chargeable item files are read
|
| POSTPAID_CIT_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| POSTPAID_CIT_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| POSTPAID_CIT_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| POSTPAID_CIT_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| POSTPAID_CIT_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| POSTPAID_CIT_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| POSTPAID_CIT_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| POSTPAID_CIT_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| POSTPAID_CIT_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| POSTPAID_CIT_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| POSTPAID_CIT_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| POSTPAID_CIT_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| POSTPAID_CIT_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| POSTPAID_DB_FILE_PROCESSOR_DIRECTORY_COUNT |
Process (Old): Output Data Generation (DB File Processing) |
The number of directories used for writing postpaid data files
|
| POSTPAID_DB_FILE_PROCESSOR_ENCODING |
Process (Old): Output Data Generation (DB File Processing) |
The encoding of the postpaid data files
|
| POSTPAID_DB_FILE_PROCESSOR_EZTAX_OUTPUT_FORMAT |
Process (Old): Output Data Generation (DB File Processing), Process: Taxing |
The format of the postpaid eztax output detail data rows
|
| POSTPAID_DB_FILE_PROCESSOR_PATH_ROOT |
Process (Old): Output Data Generation (DB File Processing) |
The root directory where postpaid data files are stored
|
| POSTPAID_DB_FILE_PROCESSOR_SQL_REQUEST_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the postpaid sql request data rows
|
| POSTPAID_DB_FILE_PROCESSOR_SUBS_REFLECT_DETAIL_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the postpaid subscription reflect detail data rows
|
| POSTPAID_DB_FILE_PROCESSOR_SUBS_REFLECT_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the postpaid subscription reflect data rows
|
| POSTPAID_DB_FILE_PROCESSOR_TRANSAC_DETAIL_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the postpaid transac detail data rows
|
| POSTPAID_DB_FILE_PROCESSOR_TRANSAC_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the postpaid transac data rows
|
| POSTPAID_DB_FILE_PROCESSOR_WRITING_CHANNELS_COUNT |
Tuning: Multithreading and Concurrency, Process (Old): Output Data Generation (DB File Processing) |
The number of writing channels used by each process for postpaid data files
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| PREPAID_CIT_ERR_INVALID_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| PREPAID_CIT_ERR_INVALID_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| PREPAID_CIT_ERR_INVALID_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| PREPAID_CIT_ERR_INVALID_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| PREPAID_CIT_ERR_INVALID_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| PREPAID_CIT_ERR_INVALID_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| PREPAID_CIT_ERR_INVALID_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| PREPAID_CIT_ERR_INVALID_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| PREPAID_CIT_ERR_INVALID_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| PREPAID_CIT_ERR_INVALID_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| PREPAID_CIT_ERR_INVALID_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| PREPAID_CIT_ERR_INVALID_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| PREPAID_CIT_ERR_INVALID_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| PREPAID_CIT_READER_CHANNEL_COUNT |
Tuning: Multithreading and Concurrency, Process: Output Data Transfer (Billable Item Processing) |
The number of reading channels used per directory
|
| PREPAID_CIT_READER_CI_BUFFER_SIZE |
Process: Output Data Transfer (Billable Item Processing) |
The size of the charged item reading buffer
|
| PREPAID_CIT_READER_REMOVE_FILE |
Process: Output Data Transfer (Billable Item Processing) |
Whether or not to keep the completely read file
|
| PREPAID_CIT_READER_ROOT_PATH |
Process: Output Data Transfer (Billable Item Processing), Frontends: File System |
The directory where charged item files, refill record files, and chargeable item files are read
|
| PREPAID_CIT_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| PREPAID_CIT_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| PREPAID_CIT_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| PREPAID_CIT_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| PREPAID_CIT_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| PREPAID_CIT_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| PREPAID_CIT_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| PREPAID_CIT_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| PREPAID_CIT_WRITER_MANAGER_COUNT |
Process: Output Data Generation |
The number of output data managers
|
| PREPAID_CIT_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| PREPAID_CIT_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| PREPAID_CIT_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| PREPAID_CIT_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| PREPAID_DB_FILE_PROCESSOR_DIRECTORY_COUNT |
Process (Old): Output Data Generation (DB File Processing) |
The number of directories used for writing prepaid data files
|
| PREPAID_DB_FILE_PROCESSOR_ENCODING |
Process (Old): Output Data Generation (DB File Processing) |
The encoding of the prepaid data files
|
| PREPAID_DB_FILE_PROCESSOR_EZTAX_OUTPUT_FORMAT |
Process (Old): Output Data Generation (DB File Processing), Process: Taxing |
The format of the prepaid EZTax output data rows
|
| PREPAID_DB_FILE_PROCESSOR_PATH_ROOT |
Process (Old): Output Data Generation (DB File Processing), Frontends: File System |
The root directory where prepaid data files are stored
|
| PREPAID_DB_FILE_PROCESSOR_REFILL_TRANSAC_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the prepaid refill transac data rows
|
| PREPAID_DB_FILE_PROCESSOR_SQL_REQUEST_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the prepaid SQL request data rows |
| PREPAID_DB_FILE_PROCESSOR_TRANSAC_FORMAT |
Process (Old): Output Data Generation (DB File Processing) |
The format of the prepaid transac data rows
|
| PREPAID_DB_FILE_PROCESSOR_WRITING_CHANNELS_COUNT |
Tuning: Multithreading and Concurrency, Process (Old): Output Data Generation (DB File Processing) |
The number of writing channels used by each process for prepaid data files
|
| PRERATING_SESSION_CONTROL_ENABLED |
Process: Charging and Rating |
The enablement or disablement of the session-based charging and prerating to be used at the same time
|
| PROCESS_IDENTIFIER |
System: Versions and Identifications, System Information: Java Virtual Machine (JVM) |
The process ID of the Java Virtual Machine (when it is available)
|
| PROTOCOL_VERSION |
System: Versions and Identifications |
The versions of the communication protocol (via Message TCP) authorized to be registered |
| RATER_RESPONSE_HANDLER_BATCH_SIZE |
Tuning: Throughput and Latency |
The batch size of responses processed by one thread of the rater response services
|
| RATER_RESPONSE_HANDLER_THREAD_COUNT |
Tuning: Throughput and Latency |
The number of threads reserved for processing the rater instance responses
|
| RATING_CONTEXT_CACHE_MAX_SIZE |
Tuning: Throughput and Latency |
The maximum number of cached rating contexts that can be reused within a processing thread for convergent charging
|
| RATING_SESSION_SELECT_POOL_SIZE |
NOT ASSIGNED
|
The size of the pool containing all the search queries performed on the Session Database
|
| RATING_SESSION_SQLHELPER_CONNECTION_COUNT |
Backends: Database Management Settings |
The total number of connections to open on an instance of the Session Database
|
| RATING_SESSION_SQLHELPER_CONNECTION_HEARTBEAT |
Backends: Database Management Settings |
The frequency (in seconds) of heartbeat operations sent to the Session Database
|
| RATING_SESSION_SQLHELPER_DB_INSTANCE_COUNT |
Backends: Database Management Settings |
The number of Session Database instances that can be used by the rater instances of the SAP CC system
|
| RATING_SESSION_SQLHELPER_DB_TIMEOUT |
Backends: Database Management Settings |
The frequency (in seconds) of ping operations sent to the Session Database
|
| RATING_SESSION_SQLHELPER_JDBC_PROPERTIES |
Backends: Database Management Settings |
The properties used to connect to the Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI1 |
Backends: Database Management Settings |
The JDBC URI to connect to the first instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI10 |
Backends: Database Management Settings |
The JDBC URI to connect to the tenth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI11 |
Backends: Database Management Settings |
The JDBC URI to connect to the eleventh instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI12 |
Backends: Database Management Settings |
The JDBC URI to connect to the twelfth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI2 |
Backends: Database Management Settings |
The JDBC URI to connect to the second instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI3 |
Backends: Database Management Settings |
The JDBC URI to connect to the third instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI4 |
Backends: Database Management Settings |
The JDBC URI to connect to the fourth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI5 |
Backends: Database Management Settings |
The JDBC URI to connect to the fifth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI6 |
Backends: Database Management Settings |
The JDBC URI to connect to the sixth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI7 |
Backends: Database Management Settings |
The JDBC URI to connect to the seventh instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI8 |
Backends: Database Management Settings |
The JDBC URI to connect to the eighth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_JDBC_URI_DBI9 |
Backends: Database Management Settings |
The JDBC URI to connect to the ninth instance of a multi-instance Session Database system
|
| RATING_SESSION_SQLHELPER_LOGIN |
Backends: Database Management Settings |
The logon used to connect to the Session Database system
|
| RATING_SESSION_SQLHELPER_MAX_REDO |
Backends: Database Management Settings |
The maximum number of redo attempts when a deadlock occurs on the Session Database
|
| RATING_SESSION_SQLHELPER_PASSWORD |
Backends: Database Management Settings |
The password used to connect to the Session Database system
|
| RATING_SESSION_SQLHELPER_RECONNECT_ATTEMPTS |
Backends: Database Management Settings |
The maximum number of connection attempts made after a connection to the Session Database has been lost
|
| RATING_SESSION_SQLHELPER_RECONNECT_INTERVAL |
Backends: Database Management Settings |
The time period in seconds between reconnection attempts after a connection to the Session Database is lost
|
| RATING_SESSION_SQLHELPER_STATEMENT_CACHE_SIZE |
Backends: Database Management Settings |
The size of the SQL request statement cache for the Session Database
|
| RATING_SESSION_UPDATE_MAX_BATCH_SIZE |
NOT ASSIGNED
|
The maximum number of queries that can be handled by a given thread of the pool dedicated to modification queries performed
on the Session Database
|
| RATING_SESSION_UPDATE_POOL_SIZE |
NOT ASSIGNED
|
The size of the pool containing all the modification queries performed on the Session Database
|
| RECHARGING_STATUS |
Process: Rerating |
The current status of the Chargeable Items Recharging feature |
| REFRESH_LAST_TRIGGER |
Process: Charging and Rating, Tuning: Data Caches, Scheduling |
The last date when the offer cache refresh has been triggered
|
| REFRESH_SCHEDULER_ENABLED |
Process: Charging and Rating, Tuning: Data Caches, Scheduling |
The enablement or disablement of the scheduler iresponsible for the offer cache switching
|
| REFRESH_SCHEDULER_LAST_TRIGGER |
Process: Charging and Rating, Tuning: Data Caches, Scheduling |
The last date when the offer cache refresh has been triggered by the scheduler
|
| REFRESH_SCHEDULER_RECURRENCE |
Process: Charging and Rating, Tuning: Data Caches, Scheduling |
The recurrence period of the scheduler in charge of refreshing the offer cache
|
| RENEW_RESERVATION_RESEND_ATTEMPTS |
Process: Notification, Process: Session-Based Charging |
The maximum number of attempts to resend a renew reservation notification if it was not acknowledged
|
| RENEW_RESERVATION_RESEND_INTERVAL |
Process: Notification, Process: Session-Based Charging |
The minimum time interval (in seconds) between two attempts to send a renew reservation notification
|
| RENEW_RESERVATION_RESEND_THREAD_COUNT |
Process: Session-Based Charging |
The number of processing threads dedicated to resending renew reservation notifications
|
| RENEW_RESERVATION_SEND_TIMEOUT |
System: Network and Communication, Process: Session-Based Charging |
The maximum time (in ms) to be used by the rater instance for sending the renew reservation notification
|
| RERATE_PROC_CLASS |
Process: Rerating |
The identifier of the Rerate Processor
|
| RERATE_WRITER_AUTO_COMMIT |
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| RERATE_WRITER_CHANNEL_COUNT |
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| RERATE_WRITER_CLEAN_ARCHIVED_FILE |
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| RERATE_WRITER_DEFLATE |
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| RERATE_WRITER_DEFLATE_OUTPUT_FORMAT |
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| RERATE_WRITER_FILE_SEQUENCE_ID |
Process: Output Data Generation |
The sequence key identifier to use
|
| RERATE_WRITER_FILE_VERSION |
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| RERATE_WRITER_LINE_NUMBERING |
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| RERATE_WRITER_MANAGER_COUNT |
Process: Output Data Generation, Process: Rerating |
The number of output data managers
|
| RERATE_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| RERATE_WRITER_PRE_CREATE_FILE |
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| RERATE_WRITER_ROOT_PATH |
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| RERATE_WRITER_TIME_BASED_FILE_ROLLOVER_POLICY |
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
| RERATING_ENABLED |
Process: Rerating |
|
| SAP_INSTANCE_NAME |
System: Versions and Identifications, System: Installations |
The SAP Instance Name of the SAP CC system instance in its host
|
| SAP_INSTANCE_NUMBER |
System: Versions and Identifications, System: Installations |
The SAP Instance Number (00-97) of the SAP CC system instance in its host
|
| SERVICES_STATISTICS |
Troubleshooting (Advanced): Performance of Services |
Do not use this indicator, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation. The usage statistics about the different services running in an SAP CC system instance.
|
| SESSION_AVG_ID_SIZE |
Tuning: Data Caches, Process: Session-Based Charging |
The average memory size allocated for one rating session ID |
| SESSION_AVG_NB_PER_HISTORY |
Tuning: Data Caches, Process: Session-Based Charging |
The average number of sessions per subscriber |
| SESSION_AVG_OBJECT_SIZE |
Tuning: Data Caches, Process: Session-Based Charging |
The average memory size allocated for one charging session
|
| SESSION_CONSISTENCY |
Troubleshooting (Advanced): Performance of Data Caches, Tuning: Data Caches, Process: Session-Based Charging |
Do not use this indicator, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| SESSION_COUNT |
Process: Charging and Rating, Process: Session-Based Charging |
The number of sessions currently stored in the session cache
|
| SESSION_FREE_MEMORY |
Troubleshooting: Performance of Memory, System Information: Memory, Tuning: Data Caches, Process: Session-Based Charging |
The remaining free memory of the charging session cache
|
| SESSION_HISTORY_CONSISTENCY |
Troubleshooting (Advanced): Performance of Data Caches, Tuning: Data Caches, Process: Session-Based Charging |
Do not use this indicator, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| SESSION_HISTORY_COUNT |
Process: Charging and Rating, Process: Session-Based Charging |
The number of session histories currently stored in the session cache
|
| SESSION_HISTORY_FREE_MEMORY |
System Information: Memory, Tuning: Data Caches, Process: Session-Based Charging |
The remaining free memory of the session history cache
|
| SESSION_HISTORY_MEMORY_SIZE |
Tuning: Data Caches, Process: Session-Based Charging |
The memory reserved for charging session histories into each rater instance
|
| SESSION_HISTORY_STATUS |
Troubleshooting: Performance of Memory, Tuning: Data Caches, Process: Session-Based Charging |
The status of the session history cache
|
| SESSION_MEMORY_INSTANCES |
Tuning: Data Caches, Process: Session-Based Charging |
The maximum number of subcaches for the session cache
|
| SESSION_MEMORY_SIZE |
Tuning: Data Caches, Process: Session-Based Charging |
The memory reserved for charging sessions into each rater instance |
| SESSION_SERIALIZATION_FORMAT |
Tuning: Data Caches, Process: Session-Based Charging |
The format of the session data serialization |
| SESSION_STATUS |
Troubleshooting: Performance of Memory, Tuning: Data Caches, Process: Session-Based Charging |
The status of the session cache
|
| SLD_PASSWORD |
Security Management Settings, Backends: System Landscape Directory (SLD), System: User Management Settings |
The password used to submit the payload to the System Landscape Directory
|
| SLD_SCHEDULER_ENABLED |
Scheduling, Backends: System Landscape Directory (SLD) |
The enablement or disablement of the scheduler responsible for sending updates to the System Landscape Directory (SLD)
|
| SLD_SCHEDULER_RECURRENCE |
Scheduling, Backends: System Landscape Directory (SLD) |
The recurrence period of the scheduler responsible for sending updates to the System Landscape Directory
|
| SLD_URL |
Backends: System Landscape Directory (SLD) |
The URL to submit the payload to the System Landscape Directory
|
| SLD_USER |
Security Management Settings, Backends: System Landscape Directory (SLD), System: User Management Settings |
The user identifier used to submit the payload to the System Landscape Directory
|
| SPENDING_STATUS_REPORT_RESEND_ATTEMPTS |
Process: Notification, Process: Spending Status Monitoring |
The maximum number of attempts to resend a spending status report if it was not acknowledged
|
| SPENDING_STATUS_REPORT_RESEND_INTERVAL |
Process: Notification, Process: Spending Status Monitoring |
The minimum time interval (in seconds) between two attempts to send a spending status report
|
| SPENDING_STATUS_REPORT_RESEND_THREAD_COUNT |
Process: Spending Status Monitoring |
The number of processing threads dedicated to resending spending status report notifications
|
| SPENDING_STATUS_REPORT_SEND_TIMEOUT |
System: Network and Communication, Process: Spending Status Monitoring |
The maximum time (in ms) to be used by the rater instance for sending the spending status report
|
| SQLHELPER_CONNECTION_COUNT |
Tuning: Multithreading and Concurrency, Backends: Database Management Settings |
The total number of connections to open on an instance of the Core Database
|
| SQLHELPER_CONNECTION_HEARTBEAT |
Backends: Database Management Settings |
The frequency (in seconds) of heartbeat operations sent to the Core Database system
|
| SQLHELPER_DB_INSTANCE_COUNT |
Backends: Database Management Settings |
The number of Core Database instances that can be used by the rater instances of the SAP CC system
|
| SQLHELPER_DB_TIMEOUT |
Backends: Database Management Settings |
The frequency (in seconds) of ping operations sent to the Core Database system
|
| SQLHELPER_ID_INTERVAL |
Backends: Database Management Settings |
The size of the pool of unique identifiers used to identify the objects into the database
|
| SQLHELPER_JDBC_PROPERTIES |
Security Management Settings, Backends: Database Management Settings |
The properties used to connect to the Core Database system
|
| SQLHELPER_JDBC_URI |
Security Management Settings, Backends: Database Management Settings |
The JDBC URI(s) to connect to the database systems
|
| SQLHELPER_JDBC_URI_DBI1 |
Backends: Database Management Settings |
The JDBC URI to connect to the first instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI10 |
Backends: Database Management Settings |
The JDBC URI to connect to the tenth instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI11 |
Backends: Database Management Settings |
The JDBC URI to connect to the eleventh instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI12 |
Backends: Database Management Settings |
The JDBC URI to connect to the twelfth instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI2 |
Backends: Database Management Settings |
The JDBC URI to connect to the second instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI3 |
Backends: Database Management Settings |
The JDBC URI to connect to the third instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI4 |
Backends: Database Management Settings |
The JDBC URI to connect to the fourth instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI5 |
Backends: Database Management Settings |
The JDBC URI to connect to the fifth instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI6 |
Backends: Database Management Settings |
The JDBC URI to connect to the sixth instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI7 |
Backends: Database Management Settings |
The JDBC URI to connect to the seventh instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI8 |
Backends: Database Management Settings |
The JDBC URI to connect to the eighth instance of a multi-instance Core Database system
|
| SQLHELPER_JDBC_URI_DBI9 |
Backends: Database Management Settings |
The JDBC URI to connect to the ninth instance of a multi-instance Core Database system
|
| SQLHELPER_LOGIN |
Security Management Settings, Backends: Database Management Settings, System: User Management Settings |
The logon used to connect to the Core Database system
|
| SQLHELPER_MAX_REDO |
Backends: Database Management Settings |
The maximum number of redo attempts when a deadlock occurs on the Core Database
|
| SQLHELPER_PASSWORD |
Security Management Settings, Backends: Database Management Settings, System: User Management Settings |
The password used to connect to the Core Database system
|
| SQLHELPER_RECONNECT_ATTEMPTS |
Backends: Database Management Settings |
The maximum number of connection attempts made after a connection to the Core Database has been lost
|
| SQLHELPER_RECONNECT_INTERVAL |
Backends: Database Management Settings |
The time period in seconds between reconnection attempts after a connection to the Core Database is lost
|
| SQLHELPER_STATEMENT_CACHE_SIZE |
Backends: Database Management Settings |
The size of the SQL request statement cache for the Core Database
|
| STATEFUL_SERVICE_BATCH_LIMIT_VALUE |
Tuning: Throughput and Latency |
The number of counters to update before to split the batch or number of milliseconds before to split the batch
|
| STATEFUL_SERVICE_BATCH_MODE |
Tuning: Throughput and Latency |
The batch mode used by the SAP CC system to split the commit of the batch
|
| STATEFUL_SERVICE_BATCH_REPLIES |
Tuning: Throughput and Latency |
The batch replies mode for the stateful services
|
| STATEFUL_SERVICE_QUEUE_POLICY_HASH_KEY_SIZE |
Tuning: Throughput and Latency |
The technical number used to compute the number of request subsets which must be distributed over the threads that are allocated
to the stateful service
|
| STATEFUL_SERVICE_QUEUE_POLICY_LEVELS |
Tuning: Throughput and Latency |
The list of levels used to distribute the requests over the threads that are allocated to the stateful service
|
| STATEFUL_SERVICE_QUEUE_SIZE |
Tuning: Throughput and Latency |
The maximum number of messages that can be queued when communicating with the Stateful Message Service (support of online
charging and interinstance communications) in a system instance
|
| STATEFUL_SERVICE_REQUEST_BATCH_SIZE |
Tuning: Throughput and Latency |
The batch size of requests processed by one thread of the stateful services
|
| STATEFUL_SERVICE_SQL_UPDATE_MAX_BATCH_SIZE |
Tuning: Throughput and Latency |
The maximum number of SQL queries that can be handled simultaneously by a given thread of the pool containing all the modification
queries linked to the stateful requests and performed on the Core Database
|
| STATEFUL_SERVICE_SQL_UPDATE_POOL_SIZE |
Tuning: Throughput and Latency |
The size of the pool containing all the modification queries linked to the stateful requests and performed on the Core Database |
| STATEFUL_SERVICE_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for the Stateful Message Service (support of online charging services and interinstance communications)
|
| STATELESS_SERVICE_BATCH_REPLIES |
Tuning: Throughput and Latency |
The batch reply mode for the stateless services
|
| STATELESS_SERVICE_QUEUE_SIZE |
Tuning: Throughput and Latency |
The maximum number of messages that can be queued when communicating with the Stateless Message Service (support of the online
stateless rating services) in a system instance
|
| STATELESS_SERVICE_REQUEST_BATCH_SIZE |
Tuning: Throughput and Latency |
The batch size of requests processed by one thread of the stateless message service
|
| STATELESS_SERVICE_THREAD_COUNT |
Tuning: Multithreading and Concurrency |
The number of threads reserved for the Stateless Message Service (support of the online stateless rating services)
|
| SUBSCRIPTION_CACHE_CONSISTENCY |
Troubleshooting (Advanced): Performance of Data Caches, Tuning: Data Caches |
Do not use this indicator, except under SAP Support Team supervision or under specific recommendation provided within the
SAP CC documentation
|
| SUBSCRIPTION_CACHE_FREE_MEMORY |
System Information: Memory, Tuning: Data Caches |
The remaining free memory into the provisioning cache
|
| SUBSCRIPTION_CACHE_INSTANCES |
Tuning: Multithreading and Concurrency, Tuning: Data Caches |
The maximum number of subcaches for the provisioning cache |
| SUBSCRIPTION_CACHE_SIZE |
Tuning: Data Caches |
The total memory size reserved for caching provisioning data |
| SUBSCRIPTION_CACHE_STATUS |
Troubleshooting: Performance of Memory, Tuning: Data Caches |
The status of the provisioning data cache
|
| SUBSCRIPTION_OBJECT_AVERAGE_SIZE |
Tuning: Data Caches |
The average memory size allocated for one data object in the provisioning cache |
| SYSTEM_ID |
System: Versions and Identifications, System: License Keys, System: Host Machines, System: Installations |
The unique identifier of the SAP CC Core Server system in the SAP system landscape |
| SYSTEM_NO |
System: Versions and Identifications, System: License Keys, System: Host Machines, System: Installations |
The SAP system number associated to the license |
| TAX_FRAMEWORK |
Process: Charging and Rating, Process: Taxing |
The identifier(s) of the tax system(s) enabled
|
| TAX_PRECISION |
Process: Charging and Rating, TIF (Transaction Integration Framework), Process: Taxing |
The precision of tax amounts computed by the SAP CC system
|
| TAX_ROUNDING_MODE |
Process: Charging and Rating, TIF (Transaction Integration Framework), Process: Taxing |
The method for rounding tax amounts |
| TFP_AMOUT_TAX_INCLUDED |
Process (Old): Output Data Generation (Transaction File Processing), Process: Taxing |
The amount of the transaction without the tax amount is replaced by the amount of the transaction with the tax amount
|
| TFP_COMPUTE_TAX |
Process (Old): Output Data Generation (Transaction File Processing), Process: Taxing |
Enables the tax process for the external account
|
| TFP_MAX_FILE_SIZE |
Process (Old): Output Data Generation (Transaction File Processing) |
The maximum size of a file for the Transaction File Processor
|
| TFP_PERIOD_POLICY |
Process (Old): Output Data Generation (Transaction File Processing) |
This parameter specifies period for the rotating files of the Transaction File Processor
|
| TFP_TRANSAC_DETAILS |
Process (Old): Output Data Generation (Transaction File Processing) |
This parameter specifies the transaction details to output with the Transaction File Processor
|
| TFP_TRANSAC_FILTERS |
Process (Old): Output Data Generation (Transaction File Processing) |
The transaction filters to use with the Transaction File Processor |
| TFP_WRITING_CHANNELS_COUNT |
Tuning: Multithreading and Concurrency, Process (Old): Output Data Generation (Transaction File Processing) |
The number of writing channels that must be used by each process when the
Transaction File Processor is used
|
| TFP_WRITING_CHANNELS_PATH |
Process (Old): Output Data Generation (Transaction File Processing) |
The path where files will be written by the Transaction File Processor
|
| THREAD_DUMP_ENABLED |
Troubleshooting (Advanced): Thread Dump File Generation |
The enablement or disablement of the management of custom thread dump files
|
| THREAD_DUMP_MINIMUM_INTERVAL |
Troubleshooting (Advanced): Thread Dump File Generation |
The minimum time interval (in seconds) between two thread dumps |
| THREAD_DUMP_OUTPUT_PATH |
Troubleshooting (Advanced): Thread Dump File Generation |
The storage location of the created files containing thread dump files
|
| THREAD_DUMP_RETENTION_PERIOD |
Troubleshooting (Advanced): Thread Dump File Generation |
The duration (in days) of the retention period for thread dumps |
| THREAD_DUMP_THRESHOLD_CPU_TIME |
Troubleshooting (Advanced): Thread Dump File Generation |
The threshold (in ms) relating to CPU time above which a thread dump must be generated |
| THREAD_DUMP_THRESHOLD_OUTPUT_ITEMS |
Troubleshooting (Advanced): Thread Dump File Generation |
The threshold relating to the number of output items generated by a thread above that a thread dump must be generated |
| THREAD_DUMP_THRESHOLD_RATING_CONTEXTS |
Troubleshooting (Advanced): Thread Dump File Generation |
The threshold relating to the number of rating contexts used by a thread above that a thread dump must be generated |
| THREAD_DUMP_THRESHOLD_SQL_TIME |
Troubleshooting (Advanced): Thread Dump File Generation |
The threshold (in ms) relating to the duration of an SQL query executed within a thread above which a thread dump must be
generated
|
| THREAD_DUMP_TRIGGER_PERIOD |
Troubleshooting (Advanced): Thread Dump File Generation |
The period (in seconds) used by the scheduled trigger after which a thread dump must be generated |
| TLS_CIPHER_SUITES |
Security Management Settings, System: Network and Communication |
The list of enabled cipher suites for encrypted communications using SSL/TLS |
| TLS_PROTOCOLS |
Security Management Settings, System: Network and Communication |
The list of enabled protocols for encrypted communications using SSL/TLS |
| TOTAL_MEMORY |
System: Host Machines, System Information: Java Virtual Machine (JVM), System Information: Memory |
The total host memory allocated to the Java Virtual Machine
|
| TRANSAC_PROC_CLASS |
Process (Old): Output Data Generation (Transaction File Processing), Process (Old): Output Data Generation (DB File Processing), TIF (Transaction Integration Framework) |
The identifier of the Transaction Processor
|
| TRANSACTION_DETAIL_PRECISION |
Process: Charging and Rating, TIF (Transaction Integration Framework) |
The precision of the numerical transaction details |
| TRANSACTION_DETAIL_ROUNDING_MODE |
Process: Charging and Rating, TIF (Transaction Integration Framework) |
The method for rounding numerical transaction details |
| TRANSACTION_PRECISION |
Process: Charging and Rating, TIF (Transaction Integration Framework) |
The precision of transaction amounts |
| TRANSACTION_ROUNDING_MODE |
Process: Charging and Rating, TIF (Transaction Integration Framework) |
The method for rounding transaction amounts |
| TRANSACTIONS_TO_CANCEL_IN_RESULT_ENABLED |
Process: Session-Based Charging |
The enablement or disablement of the computation of transactions to cancel during session-based charging
|
| TRANSPORT_SCHEDULER_ENABLED |
Scheduling |
The enablement or disablement of the internal scheduler responsible for processing the transport requests
|
| TRANSPORT_SCHEDULER_RECURRENCE |
Scheduling |
The recurrence period related to the execution of the scheduler in charge of executing the transport requests
|
| TRX_NAME |
System: Versions and Identifications, System: License Keys, System: Installations |
The SAP product name and commercial release number of the deployed SAP CC system
|
| USER_ISOLATION_ENABLED |
System: User Management Settings |
The enablement or disablement of the isolation between service and individual users
|
| USER_SESSION_ENABLED |
System: User Management Settings |
The enablement or disablement of the user session management and concurrent edition management
|
| USER_SESSION_SESSION_LIMIT_PER_USER_AND_TOOL |
System: User Management Settings |
The limit of user sessions per user and user interface
|
| USER_SESSION_VALIDITY_PERIOD |
System: User Management Settings |
The validity period of user sessions (in seconds)
|
| VERSION |
System: Versions and Identifications, System: License Keys, System: Installations |
The technical version number of the instance in the SAP CC system
|
| WS_MONITORING_PLAN_RETURNED_AS_CHARGE_PLAN |
Process: Provisioning of Provider Contracts in Master Data, Process: Spending Status Monitoring |
The enablement or disablement of the returning of monitoring plans as charge plans
|
| WS_SERVER_QUEUE_SIZE |
Tuning: Throughput and Latency, System: Network and Communication |
The maximum number of operation requests that can be queued when communicating with the instance over the Web Services (WS)
technical interface
|
| WS_SERVER_THREAD_COUNT |
Tuning: Multithreading and Concurrency, System: Network and Communication |
The number of threads reserved for processing the queued WS requests for parallel processing and performance optimization
|
| WS_SSO_ENABLED |
Security Management Settings, System: Network and Communication |
The Single Sign-On authentication for the Web Services activated or not
|
| XML_SCHEMA_VALIDATION |
System: Network and Communication |
The XML schema validation activated or not
|
| XXX_AUTO_COMMIT (BillableItemLoader)
|
Process: Output Data Transfer (Billable Item Processing) |
Indicates how the billable items sent to SAP CI must be committed or rolled-back
|
| XXX_AUTO_COMMIT (BulkWriter)
|
Process: Output Data Generation |
Whether or not to write all charged items or only those whose charging operation is successful
|
| XXX_CHANNEL_COUNT (BulkWriter)
|
Process: Output Data Generation |
The number of writing channels and files used per directory to store charged items and other data
|
| XXX_CHANNEL_COUNT (BulkReader)
|
Tuning: Multithreading and Concurrency, Process: Output Data Transfer (Billable Item Processing) |
The number of reading channels used per directory
|
| XXX_CI_BUFFER_SIZE (BulkReader)
|
Process: Output Data Transfer (Billable Item Processing) |
The size of the charged item reading buffer
|
| XXX_CLEAN_ARCHIVED_FILE (BulkWriter)
|
Process: Output Data Generation |
This flag gives the possibility to enable or disable the removal of uncommitted items from data files during archiving operations
|
| XXX_CLIENT (BillableItemLoader)
|
Process: Output Data Transfer (Billable Item Processing), Backends: JCo |
The JCo client of a Billable Item Loader function
|
| XXX_DEFLATE (BulkWriter)
|
Process: Output Data Generation |
The enablement or disablement of the deflate data compression of the generated files
|
| XXX_DEFLATE_OUTPUT_FORMAT (BulkWriter)
|
Process: Output Data Generation |
This flag indicates the file format used if that files are deflated
|
| XXX_DESTINATION_NAME (BillableItemLoader)
|
Process: Output Data Transfer (Billable Item Processing), Backends: JCo |
The JCo destination name of a Billable Item Loader function
|
| XXX_FILE_SEQUENCE_ID (BulkWriter)
|
Process: Output Data Generation |
The sequence key identifier to use
|
| XXX_FILE_VERSION (BulkWriter)
|
Process: Output Data Generation |
This flag indicates the version of the generated data files
|
| XXX_LINE_NUMBERING (BulkWriter)
|
Process: Output Data Generation |
This flag indicates whether the line number is written in the data file as the first field, or not
|
| XXX_MANAGER_COUNT (BulkWriter)
|
Process: Output Data Generation |
The number of output data managers
|
| XXX_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY (BulkWriter)
|
Process: Output Data Generation |
The file size-based rollover policy that triggers a file size dependent switch from current file to a new one
|
| XXX_PRE_CREATE_FILE (BulkWriter)
|
Process: Output Data Generation |
This flag defines the policy relating to the pre-creation of data files
|
| XXX_REMOVE_FILE (BulkReader)
|
Process: Output Data Transfer (Billable Item Processing) |
Whether or not to keep the completely read file
|
| XXX_ROOT_PATH (BulkWriter)
|
Process: Output Data Generation, Backends: File System |
The directory where charged item files, refill record files, and chargeable item files are created
|
| XXX_ROOT_PATH (BulkReader)
|
Process: Output Data Transfer (Billable Item Processing), Frontends: File System |
The directory where charged item files, refill record files, and chargeable item files are read
|
| XXX_TIME_BASED_FILE_ROLLOVER_POLICY (BulkWriter)
|
Process: Output Data Generation |
The file time-based rollover policy that triggers a time dependent switch from current file to a new one
|
