Editing a Custom Transaction Type

Use the following procedure to make changes to an existing custom transaction type. Some fields, such as the Transaction Style field, cannot be changed after you have saved the type. Additionally, after transaction instances have been created, the Credit box cannot be changed.

You can change key fields such as Account, Filter Account Type, and Posting. When you edit those fields, the changed settings are not applied automatically to historical transactions. However, if you edit a historical transaction, the changes are applied and the GL impact of the transaction can change.

Note:

In some cases, a transaction type that was installed from a bundle may be locked to editing. In these cases, you cannot directly edit the transaction type as described in this topic. However, you can still make changes to certain aspects of the transaction type’s behavior. For details, see Locked Custom Transaction Types.

To edit a custom transaction type:

Go to Customization > Lists, Records & Fields > Transaction Types.
In the Edit column, click the name of the transaction type you want to edit.
Change any of the following values, as appropriate:
- Name – This value must be unique. As a best practice, enter a singular noun. (For certain locales, the system uses the plural form of the name in the transaction type’s List view.) When you make a change to the type’s name, the old name is no longer used, even for existing transaction instances.
- Account – The system displays the Account field only if the transaction type has a Transaction Style of Basic, Sales, or Purchase. In these cases, you can use the list to modify the offset account, which is the account to be debited or credited each time a user enters an instance of the transaction type. Any change you make to the Account field affects only those transaction instances created or edited after you save your change.
  
  The way this account is used varies depending on whether the Credit box is checked. For more information about the Account field and Credit box, see Account Field Setup for Custom Transaction Types.
- Allow Void Transactions Using Reversing Journals – This option enables users to create reverse journal entries for posting transactions. To use this option, you must have enabled the global Void Transactions Using Reversing Journals preference, which is available at Setup > Accounting > Accounting Preferences.
  
  Note:
  For sales and purchase transaction types, users can void only transactions that do not use inventory items.
- Class, Department, and Location – Use these fields to make changes to whether class, department, and location can be set on instances of this transaction type. Any changes you make affect existing transaction instances as well as new ones. For more details on these fields, see Custom Transaction Type Classification Fields.
The ID field is used to reference this transaction type during scripting. All IDs have a prefix that cannot be changed:
- Basic, Journal, and Header Only styles have a prefix of customtransaction.
- Purchase styles have a prefix of custompurchase.
- Sales styles have a prefix of customsale.
For information about best practices and naming conventions, see Conventions for Naming Custom Objects. For information about changing an existing ID, see Changing the ID of a Custom Object.
(Optional) To further define your custom transaction type, make changes on any of the following subtabs:
- Custom Fields – Create custom fields and automatically add them to the transaction type (and to any transaction type). Be aware that any custom field you create is available to be added to any standard or custom transaction type that exists in your system. For more information, see Custom Fields in Custom Transaction Types.
- Document Numbers – Configure autonumbering for the type. For more information, see Numbering for a Custom Transaction Type.
- Transaction Numbers – Configure autogenerated transaction numbering for the type. For more information, see Numbering for a Custom Transaction Type and Records and Transactions Available for Auto-Numbering
- Accounting – Configure account details for the type. The fields on the Accounting subtab apply to Basic, Sales, and Purchase Transaction Styles. In these cases, you can use the list to modify the offset account, which is the account to be debited or credited each time a user enters an instance of the transaction type. Any change you make to the Account field affects only those transaction instances created or edited after you save your change.
  
  The way this account is used varies depending on whether the Credit box is checked. For more information about the Account field and Credit box, see Account Field Setup for Custom Transaction Types.
- Statuses – Create posting and nonposting for statuses the type. When editing existing statuses, some limits exist. For more information, see Statuses for a Custom Transaction Type.
- Links – Create menu paths for the transaction type. For more information, see Creating Links for a Custom Transaction Type.
- Forms – Create custom entry forms for the transaction type. For more information, see Adding Custom Forms for a Custom Transaction Type.
- Permissions – Select the roles that should be permitted to work with instances of this custom transaction type. For more information, see Permissions for Custom Transaction Instances.
- Translation – Define translations for the custom transaction type’s name. This subtab is displayed only if the Multi-Language option is selected at Setup > Company > Enable Features, on the Company subtab. For more information, see Adding Translations for a Custom Transaction Type.
Click Save.

System Notes v2 for Custom Transaction Types

To access System Notes from the Custom Transaction types page, click System Notes located in the upper right of the page.

Custom Transaction configuration changes are logged using System Notes v2. For more information, see Viewing System Notes v2.

To edit a custom transaction type:

System Notes v2 for Custom Transaction Types

Related Topics