Cognite SAP extractor: Intgerate with T-codes

Thank you for sharing one more your insightful reflection, Harsha! 

We greatly appreciate your contribution and stay tuned for updates on how we plan to proceed.

 @Har

@Harsha I would like to understand how you are thinking about utilizing this enhancement. As far as I know, the Transaction Codes are mainly for interacting with SAP using the SAP GUI. 

Thanks,

Dinesh

1. Existing Business Processes:

   • integrating directly with these codes can be more aligned with the current workflow.

2. Complexity and Customization:

   • Some SAP functionalities or customizations may not have corresponding BAPIs or standard APIs. In such cases, using T-codes might be the only feasible option for integration.

we are also struggling with Performance of the extractor.

Hello @Harsha ,

Thank you for reaching out to us with your suggestion regarding SAP T-codes.

We truly appreciate your interest in improving our system. However, after careful consideration and analysis of our current strategy, we've determined that developing T-codes is not aligned with our current direction.

SAP T-codes indeed play a significant role in utilizing SAP resources and system operations. However, it's worth noting that our approach to data extraction is more aligned with modern practices. Our extractor was specifically designed to fetch data from SAP at the entity level, offering a more efficient and streamlined process compared to traditional T-code usage.

We understand that this may not be the response you were hoping for, but please know that we value your input and suggestions. If you have any other ideas or feedback that you'd like to share, we're all ears!

Once again, thank you for taking the time to share your thoughts with us. We appreciate your understanding.

Best regards,

Elka