A custom transaction instance can have a predefined transaction type prefix and a location or subsidiary prefix. The following example demonstrates how to set up a custom purchase type transaction to include both a transaction type prefix and a location prefix. It also describes how to set the initial number NetSuite uses for the autogenerated number.
Transaction Type Prefix
TO set up the transaction type prefix in the custom transaction type record. In the following example, on the Transaction Number sublist:
- The Use Location box is checked. With this box checked, the resulting transaction number includes the location prefix if one is defined on the location record.
- The Prefix field has a transaction type prefix of PURCH. This prefix is added to the transaction numbers of all instances of this transaction type. In the generated transaction number, this prefix precedes the location (or subsidiary) prefix if one is used.
- The Update Initial Number box is checked, and an initial number is defined in the Initial Number field. This setting is optional and defines the number that should be used for the first transaction instance. If you do not enter a value, the system (in most cases) starts the sequence at 1. This initial number is used for transactions that do not use a location (or subsidiary) prefix. If a location (or subsidiary) prefix is used, this number is ignored and the initial number setting on the location (or subsidiary) record is used instead.
Location Prefix
To set up the location prefix on the location record.
On the location record in the following example:
- The Transaction Number Prefix has a location prefix of KWLOC. prefix is added to the transaction numbers of all instances that are associated with this location. In the generated transaction number, this prefix follows the location (or subsidiary) prefix if one is used.
- The Transaction Numbers subtab, the Update Initial Number box is checked for the transaction type, and an initial number is defined in the Initial Number field. This setting is optional and defines the initial number that should be used for the first transaction instance that uses the location. If you do not enter a value, the system (in most cases) starts the sequence at 1. If a value is entered here, it overrides the initial number on the custom transaction type record, if one is defined.
