1. Home
  2. Utility API sandbox
  3. Oracle CC&B test environment

Solution

Oracle CC&B test environment for field activity integrations

Last updated

This free Oracle CC&B-style test environment imitates an OUAF billing system's REST and SOAP services. Read service points, devices, field activities and measurements with limit and offset paging. Complete an exchange field activity over REST or a SOAP inbound web service, and get OUAF-style dates and errors back. No Oracle licence or test tenant is needed.

What it's for

Most Oracle Utilities API detail sits behind a licensed tenant or a support login, so integrators often meet OUAF behaviour for the first time on the customer's test system. This environment lets you build and test a field activity integration first. It's one of the three surfaces of the utility API sandbox.

Get started

Create a workspace, then call the REST service with HTTP Basic (SBX_USER / Sandbox#1) or an OAuth 2.0 bearer token from /oauth/token in your workspace:

curl -X POST https://sandbox.piebench.com/workspaces
curl -u 'SBX_USER:Sandbox#1' "https://sandbox.piebench.com/ws_…/oracle/ouaf/rest/apis/cm/fieldwork/fieldActivities?status=PENDING"

Resources

ResourceHolds
servicePointsAccount, customer name, address, rate schedule, coordinates, installed badge number
devicesBadge number, device type, status, service point, install and removal date-times
fieldActivitiesExchange activities (type CM-EXCHMTR): existing and new badge numbers, status (PENDING, COMPLETED)
measurementsBadge number, value, date-time, read type (PERIODIC, INSTALLATION, REMOVAL)

Get one record with /{resource}/{id}, for example /devices/OLD0001. Filter by adding a field as a query parameter, such as ?status=PENDING.

Paging

Use limit (default 25, maximum 100) and offset. Each response has items, count, hasMore and a links list with a next link while more remain. A client that ignores hasMore reads 25 of the 60 service points.

Dates

Dates use the OUAF format YYYY-MM-DD-HH.MM.SS in UTC, for example 2026-11-15-09.30.00. Sending ISO 8601 (2026-11-15T09:30:00Z) is rejected with a message naming the expected format. Date mix-ups are a common integration bug, which is why the mock enforces this.

Complete a field activity over REST

curl -u 'SBX_USER:Sandbox#1' -H "Content-Type: application/json" \
  -d '{"existingBadgeNumber":"OLD0001","removalRead":9000,"newBadgeNumber":"NEW0001","installRead":0}' \
  "https://sandbox.piebench.com/ws_…/oracle/ouaf/rest/apis/cm/fieldwork/fieldActivities/WO0001/completion"

The billing side checks the badge numbers and readings, removes the old meter, installs the new one, confirms the initial reading and notifies the head-end. The response says whether it did (headEndNotified). completionDateTime is optional and defaults to now.

Post extra reads to /measurements as {"measurements": [{"badgeNumber", "measurementValue", "measurementDateTime"}]}, up to 600 per call. An upload is all-or-nothing: if one read fails, none are saved.

Complete a field activity over SOAP

Many CC&B integrations still use inbound web services. Post a SOAP envelope with Content-Type: text/xml. Authenticate with HTTP Basic or a WS-Security UsernameToken in the SOAP header:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
      <wsse:UsernameToken><wsse:Username>SBX_USER</wsse:Username><wsse:Password>Sandbox#1</wsse:Password></wsse:UsernameToken>
    </wsse:Security>
  </soapenv:Header>
  <soapenv:Body>
    <cm:CM-FieldActivityCompletion xmlns:cm="urn:sandbox">
      <cm:fieldActivityId>WO0002</cm:fieldActivityId>
      <cm:existingBadgeNumber>OLD0002</cm:existingBadgeNumber>
      <cm:removalRead>9000</cm:removalRead>
      <cm:newBadgeNumber>NEW0002</cm:newBadgeNumber>
      <cm:installRead>0</cm:installRead>
    </cm:CM-FieldActivityCompletion>
  </soapenv:Body>
</soapenv:Envelope>

Send it to https://sandbox.piebench.com/ws_…/oracle/ouaf/webservices/CM-FieldActivityCompletion. Bodies are limited to 16 KB.

Errors you will see

REST errors come back as a problemDetailDocument with httpStatus, detail and a serverMessage holding messageCategory and messageNbr. SOAP errors are a soapenv:Fault with faultcode Server.CISApplicationError and a ResponseCode. The numbers are the sandbox's own:

Category / numberWhen
90001 / 1533Reading is lower than the previous reading
90001 / 1418No register is installed on the meter on that date
90002 / 2010Existing badge number isn't installed at the service point
90002 / 2011New meter isn't in stock
90003 / 3020Field activity is already completed (HTTP 409)
90003 / 3021Field activity doesn't exist

What it doesn't do

It's a simulator, not Oracle software. There are no WSDLs to import, no business objects beyond those listed, no batch jobs and no billing calculation. Names, activity types and message numbers are illustrative, and PIEBENCH isn't affiliated with Oracle. For how a field app connects to a real CC&B system, see Oracle CC&B field integration.

Built to integrate with your systems

HES, MDM, SAP IS-U, Oracle CC&B and billing systems, over REST, OAuth or a direct SQL connection. How integrations work

Questions buyers ask

Can I test an Oracle CC&B integration without an Oracle tenant?

You can test the behaviour your client depends on: limit and offset paging, OUAF date formats, SOAP and REST completion of a field activity, and error handling. Final acceptance still needs the utility's own test environment, because real CC&B configuration differs per utility.

What date format does the mock expect?

YYYY-MM-DD-HH.MM.SS in UTC, the OUAF style, for example 2026-11-15-09.30.00. ISO 8601 timestamps are rejected with a message naming the expected format.

Does the SOAP service need WS-Security?

It accepts either HTTP Basic authentication or a WS-Security UsernameToken in the SOAP header, so you can test both styles your integration platform might use.

Can I import a WSDL into SoapUI?

No WSDL is published. Build the request from the example envelope on this page. The service reads the fields by element name and ignores namespaces.

What happens if I complete the same field activity twice?

The second call is rejected: HTTP 409 with message 90003 / 3020 over REST, or a SOAP fault with ResponseCode 3020. Use this to test that your retries are safe.

Free trial · no card

See it with your own crew

Start a free trial, or ask us for a walkthrough of your rollout.

Related