technology Online Quiz - 1794

Cognos Planning Contributor is designed specifically for collaborative planning and budgeting. It supports both top-down budgeting (where management sets targets that cascade down) and bottom-up forecasting (where individual units build up projections). Metric Designer is for KPI definitions, Datamanager is for ETL, and TM1 is for specialized financial modeling.

Event Studio is designed for event-driven notifications and actions in Cognos. When a condition is met (like product returns exceeding 10), it can automatically send emails and run reports to specified recipients. Metric Studio tracks KPIs over time but isn't designed for conditional event-based alerts with actions.

PowerPlay Transformer is the Cognos tool specifically designed for creating OLAP cubes. It takes dimensional models and data sources to build cube files (.mdc) optimized for multidimensional analysis. Framework Manager builds metadata models, Cognos Architect doesn't exist as a cube creation tool, and Datamanager is for ETL processes.

The Cognos Connection Administration Page allows administrators to configure and tune server settings, including the number of processes that run per CPU. This is done through server configuration properties in the administration interface. Cognos Configuration is for initial setup, Framework Manager is for metadata modeling, and Map Manager doesn't handle server tuning.

Metric Studio is the IBM Cognos component specifically designed for creating scorecards and monitoring KPIs over time. It provides the framework for defining metrics, setting thresholds, and visualizing performance trends. Cognos Planning is for budgeting and forecasting, TM1 is for multidimensional analysis, and Analysis Studio is for ad-hoc data exploration.

Before accounting document creation, billing date can be modified, account determination can be changed, and output determination parameters can be adjusted. Partner functions and shipping points are inherited from earlier stages and cannot be changed.

Pricing type updates are configured in the Pricing Procedure and controlled via Copying Control during document flow. The procedure defines calculation logic and copying rules govern type updates during document transfer.

The item category determines whether BOM explosion occurs and how deep the structure expands. Different item categories have different BOM explosion settings configured in the item category determination.

When sales area is not specified during sales order entry, the system derives it from the customer master record of the sold-to party. The customer master contains the sales area assignment.

SAP SD handles outgoing deliveries to customers (outbound logistics). SAP MM handles incoming deliveries from vendors (inbound logistics). This module separation reflects the sales vs. procurement business functions.

Item category configuration controls whether Incoterms can differ between header and item level. This validation setting is defined at the item category level, not in copying control or document type.

Availability check uses the plant as the organizational basis. Stock and requirements are checked at the plant level, making plant the foundation for Available-to-Promise (ATP) logic.

During sales order creation, the system checks the ship-to party partner function in customer master to determine the supplying plant. The ship-to party's master data contains the plant assignment for delivery logic.

For successful order combination in SAP SD outbound deliveries, items must share key characteristics: Incoterms define delivery terms and responsibilities, shipping dates ensure synchronized processing, shipping points determine logistical compatibility, partner functions maintain consistent business relationships, and routes specify transportation paths. All five criteria must align for the system to combine items from different sales orders into one delivery.

Delivery scheduling and goods issue date checks are performed at the Ship-to party level because that's where the delivery location and transportation calendar are maintained. The Ship-to party's master data contains the specific unloading point, transportation zone, and delivery calendar that determine whether delivery is accepted on a particular day and time. The Sold-to, Payer, and Bill-to partners don't control these logistics parameters.

In SAP SD mandatory reference configuration, valid reference documents for sales orders include Sales orders (for returns or subsequent orders), Inquiries (converted to orders), Quotations (accepted quotations), and Billing documents (for returns or corrections). Delivery documents cannot serve as mandatory references for sales order creation - the relationship flows the other way (sales order → delivery). The mandatory reference setting prevents document creation without a preceding document in the sales cycle.

When SAP creates an accounting document from billing, all five posting types appear: Accruals (for deferred revenue or costs), Cash Clearing (payment card or cash sale processing), Sales Deductions (rebates, discounts, allowances), Output Tax (tax liability posting), and Sales Revenue (the main revenue posting). These represent the complete financial picture of the business transaction flowing from SD to FI.

Payment card configuration in SAP allows viewing card details in customer master change mode for authorized access, and you can control multiple payment cards per transaction through customization. Payment card plans are assigned at item level only, not header. Card types are assigned to sales document types, not all types. Authorization comes from the payment card provider (acquirer), not the merchant's house bank which only receives settlement.

For monthly billing agreements, SAP uses factory calendar configuration at the customer master level (where billing calendars are maintained) combined with special rules in the factory calendar for individual billing dates. Material master, customer-material info records, and sales organization don't control customer-level billing schedules. The factory calendar in customer master defines when billing can occur, and special rules set specific monthly billing dates.