As mentioned earlier SAP is very much flexible and you can use as per your requirement. I had the similar requirement in one of my implementation project where client was not confident to use the online SAP RF functionality and hence the system was designed in such a way that after transfer order creation, Transfer order related detail was getting converted into the CSV file and gets transferred to the RF device which was working in offline mode. Once user complete the process then again we used to upload the CSV data file from RF to SAP system and then further confirmation / cancellation / Deletion of Transfer order used to take place in SAP
High Level process Steps
1) Transfer order creation in SAP WM
2) Transfer the CSV file to AL11 directory with a unique naming convention e.g. YYYYMMDDHHMMSS_TO NUMBER
3) Operator dock the RF device to DOCKING station
4) Custom program to trigger the upload of CSV file from AL11 directory to RF device, Logic built to make sure that file are getting transferred successfully
5) Once file gets transferred successfully it gets moved to archive folder
6) After completion of task operator docks the RF gun at Docking station back and run the download program , This will download the CSV file from RF to system folder.
7) Run the upload program and it will transfer the file from C:\ drive to AL11 folder and then TO confirmation takes place
Hope the above steps will give you some insight. Revert back if you need any further input
The con of the above process is you need a medium to complex custom development in SAP and same in RF for picking / put away and other activity which u have planned. Keep a track of AL11 folder size / archiving process. Troubleshooting (Handling any worst situation where data (CSV) lost during transfer or got deleted by mistake / Dependency on vendor to make change (if any ) in the RF device for the developed screen)