MB-330 cheat sheet

Products are of type Item or Service; item number sequences can be configured per product type so service items never consume item numbers.

A product master uses exactly one configuration technology: predefined variants, dimension-based (rule-based) configuration, or constraint-based configuration built from a product configuration model.

Dimension groups split into three types: product dimension group (Configuration, Size, Style, Color) drives variants, storage dimension group (Site, Warehouse, Location, Inventory status) drives inventory, tracking dimension group (Batch, Serial, Owner) drives traceability.

A product or product master must be released to a legal entity before any transaction; releasing a master creates one released product per active variant.

An item model group defines negative inventory behavior (physical and financial), the inventory model (FIFO, LIFO, weighted average, moving average, standard cost), and the ledger posting accounts.

Tracking dimension group serial control options are None, Per unit, and Per quantity; batch number control options are None, Per quantity, and Per unit.

Storage dimension group flags per dimension are Active, Primary stocking, Physical inventory, Financial inventory, and Coverage plan by dimension; the Coverage plan flag lets master planning net requirements at that dimension level.

Product attribute data types are Currency, Date/time, Decimal, Integer, Text, Boolean, and Reference; attributes attach to category hierarchy nodes and support category-based pricing and product search.

Inventory models are Standard cost, Moving average, FIFO, LIFO, and Weighted average; moving average is the default, and weighted average is only calculated during inventory close.

Inventory recalculation revalues on-hand and recalculates issue costs, while inventory close settles issues against receipts; a completed inventory close cannot be reversed.

Counting journals come as Counting (by item), Tag counting, and Counting by warehouse; posting writes adjustment transactions for the counted inventory dimensions.

The reservation hierarchy is a per-dimension setting on storage and tracking dimension groups; dimensions ordered above Location are reserved in aggregate, and only lower dimensions are allocated to a specific location.

Transfer orders require a from-warehouse and a to-warehouse; when a transit warehouse is defined in Inventory and warehouse management parameters, goods in transit are tracked between shipment and receipt.

Inventory status is a storage dimension used to block stock (for example Unavailable or Quarantine) so the quantity stays physically on hand but cannot be reserved, picked, or issued.

The inventory aging report buckets on-hand quantity and value into aging periods defined by an interval and a unit, measured from the receipt date of each on-hand transaction.

Enterprise Asset Management uses functional locations to build the asset hierarchy and asset types to define lifecycle states, maintenance sequences, and attribute requirements; work orders are created from maintenance requests, maintenance plans, or manually.

Vendor invoice matching supports two-way (price) and three-way (quantity against product receipt) matching; the policy resolves from the most specific setup among Accounts payable parameters, vendor, item, and vendor-item.

Trade agreements store price and discount agreements by item, party, unit, currency, and date range; the system searches item-and-account specific agreements before broader ones when an order line is created.

A purchase requisition runs through workflow, and once approved it can be converted into a purchase order or used as the basis for a request for quotation.

Request for quotation replies can be accepted and transferred to create or update purchase orders; sealed bidding hides competing vendor bids until the reply deadline.

Purchase agreements carry a product quantity, product value, product category value, or value commitment, and release orders draw down that commitment over the agreement period.

Credit management blocks sales orders that exceed the customer's credit limit or match a credit hold rule; a held order must be released before it can be confirmed, picked, or invoiced.

Intercompany trading requires a paired intercompany customer and vendor; an intercompany sales order automatically creates the matching purchase order, and direct delivery ships from the selling company's vendor straight to the buyer.

Charges codes define manual or automatic charges with debit and credit types (customer, vendor, ledger); auto charges are applied through module-specific auto charge configurations for sales, purchase, and inventory.

WMS processes apply only when the warehouse has Use warehouse management processes enabled and the item's storage dimension group has Warehouse and Location active.

Location directives match on work order type and work type, then apply a query (site, warehouse, location profile, inventory status) and sequenced lines; the first matching line with sufficient quantity supplies the location.

Location directive line strategies include None, Fixed location, Closest location, FIFO date, LIFO date, and FEFO date.

Wave templates group wave methods such as allocate, replenish, and create work; methods run in the sequence defined on the template, and the template type (shipping, receiving, production, replenishment, cycle counting, kanban) determines available methods.

Work templates define pick and put location types and how work headers and lines break, for example one line per license plate or per item; work classes group work lines for mobile device processing.

Cycle counting in WMS uses cycle count plans that hold thresholds such as percent of maximum quantity; the cycle count scheduling batch job generates counting work from these plans.

Transportation management rating uses a rate master that combines a rate base, break master limits, and rate engine data; the transit time engine returns delivery dates and the mileage engine calculates distances between hubs.

Load planning workbench builds loads from sales, transfer, and purchase orders using load templates that cap weight, volume, and line count; loads can be tendered to a carrier and used for dock appointment scheduling, and freight bills support carrier invoice reconciliation.

Coverage codes: Manual (no automatic planning), Requirement (plans only existing demand), Period (coverage period plus negative days), and Min/Max (replenish to maximum when projected inventory falls below minimum).

A static master plan works from a snapshot of data that must be refreshed, while a dynamic master plan always uses live data; both are bounded by the planning horizon set on the master plan.

Item lead times used in planning are purchase lead time, production lead time, and transfer lead time from Default order settings; planned order dates are offset by the lead time of the relevant order type.

The item's default order type (Production, Purchase, Transfer, or Kanban) together with coverage determines whether master planning creates a planned production, planned purchase, planned transfer order, or kanban.

Planned orders become real orders by firming; firming can be done manually on the planned orders page, by a batch firming job, or automatically when auto-firm is enabled on coverage settings within the firming time fence.

Action messages are Advance, Postpone, Increase, and Decrease; they advise changing the date or quantity of an existing open order so it matches recalculated net requirements.

Forecast demand enters master planning through a forecast plan assigned to the master plan, and forecast reduction consumes forecast with actual sales orders according to the reduction principle and time buckets.

Coverage quantity fields are Minimum, Maximum, Multiple, and Standard order quantity; under Min/Max coverage the minimum triggers replenishment and the maximum is the level replenished to, and the safety stock journal updates the minimum quantity.

Negative days allow requirements earlier than today to be moved to today, positive days extend the window in which supply can be netted against demand, and both are set on item coverage.

Products are of type Item or Service; item number sequences can be configured per product type so service items never consume item numbers.

A product master uses exactly one configuration technology: predefined variants, dimension-based (rule-based) configuration, or constraint-based configuration built from a product configuration model.

Dimension groups split into three types: product dimension group (Configuration, Size, Style, Color) drives variants, storage dimension group (Site, Warehouse, Location, Inventory status) drives inventory, tracking dimension group (Batch, Serial, Owner) drives traceability.

A product or product master must be released to a legal entity before any transaction; releasing a master creates one released product per active variant.

An item model group defines negative inventory behavior (physical and financial), the inventory model (FIFO, LIFO, weighted average, moving average, standard cost), and the ledger posting accounts.

Tracking dimension group serial control options are None, Per unit, and Per quantity; batch number control options are None, Per quantity, and Per unit.

Storage dimension group flags per dimension are Active, Primary stocking, Physical inventory, Financial inventory, and Coverage plan by dimension; the Coverage plan flag lets master planning net requirements at that dimension level.

Product attribute data types are Currency, Date/time, Decimal, Integer, Text, Boolean, and Reference; attributes attach to category hierarchy nodes and support category-based pricing and product search.