Skip to content

ERP & interface engineering

Make Infor COM work across processes, screens and interfaces

I help investigate Infor COM ERP problems, improve defined workflows and connect operational records with the systems that depend on them: Infor Global Financials (IGF), Varial, EDI and reporting.

Start with one concrete issue: a missing field, a failed transfer, a delivery-note flow, an unreliable report or an administration problem.

Infor COM · IGF · EDI

The systems and tools behind the workflow

Follow the real business record from the user action to its downstream result. The scope is agreed against your installed COM version, modules, customisations and connected systems.

Infor COM ERP processes

Investigate how sales, purchasing, inventory and production records move through screens, statuses and business rules. Trace inconsistencies back to the relevant master data and processing step.

Sales orders · purchase orders · items · bills of material · routings · production orders · inventory · delivery notes

IGF & Varial

Trace transfers between COM and Infor Global Financials, including the Varial World Edition context. Check mappings, rejected documents and reconciliation with the finance owner before changing the handover.

Document transfers · customers and suppliers · receivables and payables · general ledger accounts · posting periods · tax keys · cost centres · currencies

EDI & system integration

Investigate order, delivery-note and invoice exchanges, whether a COM interface or an external EDI solution carries the messages. Define validation, acknowledgements, duplicate handling, retries and accountable monitoring.

EDI · partner mappings · message status · imports and exports · APIs · files · scheduled jobs · error handling

IMC & operational administration

Review the Infor Management Console and the application context behind an access or processing problem. Reproduce the issue with the relevant user, company, services and batch processing.

IMC / Infor MC · users and groups · roles · permissions · sessions · batch services · system and site configuration · client and database connections

IDM, Lj4 & repository customisation

Investigate and implement a defined screen or logic change using the mechanisms available in your installation. Trace field bindings, repository objects and their callers; test the behaviour with representative records and roles.

Infor Dialog Manager (IDM) · dialogs and menus · DialogDef · repository · Lj4 · VQL · ISL · VTabs and records · plausibility rules · tracing and debugging

SQL, reports & operational dashboards

Clarify the business meaning of a query, report or KPI before changing it. Review data selection, parameters and totals, and build a contained report or dashboard with a reproducible calculation.

SQL · Microsoft SQL Server · VQL · Jasper Reports · report parameters · document output · KPI dashboards · data quality

Concrete issues to bring to a first conversation

These are possible work packages. The useful starting point is your actual record, screen, message or report.

A transfer from COM to IGF fails or does not reconcile

Compare the source document, mapping, processing status and finance result. Identify what should be corrected, how to retest it and who owns the outcome.

An EDI delivery note reaches the wrong state

Follow the delivery record through export, partner mapping and acknowledgement. Distinguish missing data, timing problems and repeated messages.

A screen, field or menu needs a defined extension

Review the existing dialog, field binding, permissions and repository logic. Implement the agreed change in a test environment and document its dependencies.

An operational report or KPI is hard to trust

Agree what is counted and when. Trace SQL or VQL selection, validate totals against sample records and make exceptions visible to the owner.

A change your team can inspect and maintain

A first assignment can be diagnosis, a contained implementation or a partner work package. Agree the outcome, available access and acceptance cases before work starts.

  • Findings linked to example records, messages or screens, with a prioritised next step.
  • A documented configuration or code change, with normal and exception cases tested in the agreed environment.
  • Mappings, queries or report definitions that explain the data and business rules.
  • Handover notes covering dependencies, recovery, ownership and checks to repeat after an update.

ERP support within the wider operational systems practice

Infor COM work sits alongside my EAM boutique and independent interface engineering. You can bring a COM, IGF/Varial or EDI issue on its own. For delivery partners, I can take a defined technical work package inside your project structure.

Useful distinctions before we start

Does IDM mean Infor Document Management here?

On this page, IDM means Infor Dialog Manager, the COM tool for dialogs and repository objects. Infor Document Management is a separate product. If that product is involved, name it explicitly when describing your interface.

What is Infor MC / IMC?

IMC is the Infor Management Console used in the COM administration context. We check the affected installation, system, users and services alongside application roles and permissions.

Can you work on IGF or EDI without an EAM project?

Yes. COM-to-finance transfers and EDI reliability can be scoped independently. Finance owners define the accounting requirements; I help investigate and implement the technical flow and agreed controls.

Which versions and extensions are in scope?

Describe your COM and IGF release, modules, database and existing customisations. Documentation for another release is a reference; the installed build and its supported mechanisms determine the implementation and tests.

Which Infor COM workflow needs attention?

Send the COM/IGF version and one example: a screen, failed transfer to IGF, EDI message, report or recurring manual correction. We can identify a useful first work package and its acceptance criteria.