233 SOAP services · 10 menu systems · 460 payload tables · 9,616 fields
· browse all by system
AllInbound →Outbound ←Has request table
system
sort
export
Web Services Explorer — Help
Every SOAP web service in the standard Ross ERP 8.0 integration layer (the RS_* services). Each is registered in the dictionary procedures table and moves data as a MethodXML<method> document (parameters + tables). 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 SOAP / MethodXML request and response, generated from the field definitions. Dates use DD-MMM-YYYY (the documented format); a few interface fields differ by design — the RF/MES export emits ISO-8601 …T…+00:00, Crystal renders MM/dd/yyyy — and ISO input is accepted but not required. Times of day HHMM. All values are text (no wire-level typing). Placeholders are 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
Verified against the Ross ERP 8.0 Service Reference Guide + IAF Connect UG 9.3 and a working ExecuteXML client. Host / .asmx path and credentials are placeholders — confirm them for your install.
TransportEvery call goes through the generic IAF Connect runner ConnectService.ExecuteXML (namespace http://rossinc.com/webservices/; GemXMLServer.ProcessRequest in the .NET API). It carries the broker connection — host, port, username, password, application — plus the MethodXML, on every call; the connection is not server-side-only and not inside the methodXML. The <method name> selects the service.
MethodXML<method name="RS_…"> with <parameters> and <tables> (an optional <database> selects the environment). Input tables = the request payload for writes / the selection-criteria table for reads. Values are element text — no wire-level typing (the long/short/text shown are the underlying Data Dictionary column types).
EmbeddingThe methodXML rides inside <methodXML> as a string: a working client entity-escapes it (<method>…); an equivalent <![CDATA[…]]> wrapper delivers the identical string. Elements sit in the service namespace — declared as a default xmlns on the operation, or via a prefix (<tns:host>) — identical on the wire.
Response<ExecuteXMLResult> wrapping the (escaped) result method XML, or an <errors>/GemException block. Status comes back in #ERROR_OCCURRED and the RS_SYS_MESSAGES table. XML_TAGS controls response metadata (0 = data only; +16 field names; +4096 descriptions — additive).
DatesDD-MMM-YYYY (e.g. 05-JAN-2026) — every date field in the field spec, and what most wrappers emit via MASK("!DD-!3SM-!LY") (combined date-time adds HH:MM). A few interface fields differ by design: the RF/MES job export emits ISO-8601 2026-01-05T08:00:00+00:00; the Crystal print path renders MM/dd/yyyy per IafConfig. ISO input is accepted (fields are xs:string) but not required. Times of day HHMM.
Wrapper variantA deployment may instead publish a single service as its own SOAP wrapper — RsIncreaseInventory(methodString, iRenLogin, iRenPassword) — with the connection fixed in that service's config (Ross ERP 8.0 Service Reference Guide).
Not thisNo JSON/REST interface. The generic xpo.aspx page takes scalar parameters only and cannot carry these tables. The Postman / OpenAPI exports describe the ExecuteXML call.
Keyboard shortcuts
?Open / close this help
/Jump to search
EscClose help · leave search
Services are read from the standard Ross ERP 8.0 dictionary (procedures + payload table definitions). Customer and site customizations are excluded, and custom columns grafted onto standard tables are scrubbed. Deep-link any service by name (#rs_wms_get_ship_note). Catalog metadata only — no proprietary source is included.