Sap usage is forbidden by software component

If it is probable or known that the structure of a component hierarchy will change for example, a child component will be taken out of its parent's enclosure , the name must not refer to the relationship. The name example. Therefore, the workspace identifier must not be part of the DC's name. Component names should not contain versioning or state information of any kind. This includes, for example, things like specification and implementation versions used on the Java EE platform.

Component names must have a globally unique vendor identifier. This identifier is usually derived from an Internet domain that belongs to the vendor for example, sap. If the Internet domain with the identifier example. This makes your component names unique among all vendors.

Component names should not contain identifiers of developers, groups, or departments of a company. Responsibilities may change, but component names must not. Furthermore, do not use time-stamps, dates, hosts, and so on. Component names should reflect the intended purpose and functionality of a component, and nothing else. But package concept has many other use cases — we can define dependencies to other packages of SAP standard as well to your own packages: You can define dependencies to SAP standard.

In a larger development project you can structure your application. You can define your own stable APIs to tell the developers who to use APIs and to protect some parts you would like to change in the future. This is most important if you want to decouple applications for an independent release cycle. If you are delivering software components using the Add On Assembly Kit the control of dependencies to guarantee the installability of custom made SCs. Reuse of Development Objects The most important aspect of package concept is to keep control on reuse.

I think there is a simple advice: If you use the data model of an SAP standard application, you should exactly the data elements of the application. But misusing them will bring you into trouble. In most cases short texts and documentation is not correct. The definition of own data elements will allow you to define proper texts and documentation.

Another consequence of misuse of data elements is that your software is not merger ready with SAP standard tools like Landscape Transformation: Basic Operations. My advice is simple: Use SAP domains only if you have a good reason. Merger readiness of an ABAP application is such a reason. Therefore you should create a new data element to have be able to define short texts, F1-help and search-helps.

If you are using domains like CHARxyz please check whether they are exposed in package interfaces. Alert Moderator. Alerting is not available for unauthorized users. Assigned Tags. Similar Blog Posts. Related Questions. You must be Logged on to comment or reply to a post.

Peter Langner. Hi Tobias, thank you for that great blog. Like 0 Share. Right click and copy the link to share this comment. Tobias Trapp Blog Post Author. Hi Peter, glad you liked the blog. Krishnendu Laha. Brilliant idea, looking forward for future blogs.. Former Member. There are some very cool security advantages as well. Hi Julius, you are absolutely right: when you use package checks SAP developers are forced to use proper APIs containing autority checks - I think I already mentioned it.

Cheers, Tobias. Peter Inotai. Hi Tobias, Nice topic. Keep blogging, Peter. Best Regards, Tobias. I believe there is only very little number of customers using this tool. In NW 7. Do you have any info about Package hierarchy tab in NW 7.

Thanks, Peter. I'll blog about the differences between NW 7. Kumud Singh. Hello, I read twice to get into the feeling of it. Development from Scratch Regards, Kumud. This is an important and timely topic for many projects. Paul Hardy. Cheersy Cheers Paul. Hi Paul, my recommendation is that you try to copy the Java programming model. Does it answer your question? Cheers, Tobias P. Link Text. Open link in a new tab. No search term specified. Showing recent items. Note: The consistency of data when you back up more than one database is the responsibility of the user.

You can create a backup copy of your database so that you can recover the database if errors occur. For more information, see your database-specific documentation.

To ensure that the online file system backup is consistent, the SAP System must be up and running and no deploy operations must be performed during the process. After the online backup of the system has finished, revert the property to the default value OFF.

You must make sure that no deploy operations have been started on the system before the property is set. If you want to automate the process, you can use the command line tool opm. Install a new AS Java system using the software provisioning manager, or restore the file system from the latest offline backups that you have created.

For more information, see SAP Note Run the bootstrap process. For example, you can: restore the initial state of the system if an installation or upgrade fails restore the AS Java installation in case of operating system or file system problems restore the SAP system data if the database crashes, and so on.

You can apply two backup strategies: Offline backup- this strategy enables you to create a full and reliable backup of your system, so that the system can be restored in case of a hard disk crash or operating system problems. Recommendation We recommend that you perform regular offline and online backups of your system and system components.