Custom Transaction Type Classification Fields
Classification fields, including the Mandatory boxes, are not available for the sales and purchase custom transaction types. For sales and purchase transaction types, class, department, and location and determined automatically based on the features and preferences enabled in your account. You can use form customization to configure whether classification fields are available for sales and purchase custom transactions.
For each transaction type, you can decide whether instances of the type include fields for class, department, and location.
Your choices for each of these fields are as follows:
-
None – (Default choice) The field is not used.
-
Header – The field is displayed on the transaction’s body.
-
Lines – The field is a column in the transaction’s Lines sublist.
For each field, you can also check a Mandatory box. If you check this box, users entering transaction instances are required to enter a value for the field.
Your choices about these fields are all reflected on the standard form for the transaction type. Your choices are also reflected in the default configuration of any custom forms you create, although you can make changes to the custom forms. For example, on a custom form, you can hide any of the classification fields, even if the transaction type was configured to make the field visible and mandatory. In this manner, you can bypass the transaction type’s settings.
Your custom transaction type can be associated with a plug-in implementation. If it is, consider the logic of the plug-in implementation before setting these fields. Specifically, the plug-in implementation may set line values for class, department, or location. If it does, you must set the Class, Department, or Location list to Lines. If you do not, the values provided by the plug-in are not used.
You can set values for the classification fields both when you create a custom transaction type and when you edit one. For details, see Creating a Custom Transaction Type and Editing a Custom Transaction Type.
For more information about the classification fields, see the following topics:
Impact of Global Preferences
The choices that you make on the custom transaction type for class, department, and location override your global accounting preferences. These preferences are set at Setup > Accounting > Accounting Preferences. However, if your transaction type’s Mandatory setting is less restrictive than your global accounting preferences, the system displays a warning. In this case, you can dismiss the warning and save the less-restrictive setting.
Classification Fields in Numbering
If you configure your transaction type to include the Location field on the transaction header, you may also want to refer to location in the autonumbering scheme for instances of this transaction type. Similarly, if you have a OneWorld account, you can refer to subsidiary when configuring your autonumbering sequence. For details, see Numbering for a Custom Transaction Type.
Behavior of Classification Fields Following Edits
When you edit an existing custom transaction type, you can change the settings related to class, department, and location. Any changes you make affect existing instances of the transaction type, as well as new ones. If you make changes, note the following:
-
If you move a field from the Lines sublist to the header, the new header field is populated only if all of the fields on the transaction instance’s Lines sublist shared the same value. Otherwise, the field’s value is not defined. If you change the location back to Lines, the former values are restored.
-
If you choose to make a field mandatory that was not previously required, existing transaction instances may not have the required value. However, a user editing one of these instances is required to enter a value before being permitted to save changes.
Related Topics
- Creating and Editing Custom Transaction Types
- Custom Transaction Styles Overview
- Creating a Custom Transaction Type
- Editing a Custom Transaction Type
- Locked Custom Transaction Types
- Custom Fields in Custom Transaction Types
- Numbering for a Custom Transaction Type
- Account Field Setup for Custom Transaction Types
- Statuses for a Custom Transaction Type
- Creating Links for a Custom Transaction Type
- Adding Custom Forms for a Custom Transaction Type
- Permissions for Custom Transaction Instances
- Adding Translations for a Custom Transaction Type