2013 Sep 15 1:24 AM
Hi:
I have create LSMW via method batch input while recording I ended with cancel button.
System create batch input ended with /EESC.
but when I run LSMW ,it's created real transaction record.
is there anyway to make LSMW do the same as /eesc while I do recording.
I also see in the field mapping per screen below that it transfer record, transfer transaction. is there anyway to make it not committed record.
2013 Sep 15 10:22 AM
I dont see any connection between a /EESC in your recording and the field mapping from LSMW.
The field mapping in LSMW cares about the fields that you recorded, not about the functions.
the processing times and global functions are related to the conversion process of your source data.
if you have 100 records in your source file, then you convert 100 records and get 100 records in the .conv file (if you have not skipped some with logic during the conversion process) .
then you create a batch input session from this .conv file.
so you finally have 100 transactions in the batch input, and each gets cancelled on the last screen, result: noting posted . A lot effort for nothing
You have to record including the SAVE otherwise you will not write anything to the database with such recording
Hi:
I have create LSMW via method batch input while recording I ended with cancel button.
System create batch input ended with /EESC.
but when I run LSMW ,it's created real transaction record.
is there anyway to make LSMW do the same as /eesc while I do recording.
I also see in the field mapping per screen below that it transfer record, transfer transaction. is there anyway to make it not committed record.
2013 Sep 15 10:22 AM
I dont see any connection between a /EESC in your recording and the field mapping from LSMW.
The field mapping in LSMW cares about the fields that you recorded, not about the functions.
the processing times and global functions are related to the conversion process of your source data.
if you have 100 records in your source file, then you convert 100 records and get 100 records in the .conv file (if you have not skipped some with logic during the conversion process) .
then you create a batch input session from this .conv file.
so you finally have 100 transactions in the batch input, and each gets cancelled on the last screen, result: noting posted . A lot effort for nothing
You have to record including the SAVE otherwise you will not write anything to the database with such recording
2013 Sep 15 11:19 AM
yes,it's my intention not to save because I just would like to test run whether the data correct or not.
I see the abap program is /SAPDMC/SAP_LSMW_BI_RECORDING.
is there anywhere that I can comment out the command SAVE please.
2013 Sep 15 11:32 AM
technically you can export your LSMW object and edit it with notepad and import it again. I did it a few times but for different cases, not sure if it will work for your desire.
But the only thing that you could test this way is the screen sequencing, if you have batch input data for the screen that may come up, but the checks that are performed during posting cannot be checked this way