packaged enterprise solutions Online Quiz - 27

The Progs table in TLM monitors server status and tracks which servers are running. This table is checked to verify server availability before processing.

In TLM, RELEASE moves items from Outstanding to History status. This action indicates the item has been processed and is no longer outstanding, becoming part of the historical record.

An Agent Bank (or correspondent bank) acts as the custodian that holds the Nostro account on behalf of the customer bank. Therefore, the Nostro account is indeed held at the agent bank.

A Nostro account (derived from the Latin word for 'ours') is an account that a bank holds in a foreign currency at another, usually foreign, bank, allowing for international transactions.

In SmartStream TLM, the RECALL action moves transactions back from the History table into the Outstanding table so they can be reprocessed or matched, reversing the archiving process.

In SmartStream TLM (Transaction Lifecycle Management), Search Rules are specifically used to query and display targeted transaction data on user dashboards, whereas Scope, Population, and Pass Quality rules govern matching and data preparation.

This appears to be about Business Data Repository (BDR) rules in a specific system. The term 'Scope Rule' likely refers to a rule controlling data retrieval scope, though this is not standard terminology in mainstream database or software architecture literature.

In TLM (Transaction Lifecycle Management) systems, sets configured represent accounts while message feeds represent sub-accounts. This hierarchical structure allows for organizing transactions and messages within the account-sub account framework.

Trade settlement in India follows a T+1 cycle, meaning settlement occurs on the next business day after the trade. India shifted from T+2 to T+1 settlement in 2021 to align with global market standards and reduce counterparty risk.

In TLM (Transaction Lifecycle Management) systems, dashboards provide a graphical visualization of items stored in the database. While views allow data examination, the term specifically referring to a graphical display window is dashboards.

In TLM and knowledge management systems, KB stands for Knowledge Base - a centralized repository of information, data, and knowledge used for storage, organization, and retrieval of expertise.

Nostro reconciliation is the process of reconciling cash balances between a bank's internal ledger and the account statement provided by its foreign correspondent bank (the Nostro account), classifying it as Cash Reconciliation.

BEx Web Analyzer is a flexible SAP Business Explorer tool. It can be accessed as a standalone web application via URL, integrated as an iView within SAP Portal, and allows saving data views after ad-hoc analysis. Therefore all three statements A, B, and C are correct, making D the right choice.

Currency translations in SAP BW can be implemented at multiple points: during Query Definition (setting translation rules in the query itself), at Query Runtime (executing translation during query execution), and in Transformation rules (converting currencies during data loading). Infopackages are for data loading and don't handle currency translation logic.

Exception Cells in SAP BW queries require two structures: one in the rows and one in the columns. Exception cells are defined at the intersection of these structures. A single structure or no structures are insufficient - the intersection point is necessary for exception cell definition.

A restricted key figure is a basic key figure filtered by one or more characteristic values (e.g., Revenue restricted to Country='USA'). It is NOT defined by formulas (A) - that would be a calculated key figure. Hierarchy display (C) is unrelated. B correctly captures the core concept.

Calculated key figures can be defined at the InfoProvider level (A, reusable across queries) or locally within a specific query (C, query-specific). They are NOT stored in the PSA (B) - PSA is for transaction data storage. Query-level calculations are local to that query and cannot be reused elsewhere (D is false).

In SAP BW Integrated Planning, the valid InfoProvider types are InfoCubes (A) and MultiProviders (C) which aggregate data for planning. DSOs (B) and InfoSets (D) are NOT supported as planning providers - DSOs are for data staging and InfoSets for join-based reporting.

In SAP BW, aggregates (pre-summarized data structures for performance) can ONLY be created for InfoCubes (D). MultiProviders (A) are logical views that cannot have aggregates. Virtual Providers (B) provide real-time access and don't support aggregates. DSOs (C) are for data staging, not reporting aggregates.