Siebel CRM does not map these data types to the physical data types that it defines for the database. The data type of the field is typically more specific than the data type of the underlying column. Just as the data type of the underlying table column restricts the set of field data types that work correctly, the data type of a business component field restricts the set of format options that Siebel CRM can use in the control or list column that reference the field.
It is recommended that you do not map a field to a table column that is not the same type as the field. Overriding the default format in the Siebel repository but might cause confusion. The Type property of a multi-value field is empty because Siebel CRM defines the data type of the field in the child business component that enters data in the multi-value field. A calculated field is a type of business component field that gets values from other fields that reside in the same business component or from the parent business component in an active link where the current business component is the child business component.
The Calculated property of a calculated field contains a check mark and the Calculated Value property contains a value that is not empty. The Calculated Value property contains an expression that Siebel CRM builds from field names, predefined functions, and string, numeric, and logical operators. For example, the Calculated Value property of the Full Name field that resides in the Contact business component includes the following value:. If Siebel CRM modifies the calculated value of a field, then it does not refresh this calculated field, by default.
It only refreshes a calculated field after it commits the record. To refresh the field immediately after Siebel CRM modifies the value in this field, you can make sure the Immediate Post Changes property of this field contains a check mark. A calculated field cannot reference itself in the Calculated Value property. For example, you cannot use Last Name in a calculation expression for the Last Name field. If the Cache Data property of the business component contains a check mark, then Siebel CRM does not support a query on a calculated field in this business component.
A situation might occur where you must create a field that provides sequential numbering for the parent business component. For example, you might need to number line items in an order or products in an opportunity. The sequence field behaves as follows:. When Siebel CRM creates a new record, the initial sequence number is the maximum sequence number of the existing child records, incremented by one.
Siebel CRM does not renumber records to resolve the gap that results when it deletes a record. The user must do this work manually.
The following figure describes how Siebel CRM creates a sequence field. Siebel CRM uses the following objects to create a sequence field:. Parent business component. The business component that contains the parent records in the parent-child relationship where the child records are numbered.
For example, the Opportunity business component is the parent in the parent-child relationship with Opportunity Product. Numbered business component. The business component that contains the child records in the parent-child relationship.
For example, the Opportunity Product business component is the detail in the parent-child relationship with Opportunity. The numbered business component includes the following child object definitions:. Sequence value field. Line Number and Order are examples of a sequence value field. Business component user property. The Sequence Field business component user property must be present, with the Value property set to the name of the sequence value field.
Sequence business component. This business component is named xx. Foreign key field. A foreign key field that references a foreign key column that resides in the detail table. The foreign key column references the primary key of the base table that the parent business component references. You can use it to create the link that resides between the parent business component and the sequence business component.
Detail table. The base table that the numbered business component and the sequence business component references. Main link. The parent-child relationship that exists between the parent business component and the numbered business component. This link is typically predefined, such as Opportunity or Opportunity Product. Sequence link.
The parent-child relationship that exists between the parent business component and the sequence business component. You must typically add this link, except when a predefined Siebel application includes the sequence configuration. Opportunity and Opportunity Product.
Line Number Sequence are examples of a link to a sequence business component. You can view an example configuration of a sequence field in a predefined Siebel application in Siebel Tools.
Order Sequence sequence business component. Table Sample table. Default table is the business component table. This property is required unless it is a calculated field. User-defined name for the field. It must be unique within the business component. This property is required. Siebel Tools gets the text length from the database and, for columns with a physical type of varchar, sets the Text Length property for a business component field to this value.
For number, date, and datetime fields, Siebel Tools does not put a value in Text Length. Exceptions are fields mapped to foreign key columns these columns have names that end in ID and have a physical type of varchar and length of If you edit the value in the Text Length property, it is ignored unless the value in a picklist is longer than what is specified on the business component field.
In this case you get an error. The field data type. This topic describes how Siebel CRM defines read-only behavior for a business component.
It includes the following information:. You can turn on or turn off the read-only status of a business component or business component field while Siebel CRM is running, depending on the value that the field of the current record contains. The following table describes the business component user properties that you can use to define read-only behavior. For more information about user properties, see Siebel Developer's Reference. If TRUE, then the current record is read-only. If TRUE, then the target field is read-only.
The format for FieldName works if FieldName is not a join field. If FieldName is a join field to another table, then this format does not update the field that uses this format in the Pre Default Value property of the field. If TRUE, then the target business component is read-only. This configuration is similar to the Parent Read Only Field business component user property, except the name of the user property rather than the value specifies the parent business component.
It prevents the user from updating or deleting the record but it does not prevent the user from adding a new record to the business component. Contains the name of a field that resides in the parent business component of this business component user property.
Assume Siebel CRM must prevent the user from updating an inactive account. To configure dynamic read-only behavior for the Account business component, you can add a business component user property to the Account business component.
This example business component user property contains the following properties:. The Field Read Only Field user property is similar to the BC Read Only Field user property because it tests the field that you define in the Value property, and it enforces a read-only restriction if the value of the test field for the current record is TRUE. Unlike the BC Read Only Field user property, the Field Read Only Field user property restricts only one field in the business component record rather than restricting all fields in the entire business component record.
Contains the name of the test field. You must create one Field Read Only Field user property for each field that you must make conditionally read-only. The Parent Read Only Field user property, like the BC Read Only Field user property, places a read-only restriction on an entire business component rather than on a single field. In the other user properties, Siebel CRM places the read-only restriction on the business component that contains the test field, or on another field in the same business component.
Restrict the child records that Siebel CRM includes in a multi-value group. Restrict the child records that Siebel CRM includes in a master-detail view. You must make sure that Siebel CRM does not use the restricted business component in the context of some other business object. For example, Account. Inactive Account. You add the user property as a child of the business component that Siebel CRM restricts according to a condition.
The business component that contains the test field must be a parent of the restricted business component through a link or through a series of link relationships. If it is not TRUE, then the dynamic read-only functionality does not work. You then add a user property to the Business Address business component with the following values:.
This configuration causes the Account Address Mvg Applet to be read-only if the account record is for a competitor. The behavior of the Parent Read Only Field: business component name user property is similar to the behavior of the Parent Read Only Field user property.
The name rather than the value specifies the parent business component. Do not use a business component user property with an applet that resides in a view if the Admin Mode Flag property of this view contains a check mark. Turns off all insert and update restrictions for the business components that the view uses, including the restrictions that the business component user property defines.
You can include a check mark in the Admin Mode Flag property only if the view is part of a screen that contains only administration views. You can create a list view where the Admin Mode Flag property contains a check mark if this list view drills down to a detail view that Siebel CRM does not mark as an administration view. This configuration allows you to share a detail view with a list view that is not an administration view.
A system field is a business component field that represents the data that Siebel CRM gets from a system column. All business components in Siebel CRM include system fields. You are not required to do any special configuration to display or manipulate a system field. You do not need to define it as a business component field. For example, you can reference a system field in the Field property of a control, list column, or in another object.
You must not modify a system field. For example, by renaming it. Siebel CRM does not support modifying a system field. For more information, see System Columns of a Siebel Table , and. Displaying a System Field in an Applet. For example, in the Source Field property of a link where an empty value indicates the Id field. You must not explicitly create a system field for a business component. If you create a business component field that references a system column, then Siebel CRM attempts to write a value to the column twice in the insert statement, which causes a duplicate column SQL error.
The following table describes the relationship that exists between a system field and a system column. Each field is predefined. You do not explicitly define it. You can configure Siebel CRM to reference a system field in the Field property of a control, list column, or other object, even though Siebel Tools does not display the field in the Business Components list.
Stores the date of the most recent update that Siebel CRM performed on the row. In some situations, Siebel CRM updates this field even though the user does not actively update the record. For example, if Siebel CRM configures a multi-value link with a primary join. Stores the date of the most recent update that Siebel CRM performed on the row in the Siebel database. The system field name varies. If you define the name of a business component field, then use the following guidelines:.
Do not use parentheses in a field name. Apply the following requirements if each field is the only such field in the business component:. Reusing Predefined Objects. Guidelines for Reusing a Predefined Object. Guidelines for Creating a Join. A join creates a relationship between a business component and a table that is not the base table of the business component.
For more information, see Join. To observe how a join works, in the Siebel client, you can navigate to the Service Request screen, and then examine the Service Request List Applet.
This applet includes the Account field. A join brings the Account field to the Service Request business component, and then the Service Request List Applet displays the data in the Siebel client. The following figure describes how a foreign key column that resides in the detail table defines the parent-child relationship. Multiple rows in the detail table include the same foreign key value that references back to the same row in the parent table. After you create a join, you can define more fields in the business component that reference columns in the joined table.
You can use a joined field as the Source Field on the join specification. Sudhakar Dec 14th, Sukesh Mar 19th, Give your answer: If you think the above answer is not correct, Please select a reason and add your answer below.
Open Questions Answered. Latest News. It looks like you are using an AD Blocker! Disable Ad Blocker Learn More. Login GeekInterview Login. How to configure a Siebel Join? You create a join in two steps- 1.
There can be one or more than one specifications for a single join. Join constraint is a simple text value in most cases.
However, specific calculation formulae are also allowed. For e. An outer join would look like this Interesting Points to Note Joins may have one or more join specification and join constraint.
There is no scientific basis for the assumption. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy.
Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox.
Newsletter Topics Select minimum 1 topic. Enterprise Software.
0コメント