Error messages on EBS Forms

1. "XXXX is not a valid responsibility for the current user. Please contact your System Administrator."

- First possibility is that this responsibility has an End date for this user. Check user's account.

- After adding a responsibility to a user, the user may receive above message. And the attached responsibility may not appear in the Home Page until the Apache is bounced.

One solution could be to clear the cache:
Navigate to Functional administrator > Core Service > Caching Framework > Global Configuration > Clear All Cache

Another place to check:
Search for profile 'Applications Start Page'. Delete the value set at user level (if any).

Also make sure Workflow Service Components are up and running (OAM -> Workflow Manager (dropdown) -> Service Components):
   . Workflow Deferred Agent Listener
   . Workflow Java Deferred Agent Listener

2. "Function not available to this responsibility. Change responsibilities or contact System Administrator"

- If it is on a custom form, make sure its path CUSTOM_TOP is added to $INST_TOP/ora/10.1.2/forms/server/default.env file.

- Use submenu item Help --> Diagnostics --> Examine.  Then, click the "Examine Fields and variable values" to troubleshoot. Reference Doc ID 1079951.1.

- If this message shows in R12.1.3 while trying to access Help --> Diagnostics, change the profile "Utilities:Diagnostics" to Yes at user or responsibility level. Please see Doc ID 1200743.1.

3.  If  R12.1 "adformsctl.sh start" gets error, check logs:

$LOG_HOME/ora/10.1.3/j2ee/forms/forms_default_group_1/application.log
$LOG_HOME/ora/10.1.3/j2ee/oacore/oacore_default_group_1/application.log

When the Form service is starting, it checks whether latest formsapp.ear is deployed. If it finds a newer version, Form service will take longer to start and say message:
==========================================
*** Latest formsapp.ear has NOT been deployed ***
Deploying the latest EAR file...
==========================================
See DocID 1210660.1 (Forms Startup Script adformsctl.sh Shows Deployment Message While Starting Forms Services).

4.  How to deploy Forms EAR (Enterprise ARchive) file, such as formsapp.ear (under $ORACLE_HOME/forms/j2ee) ?

DocID 397174.1 (Deploying a New EAR File in Oracle Applications Release 12) gives two key steps:
1) Edit file (with a temp password) - $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
2) Run deployment - $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp
    (if all work, it shall say "No error encountered." at the end)

DocID 1945012.1 also gives a way to manually deploy formsapp.ear (for Oracle Forms ?? vs Oracle EBS R12). But I never try it:
$ dcmctl redeployApplication -f $ORACLE_HOME/forms/j2ee/formsapp.ear -a formsapp -co OC4J_BI_Forms