Applies to:
Product Release: V7 (Enterprise)Version: 7.5.3.6 [16186] Life Sci
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3
This document was previously published as Siebel SR 38-1532416087.
Symptoms
SBL-DAT-00180Hello,
We are implementing the Siebel Sample funcionality in our environment and we have
some doubts about it. First of all we are using EIM to upload all the information, rigth now we
already can upload the information for lots, inventory and sent samples. Our problem is the
Submit button in the My Sent Samples view, Is it possible to upload information by EIM to avoid
this button??
Is it possible to submit(Clicking the button) a group of records in this view?
or only it's possible one by one.
I checked the SR#38-1100925388 and there is a code to invoke
the method "WrappedSubmit". Can I use it to invoke the method for records uploaded by
EIM?
Thanks in advance
Solution
Message 1
For the benefit of other users, the customer is asking how to submit the Sent Samples in Siebel life science application when the Samples are imported e.g. by EIM.Currently (till Siebel version 7.8), users must use the Submit button in the Samples > My Sent Samples view to submit one sample at a time.
Tests are conducted with scripting similar to the segment in SR38-1100925388, and it does not work as expected.
A new enhancement request is logged to address this need: 12-PS601J - Need feature to submit all Sent Samples and their lines imported by EIM.
Applies to:
Siebel Universal Customer Master - Version: 7.8.2 [19213]IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: IBM DB2 8.2
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-3098871061.
***Checked for relevance on 12-NOV-2010***
Symptoms
Customer loaded Contact, Address, and FINCORP Account data to Source Data and History (SDH) tables using EIM process and confirmed the UCM type was set to Queued-Insert in UCM application 7.8.2. When moving the SDH records to base tables using UCM Contact Batch Data Management Workflow (BDM workflow), the following error was reported:PrcExec BatchErr 1 0 2006-07-21 09:34:56 Siebel Error Symbol '2: Unknown'. Siebel Error Message '2: System preference '<?>' is not defined.(SBL-DAT-00191)'
Cause
It was found the customer created below system preferences and set corresponding values for UCM:
- Enable CDM Cleanse: Contact, FALSE
- Enable CDM EM: Contact, FALSE
- Enable CDM Match: Contact, TRUE
- Enable Survivorship Engine, TRUE
They, however, did not create the following required system preferences and values in their UCM application:
- Unique Id: Contact, Party UId
That was why above error was reported when running UCM BDM workflow. For all available system preferences for UCM operation, please refer Siebel Bookshelf, Siebel Master Data Applications Reference for Industry Applications > Administering Siebel Master Data Applications > About System Preferences for Siebel UCM.
Solution
Please create system preferences- UID Generation Service, "FINS Teller Converter Extensions, ""GenerateID"", ""IDType|GUID"""
- Unique Id: Contact, Party UId
Once this was done the original error was not observed anymore but Contact, Address, and FINCORP Account records were inserted to base tables as expected but the UCM type code did not get updated to Source-Inserted.
To narrow down any possible reason, a WfProcBatchMgr component log was analyzed and below error was found:
ObjMgrLog Error 1 0 2006-07-24 17:22:54 (adptutils.cpp (1090)) SBL-EAI-04397: No user key can be used for the Integration Component instance 'FINCORP Account'.
ObjMgrDBConnLog EndTransaction 4 0 2006-07-24 17:22:54 EndTransaction (ABORT) was called on DB connection 11de5048
Thus, UCMContactSourceDataAndHistory Integration Object (IO) was reviewed and it was turned out that the FINCORP Account Integration Component (IC) was added to the IO but no user key was defined for the IC. Based on this, user keys were defined for the FINCORP Account IC and then the UCM type code got updated as expected upon completing the UCM BDM workflow.
Please note you can refer the user keys for FINCORP Account IC under CIFContactInsert IO when adding new user keys for FINCORP Account IC under UCMContactSourceDataAndHistory IO.
Applies to:
Product Release: V7 (Enterprise)Version: 7.5.2.7 [15058] Cons Sec
Database: Microsoft SQL Server 2000 SP4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1
This document was previously published as Siebel SR 38-3360319221.
Symptoms
Dear Support,We are getting an error while starting the mobile clients. We get the following error message:
"System preference '<?>' is not defined.(SBL-DAT-00191)".
This is due to the fact that we have a runtime event that gets executed when the user logs into the application. The runtime event will get a System Preference value and assign it to a profile attribute. That System Preference is not located in the local db and when the runtime event gets executed, the System Preference is not found, we get this error message.
The System Preference we have got is as follows:
"CompanyStckMgmt_<Organization Id>" (Company was prefixed since we have sinc ein the docking object for S_SYS_PREF that only certain value sgets routed to the local db)
The runtime event is as follows:
SystemPreference("CompanyStckMgmt_" + GetProfileAttr('Organization id')).
What we would like to know is in the evntuality that the system preference does not exist, what does the function "SystemPreference" returns? Do we have a proper way of catching it in the runtime event to prevent the mobile clients from getting this error message?
Solution
Message 1
For the benefit of other users,The behavior was reproduced with the steps of the customer. As system preference we defined a value which does not exist.
Function SystemPreference() generates error:
"System preference '<?>' is not defined.(SBL-DAT-00191)".
The error comes from within the function SystemPreference() and there is no possibility to catch this error and handle it by yourself.
There are a few workarounds:
1) You take care that all system preferences exist and return a value
2) You change the method. Instead of SystemPreference() you would use a method like BCHasRow in combination with IfNull or IIF, which checks BC "System Preferences" and returns the value or a null string.
You can also do this by personalization method InvokeMethod and handle the complete processing in your own BS. See also "Technical Note 654: How To Access System Preference Values Via a Script".
We created enhancement request #12-1JMZ7HX in order to change the behavior of this function and return with a well defined value in case of an error.
Siebel Technical Support
Keywords: runtime event, personalization, systempreference, system preferences, error
Applies to:
Siebel Universal Customer Masterz*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.1.1 [19310] UCM
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1
This document was previously published as Siebel SR 38-3028852622.
***Checked for relevance on 12-NOV-2010***
Symptoms
the following error was reported reported when attempting to simulate a UCM Workflow via the Simulator :-
Error invoking service 'UCM Converter', method 'SiebelMsgPropSetToXMLHierPropSet' at step 'SM to XMLHier Converter'.(SBL-BPR-00162)
--
The method 'SiebelMsgPropSetToXMLHierPropSet' is not supported on Business Service 'UCM Converter'.(SBL-DAT-00323)
Cause
The reason for this error was the UCM 7.8.2 install (on top of Siebel 7.8.2) only updates the Siebel Server, and does not install UCM dlls on the Siebel client.Solution
The dlls are:
ssfaixmlsv.dll
ssfautilsv.dll
sscaucmsdhsv.dll
sscaucmsurvsv.dll
ssfaelmsv.dll
ssfaacordixmlsv.dll
ssfaiaaixmlsv.dll
ssfafxixmlsv.dll
sscaucmbc.dll
sscaucmdmsv.dll
fasvccif.dll
After this, a later error was reported :
Error invoking service 'UCM Batch Manager', method 'CalculateCDMOptions' at step 'Calculate CDM Options'.(SBL-BPR-00162)
--
System preference 'Enable CDM Cleanse: Contact' is not defined.(SBL-DAT-00191)
This was resolved by adding the required UCM System Preferences listed in reference
Siebel Master Data Applications Reference for Industry Applications > Administering Siebel Master Data Applications > About System Preferences for Siebel UCM
Change request 12-1E801CP has been logged to request that UCM System Preferences are created during install (or method provided to import them).
No comments:
Post a Comment