TRANXACT.AI Help

API package

Supply Chain

Items, suppliers, purchasing, bin-level inventory, and warehouse execution. Receipts accrue GR/IR in Accounting.

208 APIs1511 operationsBase path /api/scm

Automation

Buying

Capacity & Scheduling

Collaboration

Contract Management

Demand Planning

Direct Materials

Dock Scheduling

Drop-Ship

Electronic Data Interchange

Freight Forwarding

Freight Management

Accessorial Charges What a carrier charges for beyond moving the goods. Half a freight bill is usually these, and an accrual that ignores them is wrong by half. /api/scm/accessorial-charges GET2 POST2 PUT1 DELETE1 Carrier Scorecard Computed rather than typed: what each carrier moved, what it cost, how much of it arrived on time, and how often their invoice was wrong. /api/scm/carrier-scorecard GET2 POST2 PUT1 DELETE1 Carrier Services What a carrier sells. "UPS" is not a service; "UPS 2nd Day Air" is, and it is the thing that has a transit time and a cutoff. /api/scm/carrier-services GET2 POST2 PUT1 DELETE1 Carriers Who moves it. A carrier IS a supplier as far as payables is concerned, so a freight invoice posts against the supplier record rather than into a second ledger. /api/scm/carriers GET2 POST2 PUT1 DELETE1 Freight Classes The NMFC scale. Density, stowability, handling and liability decide it, and it is the single biggest driver of an LTL price. /api/scm/freight-classes GET2 POST2 PUT1 DELETE1 Freight Orders The instruction to a carrier: collect here, deliver there, these stops in this order. Tendered, accepted, refused, offered to the next one down. /api/scm/freight-orders GET5 POST6 PUT3 DELETE3 Freight Tariffs A price agreement with a carrier. The rate basis is what lets one engine price parcel, LTL and truckload: three different arithmetics, one lane comparison. /api/scm/freight-tariffs GET3 POST3 PUT2 DELETE2 Rate Shopping What came back when several carriers were asked. Kept rather than thrown away: "why did we ship this on the expensive one" is a question somebody asks three weeks later. /api/scm/rate-quotes GET3 POST3 PUT2 DELETE2 Routes The drawn line and the plan behind it. Sequencing the stops is nearest-neighbour with time windows pulling a stop forward: crude, fast, and typically within a fifth of optimal on a delivery round. /api/scm/transport-routes GET2 POST3 PUT1 DELETE1 Tracking Events What the carrier told us, when. The evidence behind an on-time-delivery figure, normalized so a dashboard does not have to know that UPS says "I" and FedEx says "IT". /api/scm/tracking-events GET2 POST2 PUT1 DELETE1 Transport Lanes Origin region to destination region, by mode. The unit a rate is quoted on and the unit a spend analysis is done on. /api/scm/transport-lanes GET2 POST2 PUT1 DELETE1

Freight Settlement

Goods Movement

Inventory Costing

Inventory Structure

Invoices & Payment

Items & Suppliers

Items Open an item and everything about it is there: its organizations, sales, purchasing, planning, work definition, revisions, stocking, quality, costing and lot control, each one dated so you can read it as it stood on any day. /api/scm/items GET7 POST4 PUT2 DELETE2 Quota Arrangements For each item, how its demand is split between suppliers, in which part of the company and for what period. A requisition line that names no vendor is proposed the supplier furthest below its share: the one whose allocated quantity plus the line’s, divided by its share, is lowest. Shares in force at the same time may add up to 100% at most. Quota arrangements are asked first; then the Source List’s fixed source, an outline agreement (Contracts), and the item’s Purchasing record. /api/scm/quota-arrangements GET2 POST2 PUT1 DELETE1 Source List For each item, which suppliers it may be bought from, in which part of the company and for what period. A blocked supplier is refused on purchase orders for the item. The fixed source is the supplier a requisition line takes when nobody names one, and its Purchasing record prices the line. Where the item’s Purchasing record says “Source list required”, only the suppliers listed here may be ordered from. /api/scm/source-lists GET2 POST2 PUT1 DELETE1 Suppliers Open a supplier for its sites, financial terms, bank details, certifications, diversity and exclusions — the ordering address is almost never the one you pay. /api/scm/suppliers GET4 POST3 PUT1 DELETE1

Load Building

Maps & Geography

Network

Procurement Control

Approval Levels The people a rule asks to sign, one level at a time, in order. A level whose approver has left or is on leave is skipped and the next one fills it; a level that must be filled by somebody holds the document instead. Works the same way for a purchase order and for a requisition, because it is one policy. /api/scm/approval-levels GET2 POST2 PUT1 DELETE1 Material at Subcontractors What the company owns and is not holding: material issued to a subcontractor, what they consumed, returned and spoiled, and what is still out there. /api/scm/subcontract-issues GET2 POST4 PUT1 DELETE1 Procurement Exceptions Everything between a customer order and the material it needs that is not moving — unapproved requisitions, unawarded tenders, late deliveries, rejected material, overdue subcontractors and invoices that will not match. /api/scm/procurement-exceptions GET2 POST2 PUT1 DELETE1 Requisition Approval Rules Which purchase requisitions need a signature, and whose. The same shape a purchase order rule has, because a company should express its delegation of authority once. /api/scm/pr-approval-rules GET3 POST3 PUT1 DELETE1 Requisition Approvals Every signature a requisition is waiting for, oldest first. A requisition may not become a purchase order until they are all in — and the database, not a screen, is what enforces that. /api/scm/pr-approvals GET2 POST3 PUT1 DELETE1 Vendor Evaluation Criteria What responses will be compared on, and how much each counts — declared before any response is opened. Criteria chosen afterwards are criteria chosen to fit the preferred answer. /api/scm/rfx-criteria GET2 POST2 PUT1 DELETE1 Vendor Evaluation Scores What each vendor scored on each criterion, and what it was worth once weighted. Price, lead time and payment terms are each scored against the best response: the lowest offer, the shortest lead time, the longest credit. Unless the event says otherwise they weigh 60%, 20% and 20%. /api/scm/rfx-scores GET2 POST2 PUT1 DELETE1

Product Configurator

Configurations What customers actually configured, what it came to, and whether it can be made yet. /api/scm/configurations GET9 POST8 PUT1 DELETE1 Configurator · Models A configurable product and how a configuration of it gets made — configure, assemble, make or engineer to order. /api/scm/config-models GET4 POST4 PUT3 DELETE3 Configurator · Options The answers. An option with an item puts a part in the product; one without is a characteristic that changes price and paperwork. /api/scm/config-options GET2 POST2 PUT1 DELETE1 Configurator · Parameters The named constants a calculation rule leans on — the process allowance, the cutting allowance, a density. Named so a formula reads as a sentence rather than as arithmetic over numbers nobody can place. /api/scm/config-parameters GET2 POST2 PUT1 DELETE1 Configurator · Questions The questions a model asks, in order. How many answers each takes decides whether it is a radio button or a checklist. /api/scm/config-option-classes GET2 POST2 PUT1 DELETE1 Configurator · Rules Two kinds of rule in one list. CONSTRAINT rules say what may be chosen, as explicit pairs, because a rule has to be explicable to a salesperson standing in front of a customer. PROCESS rules say what the choice MEANS — which component, in what quantity, through which operation, with which inspection — and carry a condition written in the ordinary expression language. /api/scm/config-rules GET4 POST5 PUT2 PATCH1 DELETE2 Configurator · Sub-assembly Inheritance Which of a parent model’s answers travel down to a child model, and under what name there. Without the map a sub-assembly is configured in isolation, and a 12 mm machine acquires a 10 mm axle. /api/scm/config-inheritance GET2 POST2 PUT1 DELETE1 Configurator · Workbook The whole definition of a configurable product — models, characteristics, values, rules written as IF … THEN … sentences, components, operations and sub-assembly structure — as one Excel workbook to download, edit and upload; or many rules pasted as text at once. /api/scm/config-workbook GET1 POST1 Configured · Components Every part the rules put in a configuration, at the quantity their formulas computed, with the rule that chose it. The answer to “why does this order have this part”. /api/scm/resolved-components GET2 POST2 PUT1 DELETE1 Configured · Cost Sheet The rolled-up cost of a configuration, element by element — material, labour, machine, setup, outside processing, scrap, freight, packaging and overhead. A total nobody can check is a total nobody can defend. /api/scm/config-cost-sheet GET2 POST2 PUT1 DELETE1 Configured · Inspections The inspections a configuration’s characteristics decided on — incoming, in-process and final. The same rules that chose the parts choose what is measured. /api/scm/resolved-inspections GET2 POST2 PUT1 DELETE1 Configured · Routing The operations a configuration resolved to, in sequence, with the work centre, the time the rules computed and what each costs. A galvanizing operation that is not there is the answer to “why is this one cheaper”. /api/scm/resolved-operations GET2 POST2 PUT1 DELETE1 Configured · Why Every fact about one configuration in one list: what was answered, what was computed from it, what that selected, and which rule did it. The screen a production engineer opens when an operator asks why the traveller says what it says. /api/scm/config-explanation GET2 POST2 PUT1 DELETE1

Purchase Charges

Purchase Order Types

Customs Lines The tariff lines of a declaration: what it is, what it is classified under, where it came from, and what is owed on it. /api/scm/customs-lines GET2 POST2 PUT1 DELETE1 Freight Invoice Lines Line by line against what was agreed, naming which of the seven ways a freight bill goes wrong this one is. /api/scm/freight-invoice-lines GET2 POST2 PUT1 DELETE1 Freight Order Lines What is on the freight order as the carrier is told it: twelve pallets, 4,800 kg, class 70. Not the contents of each. /api/scm/freight-order-lines GET2 POST2 PUT1 DELETE1 Item · Costing The cost method, the elements that make up the standard, and where it posts. The elements must add up to the standard — the platform refuses a row where they do not. /api/scm/item-costing GET2 POST2 PUT1 DELETE1 Item · Engineering Revisions What changed, when it took effect, what authorized it, and what happens to the stock that already exists. Geometry links to the model viewer. /api/scm/item-revisions GET2 POST2 PUT1 DELETE1 Item · Lot & Serial Control The POLICY. Whether lots and serials are demanded, how they are formed, and what may not move without them — which is what turns traceability from an intention into a control. /api/scm/item-traceability GET2 POST2 PUT1 DELETE1 Item · Organizations Which plants and business units an item is defined in. An item not assigned to an organization cannot be transacted there — that is the control. /api/scm/item-orgs GET2 POST2 PUT1 DELETE1 Item · Planning How supply is decided and how demand is read — both sides in one row, because the planning run reads them together. /api/scm/item-planning GET2 POST2 PUT1 DELETE1 Item · Purchasing Who it is bought from, on what terms, with what tolerance, and how the invoice is matched. /api/scm/item-purchasing GET2 POST2 PUT1 DELETE1 Item · Quality When it is inspected, against what, and what happens when it fails. The flags here are what turn a receipt into quarantine. /api/scm/item-quality GET2 POST2 PUT1 DELETE1 Item · Sales What may be ordered, at what price, promised how, and invoiced when. /api/scm/item-sales GET2 POST2 PUT1 DELETE1 Item · Stocking Policy Where an item may be stocked and how it is restocked there — which is a different question from how the item is planned. /api/scm/item-subinventories GET2 POST2 PUT1 DELETE1 Item · Warehouse Dimensions, packing, putaway and picking — what the physical handling of the thing needs to know, as distinct from what planning needs. /api/scm/item-wms GET2 POST2 PUT1 DELETE1 Item · Work Definition How it is built: the bill of material and routing it is built against, the lot sizes, the yield and how components are consumed. /api/scm/item-manufacturing GET2 POST2 PUT1 DELETE1 Load Stops Where the vehicle stops, in order. The sequence decides the loading order, because the first delivery has to be at the back of the trailer. /api/scm/load-stops GET2 POST2 PUT1 DELETE1 On the Deck One thing on the vehicle, and where it sits. The coordinates are what make the axle calculation and the picture the same fact. /api/scm/load-items GET2 POST2 PUT1 DELETE1 Quote Options What each carrier said, and the arithmetic behind it. Kept so a disputed rate can be replayed. /api/scm/rate-quote-options GET2 POST2 PUT1 DELETE1 Rate Bands One band of a tariff: between 500 and 1,000 kg, class 70, zone 4, this much per kg with a minimum. /api/scm/freight-rate-breaks GET2 POST2 PUT1 DELETE1 Schedule Entries One bar on the Gantt. What makes it a schedule rather than a calendar is the dependency: operation 20 cannot start before operation 10 has finished. /api/scm/schedule-entries GET2 POST2 PUT1 DELETE1 Slotting Recommendations Where each item ought to move to, and why. Accepting one raises the move; rejecting one records that somebody looked. /api/scm/slotting-recommendations GET2 POST3 PUT1 DELETE1 Supplier · Bank Details Where the money goes. Changing any identifier resets the verification — an emailed "we have changed our bank" is the commonest fraud there is. /api/scm/supplier-bank-accounts GET2 POST2 PUT1 DELETE1 Supplier · Buying Context What each business unit is allowed to do with this supplier, and until when the approval lasts. /api/scm/supplier-orgs GET2 POST2 PUT1 DELETE1 Supplier · Certifications What the supplier holds that lets us use them, its scope, and what happens when it lapses. The status follows the dates rather than being typed. /api/scm/supplier-certifications GET2 POST2 PUT1 DELETE1 Supplier · Diversity Classification and the evidence behind it. Self-declared and third-party certified are different evidence, and spend reporting that conflates them will not survive an audit. /api/scm/supplier-diversity GET2 POST2 PUT1 DELETE1 Supplier · Exclusions Reasons a supplier may not be used, and exactly what each one blocks. Distinct from diversity on purpose: one is a preference, this is a control. /api/scm/supplier-exclusions GET2 POST2 PUT1 DELETE1 Supplier · Financial Payment method, matching tolerance, withholding and the hold flag — at supplier level, or overridden per site. /api/scm/supplier-financials GET2 POST2 PUT1 DELETE1 Supplier Sites One supplier, several places: where invoices come from (billing), where the goods leave from (shipping), where the payment goes and where orders are sent. Purposes are independent ticks because one address is very often several of them. /api/scm/supplier-sites GET2 POST2 PUT1 DELETE1

Records

Reporting

Requisitions & Orders

Returns

Services and actions

Assets The assets service of Supply Chain: 5 operation(s). /api/scm/assets GET3 POST2 Contract price check The contract price check service of Supply Chain: 1 operation(s). /api/scm/contract-price-check GET1 Freight The freight service of Supply Chain: 1 operation(s). /api/scm/freight POST1 Geo The geo service of Supply Chain: 2 operation(s). /api/scm/geo POST2 Gst The gst service of Supply Chain: 2 operation(s). /api/scm/gst GET2 Guided buying The guided buying service of Supply Chain: 1 operation(s). /api/scm/guided-buying POST1 Inventory The inventory service of Supply Chain: 2 operation(s). /api/scm/inventory POST2 Labels The labels service of Supply Chain: 1 operation(s). /api/scm/labels POST1 Models The models service of Supply Chain: 2 operation(s). /api/scm/models GET2 Movement The movement service of Supply Chain: 10 operation(s). /api/scm/movement GET6 POST4 Packing The packing service of Supply Chain: 1 operation(s). /api/scm/packing POST1 Planning The planning service of Supply Chain: 1 operation(s). /api/scm/planning GET1 Putaway The putaway service of Supply Chain: 1 operation(s). /api/scm/putaway POST1 Recommendations The recommendations service of Supply Chain: 1 operation(s). /api/scm/recommendations GET1 Replenishment The replenishment service of Supply Chain: 1 operation(s). /api/scm/replenishment POST1 Rfid The rfid service of Supply Chain: 1 operation(s). /api/scm/rfid POST1 Rfx derivable The rfx derivable service of Supply Chain: 1 operation(s). /api/scm/rfx-derivable GET1 Rfx derive The rfx derive service of Supply Chain: 1 operation(s). /api/scm/rfx-derive POST1 Scan The scan service of Supply Chain: 1 operation(s). /api/scm/scan POST1 Slotting The slotting service of Supply Chain: 1 operation(s). /api/scm/slotting POST1 Transport The transport service of Supply Chain: 2 operation(s). /api/scm/transport GET2 Uom The uom service of Supply Chain: 1 operation(s). /api/scm/uom POST1

Stock & Counts

Strategic Sourcing

Supplier Management

Supplier Portal

Supply Planning

Third-Party Logistics

Traceability

Units & Packaging

Handling Units The actual, physical, numbered thing on the floor: pallet, carton, container. They nest, and the weight of a parent is the sum of everything under it — maintained rather than typed, because a pallet whose weight is a guess is a pallet that overloads an axle. /api/scm/handling-units GET4 POST5 PUT2 DELETE2 Item Units Every unit one item may be transacted in, and what each is worth in the item’s stocking unit. This is what a purchase order line’s unit picker reads. /api/scm/item-units GET2 POST2 PUT1 DELETE1 Package Types The pallets, cartons, totes, drums and containers goods are shipped in — with the outside dimensions and the tare weight that make a load plan arithmetic rather than an opinion. /api/scm/package-types GET2 POST2 PUT1 DELETE1 Packaging Materials What goes into a pack and is not the goods: film, void fill, desiccant, the label. Costed, because packaging cost per order is a real number nobody can produce without it. /api/scm/packaging-materials GET2 POST2 PUT1 DELETE1 Packing Instructions How many go in the carton, how many cartons on the layer, how many layers on the pallet. One row per level, so a customer who wants it packed differently is a second instruction rather than an argument. /api/scm/packing-instructions GET2 POST2 PUT1 DELETE1 Unit Conversions The conversions arithmetic cannot derive. A rule with no item is a company rule; a rule with one belongs to that item and beats it. /api/scm/uom-conversions GET2 POST2 PUT1 DELETE1 Units of Measure A unit belongs to a dimension and carries a factor to that dimension’s base unit, so any two units of one dimension convert without anybody declaring anything. /api/scm/units-of-measure GET2 POST2 PUT1 DELETE1

Warehouse Execution

Bin Utilization How full each bin is against what it will take. The number the warehouse map colors by, and the one a putaway strategy checks before it proposes anything. /api/scm/bin-utilization GET2 POST2 PUT1 DELETE1 Labor Performance What one person actually did in one shift, against the standard. The row that makes warehouse productivity reportable next to the roster and the payroll. /api/scm/labor-records GET2 POST2 PUT1 DELETE1 Labor Standards How long one of these tasks ought to take. Split into fixed and variable, because walking to the bin costs the same whether you pick one case or ten. /api/scm/labor-standards GET2 POST2 PUT1 DELETE1 Slotting Where each item OUGHT to live, given how it actually moves. A recommendation with its reasoning attached, so nothing is moved without somebody agreeing to it. /api/scm/slotting-analyses GET3 POST3 PUT2 DELETE2 Warehouse Orders A bundle of tasks for one person to do in one go. The unit of assignment, as opposed to the unit of work. /api/scm/warehouse-orders GET3 POST3 PUT2 DELETE2 Warehouse Tasks One move: this quantity of this item, from this bin, to that one. Every kind of warehouse work is this shape, which is why there is one list rather than six. Confirming a task is the only thing here that moves stock. /api/scm/warehouse-tasks GET2 POST3 PUT1 DELETE1 Waves The decision to work on THESE orders now. Picking one order at a time walks the same aisle forty times; a truck leaving at four means the work starts at one. /api/scm/waves GET3 POST4 PUT2 DELETE2 What Needs Replenishing Every pick face at or below its minimum, right now. The replenishment run reads exactly this and turns each row into a task. /api/scm/replenishment-needs GET2 POST2 PUT1 DELETE1

Warehouse Structure

Warehouse Systems

Yard