Removing Custom Transaction Types

When a custom transaction type is installed as part of a bundle, it can also be removed, even if instances of that transaction type exist. You can remove the type by uninstalling the bundle. Additionally, a bundle update can remove the type.

This behavior differs from how the system treats transaction types that were created in the UI. Transaction types created in the UI cannot be deleted if an instance of the type exists.

When a bundle operation is used to delete a transaction type, the system takes the following actions with any existing instances of that transaction type:

• The transactions are migrated to a new transaction type called Deprecated Custom Transaction.

• The transactions are locked to editing, although they can still be voided.

• If the transactions are in open periods, they can be deleted.

• Body fields are added to the transaction showing:

  • The name of the custom transaction type that was deleted.

  • The status of the transaction at the time the transaction type was deleted.

• Associated printing templates are deleted.

• Custom fields are discarded unless they are related to a custom segment that has GL impact.

To see a list of transactions that were instances of deleted custom transaction types, use the Transaction search type. Set the Type field to Deprecated Transaction Type.

For more information about custom transactions, see Custom Transactions.

Related Topics

• Custom Transaction Types in Bundles
• Pre-Bundling Checklist
• Including a Custom Transaction Type in a Bundle
• Other Suggested Objects
• Post-Installation Steps
• Accounting Preferences for Custom Transactions Applied to a Bundle

General Notices