So you are trying to directly manipulate files in moodledata/filedir/XX/XX/ that are scorm zip's?
Using mysql client search for one of those uploaded .zip files and get the contenthash as well as contextid.
then another query like:
select contenthash,component,filearea,contextid,filename,filesize from mdl_files where (component like '%scorm%' and contextid like '3469');
I did this for a site that uses scorm almost exclusively ... that's where the contextid came from in this example.
The zip file originally uploaded (you call module) was named: interactive_long_09_SL2_17_07-Storylineoutput.zip
72036926 in size and when unzipped in a test directory on the server ...
adlcp_rootv1p2.xsd ims_xml.xsd lms story.html
imscp_rootv1p1p2.xsd index_lms.html meta.xml story_html5.html
imsmanifest.xml index_lms_html5.html mobile story.swf
imsmd_rootv1p2p1.xsd interactive_long_09_SL2_17_07-Storylineoutput.zip story_content story_unsupported.html
For that one scorm package ... which is unzipped .... there are 843 references in mdl_files to files contained in the scorm package - in moodledata/filedir/ none of them have the same contenthash directories ... but are spread out all over moodledata/filedir/
So am not sure one can manipulate 'modules' (scorms) in the fashion you are attempting.
'spirit of sharing', Ken