MB-920 cheat sheet

Supply Chain Management covers sourcing, procurement, production, warehousing, transportation, and asset management in one app; modules include Procurement and sourcing, Product information management, Inventory management, Warehouse management, Master planning, Production control, Transportation management, and Asset management.

Inventory management tracks on-hand quantity by item, site, warehouse, and location; Inventory closing and adjustment settles transactions so that issue transactions are costed against receipts under the configured costing model.

Costing models include FIFO, LIFO, weighted average, moving average, and standard cost; standard cost uses a cost version with planned and fallback cost prices for valuation.

Master planning generates planned orders (purchase, transfer, production) from net requirements; coverage settings (coverage code, lead time, safety stock, min/max) drive the calculation, and planned orders are firmed into real orders.

Warehouse management uses warehouse-specific processes: location directives determine put/get locations, work templates and work headers create picking/put work, and mobile device menu items drive scanning on handhelds.

Procurement and sourcing supports purchase requisitions, RFQ, purchase orders, change management with approval workflows, vendor collaboration, and three-way matching of PO, packing slip, and invoice.

Production control supports discrete, process, and lean manufacturing; bills of materials (BOM), routes, and resources define production, and production orders can be estimated, scheduled, released, started, and reported as finished.

Transportation management defines load building, rate and route engines, carriers, and freight reconciliation; Asset management tracks fixed assets for maintenance with functional locations, maintenance requests, and work orders.

Finance covers general ledger, accounts payable, accounts receivable, fixed assets, budgeting, cash and bank management, cost accounting, and financial reporting.

The chart of accounts is shared across legal entities; main accounts have a main account type (Asset, Liability, Equity, Revenue, Expense) that controls posting behavior and closing rules.

Financial dimensions are backed by dimension values and dimension sets; account structures and advanced rule structures determine which combinations are valid for entry.

The general ledger posts via journals: daily, allocation, periodic (e.g., accrual, depreciation), and reversing journals; posting layers separate current from tax and operations postings.

Accounts payable handles vendor invoices, payment proposals, payment journals, and vendor balances; accounts receivable handles free text invoices, customer payments, collection letters, and credit limits.

Fixed assets are created from asset records, assigned to asset books, and depreciated by running depreciation proposals; acquisitions and disposals post through fixed asset journals.

Budgeting supports budget register entries, budget models, budget control, and budget plans; budget control blocks or warns on postings that exceed available budget.

Financial reporting (formerly Management Reporter) builds row/column/reporting tree definitions for statements such as balance sheet and income statement, sourced from posted ledger balances.

Finance and operations apps share a common platform: Lifecycle Services (LCS), a unified security model, Office integration, Power Platform integration, and a single set of master data patterns.

Security is role-based: users are assigned to roles, roles contain duties, duties contain privileges, and privileges map to entry points or permissions; direct user assignment is an exception path.

Legal entities are the top-level data boundary for transactions; data is shared across legal entities via global address book, products, and chart of accounts where configured.

Workflows use the workflow editor to define approvals per document type; users can delegate approvals, and workflow history is retained on the record.

Lifecycle Services supports project onboarding, environment management (develop, sandbox, production), asset library, business process modeler, and the regression suite automation tool.

Data management uses the Data Management workspace with entities, projects, and recurring integrations; the Data entity framework supports import/export and dual-write with Dataverse.

Personalization and saved views let users change forms and grids without code; extensions (not overlayering) are the supported customization model, and code is deployed via deployable packages.

Power Platform integration enables Power Apps, Power Automate flows, and Power BI to work with finance and operations data through virtual entities, business events, and the data lake export.