MB-335 cheat sheet

Product masters define the variant dimensions (configuration technologies: product dimensions, predefined variants, or a constraint-based configurator); released products are the company-specific items that carry site/warehouse and item model group defaults.

Product dimension groups control storage (site, warehouse, location, pallet) versus product dimensions (configuration, size, style, color); only dimensions enabled in the group can be used on a released product and its variants.

A released product variant is created by combining configuration, size, style, and color values; a variant can only be released if all mandatory product dimensions are assigned.

When creating a product master, set the variant naming and whether the configuration dimension is active; disabling configuration prevents variant creation for that master.

Product lifecycle states (planned, active, inactive, archived) gate transactions: inactive items cannot be used on new sales or purchase order lines unless the item model group allows it.

Use product attributes and attribute types to capture descriptive data; attributes can be marked for use in the configurator or in category-based pricing.

Category hierarchies drive procurement and sales category policies; assign a released product to a procurement category to enable category-based vendor rules and purchase agreements.

Unit conversion must be defined per released product (or globally) before inventory transactions; base unit is fixed after transactions exist, so choose it before releasing.

A bill of materials (BOM) is versioned; each BOM version has from/to dates and an active flag, and explosion selects the version valid on the calculation date.

BOM lines specify component, quantity, unit, scrap, and line type (item, phantom, pegged supply, vendor); phantom lines explode through the child BOM without creating a separate production order.

Route operations define the sequence of work; resources are either resources, resource groups, or capabilities, and each operation references a resource requirement.

A route version is versioned like a BOM; the default route is selected by the active version and the order date.

Production prerequisites include configured calendars for resources, capacity settings (capacity, efficiency, queue/batch times), and cost categories for routing operations.

Costing prerequisites: item cost price and cost group for components, and cost categories for route operations, drive the calculated production cost.

Inventory dimensions (site, warehouse, location) must be configured and coverage settings defined before production orders can reserve or generate component demand.

Default production order settings (production group, ledger posting profiles, and inventory model group) come from the released product and its item model group.

Production types: discrete (BOM + route), process (formula + route with co-products/by-products), lean (kanban), and project production; the type is set by the production control parameters and the item's production type.

Discrete production uses a BOM version and route version; process manufacturing uses formula versions with co-products and by-products and supports batch orders.

Kanban rules implement lean: production kanban, withdrawal kanban, and event kanban; kanban rules define replenishment strategy and trigger events.

Phantom BOM lines are exploded at estimation; pegged supply lines create direct links to sub-production orders instead of inventory transactions.

Scrap is defined on BOM lines (constant or variable) and on route operations; scrap increases component consumption and operation time.

Route operation time is calculated from process time, setup time, queue time, transfer time, and run time per quantity, multiplied by the resource's efficiency.

Co-products and by-products are defined on the formula version; co-products can have a cost share and are posted as separate items, by-products post as scrap value.

Production control parameters set the number sequence for production orders, default production group, and whether to post packing slips and route card journals automatically.

Production order lifecycle: created, estimated, scheduled, released, started, reported as finished, and ended; estimation calculates material and capacity requirements.

Scheduling options: operations scheduling (job-level, respects resource capacity and times) versus job scheduling (individual jobs on specific resources with start/end times).

Release makes the production order available for picking and posting; the picking list journal consumes components and creates inventory transactions.

Report as finished posts the finished item to inventory and consumes the BOM per the reporting quantity; ending the order closes remaining quantities and posts variances.

Costing: estimated cost is calculated at estimation, actual cost accumulates from journals, and the difference posts as production variance at ending.

Master planning covers production demand through planned orders; planned production orders can be firmed into production orders.

Capacity reservations and load are managed through the resource load and capacity planning views; overload is resolved by rescheduling or adding capacity.

Quality management: quality associations trigger quality orders on receipt or production; test groups define tests and acceptable values.

Warehouse management: work templates, location directives, and mobile device menu items control put-away and picking; wave templates group work for release.

Transportation management: load templates, rate engines, and route plans calculate freight and plan shipments.

Vendor collaboration and procurement catalogs extend purchasing; purchase agreements hold committed quantities and prices with validity dates.

Inventory management: counting journals, inventory blocking, and quality orders integrate with warehouse processes; on-hand and reservation control availability.

Master planning: coverage groups define coverage code, positive/negative days, and safety margins; planned orders are generated per coverage settings.

Sales and marketing: sales agreements, trade agreements, and pricing/discount hierarchies determine prices and rebates on sales order lines.