hi Maria, I am a bit confused by this post.
I am currently building an Evolve solution in which I use about 6 direct scripts (xml).
They do not have the "Commit Required" check on. However, the data is posted in SAP.
What I do notice however, is that for example with BAPI RFC_CVI_EI_INBOUND_MAIN, the general (BP 000000) data I create, at first is not available via tcode BP. I do see the data in table BUT000000 (not in KNA1).
The BAPI also returned a BP number.
Only when I do a next script (which is not a BAPI) to complete this data and then open that BP number in tcode BP, it fully shows.
I always (thought to) understood that, if Commit Required is unchecked, you would need another BAPI to actually commit it. This would also mean that, as long as it is not committed, the data is somewhere in SAP claiming a (in this case) BP number. I don't know for how long though.
I can understand that this is a way to "validate" but is it a correct way? Could you elaborate on this topic?
------------------------------
Ed Meiners
Lead Consultant MDIM
Wessanen Nederland Holding BV
Amsterdam
------------------------------
Original Message:
Sent: 08-11-2025 10:12
From: Maria Ebner
Subject: Tip of the Week – Create Validation Script for BAPI Using Direct
Hi Automate Community!
This week I have a quick tip when creating BAPI scripts using the Direct module in Automate Studio. If you need to post data to SAP, then check "Commit required" in the panel on the right in the Workspace tab:

Direct scripts don't have a validate option, so if you want to validate the data before posting, you can create a copy of the script and uncheck "Commit required". This can be your validation script.
If you're using a BAPI to get data from SAP, then you don't need to check "Commit required" since changes are not getting posted to SAP.
Here is documentation to create a Direct script for a BAPI.
Thanks!
------------------------------
Maria Ebner
*Precisely Software Inc.
------------------------------