Background

The SAP Sourcing DBimport tool (DBimporter) is, after the SAP Sourcing configure tool, one of the most essential tools for the respective system`s setup.

To clear up a bit of confusion on this topic (e.g. how to point the SAP Sourcing DBimport tool in an expected way to an out of the box script) I hope that this blog post can help.

Overview


The SAP Sourcing dbimport tool is used to:

• execute the actual data imports into the SAP Sourcing schema upon initial installation

• execute any succeeding upgrade task scripts

• execute import scripts for language pack imports (for a list of supported SAP Sourcing languages please check the official documentation)

• execute synch scripts if specific needs would need to be met (more details on this see KBAs 1997022 and 1992162)

Screenshot of the actual SAP Sourcing dbimporter tool binaries in the SAP Sourcing binary installation directory under /bin

/wp-content/uploads/2015/02/1_629086.jpg

Specifics for the use cases for the SAP Sourcing dbimporter tool

In general the SAP Sourcing importer has two modes of operation. It can be pointed (and this is expected for all out of the box functionality unless otherwise specifically stated to deviate from it) directly at the SAP Sourcing binary installations` jar files that would contain the typical out of the box dbimport scripts you may have to execute (upgrade_schema, upgrade_data, import_netweaver_system_properties, install_language). Else for customized scripts you wouldd just directly point at the file location.

Two usage types as such for the SAP Sourcing DBimport tool:

a) executing out of the box scripts

b) executing customized scripts

Common issues

In general the official documentation does outline the specifics of how execute the scripts upon careful study very clearly. Nonetheless very typical breaking points are:

a) selection was not done in an expected way (i.e. pointing to the files contained within the out of the box jars has to be done through the dropdown menu after clicking on “…”)

NOTE: if you do not select out of the box scripts this way you may run e.g. into an “Error! Error parsing file” error

/wp-content/uploads/2015/02/2_629090.jpg

/wp-content/uploads/2015/02/3_629091.jpg

b) the respective “context” (to determine the scope) was either missed, not selected or otherwise is not matching to what the script is meant for

/wp-content/uploads/2015/02/4_629092.jpg

c) start-up problems should not occur if in the configure tool the JAVA_HOME was properly set – make always sure to use a JVM that is matching your SAP Sourcing release (else unexpected behaviour during the generation of e.g. upgrade scripts can occur)

Customized scripts

Are being pointed to in the expected way after clicking on “…” by directly pointing to them in the file system. As they aren`t packed into jars like the out of the box scripts the dropdown selection is unnecessary in this use case.

/wp-content/uploads/2015/02/5_629093.jpg

To sum up

Follow the outlying documentation to the letter and typically, unless there may be a bug, you should be having no problems to run the DBimport tool.

If you have thoughts or inputs, let me know.

Regards,

Joerg Lippmann

References


• SAP Sourcing official documentation and help: http://help.sap.com/sourcing

Installing Multiple Language Packs (Windows OS): Installing Multiple Language Packs (Windows OS)

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply