Services Integration Framework Guide

10.3

Back Next

CleanTable

A CleanTable request removes data from an

Operational Reference Store

table and all its companion tables.

Request Parameters

A CleanTable request contains the following parameters:

SiperianObjectUid: Identifier of a base object or a table from which you want to remove data.
CleanStaging: Optional. Indicates whether to remove rows in the staging tables and the dependent tables such as
<Staging Table>_CL
,
<Staging Table>_DLT
,
<Staging Table>_RAW
,
<Staging Table>_REJ
,
<Staging Table>_OPL
, and
<Staging Table>_PRL
.; The CleanStaging parameter uses the following values:
True. Removes the rows in the staging tables and the dependent tables.
False. Retains the rows in the staging tables and the dependent tables.

Default is false.
UseTruncate: Optional. Indicates whether to use the TRUNCATE or DELETE statement to remove the records.; The UseTruncate parameter uses the following values:
True. Uses the TRUNCATE statement, which functions faster, to remove the records. In the Oracle-distributed transaction environments, the TRUNCATE statement commits transactions that might cause errors.
False. Uses the DELETE statement, which functions slower, to remove the records.

Default is false.

Response Fields

The CleanTable request returns the following fields:

InteractionId: An identifier for the request.
Message: A brief message about the status of the request.

Usage Example

The following code sample uses the TRUNCATE statement to remove data from the base object C_PARTY and the associated staging table:

CleanTableRequest request = new CleanTableRequest(); 
request.setSiperianObjectUid("BASE_OBJECT.C_PARTY");
request.setCleanStaging(true);
request.setUseTruncate(true);
CleanTableResponse response = (CleanTableResponse)sipClient.process(request);

Rename Saved Search

Table of Contents

Services Integration Framework Guide

Services Integration Framework Guide

CleanTable

CleanTable

Request Parameters

Response Fields

Usage Example