I have discovered that our SAP R/3 4.6C implementation contains a DEV/QAS instance that was configured as a schema system and the PRD instance is a non-schema system. What issues, problems, etc. could result because of this scenario?
If you look at SAP Note 151603 for instance, under Step 1 Preparations - item #2, "Establish whether you use a schema system or not". In SAP this can be checked by going to the menu option System and then selecting status. If the owner field has the <sid> value, then it is a schema system (MCOD). If the owner field shows <dbo> it is considered non schema. In our case, the DEV and QAS instances show <dev> or <qas> and the PRD instance shows <dbo>
ok, the term "schema-system" is rather uncommon if not wrong (although it is used in the note).
It's all about MCOD or pre-MCOD systems here.
Anyhow, for the ABAP-layer is does not matter what username you're actually using, as long as the environment variables/connection information are correctly setup.
Once logged on, the workprocesses don't care about the actual schema name anymore - all database objects are just refered without schemaname/owner.
SAP always recommends to use MCOD system. If you are using pre-MCOD system download "SAP Tools" from SAP service marketplace. When you run the SAP Tools there is an option named Schema Conversion which converts all objects from dbo schema to <sid> schema.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.