SERVICES
We develop, deploy and operate integration services between Logo ERP, Logo Payroll, SAP, Oracle, Mikro, Idenfit and in-house applications. Every connection is delivered with matching rules that prevent duplicates, an error log and email reports.
Discuss your integration requirementsTeams that enter the same record twice: a warehouse retyping field despatch notes into Logo, a sales team re-entering orders from another platform, or an HR team copying payroll changes into an HR application. We first agree which system owns each record, then build the transfer around that rule.
We choose the method by Logo product and record type: • Logo Objects REST service: invoices, despatch notes, financial vouchers and master data. VibeTrans 360 uses this route. • Logo Objects (UnityObjects): documents whose lines link to orders or lots, such as sales despatch notes and export operation vouchers. • HR Objects for Logo Payroll: writing leave approved in an HR application back to payroll. • Read-only database queries: reports, Logo Payroll personnel records and open orders sent to the field. • Logo Flow: custom activities, web forms built on the Flow REST service and maintenance of Flow definitions.
• Open Logo orders sent to handheld terminals, with despatch notes created in the field returned to Logo as sales despatches through a queue. • Orders and customer accounts from the Veribase field sales platform transferred to Logo GO 3, with unmatched records held in quarantine. • Invoices, vouchers and master data imported from Excel into Logo with VibeTrans 360. • Personnel records from Logo Payroll, SAP HR, Oracle and Mikro transferred to Idenfit. • Leave approved in Idenfit written to SAP HR and Logo Payroll. • A desktop application that assigns product certificate numbers to Logo despatch lines.
We have connected to SAP HR through SOAP/RFC services, to Oracle through report services, to Mikro and Mikro Fly through their API and database, to Nebim V3 through SQL and to Idenfit through REST and GraphQL. We have also built document transfers to Google Drive.
WORKFLOW
Each record passes the matching rules, enters a queue, and its result in the target system is stored with the source identifier.
Together we identify where order, stock, account, document and personnel records originate. A mapping table records each field's source, target, owner and update frequency. Code mappings for accounts, items, warehouses, payment plans, branches, units and titles are kept in separate tables; a missing mapping does not stop the transfer but sets the record aside for review.
Every transferred record is written to a control table with its source identifier, so the same document is never sent twice. Only changed source records are processed. If the target is busy or the connection drops, the record waits in the queue and is retried a limited number of times. Logo error codes are stored with a readable description; a record that still fails is set aside for manual review.
Integrations run as Windows services on the customer's server. Where needed, an admin panel shows pending, sent and failed records and lets authorised users resend them. On first installation a preview mode lists the planned actions without writing to the target. Successes and failures go to daily logs and an email summary. Connection details live in a server-specific settings file, never in source code.
An agreed data map, a working service with installation scripts, test results, technical documentation and a closure document. After closure, log reviews, error analysis and requests for new fields are handled under support.
We have worked with orders, despatch notes, invoices, customer and item cards, accounting, bank and cash vouchers, export operation vouchers, personnel records, leave and work schedules. For a new record type we start with a table that maps the fields in both systems.
The record waits in the queue and is resent when the connection returns. The retry count and last error appear in the panel or the email report. A document whose result is uncertain is not resent without a check, so no duplicate is created.
IMPLEMENTATION AND SERVICE
We automate the transfer of personnel records, organisation data, leave and work schedules between payroll, ERP and HR/time-attendance applications. As an Idenfit partner, our services connecting Logo Payroll, SAP HR, Oracle, Mikro and Nebim to Idenfit run at media, hospitality, retail, manufacturing and logistics companies.
RELATED SOLUTION
Transfer invoices, dispatch notes, financial slips and master data from Excel to Logo. Use VibeTrans 360 to map the spreadsheet columns, check the prepared records and follow the outcome of each transfer.
RELATED SOLUTION
Send open Logo order lines to your dispatch team's handheld terminals. Scan products by barcode and print the despatch note on the device; the note is then transferred to Logo as a sales despatch linked to the order.
Share your current applications and the process you want to improve. We can agree where to start in our first conversation.
info@vibebilisim.com +90 (850) 242 84 23