Workflow information can be found in the wf_item_types_tl table.
It will give the long name and the short name for all workflows.
Login to Test Instance, Set the Environment
WFLOAD apps/apps 0 Y DOWNLOAD reqappv_final.wft REQAPPRV
WFLOAD apps/apps 0 Y DOWNLOAD poapprv_final.wft POAPPRV
Copy or Ftp the files created to the production database server.
Execute the following to backup original on production:
WFLOAD apps/apps 0 Y DOWNLOAD reqappv_prod.wft REQAPPRV
WFLOAD apps/apps 0 Y DOWNLOAD poapprv_prod.wft POAPPRV
WFLOAD apps/apps 0 Y UPGRADE reqappv_final.wft
WFLOAD apps/apps 0 Y UPGRADE poapprv_final.wft
This will upload the wft file - into the database - for the new instance.
Another way is to use the workflow builder.
1. Pull up the workflow from test in the workflow builder.
2. Then choose File/Save As - and enter the production database information and save.
3. You have now saved the workflow into the production database.
Java Web Start provides a browser-independent architecture.. No dependency on Browser make or version for launching forms in EBS. Java a...
Adop phases 1) prepare - Starts a new patching cycle. Usage: adop phase=prepare 2) Apply - Used to apply a patch to the ...
In a multi-node environment, we have seen issues where one of the nodes gets abandoned due to few issues. Main cause is -- One of the ...
Below Pre-upgrade steps on 12.2 servers can be done well in advance before the actual upgrade downtime. Pre-upgrade Steps on 12.2 =========...