During the setup of your SAP Focused Run system, the Simple System Integration (SSI) SA38 report P_SSI_PREPARATION must be used. The SAP 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:
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).
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.
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.
| Database Names | Extended SID for Primary Database | Extended SID for Virtual Database | Extended SID for Replication Targets |
|---|---|---|---|
CustomerDatabase | CUSSAP | CUSSAPV | CUSSAP01 … CUSSAP09, |
EmployeeDatabase | EMPSAP | EMPSAPV | EMPSAP01 … EMPSAP09, |
FinancialDatabaseDE | FINSAP | FINSAPV | FINSAP01 … FINSAP09, |
FinancialDatabaseUS | FINSAP10 | FINSAPV0 | FINSAP11 … FINSAP19, |
StorageLocation01DB | STOSAP | STOSAPV | STOSAP01 … STOSAP09, |
StorageLocation02DB | STOSAP10 | STOSAPV0 | STOSAP11 … STOSAP19, |
StorageLocation03DB | STOSAP20 | STOSAPV1 | STOSAP21 … STOSAP29, |
StorageLocation04DB | STOSAP30 | STOSAPV2 | STOSAP31 … STOSAP39, |
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:
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. Check the appropriate database description for additional background information.