OASIS will use the following logic to attempt to match orders and invoices downloaded from the factory with the orders in OASIS.

Orders

Header Level Matching

The Manufacturer and PO Number in the download must match what is in OASIS. If not, the operation is terminated and the user must apply the transaction manually. Customer number is optional.
The customer account is looked up for the manufacturer/customer combination. If not found, the parent manufacturer (if setup) is looked up. The parent customer is NOT looked up.
- If the account is found, then the customer is used and the search for a PO matching the MFG/cust/po is performed. If this is successful then the order is matched.
- If multiple matches occur, the operation is terminated and the user must apply the transaction manually.
If the above does not find a match, then the search is performed by only the MFG/PO. If not found, the parent MFG/PO search is performed.
- If found, the PO is used and the order is matched.
- If multiple matches occur, the operation is terminated and the user must apply the transaction manually.

Once the order is matched from above, then OASIS will attempt to match the lines. All lines on the download MUST match ONE line on the order. If this is successful, then the line is matched. If not, the operation is terminated and the user must apply the lines manually.
If the download has OASIS line UIDs, then the line IDs will be used for matching. If UIDs match, then the line is matched. Any mismatches or failures the operation is terminated and the user must apply the lines manually. Splits WILL happen if the matching line UID is found on the order but the catalog number is different.
If there are no OASIS line UIDs, then the fixture type and manufacturer code is used for matching. If a line is found with a matching type and manufacturer then the line is matched. If no matching type/manufacturer is found, the operation is terminated and the user must apply the transaction manually. If the line has a fixture type and the download does not, then the user must apply the transaction manually.

Some scenarios will prevent the above matching from taking place:

Duplicate lines (usually caused by partial shipments)
Manual Mode "MM" checkbox is checked
Multiple Releases
Order lines that don't match one for one, will force the entire order to be process manually

OASIS will first use the same logic above to match the invoice to the order. If the PO is found with the above logic:

If the line level matches are unique, then the invoice is applied at the line level
if line level matching is not possible (see the steps above), then the invoice is applied as a lot - with notes about the items that shipped. The lines will appear on the invoice, but are purely "notes."