IFC – POS Interface Investigation, Troubleshooting & Training Manual

Purpose of This Document

This document provides structured guidance for identifying, investigating, and resolving common IFC (Interface) issues between POS systems and integrated platforms.

It standardizes troubleshooting steps and ensures consistent resolution processes across the team.

This manual is intended for:

  • Support Engineers
  • System Administrators
  • Interface Specialists
  • Escalation Teams

 

2. Introduction to IFC Architecture

A Property Interface passes data between OPERA PMS and third-party systems such as POS.

The IFC8 service translates POS messages to PMS web services and vice versa via the Opera IFC Controller.

Integration Overview

PMS ↔ POS integration via XML over TCP/IP/HTTPS

  • IFC8 handles vendor communication and translation
  • Opera IFC Controller brokers IFC8 with OPERA Web Services
  • IFC8 Web Service runs on the OPERA application server

3. How the IFC Interface Works

Understanding transaction flow is critical before troubleshooting.

Transaction Flow

  1. A transaction is completed in POS.
  2. The transaction is written to the POS database.
  3. The IFC service reads the transaction data.
  4. The IFC sends the data to the destination system (API or external server).
  5. The receiving system acknowledges receipt.
  6. The transaction is marked as successfully processed.

If any step fails, transactions may:

  • Not post
  • Duplicate
  • Delay

System Flow Diagram

POS → Database → IFC Service → API / Destination System

Component Roles

  • POS System – Captures and closes transactions
  • POS Database – Stores transaction records
  • IFC8.exe – Communicates with vendor and translates messages
  • Opera IFC Controller – Connects IFC8 to OPERA Web Services, manages states, writes logs
  • OPERA Application Server – Hosts IFC Web Services
  • Vendor System (Simphony/CAPS) – Connects for room inquiry and postings
  • Network Layer – Enables server communication
  • Acknowledgement Response – Confirms receipt

 

5. IFC Version Check Procedures

5.1 OPERA Cloud – IFC Controller Version

Path:
OPERA Cloud → Administration → Interfaces → Property Interface → Edit Interface → Primary Information → Machine

Shows:

  • Controller Port
  • Version
  • Machine details

5.2 IFC8 Application Version (Server)

Path:
Control Panel → Programs and Features

Steps:

  1. Log into IFC server
  2. Open Control Panel
  3. Select Programs and Features
  4. Locate IFC8
  5. Record full version

IFC8 may run:

  • As a Windows service
  • As an application (for GUI diagnostics)

For GUI diagnostics:

  1. Stop the IFC service
  2. Start IFC8 using the XML shortcut

6.        IFC8 GUI Indicators (Lamp States)

7.       

Lamp meanings:

  • Queue to Vendor (Green) – Vendor socket initialized
  • Queue PMS↔IFC Object (Green) – Local pipeline OK
  • Physical Layer PMS (Yellow/Red) – Cannot reach Opera IFC Controller
  • Application Layer (Red) – Waiting for vendor connection or room inquiry trigger

Lamp colours are critical for first-level diagnosis.

 

7. Logs & File Locations

IFC Controller Logs

C:/ or D:/Fidelio/IFC8/Controller/

IFC8 Interface Logs (Example: Simphony)

C:/Fidelio/IFC8/SPH/

OPI Logs (Payments v20.x)

Files include:

  • transaction.log
  • debug.log
  • system.log
  • gateway.log

Log colors in IFC8:

  • Red = inbound
  • Green = outbound
  • Black = internal

 

8. First-Response Troubleshooting Checklist

Before escalating:

  1. Capture issue start date/time
  2. Check recent changes (network, upgrades, parameters)
  3. Open IFC8 GUI
  4. Review lamp states
  5. Check Controller logs at incident time
  6. Validate network connectivity
  7. Restart Controller only if necessary
  8. Capture screenshots
  9. Document exact error messages

 

9. IFC Down / Not Communicating

9.1 Check Services

Open Services.msc

Verify:

  • Opera IFC Controller running
  • IFC8 service running
  • Startup Type = Automatic

If stopped:

  • Start service
  • Restart if required

9.2 Check Connectivity

From CAPS/Service Host:

ping <IFC_IP>

telnet <IFC_IP> (e.g., 5001/5501)

If:

  • Ping fails → Network issue
  • Telnet fails but ping works → Firewall/port issue

Note: Telnet from IFC to CAPS is not meaningful if IFC8 is listener.

 

 

10. Transactions Not Posting

Step 1 – Validate in POS

  • Confirm check is closed
  • Ensure not open
  • Verify no pending batches

Open checks will not transmit.

Step 2 – Check IFC Queue

If transactions appear stuck:

  • Review logs first
  • Restart only if required

The queue temporarily stores transactions before sending.

Step 3 – Database Validation (If Required)

Run validation script:

  • Confirm no unexpected open checks
  • Confirm no database errors

Corrupted/open records may block posting.

 

11. Simphony Gen2 Transaction API Report

FIRST step of API troubleshooting.

Navigate:

Administrator → System → API Activity → Simphony Gen2 Transaction API

Check:

  • Requests received
  • Status codes
  • Failure responses
  • Matching timestamps

If error found:

  • Open record
  • Review detailed error
  • Refer to documentation

Status codes determine success/rejection.

 

12. Common Scenarios & Fixes

12.1 Timeout – Room Inquiry / Check Close

  • Refresh POS Extension Application configuration
  • Test CAPS → IFC connectivity
  • Engage site IT if port blocked

 

12.2 SQL Connection Errors

Examples:

  • ORA-28001 (Password expired)
  • ORA-01000 (Open cursors exceeded)

Action:

  • Engage DBA
  • Reset credentials
  • Reload WS database

 

12.3 Unable to Find Extension Application – Opera

Cause:

  • Missing/misconfigured Extension Application folder
  • Incorrect files

Action:

  • Verify Extension Application → OPERA in EMC
  • Use latest Simphony2 Enhanced IFC files

 

12.4 Invalid Account / Guest Not Found / No-Credit

In OPERA:

  • Ensure PM/PI rooms checked in
  • Remove ‘No Post’ privilege
  • Validate Posting Accounts mapping

 

12.5 Duplicate Postings

Check:

  • POS timeout setting
  • Registry values on IFC server:
    • WSMaxRetry=0
    • WSRetryInterval=0
    • WSTimeout=15

Restart Controller after change.

Confirm:

  • PM accounts rotated daily
  • Compare PostRequest vs PostAnswer timestamps

Operation timed out = common root cause.

 

12.6 Auto-Reversal (Simphony ↔ PMS)

Often due to old ISL files.

Solution:

  • Remove entities
  • Re-add using latest Simphony2 Enhanced IFC files

 

12.7 Wrong Transaction Code Mapping

Validate in OPERA:

Configuration → Setup → Property Interfaces → Interface Configuration

Check:

  • Serving Period + Revenue Center mappings
  • All Charges default
  • Difference Code (DC)
  • Tender media mapped correctly

Itemizers:

  • ST1–ST16 (Sales)
  • DC1–DC16 (Discount)
  • SC1–SC16 (Service)
  • TX1+ (Tax)

 

13. IFC Controller Log Errors (Examples)

Invalid timestamp → Fix system time (NTP), restart

Invalid Security / OSB-386200 → Update service credentials

Port already in use → Change port (e.g., 5501)

Socket 10054 → Remote host closed connection

Operation timed out → Latency issue

14. Performance Issues

Check:

  • CPU usage
  • Memory usage
  • Disk space
  • Database growth

High resource usage can delay transaction processing.

 

15. OPI (Payments) – Common Errors

Issuer/switch inoperative
Connection refused
Timed out

Check:

  • PSP/gateway services
  • Network path
  • Restart PSP

Database errors:

  • Update DB password
  • Ensure connection pool reconnects

 

16. Data Collection Pack for Escalation

Include:

  • IFC8 logs (time window)
  • Controller logs
  • POS Check Preview/Journal
  • OPERA FinjrLbyTrans2 report
  • Screenshots of lamp states
  • Error messages
  • Ping/telnet proof

Escalate only after full validation.

 

17. Quick SOPs

Restart Opera IFC Controller

Services.msc → Opera IFC Controller → Restart
If needed → Stop → Start

 

Start IFC8 as Application

  1. Stop IFC8 service
  2. Launch XML shortcut (e.g., ifc8Config_M87POS.xml)
  3. Observe lamp states

 

Validate Posting Accounts in OPERA

OPERA → Configuration → Setup → Property Interfaces → Interface Configuration

Edit POS Interface → Trans Codes tab → Posting Accounts

Verify:

  • PM room numbers
  • Tender mappings

 

18. Escalation Rules

Escalate only after:

  • Logs reviewed
  • Services verified
  • Connectivity tested
  • Screenshots captured
  • Errors documented

Incomplete investigations delay resolution.