How should EXPORT MATCHES and DELETE MATCHES be used in Siebel?
The syntax of EXPORT MATCHES and DELETE MATCHES has been changed in version 7.x./8.x This information was not available in the Siebel Bookshelf.
The following are the correct syntax for the EXPORT MATCHES and DELETE MATCHES parameters:
If the interface table's target table is not S_PARTY:
- It allows syntax of:
EXPORT MATCHES = <interface table name>, (...criteria...)
or
DELETE MATCHES = <interface table name>, (...criteria...)
EXPORT MATCHES = <target base table name>, (...criteria...)
or
DELETE MATCHES = <target base table name>, (...criteria...)
EXPORT MATCHES = (...criteria...)
or
DELETE MATCHES = (...criteria...)
- It does not allow syntax of:
EXPORT MATCHES = <non-target base table name>, (...criteria...)
or
DELETE MATCHES = <non-target base table name>, (...criteria...)
If the interface table's target table is S_PARTY:
- It allows syntax of:
EXPORT MATCHES = <target base table name, i.e. S_PARTY>, (...criteria...)
or
DELETE MATCHES = <target base table name, i.e. S_PARTY>, (...criteria...)
EXPORT MATCHES = <non-target base tables name of Siebel Extension type>, (...criteria...)
or
DELETE MATCHES = <non-target base tables name of Siebel Extension type>, (...criteria...)
- It does not allow syntax of:
EXPORT MATCHES = <interface table name>, (...criteria...)
or
DELETE MATCHES = <interface table name>, (...criteria...)
EXPORT MATCHES = (...criteria...)
or
DELETE MATCHES = (...criteria...)
To check whether a base table is of Siebel Extension type, do the following:
Login to Tools
Navigate to Table control and query a table name.
Check the Type property value. If it contains 'Extension (Siebel)', it means that this table is a Siebel Extension type table.
Note: The column names included in the criteria must be columns from the target base table or table that is specified for the EXPORT MATCHES parameter.
Strong caution is recommended when using DELETE MATCHES against non-target base table of Siebel Extension type (for example, S_ORG_EXT and S_CONTACT):
S_ORG_EXT contains records for accounts, divisions, organizations and partners.
To delete all accounts, but not divisions, organizations or partners, use the following .ifb setting:
DELETE MATCHES = S_ORG_EXT, (INT_ORG_FLG = 'N' AND PRTNR_FLG = 'N')
Refer to following SupportWeb posting on similar behavior:
Service Request 38-680047351: Using EIM to delete all Accounts
(The posting can be found by searching SupportWeb using search string: EIM AND DELETE AND EIM_ACCOUNT AND S_PARTY)
To delete all rows from S_ORG_EXT (including accounts, divisions and organizations), please use the following .ifb setting:
DELETE MATCHES = S_ORG_EXT, (NAME <> 'Default Organization')
(The seed data 'Default Organization' should not be deleted.)
S_CONTACT contains records for contacts and employees.
To delete all contacts, but not employees, use the following .ifb setting:
DELETE MATCHES = S_ORG_EXT, (EMP_FLG = 'N')
To delete all rows from S_CONTACT (including contacts and employees), use the following .ifb setting:
DELETE MATCHES = S_ORG_EXT, (ROW_ID <> '0-1')
(S_CONTACT record with ROW_ID = '0-1' is the seed data for Siebel Administrator, which should not be deleted.)
Related Articles:
Browse Categories
User login
Navigation
Popular content
- Autosys Job Handling (13,609)
- GE UNIVERSAL REMOTE INSTRUCTIONS (12,357)
- Siebel User properties (9,094)
- Test 1 - NC Drivers License Test - DMV Question Dump (8,770)
- Making a View "Read Only" based on a criteria: Aspect User Property (4,216)
- Siebel Application Response Measurement (SARM) (4,144)
- Siebel Predefined Queries (PDQ) – Reference (4,080)
- Siebel Server Component Event Logging (3,662)
- Strategies for Building Team Cohesion (3,153)
- How to create the EBC’s in Siebel (3,085)
Readers who viewed this page, also viewed:
- Real time Siebel EIM (Enterprise Integration Manager) Interview Questions – Part 1 (92.3%)
- How to Troubleshoot Database Errors Caused by Deleting Repositories using Siebel Tools (69.2%)
- Automatic Logoff from the Siebel Client session, based on specific conditions. (69.2%)
- Is it possible to set up individual user locales? (61.5%)
- What values must be populated for PARTY_TYPE_CD, PARTY_UID and ROOT_PARTY_FLG columns in S_PARTY table using EIM (61.5%)
- Handling Data Dependencies in EIM using IFB Files (61.5%)
- Siebel EIM Import Order of Entities (61.5%)
- Tracing Siebel server task with SQL Trace and TKPROF in Oracle (53.8%)
- Overview of Siebel Enterprise Integration Manager (EIM) (53.8%)
- EIM EXPORT / DELETE functionality for S_PARTY siebel base tables (53.8%)
