Object documentationNamespaces for BW Objects Locate this document in the navigation structure

 

The following Namespaces are generally available for BW objects:

SAP-delivery (Business Content) namespace:

  • Objects beginning with 0

  • Generated objects in the DDIC beginning with /BI0/

    Example Example

    InfoCube 0SALES, fact table /BI0/FSALES

    End of the example.

Customer namespace:

  • Objects beginning with A-Z

  • Generated objects in the DDIC beginning with /BIC/

    Example Example

    InfoCube SALES, fact table /BIC/FSALES

    End of the example.

Partner-specific namespace and customer-specific namespace:

  • Object begins with /XYZ/ (example)

Special SAP namespaces for generated objects:

  • The prefixes 1, 2, 3, 4, 6, 7, 8 are required in BW for DataSources and InfoSources in special SAP applications.

  • The prefix 9A is required for the SAP APO application.

 

When you create your own objects, therefore, give them technical names that start with a letter. The maximum permitted length for a name varies from object to object. Typically, 9 to 11 letters can be used.

You can transfer from the Business Content version any Business Content objects that start with 0 and modify them to meet your requirements. If you change an InfoObject in the SAP namespace, your modified InfoObject is not overwritten immediately when you install a new release, and your changes remain in place for the time being.

You also have the option of enhancing the SAP Business Content without a modification. There is a partner namespace and a customer namespace available for you to do this. You have to request these namespaces specially. Once you have prepared the partner namespace and the customer namespace (for example, /XYZ/) you are able to create BW objects that start with the prefix /XYZ/. You use a forward slash "/" to avoid overlaps with SAP Business Content and customer-specific objects. For more information, see Using the Namespace for Developing BW Objects.

See also:

InfoObject Naming Conventions

Generating the Master Data Export DataSource

Naming Conventions for Background Jobs