MB-330 Sample Questions & Answers

The correct process for a standard cost rollup is sequential and structured. First, a new costing version is created to contain the pending cost changes. Then, the cost of the component (the raw material) must be updated and activated first. Once the raw material has a new active standard cost, the BOM calculation for the finished good can be run. This calculation will pull the new active cost of the component to accurately calculate the rolled-up cost of the finished product. Finally, the new calculated cost for the finished good must be activated to be used in future transactions.

The standard functionality to manage in-transit inventory for transfer orders is by using a transit warehouse. A virtual warehouse should be created for this purpose. This transit warehouse is then assigned in the 'Transit warehouse' field on the main warehouse's setup page (specifically, the source warehouse in the shipping relationship). When a transfer order is shipped, the system automatically moves the inventory from the source warehouse to this designated transit warehouse, where it remains until it is received at the destination. This provides both physical and financial visibility of in-transit stock.

The 'Purchase order vendor confirmation' workflow is specifically designed to manage the approval process for POs confirmed by vendors through the collaboration portal. This workflow can be configured with conditional steps. You can add a condition that checks if the 'Confirmed delivery date' on the PO line is more than 5 days after the 'Delivery date'. If this condition is met, the workflow can route the confirmation to a specific user or user group (like the purchasing manager) for approval. This directly addresses the requirement to handle exceptions based on delivery date changes.

This process involves three distinct stages supported by specific menu items. First, 'Sales picking' (or a similar picking process) is used to pick items into the tote. Second, at the packing station, a 'Packing' process menu item is used to scan the tote and move its contents into a new shipping container. Finally, after packing is complete, a 'Container close/reopen' process is needed to finalize the shipping container, which typically triggers label printing and updates the shipment status.

This requirement is met by configuring a cycle count plan. The plan should be filtered using a query to only include items where the ABC code is 'A'. The 'Days between cycle counting' field ensures that once an item is counted, it won't be suggested again for 7 days. The 'Maximum number of cycle counts' field limits the generated work to 3 items per run. Finally, scheduling the 'Cycle count work by plan' periodic job ensures this logic is executed automatically every day to generate the required work.

This is the standard approach for managing different units of measure for different processes. The inventory unit is the base unit for all transactions (Each). The sales unit is set to 'Box' on the released product, which will be the default on sales orders. A standard unit conversion (1 Box = 12 Each) allows the system to automatically translate the sales quantity into the inventory quantity for picking and reservation while applying pricing based on the sales unit.

Planning Optimization relies on a specific data entity, the 'Approved Vendor List', to source vendor lead times accurately. If this feature is not enabled for use within the Planning Optimization configuration, the service will not be able to find and apply the vendor-specific lead time from the purchase trade agreement or default order settings. Instead, it may fall back to a zero or minimal lead time, causing it to schedule the orders based only on the requirement date, which results in them being created too early. Enabling the use of the approved vendor list is a critical step for accurate purchase planning.

This scenario requires dynamic inspection levels. The initial 10% inspection is configured via a quality association for the vendor/item combination, linked to an item sampling record set to 10%. The test group associated with the quality order should have 'Full blocking' enabled to prevent usage of failed items. The second part of the requirement, increasing inspection to 100% after a failure for a period, is a manual or semi-automated process. After a quality order fails, the quality manager must update the quality association for that vendor to a different item sampling record set to 100%. This combination of features provides the required control.

This rating structure is configured using the rate engine. A 'Rate master' is created to hold the actual rates. For this scenario, a Point-to-Point (P2P) type is appropriate. Inside the rate master, you define the breaks (1-100kg, 101-500kg) and the corresponding rates ($50, $125). To link this rate to the destination, you use a 'Rate base assignment'. This connects the destination postal code (90210) to a rate base, which is then used as a lookup in the rate master. This combination allows the engine to find the correct rate based on both destination and weight.

The scenario describes a classic min/max replenishment requirement between warehouses. The correct solution is to use the warehouse replenishment feature. You would create replenishment templates of type 'Min/Max'. In these templates, you define the minimum stock level that triggers replenishment and the maximum level to replenish to. The key is to run this replenishment for the store warehouses and configure the DC as the source warehouse. When the periodic replenishment job runs, it will evaluate stock levels in the stores and automatically create the necessary transfer orders from the DC.