Transfer Charge Rules
transferChargeRules Based on 26C
Create, change, delete and look up Transfer Charge Rules, with rule details.
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE
- Record key
TransferChargeRuleId- Required on create
DestinationOrganizationIdDestinationOrganizationNameSourceOrganizationIdSourceOrganizationNameStartDate- At a glance
- 16 fields1 finders1 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/transferChargeRules?fields=CreatedBy,CreationDate,DestinationOrganizationCode,DestinationOrganizationId,DestinationOrganizationName&limit=25&onlyData=true
{
"items": [
{
"CreatedBy": "<string, max 64>",
"CreationDate": "2026-01-31T09:00:00+00:00",
"DestinationOrganizationCode": "<string, max 18>",
"DestinationOrganizationId": 0,
"DestinationOrganizationName": "<string, max 240>"
}
],
"count": 25,
"hasMore": true,
"limit": 25,
"offset": 0
}Shapes and placeholders, not real data. Replace https://<your-pod> and the login with your own: this site never sees them. Based on Oracle's 26C REST specification.
Fields 16
| Attribute | Type | Use |
|---|---|---|
CreatedBy | text · max 64 | Read-onlySearchable |
CreationDate | date-time | Read-onlySearchable |
DestinationOrganizationCode | text · max 18 | Optional on createUpdatableSearchable |
DestinationOrganizationId | number | Required on createUpdatableSearchable |
DestinationOrganizationName | text · max 240 | Required on createUpdatableSearchable |
EndDate | date | Optional on createUpdatableSearchable |
LastUpdateDate | date-time | Read-onlySearchable |
LastUpdatedBy | text · max 64 | Read-onlySearchable |
LastUsedDate | date-time | Optional on createUpdatableSearchable |
RuleSetName | text · max 80 | Optional on createSearchable |
SourceOrganizationCode | text · max 18 | Optional on createUpdatableSearchable |
SourceOrganizationId | number | Required on createUpdatableSearchable |
SourceOrganizationName | text · max 240 | Required on createUpdatableSearchable |
StartDate | date | Required on createUpdatableSearchable |
TransferChargeRuleId | number | Read-onlySearchable |
TransferChargeRuleSetId | number | Optional on createSearchable |
Names, types, labels and flags from Oracle's REST specification (26C). Flexfield and custom attributes vary by pod: check /describe for yours.
Finders 1
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
findTransferChargeRule·bindDestinationOrganizationCodebindRuleSetNamebindSourceOrganizationCode
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Children 1
Child resources sit under one record: /fscmRestApi/resources/11.13.18.05/transferChargeRules/{TransferChargeRuleId}/child/<name>. Add them to a GET with expand.
ruleDetailsGET · POST · PATCH · DELETE Transfer Charge Rule Details · 15 fieldsCostElementCostElementIdCostElementTypeCostElementTypeCodeCreatedByCreationDateExpensePoolCodeExpensePoolIdLastUpdateDateLastUpdatedByTransferChargeRuleDetailIdTransferChargeRuleIdTransferChargeTypeTransferChargeTypeCodeTransferChargeValue
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/transferChargeRulesand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findTransferChargeRulefor the agent's main search: its variables become clean tool parameters. - Narrow with
q=on searchable fields and a smalllimit; for a count usetotalResults=true&limit=1. - Call once and pass the result on to later steps rather than calling the same endpoint again.
- This resource can change data. Put a human approval step before any create, update, delete or action call.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:DestinationOrganizationCode, notdestinationorganizationcode. - 5 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
- Send dates as
YYYY-MM-DD; date-time fields take ISO 8601 with a time zone. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through. - Text fields have maximum lengths (shown in the field table). Longer values are rejected.