Reconcile the material records with our batch evidence.
Neil
- Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
- Reads
Supplier, inventory and other ERP data your edition exposes
- Returns
- Quantities, identifiers and unmatched records
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
Connect Sage ERP data, for example from Sage Intacct or Sage X3, with supplier, inventory and batch records in Seal through a connection set up with Seal’s API or Scripts. Confirm your edition and its available endpoints before scoping.
Connection setup and permissions
Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.
Related blueprints
2Read supplier, item and lot records from Sage Intacct or X3.
Route
Sage Intacct’s web services take XML only, posted to one gateway endpoint. Purchasing transactions, from requisitions to vendor invoices, are queried through the PODOCUMENT object.¹² Sage X3 has a REST Web API based on SData 2.0, with a URL for each resource such as a supplier or product, and SOAP web services for modules not yet moved to its newer model. X3 Online accepts only OAuth 2.³
Record identity
An Intacct vendor’s VENDORID is its unique ID, and it can also be read by RECORDNO. Updating a purchasing transaction deletes and recreates its accounts-payable transaction, which then has a new RECORDNO.⁴² In X3, lot numbers of up to 15 characters distinguish stock lines, and a product with mandatory lots needs a lot on every transaction.⁵
Units
Intacct items carry a unit of measure group, and purchasing lines a unit for the quantity. In X3, a unit other than the stock unit needs a conversion factor to it.⁶²⁵
When it fails
- A request timed out but finished
- A large Intacct request can time out after 15 minutes while still processing, and a failure can leave part of a request done. Unique function IDs make it safe to send again.¹⁷ Give each function a unique ID tied to the Seal record, and resend with the same ID.
- Records moved between pages
- Each offset page is a new query, so changes between calls can shift the results.⁸ Page in a stable order and check the total against a final count.
- A link to an accounts-payable record broke
- The recreated accounts-payable transaction has a new RECORDNO.² Link Seal records to the vendor and purchasing identifiers, not to the accounts-payable RECORDNO.
Check one record
Read one supplier and one lot-tracked item from a test company into Seal. The supplier should keep its VENDORID and the item its unit. Receive a lot against a purchase order and confirm the lot number and unit reach the Seal batch record unchanged.
3Start with the job.
Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.
4Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.
