Jump to

• Request
• Response

Rebuild transaction accounts

post

/fscmRestApi/resources/11.13.18.05/draftPurchaseOrders/{draftPurchaseOrdersUniqID}/child/lines/{POLineId}/child/schedules/{schedulesUniqID}/child/distributions/{distributionsUniqID}/action/rebuildAccounts

Derives transaction accounts for purchase order distributions.

Request

Path Parameters

• POLineId(required): integer(int64)
  The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
• distributionsUniqID(required): string
  This is the hash key of the attributes which make up the composite key for the Distributions resource and used to uniquely identify an instance of Distributions. The client should not generate the hash key value. Instead, the client should query on the Distributions collection resource in order to navigate to a specific instance of Distributions to get the hash key.
• draftPurchaseOrdersUniqID(required): string
  This is the hash key of the attributes which make up the composite key for the Draft Purchase Orders resource and used to uniquely identify an instance of Draft Purchase Orders. The client should not generate the hash key value. Instead, the client should query on the Draft Purchase Orders collection resource in order to navigate to a specific instance of Draft Purchase Orders to get the hash key.
• schedulesUniqID(required): string
  This is the hash key of the attributes which make up the composite key for the Schedules resource and used to uniquely identify an instance of Schedules. The client should not generate the hash key value. Instead, the client should query on the Schedules collection resource in order to navigate to a specific instance of Schedules to get the hash key.

Header Parameters

• Metadata-Context: string
  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".
• REST-Framework-Version: string
  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.

Supported Media Types

• application/vnd.oracle.adf.action+json

Request Body - application/vnd.oracle.adf.action+json ()

Root Schema : schema

Type: object

Show Source

• initiatingParty: string
  Name of the party that requested the derivation of transaction accounts. Valid values are Buyer and Requester.

{
    "type":"object",
    "properties":{
        "initiatingParty":{
            "type":"string",
            "description":"Name of the party that requested the derivation of transaction accounts. Valid values are Buyer and Requester.",
            "nullable":true
        }
    },
    "additionalProperties":false
}

Back to Top

Response

Supported Media Types

• application/json
• application/vnd.oracle.adf.actionresult+json

Default Response

The following table describes the default response for this task.

Body ()

Root Schema : schema

Type: object

Show Source

• result(required): string
  If the request is successful, then this action returns a value of Success. Otherwise, this action returns a value of Failure.

{
    "required":[
        "result"
    ],
    "type":"object",
    "properties":{
        "result":{
            "type":"string",
            "description":"If the request is successful, then this action returns a value of Success. Otherwise, this action returns a value of Failure."
        }
    },
    "additionalProperties":false
}

Back to Top