What is the SOAP payload to create a customer account in Oracle ERP (Fusion) Cloud?

createCustomer — SOAP payload to create a customer, account, site and site use | Oracle Fusion SOAP example

createCustomer — SOAP payload to create a customer, account, site and site use

SOAP APIOracle Fusion · Financials · CustomersMedium confidenceCurated

ReceivablesCustomerService.createCustomer is the ERP Cloud service that creates the whole customer structure in one call: the organization party, its customer account, an account site (from an existing PartySiteId or an inline address), and one or more site uses (BILL_TO, SHIP_TO). CreatedByModule (HZ_WS) is set at every level; OrigSystemReference carries your source-system key. Element names below follow the documented pattern — confirm exact names against Oracle's 'SOAP Web Services for Financials Cloud' and the A-Team customer-creation guide.

WSDL

SOAPhttps://<your-fusion-host>:443/fscmService/ReceivablesCustomerService?WSDL

POST the SOAP envelope to the same URL without ?WSDL. Replace <your-fusion-host> with your pod host.

Purpose

Create a customer end to end (party, account, account site, site use) without separate calls. POST the envelope to the WSDL URL without ?WSDL with a WS-Security UsernameToken. The response returns the generated PartyId, CustAccountId, CustAcctSiteId and site-use ids. This mirrors the A-Team 'ERP Cloud customer creation through integration' approach.

Parameters

OrganizationNamerequiredCustomer organization name (use PersonFirstName/PersonLastName for a person customer).

CreatedByModulerequired'HZ_WS' — set on the party, the Account, the AccountSite and each AccountSiteUse.

Account / AccountNamerequiredThe customer account block; AccountNumber optional when automatic account numbering is on.

AccountSite / PartySiteIdrequiredThe party site to attach as an account site — create it first (see the Create Party Site example) or pass an inline address.

AccountSiteUse / SiteUseCoderequiredPurpose of the account site use, e.g. BILL_TO, SHIP_TO. One block per purpose.

OrigSystemReferenceYour source-system unique key for the party / account / site — enables later lookups and idempotency.

Example request

Request

<soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:typ="http://xmlns.oracle.com/apps/financials/receivables/customerSetup/customerServices/receivablesCustomerService/types/"
    xmlns:cus="http://xmlns.oracle.com/apps/financials/receivables/customerSetup/customerServices/receivablesCustomerService/">
  <soapenv:Header/>
  <soapenv:Body>
    <typ:createCustomer>
      <typ:customerParty>
        <cus:OrganizationName>Pinnacle Technologies Inc</cus:OrganizationName>
        <cus:CreatedByModule>HZ_WS</cus:CreatedByModule>
        <cus:OrigSystemReference>EXT-CUST-1043</cus:OrigSystemReference>
        <cus:Account>
          <cus:AccountName>Pinnacle Technologies Inc</cus:AccountName>
          <cus:CreatedByModule>HZ_WS</cus:CreatedByModule>
          <cus:OrigSystemReference>EXT-ACCT-1043</cus:OrigSystemReference>
          <cus:AccountSite>
            <cus:CreatedByModule>HZ_WS</cus:CreatedByModule>
            <cus:OrigSystemReference>EXT-SITE-1043-1</cus:OrigSystemReference>
            <cus:PartySiteId>300100573317048</cus:PartySiteId>
            <cus:AccountSiteUse>
              <cus:SiteUseCode>BILL_TO</cus:SiteUseCode>
              <cus:PrimaryFlag>true</cus:PrimaryFlag>
              <cus:CreatedByModule>HZ_WS</cus:CreatedByModule>
            </cus:AccountSiteUse>
            <cus:AccountSiteUse>
              <cus:SiteUseCode>SHIP_TO</cus:SiteUseCode>
              <cus:PrimaryFlag>true</cus:PrimaryFlag>
              <cus:CreatedByModule>HZ_WS</cus:CreatedByModule>
            </cus:AccountSiteUse>
          </cus:AccountSite>
        </cus:Account>
      </typ:customerParty>
    </typ:createCustomer>
  </soapenv:Body>
</soapenv:Envelope>

Example response

Response

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  <env:Body>
    <ns0:createCustomerResponse
        xmlns:ns0="http://xmlns.oracle.com/apps/financials/receivables/customerSetup/customerServices/receivablesCustomerService/types/">
      <ns0:result
          xmlns:ns1="http://xmlns.oracle.com/apps/financials/receivables/customerSetup/customerServices/receivablesCustomerService/">
        <ns1:PartyId>300100573401122</ns1:PartyId>
        <ns1:PartyNumber>CDRM_1043</ns1:PartyNumber>
        <ns1:OrganizationName>Pinnacle Technologies Inc</ns1:OrganizationName>
        <ns1:Account>
          <ns1:CustAccountId>300100573401200</ns1:CustAccountId>
          <ns1:AccountNumber>1043</ns1:AccountNumber>
          <ns1:AccountSite>
            <ns1:CustAcctSiteId>300100573401255</ns1:CustAcctSiteId>
            <ns1:PartySiteId>300100573317048</ns1:PartySiteId>
            <ns1:AccountSiteUse>
              <ns1:SiteUseId>300100573401260</ns1:SiteUseId>
              <ns1:SiteUseCode>BILL_TO</ns1:SiteUseCode>
            </ns1:AccountSiteUse>
          </ns1:AccountSite>
        </ns1:Account>
      </ns0:result>
    </ns0:createCustomerResponse>
  </env:Body>
</env:Envelope>

Call lifecycle

01
WS-Security UsernameToken in the SOAP header.
- User needs the Customer Account Administration privilege
- POST to the WSDL URL without ?WSDL
02
03
04