Ross ERP Web Services Explorer

Web Services Explorer — Help

Every SOAP / Connect web service in the standard vanilla Ross ERP 8.0 integration layer (the RS_* services). Each is registered in the dictionary procedures table and moves data as IAF <tables> documents. This is a catalog of the registration and payload schema — description, menu system, typed parameters, and the request / response tables with their fields. No wrapper source body is published.

What a service shows

DirectionInbound → the caller writes into Ross (create / load / confirm / post). Outbound ← the caller reads from Ross (get / query / export). Inferred from the service verb.

ParametersThe typed call parameters from the procedures table — XML_TAGS (response metadata bitmask), ROW_SELECT_COUNT, and ERROR_OCCURRED (0 = success).

Request / Response payloadThe IAF tables the caller sends and receives, each with its fields, types and descriptions — cross-linked to the Data Dictionary. An echoed table is one the caller populates and the service returns.

Example callA representative IAF Connect <tables> request and response, generated from the field definitions. Values are type-appropriate placeholders — a shape reference, not a live capture.

Search & filter

Search matches service name, description, payload table and facility id. Narrow with the Inbound / Outbound direction chips, Has request table, and the menu system selector. Open a service to cross over to its backing Facility and Program.

How the call works

A service is invoked as an IAF stored procedure over Connect. Two transports: the xpo.aspx runner — a plain HTTP call (GET for reads, POST of the IAF <tables><table name="…"><data><row>… request document for writes; procedure in pn=, by-value params in p1..pn) — and the sample ConnectService.asmx SOAP wrapper around the ExecuteXML method, which carries a <method name="…"> document of parameters and tables. The broker connection (host, port, application, user, password) is supplied by the client via IafConfig.xml / a resource bundle; xpo.aspx can override user/pass per call with secUN/secPW. There is no JSON/REST interface in vanilla Connect. XML_TAGS controls how much field metadata the response carries (0 = data only; +16 field names; +4096 descriptions — additive). Every service reports status through #ERROR_OCCURRED and the RS_SYS_MESSAGES table. The Postman buttons export the exact xpo.aspx call.

Keyboard shortcuts

?Open / close this help

/Jump to search

EscClose help · leave search

Services are read from the standard vanilla Ross ERP 8.0 dictionary (procedures + payload table definitions). Customer and site customizations are excluded, and custom columns grafted onto vanilla tables are scrubbed. Deep-link any service by name (#rs_wms_get_ship_note). Catalog metadata only — no proprietary source is included.