Master Data
This documentation is incomplete.
All saleable products are created as inventory items in the item master. The item master is a master data table that contains all the information about materials/items related to sales, purchasing, manufacturing, etc.
You can maintain the sales price information for each item either in the item master or in the item price list.
The combined item master and price information are created as a product in the POS module. The product also contains POS item category information assigned in the item master.
The POS product table contains all the information about the product required to create a sales order line.
This approach allows you to operate POS in any simple hardware device without requiring several database connections to the central ERP system. The POS can be used in any POS terminal, desktop computer, laptop, or mobile device without an active internet connection.
Product
A product is an item available for sale. It contains item master information, item price information, and POS item category information.
Products can be created in 2 ways in the system :
- Importing item master and item price information from ERP.
- Manually creating a product in the POS module. You can also copy an existing product to create a new product.
You can also create store-specific products for the same inventory item, i.e., create the same product in different stores with different price information.
To view/create/update a Product, navigate to the "Product" search screen from your dashboard/favorite.
Enter the Product details or any other criteria in the search form and click on the search button to view an existing Product. Click on create a new button to create a new Product; by manually entering all the information. Copying an existing Product to a new One is always better than manually entering all the data to create a new One.
If you click on the create a new button, the system will open a simple step form to create a new item. You can click on the detail right bottom to view all the fields available for the object.
The application will fetch all the server data and take you to the search result screen. The search result screen looks a bit different on desktop and mobile devices.
The system will show all the products if you click the search button without entering any organization/product details. If your organization configures any field mandatory for search, you must enter those fields into search products.
To view the search result in a table format, click on the table icon in the bottom left corner.
To open a specific Product, click on the menu of that record, and click on view/fetch & view.
You can also click on the expand icon against any item on the search result screen to view the Product header details such as item name, item description, manager, etc.
The system will fetch all the data related to the selected store. The Product details are shown either right to the search result screen or on a separate screen, depending on the device size.
Item Number: An item number is a unique identifier for an item. It is used to identify the item in the system. Item numbers are created in the item master and assigned to various inventory organizations.
Store Code: A store code is a unique identifier for a store. The store is not a mandatory field in the product. However, if you want to create a product with different price information across stores, you must enter the store code in the product master.
List Price: List price is the price used to calculate sales. The sales price is a mandatory field in the product master, and the value is shown on the POS product screen.
The system calculates the total line price by multiplying the list price by the quantity.
Item Description: Item and long item descriptions are copied from the item master. However, you can edit the item description in the product master.
Scroll left, right, up, and down to view all the details. The Product line and details are shown in a separate tab. The default configuration shows fields in various functional groups, such as
- Finance
- Entity
- Reference
- Data
- Control
- Etc
You can configure the application to show which fields should be shown under which group. You can also create new groups as per your business requirements.
All Fields
| Sequence | Name | Label | InputType | Field Group |
|---|---|---|---|---|
| 10 | vvInvOrgCode | Inv Org Code | deferredSelect | ENTITY |
| 10 | vvInvOrgId | Inv Org Id | deferredSelect | REFERENCE |
| 20 | subInventoryId | Sub Inventory Id | InputType.text | REFERENCE |
| 30 | subInventory | Sub Inventory | InputType.textField | ENTITY |
| 40 | subInventoryType | Sub Inventory Type | InputType.select | CONTROL |
| 50 | mdmInventoryOrgId | Mdm Inventory Org Id | deferredSelect | PLANNING |
| 60 | subInventoryClass | Sub Inventory Class | InputType.select | ENTITY |
| 70 | description | Description | InputType.textField | DEFAULT |
| 80 | terminalControl | Terminal Control | InputType.textField | ENTITY |
| 90 | allowNegativeBalanceCb | Allow Negative Balance Cb | InputType.switchField | DEFAULT |
| 100 | defaultCostGroup | Default Cost Group | InputType.textField | PLANNING |
| 110 | shipmentPickPriority | Shipment Pick Priority | InputType.number | ENTITY |
| 120 | materialAcId | Material Ac Id | deferredSelect | REFERENCE |
| 130 | materialOhAcId | Material Oh Ac Id | deferredSelect | REFERENCE |
| 140 | overheadAcId | Overhead Ac Id | deferredSelect | REFERENCE |
| 150 | resourceAcId | Resource Ac Id | deferredSelect | REFERENCE |
| 160 | ospAcId | Osp Ac Id | deferredSelect | REFERENCE |
| 170 | expenseAcId | Expense Ac Id | deferredSelect | REFERENCE |
| 180 | status | Status | InputType.textField | CONTROL |
| 190 | revNumber | Rev Number | InputType.textField | DATA |
| 240 | glAcProfileHeaderId | Gl Ac Profile Header Id | deferredSelect | REFERENCE |
| 250 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
| 260 | srcEntityId | Src Entity Id | InputType.text | REFERENCE |
| 5200 | createdBy | Created By | InputType.text | REFERENCE |
| 5210 | creationDate | Creation Date | InputType.text | REFERENCE |
| 5220 | lastUpdatedBy | Last Updated By | InputType.text | REFERENCE |
| 5230 | lastUpdateDate | Last Update Date | InputType.text | REFERENCE |
Refresh For Off-line
Click on the "Refresh Local Data" button in the top right corner of the product search screen to import all product data from the server.
The program completes below two steps:
- Deletes all existing product data in the local database.
- Imports all product data from the server to the local database.
Item Master
Refer to item master for more details on item master. Similarly, refer to organizations item for more details on organization item details.
Customer
A customer is a person or an internal/external organization that purchases products or services from a business organization.
In inoERP, customers are created in 2 different modules :
- POS: A simple customer object that contains the basic information about the customer used only in the POS module.
- Master Data Management: A generic customer object used in all ERP modules - i.e., Sales and Distribution, Receivable, Purchasing, Manufacturing, Project, etc.
Refer to customer master for more details.
To view/create/update a customer, navigate to the "customer" search screen from your dashboard/favorite.
Enter the customer details or any other criteria in the search form and click on the search button to view an existing customer.
Click on create a new button to create a new customer; by manually entering all the information. Copying an existing customer to a new customer is always better than manually entering all the data to create a new customer.
If you click on the create a new button, the system will open a simple step form to create a new item. You can click on the detail right bottom to view all the fields available for the object.
The application will fetch all the server data and take you to the search result screen. The search result screen looks a bit different on desktop and mobile devices.
The system will show all the customers if you click the search button without entering any organization/customer details. If your organization has configured to make any field mandatory for search, you must enter those fields into search customers.
To view the search result in a table format, click on the table icon in the bottom left corner.
To open a specific customer, click on the menu of that record, and click on view/fetch & view.
You can also click on the expand icon against any item on the search result screen to view the customer header details such as first name, last name, loyalty card, etc.
The system will fetch all the data related to the selected store. The customer details are shown either right to the search result screen or on a separate screen, depending on the device size.
First Name: First name of the customer. If the customer is a person, the first name is the first name of the person. If the customer is an organization, the first name is the name of the organization. First name is a mandatory field.
Last Name: Last name of the customer. It is not a mandatory field.
Loyalty Card Id: Enter the loyalty card id of the customer. It is not a mandatory field. However, if you want to use the loyalty card feature, you must enter the loyalty card id.
Scroll left, right, up, and down to view all the details. The customer line and details are shown in a separate tab. The default configuration shows fields in various functional groups, such as
- Finance
- Entity
- Reference
- Data
- Control
- Etc
You can configure the application to show which fields should be shown under which group. You can also create new groups as per your business requirements.
All Fields
| Sequence | Name | Label | InputType | Field Group |
|---|---|---|---|---|
| 10 | vvInvOrgCode | Inv Org Code | deferredSelect | ENTITY |
| 10 | vvInvOrgId | Inv Org Id | deferredSelect | REFERENCE |
| 20 | subInventoryId | Sub Inventory Id | InputType.text | REFERENCE |
| 30 | subInventory | Sub Inventory | InputType.textField | ENTITY |
| 40 | subInventoryType | Sub Inventory Type | InputType.select | CONTROL |
| 50 | mdmInventoryOrgId | Mdm Inventory Org Id | deferredSelect | PLANNING |
| 60 | subInventoryClass | Sub Inventory Class | InputType.select | ENTITY |
| 70 | description | Description | InputType.textField | DEFAULT |
| 80 | terminalControl | Terminal Control | InputType.textField | ENTITY |
| 90 | allowNegativeBalanceCb | Allow Negative Balance Cb | InputType.switchField | DEFAULT |
| 100 | defaultCostGroup | Default Cost Group | InputType.textField | PLANNING |
| 110 | shipmentPickPriority | Shipment Pick Priority | InputType.number | ENTITY |
| 120 | materialAcId | Material Ac Id | deferredSelect | REFERENCE |
| 130 | materialOhAcId | Material Oh Ac Id | deferredSelect | REFERENCE |
| 140 | overheadAcId | Overhead Ac Id | deferredSelect | REFERENCE |
| 150 | resourceAcId | Resource Ac Id | deferredSelect | REFERENCE |
| 160 | ospAcId | Osp Ac Id | deferredSelect | REFERENCE |
| 170 | expenseAcId | Expense Ac Id | deferredSelect | REFERENCE |
| 180 | status | Status | InputType.textField | CONTROL |
| 190 | revNumber | Rev Number | InputType.textField | DATA |
| 240 | glAcProfileHeaderId | Gl Ac Profile Header Id | deferredSelect | REFERENCE |
| 250 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
| 260 | srcEntityId | Src Entity Id | InputType.text | REFERENCE |
| 5200 | createdBy | Created By | InputType.text | REFERENCE |
| 5210 | creationDate | Creation Date | InputType.text | REFERENCE |
| 5220 | lastUpdatedBy | Last Updated By | InputType.text | REFERENCE |
| 5230 | lastUpdateDate | Last Update Date | InputType.text | REFERENCE |