What problem does it solve? Operating Infor ERP through an AI assistant is risky because every goods receipt, invoice match, or journal posting is an audited financial event, and the three product lines (M3, LN, SyteLine/CSI) name the same objects and screens differently, so acting with the wrong line's assumptions targets the wrong screen or field. ## Core Features & Use Cases - Product-line identification: Distinguishes M3 (program codes like PPS200/MMS060), LN (session codes like tdpur/tfacp/whinh), and SyteLine (named forms and IDOs) before any action, including which line sits under each CloudSuite edition. - Action classification and gating: Classifies every operation as read, reversible write, committing write, or destructive, with rules for when to stop for human approval (e.g., posting a receipt, releasing a matching hold, reopening a closed period). - Domain gotchas and recovery patterns: Covers 22 real failure modes such as LN's decoupled integration transactions, MAUC average-cost distortion, ION approval state living outside the ERP screen, and BOD replication lag, plus how to reverse receipts, vouchers, and payments safely. - Use Case: When asked to post a supplier invoice in Infor LN, the skill directs checking the fiscal and tax period status, verifying the three-way match tolerance, and confirming integration transactions are processed before treating the ledger as current. ## Quick Start Ask the assistant how to safely receive a purchase order and match a supplier invoice in Infor M3 without posting into a closed period.
