To pass SYSDATE when you upload a DFF using FNDLOAD

The dates or rather the entire RowWho information will be passed in from Source System, i.e. whatever is in the ldt file.
Open the lct file by doing
vi $FND_TOP/patch/115/import/afffload.lct
search for string fnd_flex_loader_apis.up_desc_flex
In the parameter last_update_date you can pass sysdate, replacing the value read from ldt file

Versions of Oracle EBS Components

It is pretty coolest thing to remember, the VERSIONS: :)

Whenever you are working in oracle applications you will face some situation where you have to know the version of the products you are using in your Oracle Application. Though the env file help you a lot to reduce the need of the versions as it makes the system user friendly. In some issue solving cases such as upgrade, patching or some specific issues you must have to know the versions.The products we are using can be of almost three types
1. Components related to Application
2. Components related to Database.
3. Components related to some useful utilities and OS
Components related to Application:
a. The version of the oracle application.
Step 1. First open the Oracle Application Frontend
Step 2. Open any form session in it
Step 3. Go to help
Step 4. Click on "About Oracle Application"

b. Version of Oracle Application Forms or Reports.
Step 1. Go to the UNIX box
Step 2. Go to the $CUSTOM_TOP location
Step 3. Then go to /11.5.0/forms/US/
Step 4. Run the following command
$strings -a grep Header
Step 1. Go to the UNIX box
Step 2. Go to the report location
Step 3. Run the following command
$strings -a grep Header
c. Class file version
Step 1. Go to the UNIX box
Step 2. Go to the class file location
$strings -a grep Header
d. Apachhe Version
Step 1. Go to the UNIX box
Step 2. Go to the $iAS or $IAS_CONFIG_HOME
Step 3. Then go to Apachhe/Apache/bin directory
Step 4. run the following Command
$httpd -version
The output will be
$ httpd -version
Server: Oracle HTTP Server Powered by Apache/1.3.19 (Unix)Server built: Jan 26 2005 11:06:44 (iAS 1.0.2.2.2 rollup 5)
e. OA Framework Version
Step 1. Open the following URLhttp://.:/OA_HTML/OAInfo.jsp

The page will show like the following
OA Framework Version Information
OA Framework Version 11.5.10.4
RUP. MDS Version 9.0.5.4.89 (build 555)
UIX Version 2.2.24
BC4J Version 9.0.3.13.93
Generated on Wed Dec 10 20:06:25 GMT+05:00 2008

f. Patch Level or Patch Version
It is the most genegal requirement in oracle apps. It can be found from the following query in sqlplus
select patch_level from fnd_product_installations where patch_level like '%AD%';
The output will be
PATCH_LEVEL
------------
11i.AD.I.4
g. Workflow VersionIt is one of the most genegal requirement in oracle apps.
It can be found from the following query in sqlplus
select text Workflow_version from wf_resources where type = 'WFTKN' and name= 'WF_VERSION';
The output will be
WORKFLOW_VERSION
-----------------
2.6.0h.
XML Publisher Version
Step 1. Go to the UNIX box
Step 2. Go to the $OA_JAVAor JAVA top
Step 3. Then go to oracle/apps/xdo/common directory
Step 4. Open the MetaInfo.classComponents Of oracle Database:
a. Oracle RDBMS VersionRun the following query
select * from v$version;
The output will be
BANNER
----------------------------------------------------------------
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
PL/SQL Release 9.2.0.6.0 - ProductionCORE 9.2.0.6.0
ProductionTNS for Solaris: Version 9.2.0.6.0 - Production
NLSRTL Version 9.2.0.6.0 - Production

b. OPATCH version
Step 1. Go to the UNIX box
Step 2. Go to the $ORACLE_HOME
Step 3. Then go to OPatch/ directory
Step 4. run the following Command
$ perl opatch.pl version
Oracle Interim Patch Installer version 1.0.0.0.52Copyright (c) 2005 Oracle Corporation. All Rights Reserved..

We recommend you refer to the OPatch documentation underOPatch/docs for usage reference. We also recommend using the latest OPatch version. For the latest OPatch versionand other support related issues,
please refer to document293369.1
which is viewable from metalink.oracle.com
OPatch Version: 1.0.0.0.52

:bad interpreter: No such file or directory /bin/sh

When you attempt to launch the installation of oracle EBIZ using ./rapidwiz from stage, you may be experiencing the issue

: bad interpreter : no such file or directory,

Here is the fix:
This error pops up for a couple of reasons. At the top of the script there will probably be a line that looks like this:
#!/bin/sh

This is telling Linux that this script should be interpreted using the /bin/sh program. So your first step is to verify that program exists. I tend to use:
which shThis will typically come back with a response like this:
/bin/sh

This is telling us that the path to the sh program is in fact /bin/sh, matching the path specified at the top of the script. Ok,

It's possible that this script was made on an operating system that has line ending characters different than linux. This could have been on on a Mac or PC, or the file could have been converted when it was packaged. In this case, you get the relatively misleading bad interpreter: No such file or directory message, which is really trying to look for sh, although you don't get any indication of the fact. So,

how to fix? Read on.

There are various ways to fix the problem, but I find one of the simplest being the use of vi which is standard on most unix systems, and in linux comes in the form of the vim package. Load the script up in vim, by typing vi filenamevi is a text based dinosaur in the day of wysiwyg editors, so if you don't know your way around, make sure you follow these steps carefully.Once the file is loaded type:

:set fileformat=unix

And hit Enter/Return.You won't notice anything, but the file has already been fixed. Now all you need to do is save and exit.
:wq!
Again Return, and you should be back in your shell. Run the shell script, and if all goes well, it should now execute properly, and without the dreaded bad interpreter: No such file or directory message.