Copying a Transaction Record Type

Instead of creating a transaction record type from scratch, you can create a new transaction record type using an existing transaction record type. This is possible through copying a transaction record type. On copying of a transaction record type, the details including the input or output parameters and temporary fields are also copied to the new transaction record type. You can then edit the details, if required.

Prerequisites

To copy a transaction record type, you should have:

  • Transaction record type (whose copy you want to create) defined in the application

  • Validation algorithm defined using the C1-RULE-VAL algorithm type

  • Transaction Information String algorithm defined using the C1-TXDETINFO algorithm type

  • Fields (that you want to use as input or output parameter) defined in the application

Procedure

To copy a transaction record type:

  1. Search for the transaction record type in the Transaction Record Type screen.
  2. In the Search Results section, click the Copy (The Duplicate Icon) icon in the Copy column corresponding to the transaction record type whose copy you want to create.

    The Transaction Record Type screen appears. It contains the following fields:

    Field Name Field Description Mandatory (Yes or No)
    Transaction Source Used to indicate the transaction source for which you want to define the transaction record type.
    Note:

    The Search (The Search Icon) icon appears corresponding to this field. On clicking the Search icon, the Search Transaction Source window appears where you can search for the required transaction source.

    		 Yes
    Transaction Record Type Used to specify the transaction record type.
    Note: You cannot specify any special character except underscore (_​) in the transaction record type.
    		 Yes
    Description Used to specify the description for the transaction record type. Yes
    Rule Type Used to specify the rule type.
    Note: You cannot specify any special character except underscore (_​) in the rule type.
    		 Yes
    Rule Type Description Used to specify the description for the rule type. Yes
    Rule Validation Algorithm Used to specify the validation algorithm that will be triggered when a rule is defined using the rule type.
    Note: This algorithm checks whether:

    • The values specified against the output parameters exist in the system

    • The same price item parameter (for example, PCD1_​1_​1_​VAL) is not used multiple times for a division, account, and price item combination

    The Search (The Search Icon) icon appears corresponding to this field. On clicking the Search icon, the Algorithm Search window appears where you can search for the required algorithm.

    		 No
    Info String Algorithm Used to specify the algorithm that will generate the information string which appears in the Transaction Information column throughout the application.
    Note: This algorithm concatenates the fields (related to the transaction) and delimiters specified as parameters in the algorithm.

    The Search (The Search Icon) icon appears corresponding to this field. On clicking the Search icon, the Algorithm Search window appears where you can search for the required algorithm.

    		 No
    Maximum Accounts to be charged Used to indicate the maximum number of accounts which can bear the charges for a transaction. The valid values are:

    • 01

    • 02

    • 03

    • 04

    • 05

    • 06

    • 07

    • 08

    • 09

    • 10

    Note: At present, the system supports maximum 10 accounts which can bear the charges for a transaction.
    		 Yes
    Maximum Price Items to be mapped Used to indicate the maximum number of price items to which a transaction can be mapped for each account. The valid values are:

    • 01

    • 02

    • 03

    • 04

    • 05

    • 06

    • 07

    • 08

    • 09

    • 10

    Note: At present, the system supports maximum 10 price items to which a transaction can be mapped for each account.
    		 Yes
    Maximum Price Item Parameters Used to indicate the maximum number of parameters that can be used with each price item to determine the price item pricing. The valid values are:

    • 00

    • 01

    • 02

    • 03

    • 04

    • 05

    • 06

    • 07

    • 08

    • 09

    • 10

    • 11

    • 12

    • 13

    • 14

    • 15

    Note: At present, the system supports maximum 15 parameters that can be used with each price item to determine the price item pricing.
    		 Yes

    In addition, this screen contains the following two sections:

    • Input/Output Parameters - Enables you to select the transaction detail fields that you can use as input or output parameter while defining a rule. It contains the following fields:

      Field Name Field Description Mandatory (Yes or No)
      Rule Input/Output Used to indicate whether you want to use the transaction detail field as input or output parameter. No
      Transaction Field Displays the transaction field name. Not applicable
      Business Label Used to specify a business label for the user defined fields.
      Note: The business label appears when you add, copy, or view a transaction in the Transaction Details screen. The label changes depending on the transaction source and record type combination that you have selected.
      		 No
      Note: At present, you can use the following transaction fields as input or output parameter while defining a rule - Account Identifier (ACCT_​NBR), Account Identifier Type (ACCT_​NBR_​TYPE_​CD), Division (CIS_​DIVISION), Currency Code (CURRENCY_​CD), Customer Reference Number (CUST_​REF_​NBR), Do not Aggregate Switch (DO_​NOT_​AGG_​SW), External Reference Number (EXT_​TXN_​NBR), Credit/Debit Indicator (HOW_​TO_​USE_​TXN_​FLG), Manual Entry (MANUAL_​SW), Transaction Amount (TXN_​AMT), Transaction Date (TXN_​DTTM), Transaction Record Type (TXN_​REC_​TYPE_​CD), Transaction Source (TXN_​SOURCE_​CD), Transaction Upload Date (TXN_​UPLOAD_​DTTM), Transaction Volume (TXN_​VOL), Additional Amount 1 (UDF_​AMT_​1), Additional Amount 2 (UDF_​AMT_​2), Additional Amount 3 (UDF_​AMT_​3), Additional Amount 4 (UDF_​AMT_​4), Additional Amount 5 (UDF_​AMT_​5), Additional Amount 6 (UDF_​AMT_​6), Additional Amount 7 (UDF_​AMT_​7), Additional Amount 8 (UDF_​AMT_​8), Additional Amount 9 (UDF_​AMT_​9), Additional Amount 10 (UDF_​AMT_​10), Additional Data 1 (UDF_​CHAR_​1), Additional Data 2 (UDF_​CHAR_​2), Additional Data 3 (UDF_​CHAR_​3), Additional Data 4 (UDF_​CHAR_​4), Additional Data 5 (UDF_​CHAR_​5), Additional Data 6 (UDF_​CHAR_​6), Additional Data 7 (UDF_​CHAR_​7), Additional Data 8 (UDF_​CHAR_​8), Additional Data 9 (UDF_​CHAR_​9), Additional Data 10 (UDF_​CHAR_​10), Additional Data 11 (UDF_​CHAR_​11), Additional Data 12 (UDF_​CHAR_​12), Additional Data 13 (UDF_​CHAR_​13), Additional Data 14 (UDF_​CHAR_​14), Additional Data 15 (UDF_​CHAR_​15), Additional Data 16 (UDF_​CHAR_​16), Additional Data 17 (UDF_​CHAR_​17), Additional Data 18 (UDF_​CHAR_​18), Additional Data 19 (UDF_​CHAR_​19), Additional Data 20 (UDF_​CHAR_​20), Additional Data 21 (UDF_​CHAR_​21), Additional Data 22 (UDF_​CHAR_​22), Additional Data 23 (UDF_​CHAR_​23), Additional Data 24 (UDF_​CHAR_​24), Additional Data 25 (UDF_​CHAR_​25), Additional Data 26 (UDF_​CHAR_​26), Additional Data 27 (UDF_​CHAR_​27), Additional Data 28 (UDF_​CHAR_​28), Additional Data 29 (UDF_​CHAR_​29), Additional Data 30 (UDF_​CHAR_​30), Additional Data 31 (UDF_​CHAR_​31), Additional Data 32 (UDF_​CHAR_​32), Additional Data 33 (UDF_​CHAR_​33), Additional Data 34 (UDF_​CHAR_​34), Additional Data 35 (UDF_​CHAR_​35), Additional Data 36 (UDF_​CHAR_​36), Additional Data 37 (UDF_​CHAR_​37), Additional Data 38 (UDF_​CHAR_​38), Additional Data 39 (UDF_​CHAR_​39), Additional Data 40 (UDF_​CHAR_​40), Additional Data 41 (UDF_​CHAR_​41), Additional Data 42 (UDF_​CHAR_​42), Additional Data 43 (UDF_​CHAR_​43), Additional Data 44 (UDF_​CHAR_​44), Additional Data 45 (UDF_​CHAR_​45), Additional Data 46 (UDF_​CHAR_​46), Additional Data 47 (UDF_​CHAR_​47), Additional Data 48 (UDF_​CHAR_​48), Additional Data 49 (UDF_​CHAR_​49), Additional Data 50 (UDF_​CHAR_​50), Amount 1 Currency Code (UDF_​CURRENCY_​CD_​1), Amount 2 Currency Code (UDF_​CURRENCY_​CD_​2), Amount 3 Currency Code (UDF_​CURRENCY_​CD_​3), Amount 4 Currency Code (UDF_​CURRENCY_​CD_​4), Amount 5 Currency Code (UDF_​CURRENCY_​CD_​5), Amount 6 Currency Code (UDF_​CURRENCY_​CD_​6), Amount 7 Currency Code (UDF_​CURRENCY_​CD_​7), Amount 8 Currency Code (UDF_​CURRENCY_​CD_​8), Amount 9 Currency Code (UDF_​CURRENCY_​CD_​9), Amount 10 Currency Code (UDF_​CURRENCY_​CD_​10), Additional Date 1 (UDF_​DTTM_​1), Additional Date 2 (UDF_​DTTM_​2), Additional Date 3 (UDF_​DTTM_​3), Additional Date 4 (UDF_​DTTM_​4), Additional Date 5 (UDF_​DTTM_​5), Additional Numeric Data 1 (UDF_​NBR_​1), Additional Numeric Data 2 (UDF_​NBR_​2), Additional Numeric Data 3 (UDF_​NBR_​3), Additional Numeric Data 4 (UDF_​NBR_​4), Additional Numeric Data 5 (UDF_​NBR_​5), Additional Numeric Data 6 (UDF_​NBR_​6), Additional Numeric Data 7 (UDF_​NBR_​7), Additional Numeric Data 8 (UDF_​NBR_​8), Additional Numeric Data 9 (UDF_​NBR_​9), Additional Numeric Data 10 (UDF_​NBR_​10), Additional Numeric Data 11 (UDF_​NBR_​11), Additional Numeric Data 12 (UDF_​NBR_​12), Additional Numeric Data 13 (UDF_​NBR_​13), Additional Numeric Data 14 (UDF_​NBR_​14), Additional Numeric Data 15 (UDF_​NBR_​15), Additional Numeric Data 16 (UDF_​NBR_​16), Additional Numeric Data 17 (UDF_​NBR_​17), Additional Numeric Data 18 (UDF_​NBR_​18), Additional Numeric Data 19 (UDF_​NBR_​19), Additional Numeric Data 20 (UDF_​NBR_​20).

    • Temporary Fields - Enables you to select non-transactional fields that you can use as input or output parameter while defining a rule. It contains the following fields:

      Field Name Field Description Mandatory (Yes or No)
      Temporary Field Used to indicate the non-transactional field that you want to use as input or output parameter.
      Note:

      The Search (The Search Icon) icon appears corresponding to this field. On clicking the Search icon, the Transaction Record Type Tempo Field Search window appears.

      		 No
  3. Enter the required details.
    Note: You can search for an algorithm by clicking the Search (The Search Icon) icon corresponding to the respective field.
  4. Select the check box corresponding to the transaction fields that you want to use as input or output parameters.
  5. If required, you can select a non-transactional field as input or output parameter in the Temporary Fields section.
    Note:

    You can search for a field by clicking the Search (The Search Icon) icon corresponding to the respective field.

    If you want to add more than one temporary field to the transaction record type, click the Add (The Add Icon) icon and then repeat step 5. However, if you want to remove a temporary field from the transaction record type, click the Delete (The Delete Icon) icon corresponding to the temporary field.

  6. Click Save.
    The new transaction record type is defined.

Related Topics

For more information on... See...
How to search for a transaction record type Searching for a Transaction Record Type