Get all project expenditure batches

get

/fscmRestApi/resources/11.13.18.05/projectExpenditureBatches

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 all project expenditure batches with the specified ID.
      Finder Variables
      • BatchId; integer; Identifier of the project expenditure batch.
  • 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:
    • BatchDescription; string; Description of the project expenditure batch.
    • BatchId; integer; Identifier of the project expenditure batch.
    • BatchName; string; Name of the project expenditure batch.
    • BatchStatus; string; Identifies the status of the project expenditure batch, for example, Submitted, Rejected, and so on. A list of valid values is defined in the lookup type PJC_TXN_BATCH_STATUS.
    • BatchStatusCode; string; Code that identifies the status of the project expenditure batch, for example, SUBMITTED, REJECTED, and so on. A list of valid values is defined in the lookup type PJC_TXN_BATCH_STATUS.
    • BusinessUnit; string; Name of the expenditure business unit that incurred the unprocessed costs in the project expenditure batch.
    • BusinessUnitId; integer; Identifier of the expenditure business unit that incurred the unprocessed costs in the project expenditure batch.
    • CreatedBy; string; The user who created the record.
    • CreationDate; string; The date when the record was created.
    • Document; string; Name of the document used to capture unprocessed costs in the project expenditure batch.
    • DocumentId; integer; Identifier of the document used to capture unprocessed costs in the project expenditure batch.
    • LastUpdateDate; string; The date when the record was last updated.
    • LastUpdatedBy; string; The user who last updated the record.
    • TransactionSource; string; Identifier of the application in which the expenditure batch was originally created.
    • TransactionSourceId; integer; Name of the application in which the expenditure batch was originally created.
  • 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 : projectExpenditureBatches
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : projectExpenditureBatches-item-response
Type: object
Show Source
  • Title: Expenditure Batch Description
    Maximum Length: 250
    Description of the project expenditure batch.
  • Read Only: true
    Identifier of the project expenditure batch.
  • Title: Expenditure Batch
    Read Only: true
    Maximum Length: 200
    Name of the project expenditure batch.
  • Title: Status
    Maximum Length: 80
    Identifies the status of the project expenditure batch, for example, Submitted, Rejected, and so on. A list of valid values is defined in the lookup type PJC_TXN_BATCH_STATUS.
  • Title: Status Code
    Maximum Length: 30
    Code that identifies the status of the project expenditure batch, for example, SUBMITTED, REJECTED, and so on. A list of valid values is defined in the lookup type PJC_TXN_BATCH_STATUS.
  • Title: Business Unit
    Read Only: true
    Maximum Length: 240
    Name of the expenditure business unit that incurred the unprocessed costs in the project expenditure batch.
  • Title: Business Unit ID
    Read Only: true
    Identifier of the expenditure business unit that incurred the unprocessed costs in the project expenditure batch.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    Read Only: true
    The date when the record was created.
  • Title: Document
    Read Only: true
    Maximum Length: 240
    Name of the document used to capture unprocessed costs in the project expenditure batch.
  • Title: Document ID
    Read Only: true
    Identifier of the document used to capture unprocessed costs in the project expenditure batch.
  • Title: Last Updated Date
    Read Only: true
    The date when the record was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the record.
  • Links
  • Title: Transaction Source
    Read Only: true
    Maximum Length: 240
    Identifier of the application in which the expenditure batch was originally created.
  • Title: Transaction Source ID
    Read Only: true
    Name of the application in which the expenditure batch was originally created.
Back to Top

Examples

The following example shows how to get all the all project expenditure batches by submitting a GET request on the REST resource using cURL.

curl --user ppm_cloud_user https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectExpenditureBatches

Response Body Example

The following shows an example of the response body in JSON format of all project expenditure batches.

{
  "items": [
    {
      "BatchId": 300100185225596,
      "BatchName": "Projects Approval",
      "BatchDescription": null,
      "BusinessUnitId": 204,
      "BusinessUnit": "Vision Operations",
      "TransactionSourceId": 100010023900191,
      "TransactionSource": "Oracle Fusion Projects",
      "DocumentId": 100010023900197,
      "Document": "Miscellaneous Expenditure",
      "BatchStatusCode": "APPROVED",
      "BatchStatus": "Approved",
      "CreatedBy": "ABRAHAM.MASON",
      "CreationDate": "2020-06-12T05:00:25+00:00",
      "LastUpdatedBy": "ABRAHAM.MASON",
      "LastUpdateDate": "2020-06-12T05:04:49+00:00",
      "@context": {
        "key": "300100185225596",
        "headers": {
          "ETag": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000378"
        },
        "links": [
          {
            "rel": "self",
            "href": "https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectExpenditureBatches/300100185225596",
            "name": "projectExpenditureBatches",
            "kind": "item"
          },
          {
            "rel": "canonical",
            "href": "https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectExpenditureBatches/300100185225596",
            "name": "projectExpenditureBatches",
            "kind": "item"
          }
        ]
      }
    }
Back to Top