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.

APPS.FND_DOCUMENT_MANAGEMENT dependencies on STANDARD

Line 542: standard URL syntax to allow for extra url links/icons that

538: The challenge here is to return the DM system id, the
539: document id, and the document name for the document that
540: you've selected during your search process. We'll likely
541: need our DM software partners to add new arguments to their
542: standard URL syntax to allow for extra url links/icons that
543: refer to Oracle Application functions that will allow us to
544: return the selected documents that you wish to attach to your
545: application business objects. The extra arguments would be
546: pushed into the standard HTML templates so you can execute

Line 546: pushed into the standard HTML templates so you can execute

542: standard URL syntax to allow for extra url links/icons that
543: refer to Oracle Application functions that will allow us to
544: return the selected documents that you wish to attach to your
545: application business objects. The extra arguments would be
546: pushed into the standard HTML templates so you can execute
547: these functions when you've selected the appropriate document.
548:
549: ============================================================================*/
550: PROCEDURE get_search_document_url

Line 687: partners to add new arguments to their standard URL

683: system by clicking on the Create New link. Once you provide
684: all the meta data for that document in the DM system we'll
685: need to push the document information back to the creating
686: application object. We'll likely need our DM software
687: partners to add new arguments to their standard URL
688: syntax to allow for extra url links/icons that refer to
689: Oracle Application functions that will allow us to return
690: the selected document id information once you've created
691: your document. The extra arguments would be pushed into

Line 692: the standard HTML templates so you can execute these

688: syntax to allow for extra url links/icons that refer to
689: Oracle Application functions that will allow us to return
690: the selected document id information once you've created
691: your document. The extra arguments would be pushed into
692: the standard HTML templates so you can execute these
693: functions when you've selected the created the document.
694:
695: ============================================================================*/
696: PROCEDURE get_create_document_url

Line 885: partners to add new arguments to their standard URL

881: browse feature. Once you select a document in the DM
882: system we'll need to push the document information
883: back to the creating application object. We'll likely
884: need our DM software
885: partners to add new arguments to their standard URL
886: syntax to allow for extra url links/icons that refer to
887: Oracle Application functions that will allow us to return
888: the selected document id information once you've created
889: your document. The extra arguments would be pushed into

Line 890: the standard HTML templates so you can execute these

886: syntax to allow for extra url links/icons that refer to
887: Oracle Application functions that will allow us to return
888: the selected document id information once you've created
889: your document. The extra arguments would be pushed into
890: the standard HTML templates so you can execute these
891: functions when you've selected the created the document.
892:
893: ============================================================================*/
894: PROCEDURE get_browse_document_url

Line 4653:
The standard Release 10.7 product provides NLS support. Supported

4649: than a single language on a single database instance.
4650:

4651:
Release 10.7
4652:

4653:
The standard Release 10.7 product provides NLS support. Supported
4654: functionality consists of installing and running Release 10.7 in exactly
4655: one (1) of 25 national languages.
4656:

4657:
The installation process for a translation installs both the US English

Line 4691: Korean standard character set and run both that language and English in

4687: other than Unicode (UTF-8). For example, all Western European languages
4688: can be supported with the WE8ISO8859P1 date character set, but this character
4689: set does not support Greek or Russian. Asian character sets support
4690: ASCII as a subset, so it is possible to choose the Japanese, Chinese, or
4691: Korean standard character set and run both that language and English in
4692: a single instance. But it is not possible to run, say, both Japanese
4693: and Korean in a single character set.
4694:

4695:
Data modeled multilingually in Release 11.0 is limited to the AOL tables.