June 20, 2013 – Siebel Incremental Repository Merge [ID 1548094.1]

A Webcast is planned on Incremental Repository Merge (IRM). IRM will be the way forward. Even though that the initial release of IRM comes with its flaws – attending this Webcast can take away most of your questions. Also the use of IRM for customer developments (e.g. parallel development) will be discussed. Enjoy!


ADVISOR WEBCAST: Siebel Incremental Repository Merge

PRODUCT FAMILY: Siebel CRM Siebel Tools & Scripting – SBL

June 20, 2013 at 11 am ET, 10 am CT, 9 am MT, 8 am PT, 4:00 pm London

This will be one-hour session for technical and functional users who are well involved in Siebel Development. Session will cover easy installation of Innovation Packs or ACR, about Siebel Delta files and Tagging which is used for differentiating the work done by different developers on Server Database. This will also cover on why to go for IRM, the pre-requisities, troubleshooting when running IRM. Customers attending this session will get to know the new feature availability in and This will let them know how the time consuming ACRs can be applied in a single go without manual intervention. Currently there is no External Document created on the process of IRM. The only information provided is Bookshelf. We will also discuss on the common issues faces when Running on IRM based on existing SRs.


  • New Features of and
  • Why and What is IRM
  • Pre Requisites of IRM
  • Demo of IRM
  • Development Tagging – New Feature
  • Common Issues occurring with IRM – troubleshooting SQL Errors

A short, live demonstration (only if applicable) and question and answer period will be included. Oracle Advisor Webcasts are dedicated to building your awareness around our products and services. This session does not replace offerings from Oracle Global Support Services.

Current Schedule and Archived Downloads can be found in Note 740966.1

WebEx Conference Details

Thursday, June 20, 2013 9:00 am, Mountain Daylight Time (Denver, GMT-06:00)
Thursday, June 20, 2013 4:00 pm, GMT Summer Time (London, GMT+01:00)
Thursday, June 20, 2013 8:00 am, Pacific Daylight Time (San Francisco, GMT-07:00)
Thursday, June 20, 2013 11:00 am, Eastern Daylight Time (New York, GMT-04:00)

Event number: 594 859 162

To register for this meeting

1. Event address for attendees: https://oracleaw.webex.com/oracleaw/onstage/g.php?d=594859162&t=a
2. Register for the meeting.

Once the host approves your request, you will receive a confirmation email with instructions for joining the meeting.

InterCall Audio Instructions

A list of Toll-Free Numbers can be found below.

  • Participant US/Canada Dial-in #:888-259-4812
  • International Toll-Free Numbers
  • Alternate International Dial-In #:706-679-4880
  • Conference ID: AdvisorPG

BI Apps – Bye Informatice, Bye DAC – Hello ODI

BI Apps – Bye Informatice, Bye DAC – Hello ODI

Read this good blog post from Mark Rittman with regards to sunsetting the long OEM relationship between Oracle and Informatica. Oracle Data Integrator (ODI) and the new BI Apps Configuration Manager plus the Fusion Functional Setup Manager will replace the DAC. This drastic move which can be well understand from an Oracle’s point of view will have potentially large consequences. There is no such thing a migration Information Workflows toward ODI Load Plans. To be continued!

Siebel Profile Attribute Management utility

Siebel Profile Attribute Management

Working with profile attributes in Siebel can be a nightmare. Especially if used in abundance and when not documented well enough or by giving troublesome names…

Nevertheless they can be very useful.

Siebel is lacking a utility to manage (set / reset / view) profile attributes.

There are scenario’s where you want to check the value of a known profile attribute – or deliberately want to change it for unit testing purposes.

In the past I created a small (Siebel) utility for this same purpose. It enables you to just that. Essentially it’s a VBC with a small portion of eScript. The VBC can use a so-called watch-list of profile attributes retrieved as LOV values. This enables you to persistently define a number of profile attributes for which you want to quickly see the values. The VBC displays the profile attributes in a simple list applet. You can add new profile attributes and define (if you want) a value for it. If the profile attribute exists – the value will be shown immediately.

A small utility with great use from time to time.

Here you will find:

Siebel / – BI Publisher integration improvements & webinar



There are a number of key improvements with regards to Siebel BI Publisher integration. Most improvements have made it in and couple followed in

Key capabilities:
– UI notifications to shows report generation has been completed (this is available for both Open UI as well as the traditional HI client);
– Option to open a report directly from the Notification list area in the toolbar;
– Intuitive buttons for tablet usability;
– Improved usability using collapsible menus and no popus;
– Return context to the application immediately after report execution;
– Less button clicks to execute reports and open the report output.

Finally – the certification with BI Publisher 11g has become available. You need to be on the BI Publisher patch. BI Publisher 11g works with all Siebel releases – since the integration has been simplied between 10g and 11g.

There is a public Webinar with regards to all the good improvements in / ( / TOI: Siebel Reports Functional Overview – Browser script security feature BusCompAccessLevel added

Backported from Siebel (already present), per Siebel a new security feature “BusCompLevelAccess” got introduced. This is affecting many customers, because they have not been proactively informed and the default behavior is restricting existing transactional operations through Browser Scripts against business components.

The BusCompAccessLevel feature is documented in Bookshelf.

Siebel CRM provides object interface methods that can be used on Siebel business components to make their data and functions available to custom code, for example, to code that is written using Siebel scripting interfaces such as Browser Script. This topic describes how to control the operations that can be performed on business components from the Siebel scripting interfaces. The following parameters allow you to configure the operations that can be performed on business components from scripting interfaces:

  • The Siebel Server parameter, BusCompAccessLevel, can be specified for all business components to configure the operations that can be performed directly on a business component from scripting interfaces. Values are “None”, “Readonly” (=default) and “All”.
  • The business component user property, DirectUIAccess, allows you to enable or disable operations on a specific business component from the scripting interfaces. The value of the DirectUIAccess property specified for a business component overrides any value set for business components using the BusCompAccessLevel server parameter. Values are “None”, “Readonly” (=default) and “LimitedWrite”, “All”.
  • If the value “LimitedWrite” is used for the “DirectUIAccess” Business component user property, an additional  DirectUIAccessFieldList defines which fields are updateable by Browser script.


Siebel Open UI – Mobile Disconnected

Oracle will be releasing later this year its initial release of Siebel Open UI for Disconnected Mobile use. Something particular industries (consumer goods, life sciences, enterprises with field service operations) are looking forward to. Disconnected Mobile will be either released as a QF on top of or included in (the IP2013). This will require also the uptake of the respective ACR. ACRs are from onwards implemented using IRM (Incremental Repository Merge) – see separate post. Disconnected Mobile will leverage a technological model for bi-directional synchronization which will be conceptually similar to the the handheld synchronization technology patented by Oracle. It will use data extraction filters to limit data being available on the disconnected client. Disconnected Mobile will be based on HTLM5 browser capabilities, more specific the Web SQL API. Browsers will need to support the Web SQL API standard.