We can send email by using out of box business service, outbound communication manager and selecting appropriate method to send the email with or without template. This service can be called through a script or through a workflow process where this business service is a step in it.
This is not possible. EIM relies on user keys to identify rows in base tables. If there are two rows in the base table that have the same user key but different conflict IDs, EIM cannot distinguish these rows. In such case, the IF_ROW_STAT field of the row in the interface table will be marked as ambiguous.
NOTE: When you are deleting records based on user keys, the parameter DELETE EXACT should be specified in the .ifb configuration file.
BU_ID is primarily created , to provide a setup to have multiple organizations in the same application. This concept will be very useful when people store the information about 'sister' concern which always say.
At this moment, it is important to differentiate the different critical business entities across organizations, such as ACCOUNT, PRODUCT, POSITION and so on which are in the top hierarchy. That is why to identify an unique account across organization, BU_ID has been added into the user key of most of the table and thus inserting these data into siebel through EIM/Regular import requires BU_ID to get populated.
For all columns to export using an interface table (both data from the base table and data from related child tables), you need to add or modify the following line in the . ifb configuration file:
Export all Columns = TRUE
NOTE: Rows from child tables of related child tables will not be exported.
The delete process performed by EIM is cascade delete. The data deleted is not restricted to the base tables mapped to the interface table that you specified in the delete process but all child records as well. You should be very careful and specific when specifying delete criteria.
EIM tables are interface tables, when we want to export or import data from siebel base tables we need first to get the data from tha base tables to interface tables, the EIM component will have the .IFB file, in that file we need to specify type, source table, target table, batch number. It will successfully export or import the data.
A single siebel enterprise server can have one db server(a 3rd party RDBMS) this scenario is possible. A single siebel enterprise server can have multiple or more than one db server(multiple 3rd party RDBMS.
No, you should not remove unnecessary seed data by deleting all rows from the S_LST_OF_VAL base table. If you do so, you will not be able to reimport "clean" data and you will be forced to rebuild the seed data or restore from backup.
Using the criteria "DELETE MATCHES = EIM_PARTY, (CREATED > xxxxx)" will cause all records of S_PARTY that matches this criteria to be deleted from the database.
To import international phone numbers, the phone number must be prefixed with a plus (+) sign and the country code. For example, an international phone number with a country code of 44 should have the following format: +44123456789. Any phone number without a preceding plus sign in the database will be treated as country's phone number. This will lead to the display of +1 in front of the phone number and the use of the corresponding PHONE_FORMAT if the regional settings of the client are different.