> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-im-wm-strm/support/faq.md).

# FAQ

<details>

<summary>How is the PreBilt language determined when using SSO?</summary>

#### When using Single Sign-On (SSO), how does PreBilt determine which language to display? Does it use the SAP user language, browser language or logon language?

When using SSO, the normal SAP logon screen is bypassed, so users cannot select a language during login.

The language displayed in PreBilt may be influenced by several factors, including:

* Browser language settings
* URL parameters such as `&sap-language=es`
* SAP language configuration
* PreBilt frontend configuration

Where language selection is required for users accessing PreBilt via SSO, a common workaround is to append a language parameter to the URL, for example:

`&sap-language=es`

For customers running multilingual warehouses, browser language settings should also be reviewed as part of troubleshooting.

</details>

<details>

<summary>Can I see who is currently using PreBilt?</summary>

#### Is there a way to see which users are currently logged in to PreBilt?

There is no dedicated "currently logged-in users" screen available within PreBilt itself.

Depending on system configuration, the following options may provide visibility into usage:

* Application Usage reporting - transaction `/TCTM/WM_APP_USAGE`
* SAP transaction SM04
* Neptune administration tools

The level of detail available will depend on the customer's configuration and PreBilt version.

</details>

<details>

<summary>Does PreBilt provide an audit trail or transaction history?</summary>

#### A user completed a transaction incorrectly. Can I see what actions were performed in PreBilt?

PreBilt itself does not provide a complete audit trail for every business transaction.

Available history depends on:

* The application being used
* SAP standard document history
* Application Usage configuration
* Customer-specific logging enhancements

Where transaction traceability is required, SAP documents and movement history should be reviewed first.

Some implementations may also use Application Usage reporting to understand which transactions were executed and by whom.

</details>

<details>

<summary>Can the Neptune user expiry period be changed?</summary>

#### Can the Neptune inactive-user expiry period be modified?

No.

The standard Neptune inactive-user expiry period of 120 days cannot be changed.

Context users are treated differently and typically remain active unless:

* Their SAP validity period expires, or
* Other user-specific restrictions are applied.

</details>