Results for “word_processor_path”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view AS_WORD_PROCESSORS_ACTIVE_V is a reporting and integration object within the Oracle E-Business Suite Sales Foundation (AS) product family. Its documented description is the "Active word processors view," and it exists to expose only those word processor definitions that have been enabled for use by the application. In Oracle EBS, letter and document generation for sales-related activities relies on word processor configurations — typically installations of Microsoft Word — that are registered and maintained in the application. The base table AS_WORD_PROCESSORS stores all such configurations, including both active and disabled entries, while this view filters that superset down to a single enabled population.

The view is documented in ETRM for release 12.2.2 as having no documented owner and no documented referenced base objects, though its view text clearly derives from AS_WORD_PROCESSORS. The ETRM implementation note also records that the object was not implemented in the specific database instance documented. The view's role is primarily reporting: it allows concurrent programs, forms, and custom queries to identify which word processor definitions are available without embedding the ENABLED_FLAG = 'Y' predicate in every call site.

Underlying Base Objects

The view is defined over a single base table, AS_WORD_PROCESSORS. The defining query selects the columns WORD_PROCESSOR_ID, NAME, DESCRIPTION, PATH, STARTUP_COMMAND, LETTER_LOCATION_PATH, and WORD_PROCESSOR_NAME from that table, with the filter predicate WHERE ENABLED_FLAG = 'Y'. There is no join, no aggregation, and no union: the view is a simple projection and restriction of the base table. Consequently, the row count of the view is always less than or equal to the row count of AS_WORD_PROCESSORS, and every row in the view corresponds one-to-one with an enabled row in the base table. No lifecycle transformations occur — the view is read-only in practice, and all maintenance (insert, update, disable) is performed against the underlying table, typically through the Sales Foundation setup forms. Because the filter is fixed at the view layer, the view cannot surface historical or disabled configurations.

Key Columns

• WORD_PROCESSOR_ID — the primary identifier of the word processor registration; used as the foreign key in downstream letter and document generation logic.
• NAME — the user-facing name of the word processor definition as displayed in setup and selection lists.
• DESCRIPTION — free-text description of the word processor record, used for administrative clarity.
• WORD_PROCESSOR_PATH (selected as PATH) — the operating-system path to the word processor executable or installation.
• WORD_PROCESSOR_STARTUP_COMMAND (selected as STARTUP_COMMAND) — the command line used to invoke the word processor, potentially including switches or parameters.
• LETTER_LOCATION_PATH — the directory path where generated letters and document templates are stored or retrieved.
• WORD_PROCESSOR_NAME — the internal or application-level name associated with the word processor.

These columns are effectively read-through aliases of their base table counterparts; no expressions or derivations are applied.

Common Use Cases and Queries

A typical use case is validation during letter generation or setup review, where an administrator or concurrent program must confirm that at least one active word processor exists and identify its configured paths. The following query lists all active word processors in a concise form:

SELECT word_processor_id, name, word_processor_path, word_processor_startup_command FROM as_word_processors_active_v ORDER BY name;

A second scenario checks whether any active word processor points at a specific executable or installation, which is useful when migrating client configurations or auditing Office version dependency:

SELECT name, word_processor_path, word_processor_name FROM as_word_processors_active_v WHERE word_processor_path LIKE '%WINWORD%';

A third scenario verifies letter storage configuration across active entries, ensuring that letter_location_path is populated consistently before document generation is enabled.

SELECT name, letter_location_path FROM as_word_processors_active_v WHERE letter_location_path IS NULL;

Because the view is documented as not implemented in the reference database, deployments should verify its existence in the target instance before relying on it in custom reports or integrations.