Default Extended SID Handling

During the setup of your SAP Focused Run system, the Simple System Integration (SSI) SA38 report P_SSI_PREPARATION must be used. The Focused Run Master Guide recommends marking the option Enable Default Extended SID as checked.

Marking the option Enable Default Extended SID Handling as checked, causes extended SID changes at following events:

  • Whenever a technical system of the following types is initially registered in the LMDB, the default LMDB extended SID calculation is overridden by SSI:
    • Application Server ABAP
    • Application Server Java
    • Introscope Enterprise Manager (Cluster)
    • Introscope Enterprise Manager (Standalone)
    • SAP HANA Database
    • SAP liveCache
    • SAP NetWeaver Master Data Management Server
    • SAP Web Dispatcher

During registration in the LMDB, the extended SID of such technical system is set to <SID><CID> (where <SID> stands for: system ID, and <CID> stands for: customer ID).

  • Later, whenever SSI is executed, the extended SIDs of technical systems of type Database System (databases, excluding SAP HANA Databases) are changed if needed. See section Database Extended SID Renaming below. SSI execution may be triggered manually, via Web Service, or due to LMDB events.  The extended SIDs of other system types remain unchanged during SSI execution.

If you have enabled option Enable Default Extended SID Handling, we recommend that you no longer perform manual LMDB extended SID changes for technical systems of type Database System. Those changes may get reverted when running SSI.

If you perform a manual extended SID change for a technical system or database, the LMDB event handling implemented by SSI, will automatically trigger a reconfiguration for the affected technical system or database, thus ensuring configuration-consistency.

Disabling the option will not perform any of the above-mentioned extended SID changes anymore (from the point of disabling onward). Only the default LMDB extended SID calculation will be performed, whenever technical systems or databases are initially registered in the LMDB. This will result in extended SIDs such as JAV, JAV00001, JAV00002.

Database Extended SID Renaming

As described above, extended SIDs of databases (excluding SAP HANA Databases) get special treatment. The algorithm is described below, it is applied within the scope of a customer network.

  • For below example we assume following database names:
    • CustomerDatabase
    • EmployeeDatabase
    • FinancialDatabaseDE
    • FinancialDatabaseUS
    • StorageLocation01DB
    • StorageLocation02DB
    • StorageLocation03DB
    • StorageLocation04DB
  • For each primary database, we take the first 3 characters of the database name, the customer id, and add a free suffix from the 36 values available in range [none (instead of 00), 10, 20, …, 80, 90, A0, B0, …, Y0, Z0].
  • For virtual databases, the suffix is replaced by one of V/W/X/Y/Z, possibly followed by 0-9, A-Z.
  • For replication targets, the trailing 0 is replaced by one of 1-9, A-Z. See the special treatment for the mentioned “none” case illustrated below.
  • For customer SAP this gives:

Database NamesExtended SID for Primary DatabaseExtended SID for Virtual DatabaseExtended SID for Replication Targets

CustomerDatabase

CUSSAP

CUSSAPV

CUSSAP01 … CUSSAP09,
CUSSAP0A … CUSSAP0Z

EmployeeDatabase

EMPSAP

EMPSAPV

EMPSAP01 … EMPSAP09,
EMPSAP0A … EMPSAP0Z

FinancialDatabaseDE

FINSAP

FINSAPV

FINSAP01 … FINSAP09,
FINSAP0A … FINSAP0Z

FinancialDatabaseUS

FINSAP10

FINSAPV0

FINSAP11 … FINSAP19,
FINSAP1A … FINSAP1Z

StorageLocation01DB

STOSAP

STOSAPV

STOSAP01 … STOSAP09,
STOSAP0A … STOSAP0Z

StorageLocation02DB

STOSAP10

STOSAPV0

STOSAP11 … STOSAP19,
STOSAP1A … STOSAP1Z

StorageLocation03DB

STOSAP20

STOSAPV1

STOSAP21 … STOSAP29,
STOSAP2A … STOSAP2Z

StorageLocation04DB

STOSAP30

STOSAPV2

STOSAP31 … STOSAP39,
STOSAP3A … STOSAP3Z

Suffix Range Exhausted

In case for any of the described naming patterns, the pattern suffix range is exhausted, but an additional extended SID must be provided, following happens:

  • For SAP Focused Run 2.0 FP03 and higher:
    • SSI generates a “suffix range exhausted” warning, defaults to using the LMDB generated extended SID (like STO00000) and continues the SSI procedure.
  • For SAP Focused Run 2.0 FP02 and lower:
    • SSI generates a “suffix range exhausted” error and aborts the SSI procedure.
    • For SAP Focused Run 2.0 FP01 and FP02 installations, SAP Note 2907452 can be implemented, to get the improved SAP Focused Run 2.0 FP03 behavior.

If you have many database names in one customer network that all start with the same 3 characters, you may face the “Suffix Range Exhausted” issue. Database name refers to respective LMDB attribute. Following scenarios can be considered:

a)       You are fine with the fact that at some point in time the SSI extended SID calculation, defaults to LMDB extended SID calculation, for those situations where the suffix range is exhausted.

b)      You decide to provide your own implementation of BAdI BADI_SSI_SYS_IDENT_SERVICE, so that you have full programmatic control over extended SID calculation.

c)       You mark the option Enable Default Extended SID as unchecked. This option is described in the SAP Focused Run Master Guide section for Simple System Integration (SSI), on SA38 report P_SSI_PREPARATION. This will stop further SSI extended SID calculation for technical systems and for databases, from then on always applying LMDB extended SID calculation.

d)      You contact your local database experts and discuss if your company can implement a different naming schema for databases. You consider all technical and organizational aspects and risks. This would largely prevent suffix range exhausted situations. Aim at a naming schema that will not give more than 36 database names (for primary databases), with the same 3 starting characters, per customer network. In case of database rename, re-running outside discovery and re-running SSI is mandatory. Preparing Databases offers background information.