Spend Classification Knowledge Base Keyword Details
spendClassificationKnowledgeBaseKeywordDetails Based on 26C
Look up Spend Classification Knowledge Base Keyword Details. Read-only.
The record key spendClassificationKnowledgeBaseKeywordDetailsUniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
- Operations
- GET (list)GET (one)
- Record key
spendClassificationKnowledgeBaseKeywordDetailsUniqID- Required on create
- no create on this resource
- At a glance
- 7 fields1 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/spendClassificationKnowledgeBaseKeywordDetails?fields=CategoryId,CategoryName,DisableActionFlag,Keyword,KnowledgeBaseName&limit=25&onlyData=true
{
"items": [
{
"CategoryId": 0,
"CategoryName": "<string, max 4000>",
"DisableActionFlag": "<string, max 20>",
"Keyword": "<string, max 160>",
"KnowledgeBaseName": "<string, max 90>"
}
],
"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 7
| Attribute | Type | Use |
|---|---|---|
CategoryId | number | Read-onlySearchable |
CategoryName | text · max 4000 | Read-onlySearchable |
DisableActionFlag | text · max 20 | Read-onlySearchable |
Keyword | text · max 160 | Read-onlySearchable |
KnowledgeBaseName | text · max 90 | Read-onlySearchable |
NumberOfTransactions | number | Read-onlySearchable |
SerialNumber | number | 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.
KnowledgeBaseKeywordDetailsFinder·bindKeywordbindModelName
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/spendClassificationKnowledgeBaseKeywordDetailsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
KnowledgeBaseKeywordDetailsFinderfor 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.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:CategoryId, notcategoryid. onlyData=trueremoveslinks, and this resource's key only comes fromlinks. Leave it off when you need the key.- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.