Browse Prior Art Database

Original Publication Date: 2005-Aug-31
Included in the Prior Art Database: 2005-Aug-31
Document File: 7 page(s) / 65K

Publishing Venue



A method, a program product to set primary ID fields with valid child table rowid for a large record set for the given Business Component entity and Tables within Siebel. Siebel does not provide any method to set the Primary id fields without creating the audit record by updating the audit columns in tables. This method receives business Component and table name as input parameters and gathers the relationship between primary ID field and child entity from Siebel application repository. Based on the metadata information the update SQL statement is dynamically prepared then identify the appropriate child record rowId and update the Primary Id columns within the base table. If no valid or appropriate record is found the Primary Id field has gets updated with "No Match Row ID".

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 20% of the total text.

Page 1 of 7



    This article relates to a method which sets primary ID field with valid record from child table for a large record set in Siebel CRM Application. A Primary ID field in Siebel application is a reference to a designated primary child record where relationship between entities is one-to-many or many-to-many. For example one account has many contacts and out of many contacts one contact is designated as primary contact. There are many such primary Id fields that exist within Siebel application for a single table. In Siebel if no valid child record exist then the primary ID field value is set to "No Match Row ID" instead of NULL, to improve the performance of GUI response time. If in case due to any reason if these fields are left NULL and any user happens to steps on the records in GUI, application automatically update these field with valid child reference. If valid record is not found then the Primary Id field is updated with "No Match Row ID". At the same time while the record is updated an audit record gets created, also updating audit columns like LAST_UPD_BY, LAST_UPD, MODIFICATION_NUM within the table with the current user information and current date and time. The above method is a Siebel inbuilt feature. Moreover Siebel also contains all the relationships within the Meta data that is called Siebel application repository, which is configurable and might be different for different implementation depending on the entity relationship defined by the business rules.


Siebel application could be integrated with many different legacy systems and there could be large amount of data that are sent through these interfaces to Siebel. Often these interface records provide NULL value to Primary Id fields as these columns are not mandatory columns required by Siebel for insert of records. When any user navigates to such records, Siebel application looks for the valid child record value and set the Primary Id field from the child table and if not found set to "No Match Row ID". This update of record creates an audit trail record and also changes the modification date, modified by user and modification number field for those records. This causes problem for audit and control people, because users are incorrectly being identified for changing the record though they just happen to view the record and not update. Siebel does not provide any method devised to such primary ID fields value in bulk. To handle this problem a requirement was raised to identify the valid primary Id field and update them from the backend without updating modification date and modified by user field and this will also prevent to create an audit record. So now when the user steps on the record just for read purpose the audit columns for the record does not get updated.

To device this methodology a generic process would need to be developed to update primary id field for...