1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Inventory Management
  4. Cycle Count Transactions

Create transactions

post

/fscmRestApi/resources/11.13.18.05/cycleCountTransactions

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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Count Lines
Type: array
Title: Count Lines
The Count Lines resource manages transaction details for the count sequence.
Show Source
Nested Schema : schema
Type: object
Show Source
Nested Schema : Flexfields for Count Lines
Type: array
Title: Flexfields for Count Lines
The Flexfields for Count Lines resource manages details of the descriptive flexfields that reference the count lines.
Show Source
Nested Schema : Flexfields for Tracking Attributes
Type: array
Title: Flexfields for Tracking Attributes
The Flexfields for Tracking Attributes resource manages details of the descriptive flexfields that reference the count lines.
Show Source
Nested Schema : cycleCountTransactions-countLines-countLinesDFF-item-post-request
Type: object
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 : cycleCountTransactions-item-response
Type: object
Show Source
Nested Schema : Count Lines
Type: array
Title: Count Lines
The Count Lines resource manages transaction details for the count sequence.
Show Source
Nested Schema : cycleCountTransactions-countLines-item-response
Type: object
Show Source
Nested Schema : Flexfields for Count Lines
Type: array
Title: Flexfields for Count Lines
The Flexfields for Count Lines resource manages details of the descriptive flexfields that reference the count lines.
Show Source
Nested Schema : Flexfields for Tracking Attributes
Type: array
Title: Flexfields for Tracking Attributes
The Flexfields for Tracking Attributes resource manages details of the descriptive flexfields that reference the count lines.
Show Source
Nested Schema : cycleCountTransactions-countLines-countLinesDFF-item-response
Type: object
Show Source
Nested Schema : cycleCountTransactions-countLines-inventoryAttributesDFF-item-response
Type: object
Show Source
Links
countLines
Parameters:
  • cycleCountTransactionsUniqID: $request.path.cycleCountTransactionsUniqID
The Count Lines resource manages transaction details for the count sequence.
Back to Top

Examples

This example describes how to process cycle count transactions.

Example cURL Command

Use the following cURL command to submit a request on the REST resource. This example processes cycle count transactions for item CYC01-100, that occur on 2011-07-14, in subinventory FGI, in organization M1, counted by employee 57, for cycle count CC-RRF:

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

Example 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. 

{
  "countLines": [
    {
      "OrganizationCode": "M1",
      "CountName": "CC-RRF",
      "Item": "CYC01-100",
      "CountQuantity" : 510,
      "CountUnitOfMeasure": "Each",      
      "CountDate": "2011-07-14",
      "CountedByEmployeeId" : 57,
      "Subinventory": "FGI" 
    }
  ]
}

Example Response Body

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

{
  "ReturnStatus" : "SUCCESS",
  "ErrorCode" : null,
  "ErrorExplanation" : null,
  "ErrorUniqueTransactionId" : "0",
  "countLines" : [ {
    "UniqueTransactionId" : 300100090015943,
    "OrganizationId" : null,
    "OrganizationCode" : "M1",
    "CycleCountHeaderId" : null,
    "CountName" : "CC-RRF",
    "CycleCountEntryId" : null,
    "CountSequence" : null,
    "InventoryItemId" : null,
    "Item" : "CYC01-100",
    "Revision" : null,
    "Subinventory" : "FGI",
    "LocatorId" : null,
    "Lot" : null,
    "SerialNumber" : null,
    "CountUOM" : null,
    "CountUnitOfMeasure" : "Each",
    "CountQuantity" : 510,
    "CountDate" : "2011-07-14",
    "SecondaryCountQuantity" : null,
    "SecondaryUnitOfMeasure" : null,
    "SecondaryUOM" : null,
    "CountedByEmployeeName" : null,
    "CountedByEmployeeId" : 57,
    "Comments" : null,
    "Reason" : null,
    "TransactionReasonId" : null,
    "OwningType" : null,
    "OwningEntityId" : null,
    "OwningEntityCode" : null,
    "ProcurementBU" : null,
    "VendorName" : null,
    "VendorNumber" : null,
    "ConsignmentAgreementNumber" : null,
    "LocatorName" : null
  } ]
}
Back to Top