Forbidden, allowed and recommended database issues
This post´s goal is to clarify what SAP says about database manipulation. I think it is not clear yet, as you can see (there will be more for sure).
So i can guess there are 3 possible answer about database manipulation issues, Forbidden, allowed and recommended (For certification).
The topics that come to my mind are:
In SBO database:
- Creating tables using SQL statement (non SBO).
- Creating Stored Procedures.
- Creating Functions
- Creating Views
- Creating Triggers against SBO tables
- Creating Triggers against non SBO tables
- Making Select statemens (from any SP, function or view)
- Making inserts/updates/delete statements against SBO tables.
- Making inserts/updates/delete statements against SBO user tables.
- Making inserts/updates/delete statements against non SBO tables.
In another database:
- Creating Stored Procedures that get data from SBO.
- Creating Stored Procedures that change data in SBO.
- Creating Functions against SBO data.
- Creating Views against SBO data.
I hope Frank can clarify all this and the ones from other people.
Some of them are clear in the previous posts, but I´m looking for a full information post. If we make it complete, perhaps I could create a weblog with the information.
Frank Moebius replied
1. There's a Forum in the ICC area here on SDN where SAP ICC can be asked questions about
certification criteria (note: SAP ICC is in the end responsible for the execution).
2. I (or someone from ICC) am going to write a Weblog which clarifies the cert. requirements
and the motiviation for each of them (the motivation / overall goals / context is important)
in a comprehensive way.
(I just applied to become a Weblogger ;-); ...but I won't be able to do so in the next 2 weeks ...)
3. However, I will answer your questions around the database here:
Forbidden ("-"), allowed ("0") and recommended ("+") for <b>certification</b>
(may be stricter than SAP Support).
In B1 Company database:
-/0/+ --------------------------------------------------- 0 Creating tables using SQL statement (non B1); not recommended though. - Creating Stored Procedures. - Creating Functions 0 Creating Views - Creating Triggers on B1 tables - Creating Triggers on non B1 tables 0 Making Select statements (from any SP, function or view) - Making inserts/updates/delete statements on B1 tables. 0 Making inserts/updates/delete statements on "No Object" UDTs. 0 Making inserts/updates/delete statements on non B1 tables. In another database: 0 Creating Stored Procedures that get data from B1. 0 Creating Stored Procedures that change data in "No Object" UDTs in B1. - Creating Stored Procedures that change data in B1 tables. 0 Creating Functions on B1 data, IF these functions don't change B1 data of course. 0 Creating Views on B1 data.
The <b>only</b> <u>recommended</u> way to work with the database is:
<b>NOT</b> to work directly with the database!
However, today this would just be the ideal case; unfortunately we are not there yet.
Edited by: Frank Moebius on Feb 28, 2008 4:49 PM