*A reservation of a different kind – why, what and how of BPC name space* Having a reserved namespace is not new to SAP. Anyone who has worked in Netweaver BI arena for some time knows that the objects starting with 0 are delivered by SAP and are part of the business content (0ACCOUNT, 0AMOUNT etc.). So if you are developing some new objects, one should avoid starting anything with 0 and in fact, should use the customer namespace of objects starting with y and z for technical names. Enter stage right BPC for Netweaver and we have a new namespace for some objects created by BPC. In this blog, let us try to understand this namespace in some details. Here is the why, what and how of this new namespace. *Why the new namespace:* Business Planning and Consolidation version for Netweaver (BPC7NW for short) delivers almost all of the end user functionality that was available in BPC for Microsoft platform with the difference that the master data and transactional data are stored in Netweaver BI. So when the BPC user creates a dimension, a BI characteristic is created in the BI system and when he/she creates an application, BI infoproviders are created in the BI system. So these objects are system generated objects (using a service user) and not user created. At the same time, they are not ‘delivered’ objects. So they can’t be ‘z’ objects and they can’t be ‘0’ objects. Hence there was a need for having a separate namespace for such objects. The extent of the BPC namespace can not stop just at the namespace for BI objects alone. We should store the BPC related data dictionary separately; and hence there is a need for a separate namespace for the BPC dictionary namespace as well. *What is the new namespace:* Now we have /CPMB namespace for all the BPC related infoobjects that are generated by the system when a BPC user creates BPC objects using BPC front end. For example, when a BPC user creates a new appset, an infoarea is created in the /CPMB namespace. When he/she creates a new BPC dimension in that appset, a corresponding BI characteristic is created in the /CPMB namespace in the same info area. Following is a screenshot of a BPC7NW system for our familiar transaction rsa1 (Datawarehousing Workbench) and it shows the BI objects in the /CPMB namespace.