Automate

Good afternoon, users. I want to establish connections with other businesses that extract component allocation. My objective is to learn how other businesses' extract processes in order to identify methods for enhancing our own. We are increasing the use of component allocation in Q1 2025, hence we need a quicker way to gather data for updates. For particularly big assemblies, our current method of retrieving data using an Excel macro can take up to two hours. Attempts to use the Studio extract process results in user error and the additional bom component numbers. 

Hi Ben,

We went through the same thing a few years ago trying to figure out how to get the data out of SAP. I messed around with queries for a while, but I wasn't able to figure it out enough where it would provide consistent results.

I eventually recorded a CA03 (and CA13 for reference operation sets) script as a transaction and downloaded the fields to provide results. One thing to note - and this is TOTALLY not Winshuttle's fault - but it runs slower than a two-dollar mule. I re-recorded it with the same results. It's just something about the way it pulls the data out of our system that makes it grind away for a long time. I attached a couple screen shots to give you an idea of how to get into the t-code and then the fields that are downloaded. Works great, just not fast. It does run on the server for us so whenever I need to pull data I schedule it and just wait for the results whilst working on other stuff.

Hope this helps.

Derek

Good afternoon, users. I want to establish connections with other businesses that extract component allocation. My objective is to learn how other businesses' extract processes in order to identify methods for enhancing our own. We are increasing the use of component allocation in Q1 2025, hence we need a quicker way to gather data for updates. For particularly big assemblies, our current method of retrieving data using an Excel macro can take up to two hours. Attempts to use the Studio extract process results in user error and the additional bom component numbers. 

Thank you, Derek. To confirm systems, we are using SAP ECC 760. This looks promising to try out. If at all possible, could I set up a meeting to walk through the steps after the main screen of CA03. I am not able to follow the fields to screen steps from the screens you sent. I am willing to display my data to understand all screens and steps that are used. Thank you in advance.

Hi Ben,

We went through the same thing a few years ago trying to figure out how to get the data out of SAP. I messed around with queries for a while, but I wasn't able to figure it out enough where it would provide consistent results.

I eventually recorded a CA03 (and CA13 for reference operation sets) script as a transaction and downloaded the fields to provide results. One thing to note - and this is TOTALLY not Winshuttle's fault - but it runs slower than a two-dollar mule. I re-recorded it with the same results. It's just something about the way it pulls the data out of our system that makes it grind away for a long time. I attached a couple screen shots to give you an idea of how to get into the t-code and then the fields that are downloaded. Works great, just not fast. It does run on the server for us so whenever I need to pull data I schedule it and just wait for the results whilst working on other stuff.

Hope this helps.

Derek

Good afternoon, users. I want to establish connections with other businesses that extract component allocation. My objective is to learn how other businesses' extract processes in order to identify methods for enhancing our own. We are increasing the use of component allocation in Q1 2025, hence we need a quicker way to gather data for updates. For particularly big assemblies, our current method of retrieving data using an Excel macro can take up to two hours. Attempts to use the Studio extract process results in user error and the additional bom component numbers.