After setting up the data file, the next step is to define where the data will be delivered. This includes creating client staging and transaction tables. A client staging table is a temporary storage area where transaction data is imported, validated, and prepared for matching.

Once processed, the data is moved from the client staging table to the client transaction table. This table holds the structured data used for matching, which makes it easier to match across datasets.

To create a staging table:

  1. Select Configure in the navigation pane.
  2. Select Staging Tables, then Add to create a new table.
    Provide a relevant name, such as Cash_GL_Staging.
  3. Select OK.
    The created table displays.
  4. Next, select Add to add fields and their data types, then Save.
    The field names, data types, and order must exactly match those in the transaction file​.

Understanding data types

It's important to understand the proper data types for each field:

  • String: Most fields are set as string data types, allowing you to use the filters in Matching, such as Contains and Starts with.
  • Date: Set date as a data type to the date field. It's useful to compare it with other date fields.
  • Monetary amounts: It's recommended to define monetary fields as a float data type, and for the SQL Data Type, select money. These fields could include a debit and credit amount or a total amount. Debits and credits are the commonly used.

Note: You'll need to change the data if your file has different debit and credit fields but no total amount field. Anaplan needs a single amount field to calculate differences.

You should also add any other fields from the transaction file. These are used for filtering or comparison purposes. Keep in mind that only fields with similar data types can be compared. For example, Fedfile_Staging client staging table may closely represent an actual FED or Federal Reserve file. Such Federal Reserve files often have multiple fields, including credit, debit, and total amounts. All of these fields are set as floating point values with the money data type.

You can also use fields for non-monetary amounts, such as floats for inventory units or aging in days. You can't compare different fields if you change the SQL data type. For example, if you want to compare aging in days, the field should be a decimal, float, or another non-monetary data type. This can be used in matching rules.

Set a primary key

You may need to set one field as the primary key. Only one main key is allowed, and it isn't required. You can use a field, such as the transaction ID, as a unique identifier. If you don't set a primary key, Anaplan will create one in the background. It'll be a self-incrementing ID with no uniqueness, for example, 1, 2, 3, 4, etc.

Nullable fields

The Nullable column is essential. If you want to enable data import without specific fields, such as missing dates, you can mark those fields as Nullable. However, including key information, such as the amount, is recommended. For example, if you import data with only a transaction ID and no other details, there won't be much you can do with it.

Select here to view a video about creating staging tables .