topic Re: Application Components vs. Namespace in Application Development and Automation Discussions

Application Components vs. Namespace

Former Member — Fri, 06 Mar 2009 09:04:46 GMT

Hi everyone.

I've recently worked on translating our some components in our namespace, and I'm now looking into how the SAP standard way of translation is. So far google gave me this document: http://www3.telus.net/public/surasa72/System_Setup.pdf which could prove to be a great source.

On page 4: http://screencast.com/t/uvOp63aeXQK the document describes a structure: Objects\Packages\Application Components.

The document describes App. Comp. like this: http://screencast.com/t/KtGnPqacA

What are the differences between Application Components and Namespaces?

Best regards

Lasse Finderup

Edited by: Lasse Finderup on Mar 6, 2009 10:10 AM

Re: Application Components vs. Namespace

uwe_schieferstein — Fri, 06 Mar 2009 10:21:41 GMT

Hello Lasse

Basically there are three namespaces available for customer:

- Y objects
- Z objects
- /mynamespace/ objects

You can register with SAP your own namespace which makes sense if you are working in a company where you do professional ABAP development for other customers.

Application components describe the structural hierarchy of the entire SAP system, e.g.

CA = Cross-Applications
FI = Financial Accounting
BC = Basis

If you assign your own packages to a specific application component then these packages will show up wherever you have a report using the application components as selection criteria.

If you have huge development projects such an assignment makes sense but I have never assigned any of my packages to a specific application component (except for eCATT scripts where this is mandatory).

Regards

Uwe

Re: Application Components vs. Namespace

Former Member — Fri, 06 Mar 2009 10:25:19 GMT

Thank you Uwe