eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: APPLSYS.FND_LOBS

Object Details

Object Name:	FND_LOBS
Object Type:	TABLE
Owner:	APPLSYS
FND Design Data:	FND.FND_LOBS
Subobject Name:
Status:	VALID

FND_LOBS stores information about all LOBs managed by the Generic File Manager (GFM).
Each row includes the file identifier, name, content-type, and actual data. Each row also
includes the dates the file was uploaded and will expire, the associated program name and
tag, and the language and Oracle characterset.
.
The file data, which is a binary LOB, is stored exactly as it is uploaded from a client browser,
which means that no translation work is required during a download to make it HTTP compliant.
Therefore uploads from non-browser sources will have to prepare the contents
appropriately (for instance, separating lines with CRLF).
.
The program_name and program_tag may be used by clients of the GFM for any purpose,
such as striping, partitioning, or purging the table if the program is de-installed.
They are otherwise strictly informative.
These columns and the expiration date are properly set when the
procedure FND_GFM.CONFIRM_UPLOAD is called. If not called, the column
expiration_date remains set, and will eventually be purged by the procedure
FND_GFM.PURGE_EXPIRED.
.

Storage Details

Tablespace:	APPS_TS_MEDIA
PCT Free:	10
PCT Used:

Primary Key: SYS_C0036531

FILE_ID

Indexes

Index	Type	Uniqueness	Tablespace	Column
FND_LOBS_U1	NORMAL	UNIQUE	APPS_TS_MEDIA	FILE_ID
SYS_IL0000034032C00004$$	LOB	UNIQUE	APPS_TS_MEDIA
FND_LOBS_CTX	DOMAIN	NONUNIQUE		FILE_DATA
FND_LOBS_N1	NORMAL	NONUNIQUE	APPS_TS_MEDIA	EXPIRATION_DATE PROGRAM_NAME PROGRAM_TAG

Columns

Name	Datatype	Length	Mandatory	Comments
FILE_ID	NUMBER		Yes	Identifier that uniquely identifies the file
FILE_NAME	VARCHAR2	(256)		User's name for the file as provided during the uploading process
FILE_CONTENT_TYPE	VARCHAR2	(256)	Yes	Content type as specified during the uploading process. This string is an unparsed entity-header for the entity "Content-Type", and specifies the content type, and any additional parameters (such as character set) that describe the stored contents.
FILE_DATA	BLOB	(4000)		The uploaded data itself, which is a binary LOB
UPLOAD_DATE	DATE			Timestamp at which the LOB was uploaded
EXPIRATION_DATE	DATE			Timestamp after which the LOB may be purged from the table. When the LOB is first uploaded, this is set to be one day from the current time.
PROGRAM_NAME	VARCHAR2	(32)		Name of the program on whose behalf the LOB is being maintained.
PROGRAM_TAG	VARCHAR2	(32)		Optional string used by the GFM client program to further categorize the LOB.
LANGUAGE	VARCHAR2	(4)		Language of file
ORACLE_CHARSET	VARCHAR2	(30)		Oracle character set of file
FILE_FORMAT	VARCHAR2	(10)	Yes	File format ('text' or 'binary')

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT FILE_ID
,      FILE_NAME
,      FILE_CONTENT_TYPE
,      FILE_DATA
,      UPLOAD_DATE
,      EXPIRATION_DATE
,      PROGRAM_NAME
,      PROGRAM_TAG
,      LANGUAGE
,      ORACLE_CHARSET
,      FILE_FORMAT
FROM APPLSYS.FND_LOBS;

Dependencies

[top of page]

APPLSYS.FND_LOBS does not reference any database object

APPLSYS.FND_LOBS is referenced by following:

APPS: FND_LOBS