SAP AS ABAP Administration · OS Integration: Directory Structure & Users

On a distributed SAP system, why must /sapmnt/<SID> be a single shared filesystem rather than a separate copy on each host, and what breaks if a host can't reach it?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in OS Integration: Directory Structure & Users

A colleague proposes 'prd' as the SID for the new production system. It's short and three characters, yet installation rejects it. What are the hard rules for a valid SID?

At install you're prompted for both a SAPSID and a DBSID. Can they differ, should they, and is there a case that forces them apart?

OS-level abbreviations like ms, dw, and gwrd tell you a process type but not what an SAP process is currently doing. Where are those abbreviations defined, and what are ms and gwrd?

You already watch the fill level of the database and log filesystems. Why does SAP insist you also clean up the transport and instance directories, and what actually breaks if you don't?

Under the \usr\sap root you see two Windows shares, sapmnt and saploc, but on a UNIX host you don't. How is the same central-access mechanism achieved on each OS?

The team wants 'SAP' or 'TMP' as a memorable system ID. Both are three capital letters starting with a letter, yet the installer still blocks them. Why?

Start learning today

Free to start — download the app or use it in your browser.