CertifyDeckCargando contenido…
The official Microsoft Certified: Supply Chain Management AI Consultant Associate syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Develop a product strategy
A category hierarchy is created with a name and category nodes (name, code and friendly name), and its purpose is set by associating it with a hierarchy type such as commodity code or procurement. Released products are classified by assigning them categories from one or more hierarchies, for export, procurement, sales or other purposes.
Create a hierarchy of product classification ↗Classify a product using category hierarchies ↗
Product lifecycle states determine which business processes can use a released product or variant: each process is set to Enabled, Blocked or Enabled with warning. The Is active for planning option includes or excludes the product from master planning and BOM level calculations, and one state can be the default applied when products are released to a legal entity.
Attributes are user-defined fields that describe products, and each one is based on an attribute type that sets the data type and allowed values. When assigned to a category, products inherit the attributes and their default values, which can be overridden per product. They classify the product, not each item of inventory, and are not connected to inventory dimensions.
Price attributes for products, customers, and orders ↗Batch attributes ↗
The product dimension group determines which dimensions create variants and cannot be changed after the record is created. The storage dimension group controls how inventory is stored and taken out, and the tracking dimension group adds batch or serial number. Physical and Financial inventory define the detail of records and costs; Financial inventory cannot be enabled for the Location dimension.
Inventory costing FAQ ↗Create a released product for a single company ↗
The item model group determines how receipts and issues of a product are controlled and how it is valued: inventory model, stocked product, physical and financial posting, negative inventory, and registration, receiving, picking and deduction requirements. Each released product uses one costing model, and FEFO is a reservation technique rather than a costing method.
Inventory costing FAQ ↗Create a released product for a single company ↗
The reservation hierarchy defines the levels where reservations are made, and the key decision is which dimensions sit above or below location. Those above are set on the order and workers cannot change them; those below are decided by the warehouse. With batch below location, the Allow reservation on demand order option lets you reserve a specific batch when the customer asks for one.
Reservations in Warehouse management ↗Flexible warehouse-level dimension reservation policy ↗
A unit sequence group lists the units that warehouse processes use, from smallest to largest, and the smallest must match the inventory unit of the product. Its lines define license plate grouping, cycle counting units and the units suggested on mobile devices. It is mandatory for released products that use warehouse management processes.
Introduce products
A product master defines the rules from which variants are generated, and it carries a product dimension group and a configuration technology that cannot be converted after implementation. Products are released to one or many legal entities, and manually creating a released product also releases it to the current entity. Variant suggestions propose the dimension combinations.
Product information overview ↗Create predefined product variants ↗
A BOM defines the components of a product at a single level, and the BOM version relates it to a product and constrains its validity by period, quantity or site. A version must be approved before planning or manufacturing can use it, and activating it makes it the default; a conflicting activation raises an error. The line type determines how the component is supplied.
Trade agreements are recorded in journals: each line states who it applies to (table, group or all), the product, quantity breaks, the price and dates, and takes effect after it is validated and posted. A sales price requires the Table product code type. Discounts can be line, multiline or total, and master planning can select a vendor based on purchase trade agreements.
Create a new trade agreement ↗Master planning with purchase trade agreements ↗
Formulas offer features of their own: size and multiples determine the allowed batches, yield applies a factor to the lines, From formula size selects the version by quantity, plan groups let ingredients be substituted by priority, and step consumption handles non-linear consumption. A planning item groups co-products that are produced together without a primary formula item.
A formula brings together the ingredients needed to produce a quantity of an item, and every formula needs at least one version, which holds the yield, co-products, by-products and cost allocation. Versions must be approved before use, and several can be active if their date ranges and from quantities do not overlap. Production control parameters can block editing and removal of approval.
Formulas and formula versions ↗Total cost allocation method ↗
Manage active products
Product filters classify items for handling, purchasing and selling, and they apply only to items that use warehouse management processes. Filter codes are defined by title, required on the item group and assigned on the released product, and filter groups simplify location directive queries. Customer and vendor filters are enabled in the Warehouse management parameters.
A costing version holds standard or planned cost records according to its costing type: standard costs value transactions and planned costs support simulations. Item cost records start as Pending and become Active when activated; the Block and Block activation policies control their maintenance. The two-version approach keeps updates separate and relies on a fallback principle.
To use standard costs you create an item model group with the Standard cost inventory model, financial negative inventory and physical and financial posting, then define variance accounts and costing versions. The active cost values receipts and issues. Existing items move to this model through standard cost conversions, and an activated cost cannot be deactivated or deleted.
Prerequisites for standard costs ↗Standard cost conversion overview ↗
Item cost records start as pending in a costing version and become active when you activate them; the current active record values inventory under standard cost. The Block and Block activation policies control maintenance and activation, and BOM calculations produce the cost of manufactured items.