Known issues in SXe V11 and Adv Mobile/Cyan POD/P&D

KB 2003877: V11 OEEBI OEEBU does not set the bofl, printprice, botype, usagefl and taxable fields correctly
Description:

Orders are loaded into the system using OEEBI/OEEBU processing. The user is not manually entering these orders.
The oeel.printpricefl = NO for each line item in these orders.
Therefore, the pricing is not printing on the invoices.

Steps To Reproduce:

Note: Use the same Cust#, product, qty, and price
1. Run EDEPP/OEEBU to create an order
2. Run OEEBI - OEEBU runs automatically BY OEEBI
3. OEET - Create an order
4. Compare the following fields on the 3 orders:
oeeh.bofl
oeel.printprice
oeel.usage
oeel.botype
BUG: Orders created via OEEBI are not set correctly.

Resolution:

Jira SXWEB-28729 fixed on version 11.18.10

SOLUTION: V11 OEEBI OEEBU will set the bofl, printpricefl, botype, usagefl and taxablefl fields correctly.

KB 1117447: EDEPP / OEEBU creating orders with blank Country Code

Description:

When creating an order via EDEPP and OEEBU, the country code field (oeeh.countrycd) does NOT get populated if

1. Shipto number is blank and ship to record is not found.
2. Shipto number is not blank and ship to address fields do not match ARSS record

Country Code not populated for EDI orders
EDI - Does edepp/oeebu populate the oeeh.countrycd from the arsc/arss records? and leaves the field blank?
EDI 850in - country code

Steps To Reproduce:

1. ARSC-Required: Confirm Country Code is set up.
2. ARSS-Required: Confirm Country Code is set up.
3. Create an edi850_i.dat flat file with 2 orders for Cust# and Shipto in steps 1 and 2.
--First Order - populate the "Shipto" record with the following fields; shipto number shipto name, address1, city, state, and zip.
--Second Order - only populate the shipto number in the shipto record.
6. Run EDEPP and OEEBU.
7. Run a q&d on oeeh.countrycd. The order that had shipto number only (blank shipto address fields) has country code populated.

Resolution:

Jira SXWEB-28292 (formerly MSF-174779) is entered for Development to review and is not fixed at the time of this writing (06/15/18)