GhiLMIS Quick User Guide
GhiLMIS Quick User Guide
In cases where items do not have an order number, such as donations, the GhiLMIS system allows for manual receipt creation. The Warehouse Manager must capture data such as location, item description, off-network shipment details, actual quantity, lot information, and unit value. This process ensures that all relevant fields are populated, after which a receipt is created and then validated, inspected, acknowledged, and updated until the final state is 'Closed' .
In the GhiLMIS system, receipt management undergoes a quality assurance process post-creation. It involves navigating to receipts in the Open state and verifying data such as location, quantities, and lot details. Post-verification, the receipt state is set to 'In QA' upon inspection. After acknowledgment, the state advances to 'Accepted,' followed by updates and closure. This ensures accuracy and compliance before the receipt is finalized .
The final states of an order in the GhiLMIS system include 'Draft,' 'Awaiting Approval,' 'New,' 'Vendor Confirm with Changes,' 'Open,' 'In Transit,' and 'Partially Shipped.' Each state signifies a different stage in the order's lifecycle. 'Draft' denotes it is pending user submission, 'Awaiting Approval' indicates it's pending approval by DHD/MHD, 'New' means it's ready for processing at RMS. 'Vendor Confirm with Changes' occurs for user confirmation of RMS changes, while 'Open' signifies the RMS's satisfaction with the requests. 'In Transit' and 'Partially Shipped' relate to order receipt readiness and delivery status to the facility .
The dashboard in the GhiLMIS system is used to monitor order transactions from facilities to the RMS and vice versa, effectively summarizing requisitions and distributions. Essential widgets for this purpose are the PO State Summary and SO State Summary. These widgets help track the status of orders made to the RMS and distributions/allocations from the RMS and DHD/MHD, respectively .
The 'Consume' function is utilized by a Warehouse Manager for internal usage or dispensing to clients. This requires navigating to Location Inventory, selecting the items, and using the Consume action. Essential data include consume quantity, internal usage indication, operation date, and reason code ('Internal' if used within the facility, 'Dispensed' if given to clients), with comments for usage specifics. Once captured, the data is submitted for processing .
To create and submit a purchase order in the GhiLMIS system, a user in the role of Customer Order Admin or Manager must navigate to Order Management and click on New PO. They need to populate the mandatory header fields such as Buying Organization, Ship to, Trans Mode, Request Delivery Date, Vendor, and Ship From. The PO lines requiring fields like Item, Request Quantity, and Program must also be completed. After saving, the order can be submitted and awaits approval .
In the GhiLMIS system, the roles involved in the order creation and approval process include the Customer Order Admin, Customer Order Manager, and Warehouse Manager. The Customer Order Admin is responsible for creating and submitting an order for approval by the DHD/MHD. The Customer Order Manager not only creates and submits orders but can also review and approve orders to the RMS. The Warehouse Manager's responsibilities are broader in warehouse activities and include actions such as creating a dashboard and managing inventory transactions .
The Warehouse Manager generates receipts by accessing the Warehouse Management section, filtering for orders in-transit or partially shipped, and generating a receipt through system actions. They must confirm item details, including location, item, shipped quantity, and mandatory fields such as lot information and unit value. Post-confirmation, they create the receipt, which undergoes further validation and QA before being accepted and closed .
The GhiLMIS system structures inventory transactions through roles like Warehouse Manager, who manage transfers, consumption, and adjustments to facilitate efficient management. Transfer processes require destination cell selection, item handling, and precise documentation for operation and posting dates. Consumption demands internal or client-oriented categorization with accurate record-keeping for usage. This structured approach ensures goods' traceability and accountability across different zones and cells, fostering operational efficiency .
A Warehouse Manager performing an inventory transfer in the GhiLMIS system must go to Location Inventory, filter for the necessary transfer location, select the items, and initiate the Transfer action. Required fields such as the destination location, transfer quantity, operation and posting dates, a reason code, and comments regarding the transfer's purpose must be filled before submission .





