1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Inventory Management
  4. Defaults Headers for Staged Item Transactions

Get all default headers for an item-staged transaction

get

/fscmRestApi/resources/11.13.18.05/itemStagedTransactionDefaults

Request

Query Parameters
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey: Finds the default header of the item-staged transaction using the primary key.
      Finder Variables:
      • TransactionDefaultsHeaderId; integer; Value that uniquely identifies the default header of the item-staged transaction . It's a primary key that the application generates when it creates the item staged transaction default header. This attribute is required.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • ActionCode; string; Value that identifies the create or update action for a default header of an item-staged transaction.
    • CreatedBy; string; Indicates the user who created the record.
    • CreationDate; string; Date when the record was created.
    • FailedLines; integer; Value that identifies the total number of lines that failed to process for the default header of an item-staged transaction.
    • LockFlagValue; string; Value that identifies whether the header is picked for processing or not.
    • ObjectVersionNumber; integer; Indicates object version number for the record.
    • OrganizationId; integer; Value that uniquely identifies the inventory organization that's enabled for the default line of the item-staged transaction.
    • PersonName; string; Name of the user who submitted the record.
    • ProcessId; integer; Application-generated unique identifier for the request to create or update item-transaction defaults.
    • StatusCode; string; Abbreviation that identifies the default header status of an item-staged transaction.
    • StatusCodeMeaning; string; Status code meaning of an item-staged transaction.
    • SuccessfulLines; integer; Value that identifies the total number of lines processed successfully for the default header of an item-staged transaction.
    • TotalLines; integer; Value that identifies the total number of lines requested for processing for the default header of an item-staged transaction.
    • TransactionDefaultsHeaderId; integer; Value that uniquely identifies the default header of the item-staged transaction. It's a primary key that the application generates when it creates the default header of the item-staged transaction.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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.

There's no request body for this operation.

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 : itemStagedTransactionDefaults
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : itemStagedTransactionDefaults-item-response
Type: object
Show Source
Nested Schema : Attachments
Type: array
Title: Attachments
The attachments resource is used to view, create, and update attachments.
Show Source
Nested Schema : Defaults Lines for Staged Item Transactions
Type: array
Title: Defaults Lines for Staged Item Transactions
A line that???s ready to process staged item transactions.
Show Source
Nested Schema : itemStagedTransactionDefaults-Attachments-item-response
Type: object
Show Source
Nested Schema : itemStagedTransactionDefaults-ItemStagedTransactionDefaultsLine-item-response
Type: object
Show Source
  • Value that identifies the batch in which the record has been loaded into the table.
  • Maximum Length: 30
    Value that identifies the transaction type.
  • Maximum Length: 80
    Value that identifies the meaning of the transaction type.
  • Maximum Length: 240
    Code that identifies the status of the staged transaction's default lines.
  • Maximum Length: 240
    Explanation for the status of the staged transaction's default lines.
  • Value that uniquely identifies the item in the inventory organization.
  • Maximum Length: 300
    Number that identifies the item.
  • Links
  • Value that uniquely identifies the updated locator.
  • Maximum Length: 240
    Name of the updated locator in a subinventory where default lines of an item-staged transaction are created in the inventory organization.
  • Maximum Length: 10
    Name of the updated subinventory where default lines of an item-staged transaction are created in the inventory organization.
  • Value that uniquely identifies the locator prior to the update.
  • Maximum Length: 240
    Name of the locator in a subinventory prior to an update where default lines for an item-staged transaction are created in the inventory organization.
  • Maximum Length: 10
    Name of the subinventory prior to the update in which default lines for item-staged transactions are created in the inventory organization.
  • Maximum Length: 18
    Abbreviation that identifies the inventory organization that's enabled for the default line of the item-staged transaction.
  • Value that uniquely identifies the inventory organization that's enabled for the default line of the item-staged transaction.
  • Maximum Length: 240
    Name that identifies the inventory organization that's enabled for the default line of the item-staged transaction.
  • Maximum Length: 18
    Value that identifies if the status of the default lines of the staged transaction is valid.
  • Maximum Length: 11
    Name of the subinventory and locator where default lines for item-staged transactions are created in the inventory organization.
  • Value that uniquely identifies the item-staged transaction header. It's a primary key that the application generates when it creates the default header of the item-staged transaction.
  • Value that uniquely identifies the default line of the item-staged transaction. It's a primary key that the application generates when it creates the item-staged transaction default line.
Back to Top