AS400 and ASI, Quick Item Add

Overview

• Faction never writes directly to AS400.
• Faction sends a complete, validated Quick Item Add payload to MSC's integration layer, and MSC's middleware performs the write.
• The QIA part number and ASI reference come back to Faction, so every item traces to its source.

Phase: Production. MSC owner: MSC IT.

Setup

1. MSC IT defines the handoff point (an API endpoint, queue or file drop) and shares the payload specification.
2. Faction maps the 19 fields to the payload and validates each payload before handoff.
3. MSC IT defines how the QIA part number and ASI reference are returned.
4. Faction and MSC IT test the handoff and key return in UAT.

What Faction sends

One payload per resolved line, after an associate confirms the source. It contains the 19 fields from the chosen candidate, validated against MSC's specification. Failed handoffs are retried.

What comes back

The QIA part number and ASI reference are stored on the sourcing decision with the source of every field. A reconciliation report lists any decision missing a key in either system.

Security

• Faction needs no AS400 or ASI access or credentials.
• Every item is confirmed by an associate before handoff, until MSC chooses to automate.

MSC provides: the handoff point, the payload specification and the write.

Faction handles: building and validating the payload, retries and the audit record.