Project Numbering Configurations
projectNumberingConfigurations Based on 26C
Change and look up Project Numbering Configurations, with project numbering configuration details. No create.
- Operations
- GET (list)GET (one)PATCH (update)
- Record key
ConfigurationId- Required on create
- no create on this resource
- At a glance
- 5 fields0 finders1 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/projectNumberingConfigurations?fields=ConfigurationId,ConfigureBy,ConfigureByCode,LastUpdateDate,LastUpdatedBy&limit=25&onlyData=true
{
"items": [
{
"ConfigurationId": "<string, max 32>",
"ConfigureBy": "<string, max 80>",
"ConfigureByCode": "<string, max 30>",
"LastUpdateDate": "2026-01-31T09:00:00+00:00",
"LastUpdatedBy": "<string, max 64>"
}
],
"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 5
| Attribute | Type | Use |
|---|---|---|
ConfigurationId | text · max 32 | Read-onlySearchable |
ConfigureBy | text · max 80 | UpdatableSearchable |
ConfigureByCode | text · max 30 | UpdatableSearchable |
LastUpdateDate | date-time | Read-onlySearchable |
LastUpdatedBy | text · max 64 | Read-onlySearchable |
Names, types, labels and flags from Oracle's REST specification (26C). Flexfield and custom attributes vary by pod: check /describe for yours.
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/projectNumberingConfigurations/{ConfigurationId}/child/<name>. Add them to a GET with expand.
ProjectNumberingConfigurationDetailsGET · POST · PATCH · DELETE Project Numbering Configuration Details · 13 fieldsConfigurationDetailIdCreatedByCreationDateDeterminantIdDeterminantNameLastUpdateDateLastUpdatedByMethodMethodCodeNextAutomaticNumberPrefixTypeTypeCode
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/projectNumberingConfigurationsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - 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:ConfigureBy, notconfigureby. - 3 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.