XXX_PRE_CREATE_FILE (BulkWriter) (Parameter)

Parameter: XXX_PRE_CREATE_FILE (BulkWriter)

This information topic represents several parameters (or indicators) depending on your customizing during the implementation and integration project.

Definition

This flag defines the policy relating to the pre-creation of data files

Description and Use

Rater and bulkloader instances write data within files that are technically managed by bulkwriters, from creation to closing. Each bulkwriter uses a set of writing channels, each of which:

Creates a new data file when no data file is available for writing.
Writes data into available data files until these files are closed for reasons such as:
- The condition of the rollover policy (time-based or size-based) is reached.
- An exception occurred during the use of a writing channel. The transaction cannot be ended correctly, leading to an inconsistent file that cannot be used anymore and must thus be closed.

For optimization purpose, it can be necessary to asynchronously pre-create new data files instead of waiting for the associated channel to create these files on-demand. This system parameter is used to define the policy related to the pre-creation of these data files.

Technical Operations: Monitoring

Use the performance and health metrics to monitor this function in the SAP CC system. See the File Management node in backends.

Syntax and Constraints

The possible value of this system parameter is a combination of the following triggering events, separated with a comma (','):

ROLLOVER: New data files are pre-created:
- When a condition of the rollover policy is reached or when an exception occurred during the use of a writing channel.
- When a charged item class, chargeable item class, refill record class or notification type has been updated
Notes

The currently used data file is only closed when the newly created one is available for writing operations.

As a consequence, the rollover condition may not be strictly respected in terms of file size or recording time.
STARTUP:
- New data files are pre-created on rater startup, during the warmup of the following cached structures: charged items classes, chargeable item classes, refill record classes and notification types. This ensures that rater instances are fully available for handling charging requests (without any additional latency for the first requests)
CLASS_CREATION:
- New data files are pre-created when a new charged item class, chargeable item class or refill record class has been created

Notes

When specifying a value, note that the new data files remain empty until there are used (as the rollover operation is only effective when no more data must be written into the file).
When no value is specified, no data file is pre-created. In this case, data files are created on-demand by each writing channel that needs to write into a new data file.

Technical Details

For more information, consult this section.

Name

XXX_PRE_CREATE_FILE (BulkWriter)

This flag defines the policy relating to the pre-creation of data files

The following parameters may be available in your SAP CC Core Server system:

POSTPAID_CIT_WRITER_PRE_CREATE_FILE
PREPAID_CIT_WRITER_PRE_CREATE_FILE
CHARGED_CI_WRITER_PRE_CREATE_FILE
ACQUIRED_CI_WRITER_PRE_CREATE_FILE
RERATE_WRITER_PRE_CREATE_FILE
NOTIF_WRITER_PRE_CREATE_FILE
AMOUNT_ALERT_NOTIF_WRITER_PRE_CREATE_FILE
EXPIRATION_ALERT_NOTIF_WRITER_PRE_CREATE_FILE
POSTPAID_CIT_ERR_INVALID_WRITER_PRE_CREATE_FILE
POSTPAID_CIT_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE
PREPAID_CIT_ERR_INVALID_WRITER_PRE_CREATE_FILE
PREPAID_CIT_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE
CHARGED_CI_ERR_INVALID_WRITER_PRE_CREATE_FILE
CHARGED_CI_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE
ACQUIRED_CI_ERR_INVALID_WRITER_PRE_CREATE_FILE
ACQUIRED_CI_ERR_COM_EXCEPTION_WRITER_PRE_CREATE_FILE

Note

If your SAP CC Core Server system has been customized by the implementation project team, the above list of parameter names may differ from names in your system landscape.

Use SAP CC Admin+ or SAP CC Config Tool to view the up-to-date list of parameters available in your running SAP CC system.

Handler BulkWriter

Default Value(s)

The possible default values are not available in this documentation. Get the information from the templates of configuration files of the SAP CC system. You can use the export command of the Setup Tool user interface to view the current settings.

Category Parameter

Type String

Access (RO/RW)

RW(+): Dynamic Read / Static and Dynamic Write

An immediate change is possible but is temporary. When it is relevant, change the permanent settings used by the SAP CC Core Server system when it restarts.

Use the Admin+ user interface to change the runtime values or the permanent values of this system parameter in an instance of the SAP CC Core Server system or in multiple instances.

Groups

Process: Output Data Generation

Instance Types

This system parameter is available in the following types of instances in a running SAP CC Core Server system:

rater, bulkloader

Default Values (Factory Settings)

The predefined default values are:

Instance Type

Value

Rater

<Empty value>

Bulkloader

<Empty value>

You can use a default value to reset the runtime value or the restart value (persistent) in the Admin+ user interface.

Note

A default value is part of the factory settings of the SAP CC Core Server systems. It differs from the original value set during the installation or after the Customizing activities.

In Admin+, you can reset a parameter value to this default value, but it is not recommended:

This value may differ from the original value set during the installation of your SAP CC system.
Note that it may also differ from the value defined by the implementation project team and set during the Implementation Phase of the integration project.

Verify the values in your running SAP CC systems before to use the reset command.