> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/formula-syntax/identifiers/closedperiod.md).

# CLOSEDPERIOD

Identifies and calculate values for closed forecast periods using CLOSEDPERIOD and use NOT to reference open periods.

When you need to perform an action specific to the closed or open periods in a forecast, you can use the **.CLOSEDPERIOD** in conjunction with \[Forecast] to refer to the closed periods. To refer to the open periods, use the NOT operator along with the CLOSEDPERIOD function.&#x20;

### Example

Let us say we want to add adjustment values to the open periods while marking 'closed' for the closed periods. To refer to the closed periods, we have used \[Forecast].CLOSEDPERIOD in the example below. To check and execute the action we have used the conditional statement, [IF](/formula-syntax/conditional-statements.md).

<figure><img src="https://3062809325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEbkCXCUXmtUq5tcnUtZE%2Fuploads%2FVVeNGssbSTYTqEW17AWY%2FForecast%20reference.png?alt=media&amp;token=cbdfa46e-0ff1-4029-b254-cc8bd00ad628" alt=""><figcaption><p>Applying .CLOSEDPERIOD</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inforiver.com/formula-syntax/identifiers/closedperiod.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
