Get a period status

get

/fscmRestApi/resources/11.13.18.05/accountingPeriodStatusLOV/{accountingPeriodStatusLOVUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- PeriodNameId, ApplicationId and LedgerId ---for the Accounting Period Status List of Values resource and used to uniquely identify an instance of Accounting Period Status List of Values. The client should not generate the hash key value. Instead, the client should query on the Accounting Period Status List of Values collection resource with a filter on the primary key values in order to navigate to a specific instance of Accounting Period Status List of Values.

    For example: accountingPeriodStatusLOV?q=PeriodNameId=<value1>;ApplicationId=<value2>;LedgerId=<value3>
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : accountingPeriodStatusLOV-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 1
    The indicator of the calendar adjustment period status.
  • Read Only: true
    The unique identifier of the application.
  • Title: Status
    Read Only: true
    Maximum Length: 1
    The indicator of the closing status of an accounting period, whether the period is open or closed. Valid values include O for Open, C for Closed, F for Future Enterable, N for Never Opened, P for Permanently Closed and W for Close Pending.
  • Read Only: true
    The internally derived denormalized period number used to identify a period name. The effective period number for the accounting period name can be derived as (PERIOD_YEAR*10000 + PERIOD_NUM). For example, the effective period number for the first month of the year 2019 would be (2019*10000+1) = 20190001.
  • Title: End Date
    Read Only: true
    The date when the accounting period ends.
  • Read Only: true
    The unique identifier of the ledger.
  • Links
  • Title: Accounting Period
    Read Only: true
    Maximum Length: 15
    The accounting period name in a calendar.
  • Title: Period Number
    Read Only: true
    An unique period number within the accounting calendar year.
  • Title: Year
    Read Only: true
    The accounting calendar year represented by a numerical value, such as 2019.
  • Title: Start Date
    Read Only: true
    The date when the accounting period begins.
Back to Top

Examples

The following example shows how to retrieve a period status by submitting a GET request on the REST resource using cURL.

curl -i -u "<username>:<password>" -H "Content-Type: application/json" -X GET https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/accountingPeriodStatusLOV/0003000000064A756E2D31390000000EACED0005770800000000000027350000000EACED00057708000110F080AADDE3

Example Response Body

The following example shows the contents of the response body in JSON format:

{
    "PeriodNameId": "Jun-19",
    "ApplicationId": 10037,
    "LedgerId": 300100113587683,
    "ClosingStatus": "N",
    "EndDate": "2019-06-30",
    "StartDate": "2019-06-01",
    "EffectivePeriodNumber": 20200003,
    "PeriodYear": 2020,
    "PeriodNumber": 3,
    "AdjustmentPeriodFlag": false,
    "links": [
        {
            "rel": "self",
            "href": "http://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/accountingPeriodStatusLOV/0003000000064A756E2D31390000000EACED0005770800000000000027350000000EACED00057708000110F080AADDE3",
            "name": "accountingPeriodStatusLOV",
            "kind": "item"
        },
        {
            "rel": "canonical",
            "href": "http://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/accountingPeriodStatusLOV/0003000000064A756E2D31390000000EACED0005770800000000000027350000000EACED00057708000110F080AADDE3",
            "name": "accountingPeriodStatusLOV",
            "kind": "item"
        }
    ]
}
Back to Top