Pre-Bundling Checklist
Before bundling your custom transaction type, you may want to review the type. 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 includes statuses, check that the statuses are set up correctly. For example, you may want to make sure that the posting flag has been set as needed for each status. After the bundle is installed, the Statuses sublist cannot be modified in the target account. This limitation exists even if you do not select the Lock On Install option for the transaction type. You can always make changes to the type’s statuses in the source account and update the bundle. However, users in the target account are never able to change existing statuses or add new statuses. For more information about statuses, see Statuses for a Custom Transaction Type.
Class, Department, and Location
Check that your custom transaction type has the required 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 of the custom transaction type. This subtab lists all custom body fields and column fields that are 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 the name of the field 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.