Purchase Orders List of Values
purchaseOrdersLOV Based on 26C
Look up the list of values for Purchase Orders.
The record key purchaseOrdersLOVUniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
Oracle documents an Effective-Of header and an effectiveDate parameter for this resource, used for date-effective reads and changes.
- Operations
- GET (list)GET (one)
- Record key
purchaseOrdersLOVUniqID- Required on create
- no create on this resource
- At a glance
- 19 fields1 finders0 children
- Extra parameters
?effectiveDate=Effective-Of:
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/purchaseOrdersLOV?fields=BillToBU,BillToBUId,Buyer,BuyerId,Currency&limit=25&onlyData=true
{
"items": [
{
"BillToBU": "<string, max 240>",
"BillToBUId": 0,
"Buyer": "<string, max 240>",
"BuyerId": 0,
"Currency": "<string, max 80>"
}
],
"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 19
| Attribute | Type | Use |
|---|---|---|
BillToBU | text · max 240 | Read-onlySearchable |
BillToBUId | number | Read-only |
Buyer | text · max 240 | Read-onlySearchable |
BuyerId | number | Read-only |
Currency | text · max 80 | Read-only |
CurrencyCode | text · max 15 | Read-only |
Description | text · max 240 | Read-only |
OrderNumber | text · max 30 | Read-onlySearchable |
POHeaderId | number | Read-onlySearchable |
PaymentTerms | text · max 50 | Read-only |
PaymentTermsId | number | Read-only |
SoldToLegalEntity | text · max 240 | Read-onlySearchable |
SoldToLegalEntityId | number | Read-only |
Status | text · max 80 | Read-onlySearchable |
StatusCode | text · max 25 | Read-onlySearchable |
Supplier | text · max 360 | Read-onlySearchable |
SupplierId | number | Read-only |
SupplierSite | text · max 240 | Read-onlySearchable |
SupplierSiteId | number | Read-only |
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.
findByIntent·IntentSysEffectiveDate
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/purchaseOrdersLOVand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByIntentfor 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:BillToBU, notbilltobu. 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.