Automate

​Hi all

I have a solution for single records in composer that utilizes both query and transaction that works well for.
We are now looking into multiple records for both download and upload stream using Excel with studio intergration.
What I am looking for is the possibility to download (query) multiple records to excel, amend data or some attributes and then upload the new data but using excel-intergration with Studio in the background rather than having an online form.
Anyone running this kind of set-up for mass-change or have any other advice or tips?

------------------------------
Henrik Axell Master Data Analyst
Essity Hygiene and Health
------------------------------

Hi Henrik

I have created a few solutions to do a "round trip" in a form. 

They can be a great format, as long as you don't have too much data (for usability and performance), and you make it easy for someone to update columns in rows - like using header fields to push values down into the table.

(1) I typically start by adding the Transaction script to do the update, and I make it a repeating web service when I import it - don't add it through the new solution wizard.
(2) I add the query script.  When I do, I map the query output fields directly to the Transaction input fields.  No need to make this a repeating web service, the output is already repeating.

There are lots of little things to consider with the repeating table - turning on pagination if you expect more than 20-30 rows, disabling adding rows, making sure you have ways to do look ups (not all work in a repeating group/table), etc.  

Hope that helps a little.  

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle North America
------------------------------

​Hi Henrik:

We often use two scripts developed in Transaction to do data cleansing on the Vendor Master.  We record an upload script [excel to SAP] first, then clone the same script with a different name [like the original script name + report].  We go into the clone with Transaction and change the direction from upload to download [SAP to Excel].  Now we have two scripts that share the same layout.

We select a target batch of Vendor Numbers for cleansing and use the report script to download the data to excel.  We get the data stewards responsible for that data to review the batch and make corrections in Excel, then we upload the changes using the upload script.

We have also used this two script method for Material MRP update verifications, our logistics folks provide the mass update excel and we use the report script to verify the changes using upload script first and running the report script after to provide verifications of the changes [for our audit friends].

To keep longer running batches from keeping our laptops busy, we have two workstation in a hotel cube to run long Winshuttles on.  We don't have the coin to buy all the products we want, so we utilize Transaction and Runner to the fullest extent.  We are currently on Studio v11 for both, most people don't utilize the download features in Transaction but they are there to be exploited. 

Good luck and hope this helps.

------------------------------
Robert D Thomas | MDG Supply Chain Advisor / PM
Southern California Edison (SCE) | 626-665-8313
------------------------------

Thank you both Sigrid and Robert, this helps quite a bit in my way of thinking and move forward.
In a smaller scope I think it would work really well to utilize a downstream and upstream with transaction, but I also like the versatility that query offers in terms of individual settings and I wonder if I can use query and change the search-criteria or set so I can use various search-criterias in order to extract data?

------------------------------
Henrik Axell Master Data Analyst
Essity Hygiene and Health
------------------------------

Original Message:
Sent: 02-06-2019 16:51
From: Robert D Thomas
Subject: MM02 Multiple records

​Hi Henrik:

We often use two scripts developed in Transaction to do data cleansing on the Vendor Master.  We record an upload script [excel to SAP] first, then clone the same script with a different name [like the original script name + report].  We go into the clone with Transaction and change the direction from upload to download [SAP to Excel].  Now we have two scripts that share the same layout.

We select a target batch of Vendor Numbers for cleansing and use the report script to download the data to excel.  We get the data stewards responsible for that data to review the batch and make corrections in Excel, then we upload the changes using the upload script.

We have also used this two script method for Material MRP update verifications, our logistics folks provide the mass update excel and we use the report script to verify the changes using upload script first and running the report script after to provide verifications of the changes [for our audit friends].

To keep longer running batches from keeping our laptops busy, we have two workstation in a hotel cube to run long Winshuttles on.  We don't have the coin to buy all the products we want, so we utilize Transaction and Runner to the fullest extent.  We are currently on Studio v11 for both, most people don't utilize the download features in Transaction but they are there to be exploited.

Good luck and hope this helps.

------------------------------
Robert D Thomas | MDG Supply Chain Advisor / PM
Southern California Edison (SCE) | 626-665-8313
------------------------------

Hi Henrik

Robert's suggestion is good if you know what you want to update.  I've shown that technique, as well.

With query, you have the flexibility to use search criteria directly in the form to find what you need to update. 

• I like to make some of the criteria required in the script, so that someone doesn't accidentally try to return all of the objects in SAP. 
• I expose some search criteria in the form
• I like to either fix the values of some of the criteria in the query script (as appropriate) or set behind the scenes so that the person using the form doesn't have to enter them. 
• With Query criteria, case can sometimes be important, as can padding, so please keep that in mind when exposing search criteria - in a form or in excel.  

HTH
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle North America
------------------------------

Original Message:
Sent: 02-07-2019 09:47
From: Henrik Axell
Subject: MM02 Multiple records

Thank you both Sigrid and Robert, this helps quite a bit in my way of thinking and move forward.
In a smaller scope I think it would work really well to utilize a downstream and upstream with transaction, but I also like the versatility that query offers in terms of individual settings and I wonder if I can use query and change the search-criteria or set so I can use various search-criterias in order to extract data?

------------------------------
Henrik Axell Master Data Analyst
Essity Hygiene and Health
------------------------------


Original Message:
Sent: 02-06-2019 16:51
From: Robert D Thomas
Subject: MM02 Multiple records

​Hi Henrik:

We often use two scripts developed in Transaction to do data cleansing on the Vendor Master.  We record an upload script [excel to SAP] first, then clone the same script with a different name [like the original script name + report].  We go into the clone with Transaction and change the direction from upload to download [SAP to Excel].  Now we have two scripts that share the same layout.

We select a target batch of Vendor Numbers for cleansing and use the report script to download the data to excel.  We get the data stewards responsible for that data to review the batch and make corrections in Excel, then we upload the changes using the upload script.

We have also used this two script method for Material MRP update verifications, our logistics folks provide the mass update excel and we use the report script to verify the changes using upload script first and running the report script after to provide verifications of the changes [for our audit friends].

To keep longer running batches from keeping our laptops busy, we have two workstation in a hotel cube to run long Winshuttles on.  We don't have the coin to buy all the products we want, so we utilize Transaction and Runner to the fullest extent.  We are currently on Studio v11 for both, most people don't utilize the download features in Transaction but they are there to be exploited.

Good luck and hope this helps.

------------------------------
Robert D Thomas | MDG Supply Chain Advisor / PM
Southern California Edison (SCE) | 626-665-8313