Collaboration Document Metadata
collaborationDocumentMetadata Based on 26C
Look up Collaboration Document Metadata, with document measure metadata. Read-only.
- Operations
- GET (list)GET (one)
- Record key
DocumentTypeCode- Required on create
- no create on this resource
- At a glance
- 8 fields1 finders1 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/collaborationDocumentMetadata?fields=CustomerLevelCode,DocumentMetadataId,DocumentTypeCode,DocumentTypeName,ItemLevelCode&limit=25&onlyData=true
{
"items": [
{
"CustomerLevelCode": "<string, max 30>",
"DocumentMetadataId": 0,
"DocumentTypeCode": "<string, max 30>",
"DocumentTypeName": "<string, max 80>",
"ItemLevelCode": "<string, max 30>"
}
],
"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 8
| Attribute | Type | Use |
|---|---|---|
CustomerLevelCode | text · max 30 | Read-onlySearchable |
DocumentMetadataId | number | Read-onlySearchable |
DocumentTypeCode | text · max 30 | Read-onlySearchable |
DocumentTypeName | text · max 80 | Read-onlySearchable |
ItemLevelCode | text · max 30 | Read-onlySearchable |
ItemResolutionCode | text · max 30 | Read-onlySearchable |
OrganizationLevelCode | text · max 30 | Read-onlySearchable |
StatusCode | text · max 30 | 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.
RowFinder·DocumentTypeCode
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/collaborationDocumentMetadata/{DocumentTypeCode}/child/<name>. Add them to a GET with expand.
documentMeasureMetadataGET Document Measure Metadata · 12 fieldsCurrentCycleFlagDisplayNameDocumentMeasureMetadataIdEditStartDateEndDateExpiringMeasureFlagMeasureTypeCodeParticipantOwnerCodeParticipantOwnerNameSequenceStartDateTimeSeriesFlag
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/collaborationDocumentMetadataand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
RowFinderfor 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:CustomerLevelCode, notcustomerlevelcode. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.