Set up LAVINET in ImaCash
This guide covers the Lavinet profile in ImaCash’s selector for LAVINET pharmacy software. Although the website lists it under Pharmacy, the current program selection is under POS. The connection reads the exchange prepared in Oracle; it does not integrate every module of the software.
Before you start
The provider must confirm the edition and prepare the Oracle exchange. The administrator supplies the private server details and an account with query access to the required views or tables. Do not use a shared privileged account or publish access details. Check access from the computer and Windows account running ImaCash. This profile is not configured through an ODBC DSN. The check uses ping before attempting Oracle. If the network blocks ICMP, review the policy with the administrator; that refusal alone does not prove Oracle is down.
Setup steps
- Open Configuration > Integration using the identification and permissions of your installation. Under Management program, select POS > Lavinet.
- Enter Server IP and Port using the Oracle destination confirmed by the administrator. Do not assume that another installation’s details apply or that there is a universal port.
- In Service name, enter the Oracle instance SID supplied by the provider. This profile uses that field as a SID: an Oracle service name, alias or DSN is not an automatic substitute.
- Fill in User and Password with the private account authorized to query the exchange. These are not your personal pharmacy software login details. No sales file or additional database name is requested here.
- Review the retrieval date and time and any terminal and cashier filters you need. Check their codes and names with the provider and ImaCash’s history before extending the interval or resynchronizing.
- When closing Configuration, choose Save, Exit without saving or Continue editing. Reopen it and check what was saved. Do not send a payment to an installation in use to check these fields.
Saving and checking access
Applying the profile attempts to open and close the Oracle connection. A connection indicator does not prove that queries retrieve the correct sales or that a physical payment is valid. Some settings are saved in stages: a later failure does not guarantee that all changes are rolled back. If an error occurs, keep the observed information and review the details with the administrator.
Which transactions are retrieved
Retrieval starts at the chosen date and time, inclusively, and applies terminal and cashier filters. An empty list may reflect the data, interval, a filter or a failed query; it does not prove that no sales exist. This reader does not filter by company. Before use, check references, amounts, signs, dates and cash or card classification with the provider.
Confirmation and cancellation are different actions
Confirming or rejecting a transaction in ImaCash does not write a confirmation or cancellation to LAVINET. Check the pharmacy software’s status and the device’s result separately. A transaction classified as card does not prove bank authorization; this profile does not provide an independent bank total either.
If a transaction does not match
Keep the reference and compare LAVINET, ImaCash’s history and the actual cash before repeating, resynchronizing or restarting. Do not extend the interval to force another payment while the result remains pending. This profile does not import products, stock, EAN scans or shifts, and does not replace checking those details in their source program.
Checks before use
The responsible person and provider must supervise a representative retrieval and the installation’s complete workflow. The guide, logo and a connection do not validate every LAVINET edition or physical operation. Use only private parameters confirmed for your installation.