// fusionrest agent · procurement
Spend Classification Knowledge Base Transactions
spendClassificationKnowledgeBaseTransactions Based on 26C
Create, change, delete and look up Spend Classification Knowledge Base Transactions.
/fscmRestApi/resources/11.13.18.05/spendClassificationKnowledgeBaseTransactions
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE
- Record key
TransactionId- Required on create
- none marked
- At a glance
- 12 fields1 finders0 children
Try it
Response fields ·
Filters (q)
Only attributes Oracle marks as searchable are offered.
Finder
Paging and options
limit
GET /fscmRestApi/resources/11.13.18.05/spendClassificationKnowledgeBaseTransactions?fields=CategoryId,CategoryName,Item,ItemDescription,LineAmount&limit=25&onlyData=true
Response shape (placeholders)
{
"items": [
{
"CategoryId": 0,
"CategoryName": "<string, max 4000>",
"Item": "<string, max 300>",
"ItemDescription": "<string, max 2000>",
"LineAmount": 0
}
],
"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 12
| Attribute | Type | Use |
|---|---|---|
CategoryId | number | Read-onlySearchable |
CategoryName | text · max 4000 | Read-onlySearchable |
Item | text · max 300 | Read-onlySearchable |
ItemDescription | text · max 2000 | Read-onlySearchable |
LineAmount | number | Read-onlySearchable |
LineDescription | text · max 2000 | Read-onlySearchable |
SourceTransactionId | number | Read-onlySearchable |
SupplierName | text · max 360 | Read-onlySearchable |
SupplierSite | text · max 240 | Read-onlySearchable |
TransactionDescription | text · max 2000 | Read-onlySearchable |
TransactionId | number | Read-onlySearchable |
TransactionNumber | text · max 320 | Read-onlySearchable |
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.
KnowledgeBaseTransactionFinder·bindCategoryIdbindKeywordbindModelNamebindTaxonomyId
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/spendClassificationKnowledgeBaseTransactionsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
KnowledgeBaseTransactionFinderfor 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:CategoryId, notcategoryid. - 12 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.