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
------------------------------

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