Automate

Hello All,

Is there any knowledge of why transactions ABSO and AB01 cannot be recorded using Standard or Batch recording modes against a S4 converted SAP?  We had ABSO scripts that worked against ECC, but now after converting to S4, they fail with a logfield message of "LEAVE TO TRANSACTION" is not allowed in batch input. 

When I go to do a new recording, it does not open the SAP instance and get the following errors:

Standard:
No_Input_Value

Batch:
Recording was either canceled or an error occurred.

It does appear a GUI Scripting recording type might work, so I am exploring that, but I wanted to see if anything was known on the above while I did.  I did see other posts about other transactions with similar issues and the recording types, but nothing was ever brought back if there was information discovered.

Thanks!

Hey Scott, 

What SAPGUI and Studio Versions are you using? 

Hello All,

Is there any knowledge of why transactions ABSO and AB01 cannot be recorded using Standard or Batch recording modes against a S4 converted SAP?  We had ABSO scripts that worked against ECC, but now after converting to S4, they fail with a logfield message of "LEAVE TO TRANSACTION" is not allowed in batch input. 

When I go to do a new recording, it does not open the SAP instance and get the following errors:

Standard:
No_Input_Value

Batch:
Recording was either canceled or an error occurred.

It does appear a GUI Scripting recording type might work, so I am exploring that, but I wanted to see if anything was known on the above while I did.  I did see other posts about other transactions with similar issues and the recording types, but nothing was ever brought back if there was information discovered.

Thanks!

Hello All,

Is there any knowledge of why transactions ABSO and AB01 cannot be recorded using Standard or Batch recording modes against a S4 converted SAP?  We had ABSO scripts that worked against ECC, but now after converting to S4, they fail with a logfield message of "LEAVE TO TRANSACTION" is not allowed in batch input. 

When I go to do a new recording, it does not open the SAP instance and get the following errors:

Standard:
No_Input_Value

Batch:
Recording was either canceled or an error occurred.

It does appear a GUI Scripting recording type might work, so I am exploring that, but I wanted to see if anything was known on the above while I did.  I did see other posts about other transactions with similar issues and the recording types, but nothing was ever brought back if there was information discovered.

Thanks!

Hi Scott

Does this community post help?  https://community.precisely.com/communities/community-home/digestviewer/viewthread?GroupId=865&MID=44997&CommunityKey=4418e63a-9f6f-4468-b3f1-0186605ed001

They put an IF First Transaction around the pop-up.  Different tcode, but similar message in Asset Accounting.

HTH,

Sigrid

Hello All,

Is there any knowledge of why transactions ABSO and AB01 cannot be recorded using Standard or Batch recording modes against a S4 converted SAP?  We had ABSO scripts that worked against ECC, but now after converting to S4, they fail with a logfield message of "LEAVE TO TRANSACTION" is not allowed in batch input. 

When I go to do a new recording, it does not open the SAP instance and get the following errors:

Standard:
No_Input_Value

Batch:
Recording was either canceled or an error occurred.

It does appear a GUI Scripting recording type might work, so I am exploring that, but I wanted to see if anything was known on the above while I did.  I did see other posts about other transactions with similar issues and the recording types, but nothing was ever brought back if there was information discovered.

Thanks!

Unfortunately no.  Thanks for the suggestion.  Yes, it is the same message, but that post was referring to a script that would run the first record then fail after. 

I can't even start a new recording against the T-Code in Standard or Batch mode without error pop ups.  Also for the existing script, it is a Batch recording so no Extended log is available and I try to run Debug mode and it fails to open SAP and drops that same log message to the file, stating it was a successful run.  I tried to switch that script to other Recording Modes, to see if the Extended log would show anything different, it behaves the same and the Extended log shows the same as the normal log. 

Hi Scott

Does this community post help?  https://community.precisely.com/communities/community-home/digestviewer/viewthread?GroupId=865&MID=44997&CommunityKey=4418e63a-9f6f-4468-b3f1-0186605ed001

They put an IF First Transaction around the pop-up.  Different tcode, but similar message in Asset Accounting.

HTH,

Sigrid

Hello All,

Is there any knowledge of why transactions ABSO and AB01 cannot be recorded using Standard or Batch recording modes against a S4 converted SAP?  We had ABSO scripts that worked against ECC, but now after converting to S4, they fail with a logfield message of "LEAVE TO TRANSACTION" is not allowed in batch input. 

When I go to do a new recording, it does not open the SAP instance and get the following errors:

Standard:
No_Input_Value

Batch:
Recording was either canceled or an error occurred.

It does appear a GUI Scripting recording type might work, so I am exploring that, but I wanted to see if anything was known on the above while I did.  I did see other posts about other transactions with similar issues and the recording types, but nothing was ever brought back if there was information discovered.

Thanks!

Hi Scott

Would you consider a BAPI?  https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/asset-legacy-data-migration-in-new-assets-accounting-s-4-hana-1909-current/ba-p/13429877

This one mentions for AB01 to use this BAPI instead:  BAPI_ASSET_ACQUISITION_POST

I'm not an asset expert, so IDK if ABSO could be accomplished with the same BAPI or not.  I also don't know if I picked the right transaction type, but example attached.

Unfortunately no.  Thanks for the suggestion.  Yes, it is the same message, but that post was referring to a script that would run the first record then fail after. 

I can't even start a new recording against the T-Code in Standard or Batch mode without error pop ups.  Also for the existing script, it is a Batch recording so no Extended log is available and I try to run Debug mode and it fails to open SAP and drops that same log message to the file, stating it was a successful run.  I tried to switch that script to other Recording Modes, to see if the Extended log would show anything different, it behaves the same and the Extended log shows the same as the normal log. 

Hi Scott

Does this community post help?  https://community.precisely.com/communities/community-home/digestviewer/viewthread?GroupId=865&MID=44997&CommunityKey=4418e63a-9f6f-4468-b3f1-0186605ed001

They put an IF First Transaction around the pop-up.  Different tcode, but similar message in Asset Accounting.

HTH,

Sigrid

Hello All,

Is there any knowledge of why transactions ABSO and AB01 cannot be recorded using Standard or Batch recording modes against a S4 converted SAP?  We had ABSO scripts that worked against ECC, but now after converting to S4, they fail with a logfield message of "LEAVE TO TRANSACTION" is not allowed in batch input. 

When I go to do a new recording, it does not open the SAP instance and get the following errors:

Standard:
No_Input_Value

Batch:
Recording was either canceled or an error occurred.

It does appear a GUI Scripting recording type might work, so I am exploring that, but I wanted to see if anything was known on the above while I did.  I did see other posts about other transactions with similar issues and the recording types, but nothing was ever brought back if there was information discovered.

Thanks!