[Internal] Maintaining Transaction Upload Templates

Knowledge Center > Zuora RevPro > [Internal] Zuora RevPro Integration Overview > [Internal] Maintaining Transaction Upload Templates

[Internal] Maintaining Transaction Upload Templates

Prior to extracting the data from Zuora business objects, you must create a Transaction Upload Template or use an existing template in Zuora RevPro. The fields in the Zuora Central can be mapped to the destination staging table in Zuora RevPro based on the field mapping rules in the Transaction Upload Templates.  

Take the following steps to create a Transaction Upload Template:

  1. Create Transaction Upload Template Definition
  2. Manage Field Mapping

Create Transaction Upload Template Definition

To create the template definition for a Transaction Upload Template:

  1. Click icon-menu.png in the Zuora RevPro UI.
  2. Click Transactions/Cost in the File Upload section. 
  3. In the Templates section, click icon-plus.png to create a new template. 
  4. Complete the fields in the Template Definition tab.template definition.png
    • RC Grouping Rule: Select an RC grouping template from the dropdown list. The available options are the templates you defined in the RC Grouping Template in the Policies section.
    • Name: Enter a name for this template. This name will be used in the Create a data extraction job REST API.
    • (Optional) Description: Enter the description for this template.
    • Enabled: Determines whether to enable this template upon creation. The default value is Yes.
    • Is Review Required?: Determines if the transaction upload data that is loaded from the UI needs to be reviewed before the data collection is triggered. The default value is No
    • File Type: Select the file format to download the mapping template. The following formats are supported:
      • CSV
      • Text
    • Date Format: Select a format in which the date is displayed.
    • Start Row: Enter an integer that determines where the data starts in the file and if the header should be considered. If the value for the Start Row field is 1, it means the first row in the file is where the data starts. If the value is set to 2, it means the file contains a header line and the data starts from the second row.
  5. Click icon_save.png to save the template.

Manage Field Mappings

To modify the field mapping rules for a template:

  1. In the Templates table, hover over the template you created and click icon-edit.png to edit the template.
  2. Click the Field Mapping tab in the Edit Transaction Upload Template page.
  3. Click icon-greenplus.png to create a new field mapping entry or click an existing value to modify the field mapping rules. You can eithor use the standard data mapping to define field mapping rules or customize data mapping.
    • Seq: The sequence number of the field in the data mapping. The Seq field specifies the field mapping order. Note that you are not allowed to specify the sequence numbers for the custom fields that are already used by the source data. 
    • Staging Field Name: The corresponding Zuora RevPro staging field used in the staging table. You can also customize this field. See customize data mapping for more information.
    • Input Value Label: The label name of the custom field you defined in Zuora Settings. You can also customize this field. See customize data mapping for more information.
    • Input Value Type: The data type of the custom field. The following data types are supported:  Note that Zuora RevPro does not support the Picklist data type.
      • Character
      • Number
      • Date
    • Count: Set to No by default.
    • Sum: Set to No by default.
  4. (Optional) Hover over the row of the field you want to remove and click icon_delete.png to remove this field from the field mapping table. 
  5. Click icon-greensave.png to save the field mapping rules.

When you have finished the Transaction Upload Template creation, you can use the Create a data extraction job REST API to extract the desired data from Zuora Central.

Last modified


This page has no custom tags.


(not set)