Error Processing Your Request. Please Consult A Siebel Administrator
workflow was failing validation and giving a very odd message given below: Validation failed for the workflow process ‘Customer Inquiry WF: 1' for the branch ‘Y3' The ‘WF Branch Criteria Value' - field such as LO_.. or HI_.. for the respective data type is null or empty. Since this was around a 30 step workflow in which no proper naming convention was followed (at least 5 connectors were named Y). The error message also didn’t mention any step name to make things easier. As the error message mentioned ‘WF Branch Criteria Value’ I assumed it must be some condition in a decision step. Looking at decision steps didn’t help either and everything seemed in order. So, before moving to the last resort of either deleting all the decision steps and recreating them I decided to do some digging. So, to find exact step name I went behind the scenes created the following query to get a simplified data for the workflow. select w.name "Workflow Name", s.name "Step Name", s.type_cd "Step Type", b.name "Branch Name", c.name "Condition Name", vl.name "Condition Value Name" from siebel.S_WFR_STP s, siebel.S_WFR_PROC w, siebel.S_WFR_STP_BRNCH b, siebel.S_WFR_COND_CRIT c, siebel.S_WFR_COND_VAL vl where w.row_id = ‘1-22M8QD' and s.process_id = w.row_id and b.step_id = s.row_id and c.branch_id = b.row_id and vl.cond_crit_id = c.row_id This gave me the culprit step and the connector name and only after deleting and recreating the particular connector the error message went away. I stil couldn't figure the actual root cause of the error and I guess probably some thing got messed up during deployment. As this was an unusual thing that I encountered, I figured this might help someone else also. Anybody else faced something like this ? Comments welcome! Share:PrintEmailTweetSQL, Workflows SQL, workflow← Top 10 things you need to know a
pretty common error that we faced. The error to be precise was An error has occurred creating business component %1 used by business object %2. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222)” Reason: This error occurs when you miss a step while configuring your application. That precise step is to add BC to the BO. Steps from birds eye view to configure a view are as following Create a Business Object http://siebelunleashed.com/behind-the-scenes-workflow-debugging/ Create a Business Component Add Business Component to Business Object Assign Primary Business Component to Business Object Create an Applet based on the Business Component you created Create a View based on Business Object you created and Assign Applets to it. Add that view to Screen Add that Screen to Application Open your Application http://siebelunleashed.com/an-error-has-occurred-creating-business-component-sbl-dat-00222/ and Add that view Assign Responsibilities to that view If you don’t add you BC to the BO and try to use your application you will face the above mentioned error. This can be made sure with the help of scripting Write the following script and try to execute var BO = TheApplication().GetBusObject(“BO Name”); var BC = BO.GetBusComp(“BC Name”); BC.ExecuteQuery(); If your BC is missing from BO you will face the above mentioned error. Solution: Add the BC which is giving error to the BO you view is based on and it will solve the Problem. Share:PrintEmailTweetProblem Solutions Problem Solutions← esd bhd and ctd–trio that makes Email Marketing server work.How To Generate XSD and DTD Files in Siebel. → This Post has been viewed : 37,096 Times Visitors to this post, also read:Elastic List Applets @ IP 2015An error has occurred creating business component…esd bhd and ctd–trio that makes Email Marketing server…ContributeOpen UI - IP 2014 finally - component
issues and workarounds for Oracle Business Intelligence Publisher releases 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2. For installation information, consult the Oracle Business Intelligence Publisher Installation Guide, which is available http://docs.oracle.com/cd/E12844_01/doc/bip.1013/e12691/T485810T485813.htm on the Oracle Business Intelligence Publisher install media and on the Oracle Business Intelligence Publisher Web site: http://www.oracle.com/technology/documentation/bi_pub.html These release notes are organized into the following sections: How to Use These Release Notes Upgrading to this Release Issues and Workarounds General Issues Security Issues Delivery Manager Issues Scheduler Issues RTF Template Issues PDF Template Issues error processing BI Publisher Desktop Tools Issues Flash Template Issues Data Template Issues Report Building Issues Documentation Issues Resolved Issues New Features in This Release How to Use These Release Notes These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle error processing your Business Intelligence Publisher Web site: http://www.oracle.com/technology/documentation/bi_pub.html Upgrading to this Release Overview Currently the Oracle BI Publisher installer does not include an upgrade option. Follow these steps to upgrade BI Publisher versions 10.1.3.2 and later to version 10.1.3.4.2. This procedure applies to BI Publisher installations originally installed using the BI Publisher Installer or originally installed by following the manual install instructions in the Oracle Business Intelligence Publisher Installation Guide. The upgrade procedure described in this section consists of the following general steps: Back up your existing install. Manually deploy the xmlpserver.ear or xmlpserver.war to your application server. Copy the specified files from the install media to your XMLP repository folders. Prepare Your Existing Installation: Prepare your existing installation by backing up files and noting your existing scheduler configuration. Back up all the directories under the BI Publisher repository. The BI Publisher repository is the directory named "XMLP" that contains the following subdirectories: Admin Demofiles Reports Tools Users If you do not know the location of the