EDI OE (Order Entry) and PURCH Control Maintenance Records
The following control maintenance records belong to the OE (Order Entry)
area within the EDI (Electronic Data Interchange) category. Complete these
records if your company uses the EDI companion product.
Allow Auto-Matching For Lot Order
With EDI
Indicate whether to allow automatic matching for lot orders through
the EDI 810 Invoice Review Queue.
More:
|
Options
|
-
Yes - The system enables
matching for lot orders within EDI and activates the Allow Match Lot Item Invoice
field on the EDI
Add'l Doc Info screen.
-
No - The system uses
standard matching logic without taking lot orders into
effect.
Note:
This is set at the trading partner level, not
a global setting.
|
|
Outcome
of setting this control record
|
Enables matching
for lot orders within EDI and activates the Allow
Match Lot Item Invoice field on the EDI
Add'l Doc Info screen.
|
|
Default
Value(s)
|
No
|
|
Dependencies
|
The trading partner
must also be flagged to allow direct orders using the Process Invoices for Directs
field on the EDI
Add'l Doc Info screen.
|
|
Additional
Information
|
Required for matching lot items through
EDI.
|
Allow Printing of Zero/Negative Dollar Direct
Shipment PO
New in Release 9.0.3
Indicate if you want to include zero or negative dollar direct shipment
purchase orders when sending the EDI 850 transaction when customer is
on credit hold.
More
|
Options
|
-
Zero - Allows printing
of purchase orders including EDI 850s if the purchase
order generation has a zero dollar total even if a customer
is on credit hold.
-
Negative - Allows printing
of purchase orders including EDI 850s if the purchase
order generation has a negative dollar total even if
a customer is on credit hold.
-
Both - Allows prints
of purchase orders including EDI 850s if the purchase
order generation has a zero dollar or negative dollar
total even if a customer is on credit hold.
|
|
Outcome
of setting this control record
|
Allows customers
to view zero or negative dollar direct purchase order details.
|
|
Default
Value(s)
|
No
for backward compatibility.
|
Allow Writer Field To Be
Blank On EDI 840, 850, And 855 VMI Orders
Indicate whether the system leaves the Written
by field on the Header
tab of an EDI 840, 850, or 855 VMI order blank when the incoming document
does not include a writer.
More:
|
Options
|
-
Yes - The system leaves
the Written by
field blank. The next time the order is opened, usually
from the review queue, the system prompts the user to
enter the order writer.
-
No - The system populates
the Written by
field with the data from the Grp/User
to Review Received Document field in the document's
EDI
Add'l Doc Info window. If that field is blank, the
system populates the Written
by field with EDI.ADM.
|
|
Outcome
of setting this control record
|
Determines if the
system adds an order writer based on the EDI document's EDI
Add'l Doc information if an order writer is not included in
the incoming EDI.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
If you set this
record to Yes, you
must also leave the Grp/User
to Review Received Document field in the document's
EDI
Add'l Doc Info blank.
|
Create A Report For Zero Quantity
Or Confirming EDI Orders
Indicate whether the generic inbound 850 mapper creates a report rather
than a sales order when EDI receives zero quantity orders or confirming
orders.
More:
|
Options
|
-
Yes - Creates a report
and sends it to the Hold file of the user or group specified
in the Grp/User To Review
Received Document field on the Add'l
Doc Info window for the incoming document.
-
No - Creates a sales
order with ***Confirming Order - DO NOT DUPLICATE***
in either the Shipping Information or Internal Notes field
of the order
|
|
Outcome
of setting this control record
|
Determines if the
system creates an order for EDI 850s with zero quantities
or that contain 06
in the BEG01 field.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
For additional
information about the system processes EDI 850s, see How
the System Process EDI 850s.
|
Create PO Variances For EDI Invoices
Indicate if you want to create purchase order variances when EDI Invoices
match.
More:
|
Create
EDI and Manual Variances Only for:
|
|
Select
one of the following for which you want the system to create
variances and therefore populate the associated queue:
Note:
These queues are mutually exclusive. You cannot work both
queues in the system at the same time. Selecting one automatically
deactivates the other. However, you can change between them
at any time.
|
|
Create
Variances for Directs for Partial Matches
|
New in Release 9.0.2
|
If set to Yes,
the system creates variances for direct purchase orders even
if the match is not complete.
The default is No.
Note:
This setting applies only if you are using the P/O
Variance Queue and not the Payable Variance Resolution
Queue introduced in Release 9.0.3.
|
|
#
of Days for Critical Priority in PVR Queue
|
New in Release 9.0.3
|
Determines the priority of variances
listed in the Payable Variance Resolution Queue.
The default is 5.
|
|
Variance
Type
|
New in Release 9.0.3
|
Select the Variance Type, such as Quantity
or Cost, to assign default users or groups and resolution
reasons.
Note:
These values are hard coded in the system and
each has a resolution reason assigned.
|
|
P/O
Type
|
New in Release 9.0.4
|
The type of purchase order you want
the system to create, such as Stock or Job Management.
|
|
Resolve
Type
|
New in Release 9.0.4
|
Indicate how you want the resolution
handled, such as credit/rebill or automatic approval.
|
|
Assign
By Default To
|
New in Release 9.0.3
|
Select a user or group to which the
variance should be sent for resolution.
Use the Payable
Variance Queue Assign To Users/Departments control maintenance
record to maintain assignment groups.
Note:
If you select order writer, the system retrieves the order
writer ID and the variance is sent to that specific user.
|
|
Default
Resolution Reason
|
New in Release 9.0.3
|
Select one or more resolution reasons
you want the user to be able to select from when resolving
variances. If left blank, users can select from all reason
codes available.
Use the EDI
810 Payable Variance Resolution Reasons control maintenance
record to maintain resolution reasons.
|
|
Outcome
of setting this control record
|
|
Determines how the P/O
Variance and Payable
Variance Resolution queues are populated, to whom the
variances are sent depending on type, and what resolution
codes users are allowed to select from when receiving a variance.
|
|
Default
Value(s)
|
|
Dependent on the field. See above.
|
|
Additional
Information
|
|
For more information about purchase
order variances, see Managing
Variances Using the Purchase Order Variance Queue and
Managing
Variances Using the PVR Queue .
|
Default EDI Sales Source
Enter the default sales source to assign to an incoming EDI purchase
order from a customer. Valid sales sources are defined in G/L
Sales Source Maintenance.
Default Print Status To "E"
For All EDI Vendors
Indicate whether the system sets the default print status for purchase
orders to EDI vendors to E for
EDI.
More:
|
Options
|
|
|
Outcome
of setting this control record
|
The system uses
the setting in this record only if the Print
Status Override field on the vendor's Miscellaneous
Vendor Information I window is blank.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
If the system sent
an 850 for the original order generation, the system does
not populate any new generations created for that order during
receiving with E,
even if the Print Status
Override field and/or this control maintenance record
are set to Yes.
To indicate a vendor as an EDI vendor,
create an EDI
Trading Partner Profile for that vendor.
|
Disable Checking Part #'s, UOM's,
And Quantities On EDI Invoices
Indicate whether to disable the checking of part numbers, units of measure,
and quantities on EDI invoices when the system auto-reconciles invoices
in the EDI 810 Review Queue.
More:
|
Options
|
-
Yes - The system checks
invoice amounts and the number of line items, but does
not check part #s, UOMs, and quantities.
-
No - The system checks
invoice amounts, the number of line items, part #s, UOMs,
and quantities.
|
|
Outcome
of setting this control record
|
Determines whether
the system uses product part numbers, product units of measures,
and product quantities when trying to match inbound EDI 810
to existing orders in the system.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
For more information
about processing 810 invoices, see How
the System Process EDI 810s.
|
Disallow Creation Of PO Variances For EDI 810
New in Release 9.0.6
Indicate if you want the system to create variances and sent to the
Payable Variance Resolution Queue by setting this control maintenance
record to Yes.
More
|
Options
|
-
Yes - The system will
not create variances for the Payable Variance Resolution
Queue.
-
No - The system creates
the variances as usual based on the Create
PO Variances For EDI Invoices control maintenance
record.
|
|
Outcome
of setting this control record
|
If this option
is set to yes, but the Create
PO Variances For EDI Invoices control maintenance record
is set to Purchase Orders,
the system will not
create the variance records.
If the Create
PO Variances For EDI control maintenance records is
set to Payables, this
control maintenance record has no effect.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
None.
|
EDI 810 Payable Variance Resolution Reasons
New
in Release 9.0.4
Define the IDs and resolution reasons from which you want your users
to select when handling payable variances through the Payable
Variance Resolution Queue.
EDI Default Product If Not Found
Create a product record named ***EDI PRODUCT NOT FOUND*** in upper case
and with the asterisks, which the EDI program can assign to an EDI order
in the event that it cannot locate an incoming product in your product
file. After created, assign the product to this control maintenance record.
EDI PO Variances For EDI 810 Invoices
Indicate how the system should handle EDI 810 invoices and purchase
order variances.
More:
|
Options
|
-
Yes - The system creates
purchase order variance records for EDI 810s that are
received with either a price or quantity mismatch and
places them in the Purchase Order Variance Queue.
-
No - The system ignores
EDI 810 invoices when it creates purchase order variance
records.
|
|
Outcome of setting
this control record
|
After entering
the receiving information for an order that reconciles to
an EDI 810 invoice, if set to Yes,
the system creates variance records for those invoices with
a mismatch in either prices of items, or quantity of items.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
For more information
about purchase order variances, see Managing
Variances Using the Purchase Order Variance Queue.
|
EDI Product Matching Priorities
New in Release 9.0.3
Define the hierarchy in which you want the system to match product IDs
for incoming EDI documents: 810, 855, and 856. Settings at the EDI Trading
Partner level supercede this control maintenance record. This hierarchy
lets you set a global hierarchy and then have a different priority for
an individual trading partner and keep your matching different, if needed.
By default, the system uses the standard Eclipse product matching types.
For more information, see EDI
Part Number Matching
in the EDI documentation.
Expire All Matrix Cells When EDI 845 Contracts
Are Imported
New in Release 9.0.3.11
Indicate how you want to handle the expiration of matrix cells when
you import 845 contracts.
More:
|
Options
|
-
Yes - The system automatically
expires all existing matrix values a day before new matrix
created based on the imported EDI 845 effective date.
This is the default.
-
No - The system expires
the last matrix created after creating the new matrix
based on the new EDI 845.
-
Effective - No existing
matrix dates expire.
|
|
Outcome
of setting this control record
|
See table below.
|
|
Default
Value(s)
|
No.
|
|
Additional
Information
|
These settings apply in both Solar and
Eterm.
|
Additional Examples:
|
If
CMR is set to...
|
and
imported Effective Date is...
|
Then...
|
|
Yes
|
prior to the effective date from the
existing sell matrix group (expired date range on both matrix)
|
No matrix is deleted. All existing matrices
are set to expire a day before the new matrix's effective
date as created by the import. Only the new matrix effective
and expired dates are active.
|
|
Yes
|
after the effective date from the existing
sell matrix and expired date on the import
|
No matrix is deleted. The sell matrix
created on the EDI 845 is set by the quick sell matrix effective
and expiration date. The existing sell matrix is updated but
keeps its effective date. The matrix updates the expiration
date to a day before
the new matrix from EDI is effective.
|
|
No
|
updated on import
|
No matrix is deleted. The last existing
matrix sell expires and a new matrix sell is created with
the imported EDI 845 effective and expiration dates.
|
|
Effective
|
prior the current effective date
|
No matrix is deleted. The new EDI 845
matrix is created and the existing matrix is neither
deleted or expired, but remain with the original values.
|
|
Effective
|
after the current effective date
|
No matrix is deleted. The new EDI 845
matrix is created. The last existing matrix expires a day
before new EDI 845 effective date, and if they are more matrix
values, they keep the original values.
|
|
Blank
|
prior the current effective date
|
Same as Effective.
|
|
Blank
|
after the current effective date
|
Same as Effective.
|
Include Default Shipping Instructions
On EDI Orders
Indicate whether to include customer default shipping instructions on
EDI orders.
More:
|
Options
|
-
Yes - The Shipping
Instructions field on the Header of a sales order
displays the default shipping instructions set in the
customer record using the Orders
> Customer Order Entry Instructions option and
any additional instructions sent in the incoming EDI order.
-
No - Only the shipping
instructions sent on the incoming EDI order display in
the Shipping Instructions
field on the Header of a sales order.
|
|
Outcome
of setting this control record
|
Use this control
record to control whether the default instructions you have
set up for a customer are also included with their EDI orders.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
None
|
Incoming EDI 846 Status
Select the print status the system assigns to incoming EDI 846 Inventory
Advice documents.
More:
|
Options
|
|
|
Outcome
of setting this control record
|
If you want to
review the EDI 846s, set this option to P
to review them in the Invoice Preview Queue.
|
|
Default
Value(s)
|
B
|
|
Action
if set to Null
|
Same as if set
to B.
|
|
Additional
Information
|
For more information
about EDI 846s, see Receiving
846 Inventory Advice Documents.
|
Log Remote Pricing Variance
Select how you want to measure pricing variances.
More:
|
Options
|
-
Percentage - Determines
the pricing variance by a percentage. Enter the percent
by which the remote order price can vary from the LIST
price without the system logging the order with a pricing
error.
-
Dollars - Determines
the pricing variance by a dollar amount. Enter the dollar
amount by which the report price can vary from the LIST
price without the system logging the order with a pricing
error.
|
|
Outcome
of setting this control record
|
Determines by how
much an order can differ from the LIST price in the system
before it is considered in error.
|
|
Default
Value(s)
|
None
|
|
Action
if set to Null
|
Orders are not
considered in error when there is a difference between the
order price and the system's LIST price.
|
|
Additional
Information
|
To override this
control maintenance record setting at the customer level,
use the Allowed Pricing Variance
% field in the customer's Remote
Order Entry Parameters window.
|
Outgoing EDI 846 Information
This control record allows you to create control ID which can be used for different LIN and QTY segment configurations in EDI 846 outgoing document. You can also edit the control ID to change LIN and QTY segment configurations. First, you need to define the Control ID in Select 846 Ctrl ID. Then add the Vendor's Product Number and Manufacturer's Product Number.
Once you have entered the details, indicate if you want the following quantities in the EDI 846 documents.
- Qty On Hand - The quantity of a product available in warehouse.
-
Qty Committed - The quantity of a product committed for existing orders.
-
Qty Available For Sale - The quantity of a product available for sale.
-
Qty On PO (not Rec'd) - The quantity of a product for which Purchase Order is raised but items not received.
-
Qty In Transit - The quantity of a product in transit.
-
Qty BackOrdered - The quantity of a product back ordered.
|
Options
|
|
|
Outcome
of setting this control record
|
Use this control
record to control what information should be added to the EDI 846 document.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
Same as if set
to No.
|
|
Additional
Information
|
The Control ID is mapped to the trading partner to whom you want to send the report.
|
Prevent Search for EDI Part Identifiers in
Product Index
Indicate if you want to skip searching product descriptions for EDI
documents. You can override this setting at the trading partner level
using the EDI
Group Profile Global Info Table in EDI.
Reconcile EDI 810 Open Generations With Partial
Matches
Indicate if you want to automatically reconcile and create variances
for any open generations with partial matches with the defined criteria
when received through the EDI 810 invoice.
More:
|
Options
|
-
Yes -The system reconciles
the payable to the order and creates a variance
for any open generations with partial matches with the
defined criteria when received through the EDI 810 invoice.
-
No - The system creates
a variance, but does not reconcile any orders automatically.
|
|
Default
Value(s)
|
No
|
|
Action
if set to Null
|
No
|
|
Additional
Information
|
To use this feature
(Set it to Yes) make
sure the Check All Unpaid
Gens field is set to Yes
on the the Add'l Doc Info screen for the EDI 810.
|
Send Carton Packing Detail in EDI
856
See INVM Pack Parameters in
this document.
Store EDI Order Confirmation Message
In
Specify in which field on an order's Header the system stores the EDI
Order Confirmation message for EDI confirmation orders in which the BEG01
field of the incoming EDI 850 contains 06.
Select one of the following options:
-
Internal
Notes
-
Shipping Instructions
Update Rebate View Dates When An EDI 845 Processes
New
in Release 9.0.4
Indicate
if you want to allow sites to specify whether or not they also want the
dates from the inbound 845 to update the Effective Date and Expiration
Date for the Rebate view.
More
|
Options
|
-
Yes - Dates
from the inbound 845 to update the Effective Date
and Expiration Date for the Cost and Rebate
view in the sell matrix.
-
No - Dates
from the inbound 845 to update the Effective Date
and Expiration Date for the Cost
view only in the sell matrix.
|
|
Outcome
of Setting this Control Record
|
If set to Yes, adding
the dates to this view may affect how the rebate pricing is
determined because the rebate override date changes to the
newly received inbound 845 date and does not
use the ship date on the order
|
|
Default
Value(s)
|
No,
for backward compatibility.
|
|
Action
if set to Null
|
No
|
|
Additional
Information
|
If set to yes after upgrade, this
change affects only those matrixes going forward.
|
|
Prior
to Release 9.0.4, when an inbound EDI 845 was received, the
system updated the Sell Matrix records' Effective
Date and Expiration
Date in the Cost
view only using the new 845 data.
|