# How to Enter a Customer Order in M3 (OIS100) > Source: https://netray.co/erp-help/m3-ois100-how-to-enter-customer-order > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer OIS100 (Customer Order. Open) is the primary M3 program for entering and maintaining customer orders, built as a header-then-line workflow: you first create the order header with customer, order type and delivery terms, then add order lines that each carry their own item, quantity, price and delivery date defaulted from customer and item agreements. ## Kind how-to ## System infor-m3 ## Erp Infor M3 (M3 Business Engine) ## Module Order / OIS100 ## Query How do I enter a customer order in M3 (OIS100) ## Alternate Queries - M3 OIS100 customer order entry steps - how to create a sales order in M3 - M3 customer order header vs line entry - OIS100 order type and delivery terms ## Applies To Infor M3 Business Engine 10.x-14.x, Order module, M3 H5 Client ## Steps ### Enter a customer order from header to confirmation **Items:** Open OIS100 and start a new order, entering the customer number - most header fields (currency, payment terms, delivery terms, warehouse) default from the customer record in CRS610. Set the order type, which controls numbering series, whether the order is a standard sales order, a return, an intercompany order, or a specific document flow configured for your business. Review and adjust delivery address, requested delivery date, and mode of delivery/terms of delivery if they differ from the customer defaults for this specific order. Move to line entry and add each item with quantity and unit of measure - price defaults from the customer/item price list (OIS011/CRS395) unless manually overridden. Check availability (ATP) on each line if your configuration shows available-to-promise data, and adjust the confirmed delivery date if the requested date cannot be met from current or planned stock. Add any order or line text, charges, or discounts required, then review the order total before releasing it from entry status. Release the order so it becomes visible to warehouse and planning processes - released orders can trigger allocation, picking list generation, or MRP demand depending on order type configuration. Print or transmit order confirmation via OIS300 (Customer Order. Print Confirmation) if your process requires sending confirmation to the customer. ## Sections ### Header defaults versus line overrides **Body:** Almost every field on an OIS100 order line has a default source: item price from a price list, delivery warehouse from the customer or item facility record, tax code from the customer/item combination. Understanding the default chain matters because a wrong price or warehouse on an order is rarely a data entry mistake - it is usually a missing or incorrect price list, agreement, or facility connection upstream, and fixing the order line without fixing the source record means the next order will have the same problem. Order type is the single field with the most downstream effect. It determines the numbering series, which document flow the order follows (standard ship, direct delivery, intercompany, return), whether the order affects MRP demand, and which print/EDI outputs fire automatically - always confirm order type before line entry, since changing it after lines exist is not always possible without deleting and re-entering the order. ### Availability checking and delivery dates **Body:** M3's availability check on an order line looks at current stock, allocated stock, and planned supply (open purchase and manufacturing orders) up to a horizon, then proposes a confirmed delivery date that may differ from the requested date. If a customer service rep overrides the confirmed date without checking ATP, the order can promise a date that manufacturing or purchasing cannot actually hit, which shows up later as a late shipment rather than an order entry error. For make-to-order or configured items, order entry can trigger an immediate MRP-relevant demand signal even before the order is released, depending on the item's planning method - this is why item type and planning method set up correctly in MMS001/MMS002 directly affects how accurate the ATP date shown in OIS100 actually is. ### Common line-level fields that get missed **Body:** Charge and discount lines, when required by the customer agreement, are entered as separate line types rather than adjustments to the item price field, and skipping them causes the order total to mismatch the customer's PO or contract. Project or job order allocation, when a company ties customer orders to a specific project (PJS) or job, is also entered at the order or line level and is easy to miss if the entry clerk is not aware the customer requires it for billing traceability. ## Pitfalls - Changing order type after lines have been entered, which is blocked or behaves inconsistently in many M3 versions - decide order type first. - Overriding the confirmed delivery date without checking ATP, promising a date the supply chain cannot support. - Entering price manually on every line instead of fixing a missing or expired price list agreement, which just defers the problem to the next order. - Forgetting charge/discount lines required by a customer contract, causing invoice totals to not match the customer's expected amount. - Releasing an order before verifying the ship-to address and delivery terms, especially for a one-time or drop-ship customer. - Not checking the item's facility connection (MMS002) before order entry - an item without a facility record for the order's warehouse cannot be added to a line. ## Ai Angle An AI assistant grounded in the customer's M3 order, price list and inventory tables can answer order-status and ATP questions in plain language for customer service reps - what is the real available-to-promise date for this line, why did the price default differently than expected, has this customer's price agreement expired - without the rep having to trace price list, customer and item records across three separate M3 programs. ## Faq ### Can I change the order type on an M3 customer order after entry? **Answer:** In most M3 configurations, order type should be set correctly before lines are added; changing it afterward can be blocked or can leave numbering, document flow and MRP demand records inconsistent, so it is safer to cancel and re-enter the order with the correct type. ### Why does OIS100 show a different price than the customer's quoted price? **Answer:** Price defaults from the applicable price list or customer/item agreement (OIS011/CRS395); if the order shows a different price, the agreement has likely expired, has a different effective date range, or a more specific price list is matching first based on M3's price list priority rules. ### What triggers MRP demand from a customer order in M3? **Answer:** Demand is generated once the order line's item and facility combination is planning-relevant (MRP-planned) and the order is released; draft or unreleased orders typically do not generate MRP demand, which is why unreleased backlog can hide real supply problems. ### How do I confirm and print an order to the customer? **Answer:** Use OIS300 (Customer Order. Print Confirmation) after the order is released, or rely on automatic EDI/print output if your order type is configured to trigger confirmation automatically on release. ## Search terms M3 OIS100, M3 customer order entry, how to enter sales order M3, M3 order type delivery terms, M3 available to promise ATP, OIS300 order confirmation print, M3 price list CRS395, M3 order header line entry --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json