Divisibility

Particularly for central application objects with a lot of tables and fields, it is easier not to have to maintain the whole object each time, but only parts of the data (object parts) depending on the business environment. The divisibility function within the BDT can be used for this.

The BDT supports two types of divisibility:

Each instance can be created inexactly oneobject part

The information regarding which object parts an instance is created in is an attribute of the primary table. An example of this is a bank account which can only be created in exactly one account type (for example, current account, clearing account etc.).

Each instance can be createdin severalobject parts

The information regarding which object parts an instance is created in is stored in a separate table. The table key is made up of the object’s primary key and the object part. An example of this is a business partner who can appear in several roles (for example, ordering party, payer, account holder etc.).

In this form of divisibility, a further distinction can be made between whether it is permitted to maintain the instance in several object parts within a maintenance dialog. If it is permitted, object part grouping can be used to combine several parts for maintenance.

Details on Application Objects

The form of divisibility is determined here. Terms such as object part and object part grouping can be replaced by terms from the application object’s language environment. In Business Partner these terms have been replaced by "BP role" and "BP role grouping".

Menu path:  General control Application object

Naming convention: <Application><n>

Object parts should always have 6 places. It should start with the application ID followed by a set of numbers.

Object parts

For each application object, you can define any number of object parts. To define an object part, follow the steps below:

Along with the name and the title, define the screen sequence and differentiation type. You can also decide here whether or not a screen selection is to be shown on the initial screen.

Naming convention: <Application><n>

Object parts should always have 6 places. It should start with the application ID followed by a set of numbers.

This allocation will determine which applications

Only some attributes are relevant for each object part. This assignment will enable you to determine which attributes are relevant for an object part. The BDT automatically hides the remaining attributes in the dialog.

Menu path:  Control <Object > <Object parts>

Note: In many cases application transactions (see Application Transactions ) can be used for calling up the maintenance dialog. Otherwise you can call up the dialog using the BDT function module BUS_CONTROL_MAIN.

Object Part Groupings

Object parts can be combined using object part groupings. To define an object part grouping, use the following steps:

Apart from the name and the title, define only the screen sequence for the dialog here.

Naming convention: <Application><n>

Object part groupings should always have 6 places. It should start with the application ID followed by a set of numbers.

This assignment will enable you to determine which object parts make up the grouping. During the dialog for a grouping, the BDT will show only those views which are assigned to at least one relevant object part.

Menu path:  Control <Object > <Object part grouping>