Skip to main content
Answer

Cloud 25R1SU5 - error when setting history log

  • December 4, 2025
  • 3 replies
  • 50 views

Forum|alt.badge.img+8

Hi,

 

We are getting the following error when setting up a history log for a custom field table. Any help on this is appreciated. TIA

 

 

Best answer by athasanka

Okay, fixed my own issue. It seems to be a bug in the application where the error is triggerred for LUs having legacy Info Cards set up. Problem went away once I delete the records from this table.

 

 

3 replies

Marcel.Ausan
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • December 4, 2025

@athasanka most probably you’re getting the error because you wanna track updates for ROWKEY in a CFT.

The ROWKEY updates could be tracked in the base table if needed - SC_SERVICE_CONTRACT_TAB. I think you are not allowed to do it in the CFT.

Just leave CF$_VALID_TO in SC_SERVICE_CONTRACT_CFT and track updates for ROWKEY in SC_SERVICE_CONTRACT_TAB


Forum|alt.badge.img+8
  • Author
  • Sidekick (Customer)
  • December 4, 2025

@athasanka most probably you’re getting the error because you wanna track updates for ROWKEY in a CFT.

The ROWKEY updates could be tracked in the base table if needed - SC_SERVICE_CONTRACT_TAB. I think you are not allowed to do it in the CFT.

Just leave CF$_VALID_TO in SC_SERVICE_CONTRACT_CFT and track updates for ROWKEY in SC_SERVICE_CONTRACT_TAB

Hi ​@Marcel.Ausan 

 

Thanks for your response. It was a mistake from my part to turn on logging for the rowkey. I only wanted to track the changes for the custom fields. It does trigger the error either way. 

Step 1: no tracking enabled.

Step 2: Enable logging for any custom field.


Forum|alt.badge.img+8
  • Author
  • Sidekick (Customer)
  • Answer
  • December 8, 2025

Okay, fixed my own issue. It seems to be a bug in the application where the error is triggerred for LUs having legacy Info Cards set up. Problem went away once I delete the records from this table.