Pre-Bundling Checklist
Before you bundle your custom transaction type, you might want to review it first. In particular, check the type’s settings for each of the following:
Transaction Style
Make sure that you have chosen the most appropriate list style for your custom transaction type. For example, you may have created a transaction type for which the entire GL impact should be determined by a Custom GL Lines plug-in implementation. For these types, the list style should be Header Only. For more details on list styles, see Custom Transaction Styles Overview.
Statuses
If your transaction type has statuses, check that they're set up correctly. For example, you’ll want to make sure the posting flag is set as needed for each status. After you install the bundle, you can't change the Statuses sublist in the target account. This limitation applies even if you don't select the Lock On Install option for the transaction type. You can always change the type’s statuses in the source account and update the bundle. However, users in the target account can't change existing statuses or add new ones. For more information about statuses, see Statuses for a Custom Transaction Type.
Class, Department, and Location
Make sure your custom transaction type has the right settings for the class, department, and location fields. For help with these fields, see Custom Transaction Type Classification Fields.
Custom Fields
Check the Custom Fields subtab on your custom transaction type. This subtab shows all custom body and column fields linked to the transaction type. If any of these fields should be omitted from the bundled version of the type, remove them before creating the bundle. To remove a field, click its name to open it for editing. On the Applies To subtab, cancel the selection of the custom transaction type. For more details about custom fields, see Custom Fields in Custom Transaction Types.