Here the [Value] is the input value for the BS input argument "InputArg". Finally the output value in the BS output argument "OutputArg" will be mapped to the Target Field.
How to set the environment variable:
Right Click on My Computer --> Properties--> Advanced -->Environment Variables--> Add and set the value of the new environment variables: SIEBEL_LOG_EVENTS = 4 and SIEBEL_FACAP_LOG_EVENTS = 5 http://www.siebeldigest.com/
To Spool the Log at Client Side for Business Rule Processor:
The BRP log level is set with the environment variable - SIEBEL_FACAP_LOG_EVENTS, The value can range between 1 & 5. It requires the Siebel Log level (SIEBEL_LOG_EVENTS) to be set greater than 1.
Situations can occur in which you need to create a field that provides sequential numbering for the parent business component. You can configure a sequence field in a detail business component by adding a business component user property called Sequence Field and creating a sequence business component with a special business component class called CSSSequence. When you delete any record, reordering can be accomplished by using “Sequence” method in BusComp Change Record event. http://www.siebeldigest.com/
The way to do this in Siebel UCM 8.0 is to use the EIM_UCM_ORG table (one record per account), filling the PAR_OU_ID field with the ROW_ID of the related parent account. This entails the need to load parent accounts before respective children, and get their ROW_IDs. One tiny possible configuration is to add an EIM Foreign Key Mapping for the field S_UCM_ORG_EXT.PAR_OU_ID. This way, it would be possible to specify the parent account using its user key values (name, location, and organization) instead of the ROW_ID.
The attached document describes this change ("How To Add an EIM Foreign Key Mapping for S_UCM_ORG_EXT.PAR_OU_ID.doc").
But take into consideration that Oracle Siebel Expert Service must be involved before applying it in a production environment, since a modification to the S_UCM_ORG_EXT.PAR_OU_ID base table column is needed.
EIM uses temporary columns to manipulate data during processing. For example, EIM might store the ROW_ID value for a Siebel base table in a temporary column. These column names begin with T_ and indicate the table or column for which they are used. Because EIM uses these columns internally during processing, do not manipulate these columns in the EIM tables.
Each EIM table has three processing columns at the EIM table level:
1) T_DELETED_ROW_ID Deleted ROW_ID from the Base Table.
2) T_EXPORTED_ROW_ID Exported ROW_ID from Target Table.
3) T_MERGED_ROW_ID Merged into ROW_ID from Target Table.
Four processing columns for each table mapping:
1) Name : T_XXX_RID, Type: IFMGR: ROW_ID
2) Name : T_XXX_EXS, Type: IFMGR :Exists
3) Name : T_XXX_STA, Type : IFMGR : Status
4) Name : T_XXX_UNQ,Type : IFMGR: Unique
One processing column for each foreign key mapping (Name: T_XXX_BU_ID, Type: IFMGR: Fkey.
A user key specifies columns that must contain unique sets of values. It is used to determine the uniqueness of records during data import operations in EIM. The purpose of user keys is to prevent users from entering duplicate records.
A user key is designated by the name of its parent table with an _Un suffix, such as S_PROD_INT_U1. Each user key has User Key Column child objects that specify the table columns that must have unique values, for example BU_ID, NAME, and VENDR_OU_ID in the S_PROD_INT_U1 user key. A predefined index exists for each Siebel-defined user key. This index also takes the form S_TABLE_NAME_Un.
Do not modify user keys in standard Siebel tables or EIM base tables. This is a restricted activity and should not be attempted without assistance.
Posts
