MB-920 flashcards
MB-920 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Master planning purpose
- Calculates net requirements from demand and supply, then generates planned purchase, transfer, and production orders. Coverage settings, lead times, and safety stock determine timing and quantity of those planned orders.
- Planned order firming
- A planned order is a suggestion, not a transaction. Firming converts it into a purchase order, production order, or transfer order so it can be confirmed, processed, and posted.
- Location directive
- A warehouse management rule that determines where work should put or pick inventory. It evaluates directive sequences against query conditions such as item, warehouse, and location profile.
- Warehouse work templates
- Templates define the pick and put steps for a work order type, including the work class and location. Work headers and lines are generated from them when work is created.
- Inventory closing
- A periodic process that settles inventory transactions so issues are costed against receipts under the item's costing model. It can be run as a simulation before final posting.
- Standard cost valuation
- Inventory and production are valued at a fixed cost from an activated cost version. Variances between standard and actual are posted separately rather than changing on-hand value.
- Three-way match
- Accounts payable policy that compares purchase order, product receipt, and vendor invoice quantities and prices before an invoice is approved for payment.
- Production order lifecycle
- Created, estimated, scheduled, released, started, and reported as finished. Each step updates status and enables journal posting for materials, labor, and output.
- BOM and route
- A bill of materials lists components and quantities needed to build an item. A route lists the operations, resources, and times required, and both feed production estimation and scheduling.
- Asset management work order
- Schedules maintenance work on an asset at a functional location. It carries tasks, spare parts, and resources, and can originate from a maintenance request or preventive maintenance plan.
- Main account types
- Asset, Liability, Equity, Revenue, and Expense. The type controls posting behavior, balance reporting, and whether the account closes into retained earnings at year end.
- Financial dimensions
- User-defined segments such as department or cost center attached to accounts. Account structures and advanced rules determine which dimension combinations are valid for posting.
- Account structure
- Defines the valid main account and dimension combinations for a chart of accounts. It is assigned to a ledger and controls data entry validation during journal posting.
- Posting layers
- Separate sets of ledger postings, typically Current, Tax, and Operations. Transactions post to layers, and financial statements can report on a selected layer.
- Budget control
- Checks source documents against available budget funds before posting. It can be configured to warn or block when a posting would exceed the remaining budget amount.
- Budget register entry
- The record used to enter, adjust, or transfer budget amounts against budget models and dimension combinations. Approved entries become the basis for budget control.
- Fixed asset book
- A configuration that holds depreciation rules, service life, and posting profiles for an asset. One asset can have multiple books, such as a tax book and a financial book.
- Depreciation proposal
- A batch process that calculates depreciation for a period and creates a journal. The journal must be reviewed and posted before ledger balances reflect the depreciation.
- Payment proposal
- A process that selects vendor invoices due for payment based on criteria such as due date and payment method, then generates a payment journal for review and posting.
- Collection letter
- A sequenced document sent to customers with overdue balances. Sequences define the aging thresholds, fees, and text used at each escalation step.
- Financial reporting definitions
- Reports are built from row definitions, column definitions, and reporting trees. Trees roll up dimension values such as cost centers into organizational summaries.
- Fiscal calendar
- Defines the fiscal year, periods, and closing periods used by the ledger. It controls period status and whether postings are allowed into a given period.
- Intercompany accounting
- Posts transactions between legal entities in one voucher using due-to and due-from accounts. It requires configured intercompany relationships and matching accounts.
- Legal entity boundary
- A legal entity is a separate organization with its own ledger, chart of accounts assignment, and tax registration. Transactions and balances are isolated per legal entity.
- Role-based security model
- Users receive roles; roles contain duties; duties contain privileges; privileges grant permissions to entry points and data. This hierarchy replaces assigning permissions directly to users.
- Duty versus privilege
- A privilege grants access to specific entry points or data. A duty groups related privileges into a business task, and roles group duties into a job function.
- Lifecycle Services
- The cloud portal for implementation projects: environment management, asset library, business process modeler, and deployment services. It also hosts the regression suite automation tool.
- Data management workspace
- Used to create import and export projects from data entities. Supports recurring integrations, staging validation, and moving data between environments.
- Dual-write
- Near-real-time synchronization between finance and operations apps and Dataverse. It maps tables on both sides so records stay consistent across Power Platform and finance data.
- Extensions not overlayering
- Customizations are built as extensions that add to existing objects without changing base code. Overlayering is deprecated because it blocks continuous updates.
- Business events
- A mechanism that sends notifications to external endpoints such as Power Automate or Azure when a business action occurs, enabling integration without polling the database.
- Workflow delegation
- A user can assign approval authority to another user for a period. Delegated approvers act on workflow tasks while history records the original and delegate.