# Transaction Scope: Topic -\> KStream -\> KTable
**URL:** https://forum.confluent.io/t/transaction-scope-topic-kstream-ktable/37354
**Category:** Architecture and Design
**Created:** [27 February 2025 18:03 UTC](https://forum.confluent.io/t/transaction-scope-topic-kstream-ktable/37354 "2025-02-27T18:03:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@VaughnVernon](https://forum.confluent.io/u/VaughnVernon)
#### Post date: [27 February 2025 18:03 UTC](https://forum.confluent.io/t/transaction-scope-topic-kstream-ktable/37354/1 "2025-02-27T18:03:10Z")
Hey! Sorry, I don’t know if this is the correct category.
It has been suggested that a transactional producer performing topic partition send can wrap the streaming to a consumer that transforms and writes to a KTable:
```auto
producer.beginTransaction();
producer.send(record);
// in-txn-scope: post topic partition write streamed record
// in-txn-scope: streamed record transformed and written to ktable
producer.commitTransaction();
```
Is this true or false?
Thanks a bunch!
---
### Author:  [@VaughnVernon](https://forum.confluent.io/u/VaughnVernon)
#### Post date: [2 March 2025 15:41 UTC](https://forum.confluent.io/t/transaction-scope-topic-kstream-ktable/37354/2 "2025-03-02T15:41:50Z")
Shall I take no response as a “no” answer? It seems obvious to me that the KStream and/or KTable are not in the Producer’s potential multi-partition 2PC. Still, I did want to inquire in case there was recent support for KTable transactional consistency.