Siebel Connector for SAP R/3 > Customizing Integrations > Making Necessary Siebel Application and SAP R/3 Customizations >

Customization in the Siebel Application

Depending upon your analysis, some Siebel configuration may be necessary to build the desired interface. Customization may be necessary at several levels in the Siebel architecture as shown in Figure 19. In the Siebel User Interface Objects Layer you can customize screens, views, applets, controls, and navigation. In the Siebel Business Objects Layer you can customize business objects and business components. In the Siebel Data Objects Layer you can customize base tables and extension tables.

Figure 19. Siebel Architecture Diagram

The Siebel application allows customization in each of these layers. Major configuration tasks are performed through Siebel Tools. An overview of the changes you can make is provided here, but more detailed information is provided in the Using Siebel Tools guide.

Although the Siebel database model is designed to accommodate most industry specific requirements, you may find that you need to make modifications. You can add both base and extension tables to the Siebel database as well as add new fields. Changes in the Siebel data model, such as the Siebel Data Objects Layer, then require modifications to the business objects and user interface objects layers.

Changes to the business objects layer may include the addition of columns to business components. These fields then need to be exposed to the user interface in the relevant code applets. Depending upon the changes, new views or screens may need to be added to support new functionality.

Because integration objects are based upon business objects and business components, changes in any existing business objects for which there are corresponding integration objects requires the update of those integration objects. Update integration objects through the synchronize function in Siebel Tools. Take care as the integration objects may have been modified after they were originally captured. You may need to reapply modifications manually after synchronizing. For comparison, you should save a copy of the original integration object prior to synchronization.

Standard integrations use LOV (List of Values) definitions for language independent values instead of hard-coded strings in eScript maps. Create and use LOVs wherever possible in scripts instead of hard-coded strings. Maintain LOVs in Application Administration > List Of Values.