Automate

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance

Hi Leonard,

Maybe try to add an Upload Delay. That will give it a little time in between the records that are being updated. 

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance

Thank you Thersha for your quick response.  I added a 100ms upload delay at runtime and it worked perfectly with no conflicts.

Cheers!

Hi Leonard,

Maybe try to add an Upload Delay. That will give it a little time in between the records that are being updated. 

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance

Every now and then I experience the same (or similar) problem in Evolve webforms. SAP is slower to complete the first script/posting and the next (could be another script) is already trying to process the next transaction (can be with both regular recordings and Direct recordings).

I was intrigued by the Upload Delay setting (which never caught my eye before to be honest) but apparently (acc. Precisely support) this setting is not possible in XML scripts (which are mainly used in Evolve webforms).

They told me to raise it as customer idea so anyone who experience the same issue... please vote for my idea (title "Enable Upload Delay for XML scripts").

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance

Every now and then I experience the same (or similar) problem in Evolve webforms. SAP is slower to complete the first script/posting and the next (could be another script) is already trying to process the next transaction (can be with both regular recordings and Direct recordings).

I was intrigued by the Upload Delay setting (which never caught my eye before to be honest) but apparently (acc. Precisely support) this setting is not possible in XML scripts (which are mainly used in Evolve webforms).

They told me to raise it as customer idea so anyone who experience the same issue... please vote for my idea (title "Enable Upload Delay for XML scripts").

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance

Every now and then I experience the same (or similar) problem in Evolve webforms. SAP is slower to complete the first script/posting and the next (could be another script) is already trying to process the next transaction (can be with both regular recordings and Direct recordings).

I was intrigued by the Upload Delay setting (which never caught my eye before to be honest) but apparently (acc. Precisely support) this setting is not possible in XML scripts (which are mainly used in Evolve webforms).

They told me to raise it as customer idea so anyone who experience the same issue... please vote for my idea (title "Enable Upload Delay for XML scripts").

Recently just transitioned from standalone Winshuttle Studio 12 to Evolve 20.2 and I am encountering something I've never seen before with a tried-and-true script.  When running an MM02 script to update the Planned Price field, consecutive records for the same material (SKU) but different plants produce the following error:

The group data for the material 101P9101 is locked by LLANDRY

If I rerun the script on the error rows they will all be corrected without issue. The script itself is very simple in that it just opens the material master record and changes the planned price and planned price date on the costing 2 view. It then saves and reads the next row in the excel file.

I have been running this same script for several years on my standalone version of WS Studio and have never run into this issue before. Wondering if anyone has encountered this issue before and if there is some script setting that can be changed to prevent this.

Thank you in advance