1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. SCM Common
  4. B2B Account Numbers

Create B2B account numbers

post

/fscmRestApi/resources/11.13.18.05/b2bAccountNumbers

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Ship-To Assignments
Type: array
Title: Ship-To Assignments
The ShipTo Assignments resource is used to manage the list of ship-to locations that are associated with a B2B account number.
Show Source
Nested Schema : schema
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : b2bAccountNumbers-item-response
Type: object
Show Source
Nested Schema : Ship-To Assignments
Type: array
Title: Ship-To Assignments
The ShipTo Assignments resource is used to manage the list of ship-to locations that are associated with a B2B account number.
Show Source
Nested Schema : b2bAccountNumbers-shipToAssignments-item-response
Type: object
Show Source
Links
shipToAssignments
Parameters:
  • AccountNumberId: $request.path.AccountNumberId
The ShipTo Assignments resource is used to manage the list of ship-to locations that are associated with a B2B account number.
Back to Top

Examples

These examples describe how to create B2B account numbers.

Example cURL Command

Use the following cURL command to submit a request on the REST resource.

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/b2bAccountNumbers"

Example 1 Request Body

The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it creates. 

{
    "AccountNumber": "A2002",
    "SupplierNumber": "6755",
    "SupplierName": "Axcense Software",
    "SiteName": "POZ11976",
    "ProcurementBU": "Vision Operations"
}

Example 1 Response Body

The following example includes the contents of the response body in JSON format:

{
"AccountNumber": "A2002",
    "AccountNumberId": 300100644902961,
    "VendorId": 999992000322108,
    "VendorSiteId": 999992000341208,
    "SupplierName": "Axcense Software",
    "SupplierNumber": "6755",
    "SiteName": "POZ11976",
    "ProcurementBU": "Vision Operations"
}

Example 2 Request Body

The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it creates. 

{
    "parts": [
        {
            "id": "a1",
            "path": "/b2bAccountNumbers",
            "operation": "create",
            "payload": {
                "AccountNumber": "A1",
                "SupplierNumber": "6755",
                "SiteName": "POZ11976",
                "ProcurementBU": "Vision Operations"
            }
        },
        {
            "id": "a2",
            "path": "/b2bAccountNumbers",
            "operation": "create",
            "payload": {
                "AccountNumber": "A2",
                "SupplierNumber": "6755",
                "SiteName": "POZ11976",
                "ProcurementBU": "Vision Operations"
            }
        }
    ]
}

Example 2 Response Body

The following example includes the contents of the response body in JSON format:

{
    "parts": [
        {
            "id": "a1",
            "path": "https://servername/fscmRestApi/resources/version/b2bAccountNumbers",
            "operation": "create",
            "payload": {
                "AccountNumber": "A1",
                "AccountNumberId": 300100644904658,
                "VendorId": 999992000322108,
                "VendorSiteId": 999992000341208,
                "SupplierName": "Axcense Software",
                "SupplierNumber": "6755",
                "SiteName": "POZ11976",
                "ProcurementBU": "Vision Operations"
            }
        },
        {
            "id": "a2",
            "path": "https://servername/fscmRestApi/resources/version/b2bAccountNumbers",
            "operation": "create",
            "payload": {
                "AccountNumber": "A2",
                "AccountNumberId": 300100644904659,
                "VendorId": 999992000322108,
                "VendorSiteId": 999992000341208,
                "SupplierName": "Axcense Software",
                "SupplierNumber": "6755",
                "SiteName": "POZ11976",
                "ProcurementBU": "Vision Operations"
            }
        },
		{
		. . . 
		}
    ]
}
Back to Top