Importance of Common Database in SAP B1

hi guys,
Up to this point, its not very clear to me if it is necessary to back the Common Database of SAP business one.
As per documentation, it states that Common database includes tables for basic initialization of any new company database (for example, built-in reports and system queries). This means that every new database created, this is the time when Common Database is update or something?
My main concern here is, is it necessary for me to back/restore both the common and reg company database? I need to know this as early as possible because I am not backing up this common database .
Thanks,
Beth

hello Lili,
The common database stores required tables that used when run company databases. it is System Databases. In addition to the SAP Business One company database with the application data, you should backup the database SBO-Common once after installation, and after each upgrade.
when creating new company database, there maybe updating process of common database beside upgradingPL.
Based on securityguide file, it states:
Creating the SBO_SP_Role in Each New Database
This role enables execution permissions only to SAP Business One stored procedures in the specific database.
The following procedure should be carried out on the SBO-COMMON database and the company database.
1. On the Microsoft SQL Server Management Studio navigation pane, choose Databases → SBO-COMMON (or company database) → Security → Roles → Database Roles.
Right Click and choose New Database Role Database Role New window appears.
2. Enter SBO_SP_Role in the Name field and choose OK.
The list of Roles appears in the right pane.
3. Double-click the new role and choose from the left pane Securables.
4. From the right pane, press the Add button. The Add Objects window appears.
5. On the Add Objects window choose All Objects of the Types and press OK. The Select Objects Types window appears. Choose Stored Procedures. Press OK to confirm and close the window.
6. For SAP Business One stored procedures, select the EXEC option in the bottom pane.
Stored procedures might change in future releases of SAP Business One, therefore, this role should be updated accordingly. Instructions to change the role due to changed stored procedures will be included in the documentation of future versions.
See Appendix A Stored Procedures in SBO-Common and Appendix B - Stored Procedures for Regular Company
Rgds,

Similar Messages

Import failed when Import a SBO Database in SAP Hana

Hi all,
When I try to import a SBO database Rev 69 to SAP Hana with Rev 74, I receive this error:
SAP DBTech JDBC: [2048]: column store error: table import failed: [30151] Object not found in the import directory;object=SBOCOMMON:ETL_Sen
I guess that the error not have relationship with different Revs. I imported another DB with this Rev and this work.
The import was done in 2 ways:
Script:
IMPORT DATABASE."*" FROM '<directory>' WITH REPLACE
Click right in Database, Import, select directory, select tables, import...
Does anyone know what can be or the solution??
Thanks
Best regards
Marcos Taira

Hello Marcos.
You could check this note.
1981315 - HANA import fails with error "not found in the import directory"
Regards.
Mario.

DTW error "Unable to access SBO-Common database " for sap hana

Hi.. Experts
I am working on SAP Hana Pl 04 64 bit, On which I got the error "Unable to access SBO-Common database " While using DTW.
also company databases are also not presents,For more details for more details find out attachment.
I have also check out all services & Restart them.
Please give me proper solution.

Hi,
Please check:
1.Ensure you have the correct DB Type selected under the Login options.
2.Verify that all connection information is correct (for example, the correct user name and password or the user has enough right to connect to the database server in case Windows Authentication is used).
3. Check whether the database is running properly, make sure that the COMMON and company databases are not suspended or stopped.
4. Ensure there is no DI API version mismatch.
Thanks & Regards,
Nagarajan

-111: Unable to access SBO-Common database

Dear all,
I am getting following error in addon.
Error Code:-111
Error Message: Unable to access SBO-Common database
My SAP version is : SAP 9.0 PL 11
Please give me some solution

Hi Pravin,
mostl likely your sa password is wrong.
On what line do you get this error?
Regards
Ad

DTW error in SAP hana "Unable to access SBO-Common database"

Hi.. Experts
I am working on SAP Hana Pl 04 64 bit, On which I got the error "Unable to access SBO-Common database " While using DTW.
also company databases are also not presents,For more details for more details find out attachment.
I have also check out all services & Restart them.
Please give me proper solution.

Discussion moved from SAP Business One (中文) to SAP Business One Application
Find Topic Spaces on SCN (Forums)

Whats the important of " table-type " in sap abap?

hi,
i am ahmed. abap fresher.
i want to what use and importance of table-type in sap abap which comes in
                     datadictionary
                            V
                    data types
V----
V                         V                                 V
data element       structure                   table type
i want to know about table type. plz give a brief idea.
bye.

hi,
Transparent Tables
A transparent table in the dictionary has a one-to-one relationship with a table in the database. Its structure in R/3 Data Dictionary corresponds to a single database table. For each transparent table definition in the dictionary, there is one associated table in the database. The database table has the same name, the same number of fields, and the fields have the same names as the R/3 table definition. When looking at the definition of an R/3 transparent table, it might seem like you are looking at the database table itself.
Transparent tables are much more common than pooled or cluster tables. They are used to hold application data. Application data is the master data or transaction data used by an application. An example of master data is the table of vendors (called vendor master data), or the table of customers (called customer master data). An example of transaction data is the orders placed by the customers, or the orders sent to the vendors.
Transparent tables are probably the only type of table you will ever create. Pooled and cluster tables are not usually used to hold application data but instead hold system data, such as system configuration information, or historical and statistical data.
Both pooled and cluster tables have many-to-one relationships with database tables. Both can appear as many tables in R/3, but they are stored as a single table in the database. The database table has a different name, different number of fields, and different field names than the R/3 table. The difference between the two types lies in the characteristics of the data they hold, and will be explained in the following sections.
Table Pools and Pooled Tables
A pooled table in R/3 has a many-to-one relationship with a table in the database (see Figures 3.1 and 3.2). For one table in the database, there are many tables in the R/3 Data Dictionary. The table in the database has a different name than the tables in the DDIC, it has a different number of fields, and the fields have different names as well. Pooled tables are an SAP proprietary construct.
When you look at a pooled table in R/3, you see a description of a table. However, in the database, it is stored along with other pooled tables in a single table called a table pool. A table pool is a database table with a special structure that enables the data of many R/3 tables to be stored within it. It can only hold pooled tables.
R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each). Table pools reduce the amount of database resources needed when many small tables have to be open at the same time. SAP uses them for system data. You might create a table pool if you need to create hundreds of small tables that each hold only a few rows of data. To implement these small tables as pooled tables, you first create the definition of a table pool in R/3 to hold them all. When activated, an associated single table (the table pool) will be created in the database. You can then define pooled tables within R/3 and assign them all to your table pool (see Figure 3.2).
Pooled tables are primarily used by SAP to hold customizing data.
When a corporation installs any large system, the system is usually customized in some way to meet the unique needs of the corporation. In R/3, such customization is done via customizing tables. Customizing tables contain codes, field validations, number ranges, and parameters that change the way the R/3 applications behave.
Some examples of data contained in customizing tables are country codes, region (state or province) codes, reconciliation account numbers, exchange rates, depreciation methods, and pricing conditions. Even screen flows, field validations, and individual field attributes are sometimes table-driven via settings in customizing tables.
During the initial implementation of the system the data in the customizing tables is set up by a functional analyst. He or she will usually have experience relating to the business area being implemented and extensive training in the configuration of an R/3 system.
Table Clusters and Cluster Tables
A cluster table is similar to a pooled table. It has a many-to-one relationship with a table in the database. Many cluster tables are stored in a single table in the database called a table cluster.
A table cluster is similar to a table pool. It holds many tables within it. The tables it holds are all cluster tables.
Like pooled tables, cluster tables are another proprietary SAP construct. They are used to hold data from a few (approximately 2 to 10) very large tables. They would be used when these tables have a part of their primary keys in common, and if the data in these tables are all accessed simultaneously. The data is stored logically as shown in Figure 3.3.
Figure 3.3 : Table clusters store data from several tables based on the primary key fields that they have in common.
Table clusters contain fewer tables than table pools and, unlike table pools, the primary key of each table within the table cluster begins with the same field or fields. Rows from the cluster tables are combined into a single row in the table cluster. The rows are combined based on the part of the primary key they have in common. Thus, when a row is read from any one of the tables in the cluster, all related rows in all cluster tables are also retrieved, but only a single I/O is needed.
A cluster is advantageous in the case where data is accessed from multiple tables simultaneously and those tables have at least one of their primary key fields in common. Cluster tables reduce the number of database reads and thereby improve performance.
For example, as shown in Figure 3.4, the first four primary key fields in cdhdr and cdpos are identical. They become the primary key for the table cluster with the addition of a standard system field pageno to ensure that each row is unique.
Reward if helpful
Jagadish

Shrink SBO COMMON Database

I found that the log file of my customer's SBO COMMON Database is too large.
Is it important? Can I just shrink it without disturbing my customer's process?
Will the SAP performance be better after I shrink the log file of SBO COMMON?
Edited by: jupitercd on Sep 14, 2011 2:18 PM

Hi,
How many companies do you maintain in a single application server? instead of shrinking the Sbo-common,why dont you restore it to its original size? As far as i know, Common will just gather info of all DB's installed in the app server and it will keep it(add-on info, patch level and etc.) on my own opinion,its better to restore than to shrink.(how to restore?get a new common from a newly installed system with same patch level and restore it into your live DB. )
Regards,
Darius Gragasin

Export/import to/from database

hi,
i do not know what is this for. i read the help but still no idea.
i know to use export/import to/from memory id and also set/get but not export/import to/from database.
1) what help says it stores data cluster? what is data cluster
2) can have example of export/import to/from database?
3) what is the different for export/import to/from memory id and database?
thanks

Hi,
1) A data cluster is a set of data objects grouped together for the purpose of storage in a storage medium(Like database, local memory or shared meomory etc), which can only be edited using ABAP statements like EXPORT, IMPORT and DELETE.
2) Suppose you want to export the data in a internal table to database.
Here TABLE_ID is the identifer of your data cluster. You are exporting your data to a SAP table INDX and giving it an ID (TABLE_ID in this case and this ID you are giving it an area by name XY where your data will be stored). EXPORT tab = itab
TO DATABASE indx(XY)
CLIENT '000'
ID 'TABLE_ID'.
You can get this data as follows.
IMPORT tab = itab
FROM DATABASE indx(xy)
CLIENT '000'
ID 'TABLE_ID'.
3) The difference is simple when you use MEMORY ID the data you export is stored in the application server MEMORY where as in the case of DATABASE it is stored in the database.
Regards,
Sesh

Import Error - IMPORT hist FROM DATABASE MONI(DB) ID MONIKEY

Hi,
   Iin my program I am using the statement
IMPORT hist FROM DATABASE MONI(DB) ID MONIKEY.
and Internal table structure of HIST is
DATA: BEGIN OF HIST OCCURS 0,
          DATE LIKE SY-DATUM,
          TIME LIKE SY-UZEIT,
          SIZE      TYPE P,
          FREE      TYPE P,
          USED      TYPE I,
          TABLES    TYPE I,
          INDICES   TYPE I,
          TSIZE     TYPE I,
          ISIZE     TYPE I,
         END OF HIST.
This IMPORT STatement is giving dump :
Runtime Errors         CONNE_IMPORT_WRONG_COMP_TYPE
Except.                CX_SY_IMPORT_MISMATCH_ERROR
Is that any way to check before this IMPORT statement,that HIST structure should be like this or like that.If I can find out the correct structure.I can change the HIST's structure and avoid the dump.
Guide me on this.
Regards,
Ashok

please refer to the SAP note 1000275
i got the same error so i rectified it by changing fields type of hist2 .
below declaration of hist2 data is giving error
data: begin of hist2 occurs 0,
        date like sy-datum,
        time like sy-uzeit,
        size      type p,     "Changed to 'p'
        free      type p,     "Changed to 'p
        used      type i,
        tables    type i,
        indices   type i,
        tsize     type i,
        isize     type i,
      end of hist2.
error rectified with below hist2 data( tsize and isize type is changed to p)
data: begin of hist2 occurs 0,
        date like sy-datum,
        time like sy-uzeit,
        size      type p,     "Changed to 'p'
        free      type p,     "Changed to 'p
        used      type i,
        tables    type i,
        indices   type i,
        tsize     type p,
        isize     type P,
      end of hist2.

Truncate or Shrink the SBO-COMMON Database in B1.

Hello everybody!!
I need to know if it's safe to either truncate or shrink the SBO-COMMON database. I kow all recovery trail will be lost, but that doesn't matter much, since I'm planning to switch from "full recovery" to "simple" recovery model. The database is backed up on a daily basis, so only the last back up of the databse is relevant.
In notes 625546, 783183 and 548772 SAP clearly states that truncating or shrinking a production database is a safe procedure, but what about the SBO-COMMON? I guess one can follow the same rationale as in the production databases, but I'm not sure.
Thanks for any valuable help.
Emilio Méndez.

Ross:
Thanks a lot for the advice. I'm still triyng to get official word from SAP through a message in the Market Place. Anyhow, I'm going to take your adivce as a "best practice" for a reasonable maintenace plan to the databases used by B1.
I'm only waiting for some other comments before I mark the thread as "answered".
Thanks a lot for the help,
Emilio Mendez.

Upgrade of Common Database Failed (8.8)

Hi All,
I have succesfully installed SAP Business One 8.8 PL 10. Howerver when I try to upgrade to PL 12 I receive 'Upgrade of Common Database Failed'.
Any Idea?

I have the same issue: Common database upgrade failed with "Internal error (-805306369) occurred"

Convert SQL server database into SAP readable (encrypted) XML for SAP tool?

Could anyone kindly let me know what is the procedure to convert SQL server database into SAP readable (encrypted) XML for SAP Authoring tool???

So If I understood it correctly there an existing propriertory question bank with SQL server. You are looking at an option to migrate all the tests and questions from the existing system to the LSO system. Right ?
I am still not clear on the xml conversion. Have you guys found a solution which could be achieved through a xml file ?
am not aware of a way through which you could import only a xml file and create tests/questions. If you have a sample xml file then forward me so that I could do some testing on my end.As per my knowledge you could do one of the following. I
1. Create the tests and questions manually in Authoring Environment. It will be a time consuming task. Based on the number of questions you have you might have to assemble a team of content developers to acheive this.
2. Alternatively, you could create a Adobe Flash based assessment. The Flash component would be the front-end and will read from a xml file to display the questions and to drive the funcationality. This would be a easier and less time consuming than creating the assessments manually in authoring environment. However, you might miss out some of the functionality available in the Test Author of Authoring Environment unless you have all the functionality replicated inside Flash. This would require one time effort in creating the Flash template and the xml file structure. Once that is created you could create multiple assessments by just replacing the xml file. If you select this approach then you would have to ensure the data from SQL is converted in the desired xml format required by your Flash component.
Please let me know if you require any further guidance or clarification regarding this.
Regards,
Ravi Sekhar

Connecting 2 systems using 1 common database

Hi,
we have a common database SQL server for SAP and .Net system.
Can we do a database link between these two systems??
Can we do directly get the values from .net tables and put into temp db and process from that temp db into SAP??
Is that advicable??Please help me.
Appreciate for the quick response.
krishna.

Hey,
You should use the .Net connector,
in order to execute RFC:
please read note 533055 and 506603
and check
COM and .NET Connector
there is a good documentation here:
https://websmp109.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000050068&
p.s
you should mark the function module in se37, as RFC enable (remote function call)

Help on export sybase iq tables with data and import in another database ?

Help on export Sybase iq 16 tables with data and import into another database ?

Hi Nilesh,
If you have table/index create commands (DDLs), you can create them in Developper and import data using one of methods below
Extract/ Load table
Insert location method : require IQ servers to be entered in interfaces file
Backup/Restore : copy entire database content
If you have not the DDLs, you can generate them using IQ cockpit or SCC.
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01773.1604/doc/html/san1288042631955.html
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01840.1604/doc/html/san1281564927196.html
Regards,
Tayeb.

How can I import microsoft outlook database from an external harddisk?

My macbook pro was washed. I could save the hard disk. I am using it like external harddisk. But I want to import the outlook database to my new macbook. how can I do it? (without .pst or .olm file)

Hello DIRP,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
iTunes: About the Add to Library, Import, and Convert functions
http://support.apple.com/kb/ht1347
Best of luck,
Mario

Importance of Common Database in SAP B1

Similar Messages

Maybe you are looking for