Using Custom Attributes

When transmission acknowledgment builds the routing file, it includes any custom attributes that are configured in Partner Profiles for the partner and transmission being processed. An attribute hierarchy is used to determine the method of delivering the custom attributes. The order is:
  • Partner
  • Transmission
  • Global

If identically named attributes exist at multiple levels of the Partner Profiles configuration, the actual value delivered comes from the top of the hierarchy (partner). This needs to be considered when setting up the Partner Profiles configuration.

For example, an attribute named mode has the values: custom, charmed, and strange. If the global specification for this attribute is charmed and no partner nor transmission specification for MODE exists, the custom attribute delivered to the routing file is charmed, as specified globally. If the transmission specification happens to be custom, the global value is overridden and custom is delivered to the routing file. If the partner specification is strange, it overrides the transmission and global values and strange is delivered to the routing file for the attribute named mode.

The transmission acknowledgment task collects all attributes at all levels for delivery to the routing XML file. To view the output XML for the routing file, see File and XML Formats.
Note: Custom attributes for other levels, such as endpoint attributes, are not supported for transmission acknowledgment routing.
Use symbolic substitution values when specifying any custom attributes. Table 1 describes the custom attribute symbolic substitution values that are supported by the transmission acknowledgment task.
Table 1. Symbolic Substitution Values
Symbolic Value Description
%Filename% Customer transmission name
%ReceivedFilename% Received transmission name
%TestFile% Test indicator
%DThhmma% UTC based transmission creation time, where:
hh
is the hour
mm
are the minutes
a
indicates AM or PM
%DTyyyyMMdd% UTC based transmission creation date, where:
yyyy
is the 4 digit year
MM
is the 2 digit month
dd
is the 2 digit day
%DestRT% Receiving point routing number
%OrigRT% Sending point routing number
%ItemCount% Total transmission transaction count
%FileAmt% Total transmission amount derived by subtracting the debit amount from the credit amount
%FileDebitAmt% Total transmission debit amount
%FileCreditAmt% Total transmission credit amount