Overview

NorthScope allows users to create and edit inventory transaction classes. These records determine the prefix and numbering and also certain properties for inventory transactions. Inventory transaction class records do not integrate with the host system.

By default, one transaction class per transaction type (Adjustment, Production, Receipt and Transfer) is created in the system. These transaction classes are named as ‘Default’.

Step 1: Adding a New Inventory Transaction Class in NorthScope

To add a new inventory transaction class, expand the Inventory module and select Transaction Class. This opens the Transaction Class list view, which displays the inventory transaction classes configured in the system. Select New from the toolbar to open a new blank transaction class record.

Step 2: Assigning the Base Properties

A blank transaction class record is opened with the following base properties:

Transaction Type: Select the transaction type for the transaction class (Adjustment, Production, Receipt or Transfer). This property is required and it cannot be edited after the initial save.
Transaction Class: Enter the name for the transaction class. This property is required and it cannot be edited after the initial save. Duplicate Transaction Class names are not allowed.
Document Prefix: Enter a prefix that is combined with the document number to create the transactions ID for transaction belonging to this transaction class. This property is always editable.
Next Document Number: Enter a document number. This number is assigned to the first transaction created for the transaction class and it will auto increment by 1 for every new Transaction that is created. The number defaults to 10000, but this property is always editable.
Logo Location: Enter a file path to the logo image. The logo is used on all printed forms associated with the transactions that are assigned to the transaction class. This property is not required and it is always editable.

Once the base properties have been assigned. Click Save from the header toolbar to create the transaction class record.

Step 3: Assigning the Additional Properties

After saving the base properties, the following additional properties are displayed:

Auto-Create New Lots: Select if the transactions belonging to the transaction class should be allowed to create new lots (Allowed) or not (Not Allowed). The property is used as the default property value when transactions are being created, but the property can still be changed on the transaction record. This property is always editable.
Negative Available Balances: Select if the transactions belonging to the transaction class should be allowed to draw the lot balances negative (Allowed) or not (Not Allowed). This property is used as the default property when transactions for the transaction class are being created, but the property can still be changed on the transaction record. This property is always editable.
Single Date Management: Select if the transactions should use single date management. This property has a drop-down menu with the values “Yes” or “No” and defaults to “No”. If set to “Yes”, the GL Date on the transaction record view will be disabled and will always follow the transaction date.
Transaction Default: Select if the transaction class should be used as the default transaction class for the transaction (Yes/No). This property is always editable. Note that only one transaction class per transaction type can be set as the default and each transaction class must have a default transaction class.
Transaction Integration to Host System: Select if the transaction for the specified class should integrate with the host system or not ("Transaction with Journal Details" / "No Integration"). This property is required and always editable. if the company integration setup is set to “Immediate” or “Timed” for Inventory transactions and the Class level is set to “No Integration”, then neither the transaction or the journal details for the transaction will integrate to the host system. This also means that if the company integration setup is set to “None” for Inventory then no transactions will integrate to the host system no matter the property on the Transaction Class.
If no Host System is setup for the Company and the integration method is set to “No Integration”, the Transaction Integration property defaults to “No Integration” and the field is disabled. Current Transaction Classes set to “Transaction with Journal Details” will remain setup this way but when moved to “No Integration” the dropdown will be disabled. This field will be re-enabled if a Host System is added to the company setup.
Inactive: Select if the transaction class should be active (No) or inactive (Yes). Note that each transaction type must have at least one active transaction class.

The following properties are also displayed for Production type transaction classes:

Auto-Create New Lots – Inputs: Select if the transactions belonging to the transaction class should be allowed to create new lots (Allowed) or not (Not Allowed) for input type line items. This property is always editable.
Negative Available Balances – Inputs: Select if the transactions belonging to the transaction class should allow to draw the lot balances negative (Allowed) or not (Not Allowed) for input line items. This property is used as the default property when transactions for the transaction class are being created, but the property can still be changed on the Transaction record. This property is always editable.

Step 4: Selecting A Transaction Class

To select the transaction class for an inventory transaction, navigate to Inventory Transactions and click New. The drop-down menu displays all transaction classes that are currently assigned to be active. Selecting the transaction class opens a new blank transaction record. The transaction ID and properties are assigned based on the transaction class properties.

When adjustment transactions are created from the Cycle Count page, the default adjustment transaction class is used to create the transactions. When inventory transactions are imported from a file, the default transaction class is used, but the transaction class can also be defined in the transaction file, though this field is not required.

Browser not supported