Transaction
To create an inventory transaction, you need to create an inventory transaction document. In inoERP, we follow the same process for all inventory-related transactions irrespective of the document (Sales Order, Purchase Order, Work Order, Project, etc.). The process is similar to SAP MIGO (there is no corresponding process in Oracle) with some extra features such as
- The transaction document creation (ex: planner activity) and transaction completion (ex: warehouse operator activity) can be managed by different employees
- You can use the approval process for all transaction documents
- A single transaction document can contain information from multiple source documents (i.e., a Single Shipping transaction document for multiple project numbers or a Single purchasing receiving document for multiple purchase orders)
In the Project module, the application provides four different Transaction
1. Project Issue - Issue material to a project from an inventory stock/onhand
2. Project Return - Receive material from a project to an inventory stock/onhand
3. Project Shipment - Ship a material from the project to a customer
4. Project Shipment Return - Receive material from a customer against a project
Transaction document consists of
- a header
- several lines that contain item and quantity information
- serial details for serial controlled items
- lot number details for lot controlled items
Resource Transaction
You can charge resources to a project to record hours spent and corresponding expenses incurred by various resources.
To create/view/update the resource transaction, navigate to the "resource transaction" screen from your dashboard/favorite.
Enter the resource transaction details or other criteria in the search form and click on the search button to view an existing resource transaction.
The system will show you all the resource transactions if you don't enter search criteria. If your organization configures any field mandatory for search, you must enter those fields to search resource transactions.
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.
If you click on the create a new button, the system will open a simple step form to create a new resource transaction. You can click on the detail right bottom to view all the fields available for the object.
To view the search result in a table format, click on the table icon in the bottom left corner.
To view specific resource transaction details, click on the menu of that record, and click on view/fetch & view.
You can also click the expand icon against any item on the search result screen to view the resource transaction header details such as description, reason, etc.
The system will fetch all the selected document detail line data. Depending on the device size, the document details are shown either right to the search result screen or on a separate screen.
Inventory Organization: Select an inventory organization to limit the list of the available resource.
Resource Name: Select a resource name from the available list. The system shows all the resources associated with the selected project. (e.g., the unit cost per hour, associated task, etc.) The system defaults various other fields from resource details.
Unit Cost Per Hour: System defaults the unit cost per hour from the resource details. If required, you can make this field read-only.
No of hours: Enter the number of hours the resource utilizes.
Transaction Amount: System calculates the transaction amount based on the number of hours and unit cost per hour.
Transaction Amount = No of hours * Unit Cost Per Hour.
Scroll left, right, up, and down to view all the details. The document 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 | defferedSelect | ENTITY |
| 10 | vvResourceName | Resource Name | defferedSelect | DEFAULT |
| 20 | vvUomCode | Uom Code | defferedSelect | DEFAULT |
| 30 | vvResourceDescription | Resource Description | defferedSelect | DEFAULT |
| 40 | vvTrnxProjectName | Trnx Project Name | defferedSelect | DEFAULT |
| 50 | vvTrnxProjectNumber | Trnx Project Number | defferedSelect | DATA |
| 60 | vvTrnxTaskNumber | Trnx Task Number | defferedSelect | DATA |
| 70 | vvTrnxTaskName | Trnx Task Name | defferedSelect | DEFAULT |
| 80 | vvTrnxActivitySequence | Trnx Activity Sequence | defferedSelect | DEFAULT |
| 90 | vvTrnxActivityDescription | Trnx Activity Description | defferedSelect | DEFAULT |
| 100 | vvPrjProjectHeaderId | Prj Project Header Id | defferedSelect | REFERENCE |
| 110 | vvPrjProjectTaskId | Prj Project Task Id | defferedSelect | REFERENCE |
| 120 | vvOperationSequence | Operation Sequence | InputType.text | DEFAULT |
| 130 | vvResOperationSequence | Res Operation Sequence | defferedSelect | DEFAULT |
| 140 | vvMfgResource | Mfg Resource | defferedSelect | DEFAULT |
| 150 | hrResourceTransactionId | Hr Resource Transaction Id | InputType.text | REFERENCE |
| 160 | srcEntityName | Src Entity Name | defferedSelect | DEFAULT |
| 170 | srcEntityId | Src Entity Id | InputType.text | REFERENCE |
| 180 | prjProjectActivityResId | Prj Project Activity Res Id | defferedSelect | REFERENCE |
| 190 | wipWoLineResId | Wip Wo Line Res Id | InputType.text | REFERENCE |
| 200 | invOrgId | Inv Org Id | defferedSelect | REFERENCE |
| 210 | transactionType | Transaction Type | InputType.select | CONTROL |
| 220 | hrResourceId | Hr Resource Id | InputType.text | REFERENCE |
| 230 | transactionDate | Transaction Date | InputType.date | DATE |
| 240 | unitCostPerHour | Unit Cost Per Hour | InputType.textField | FINANCE |
| 250 | noOfHour | No Of Hour | InputType.textField | DEFAULT |
| 260 | unitCostPerQuantity | Unit Cost Per Quantity | InputType.textField | DATA |
| 270 | uomCode | Uom Code | defferedSelect | DEFAULT |
| 280 | transactionQuantity | Transaction Quantity | InputType.textField | DATA |
| 290 | transactionAmount | Transaction Amount | InputType.textField | FINANCE |
| 300 | reason | Reason | InputType.text | REFERENCE |
| 310 | reference | Reference | InputType.text | REFERENCE |
| 320 | scrapAccountId | Scrap Account Id | InputType.text | REFERENCE |
| 330 | salesOrderHeaderId | Sales Order Header Id | InputType.text | REFERENCE |
| 340 | salesOrderLineId | Sales Order Line Id | InputType.text | REFERENCE |
| 350 | glJournalHeaderId | Gl Journal Header Id | InputType.text | REFERENCE |
| 5360 | createdBy | Created By | InputType.text | REFERENCE |
| 5370 | creationDate | Creation Date | InputType.text | REFERENCE |
| 5380 | lastUpdatedBy | Last Updated By | InputType.text | REFERENCE |
| 5390 | lastUpdateDate | Last Update Date | InputType.text | REFERENCE |
Actions
Use actions to create accounting entries for a resource transaction.
Project Issue
The onhand/stock impact type of project issue transaction type is "BOTH" (i.e., both +ve and -ve). The transaction is similar to a subinventory transfer. Project issue transaction moves the material from an unrestricted subinventory to a project subinventory. Thus, both the source and destination subinventory are required.
Financially, the transaction moves value from one balance sheet account to another balance sheet account. i.e., RAW to PIP or PWIP. Project issue materials are restricted stock, and the stock is not available for any other transaction. In the OnHand screen, you can view the stock against the project. The system adds project_id/task_id to the stock.
To create/view/update a project issue transaction doc, navigate to the "transaction doc" screen from your dashboard/favorite.
Enter the organization/transaction doc details or other criteria in the search form and click on the search button to view an existing transaction doc.
The system will show you all the transaction docs if you don't enter organization details. If your organization configures any field mandatory for search, you must enter those fields to search transaction docs.
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.
To view the search result in a table format, click on the table icon in the bottom left corner.
To view specific transaction doc details, click on the menu of that record, and click on view/fetch & view.
You can also click the expand icon against any item on the search result screen to view the transaction doc header details, such as number, quantities, start date, status, etc.
If you click on the create a new button, the system will open a simple step form to create a new transaction doc. You can click on the detail right bottom to view all the fields available for the object.
Document Type Select the document type as project number
Transaction Type Select the transaction type as the project issue
Scroll left, right, up, and down to view all the details. The document line and components 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.
Project Number
Select a project number in the document header screen. It's an optional field. However, if you enter a value on the project number field, the app will fetch all the assigned materials and show them in the "Inv Transaction New Line" tab. If you don't enter any project number, you must manually add all the project activity material sequences you want to issue in the "Inv Transaction Doc Line" tab.
All Fields
| Sequence | Name | Label | InputType | Field Group |
|---|---|---|---|---|
| 10 | sdtransaction docHeaderId | Sd transaction doc Header Id | InputType.number | REFERENCE |
| 10 | invOrgId | Inv Org Id | deferredSelect | REFERENCE |
| 20 | sdSoHeaderId | Sd So Header Id | InputType.number | REFERENCE |
| 30 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
| 40 | srcEntityId | Src Entity Id | InputType.textField | REFERENCE |
| 50 | docNumber | Doc Number | InputType.textField | DATA |
| 60 | transaction docNumber | transaction doc Number | InputType.textField | DATA |
| 70 | comment | Comment | InputType.textField | DEFAULT |
| 80 | transactionTypeId | Transaction Type Id | InputType.number | CONTROL |
| 90 | transaction docDate | transaction doc Date | InputType.dateTime | DATE |
| 100 | docStatus | Doc Status | InputType.select | CONTROL |
| 110 | docStatus | Doc Status | InputType.select | CONTROL |
| 120 | receivedBy | Received By | InputType.textField | DEFAULT |
| 130 | carrier | Carrier | InputType.textField | DEFAULT |
| 140 | vehicleNumber | Vehicle Number | InputType.textField | DATA |
| 150 | transaction docReceivedBy | transaction doc Received By | InputType.textField | DEFAULT |
| 160 | carrierReceiptNumber | Carrier Receipt Number | InputType.textField | DATA |
| 170 | expetcedtransaction docDate | Expetced transaction doc Date | InputType.date | DATE |
| 180 | actualtransaction docDate | Actual transaction doc Date | InputType.date | DATE |
| 190 | handlingInstruction | Handling Instruction | InputType.textField | DEFAULT |
| 200 | systemMessage | System Message | InputType.textField | DEFAULT |
| 5210 | createdBy | Created By | InputType.textField | REFERENCE |
| 5220 | creationDate | Creation Date | InputType.dateTime | REFERENCE |
| 5230 | lastUpdatedBy | Last Updated By | InputType.textField | REFERENCE |
| 5240 | lastUpdateDate | Last Update Date | InputType.dateTime | REFERENCE |
Doc Lines
The document lines tab shows all the lines assigned to the document header. When you confirm and create a transaction for the document, the system will use all the information on this tab to create inventory transactions. You can also manually add a new line to the document in this tab.
If you want to default all the project number information, use the "Inv Transaction New Line" tab to add new lines to the document header. Use this tab (Doc lines) only for review/update.
You can add multiple lines to each transaction doc header. Each transaction doc line contains an item, UOM, product description, quantity, serial, and lot details.
Navigate to the lines tab to view/add/update lines.
Click on the add new entity to add a new line. If a line already exists, click on copy entity to copy all the details.
You can enable/disable fields allowed to be copied in the menu configuration.
Quantity: Enter the Quantity to be transacted against the doc line.
Line Number: Enter a document line number.
Item: Enter an item number.
Transaction Type: A read-only field, the value defaults from the transaction type selected on the document header
Document Status: A read-only field that shows the current status of the document line. You can change the document status using the actions available on the "Actions" tab. Only lines in "validated" status are used for the inventory transaction. When the system creates a transaction against a document line, the line's status is changed to closed.
The entity group shows information related to project issue inventory organization.
The reference groups show various ids for reference only. You don't need to enter any information in this section. When you save a transaction doc for the first time, the system will auto-populate the newly created header id and line ids.
Scroll left, right, up, and down view all other fields.
Enter all the other fields and click on the save button to save the transaction doc. The app will post all the data to the server and will show the messages returned from the server.
All Fields
| Sequence | Name | Label | InputType | Field Group |
|---|---|---|---|---|
| 10 | vvSoNumber | So Number | InputType.textField | DATA |
| 10 | vvSoDocNumber | So Doc Number | InputType.textField | DATA |
| 20 | vvOrgCode | Org Code | deferredSelect | ENTITY |
| 30 | vvItemNumber | Item Number | deferredSelect | DEFAULT |
| 40 | vvUomCode | Uom Code | deferredSelect | DEFAULT |
| 50 | vvUomDescription | Uom Description | deferredSelect | DEFAULT |
| 60 | vvItemStatus | Item Status | deferredSelect | CONTROL |
| 70 | vvSdSoHeaderId | Sd So Header Id | InputType.number | REFERENCE |
| 80 | vvLineNumber | Line Number | InputType.number | DATA |
| 90 | vvInvOrgId | Inv Org Id | deferredSelect | REFERENCE |
| 100 | vvInvItemMasterId | Inv Item Master Id | deferredSelect | REFERENCE |
| 110 | vvItemDescription | Item Description | deferredSelect | DEFAULT |
| 120 | vvLineQuantity | Line Quantity | InputType.textField | DATA |
| 130 | vvShipmentNumber | Shipment Number | InputType.number | DATA |
| 140 | vvSubInventory | Sub Inventory | deferredSelect | ENTITY |
| 150 | vvLocatorId | Locator Id | deferredSelect | REFERENCE |
| 160 | vvDetailLocator | Detail Locator | deferredSelect | ENTITY |
| 170 | vvQuantity | Quantity | InputType.textField | DATA |
| 180 | sdtransaction docLineId | Sd transaction doc Line Id | InputType.number | REFERENCE |
| 190 | sdtransaction docHeaderId | Sd transaction doc Header Id | InputType.number | REFERENCE |
| 200 | sdSoLineId | Sd So Line Id | InputType.textField | REFERENCE |
| 210 | sdSoDetailId | Sd So Detail Id | InputType.number | REFERENCE |
| 220 | transaction docLineNumber | transaction doc Line Number | InputType.number | DATA |
| 230 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
| 240 | srcEntityId | Src Entity Id | InputType.textField | REFERENCE |
| 250 | transaction docQuantity | transaction doc Quantity | InputType.textField | DATA |
| 260 | subInventory | Sub Inventory | deferredSelect | ENTITY |
| 270 | locatorId | Locator Id | deferredSelect | REFERENCE |
| 280 | docStatus | Doc Status | InputType.select | CONTROL |
| 290 | pickingDate | Picking Date | InputType.date | DATE |
| 300 | actualShipDate | Actual Ship Date | InputType.date | DATE |
| 310 | referenceDocType | Reference Doc Type | InputType.number | CONTROL |
| 320 | referenceDocNumber | Reference Doc Number | InputType.number | DATA |
| 330 | shipToLocationId | Ship To Location Id | InputType.number | REFERENCE |
| 340 | uomCode | Uom Code | deferredSelect | DEFAULT |
| 350 | volumeUomCode | Volume Uom Code | deferredSelect | DEFAULT |
| 360 | totalVolume | Total Volume | InputType.textField | DATA |
| 370 | weightUomCode | Weight Uom Code | deferredSelect | DEFAULT |
| 380 | totalWeight | Total Weight | InputType.date | DATA |
| 5390 | createdBy | Created By | InputType.textField | REFERENCE |
| 5400 | creationDate | Creation Date | InputType.dateTime | REFERENCE |
| 5410 | lastUpdatedBy | Last Updated By | InputType.textField | REFERENCE |
| 5420 | lastUpdateDate | Last Update Date | InputType.dateTime | REFERENCE |
New Lines
The new lines tab shows all the project activity material lines of the project number selected in the document header tab. The information in the new lines tab is not associated with the document header. This tab is used only to simplify the data entry and allows users to create document lines without manually entering all the line details.
All the new lines are shown with quantity zero; you can enter a quantity and click on the save button to save the document. All the information is saved and added as new lines to the header. You can refresh the document line tab to view the newly added lines.
All the information in the new lines tab is the same as the "Document Line Tab ."The only difference is the lines are defaulted from project numbers and are not related to the document header.
Navigate to the lines tab to view/add/update lines.
Click on the add new entity to add a new line. If a line already exists, click on copy entity to copy all the details.
You can enable/disable fields allowed to be copied in the menu configuration.
Quantity: Enter the Quantity to be transacted against the doc line.
Line Number: Enter a document line number.
Item: Enter an item number.
Scroll left, right, up, and down view all other fields.
Enter all the other fields and click on the save button to save the transaction doc. The app will post all the data to the server and will show the messages returned from the server.
All Fields
| Sequence | Name | Label | InputType | Field Group |
|---|---|---|---|---|
| 10 | vvSoNumber | So Number | InputType.textField | DATA |
| 10 | vvSoDocNumber | So Doc Number | InputType.textField | DATA |
| 20 | vvOrgCode | Org Code | deferredSelect | ENTITY |
| 30 | vvItemNumber | Item Number | deferredSelect | DEFAULT |
| 40 | vvUomCode | Uom Code | deferredSelect | DEFAULT |
| 50 | vvUomDescription | Uom Description | deferredSelect | DEFAULT |
| 60 | vvItemStatus | Item Status | deferredSelect | CONTROL |
| 70 | vvSdSoHeaderId | Sd So Header Id | InputType.number | REFERENCE |
| 80 | vvLineNumber | Line Number | InputType.number | DATA |
| 90 | vvInvOrgId | Inv Org Id | deferredSelect | REFERENCE |
| 100 | vvInvItemMasterId | Inv Item Master Id | deferredSelect | REFERENCE |
| 110 | vvItemDescription | Item Description | deferredSelect | DEFAULT |
| 120 | vvLineQuantity | Line Quantity | InputType.textField | DATA |
| 130 | vvShipmentNumber | Shipment Number | InputType.number | DATA |
| 140 | vvSubInventory | Sub Inventory | deferredSelect | ENTITY |
| 150 | vvLocatorId | Locator Id | deferredSelect | REFERENCE |
| 160 | vvDetailLocator | Detail Locator | deferredSelect | ENTITY |
| 170 | vvQuantity | Quantity | InputType.textField | DATA |
| 180 | sdtransaction docLineId | Sd transaction doc Line Id | InputType.number | REFERENCE |
| 190 | sdtransaction docHeaderId | Sd transaction doc Header Id | InputType.number | REFERENCE |
| 200 | sdSoLineId | Sd So Line Id | InputType.textField | REFERENCE |
| 210 | sdSoDetailId | Sd So Detail Id | InputType.number | REFERENCE |
| 220 | transaction docLineNumber | transaction doc Line Number | InputType.number | DATA |
| 230 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
| 240 | srcEntityId | Src Entity Id | InputType.textField | REFERENCE |
| 250 | transaction docQuantity | transaction doc Quantity | InputType.textField | DATA |
| 260 | subInventory | Sub Inventory | deferredSelect | ENTITY |
| 270 | locatorId | Locator Id | deferredSelect | REFERENCE |
| 280 | docStatus | Doc Status | InputType.select | CONTROL |
| 290 | pickingDate | Picking Date | InputType.date | DATE |
| 300 | actualShipDate | Actual Ship Date | InputType.date | DATE |
| 310 | referenceDocType | Reference Doc Type | InputType.number | CONTROL |
| 320 | referenceDocNumber | Reference Doc Number | InputType.number | DATA |
| 330 | shipToLocationId | Ship To Location Id | InputType.number | REFERENCE |
| 340 | uomCode | Uom Code | deferredSelect | DEFAULT |
| 350 | volumeUomCode | Volume Uom Code | deferredSelect | DEFAULT |
| 360 | totalVolume | Total Volume | InputType.textField | DATA |
| 370 | weightUomCode | Weight Uom Code | deferredSelect | DEFAULT |
| 380 | totalWeight | Total Weight | InputType.date | DATA |
| 5390 | createdBy | Created By | InputType.textField | REFERENCE |
| 5400 | creationDate | Creation Date | InputType.dateTime | REFERENCE |
| 5410 | lastUpdatedBy | Last Updated By | InputType.textField | REFERENCE |
| 5420 | lastUpdateDate | Last Update Date | InputType.dateTime | REFERENCE |
Actions
Actions allow you to change the status of the transaction doc. The system creates a transaction doc in draft status. If you are using custom approval or requesting someone else to complete the Transaction, click on the confirm button to confirm that the document is ready for a transaction. Confirmation is an optional step. You can directly create inventory transactions from draft status.
Usage of various button
Confirm
If the person entering a transaction document is different from the person who physically completes the task, then the document entering person can create and confirm the document. The person who completes the physical task can complete the Transaction.
Validate
All transaction documents must be validated before the system can use them for inventory transactions. The validation process checks the document details and confirms several checks - such as enough stock is available to create an inventory transaction, etc.
You can create your custom validation using javascript.
Transaction
The system uses the transaction document information to create inventory transactions. This process results in stock change and later allows you to generate GL journals against inventory transactions.
You can cancel a transaction doc by clicking on the Cancel button. Similarly, you can close any transaction doc by clicking on the Close button.
Click on the Create Transaction button to create inventory transactions. "Create the transaction" process completes all the below transactions
- Inventory transaction
- Inventory serial Transaction for serial numbers entered on transaction doc lines
- Inventory lot transaction for lot numbers entered on transaction doc lines
You can create only one inventory transaction against one transaction doc line.
Project Return
The onhand/stock impact type of project issue transaction type is "BOTH" (i.e., both +ve and -ve). It's a reversal of the project issue transaction. You can create a project return transaction to correct any wrong project issue transaction. You can also create a "return transaction" to remove excess stocks from a completed project.
The transaction is similar to a subinventory transfer. Project return transaction moves the material from a project subinventory to an unrestricted subinventory. Thus, both the source and destination subinventory are required.
Financially, the transaction moves value from one balance sheet account to another balance sheet account. i.e., PIP/PWIP to RAW.
To create/view/update a "project return transaction" doc, navigate to the "transaction doc" screen from your dashboard/favorite. Follow all the steps in the "Project Issue" section. Only change the transaction type to "Project Return."
Project Shipment
The onhand/stock impact type of project shipment transaction type is "NEGATIVE." Project shipment transactions are created to record the physical shipping of the material out of inventory. The transaction is similar to a sales order shipment transaction. The shipping process reduces stock and allows you to generate PWIP/PIP.
Project shipment transaction represents material movement from a project subinventory to a customer location. Financially, the transaction moves value from one balance sheet account to another balance sheet account. i.e., PIP/PWIP to Deferred COGS.
To create/view/update a project shipment transaction doc, navigate to the "transaction doc" screen from your dashboard/favorite. Follow all the steps in the "Project Issue" section. Only change the transaction type to "Project Shipment."
Project Shipment Return
The onhand/stock impact type of "project shipment return" transaction is "POSITIVE." It's a reversal of the project shipment transaction. You can create a project shipment return transaction to correct any wrong project shipment transaction. You can also use "return transaction" to receive any return from a customer.
Project shipment return transaction represents the movement of material from a customer location to a project subinventory. The transaction is similar to a sales order return transaction. Financially, the transaction moves value from one balance sheet account to another balance sheet account. i.e., Deferred COGS to PIP/PWIP.
To create/view/update a "project return" transaction doc, navigate to the "transaction doc" screen from your dashboard/favorite. Follow all the steps in the "Project Issue" section. Only change the transaction type to "Project Shipment Return."
Review
Inventory Transaction
After creating inventory transactions against an inventory transaction doc, you can review the inventory transactions in the inventory transaction screen. Navigate to the inventory transaction search screen and search with the transaction doc number, ID, or other criteria.
The system will show all the transactions created against a transaction document. The inventory transaction shows all the lines in the inventory transaction doc, and the system generates automatic lines created using inventory transaction doc lines. For certain transactions (such as Sub-Inventory Transfer and Inter-Org Transfer), the system might show more inventory transaction lines than the number of lines on the inventory transaction.
Transaction Doc
After creating inventory transactions against an inventory transaction doc, you can review the inventory transactions doc in the inventory transaction doc screen. Navigate to the "inventory transaction doc" search screen and search with the transaction doc number, ID, or other criteria. The system will show you the updated Transaction with closed status.
OnHand
After creating inventory transactions against an inventory transaction doc, you can review the inventory transactions doc in the inventory OnHand screen. Navigate to the inventory OnHand search screen and search the item number used in the inventory transaction doc. The system will show you the updated OnHand details.
