Setting the C1_​FM Feature Configuration

Procedure

To set the C1_​FM feature configuration:

  1. Click the Admin link in the Application toolbar.
    A list appears.
  2. From the Admin menu, select F and then click Feature Configuration.
    A sub-menu appears.
  3. Click the Search option from the Feature Configuration sub-menu.
    The Feature Configuration Query screen appears.
  4. In the Feature Configuration Search zone, enter C1_​FM in the Feature Name field.
    Note: ORMB search engine supports wildcard search, where you can substitute the percentage (%) symbol as a stand in for any word or letter in a search criteria. You can use the '%' wildcard character in all input fields except the date and ID fields. The '%' wildcard character is suffixed automatically at the end of the partial search criteria. Therefore, you may or may not specify the wildcard character at the end of the partial search criteria. However, you have to prefix the wildcard character manually wherever required.
  5. Click Search.
    A list of feature configurations that meet the search criteria appears in the search results.
  6. In the Search Results section, click the link in the Description column corresponding to the feature configuration whose details you want to edit.

    The Feature Configuration screen appears. It contains the following option types:

    Option Type Description Mandatory (Yes or No)
    First Batch in Transaction Aggregation Cycle Used to specify the first mandatory batch that you want to be executed in the transaction aggregation cycle.
    Note: At present, the system does not support any value other than C1-TXNIP for this option type.
    		 Yes
    Last Batch in Transaction Aggregation Cycle Used to specify the last mandatory batch that you want to be executed in the transaction aggregation cycle.
    Note: At present, the system does not support any value other than C1-TXNCU for this option type.
    		 Yes
    Disaggregation - Price Assignment Used to indicate whether the disaggregation request should be automatically created for a person or account when a price item is assigned to the person or account or the existing price item pricing assigned to the person or account is modified. The valid values are:

    • true

    • false

    Note: You can use this feature when an algorithm which is created using the TXNDISAGGPRA algorithm type is attached to the Post-Processing system event of the C1_​PRASGN_​BO business object.
    		 No
    Allow Duplicate Summary ID Used to indicate whether the transaction legs can have duplicate summary ID while creating an aggregated billable charge using the Service Quantity Calculation (C1-TXNSQ) batch. The valid values are:

    • true

    • false

    Note:

    If you set this option type to false, the system does not create the aggregated billable charge when one or more transaction legs have the same summary ID.

    If you do not specify the value for this option type, by default, the value is set to false.

    		 No
    Parallel Query Degree Used to specify the degree of parallelism that you want to use while creating chunks (i.e. work units) in various Transaction Feed Management (TFM) batches. The valid values are:

    • 1

    • 2

    • 3

    • 4

    • 5

    • 6

    • 7

    Note:

    With the parallel query feature, multiple threads on the database can work together simultaneously to process a single SQL statement which is used to create chunks. This helps to improve the batch performance.

    The system calculates the number of threads on the database that can be used to execute the SQL statement by setting 2 to the power of the specified parallel query degree. For example, if you set the parallel query degree to 4, the system uses 16 (i.e. 2^4) threads on the database to create work units.

    You must set the parallel query degree depending on the infrastructure available on the site. If you do not specify the value for this option type, by default, the parallel query degree is set to 2.

    		 No
    Price Item Determination Batch Description Used to specify the description for the batch which is used for validating the transaction and deriving the price item in the transaction aggregation cycle. For example, Validate Transaction and Derive Price Item. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes
    Remove Duplicates from Accumulated Rule Output Used to indicate whether duplicate transaction legs must be created during the transaction aggregation cycle through the rule output accumulation process. The valid values are:

    • true

    • false

    Note: If you do not specify the value for this option type, by default, the value is set to false.
    		 No
    Rule Output Accumulation Used to indicate whether the system should accumulate the output parameters of all rules where the criteria returns Rule Is True irrespective of whether the rule true action is set to Next Dependent, Next Rule by Priority, or Success and then create transaction legs using the accumulated output parameters. The valid values are:

    • true

    • false

    Note: If you do not specify the value for this option type, by default, the value is set to false.
    		 No
    Show Default Values in Price Item Pricing Used to indicate whether the default values must appear in the Ignore Transaction, Aggregate Transaction, and Aggregation Schedule fields while defining the price item pricing. The valid values are:

    • Y

    • N

    		 Yes
    Use Materialized Views Used to indicate whether the price item pricing information must be cached in the CI_​PRC_​AGRD, CI_​PRC_​PL, and CI_​PRC_​INH_​PL tables. The valid values are:

    • true

    • false

    		 Yes
    Maximum Price Item Parameters Cache Size Used to indicate the maximum number of price items whose parameter information can be cached in the memory. Yes
    Maximum Price Item Parameter Groups Cache Size Used to indicate the maximum number of price item parameter groups whose information can be cached in the memory. Yes
    SQ Recalculation Required Used to indicate whether the SQIs in an aggregated billable charge must be recalculated while executing the C1-TXNCU batch. The valid values are:

    • Y

    • N

    Note: If you do not specify the value for this option type or if you set the value to N, the system will not recalculate the SQIs in an aggregated billable charge.
    		 No
    Transaction Detail Account Validation Used to indicate whether the account must be validated during the transaction validation process. The valid values are:

    • Y

    • N

    Note:

    If you set this option type to N, the system overrides the transaction's account identifier type, account identifier, and division with the first derived account's account identifier type, account identifier, and division, respectively.

    If you do not specify the value for this option type, the system will validate the account during the transaction validation process.

    		 No
    Populate Summary Table Batch Description Used to specify the description for the batch which is used for adding a summary record in the CI_​TXN_​DTL_​PRITM_​SUMMARY table. For example, Populate CI_​TXN_​DTL_​PRITM_​SUMMARY Table. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes (Conditional)
    Note: This data is required when the Use C1-TXNPS During Transaction Aggregation option type is set to true.
    Find Price Item Pricing Batch Description Used to specify the description for the batch which is used for finding the price item pricing for transactions in the transaction aggregation cycle. For example, Price Item Pricing Verification. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes
    Update Transaction Status Batch Description Used to specify the description for the batch which is used for updating the status of the transactions (for which the error has occurred) in the transaction aggregation cycle. For example, Update Status. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes
    Service Quantity Calculation Batch Description Used to specify the description for the batch which is used for creating the billable charges for transactions in the transaction aggregation cycle. For example, Service Quantity Calculation. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes
    Transaction Completion Batch Description Used to specify the description for the batch which is used for updating the status of the transactions in the transaction aggregation cycle. For example, Mark Completion. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes
    Cleanup Unwanted Data Batch Description Used to specify the description for the batch which is used for updating or deleting billable charges created for transactions in the transaction aggregation cycle. For example, Clean Up. This description appears in the error message when the transaction aggregation batches are not executed in the specified sequence. Yes
    Use C1-TXNPS During Transaction Aggregation Used to indicate whether you want to use an alternative transaction aggregation process when the aggregation ratio is low. The valid values are:

    • true

    • false

    Note: If you set this option type to true, you need to execute the following batches in the specified order in the transaction aggregation cycle:

    1. Flush All Caches (F1-FLUSH)

    2. Refresh Pricing (C1-TXNRP)

    3. Header Validation (C1-TXNHV)

    4. Validate Transaction and Derive Price Item (C1-TXNIP)

    5. Populate CI_​TXN_​DTL_​PRITM_​SUMMARY Table (C1-TXNPS)

    6. Price Item Pricing Verification (C1-TXNVP)

    7. Update Status (C1-TXNEX)

    8. Service Quantity Calculation (C1-TXNSQ)

    9. Mark Completion (C1-TXNCM)

    10. Clean Up (C1-TXNCU) with the Request Type parameter set to EROR

    		No
  7. Enter the values for the required option types in the Feature Configuration screen.
  8. Click the Save button in the Page Title area.
    The changes made to the feature configuration are saved.