Free AB-330 practice test: 30 questions with answers

The Warehouse Management mobile app supports receiving and posting product receipts. Unrecorded receipts, month-end posting and emails do not capture inventory at the point of receipt.

Sites, warehouses, locations and zones form the physical structure and location profiles define behaviour. Customer, price and collaboration setups are different areas.

Cycle counting schedules frequent counts for targeted items and reconciles differences. Annual-only counts, complaint-driven counts and ignoring high-value items do not meet the control objective.

Inventory status blocking prevents use until quality approval. Treating quarantined stock as available, shipping before inspection and recording sales are incorrect.

Tracking dimensions such as lot or batch enable traceability for recalls. Colour, the PO number alone and logos do not provide traceability for product lots.

Inventory movements or movement journals record the transfer within a warehouse. Purchase orders, renaming items and notes do not record the movement.

Procurement workflows with amount conditions route requisitions to approvers automatically. Purchase orders without approvals, portals alone and email approvals outside the system do not enforce the policy.

RFQs collect vendor responses and support the award decision. A single PO to one vendor, spreadsheets and deliveries before quotation do not run a competitive award.

Purchase agreements define negotiated prices and validity, which purchase orders reference. Vendor returns, BOMs and customer invoices serve different purposes.

Over and under delivery tolerances control acceptable variance on purchase lines. Blocking all over-delivery, separate orders and ignoring the difference do not reflect the policy.

A vendor return order referencing the receipt reverses inventory and creates the credit. Deleting orders, sales orders to vendors and ignoring defects misstate inventory and payables.

Converting an approved requisition keeps the link and the approval history. Manual re-entry, emails to vendors and sales orders break the process.

ATP considers expected supply and calculates a realistic promise date. Promising without stock, refusing outright and random dates are not reliable promises.

CTP includes capacity and supply in promising. ATP alone does not evaluate capacity, fixed lead times ignore constraints, and earliest-date promises are unreliable.

Converting the quotation keeps the linked prices and lines. Retyping risks errors, emails do not create orders, and purchase orders are for buying.

A sales return order receives goods and issues credit correctly. Deleting orders, purchase orders to customers and ignoring returns misstate inventory and receivables.

Sales or trade agreements define customer prices and validity. Purchase agreements are for vendors, dimension groups classify products, and zones structure warehouses.

Sales groups and commission setup calculate commissions on relevant orders. Purchase orders, wave templates and production journals are unrelated.

Lifecycle states control availability through stages such as development and release. Products without states, default releases and immediate retirement do not manage this progression.

Phase-out or retired states stop new orders in a controlled way. Immediate deletion destroys history, indefinite acceptance and renaming do not manage discontinuation.

BOM versions with effective dates allow controlled changes while in-progress orders use the earlier version. In-place edits, deletion and new item numbers disrupt production.

Attributes describe products for classification, reporting and compliance. Warehouse hours and vendor payment method are unrelated to product attributes.

Variants under a base product share structure and maintain dimension links. Unrelated products, descriptions only and a single product lose the variant structure.

Costing versions with standard costs support comparison and activation. Zero costs, purchase price alone and random values do not provide the standard cost basis.

Finite capacity respects limits, which keeps schedules feasible. Infinite capacity ignores constraints, midnight scheduling is arbitrary, and no resource data cannot produce a valid schedule.

Release to the floor follows reservation confirmation in the production order lifecycle. Estimation, ending and creation alone do not release work.

Co-product and by-product cost allocation divides production costs appropriately. Zero costs, deletion and sales charges misstate costs.

Substitution on the production order records the change accurately. Silent BOM changes for future orders, sales returns and ignoring differences misstate production.

Subcontracting configuration with routes and warehouses manages materials and returns. A plain finished-goods PO, untracked internal work and sales orders to the subcontractor do not capture the flow.

Forecast models and parameters determine how history becomes forecast demand. Requisition templates, invoice layouts and wave templates do not generate forecasts.