Creating a Segment 
Use
After you create a BDoc type, you need to create segments. You use this procedure to create a segment for a BDoc type.
Prerequisites
You have created a BDoc type.
Procedure
...
1. Log on to the CRM server and choose Architecture and Technology ® Middleware ® Development ® Meta Object Modeling ® BDoc Modeler.
The CRM BDoc Modeler screen appears.
2. Right-click the required BDoc type in the tree.
A context menu appears.
3. Choose Add Segment.
The Segment Overview, Mappings, Joins, and Segment Fields tabs appear.
You can also
create a segment by using BDoc
® Create Segment.
However, the Create Segment menu option is enabled
only when the details of the BDoc type are displayed. In addition, you can
choose 
to create a segment.
4. In the Segment Overview tab, enter the following details:
|
Field name |
Description |
Req./Opt./Dep. |
User action and values |
Comment |
|
Segment name |
Indicates the name of the segment |
Req. |
Enter a name for the segment. For information on the naming convention for segments, see Namespace. |
|
|
Generated structure |
Indicates the name of the generated structure |
Dep. |
This field is read-only. |
The structure is automatically generated. |
|
Description |
Indicates the description of the segment |
Opt. |
Enter a description for the segment. |
|
|
Parent segment |
Indicates the name of the parent segment under which child segments are created |
Opt. |
Enter the name of the parent segment. |
You need to specify the name of the parent segment only if the segment you are creating is a child segment. |
|
Hierarchy level |
Indicates the level of the segment in the segment hierarchy |
Dep. |
This field is read-only. |
The root segment is assigned a level n while a child segment is assigned a level n+1. This is automatically generated. |
|
Order |
Indicates the order in which segments are created during the modeling process |
Dep. |
This field is read-only. |
This is automatically generated. |
|
Cascaded Delete |
Specifies the deletion of child segments when a parent segment is deleted |
Opt. |
Select the option. |
The child segments are deleted based on the value set for this flag at their level.
You have a root segment A and three child segments: B, C, and D. If you select this option for the root segment A and two child segments, B and D and you delete the root segment, the root segment A and child segments B and D are deleted. The child segment C is not deleted, as you have not selected this option. The root segment is deleted irrespective of the value set for this flag.
You can have multiple root segments for a BDoc type. This behavior is implemented in the BDoc layer. However, in the CDB services, this option is always enabled. Therefore, when a parent segment is deleted, all the child segments are deleted. |
|
Use map |
Specifies whether the segment field names and mapped table field names are same or different |
Opt. |
Select the option. |
If you select this option, mapped table field names used for generation assume that segment field names and mapped table field names are different. If you deselect this option, the segment field names used for generation assume that segment field names and mapped table field names are the same. |
|
Select Distinct |
Specifies the selection of distinct records |
Opt. |
Select the option. |
This is available for all the BDoc types except mBDoc types. This is applicable to the entire result set instead of specific columns. The default option is ALL, which is the opposite of DISTINCT. After you model a BDoc type to be DISTINCT, you cannot change it at runtime. If you select or deselect this option, it results in a BDoc type change. The indiscriminate use of this feature leads to poor performance. |
5. Save the BDoc type.
See also: