| 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
|
| 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
|
| 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
|
| 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
|
| 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
|
| CURRENT_DATE |
System: Versions and Identifications, System: Host Machines |
The current date of the host for this instance
|
| 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
|
| FREE_MEMORY |
System Information: Java Virtual Machine (JVM), System Information: Memory |
The remaining free memory in the heap of the Java Virtual Machine
|
| 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 |
| 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.
|
| 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 |
| 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
|
| 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
|
| 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
|
| PROCESS_IDENTIFIER |
System: Versions and Identifications, System Information: Java Virtual Machine (JVM) |
The process ID of the Java Virtual Machine (when it is available)
|
| REFRESH_LAST_TRIGGER |
Process: Charging and Rating, Tuning: Data Caches, Scheduling |
The last date when the offer cache refresh has been triggered
|
| 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
|
| 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.
|
| 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
|
| 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 |
| 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_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 |
| TOTAL_MEMORY |
System: Host Machines, System Information: Java Virtual Machine (JVM), System Information: Memory |
The total host memory allocated to the Java Virtual Machine
|
| 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
|
| VERSION |
System: Versions and Identifications, System: License Keys, System: Installations |
The technical version number of the instance in the SAP CC system
|
| 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
|
