Administrator
|
fmb and fmx are 2 different disk
fmx is executable and fmb is like the source.
You put your fmb into AU_TOP and compile it there. You set the output file location to CUSTOM_TOP.
for ex:
cd $AU_TOP/forms/US
frmcmp_batch ERMAN.fmb <apps_username>/<apps_password> output_file=$ERMANCUSTOM_TOP/forms/US/ERMAN.fmx compile_all=special
There is an important note: "Remember to ensure synchronization commands for the custom forms files are included in the custom synchronization driver."
As I said earlier.
you can sync the $ERMANCUSTOM_TOP/forms/US/ and test if your custom for is working.
This is a method, but it should be tried..
However, it may be better to sync the $AU_TOP/forms/<LANG>/yourcustomform.fmb to get the fmbs in the patch edition.
Adop may automatically create fmxs after this syncronization.
So, you should try by running the online patching cycle.
So, here is the action plan:
write down the necessary sync commands in adop_sync.drv for syncing the newly deployed fmb. (AU_TOP/forms/LANG/(yourcustom.fmb)
run online patching cycle.
After finishing the online patching cycle, check the patch fs a(AU_TOP)nd see if that custom fmb is synched.
Then check the CUSTOM_TOP of patch fs and see if the the custom fmx is generated automatically.
Update me with the outcome.
|