Get all cost adjustments

get

/fscmRestApi/resources/11.13.18.05/costAdjustments

Request

Query Parameters
  • This query parameter is used to fetch resources which are effective dated as of the specified start date. The value of this query parameter is a string having a date in yyyy-MM-dd format
  • 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: Find the cost adjustment according to the cost adjustment identifier as the primary key.
      Finder Variables:
      • AdjustmentHeaderId; integer; Value that uniquely identifies the cost adjustment.
    • findAdjustments: Find the cost adjustments according to the specified attributes.
      Finder Variables:
      • bindAdjustmentDate; string; Date when the cost adjustment was made.
      • bindAdjustmentNumber; string; Number that identifies the adjustment.
      • bindAdjustmentStatus; string; Status of the adjustment.
      • bindAdjustmentType; string; Type of adjustment.
      • bindCostBook; string; Name of the cost book.
      • bindCostOrgName; string; Name of the cost organization.
      • bindItem; string; Name of the item.
      • bindReason; string; Reason for the cost adjustment.
      • bindReceiptNumber; string; Number that identifies the receipt transaction.
      • bindValuationUnit; string; Name of the valuation unit.
  • 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:
    • AdjustmentDate; string; Date when the cost adjustment was made.
    • AdjustmentHeaderId; integer; Value that uniquely identifies the adjustment header. The application generates this value.
    • AdjustmentNumber; string; Number that identifies the adjustment. The application generates this value.
    • AdjustmentStatus; string; Status of the adjustment. Values include Pending, Submitted, or Voided.
    • AdjustmentStatusCode; string; Abbreviation that identifies the adjustment status. Values include P-Pending, S-Submitted, or C-Voided.
    • AdjustmentType; string; Type of adjustment. Values include Perpetual, Receipt, or Layer.
    • AdjustmentTypeCode; string; Abbreviation that identifies the adjustment type. Values include P-Perpetual, R-Receipt, or L-Layer.
    • CostBook; string; Name of the cost book for the adjustment. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Books task.
    • CostBookId; integer; Value that uniquely identifies the cost book.
    • CostDate; string; Date of the costing transaction for the adjustment.
    • CostOrganizationId; integer; Value that uniquely identifies the cost organization.
    • CostOrganizationName; string; Name of the cost organization for the adjustment. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Organizations task.
    • CurrencyCode; string; Abbreviation that identifies the currency.
    • InventoryOrganizationId; integer; Value that uniquely identifies the inventory organization.
    • InventoryOrganizationName; string; Name of the inventory organization for the adjustment.
    • Item; string; Name of the inventory item for the adjustment.
    • ItemId; integer; Value that uniquely identifies the item.
    • QuantityOnhand; number; Remaining quantity of the item.
    • Reason; string; Reason for the cost adjustment transaction.
    • ReasonCode; string; Abbreviation that identifies the reason for the cost adjustment transaction.
    • ReceiptNumber; string; Number that identifies the receipt of the transaction for the adjustment.
    • ReceiptQuantity; number; Quantity of the item received.
    • TotalNewCost; number; Total new cost of the received item.
    • TotalUnitCost; number; Total cost of the received item.
    • TransactionId; integer; Value that uniquely identifies the transaction in costing.
    • UOMCode; string; Abbreviation that identifies the unit of measure.
    • UOMName; string; Name of the unit of measure.
    • ValuationUnit; string; Valuation unit for the adjustment. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Valuation Units task.
    • ValuationUnitId; integer; Value that uniquely identifies the valuation unit.
  • 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
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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 : costAdjustments
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : costAdjustments-item-response
Type: object
Show Source
Nested Schema : Cost Adjustment Details
Type: array
Title: Cost Adjustment Details
Adjustment cost at cost-element level for a receipt or an item.
Show Source
Nested Schema : costAdjustments-AdjustmentDetail-item-response
Type: object
Show Source
  • Title: Adjustment Header ID
    Read Only: true
    Value that uniquely identifies the adjustment against which this adjustment detail is created.
  • Title: Cost Element
    Maximum Length: 30
    Cost element to use when creating an adjustment detail. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Elements task.
  • Title: Cost Element ID
    Value that uniquely identifies the cost element.
  • Title: Expense Pool
    Read Only: true
    Maximum Length: 30
    Expense pool to use when creating an adjustment detail. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Expense Pools task.
  • Title: Expense Pool ID
    Value that uniquely identifies the expense pool.
  • Links
  • Title: New Cost
    New cost of the cost element.
  • Title: Source Transaction Cost ID
    Value that uniquely identifies the transaction cost identifier for which the adjustment detail is created.
  • Title: Source Transaction ID
    Value that uniquely identifies the transaction for which the adjustment is created.
  • Title: Unit Cost
    Unit cost of the cost element.
  • Title: User Adjustment ID
    Read Only: true
    Value that uniquely identifies the adjustment detail. The application generates this value.
  • Title: Comments
    Maximum Length: 240
    Optional comment entered by the user for the cost adjustment detail.
  • Title: User Defined
    Maximum Length: 5
    Contains one of the following values: true or false. If true, then adjustment detail is user defined. If false, then adjustment detail is generated from the existing cost elements associated with the item. The attribute does not have a default value.
Back to Top

Examples

This example describes how to get all cost adjustments.

<Enter the cURL command syntax>

Get All

Use the following cURL command to submit a request on the REST resource to get all cost adjustments that the database contains:

curl -u username:password "https://servername/fscmRestApi/resources/version/costAdjustments

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

{
  "items" : [ {
    "AdjustmentHeaderId" : 25,
    "AdjustmentNumber" : "25",
    "AdjustmentTypeCode" : "R",
    "AdjustmentDate" : "2017-11-15T00:00:00+00:00",
    "AdjustmentStatusCode" : "C",
    "ReasonCode" : "ST_ADJ",
    "TransactionId" : 428831,
    "CostOrganizationId" : 100000012270096,
    "CostBookId" : 100000010001016,
    "ItemId" : 149,
    "InventoryOrganizationId" : 204,
    "ReceiptQuantity" : 11,
    "QuantityOnhand" : 11,
    "TotalUnitCost" : 0.90151,
    "TotalNewCost" : 11.901518,
    "ValuationUnitId" : 300100002800067,
    "CostDate" : "2015-03-24T23:36:50+00:00",
    "ReceiptNumber" : "UPG_0071_07_R10",
    "CurrencyCode" : "USD",
    "CostOrganizationName" : "ZCST-Vision Ops",
    "CostBook" : "ZCST-Vision Ops",
    "InventoryOrganizationName" : "Vision Operations",
    "Item" : "AS54888",
    "ValuationUnit" : "ORG4-V1",
    "AdjustmentType" : "Receipt",
    "AdjustmentStatus" : "Voided",
    "Reason" : "ST_ADJ",
    "UOMCode" : "Ea",
    "UOMName" : "Each",
     ...
   }, {
     ...
   }, {
     ...
   }
   ],
   ...
}

Get All According to Adjustment Status

Use the following cURL command to submit a request on the REST resource to get all cost adjustments according to the status of the adjustment:

curl -u username:password "https://servername/fscmRestApi/resources/version/costAdjustments?findAdjustments;bindAdjustmentStatus=Submitted

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

{
  "items" : [ {
    "AdjustmentHeaderId" : 24,
    "AdjustmentNumber" : "24",
    "AdjustmentTypeCode" : "R",
    "AdjustmentDate" : "2017-11-15T00:00:00+00:00",
    "AdjustmentStatusCode" : "S",
    "ReasonCode" : "ST_ADJ",
    "TransactionId" : 428831,
    "CostOrganizationId" : 100000012270096,
    "CostBookId" : 100000010001016,
    "ItemId" : 149,
    "InventoryOrganizationId" : 204,
    "ReceiptQuantity" : 11,
    "QuantityOnhand" : 11,
    "TotalUnitCost" : 0.90151,
    "TotalNewCost" : 11.901518,
    "ValuationUnitId" : 300100002800067,
    "CostDate" : "2015-03-24T23:36:50+00:00",
    "ReceiptNumber" : "UPG_0071_07_R10",
    "CurrencyCode" : "USD",
    "CostOrganizationName" : "ZCST-Vision Ops",
    "CostBook" : "ZCST-Vision Ops",
    "InventoryOrganizationName" : "Vision Operations",
    "Item" : "AS54888",
    "ValuationUnit" : "ORG4-V1",
    "AdjustmentType" : "Receipt",
    "AdjustmentStatus" : "Submitted",
    "Reason" : "ST_ADJ",
    "UOMCode" : "Ea",
    "UOMName" : "Each",
 ...
   }, {
    ...
   }, {
    ...
   }
   ],
   ...
}
Back to Top