Automate

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

------------------------------
Maria Ebner
Precisely Software Inc.

Original Message:
Sent: 10-27-2023 06:51
From: Maik Wienkötter
Subject: Update Payment Terms with BP

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

------------------------------
Maik Wienkötter
Process Manager Material Master Data
ZWILLING J. A. Henckels AG
------------------------------

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Andrew,

My SAP behavior might be different than yours, but please try changing renew session 1 back to 0 and change the If condition to only be around the display/change button:

If you only get an error on the first one and not subsequent ones, please remove the If condition and disable those rows. 

If you're still getting errors, please send the spreadsheet with the errors (or a screenshot).

Thanks,

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Maria,

Many thanks for getting back to me and I have made the adjustments in the script as per your suggestion but I still cannot get it to work. Running row 3 in debug mode, it doesn't seem to be resetting back to the beginning. I'll keep trying and see what I can do but if could possibly take a look and see if anything is glaring at you, please let me know.

Thanks again.

Hi Andrew,

My SAP behavior might be different than yours, but please try changing renew session 1 back to 0 and change the If condition to only be around the display/change button:

If you only get an error on the first one and not subsequent ones, please remove the If condition and disable those rows. 

If you're still getting errors, please send the spreadsheet with the errors (or a screenshot).

Thanks,

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Andrew,

Please try disabling row 3. That shouldn't be needed and could cause issues. It looks like you have a pop-up that you added a skip screen around in case it doesn't show up. Do you know when you get that pop-up? Please send the script and data file if you're still getting errors.

Thanks,

Hi Maria,

Many thanks for getting back to me and I have made the adjustments in the script as per your suggestion but I still cannot get it to work. Running row 3 in debug mode, it doesn't seem to be resetting back to the beginning. I'll keep trying and see what I can do but if could possibly take a look and see if anything is glaring at you, please let me know.

Thanks again.

Hi Andrew,

My SAP behavior might be different than yours, but please try changing renew session 1 back to 0 and change the If condition to only be around the display/change button:

If you only get an error on the first one and not subsequent ones, please remove the If condition and disable those rows. 

If you're still getting errors, please send the spreadsheet with the errors (or a screenshot).

Thanks,

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Maria

I made the changes you suggested and although the first run failed with errors, the second run worked without error? I've attached the script and template as requested so you can see what I mean. The vendors have been duplicated (highlighted in green in the second half) with the original values from our Quality test system so as not to change anything that may cause issues with other testing that is happening at the moment. (We're transitioning from 2 different ECC systems to a newer S4 system so am renewing all the scripts we currently have)

The pop up only appears the first time that a vendor (BP) is edited hence the option 2 popup with skip if not found indicator. I've attached a screenshot to show you what I mean and is displayed once the BP number is entered.

Thanks

Hi Andrew,

Please try disabling row 3. That shouldn't be needed and could cause issues. It looks like you have a pop-up that you added a skip screen around in case it doesn't show up. Do you know when you get that pop-up? Please send the script and data file if you're still getting errors.

Thanks,

Hi Maria,

Many thanks for getting back to me and I have made the adjustments in the script as per your suggestion but I still cannot get it to work. Running row 3 in debug mode, it doesn't seem to be resetting back to the beginning. I'll keep trying and see what I can do but if could possibly take a look and see if anything is glaring at you, please let me know.

Thanks again.

Hi Andrew,

My SAP behavior might be different than yours, but please try changing renew session 1 back to 0 and change the If condition to only be around the display/change button:

If you only get an error on the first one and not subsequent ones, please remove the If condition and disable those rows. 

If you're still getting errors, please send the spreadsheet with the errors (or a screenshot).

Thanks,

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Andrew,

Please try deleting the If first condition and then disable the screen that has the display/change button. When I did that in my script, it resolved the issue.

Thanks,
Maria

Hi Maria

I made the changes you suggested and although the first run failed with errors, the second run worked without error? I've attached the script and template as requested so you can see what I mean. The vendors have been duplicated (highlighted in green in the second half) with the original values from our Quality test system so as not to change anything that may cause issues with other testing that is happening at the moment. (We're transitioning from 2 different ECC systems to a newer S4 system so am renewing all the scripts we currently have)

The pop up only appears the first time that a vendor (BP) is edited hence the option 2 popup with skip if not found indicator. I've attached a screenshot to show you what I mean and is displayed once the BP number is entered.

Thanks

Hi Andrew,

Please try disabling row 3. That shouldn't be needed and could cause issues. It looks like you have a pop-up that you added a skip screen around in case it doesn't show up. Do you know when you get that pop-up? Please send the script and data file if you're still getting errors.

Thanks,

Hi Maria,

Many thanks for getting back to me and I have made the adjustments in the script as per your suggestion but I still cannot get it to work. Running row 3 in debug mode, it doesn't seem to be resetting back to the beginning. I'll keep trying and see what I can do but if could possibly take a look and see if anything is glaring at you, please let me know.

Thanks again.

Hi Andrew,

My SAP behavior might be different than yours, but please try changing renew session 1 back to 0 and change the If condition to only be around the display/change button:

If you only get an error on the first one and not subsequent ones, please remove the If condition and disable those rows. 

If you're still getting errors, please send the spreadsheet with the errors (or a screenshot).

Thanks,

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Hi Maria

Thanks ever so much for your help, the script now works seamlessly.

Many thanks again

Andy

Hi Andrew,

Please try deleting the If first condition and then disable the screen that has the display/change button. When I did that in my script, it resolved the issue.

Thanks,
Maria

Hi Maria

I made the changes you suggested and although the first run failed with errors, the second run worked without error? I've attached the script and template as requested so you can see what I mean. The vendors have been duplicated (highlighted in green in the second half) with the original values from our Quality test system so as not to change anything that may cause issues with other testing that is happening at the moment. (We're transitioning from 2 different ECC systems to a newer S4 system so am renewing all the scripts we currently have)

The pop up only appears the first time that a vendor (BP) is edited hence the option 2 popup with skip if not found indicator. I've attached a screenshot to show you what I mean and is displayed once the BP number is entered.

Thanks

Hi Andrew,

Please try disabling row 3. That shouldn't be needed and could cause issues. It looks like you have a pop-up that you added a skip screen around in case it doesn't show up. Do you know when you get that pop-up? Please send the script and data file if you're still getting errors.

Thanks,

Hi Maria,

Many thanks for getting back to me and I have made the adjustments in the script as per your suggestion but I still cannot get it to work. Running row 3 in debug mode, it doesn't seem to be resetting back to the beginning. I'll keep trying and see what I can do but if could possibly take a look and see if anything is glaring at you, please let me know.

Thanks again.

Hi Andrew,

My SAP behavior might be different than yours, but please try changing renew session 1 back to 0 and change the If condition to only be around the display/change button:

If you only get an error on the first one and not subsequent ones, please remove the If condition and disable those rows. 

If you're still getting errors, please send the spreadsheet with the errors (or a screenshot).

Thanks,

H Maria

Did you get this to work? I'm having the same issue getting my script to work so looking for some help/guidance on how to resolve. I've uploaded the script I've developed if you could give me a few pointers on getting it to work right, that would be awesome. Thanks

Hi Maik,

If the first record works and the records after that don't work, I recommend changing the "Renew session after [n] transactions" setting to 1. You can find this in the Map tab and in the properties panel on the right. Here is a screenshot:

If that doesn't resolve the issue, please share the script you created so we can take a look.

Thanks,

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

Perhaps you can get some inspiration from similar templates for BP Sales Org data (You are looking for Purchase Org data but same concept) 

https://community.precisely.com/viewdocument/bp-sales-data-round-trip?CommunityKey=e1f0c200-ca7e-46e7-b5c7-01855e5120c7&tab=librarydocuments

You can review the included transaction script and you will notice steps to set the BP Role, Tab and Edit/Display Mode are needed only the First time the BP transaction is opened. For every other row below, SAP remembers the previous selections and therefore we need to account for this behavior from SAP. 

This will ensure your remaining data also posts correctly.

------------------------------
Jayasri Varyani
SE
Winshuttle North America

Original Message:
Sent: 10-27-2023 06:51
From: Maik Wienkötter
Subject: Update Payment Terms with BP

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

------------------------------
Maik Wienkötter
Process Manager Material Master Data
ZWILLING J. A. Henckels AG
------------------------------

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik

I don't know S4 Retail but with tcode BP0 in S4 Industry you will start always from the initial starting point. In that way you don't have to work with If statement "If first transaction".

Dear all,
For some days now, I am struggeling with updating Payment Terms (LFM1-ZTERM) with TCODE BP (Business Partner) in S4 Retail and I hope, that someone might experienced the same and could lead me to a solution.
The error messages after running the recorded transaction script vary between:

Batchinput-Data for Dynpro (SAPLBUS_LOCATOR 3000 Locator Dialog Mainscreen) SAPLSPO1 0100 does not exist
SAPLBUS_LOCATOR 3000 (Values are not valid)

I found the related step-by-step approach with TCODE BUP2 (see appendix) and changed the recording mode to "BATCH INPUT mode", ticked "Start SAP GUI" on Run tab and followed the steps to return to the state when entered the transaction at the start. 
The first entry to be updated in the script works fine, the errors start from second line item.
My best guess is, that this comes from last-mentioned approach to get back to initial settings, which is special for TCODE BP.

Thank you very much for your support and efforts.

Kind regards
Maik