SX.api OE Full Order Maintenance process
SX.api OE Full Order Maintenance is used by the SX.api interface to provide real-time data processing for inbound customer POs and Requests for Quotes. This is an alternate data transfer method to the EDI Entry Processing Purchase Orders Report, which is a batch reporting process. SX.api OE Full Order Maintenance uses a set of business rules to translate either EDI 840/850 transaction sets, or order data that was submitted by a third-party application. These transaction sets are converted to Sales Order Entry header and line items. The majority of the sales orders are created with no errors. Any errors or exceptions are marked and can be viewed, corrected, and processed in Electronic Transaction Control Center.
Inbound EDI840 transaction sets, and any EDI850 change orders are created as quote orders. You can review these orders in Sales Order Entry and make any changes there.
Kit, tally, nonstock, and restricted products are not allowed and are not created as line items. If one of these products are received through OE Full Order Maintenance, a header error is generated. The order is placed on electronic hold (e-hold), and the transaction can be viewed in the Electronic Transaction Control Center.
Future Orders
Incoming orders may be created as Future Orders in Distribution SX.e based on these settings:
- The Additional Days for Calculating Requested Ship Date value in , and
- The Saturday Shipment or Sunday Shipment settings in , and
- The End of Day Cutoff in Product Warehouse Description Setup, or
- The order comes in with a FO designator.
The current date + Additional Days + 1 day (for each Saturday/Sunday Shipment option selected) + 1 day is used if the End of Day Cutoff has passed. This calculated date is compared to the requested date. If the requested date is later than the calculated date, the order is designated as a future order.
Fulfillment orders
If these conditions are met, fulfillment orders can be received and updated through SX.api:
- The order fulfillment feature is activated in SA Administrator Options.
- The sxapiFullOrderMntV6 call was modified to create and update fulfillment orders.
A submission rule for fulfillment orders that are received through SX.api is set up in Sales Order Fulfillment Setup. Fulfillment orders can be submitted automatically, submitted if fully filled, or submitted manually. If the submission rule is not set up, the fulfillment orders must be manually submitted in one of these functions:
- Sales Order Entry
- Sales Order Fulfillment Inquiry
Fulfillment orders that were not submitted are in the order fulfillment stage of eCommerce. You can search for fulfillment orders in the eCommerce stage in Sales Order Fulfillment Inquiry.
An origin code for fulfillment orders that are received through SX.api can be set up in SA Table Code Value Setup. After an fulfillment order is submitted, the tied fulfillment orders are created. If a origin code was set up for fulfillment orders, the origin code is included in the tied fulfillment orders.
3PL
If you use the 3PL, or Third-party Logistics, function, orders can be received in OE Full Order Maintenance for customer-owned inventory. This inventory is usually maintained in an area designated in your distribution warehouse as the customer’s ‘warehouse’.
If the customer's warehouse has insufficient stock, the line is automatically split and stock is obtained from an alternate warehouse to fill the order. The stock is pulled from the alternate warehouse location during the picking process. The SX.api OE Full Order Maintenance function creates the sales order and processes it normally. During order invoice processing, the warehouse transfer is created automatically to move the stock from the alternate warehouse to the selling, or customer, warehouse. An invoice is created for the alternate warehouse lines. The price and cost of those lines is obtained from the alternate warehouse’s product records, not the selling warehouse.