Skip to end of metadata
Go to start of metadata

Re-Setting COPA Init Timestamp

The target audience for this document is BW Administrators in BTC, FTS & GC's.

1.1 - Table TKEBWTS

R/3 table TKEBWTS contains data about the COPA load requests that have been ran into BW.  The key data fields in this table can be seen in the screenshot below:


The screenshot above shows the data fields contains in one table record.  The key fields contain the following information:








Dataload Request No


The low range of the timestamp.  If 0, this equates to some date a long time in the past eg. 01/01/1900.  If not 0, this equates to a time (in milliseconds) approx. 30 mins before the dataload was ran.


The high range of the timestamp.  this equates to a time (in milliseconds) approx. 30 mins before the data load was ran.


The start date of the dataload request


The start time of the dataload request


The end date of the dataload request


The end time of the dataload request


Number of records read


Number of records sent

Any record in this table with a TSLOW entry of 0 relates to an Init request.  Any record in this table with a TSLOW not equal to 0 relates to a Delta request (and the TSLOW value should equal the TSHIGH value of the previous record – so there is no discontinuity in the timing of the requests).

1.2 - Recording the timestamp from TKEBWTS

In R/3 run transaction SE16, enter table TKEBWTS

Input the relevant COPA datasource (1_CO_PA111xxxx, 1_CO_PA222xxxx or 1_CO_PA333xxxx – where xxxx is the Operating Concern)


From the table double click on the latest request

The field to be recorded is the TS HIGH field – highlighted above.

1.3 - Changing existing Timestamp in TKEBWTS

When a COPA Init is run without data transfer, no new record in created in table TKEBWTS, it can be necessary to run this Init to allow subsequent deltas to work so in order to record a timestamp in table TKEBWTS follow the process below :

In R/3, run transaction SBIW then drill-down through the following nodes:

-          Settings for Application-Specific DataSources (PI)

-          Profitability Analysis

-     Tools

(Alternatively run transaction KEB5)

Enter the Operating Concern and the CO-PA Datasource

Check the Direct Input flag and paste in the required Timestamp


You should then get a confirmation message that the update has been made. You should check this by looking in the table TKEBWTS where there will be 1 entry with Request No. = ARTIFICIAL and the timestamp should be the one you entered above.

  • No labels