Skip to Content
Author's profile photo Former Member

Pitfalls in Track Based Development – Part 2


Track based development in the Java stack simplifies the life of developer and system administrators to a great extent.

This is a continuation of the first blog Pitfalls in Track Based Development – Part 1.

Dictionary DC’s are again the focus of this blog. 

You can create Simple Data Types, Structures and Database Tables using
Dictionary DC. These are reusable and can be used in any other DC

One of the usage scenarios of Database Tables (Dictionary DCs) arises while developing applications for the extranet. You may need few master data available locally for webdynpro/java applications. Table DC’s fits the bill.

The problem is when the table DC’s are activated and deployed(Pitfalls in Track Based Development – Part 1), the tables are created in the same database schema (SAP*Application data and system data are being stored in the same database schema <strong>(SAP<SID>DB)</strong>. You cannot avoid it. No configuration options are available in NW2004 to change the deployment target to any other database.*

This limits the use of table DC’s in many cases. Application designers will prefer using  traditional tables where in they can control deployment.

System administrators should be beware when the transport contains table DC’s. 

Next blog will discuss the transport mechanism in track based development

Pitfalls in Track Based Development – Part 1. </p>

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.