advertisement
Infor ERP SX.enterprise 6.0
Release Overview
Infor introduces version 6.0 of Infor ERP SX.enterprise! This document provides an overview of some of the new features and functionality for SX.enterprise in release 6.0.
Infor ERP SX.enterprise Release Overview Page 1 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 2 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 3 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 4 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 5 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 6 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Accounts Payable
1099 Changes for 2008 (B)
There are minor changes for magnetic media, but no changes to the printed form in 2008. In the
Transmitter “T” record, two fields—Cartridge Tape File Indicator (positions 409-410) and Transmitter’s
Media Number (positions 411-416)—have been deleted. These positions are now blank.
There were changes for 2007, which were not required in 2007, so Infor did not update AP Administrator
Federal 1099 Print (APAF) at that time.
Three fields were deleted from the Payer ‘A’ Record and are no longer required. The deleted fields are
Original File Indicator (position 48), Replacement File Indicator (position 49), and Correction File Indicator
(position 50). Positions 48-50 are now blank.
Cannot Suspend or Dispute Invoices In Use (G)
When you select invoices in the invoice browser in APEI, right-click, and choose
Suspend
,
Un-Suspend
,
Dispute
, or
Un-Dispute
, the system verifies that the selected invoices are not in use by another user. All invoices that are not in use by another user are updated as requested. If one or more of the invoices is in use, the invoice status is not updated and the following message appears:
One Invoice Was Locked By Another User, Could Not Be Changed
Can Print 24 Character Reference on Checks (B)
A new option,
Print Full Reference Field (2nd Line)
, has been added to AP Entry Check Print. Select
No
to retain current functionality and print only the first nine characters of the reference on the check. Select
Yes
to print the full 24 character reference from the invoice on the check. The full 24 character reference will print on a second line below the invoice. The number of invoices that can print on each check before an overflow stub is used decreases each time a full 24-character reference is printed on the check. For example, 13 one-line invoices can print on a standard check. If you select to print the full 24-character reference and four invoices have a second reference line, then only nine invoices can print on the check; four of the invoices take up two lines each, leaving room for five one-line invoices to complete the check before an overflow stub is created.
EDI810in Processing Changes in APEGE (B)
Invoices are now matched to purchase orders with backorders from an EDI flat file in the following order:
•
APEGE compares the quantity on the invoice to the uncosted quantity on each backorder. If there is an exact match, that PO suffix will be used for the EDI invoice.
•
If there is no match, it looks for the PO backorder with an uncosted amount greater than the
EDI invoice quantity, and where the difference between the two is smaller compared to all other backorders.
If an EDI 810in file does not contain a PO or item records, the expense/asset GL account from the AP
Setup Vendor (APSV) will be used to post the AP invoice amount. If there is no account in the vendor record, the AP Expense GL account from SA Setup Operator (SASO) will be used. If no account is set up on the SASO record, the account from the R&D operator will be used. In order to correctly process invoices without a PO or item records you should set up a valid GL account in either APSV or SASO.
When the Item Record Total Cost Amount is zero in the EDI810in file, the message “
CAUTION: Total
Cost Amount = 0
” will now print on the APEGE report.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 7 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
New Label for Option 17 in APEGU (B)
Option 17 in AP Group Update/Reconcile Invoices (APEGU) controls whether recurring groups are included in the report. To more clearly describe what this option does, the label for option 17 has been changed to
Include Recurring Groups
instead of
Update Recurring Batch
.
APEI Resizes and Honors XP Look and Feel (G)
AP Entry Invoice Center can now be resized correctly and retains window display settings when you choose to use the XP Look and Feel functionality. For more information on window resizing and XP Look and Feel, refer to the 5.5 project review UI Enhancements on the Infor365 support portal Web site.
Processing Type Default Settings (G)
The values that default into the
Proc Type
drop-down box in APEI are now based on the transaction type that is selected, as well as your AO and SASO settings. If you are entering an Invoice, Rebate, or Manual
Payment transaction type, the Proc Type will be loaded with
Expense
,
Trade
, and
Addon
. Addon will not be listed If your AO-Products-Costs option,
Post to G/L By: Include Addons
, is not selected, or the operator’s
SASO-Cost Controls
Allow User to Process Addon Invoices
is not selected.
If you enter a Misc Credit, Credit Memo, or Debit Memo, the Proc Types of
Expense
and
Trade
are loaded.
Operator security will also be considered. If you do not have security for one of the processing types, that type will not be loaded on the drop-down list.
The initial Proc Type that defaults when you enter APEI will still come from the AP Setup Vendor Proc
Type, as long as that type is available for the transaction type you are adding, and your security settings permit it.
Order for New Invoices on Browse (G)
When you add an invoice it will now appear in the browse section of the Invoice List view in one of the following ways:
•
If you have selected a Sort sequence from the shortcut menu prior to adding the invoice, it will be placed in the proper sequence in the list of invoices.
•
If you have not selected a sequence from the shortcut menu prior to adding the invoice, the invoices will be sorted by group name, created date, and group sequence number.
•
If you are working with only one group, the invoice will appear at the bottom of the list.
•
If you have not specified a sort sequence and you have multiple groups, the new invoice appears at the bottom of the group it was added to.
Limitations When Accessing Locked Invoices (B)
Changes were made to enable viewing locked or closed invoices under certain conditions. You can now view invoices that are locked, or ‘in use’ by another operator but only in view mode. Also, revisions were made to disallow changes to a locked invoice or one that is in Closed stage. The
Edit PO Cost
button on the
PO Header Search screen and the
Edit PO Lines
button on the PO Lines Search screen are disabled. The
Edit
option on the shortcut menu when selecting a locked invoice will be inaccessible. If you select multiple invoices (rows), a message will appear if any of the selected invoices are locked or closed. The
Add GL
Dist
button on the GL Distribution window will be inaccessible for locked invoices, and the
Convert Percent
To Amount
and
Set Amount Equal to Proof
shortcut menu option on the GL Dist window will be inaccessible.
You can update notes for a locked or closed invoice. This also impacts F3-Invoice, F8-GL Dist, and F12-
PO Lines in the character interface.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 8 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Workflow for Manual Invoice Address Edit (G)
The workflow for entering a manual address has been improved. When you advance the workflow from the
Invoice List window for a Misc. Vendor, the Additional Invoice Info window displays. When you click workflow forward (>>), APEI displays the next screen in your workflow. If you are entering a Manual
Payment, this will be the Manual Payment window. You can click workflow back (<<) to return to the
Additional Invoice Info window. You can also access the
Addl Invoice Info
icon in the treeview at any time to display address information for the vendor and make any edits necessary.
AP Supervisor Status Allows Group Updates in APEI (G)
An operator with AP Supervisor security can add and update invoices in another operator's group in APEI
Invoice Center. Before this enhancement, if a group was created for a different user, the AP Supervisor could enter invoices into that group, but could not update them.
Warning Displayed for POs Already Added to an Invoice (G)
When you add a purchase order to an invoice in APEI, the system now checks to see if that purchase order has already been added to another invoice. If another invoice exists with that purchase order, the following message appears:
Warning: PO Already Entered On Invoice xxxx In Group xxxx (8313)
Because this is only a warning, you can continue to enter the purchase order on the existing invoice.
If you select multiple purchase orders on the PO Header Search or PO Line Search windows, the following message appears:
Warning: PO zzz-zz Already Entered On Invoice xxxx IN Group yyyy *8313)
Do You Want To Enter the PO On This Invoice As Well?
You can choose to cancel the purchase order entry or continue to enter the purchase order on the invoice.
Proof Amounts for Addon Invoices (G)
Proof amounts displayed on the APEI PO Header window for an addon invoice will now be as follows:
•
Invoice proof will be zero when the total amount of addons on the invoice equals the total amount of the invoice.
•
Addon proof will be zero when the total amount of PO addons on this screen equals the amount of the addon from the Addon window.
•
The Addon Amount will reflect the addon from the Addon window.
Close When Fully Costed Option Added (G)
An option was added to the APEI PO Header window,
Close When Fully Costed
, that will close the PO when all lines on the invoice have been costed, even if the PO has uncosted addons. If you select this option and the PO is fully costed, the PO cost reconcilation process will set the PO stage code to Closed. If you select this option and a PO has uncosted addons that are capitalized at receiving, those uncosted addons will be backed out and the Uninvoiced Addons GL account will be debited.
GL Distribution Correct on Division Number Change (G)
In AP Entry Invoice Center, when you have an invoice where the division number is zero and the GL
Distribution records include one or more suspense postings, the system deletes the existing GL
Distribution records and creates new distribution records, using the correct division number when you change the division number.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 9 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Expensed Vendor Rebates Updates to GL (G)
Improvements have been made to APEI to better handle posting of expensed vendor rebates in GL.
Options were added to the GL Distribution window that allow you to identify a posting as a debit or a credit, and to indicate when the posting will be made, at Update or Costing. In addition, a proof amount was added to show the totals amounts Posted at Costing.
When a PO or PO line contains an expensed rebate, offsetting postings will be made to IC Rebates Due and AP Expense automatically when costing is performed in APEGU or Final Update, and will be shown on the GL Distribution window in APEI. You can change the amount posted to the AP Expense account, however, the At Costing proof must balance to zero in order for Final Update or APEGU to process the invoice and cost the PO(s). The IC Rebates Due posting cannot be changed on the GL Distribution window.
SX.enterprise creates new internal APEIG records for expensed vendor rebates in three different functions: 1) In APEI when you add a PO in Received or Costed stage that has one or more expensed rebates to an APEI invoice; 2) In POEI when you receive a PO that has an expensed rebate and that PO has already been added to an APEI invoice; and 3) APEGE (EDI file edi810_i
vendor invoices) when one of the incoming invoices has a PO attached to it and the PO has an expensed rebate. After you perform any of these functions and an expensed rebate is involved, you can look at the invoice in APEI and see the rebate APEIG records on the GL Distribution window. In APEI, if you change quantity or price on a PO line that has an expensed rebate, or delete that PO or PO line altogether, APEI automatically adjusts the associated APEIG records on the GL Distribution window.
Note: Because some rebates are based on actual cost, the Final Update setting
Cost
that can be set to
Received Cost
or
Match to Cost
(i.e., use Invoice Cost) will have an effect on how those rebates are calculated. If there is a difference between received cost and invoice cost, and if the rebate is calculated based on actual cost, then the rebate and the GL Distribution records for the rebate will be calculated according to this Final Update setting. Note that the AO-Documents-Purchase Orders-Accounting option,
Value Inventory at:
, contains the default for this
Final Update
setting. APEGE uses this default setting and you cannot override it. However, you can override it in APEI on the Update/Reconciliation Options window displayed when you select
Edit
/
Final Update
. Changes to this setting should be made right after entering
APEI rather than waiting until just prior to running Final Update. This is because when you add a PO with an expensed rebate to an invoice, APEI uses the current setting of this field when it calculates the rebate amount that it uses for the GL distribution records. If you change the setting, APEI does NOT recalculate
GL distribution amounts for any invoices that have POs with expensed rebates. In order to avoid issues resulting from differences in rebate amounts based on actual cost, it's recommended that you set this setting in AO and then do not change it when running APEI. This way both APEI and APEGE will always use the same setting.
Locked Invoices Checked Before Multiple Suspend, Delete or Dispute (G)
When you select multiple invoices in the APEI Invoice browse and right-click and choose
Suspend
/
Unsuspend
,
Delete
, or
Dispute
/
Undispute
from the shortcut menu, the system will now check the lock status of the selected invoices. If one or more of the selected invoices are locked by another user, the message “
One Invoice Was Locked By Another User, Could Not Be Changed
” will appear. Any selected invoices that were not locked, will be changed.
“Quick Fill” for Reference in APET and APEI (G)
If you have previously set up references in SA Setup Table Values (SASTT), then in AP Entry Transactions
(APET) or AP Invoice Center (APEI) you can type a period or pound sign (. or #) followed by the number that has been set up and then tab out of the
Reference
field. The system fills the
Reference
field with the
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 10 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
text that is in the SASTT setup. There is also a new lookup button in APET to make entering the reference easier.
Manual Payment Allowed Without an Invoice (G)
There are situations when you need to prepay a vendor when there isn’t an invoice to apply the payment to. Prior to this enhancement, in the graphical interface, you were required to apply a manual payment to an invoice in APET. Now, the graphical interface also allows you to enter a manual payment without having to apply it to an invoice. A new Unapplied Amount window appears that displays the unapplied amount and allows you to enter a reference invoice and reference text for the miscellaneous credit that will be created.
This mirrors the functionality in the character interface.
Performance Improvements in APRA (B)
Performance improvements have been made to the AP Transaction Activity Report.
Pay Through Bank Validated in APRC and APEP (B)
If you enter a value for the
Pay Through Bank
option in either AP Cash Receipts or AP Pay Invoice Due, the system now validates whether the bank is active to prevent CK type transactions in Accounts Payable from being created with an invalid bank. If the bank is invalid, the report fails and an error, “
Bank Not Active
(5361)
”, is sent to the report log for the company.
APRC Vendor Not Paid if Current Credit Balance (B)
If you set option 9,
Pay Vendor If Credit Balance
, to
No
, and option 15,
Credit Balance by (C)urrent or (T)otal
, to
C
urrent, and the vendor has a current credit balance they will not be paid, regardless of your setting for option 8,
Take Misc. Credits
. The current miscellaneous credit(s) and any current invoices due will be displayed in the Future column on the report.
If you set option 15 to
T
otal, all credits will be applied to the balance due the vendor, even if the credit has a future due date.
If your AO-Vendors-Invoice Defaults (APAO in CHUI) option,
Take Terms Discount on Misc Credit
, is not selected, APRC considers all miscellaneous credits to be current, regardless of their due or discount dates. If the AO option is selected, then the due and discount dates are considered when determining whether the miscellaneous credit is current or future.
E-mail Address Field Length Changed in APSF (B)
An e-mail address entered in the
field in AP Setup Federal Tax 1099 is now limited to 50 characters.
This adheres to the limitations for this field set by IRS Publication 1220.
Lookup by City or State in APSS (G)
You can now perform searches in the AP Setup Vendor Ship To lookup window by city or state without entering a customer number like you can in AP Setup Vendor. Formerly, if you attempted to search by state or city, a message appeared stating that you needed to search by customer number, phone number, or zip code.
Note:
The qdkeyindex.p
program will now populate the arss.keyindex and apss.keyindex fields. You must run this conversion program during your upgrade to version 6.0 to populate the ARSS and
APSS Progress word index.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 11 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Accounts Receivable
Posting Cash in Foreign Currency (B)
When you post Miscellaneous Cash in AR Entry Cash Receipts Entry (ARECE) to a bank with foreign currency, ARECE posts the CR amount in the currency of the bank, not the domestic currency. That is, the amount that you enter is the foreign currency amount and that amount will display when you look at the transaction in CR Entry Check Center. The GL postings are always in domestic currency, so the GL amounts will have the currency exchange rate applied to the amount that you enter.
Keyboard Shortcut Enabled for Cancel (G)
You can now press
Ctrl+c
to invoke the
Cancel
button in ARECE.
Open New Journal Option Keeps ARECE Open (G)
When a journal is closed in ARECE, this closes the ARECE window and exits you from the function. A journal must be open at all times when you are in ARECE. Now, if you need to close a journal and open a new one, you can select the new option,
Open New Journal
, from the Journal menu, or press
Ctrl
+
J
. When you close a journal using this option the message, “
The Journal nnnnnn was successfully closed
” appears. When you click
OK
, the Open Journal window appears and you can click
OK
to proceed with the new set of transactions.
New Processing Option in ARECE for Split Payments (G)
A new AR Entry Cash Receipts processing option,
Load Bank from Customer on Split Check
, accessed from the
View
menu allows you to enter a customer number and have the system assign the bank using the bank from the customer’s AR Setup Customer record. Your selection is retained between sessions. If you do not select this option, the system behaves as it did before this enhancement where you must type the bank number.
If
Load Bank From Customer on Split Check
is selected and you tab to the
Bank
field and designate a bank manually, and then go back to the
Customer
field and specify a customer, the system does not override the
Bank field. If the bank you specified is not the same as the bank for the customer you specify, the following message, “
Warning: Bank is Not Customer’s Bank (8321)
”, appears. You can update the bank number or leave it and press
Update
to process.
Partial MC Not Allowed in ARELE and ARELI (B)
AR Lockbox Update and AR Entry Cash Receipts Entry do not support partial miscellaneous credits, so partial miscellaneous credits are no longer allowed in AR Lockbox Import (ARELI). If the import file attempts to process a partial MC, the transaction is suspended with the error message—"
Not Found:
Edit or charge back
". Also, if you attempt to overpay or underpay a miscellaneous credit or debit memo in ARELE, the message, “
Apply Amount Must Be Equal to Original Amount
” appears.
Highlight Function in ARIC-Transactions Based on Due Date (G)
You have the ability to highlight transactions by choosing
Highlight
>
Active
,
Inactive
,
Period 1
,
Period 2
,
Period 3
,
Period 4
, or
Period 5
from the shortcut menu in AR Customer Inquiry-Transactions. To be consistent with dates used for the aging buckets, highlighting is now done based on due date rather than invoice date.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 12 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
ARET Process Change for Consistency (G)
I n order to make the graphic interface consistent with the character interface, after entering an invoice in
AR Entry Transactions and clicking
Update
, the proposed GL accounts appear in the Browse window. If you click
X
or choose
Exit
or
Exit All
from the
File
menu, the message "
Do You Wish To Cancel All
Work
" appears. If you click
Yes
, the system exits AR Entry Transactions as it did before the message was added, without writing out the accounting records. If you select
No
, you will remain in AR Entry
Transactions so you can complete your updates and close the journal.
You can turn off this prompt, just for the current AP Entry Transactions session, by selecting
Do not ask me this question again
and clicking
No
.
Ordering/Taxing Information Available for Customer and Ship To in ARIC (G)
Prior to this enhancement, if you designated a ship to on the Customer window in AR Customer Inquiry and clicked the
Order/Tax
button, it wasn’t clear if the information that appeared on the Order/Tax window reflected the AR Setup Customer or AR Setup Customer Shipto records. Now if you designate a shipto on the Customer window, a toggle button appears on the Order/Tax information window to allow you to view either the customer or shipto-related order and taxing information. This is labeled
Toggle Ship To
, or
Toggle
Customer
.
Credit Card Transactions Clearly Identified in ARIT (C)
When viewing payment transactions in ARIT it was not clear when a credit card was used. The following changes have been made in ARIT for credit card transactions:
•
If the payment type is a credit card, the Invoice # column will display an invoice # (like noncheck lines do).
•
The Tp (type) column will still display CK. This is the standard display for a type 7 record.
•
If the payment type is a credit card, the Ref column will display CC instead of CK#.
•
The Check # column will display the description of the payment type as set up by the customer
(probably something like Mastercard or Visa) to help clarify the credit card type.
This change will affect what is displayed for type 7 transactions entered/applied before this enhancement, but because the underlying ARET data is not changed, a Q&D is not required.
Additional Level II Fields Passed to ICVERIFY Enterprise (B)
The Level II data passed to ICVERIFY Enterprise in ARRCM now includes Customer PO, Tax Amount,
Freight Amount, and Discount.
ICVERIFY Purchase Card Level 1 Data Changed (B)
The data submitted by AR Credit Manager (ARRCM) for level 1 data for the ICVERIFY for Windows credit card processor has been changed so that it no longer sends an extra entry for FSAL, RETN, and SALE type transactions where the payment type in SASTT is
Prompt for Category
. This extra entry caused the flat file interface between SX.enterprise and ICVERIFY to fail.
Backorder Processing with Payflow Pro (B)
Because Payflow Pro allows only one authorization per sale, backorders will now tie correctly to the original authorization without double-billing the credit card. A new authorization will be created when the backorder is filled.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 13 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Additional Level III Fields Passed (B)
The product category from the sales order will now be included in the Level III data passed to the credit card processor by ARRCM. If no category was entered on the order, the product category from IC Setup
Product will be passed. This will provide the data for the Commodity Code, which is required for Level III transmissions.
In addition, the VAT Tax Rate and the Product Description field lengths have been adjusted to meet
ICVERIFY limitations.
Disputed Invoices No Longer Aged (B)
Disputed invoices are no longer aged in ARRP. When the report is run by due date, disputed invoices now appear in the period in which they were disputed. When the report is run by invoice date, disputed invoices appear in the period of the invoice date.
ARRP Option 2 Ignored if Option 1 = No (B)
Option 2,
As Of Date
, on the AR Period Analysis Report, will now be ignored if option 1,
Print As Of?
, is
No
.
ARSC/ARSS Tax Window Field Placement (G)
The fields on the ARSC and ARSS Tax window have been rearranged to allow more room for the
State
,
County
,
City
,
Other1
and
Other2
descriptions. These field’s drop-down boxes have been widened.
Send by Fax or Email Setting Requires Existing Setups (B)
In the graphical interface, when you choose
or
Fax
for the customer or vendor
Send By
options in AR
Setup Customer-eComm, AR Setup Customer Ship To-EDI, AP Setup Vendor-eComm, or AP Setup
Vendor Ship From-EDI, the system checks that the appropriate setups exist. In the character interface, when you specify E(
M
)ail or
F
(ax) for the
Send By
option in Accounts Receivable Setup-Electronic Data
(ARSE) or Accounts Payable Setup-Electronic Data (APSE), the system checks that the appropriate setting exist.
If the appropriate values are not set up, on of the following new messages appear:
•
“
Fax Invalid - No Fax Phone Defined (6771)
”
•
“
E-Mail Invalid - No E-Mail Address Defined (6772)
”
In AP Setup Shipto-EDI and AP Setup Ship From-EDI, when you toggle between the
Customer
and
Ship To
Send To options, and the Send By option designated is
Fax
or
, the option is cleared to force you to make a new selection.
New AO Option Controls Ship To Service Charge Default (B)
A new option is available in AO-Customers-Services that controls how the ship to
Service Charge
setting defaults when a new shipto record is added or copied, either in AR Setup Shipto, Bid Prep, Job
Management, or via an SX.api call. If you select
Yes
for the option,
Ship To Service Chg
, the ship to Service
Charge is selected (defaults to
Yes
); if you select
No
, it is not selected (defaults to
No
); if you select
From
Customer
, the ship to Service Charge setting defaults from the AR Setup Customer record.
Lookup by City or State in ARSS (G)
You can now perform searches in the AR Setup Customer Ship To lookup window by city or state without entering a customer number like you can in AR Setup Customer. Formerly, if you attempted to search by state or city, a message appeared stating that you needed to search by customer number, phone number, or zip code.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 14 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Note:
The conversion program qdkeyindex.p
will now populate the arss.keyindex
and apss.keyindex
fields. You must run this program to populate the ARSC/APSS Progress word index.
Update Order Changed in ARECE (B)
If you choose to resequence miscellaneous credits in AR Entry Cash Receipts Entry, unused portions of existing miscellaneous credits or unapplied cash credits are kept active under a new sequence number. If these credits are never used in full, they may reach an expiration point and be lost to the customer. To prevent a possible loss of miscellaneous credits or unapplied cash credits, the update logic in AR Entry
Cash Receipts Entry has been changed. Instead of applying the amount of the check first against selected invoices, the credits selected will be applied first, then the check. An unapplied cash record is created for any unused portion of the check. This new update order is applied regardless of the AO setting,
Resequence Unapplied Credits
.
Credit Card Interface
Interface and Compliance Enhancements (B)
Considerable enhancements have been made to the Credit Card Interface in version 6.0. These include the following features and updates. For more information, refer to the Credit Card Enhancements 6.0 GUI and CHUI Project Reviews and the Credit Card Encryption Compliance 6.0 Project Review posted on the
Documentation page of Infor365.
•
Payment Type expanded to two digits - allowing up to 99 payment types
•
Multiple merchant setup and interface capabilities
•
Level I, II, and III processing enhancements
•
Enhanced reporting for credit card balancing
•
Auto Tendering enabled during Back Order Fill and Shipping Feedback
•
Order approval validation in Clippership
•
Support for Non-refundable Credit Card (immediate sale) transactions (GUI)
•
Credit card validations and warnings added to Tendering, Invoice Processing and PO printing
(GUI)
•
Tendering for Zero Quantity Shipped orders (GUI)
•
Credit card history display for RMs (GUI)
Note:
SX.enterprise version 6.0 no longer provides a credit card processing interface to WebAuthorize. If you currently use WebAuthorize, you must upgrade to ICVERIFY Enterprise Edition. For Payflow
Pro users, the TCP/IP Manager has been upgraded to version 1.2. This is the required minimum version in order to run Payflow Pro with SX.enterprise v6.0.
EDI
Inovis Certified
Infor ERP SX.enterprise has been certified to work with Inovis's EDI translation service. No changes were made to the standard EDI documents within SX.enterprise. However, EDI global maps have been developed by Infor's professional services organization that can be customized to work with your company's specific requirements. Contact your Infor sales representative or EDI support representative for assistance.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 15 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
EDI 845in Phase II (B)
The following enhancements were added to support the EDI 845 process:
•
EDEPC matching logic provides easier matching of vendors, products, and customers based on the information contained in the flat file.
•
Error messages have been removed because they are not longer applicable.
−
Multiple Vendor Identification Segments Sent (6750)
Multiple Customer Identification Segments Sent (6751)
Multiple Item Identification Segments Sent (6752)
•
A
Vendor Product Group
option has been added to SA Setup Table Values. Use this option to set up an association between a vendor and a rebate/sub rebate type, price type, product category, or product line that is used in ED Entry Processing Contract Pricing when processing an 845in flat file.
•
In PD Entry Mass Maintenance, you make modifications to an existing data set. When you are working with an existing rebate data set, the end date can be changed. If you change the End
Date to the year 2050 or later, a warning message, “
Expiration Date Removed (6788)
”, appears and the date is removed. This warning also appears when you are running ED Entry
Processing Contract Pricing and the end date is 2050 or later.
For more information on this enhancement, refer to the 6.0 project review EDI 845 Inbound Vendor
Rebates (SPA Phase II) found on the Infor365 support portal Web site.
EDI 867out Includes Component Sequence Number (B)
The EDI 867out flat file now stores a unique sequence number for BOD kits, prebuilt kits and VA kits in the
Line Item record at position 297. For more detailed information, refer to the mapping appendix in the EDI
Coordinator Guide found on the Infor365 support portal Web site.
EDEPA Includes ICSC Catalog Record Verification (B)
EDI Entry Purchase Order Acknowledgement Processing (EDEPA) now includes IC Setup Catalog (ICSC) records when validating and matching product numbers when processing the EDI 855in flat file. The new product validation hierarchy follows:
•
SX.enterprise product number
−
IC Setup Product (ICSP)
IC Setup Warehouse Product (ICSW)
IC Setup Catalog (ICSC)
•
Vendor product number
−
IC Setup Warehouse Product (ICSW)
IC Setup Catalog (ICSC)
•
Bar Code Number
−
IC Setup Extended Cross-Reference
•
UPC3 and UPC4
−
IC Setup UPC Numbers
For more detailed information, refer to the mapping appendix in the EDI Coordinator Guide found on
Infor365.
POEPP Displays ***Do Not Ship** in EDI 850out for BL POs (B)
If you are processing EDI 850 outbound flat files in PO Entry Processing Print POs (POEPP), the header shipto address section for a blanket PO will have *** Do Not Ship *** instead of shipto address information.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 16 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
New Information on EDEPC Report (B)
When processing a Date Only transaction that is set to Expire (EX) or Cancel (CC) specific rebates, the report as been modified to edit the existing rebates to see if they can be expired. If the rebates’ selected
Start Dates are beyond the transactions specified Expire Date, then a new error will display with a count of the number of rebates not updated due to the edit:
End Date Can Not be Before Start Date (5757) Count: 10
The counter will display when the transaction is a Header Level Date Only transaction.
If the transaction is an Item Level Date Only transaction where the report is updating or attempting to update specific items within a rebate range, then the report will display a message within the specific item section:
** Date Only Change **
This will notify the operator that no other changes have been applied; just the date. If the Start Date is prior to the transaction’s Expire Date, then the error as listed above for the Header Only transaction will display in the Item Section of the report, but without a counter since it is a specific Item Section:
End Date Can Not be Before Start Date (5757)
Product Edit Messages Revised (B)
When items are imported in EDEPC and a catalog item is found in IC Setup Catalog, but no product record is found in IC Setup Product, the message “
WARNING: This is a Catalog Item (6431)
” now displays.
Previously, this message stated “
WARNING: This is a Non-stock Item (6726)
.” This is just a warning as catalog records can be entered in the rebate setup.
When neither a catalog nor a product record is found, a more descriptive message, “
Error: Nonstock
Product Not Allowed
” displays. Previously, this error was “
Invalid Product: <product name>
”. This is a hard stop error, as nonstocks cannot be entered in the rebate setup.
Net Rebate Defaults from APSE Net Down To (B)
EDEPC can now calculate a net rebate amount based on a ‘Down To’ value as a flat rate. If the inbound
Down To fields from the vendor are invalid, it uses the default setting in the AP Setup Vendor-eComm
‘Net’
Rebate Down To
field. If the Down To field is Flat Rate and the rebate type is Net, the Discount Multiplier will be loaded into the PD Setup Pricing-Rebates (PD Setup Rebates in CHUI)
Rebate Amount
field. The report will reflect the amount as “Rebate Amt: xxxxxxxxx”.
Also, a default will be set for the Transaction Type for the item level transaction. This is the PAD segment field that allows for SD-Ship/Debit or DS-Drop Ship. The SD will create a PDSP record as a Whse record and DS will be a drop. If the PAD segment was not entered in the flat file transaction set, it will still build a
Whse record, and the Transactions Type will now default to SD.
Unit Default Corrected for Catalog Records (B)
If a catalog product’s unit cannot be validated via IC Setup Extended Unit Conversion (ICSEU)-Product
Specific Unit, or SA Setup Table Values (SASTT)-Unit Conversion, EDEPC will check the
EDI Unit of
Measure
field in ICSEU and SASTT-Unit Conversion-Extended. If a single match is found (not multiple units with the same EDI Unit of Measure), then the unit will be validated. Once the item unit is validated, the Unit Conversion value is used to convert the amount sent in the interface down to a 'each' (single) unit level. Once the single level is set, then the report will find the Special Price/Costing value of the item
(ICSP). Once the SPC value of the item is found, then the 'each' (single) value of the amount is converted to the SPC unit value. The PDSR (rebate) record stores the amount in the SPC unit of the item. For a
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 17 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
catalog item, it is treated like a nonstock item and there is not an SPC conversion; it is an ‘each’ price regardless of the SPC settings in ICSC.
Contract Revision Number Added to EDEPC Report (B)
The Contract Revision Number is now displayed on the EDEPC report. All contract data has been moved to the right-hand, lower section of the header screen. It will include the contract number and the contract name. Previously, just the name was displayed if both the number and name were sent.
Sub-rebate Type Processing Changes (B)
New error messages were added for sub-rebate type validation. If the inbound Rebate Type is valid, the
Sub-rebate Type will be validated in the following manner:
•
Verify the AO-Products-Rebates
Rebate Sub Types
option is selected. If not, error “
Sub Rebate
Type Not Allowed (6769)
” is displayed on the report.
•
Next, verify the sub-rebate type against the SA Setup Table Values (SASTT)-Rebates
(Product Sub Type) values. If no SASTT match, error “
Sub Rebate Type Not Set Up in
System Table (4182)
” is displayed.
•
If SASTT found, but vendor does not match, error “
Vendor Does Not Match Vendor on Sub
Rebate Type Record (6770)
” displays.
If the sub-rebate type cannot be validated, no updates will be made to the rebate in PDSP or PDEM.
Processing Continues if Multiple Identifiers Encountered (B)
If EDEPC encounters multiple identifiers for an item, it will continue processing until it can validate one of the product identifiers. The hierarchy for verification will be: vendor product, product, bar code, UPC individual section, UPC full number, and finally, NAED number. If multiple identifiers are sent and all fail, the report will show only the first error based on the hierarchy. If a group code and item identifiers are sent by your vendor, only the group data will be validated. Vendors can submit only group identifier data (Type
2, 3, 4, or 5 records) or item identifier data (Type 1 records), not both.
UPC Number Validated Based on Section Definition (B)
The UPC number will be validated by sections based on the AO-Products-Alternates/UPC UPC Structure
Length
settings. If individual sections are sent, EDEPC will check the UPC lengths for each section. If the section exceeds the AO setting, the message “
Section x is Longer Than the Defined Section
Length
” will appear. The report will show the sections based on the AO Length settings.
Note:
The report will still check sections 3 and 4 first (Vendor and Product) to validate the UPC number.
Matching POs With Backorders Follows New Logic (B)
POs with backorders are now matched in EDEPI using the following logic:
•
The invoice quantity is compared to the uncosted quantity on each backorder. If exact match is found, it uses that PO suffix for the EDI invoice.
•
If no match, the invoice quantity is compared to all PO backorders with an uncosted quantity greater than the invoice quantity, and will use the suffix where the difference between the two is smallest compare to all other backorders.
EDEPI Includes Whole Order Discount (B)
ED Entry Processing Invoices (EDEPI) can now read in a whole order discount from the EDI 810 inbound document in the invoice header record, beginning at position 215. The whole order discount is associated
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 18 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
with a purchase order. The system stores that value on the Accounts Payable batch files. The whole order discount amount from the EDI 810 inbound document is always allocated by dollar and cannot be changed to unit or manual like you can in AP Transaction Batch Entry (APEBT). The whole order discount on the
EDI documents will also be read in through APEGE (GUI) and will be applied during APEI to cost the PO.
For more detailed information, refer to the 6.0 mapping document in the EDI Coordinator Guide found on the Infor365 support portal Web site.
EDEPI and APEGE Enhanced for Processing More Than 999 Invoices (B)
ED Entry Processing Invoices (EDEPI) and AP Group EDI Invoice Processing (APEGE) have been modified to better handle EDI input files with more than 999 invoices
If there are more than 999 invoices in the edi810_i.dat
input file, EDEPI puts the first 999 into a batch with the name you enter when you run EDEPI. Subsequent invoices go into a new batch of up to 999 invoices and is named by appending a number to the end of the batch name. The second batch name has a "
2
" appended to the end, the third batch has a "
3
" appended to the end, etc.
Note:
Because EDEPI limits the batch name to eight characters, if the batch name that you designate when you run EDEPI has eight characters and more than 999 invoices in the input file, the second batch name is created by overlaying the last character of the batch name with a "
2
". For example, when you run EDEPI, the batch name is " ediabcde
". Your input file has 1500 invoices. EDEPI puts the first 999 invoices into batch " ediabcde
" and then creates a new batch " ediabcd2
" for the additional 501 invoices.
Each new batch gets its own journal number. The set numbers for the new batch start over with one (1).
EDEPI prints the name of each new batch on both the report and the log file.
AP Group EDI Invoice Processing (APEGE) has been modified in the same way. Because APEGE doesn't assign journal numbers or set numbers, the group sequence number gets reset to one (1) with each new batch. By limiting the number of invoices to 999 in an APEI group, when Final Update (or APEGU) is run, you should end up with no more than 999 set numbers on the APEI journal.
SMRVT Allows Inclusion of VA Components (B)
The SM Product Transfer/Resale – EDI 867 (SMRVT) report produces an electronic document that informs the vendor which of their products have been sold and to whom, and which products have been transferred to what branch. An option,
Include VA Components
, has been added to SMRVT (default is
No
) so VA products can be included in the output. Because there may be situation where a customer is using Value
Add for rework as well as installation services, a field (
EDI 867
) has been added in VA Entry Transactions at the header-level that allows you to exclude or include the components from designated orders.
If you select
Yes
for the
Include VA Components
option in SMRVT, components are included in the generated document if the following conditions are met:
•
The component must be sourced in OE Entry Transactions to a VA order.
•
The Value Add Entry Transactions header option,
EDI 867
, must be selected for the VA source order.
•
The VA section line component must be from an inventory component (IN) or internal process
(IT) type section.
•
The VAESL component for a stocked component must have the same IC Setup Warehouse
ARP vendor as the SMRVT vendor selection. Or, for a nonstock component, the source vendor must be the same as the SMRVT vendor selection.
Note:
When you are selling a fabricated item that already exists in stock, if a VASP record also exists for the fabricated item, the component list from the VASP record is used to report components on the
SM Product Transfer/Resale-EDI 867(SMRVT) report. It is possible that the VASP record could be
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 19 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
modified between the time that the VA fabricated items were built and when they are sold on an
OE order. If this is the case, the component list reported on the SMRVT reflects the VASP record and may not be the exact items used when the fabricated item was actually built. For example, a component may have been purchased from a different vendor.
SMRVT EDI 867out Price for VA & Kit Components is Zero (B)
The price associated with a VA or kit component will be now be zero in the EDI 867 outbound flat file. This field is at position 168 on the Line Item record.
Event Manager
Gross Margin Calculations (B)
In Order Entry, the margin calculations can be based on ordered or shipped totals depending on orderspecific factors. In most cases, the margin calculations are based on the order's shipped totals if the total quantity shipped is greater than zero. If none of the lines on a Stock Order (SO) can be shipped, the margin calculations are applied to ordered totals. The Event Manager margin trigger currently follows the
Order Entry logic to determine a system-calculated margin and margin percent.
Some distributors consider the margin calculation to be more realistic when it is always based on the full ordered amount versus factoring back orders and special orders into the equation. In addition, reflecting margin totals off shipped totals can delay the timeliness of the Event Manager notification.
This enhancement adds an administrative option that enables the Event Manager margin trigger to use ordered totals exclusively or let the system calculate margin based on ordered or shipped totals, as it currently does today.
This administrative option has been implemented for the graphical and character interfaces. It is limited to the header-level margin calculations. The line-level margin calculations will continue to utilize the system to determine the use of shipped or ordered line totals. This option will not affect historical or existing event records. Order Entry and Event Manager operating procedures remain the same.
The Event Manager header-level triggers that will calculate margin and margin percent according to the
AO-Documents-Sales Orders-Processing
Event Manager Trigger: Calculate OE Header Margin Based on
option are:
Trigger Name
oeetfinish oeet-hdrchange oeetcancel oeepi-excptns oerf-promisepd oepicktickets
Short Description Function
Finish OE order
Header Fields Change
Cancel OE Order (Lost Business)
Print Invoice Exceptions
OE Entry Transactions
OE Entry Transactions
OE Entry Transactions
OE Entry Processing Invoice
Processing
FTC Compliance Promise Date Past Due OE FTC Compliance Report
Print Pick Tickets OE Entry Processing Pick Tickets
In SX.enterprise character, this option is in OE Administrator Options (OEAO) F6-More Options (this is a new screen accessed from the OEAO screen).
Note:
The OEET-Cancel OE Order (lost business) function is also a header level trigger for OE, but when an order is made lost business, the totals of the order become zero. The margin calculation
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 20 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
will be set to zero to resolve situations where the whole order and special discounts of the order were driving the margin negative. Since the order totals are zero, there is no basis for tracking a margin trigger off lost business orders; therefore, this trigger is not controlled by the new AO option.
Event Notification Uses Salesreps’ or Operator’s E-mail (B)
The notification of a credit hold event now obtains the e-mail address for submitting an e-mail notification to the inside or outside sales rep from the following records in this order: OE Setup Salesrep (GUI) or SM
Setup Salesrep (SMSN)(CHUI); logged in operator’s SASO; if neither is available, an error is received.
General Ledger
GLIA Sort Order Labels Changed (G)
The Sort Order labels were changed to
Ascending (By Period)
and
Descending (By Post Date)
to clarify the results of choosing one or the other. If you select
Ascending (By Period)
the transactions will be listed in calendar period order. If you select
Descending
, they will be sorted by posted date.
Set # Field Size in GLIJ Increased (G)
The
Set #
field in GL Journal Inquiry now allows a five-digit set number value.
Storage Areas Added to GLSF Record Setup (G)
A Storage Areas section has been added to the GL Setup Financial Statements-Detail Record Setup window that displays when setting up horizontal account records.
Inventory Control
ABC Stratification Enhancement (G)
In 2003, Infor implemented the ABC Inventory Evaluation enhancement in conjunction with Dr. Lawrence of the Texas A&M (TAMU) Industrial Distribution School. Since then, Dr. Lawrence and his team at TAMU have refined the logic which replaces the original ABC functionality with ABC Stratification. This enhancement includes the following new features to ABC ranking in SX.enterprise:
•
Refined calculations for evaluating inventory
−
Added an additional rank, D, to drive more precise stratification
Updated the Sales logic (top 60% are A, next 20% are B, next 10% are C, and remaining
10% are D)
−
Updated the GMROI logic (those products with GMROI over 200% are A, GMROI over
100% and less than 200% are B, GRMOI over 0% and less than 100% are C, and the remaining are D)
−
Replaced the Quantity (sales quantity) logic by Hits (number of lines the product appears on). The top 60% are A, the next 20% are B, the next 10% are C, and the remaining 10% are D)
•
A new function, IC Setup ABC Stratifications, was created where you can fine tune the formulas that are used to determine stratification values
−
Set up separate stratification logic by warehouse
−
Define separate formulas for stock and order-as-needed products
Adjust the weighting of GMROI, Sales, and Hits ranks
−
Set the relative importance of each rank when determining a final rank
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 21 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
−
Set the percentage of spread among each stratification rank
•
Enhanced the IC Administrator ABC Inventory Evaluation report
•
Updated IC Setup Replenishment
•
Updated IC Setup Warehouse Product Ordering
•
In IC Setup Replenishment, you can use the resulting stratification values to set inventory controls using the existing Detail Rank records functionality.
•
IC Administrator Month End Planning will use the IC Setup Replenishment setting and ABC
Stratification ranking instead of hits ranking if you have selected the
ABC Stratification
option for the
Perform Detail Ranking?
field.
For more information on this enhancement, refer to the 6.0 project review ABC Stratification found on the
Infor365 support portal Web site.
ICAMU Exception for Extended Lead Time (B)
A new exception has been created when you run IC Administrator Month End Processing (ICAMM) with the option
Use Ext LT on Seas/Forward/Trend Items
set to
Yes
, and there is insufficient history. The exception, “Extended Lead Time Warning”, is printed for products that do not have at least 12 months of history available for this usage calculation. ICAMU will use the history that is available, but will display the exception warning. Usage months, extended lead time months, usage rate calculated, and usage history will be displayed for the Extended Line Detail on the ICAMU Exceptions tab. The usage rate is the rate that is calculated before any trending is applied.
OAN products Can Be Included in Rolled Up Usage (G)
Beginning in version 4.4.001, if the company parent warehouse usage is set to roll up usage in IC Setup
Replenishment-Usage, order-as-needed (OAN) products in the selling warehouse are not included when calculating parent warehouse usage.
Now, you can determine whether you want OAN product usage included in the usage rollup for the parent warehouse on a product-by-product basis when you are using the rolled up usage method. The default is not to include OAN products.
To include OAN products, select the
Roll Up OAN Usage
field in IC Setup Warehouse Products Ordering.
The field only appears if the parent warehouse usage is set to
Rolled Up Usage
, the warehouse product status is
OAN
, and the ARP is
Warehouse
or
Central Warehouse
. A
Roll Up OAN Usage
field also appears in
IC Setup Product Lines Ordering and provides the default for the field when you are setting up warehouse products associated with a product line.
There is a new field,
Roll OAN Usage
, in IC Administrator Exception Processing Center Mass Updating. If you select
Roll OAN Usage
, only the records that meet the criteria (ARP = W and are OAN products) will be updated.
Transfer Usage Subtracted if Using Rolled Up Usage (B)
When your IC Setup Replenishment (ICSR)-Usage, Parent Whse Usage option,
Rolled Up Usage
, is selected, exceptional usage will be calculated during ICAMM by subtracting transfer usage from normal usage. If this usage is higher than the AO-Products-Replenishment
Low Usage Threshold
,
Qty
or
Dollars
setting, then it will be compared to the prior usage as defined in ICSR and override usage will be calculated, if needed.
Rebate Type and SubType Added to IC Administrator Exception Processing (G)
To accommodate a change in the rebate type or subtype on a large number of products, rebate
Type
and
SubType
have been added to the Manual Product List and Mass Update functions of IC Administrator
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 22 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Exception Processing. You can use the rebate
Type
and
SubType
fields to create a manual product list including only those products with the rebate type and subtype that you want to modify. After selecting records that you want to update from the list, you can indicate a new rebate type and subtype. The IC
Setup Warehouse Products record for all selected product records will be updated with the rebate type and subtype you indicated on the Mass Update window.
ICAMU Exception Creation (G)
ICAMU exceptions are created from IC Administrator Month End Processing (ICAMM), IC Administrator
Usage Rate Update (ICAMR), and during the update from the PO Entry Buyers Control Center (POERA) or IC Administrator Exception Processing Center (ICAMU) Usage Analysis tabs. Exceptions will no longer be created when running ICAMA or during a POERA or ICAMU Usage Analysis tab refresh, or during a
POERA Increase/Decrease Review Cycle Days.
New Message and Warning in ICAMU Mass Update (G)
When a rebate type or rebate sub-type is updated in IC Administrator Exception Processing Center Mass
Maintenance and the vendor for the product (IC Setup Warehouse Product record) does not match, then the update will proceed, but a warning message appears. This message appears in the "Message" column of the browse in IC Administrator Exception Processing Center (ICAMU). Additionally, a pop-up message
—"
Update Exceptions/Warnings Occurred. See Highlighted Products
"— appears when there is one or more errors or warnings
.
Foreign Cost Will Always Be Last Cost in ICEAM (G)
In IC Adjust Core Master (ICEAM), the implied core value from a foreign vendor PO will be the last foreign cost from IC Setup Warehouse (ICSW)-Costs. It will no longer use the AO-Products-Costs, Core Costs
Assignments setting during PO Receipt of Inventory (POEI) when ICEAM is updated with the implied core cost. This should always be in foreign currency. GL will be updated in domestic currency.
Serial/Lot Quantity Change Not Allowed in ICEAR (B)
You cannot change quantities for serial or lot products in IC Entry Adjustments Reallocation (ICEAR). If you enter a serial or lot product and click refresh, the message, “
Cannot Change Quantities For
Serial/Lot Products Within This Function (6779)
”, appears. Use OE Entry Transactions (OEET) or OE Entry Shipping Feedback (OEES) to make changes.
Count Sheet Update Edits Added (B)
You can no longer add inactive or labor items to an existing cycle or physical count sheet in ICEPE. The message, “
Product Must Be Active - ICSP (5602)
” or “
Labor Product Not Allowed (5628)
” will display. You will also be prevented from adding a product to the count sheet if the warehouse and run number combination is invalid. The message, “
No Records Exist for This Warehouse and Run #
(4741)
” will display.
Labor Products No Longer Allowed in ICEPE (G)
When adding a product to an existing run in IC Entry Count Entry, labor products cannot be added. If you attempt to add a labor product, the message, “
Labor Product Not Allowed (5628)
”, appears.
Product Descriptions Added to ICEU (G)
A new column has been added to the IC Entry Unavailable Inventory browse. The column ‘Desc’ will show the product description (lines 1 and 2).
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 23 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
ICIAF Now Displays OE Orders for Transfer Kits (G)
IC Product Availability Inquiry Future Availability tab and ICIAF now display OE orders for BOD Transfer kits. A transfer kit is a BOD kit that you can transfer from one warehouse to another within your company.
Transfer kits allow you to enter a build on demand kit on a sales order for a customer in one warehouse, automatically create a tie to a warehouse transfer and work order, fabricate the kit in another warehouse, and ship the fabricated kit to the sales order warehouse for shipment to the customer.
ICIAW Available Amount Now Shows Two Decimals (C)
The amount displayed in the Available column in IC Wareouse Availability Inquiry (ICIAW) now includes two decimal positions. This will accommodate any amounts that are fractional, e.g., half a case or .50. This change was made to SX.enterprise character only.
Kit Warning Message in ICIP (G)
When you access the Component view in IC Product Inquiry and you view a product that was a prebuilt or build-on-demand kit but is no longer designated as a kitted product in IC Setup Product, a new pop-up message, “
Warning: Product Not Set Up as Kit in ICIP
”, appears. Any components that were set up in the past will continue to appear in the Browse window; this change will only impact ICSP records changed after you have upgraded.
Return Outs for Dirty Cores Update On Hand (B)
The On Hand amount displayed in IC Transaction Inquiry (ICIT) in character, and IC Product Inquiry-
Transactions (ICIP) in GUI, will now include Return Out (RO) transactions for dirty core products, as these adjustments should affect inventory.
Cap’d Addons and WO Discounts Included in Cost (B)
The amount shown in the
Cost
field on the Transaction Detail window in ICIT and ICIP-Transactions will now include capitalized addons and whole order discounts if they were on the purchase order during receiving. This will accurately reflect the ‘landed’ cost of a product after receiving.
New Options in ICRIN Clear Ordering Controls for OAN/DNRs (B)
Two options have been added to the IC Needs Analysis Report (ICRIN) to allow reporting on Order-asneeded and Do Not Reorder products, as well as clearing the ordering controls for these types of products.
The first,
O)AN, D)NR, B)oth OAN/DNR, A)ll Products
, can be set to review O)rder as needed only products,
D)o Not Reorder only products OAN/DNR only products (B)oth, or A)ll products. The second new option,
Clear OAN/DNR Ordering Controls
, indicates whether to clear the ordering controls for OAN/DNR products in IC Setup Warehouse, based on the selection of the first new option. The following fields in ICSW will be cleared:
Line Point/Min
,
Order Point/Min
,
Order Quantity
, and
Order Method
.
Order-as-needed and Do Not Reorder products should generally not carry ordering controls as these are considered surplus items when they have a quantity available to sell. If there are ordering controls, and the on hand quantity is below line point, or any of these ordering controls, the item may not show as surplus.
These options on the ICRIN provide a quick way to clear ordering controls for OAN and DNR products in your inventory.
For more information about the enhancement to clear ordering controls for OAN/DNR products, refer to the
Do Not Reorder/Order-as-needed Controls 6.0 Project Review available from Infor365.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 24 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Whole Units for Long Term Surplus Quantities in ICRIS (B)
The resulting quantities for long term surplus stock on the IC Surplus Stock Report (ICRIS) are now expressed in whole units instead of including decimal point extensions. Because you can only ship whole units, decimal point extensions are misleading if you use long term surplus information to distribute to other branches, return to vendors, etc.
Update PD If Special Price/Cost Changes in ICSC (G)
If the Special Price/Costing values are changed in IC Setup Catalog-Pricing (ICSP), you will now see the following question: “
Apply Special Price/Cost Changes to PD?
”. If you click
Yes
, active pricing records for Customer/Product, Customer Price Type/Product, and Product based on a dollar value in PD Setup
Pricing (PDSP) will have the SPC factor applied to the price. Product rebate records with a dollar rebate or net rebate down to a flat amount will have the SPC factor applied to the price. Price sheets for the catalog product will have the SPC factor applied to both the prices and costs. Catalog records are not company specific, however, these changes will only be applied to the Price/Discounting records for the logged in company. If you click
No
, then no updates will be made to Price/Discounting records.
Note:
This change is only applicable to the GUI interface; it was already working this way in the character interface. However, a change was made in character to apply the SPC factor to any GUI price sheets that might exist if a catalog record is updated in character.
New Edit Check and Error Message in ICSEC (B)
In IC Setup Extended Product Cross Reference (ICSEC), records are now checked to prevent a cross reference from being set up as a cross reference to itself. An error, “
Product May Not Be Cross-
Referenced to Itself (4924)
”, appears and the cross reference is not created.
Lookup Added to ICSOC Cust Type (G)
The
Cust Type
field in IC Setup Customer Grace Period is now table driven and a lookup has been added.
You can click on the lookup button or use
Ctrl
+
L
functionality to lookup a customer type when you are entering a record type that uses that field.
Lookup added to ICSP Stocking Unit (G)
To make the graphical interface consistent with the character interface, a lookup has been added to the
Stocking Unit
field in IC Setup Product.
UPC Code Assigned to Different Products or Same Product-Different Vendors (G)
To make the graphical interface consistent with the character interface, you can now assign a single UPC code to different products or to the same product with a different vendor in IC Setup UPC Numbers (ICSV).
ICSW B/O Open Option Applied Differently to Tied WTs (B)
When a tied warehouse transfer (WT) is created, the following situations determine whether the line can be back ordered:
•
If the order is Ship Complete or Tag and hold, then the WT can be back ordered.
•
If the order allows back orders, then the WT will allow back orders.
•
If the order line is tied to a DO WT, then the WT will allow back orders.
•
If none of the above conditions are met, then the IC Setup Warehouse Description
B/O Open
(
B/O Open WT
in CHUI) option is honored.
•
If a WT is created in WT Entry Transactions or through the WT RRAR, then the
B/O Open
(
B/O
Open WT
in CHUI) option is honored
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 25 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
ICSW WM Flag Cannot Be Changed if Product on Count Sheets (B)
The
Whse Mgr
option in IC Setup Warehouse Product (ICSW)-Required cannot be changed if that product exists on a count sheet in ICEPE and ICEPP.
Option to Clear Ordering Controls When Product Changed to DNR/OAN (B)
If an item’s status is changed in IC Setup Warehouse Products (ICSW) to
Order As Needed
or
Do Not
Reorder
, a new popup appears: “
Clear Ordering Controls
”. If you click
Yes
, the following fields will be cleared in the ICSW record:
Line Point/Min
,
Order Point/Min
,
Order Quantity
, and
Order Method
. This will ensure that the product’s quantity available to sell is immediately considered as surplus and will be handled in the same manner as other surplus products are. OAN and DNR products should generally have a zero on hand balance; however, when you change an existing product’s status to OAN or DNR, it may carry a balance, as well as ordering controls. If the ordering controls remain, and the on hand quantity is less than line point or any of the other controls, it may not show as a surplus item. It is recommended that you clear the ordering controls in this case, unless you have a specific reason not to for the selected product.
For more information on this enhancement, refer to the DNR & OAN Controls 6.0 Project Review, available on Infor365.
Security Controls and WT Tie Added for Ordering DNR Products (B)
Multiple security controls are now available to control the entry of Do Not Reorder (DNR) products in Order
Entry.
•
An authorization point has been added to prevent operators from entering an DNR item where the quantity ordered is greater than the quantity shipped unless they have ‘grant authority’.
The authorization point, OE No Tie For DNR Short Ship, should be reviewed to determine which operators receive grant authority.
•
A new Event Manager trigger has been added to notify your managers when DNR items are entered in OEET but there is insufficient stock to fill the order, no tie is created, and the order does not backorder. This is a short-ship situation, and the event will trigger to notify the manager of the short shipment. At the same time, the operator will see a message warning them that only the shipped (available) quantity will be supplied to the customer. If there is no stock available for the DNR item, the message “
Quantity Available is Zero and Will
Not be Reordered for Future Shipment (6786)
” appears.
In addition, you can now tie a DNR product to a Warehouse Transfer in Order Entry when there is not enough quantity available to fill the order in the ordering warehouse, but other warehouses can fill the order. A new option,
Allow Do Not Reorder Whse Transfer Tie by Company/Region/Neither
, controls whether you can sell DNR products from all warehouse in your company, from warehouses within a region, or not at all. In SX.enterprise character, this option was added to the new F6-More Options screen accessed from
OE Administrator Options (OEAO).
For more information, refer to the DNR & OAN Controls 6.0 Project Review available on the Infor365 support site, Documentation tab.
Whse Zone No Longer Required in ICSW (G)
The
Whse Zone
on the IC Setup Warehouse Products (ICSW) WL Setup screen is no longer required when you are setting up or maintaining TWL information in ICSW GUI.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 26 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
INSA
New Kit Smoothing Option (B)
A new option,
If Kit, Perform Kit Smoothing
, has been added to the IN Sales Extract (INSA). It will be used when the option,
Kit Lines (K)its, (C)omponents, (B)oth
is set to
C
omponents. If you set this option to
Y
es, kit component costs, prices and net amounts will be adjusted (smoothed), so that they add up to the kit line totals. If you select
N
o, actual component costs, prices, and net amounts are reported to saline.exp
, which may not match the total of the line.
Order Header Order Type Loaded in Position 38 (B)
The value loaded into position 38 of the saline.exp
file will revert to previous versions of INSA, where the
Order Type from the order header is loaded. This is the value from the internal record oeeh.ordertype, and contains the two-character order type code of SO, DO, etc. A change made in SX.enterprise 5.5 had changed this value to be populated by the order type from the order line (oeel.ordertype), but that has been reversed by this fix to now use the order type from the order header.
Job Management
New SASO Option to Update Printed POs in JMEC (G)
A new SASO option,
Allow/Do Not Allow Update to a Printed PO from JEMC
, allows you to control whether an operator can update a printed PO. The default is to not allow updates if the PO is printed.
If the SASO setting is
Allow Update to Printed PO from JMEC
, the error message, “
PO Already Printed,
Change will Require Reprint, OK to Continue?
” appears when you attempt to update a printed PO in JM Entry Change Order. If you click
Yes
and make changes, when you click
Final Update
the system may not be able to automatically make all the changes. If this is the case, the message—"
Warning: Unable to
Update Printed PO. Manual Updates are Necessary. See Error Messages for Details
."— appears
to
alert you to scroll through the messages on the bottom of the window or on the message viewer. If you click
No
, the Line Update window does not appear.
If the SASO setting is
Do Not Allow Update to Printed PO from JMEC
and you attempt to update a printed
PO, the message—“
PO/WT has been printed, adjust manually (5844)
”—appears. If you attempt to add a line and the PO is printed, the system looks for another non-printed PO to add the line to. If all POs are printed, the system creates a new purchase order.
The tied purchase order number, suffix, and stage have been added to the browse window in JM Entry
Change Order. There is a hyperlink from the Tied PO column to PO Order Inquiry.
Can Print Cancelled PO (G)
When you cancel a purchase order with a vendor, it is good business practice to send a printed copy of the cancelled purchase order to the vendor. You can now use the
File
,
Print POs
option in JM Entry Release
Jobs to print a cancelled purchase order and send it to a vendor. Cancelled POs can also be printed in
OEET and POET.
When printing a cancelled purchase order from JM Entry Release Jobs, the auto stored report @po+whse uses the PO Report Demand Print options to print the purchase order. The printed purchase order is clearly marked as cancelled with ***CANCELLED*** printed across the top and bottom of the document.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 27 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
JMEPC and JMEPV Use Ship To from Job (B)
JM Entry Processing Customer Quote and JM Entry Processing Vendor Quote now use the ship to address from the JM Entry Transactions job record. Before this enhancement, when the Ship To default address information was changed in JM Entry Transactions, the customer quote and vendor quote did not use the address information from the job.
Product Line/Vendor in JMER Validated (G)
When you update a product line in JM Entry Release Job-Extended, the vendor number from that window will now be used in the validation process to prevent invalid product lines
Enhanced Consistency Between Sales Reps in OE and JM (G)
Salesreps in JM are now treated more like they are in OE. JM Entry Transactions, JM Entry Transactions
Customer List (for a specific customer), and JMER Release Header sales representative defaults honor the
Allow OE Salesrep Override
settings (
Inside
,
Outside
,
Both
, or
Neither
) in SA Setup Operator. If an operator does not have security to change the sales representative, the field will not be enterable. If an outside sales representative does not default, the field is enterable regardless of operator’s security.
The sales representatives in JM Entry Transactions will now default like they do in OE Entry Transactions.
•
AR Setup Customers/AR Setup Customers Shipto sales representatives (inside and outside)
•
If AR Setup Customers/AR Setup Customers Shipto inside sales representative is blank or there is no customer, then the SA Setup Operator default sales representative will default for the inside sales representative.
•
If there is no SA Setup Operator default sales representative, then the operator’s initials will default for the inside sales representative.
If there is no customer number (name only) on the Customer List in JM Entry Transactions, the sales representatives default, and both will be enterable regardless of the operator’s security.
When you are copying an order in JM Entry Transactions using the
Copy
option from the
File
menu, if you change the customer, the sales representatives on the JM Entry Transactions header (not those on the
Customer List window) will default again.
If you change the customer when releasing a job In JM Entry Transactions Release, the sales representatives will default again in the Job Release-Header Defaults window.
Kit Production
Serial or Lots Now Printed on KPEP (B)
Serial or lot numbers assigned to a work order component will now be printed on the KP Entry Print Work
Orders report.
Component Search Time in KPIW Improved (G)
The search process in KP Work Order Inquiry has been restructured to improve the time it takes to find components. Changes were made to the files accessed, and the search process is now performed on the appserver, with a record limit applied. The option,
Set Record Count Limit
, is now available from the
Window menu in KPIW-Criteria that will be applied when performing a lookup against the
Component
field.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 28 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Miscellaneous
New License Expiration Messages (B)
For consistency between the graphical and character interface, Infor ERP SX.enterprise license expiration messages have been changed to the following:
•
“
License will expire in xx days. Please contact Infor Support to renew your license.
”
•
“
License expired. Please contact Infor Support to renew your license.
”
•
“
One or more Other Licenses will expire in xx days. Please contact Infor
Support to renew your license.
”
•
“
One or more Other Licenses expired. Please contact Infor Support to renew your license.
”
•
“
TWL License will expire in xx days. Please contact Infor Support to renew your license.”
• license.
”
•
“
TWL License expired. Please contact Infor Support to renew your license.
”
New Warning Message in CAM for Method Changes (G)
A new warning message box with the text, “
You changed the methods. Save those changes?
“ appears if you click
Cancel
and you made changes to a contact’s method of contact information and didn’t click
OK
to save those changes. At the prompt, click
Yes
to save the method changes or
No
if you don’t want to save them.
Blank Columns Exported to Excel as Text (G)
When exporting transactions to Excel in any function that supports the
Load to Excel
capability, columns that have all blank field values will be exported as text. Columns with blanks and numbers only, are exported as numbers. Columns that have blanks, numbers and any character, are now exported as text.
This will resolve the problem where columns with blanks and numerics were not exported as numbers.
Enhancements to Message Ticker (G)
You can now limit the number of messages that appear on the message ticker and their order they appear.
A new option,
Display scroll items
, with a default of 20, determines how many messages appear. If more message exist than the number that is specified on the Message Options window, a final message, “
More
Undisplayed Activities Exist
” appears with a hyperlink to the operator’s activity list on the Message
Ticker. You can also change the order the messages display by selecting one of the new radio set options.
If you select
Most Recent
, which is the default, the order the messages appear is from most recently added to oldest. If you select
Oldest Undisplayed
, the order is from oldest to newest.
Improvements to Copy Display Function in Entry Functions (G)
When you select
Edit
,
Copy Display
in any GUI entry function, such as AR Setup Customer, and then select fields for copying, the copy function will assign the internal field names to fields with no labels (e.g.,
Address2, State). If a label appears twice on the screen, a number will be appended to the label in the
Select Fields to Copy window, and will be copied with the field’s value. You must select the
Include Labels
option for labels to be included in the copy.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 29 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Infor Open SOA Enablement of SX.enterprise (B)
SX.enterprise joins other Infor ERP applications by building its on-ramp capabilities to enable integration with MyDay, the role-based interface that offers you significant value-add in software and data utilization.
The Infor Open SOA (Service-Oriented Architecture) enablement involves the following SX.enterprise features that allow BODs (business object documents) to be activated:
•
SA Administrator ESB Noun Setup (SAABN)
•
SA Administrator ESB Initial Load (SAABI)
Once activated, up to six roles can be supported with data drilldown capabilities to SX.enterprise data.
These roles include Sales VP, Sales Manager, Purchasing Manager, Purchasing Agent, AR Manager, and
AP Manager.
For more information on Infor MyDay for Infor ERP SX.enterprise, contact your Infor sales representative.
TWL Order Information Available in SX.enterprise (G)
You can now view header and line information for orders and receipts processed in a TWL warehouse in the graphical interface of SX.enterprise. The Whse Logistics view is available in OE Order Inquiry, PO
Order Inquiry, WT Transfer Inquiry, KP Work Order Inquiry and VA Order Inquiry.
For more information on this enhancement, refer to the 6.0 project review WL Inquiry found on the Infor365 support portal Web site.
Order Entry
Field Size Changes to OEDC & OEDS (B)
Field size restrictions from Direct Route have been applied to fields in the OE Direct Route
Cust/Vendor/Whse Setup (OEDC) window. The
Size
,
Symbol
, and
Color
fields are now only 2-characters in length. The format for the
Latitude
field has been increased to support a 2-digit decimal. Also on the OEDC and OE Direct Route Setup Defaults (OEDS) window, increased the size of the
Fixed Time
to 3 digits, changed the
Unload Rate
field from an integer size of 5 digits, to a decimal size of 10 digits, and increased the
Equipment Code
field to 25 characters. Note: A conversion program will run during the SX.enterprise
6.0 upgrade to handle the changes to the
Unload Rate
. The other field changes were to format only; no dictionary changes were required.
Option 9 Ignored for Certain Order Types in OEEPA (B)
Option 9,
Use Ordered Quantity Only
, will be ignored for Quote, Future, Standing, and Blanket order types, and orders with a disposition of Ship Complete or Tag and Hold. Acknowledgments will always be printed based on the ordered quantity for these order types, not the shipped quantity.
VID Not a Valid Print Option for Stored Exception Reports (G)
You can no longer set up a stored report with an exception report printed to ‘vid’ for option 9,
Printer for
Exception Report
. The message, “
Video Output Not Allowed (5000)
” appears.
Cores Conversion GL Account Updated for Market Value Changes (G)
When the market value of a dirty core changes between the date a Core Buy Return Order is entered and the date it is invoiced, the difference will be debited to the Core Conversion GL account during invoice processing. This is in addition to the current process where the price of a dirty core changes and it is different from the market value; the difference is debited to the IC Cost Adjustment account during invoice processing.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 30 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
OEES Quick Ship Stage Label Changed (G)
The label of the stage field has been changed from
Orig Stage
to
Order Stage
on the OEES Quick Ship dialog to more accurately reflect the current stage of the selected order.
Nonstock Enhancements (G)
Several changes and enhancements were added to SX.enterprise that are specific to nonstock product management.
You can now assign a bin location to nonstock records that is stored with the nonstock set in ICEAN. This bin location is set in POEI, WTEI, or ICEAN, and is printed on sourcing documents and can be updated as nonstocks are moved within the warehouse.
Other features added in this project include:
•
New Mass Update function in ICEAN that mirrors the Inventory function, but allows multiple nonstock items to update a single ICSP/ICSW record
•
New available quantity and tied quantity balances (can be viewed on lookups, ICEAN, OE
Entry)
•
New sort and search options in ICEAN for quantity values and broken ties
•
New Non Stock Count Report
•
New Quantity lookup in Non Stock Product lookup
•
Foreign vendor currency support in Non Stock window
•
Enhanced security for overriding nonstock quantity and ICEAN Bin Location
Along with the nonstock-specific enhancements, you can now create order-as-needed - nonstock products
(OAN-NS) as an ICSW record. This allows the tracking of a nonstock item within the stock inventory system and provides all of the standard stock item processing capabilities such as physical/cycle counting, quantity on hand balances, special price/cost setup, unit of measure conversions, and serial/lot control.
Some of the specific features added for OAN-NS management include:
•
Creation of OAN-NS items from the OE Non Stock window
•
NEW SASO security settings to control the ability to create OAN-NS items, or to change the
ICSW status to or from OAN-NS
•
Ability to inactivate OAN-NS products via SAAIP
•
Ability to reactivate them ‘on the fly’ in Order Entry
This is not a complete list of the enhancements added for nonstocks and orer-as-needed nonstock items.
For more information, refer to the Nonstock Project Overview and Order-as-Needed - Nonstocks Project
Review on Infor365.
Cancelled PO Can Be Printed (G)
When you cancel a purchase order with a vendor, it is good business practice to send a printed copy of the cancelled purchase order to the vendor. You can now use the
File
,
Print POs
option in OE Entry
Transactions to print a cancelled purchase order and send it to a vendor.
When printing a cancelled purchase order from OE Entry Transactions, the auto stored report @po+whse uses the PO Report Demand Print options to print the purchase order. The printed purchase order is clearly marked as cancelled with ***CANCELLED*** printed across the top and bottom of the document.
OE and JM Excel Import Includes Cross-reference Logic (G)
You can now import vendor part numbers and they will be cross referenced automatically during the Order
Entry and Job Management Import from Excel. The cross-referenced products must be set up in IC Setup
Extended Product Cross Reference (ICSEC).
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 31 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
The spreadsheet import logic for OE Entry Transactions and JM Entry Transactions now processes the following product cross-reference types:
•
Customer product (IC Setup Extended Product Cross Reference)
•
Bar code (IC Setup Extended Product Cross Reference)
•
Supersede (IC Setup Extended Product Cross Reference)
•
Vendor product (IC Setup Warehouse Vendor Prod field)
•
Interchange (IC Setup Extended Product Cross Reference)
•
Auto pricing (IC Setup Extended Product Cross Reference
A valid customer is required in the OE or JM import file. If the cross reference is successful, the requested product field is populated with the original incoming part number. If the part number cannot be crossreferenced, it will come in as a nonstock product, as it did in previous functionality. Substitute products are not supported.
The Excel Import Browse window now has standard shortcut menu options (Adjust Columns and
Move/Resize Columns) and also accepts 50 characters in the Description column.
Rebate or Price Recalculated if Direct Order Changed (B)
If a Direct Order or DO line on a Stock Order contains a rebate, and the vendor, product category, or cost is changed in OEET, the rebate will be recalculated. If the rebate amount does change, and the price is based on the rebated cost or margin, the price will be recalculated.
Internal Weight Field Size Increased (G)
An internal original weight field size has been increased to five decimals. This field was used to store the weight value on a line if the value was changed. Rounding errors due to the decimal size have been resolved. Any changes made to a line will show a correct
Total Weight
amount on the order header.
Floorplan Window Displays When Copying Order (B)
When you copy an order to a floorplan customer, the Floorplan dialog window now appears so that you can select the option to floorplan that order and choose the finance company. Previously, no Floorplan window displayed for an order copy and this increased the chance of the order being invoiced improperly.
User Interface Change in Copy Functions (G)
The Copy Order, Quote, or PD window in OEET has changed so that it is easier to avoid making multiple copies of the same OE by mistake. When you fill in the top section of fields and click
Continue
, the
OK
button changes to read
Copy+Exit
. Click
Copy+Exit
to make the copy of the order and close the dialog box.
If you do not click
Continue
, the
OK
button does not change, and clicking
OK
will close the dialog box without the OE being copied.
Alternatively, to make further copies, use the
Copy
button, then when you reach the final copy, use
Copy+Exit
to make the last copy and close the Copy Order, Quote, or PD window.
Note:
This enhancement also applies to the copy functions in PO Entry Transactions, WT Entry
Transactions, SW Entry SRO Transactions, and SW Entry Claims.
CS Copy Not Allowed if Order Has a Disposition (B)
If the order or quote you are copying from has a disposition (for example, Ship Complete) in OE Entry
Transactions, you will not be able to copy that order to a counter sale. If you attempt to copy an order with a disposition, the message, “
To proceed with Copy to a Counter Sale order, Disposition must be blank (6670)
” appears.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 32 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
OEET Tendering COD Check Box Reflects Header Terms (B)
The COD field in OE Entry Transactions Tendering is now exclusively driven by any changes made to the the terms in the order header. If you have authority to change the terms from COD to on account, the tendering
COD
check box will be cleared even if the AR Setup Customer Credit Sales Status is COD Only
(ARSC Sell Type is D for CHUI). The Sales Status option,
COD Only
, will only be used to generate a warning if terms are changed to non-COD.
Counter Sales Orders on Hold Must Be Tendered for Balance Due (B)
When a Counter Sale order is created and is put on hold, you will no longer receive the message “
Charge
Remaining To Account
”. However, the Counter Sale must be tendered if there is an amount to be paid or refunded. When a Counter Sale is put on hold, the expected action is to send the lines to lost business and create an SO order, and thus the amount to be tendered on the CS order will go to 0 and you can complete the order. The SO order would have the status placed on hold and go through the regular approval process. Otherwise, the Counter Sale order must be approved and tendered as usual. Additionally, the
“
Charge Remaining to Account
” message will no longer display for cash only and COD customers as well.
Disposition Field Active for a CR Order (B)
The
Disposition
field on a CR order now defaults to disposition on the customer record but can be changed. Before this change, the
Disposition
field was not active.
Sourcing Multiple Line Items at One Time (G)
You can now select multiple line items in OE Entry Transactions at once and tie them to a single purchase order or warehouse transfer. A new
Multi-Line Sourcing
option is available on the shortcut menu in the Line
List to perform multi-line sourcing, reducing the time you had to spend previously sourcing line items one at a time. In addition, a new column,
Related Order #
, has been added to the OE Entry Transactions Line List and OE Inquiry Orders Detail views. In each of these views, you can select multiple line items and choose
Sort
,
Related Order #
from the shortcut menu to sort the line items by related order number. To view the source document in PO Order Inquiry or WT Order Inquiry, select a single line item in either OE Entry
Transactions or OE Inquiry Orders and click the
Related Order #
column heading. The line item can be a stocked, nonstock or special, but it cannot already have a tie.
Tendering a COD Cash Sale (B)
In the graphical interface, if tendering is required (for example, an order for a C.O.D. cash customer), but you need to get back to the line list to modify the lines, click
Cancel Work
. This is the only way to get out of the Tendering window when tendering is required. Once you make changes on the Line List window, you are forced back to Tendering. If you send all lines to lost business, then you are allowed to exit the
Tendering window without tendering. If not, you must tender the amount due before leaving OE Entry
Transactions.
In the character interface, if you type a zero in the
Down Payment
and
Amount
fields on the Tendering screen, you can press
F7-Line Items
and to access the Line Items screen and make changes. If there is an amount on the Tendering screen, the message “
Can Only Change Functions if Not Tendering
(5780)
” appears and you cannot access the Line Items screen until you type zero in those fields.
Taxable Status is Validated for Orders Copied to Same Customer (B)
When you copy an order to the same customer, the taxable status of the new order is now determined by the customer’s current AR Setup Customer (ARSC) or AR Setup Customer Shipto (ARSS) settings.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 33 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Notes Import via Excel for Orders and Purchase Order Increased (G)
The size of the notes and comments data set that is imported to OE Entry Transactions or PO Entry
Transactions via Excel is increased to allow up to 1000 characters. Previously, notes imported via Excel that were longer than 24 characters resulted in duplicate notes for an order.
Vendor Notes Added to MRU Menu (G)
The
Vendor Notes
option has been added to the Most Recently Used (MRU) menu accessible by rightclicking on the
Vendor
field in the Non Stock window in OEET. The MRU menu is now available from the
Product
,
Vendor
, and
Warehouse
field on the Non Stock window.
Vendor Product Included in Product Autolookup (G)
The Product autolookup now includes the Vendor Product code when performing its search and there is more than one warehouse product record with the same Vendor Product code. When multiple records are found, the appropriate keys data will be added to the Lookup window to enable the search. These keys can also be manually entered in the
Keys
field.
Note: This requires that you rebuild the keys index during the 6.0 upgrade by running the qdwordbuild.ant
conversion program.
Automatic Print Turned Off When Report is Faxed (G)
When you have selected the
Automatic Print
option in File, Print, and you print a report to Fax, the
Automatic Print
option will be turned off. You cannot print a report to Fax and do automatic printing. After faxing the document, you must select the
Automatic Print
option again before any automatic printing is done.
Limits for Changing a Product on a Tied Line (C)
If you attempt to change the product on a line that is tied the message “
The Related PO/WT/WO/VA # Can
Be Removed but not Changed (5843)
” appears. You must manually remove the tie before you can change the product. Note: Removal of a tie may also be limited by two authorization points: Can Not Break
Ties Against Processed Ord, and Can Not Break Ties Against Open Orders. Broken PO or WT ties may be tracked with these Event Manager events: OE Can/Del line with PO still there, and OE Can/Del line with
WT still there.
BOD Kits Can Only Be Returned to Stock (C)
When you attempt to return a Build-on-demand kit to unavailable inventory, the message “
A Build On
Demand Kit Can Only Be Returned to Stock (6079)
” will appear and you will be prevented from making that selection. Previously, the system did not prevent you from doing this.
Search Time Improved for Customer Lookup (G)
The Customer lookup logic has been improved to make this faster when using the contact’s first and last names.
Credit Card Swipe Enabled for ROAs and Refunds (B)
You can now load credit card information via a swipe device when you enter a Received on Account or
Return transaction in OEET. When you are in the Received on Account window,
Payment #
field, or the
OEET Tendering window posting an RM order, you can swipe the credit card that is to have the credit applied.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 34 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
ICSW B/O Open Option Applied Differently to Tied WTs (B)
When a tied warehouse transfer (WT) is created, the following situations determine whether the OE line can be back ordered:
•
If the order is Ship Complete or Tag and hold, then the WT can be back ordered.
•
If the order allows back orders, then the WT will allow back orders.
•
If the order line is tied to a DO WT, then the WT will allow back orders.
•
If none of the above conditions are met, then the IC Setup Warehouse Description
B/O Open
(
B/O Open WT
in CHUI) option is honored.
•
If a WT is created in WT Entry Transactions or through the WT RRAR, then the
B/O Open
(
B/O
Open WT
in CHUI) option is honored
Optional Product Qty Can Be Entered as Decimal Amount (G)
When entering the quantity of an optional product in OEET, you can now type the amount as a fraction, in other words, with a decimal value. For example, you can type
2.5
in the
Quantity
field on the Optional
Products window to reflect a portion of the unit, such as a case.
New Back Order Edits for BOD Kits (B)
Edit checks have been added to OE Entry Transactions to prevent all the components in a build-ondemand kit from being back ordered.
•
“
6780 - Can't Backorder All Components
”
•
“
6781 - Cannot Delete - All Other Components are Backordered
”
Search OEIO for Orders Based on Disposition (G)
A new field,
Disposition
, has been added to the Criteria view of OE Inquiry Orders. Use this field to limit the orders that appear to those with the disposition you select. The default,
<ALL>
, includes orders with all dispositions, which is how the inquiry worked prior to this enhancement.
Net Cost & Margin Amount Based on Quantity Shipped (G)
The values displayed in the
Net Cost
and
Margin Amt
fields in OEIO Line Detail-Extended and the OEET
Line or Extended windows will now be based on the quantity shipped. Previously, these values were based on the quantity ordered, which was incorrect.
Pricing Worksheet Changes for Foreign Customers (B)
Corrections were made to the prices displayed in OEIP and other functions for foreign customers. The
Cost+ % and Margin displayed on the OEIP Pricing Worksheet in the GUI interface will calculate price based on the foreign cost. This correction was also made to the OEET Pricing Worksheet. In OEIP CHUI, when calculating the Cost+/Margin %, the Cost on the main screen will no longer be divided by the exchange rate every time a Worksheet calculation is performed. Also, any customer rebates (based on price) will be reflected in the margin calculation on the Pricing Worksheet The Foreign Exchange Rate and
Foreign Cost will now display on the OE Master List Report (OERM), Extend section. Finally, we added the ability to 'store' or create the Price Discount Quote record directly from the GUI OEIP Pricing Worksheet for a foreign customer.
Pricing Honors AO Promo Price Default Option (B)
When both a promotional price and a regular price exist, the price that appears in OE Customer Pricing
Inquiry (OEIP), or in any window in Order Entry where the promotional window does not appear, is based on the AO-Documents-Sales Orders-Entry Options option,
Promo Price Default
, for GUI or the OEAO
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 35 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
option,
Promo Price Default when Operator Does Not Have Access
option, for CHUI. In earlier versions, the system used the lower of the two prices.
Security Enforced in OEIR (G)
The security logic has been improved so that users with a SASO security level 2 (inquiry only) for OEIR will not have access to the Quick Approve and Approve All functions.
Price/Discounting
PDEM Processes for All Customer Pricing and Rebates Records (G)
Prior to this enhancement you were only able to process a subset of customer pricing records and Vendor on Sales rebate records in PD Entry Mass Maintenance. You now have the ability to perform mass maintenance on all the customer pricing record types and rebates that are available in SX.enterprise. The customer pricing types now include:
•
Type 3 - Customer Price Type/Product
•
Type 4 - Customer Price Type/ Product Price Type and Customer Price Type/Rebate type
•
Type 5 - Customer
•
Type 6 - Customer Price Type
•
Type 7 - Product
•
Type 8 - Product Price Type
The Vendor on Sale rebate types now include:
•
Type 4 - Product Line rebates
•
Type 5 - Product Category rebates
All Vendor on Purchase and Customer rebate types are now included:
•
Type 1 - Product rebates
•
Type 2 - Rebate Type rebates
•
Type 3 - Product Price Type rebates
•
Type 4 - Product Line rebates
•
Type 5 - Product Category rebates
You can now leave the Browse window even if you have invalid data in your record set. So, if you are reviewing the data and do not know the correct value, you can exit out of the row and out of the function without being forced to enter a valid value. Records are validated against PD Setup Pricing records when you click Update. Any lines with errors appear and a new Browse column, Error Message, is populated with a description of the error so you can correct it.
For more information on this enhancement, refer to the 6.0 project review PDEM Pricing/Rebate Record
Processing found on the Infor365 support portal Web site.
ED Entry Processing Contract Pricing (EDEPC) was also updated to allow processing of Vendor or Sale rebate type 4 and 5 records through PD Entry Mass Maintenance. For more detailed information on the
EDI 845 functionality as it relates to PD Entry Mass Maintenance, refer to the EDI 845 Inbound Vendor
Rebates 5.5 Project Review with 6.0 Revisions found on the Infor365 support portal Web site.
Source Drop-down Added to PDEM Set Name Lookup (G)
The
Source
field on the Set Name Lookup window has been relabeled and changed to a drop-down combo box field type. It is now labeled
Record Type (Source)
and will show the list of customer pricing and rebate record types available. The drop-down for Record Type has also been added to the PDEM File, and the
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 36 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
File, Import Excel With New Records functions. The types that display on all windows are limited by the
AO-Products-Pricing
Enable Price Types
selections.
Vendor Required For Import (G)
When you create new rebate import records in PD Entry Mass Maintenance by choosing
Import Excel with
New Records
from the File menu, you will now be required to enter a vendor number when the import records are used to create 'Vendor on Purchase' or 'Vendor on Sale' rebate records.
Default Product Not Required For Import (G)
The Default Product is no longer required when you select
Import Excel with New Records
and import product records in PDEM. If this is left blank, the individual product numbers from the spreadsheet will be used and validated. If it is entered, all records will be imported using the entered product number.
Terms Will No Longer Be Applied to Negative PDER Lines (B)
When a receipt amount on a PD Entry Rebate Reconciliation line is negative, terms discounts will no longer be applied. Negative rebate transaction should not have terms. Terms will still be used to calculate due date.
Changes to PDSP Search for Customer Pricing Records (G)
When searching for Customer Product Line records in PD Setup Pricing, if either the
Vendor
or the
Prod
Line
fields are blank, all vendor/product line combinations are returned. Before this enhancement, if the
Vendor
was blank, all vendor/product line combinations were returned, but if the
Product Line
was blank, no data was returned. Because the vendor and product line combine into one field in the lookup there must be a value in both fields; the system cannot filter the fields separately
.
New Expired Active Option Added to PDSP (G)
PD Setup Pricing and OE Customer Pricing Inquiry have been changed to allow you to include or exclude active PDSC or PDSV records with expired end dates. A new option,
Expired Active
, has been added to the browser. If this option is selected, then PDSP records which have an End Date less than current date
(but still have the
Active
flag set) will be included in the search results. If this option is unchecked, then the search results will not include those records. In the case of PDSR records for rebates, the option is labeled
Expired
since the Active flag is not set. The browsers have also been changed so that if an Inactive record is displayed, the Record #, Inactive and End Date columns are highlighted for easier visibility. When an expired or expired active record is being displayed, the Record # and End Date columns are highlighted.
Pricing Modifiers Enhancement (G)
You can now create pricing modifiers in a new function called PD Setup Pricing Modifiers (PDSPM) and associate them with a pricing record in PD Setup Pricing (PDSP). The Pricing Modifiers enhancement adds a new element to the standard SX.enterprise pricing logic by offering an additional layer of price adjustments based on sales rankings and location demographics such as company ranking, warehouse ranking, dollar movement (class), and stratification groups. This new feature also associates the pricing modifiers with pricing records so that product prices can be calculated according to the pricing modifier.
While the pricing modifier setup is only available in GUI, the pricing modifier will be applied in every function where the pricing routine is run, GUI and CHUI. For more information, refer to the 6.0 project review titled Pricing Modifiers, available from the Infor365 support Web site.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 37 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Purchase Order
POEI Includes Stocking Unit of Measure for Unavailable Quantities (G)
PO Entry Receipt of Inventory-Detail-Extend window now includes the the stocking
Unit
of Measure next to the
Unavailable Quantity
field.
Options Default for Receipt Report Run in POEI (G)
When you run the Receipts report from POEI, the printer name will default from the operator’s SASO record and the following options will default from the System Report Items PO Reports Receiving Update record:
•
Ln Sort: (L)n #, (P)rod, (V)endProd, (D)esd
•
Only Print PO Lines with Recv Qty
•
Page Break by PO #
New Exception in POEPC (B)
A new exception has been added to PO Entry Convert POs (POEPC) to alert you when a PO has been created with a nonstock line and a tie needs to be added. So if the
Order or WT Required When Non-stock
Item Entered on PO
option is selected in AO, and a blanket release is created for a nonstock item, an exception displays under a new section—Non-stock Line - Tie Required. This section lists the PO number, line number, vendor, order date, product, and description.
No Order Control Designated in POERA RRAR for OAN Products (B)
Order-as-needed (OAN) Products will no longer be classified as Critical Point, Below Order Point, or
Negative Purchase Net Available in Buyer’s Control Center, PO Entry Replenishment Action Acceptance.
Note:
If you are upgrading from a prior version, existing RRAR records will not be changed. New RRAR records will be created correctly.
Tie Information Added to POERA (G)
Buyers use the Buyers Control Center (POERA) to prioritize the fulfillment of OE and WT demand requests. Information about document ties and the promise date from the associated line provides critical information that did not appear on the Buyers Control Center Acceptance window. Now, the Buyers Control
Center Acceptance Line Items window includes five new columns that provide that information: Tied Order
#, Tied Ord Suf, Tied Line #, Tied Seq #, and Tied Promise Date for nonstock (NS) or order-as-needed
(OAN) products. The promise date reflects the Warehouse Transfer ship date, the Order Entry or Value
Add promise date, or the kit enter date. These fields are blank if the line is not a tied line. The Doc column indicates if the tie is from an OE (o) order or WT (t) order (existing functionality).
Company and Warehouse Rank Added to POERA (G)
When you are working with the PO RRAR, you might want to view fast moving products first so you can quickly review or accept them. Two columns,
Cono Rank
and
Whse Rank
, have been added to Buyers
Control Center-PO Entry Replenishment Action Acceptance Line Item browse window to display IC Setup
Warehouse Products company and warehouse ranking values, and you can select a new shortcut menu item
Sort,
if you want to sort products by
Line Number
(default),
Company Rank
, or
Whse Rank
.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 38 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Product Line List in POERP, POEVI, and POEVP Only Displays Line (B)
The Product Line List window is used to enter a list of product lines that you want to process in PO Entry
Program Release (POERP), PO Entry VMI Initial Product Data Load (POEVI) and PO Entry VMI Product
Activity Data EDI 852 (POEVP). Once you selected a product line, the display included vendor, warehouse and vendor information. This information came from the first product line in the database, not necessarily the product line you selected, which was confusing. Since you have access to the vendor, warehouse, product line description and buyer information when you use the lookup to select the product line, those fields have been removed from the Product Line List window and only the product line identifier appears.
E-Mail Address Defaults From Vendor Record in POET (B)
If you choose
as the print method in PO Entry Transactions (POET), the e-mail address on the AP
Setup Vendor Ship From record or, if there is not a AP Setup Vendor Ship From e-mail address, the e-mail address from the AP Vendor Setup record defaults. If neither of these records has an e-mail address designated, the operator's e-mail address defaults like it did before this enhancement.
Import Purchase Orders from Excel in POET (G)
You can now import data from a Microsoft
®
Excel spreadsheet into PO Entry Transactions to create new purchase orders. This allows you to quickly process data received from a vendor that is formatted correctly, import that data into PO Entry Transactions, manipulate the imported data, and then create purchase order lines and orders automatically. The following standard cross-reference logic is supported when importing data from the Excel spreadsheet:
•
Vendor product (IC Setup Extended Product Cross Reference)
•
Bar code (IC Setup Extended Product Cross Reference)
•
Supersede (IC Setup Extended Product Cross Reference)
•
Interchange (IC Setup Extended Product Cross Reference)
•
Auto pricing (IC Setup Extended Product Cross Reference)
•
Manufacturer’s product (IC Setup Warehouse - Vendor Prod)
For more information on this enhancement, refer to the 6.0 project review Importing Purchase Orders from
Excel found on the Infor365 support portal Web site.
Can Print Cancelled PO (B)
When you cancel a purchase order with a vendor, it is good business practice to send a printed copy of the cancelled purchase order to the vendor. You can now print a cancelled purchase order and send it to a vendor in the following functions:
•
JM Entry Release Jobs - File, Print POs (GUI only)
•
OE Entry Transactions - File, Print POs (GUI only)
•
PO Entry Transactions - File, Print
When printing a cancelled purchase order from any of these functions, the auto stored report @po+whse uses the PO Report Demand Print options to print the purchase order. The printed purchase order is clearly marked as cancelled with ***CANCELLED*** printed across the top and bottom of the document.
Default Resale # for a New PO Based on Receiving Warehouse (B)
Because taxes are based on where goods are received and not where the invoice is received, the resale # for a new purchase order will now default based on the IC Setup Warehouse Description value for the receiving warehouse instead of the billing warehouse.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 39 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
New Warning Message in POET (B)
When the due date, requested ship date, or expected ship date is overridden to a date that is prior to the order date, a new warning message "
Warning: Date Entered Is Prior To Order Date (8786)
" appears.
Performance Improved in POIO (C)
Performance has improved when performing a search in character PO Order Inquiry.
Vendor Product Number in POIP (G)
In PO Order inquiry, you can search by vendor product number but when viewing the results, there was no visible reference to that number on any of the tabs to indicate that a cross-reference exists. A Vendor
Product column has been added on the PO List and Line Detail windows. When product auto-lookup is active (from the Navigator window choose
Edit
,
Preferences
,
Settings
and select the
Product Auto-Lookup
Active
option), the vendor product number is automatically cross-referenced to the stocked product number. Vendor products must be set up in IC Setup Extended Cross Reference or the column value is blank. Per our standards, the column will be added as the last column, but you can change the order if you desire.
Report Scheduler
Report Scheduler Functionality Migrated to Graphical Interface (G)
The Report Scheduler functionality from the SX.enterprise character interface has been migrated to the
SX.enterprise graphical interface. Refer to the Report Scheduler Getting Started Guide on Infor365 for complete documentation for Report Scheduler.
Orphaned SAPB Record is Deleted With RSES Record (B)
When a report is removed through RSES in the character interface or RS Administrator Activity in the graphical interface, the SAPB record will be removed at the same time as the RSES record.
Note:
Prior to this enhancement, running rdclean.p removed the orphaned SAPB record or you could remove it in RS Purged Stored Reports (RSAP).
Linear Jobs Are Now Scheduled Jobs (B)
The
Linear Run Type
has been renamed to
Scheduled
in RS Setup Job Group (RSSJ). In turn, the
Start
Type
field that appeared when you selected
Linear
from the
Run Type
field is now labeled
Schedule Type
.
Scheduled run types require a schedule type. The column label in the browse was also changed to “Sched
Type”.
Report Viewer and Wizard
Enhancements to Report Viewer (G)
A new option has been added to the Report Viewer to allow you to set a maximum number of reports that are transferred at a time. This will avoid a bottleneck of report transmissions that might impact report processing time. The option,
Transfer
, is used to safeguard against a Progress stack overflow condition when too many reports are transferred from the host system. It can be set from
1-9
, indicating that up to nine reports can be retrieved at each auto report check, at the time interval determined by the Report
Viewer settings or when you click
Refresh
. The default value for this option is 1. Any changes will be reset
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 40 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
to 1 in the registry, along with other Report Viewer settings, when you exit SX.enterprise. To aid in troubleshooting, this field can be temporarily set to
0
, which prevents any report transfers from the host system.
To aid in troubleshooting, a side window listing statistics about the reports that the user has sent to the
Report Viewer has been added. Choose
Statistics
from the
View
menu or press
Ctrl
+
S
to view this information. If there are any reports that have been deleted by the user on the client machine, they are indicated in the
Delete/Host
field. Select the check box next to the field to view only reports that still remain on the Host machine but have been deleted by the user on the client. You can select a report and then choose
Transfer
from the shortcut menu to recover a report that may have been inadvertently deleted by a user on the client.
When you attempt to close the Report Viewer when file transfers are occurring, the system displays the message, "
Report Transfer in Progress, This Needs to Complete. Force Report Viewer
Exit?
". Select
no
, and the Report Viewer stays open and no errors are generated. Only select
yes
if the transfer is hung. If you select
yes
, the Report Viewer closes and errors are generated because the transfer had a "wait" component. The report viewer will re-open once the transfer is complete.
Warning When Close of Report Viewer (G)
A new warning displays when you close the Report Viewer window and a report transfer is in progress.
The message, “
Report Transfer in Progress, This Needs to Complete. Force Report Viewer
Exit?
” will now appear. If you click
No
, the Report Viewer remains open. If you click
Yes
, Report Viewer closes. When the report transfer is complete, Report Viewer will reopen.
Report Wizard Report Status Reset Properly (G)
Previously, when running Report Scheduler, if you selected a stored report in the Report Wizard and then clicked
New One-time
to run a single instance of the report, the status on the stored report was reset, causing the selected stored report and the new one-time report to be processed.
Now, a report’s status will only be reset when that report is being updated and the update is cancelled, preventing a stored report from being processed erroneously.
Service Warranty
SWEJ Date Field Changes (G)
When you are using the date field in the header to filter records, the logic is has been changed to include records with dates equal to or after the date entered. Before this enhancement, only records with the same date appeared. This change makes troubleshooting or reviewing weekly entries easier.
When entering new time records in SW Entry Job Time, the date for the first new record defaults to the last time entry record date or from the header. If you change the header date, the new date defaults to the time entry date field. If there is no date in the time entry date field when you enter that field, the current date automatically defaults.
Shortcut Keys Added to SWES (G)
The following shortcut keys have been added to the buttons in SW Entry Scheduling-Scheduling Detail for processing SROs. The button labels reflect this change.
•
Print Pick Ticket -
Alt+p
•
Print Delivery Ticket -
Alt+d
•
Complete -
Alt+c
•
Uncomplete -
Alt+n
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 41 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
•
Update -
Alt+u
You must press
Alt
to activate these and make them visible.
Column Shortcut Menu Options Added to SWIO (G)
Shortcut menu options
Adjust Columns
and
Move/Resize Columns
are now available from the shortcut menu accessed by right-clicking on a line in the Line Items browser. Also, the label of the SRO suffix column was changed to ‘Suf’.
Required Fields in SW Setup (G)
Several Service Warranty graphical setup screens were modified to make certain fields required when records are created:
•
SW Setup Cancelation Codes -
Cancel Code
•
SW Setup Job Types -
Order Approval Type
and
Charge Code
•
SW Setup Schedule Standard Tech Hours -
First Work Day of Week
and
Last Work Day of Week
•
SW Setup Warranty Claim Type -
Claim Type
System Administration
AO Enhancements (G)
The following changes have been made to Administrative Options (AO) windows in the graphical interface:
•
Before this enhancement, if you changed fields on Administrative Options windows and did not click the
Save
button, the system still saved the changes. To clarify that most changes are saved immediately, the
Save
button no longer appears on AO windows except for the Menu
Items and Report Items windows. In the case of the Menu Items and Report Items windows, you must click
Save
to keep your changes.
•
On the User Fields window, the system now validates every field change, logs who made the change, and the reason for the change.
•
The Changes section for top-level items on the tree now allows 70 characters in the Function column instead of 20 making it easier to understand the change. Many of the change descriptions were cut off when only 20 characters were allowed. For example, on the System
Configuration window, "
Maximum Days Before Password Expires
" now appears instead of
"
Maximum Days Before P
" when only 20 characters were allowed.
•
The
Phone # Format
field on the AO-System-Options window will validate any phone number masks that have been set up within the database, outside of this AO setup. If an invalid mask is detected, the format (xxx)xxx-xxxx/xxx will be applied automatically. You can type a mask or format and see an example of the setting before updating. Typing xxxxxxxxxxxxxxxxxx
(18 x’s) creates an 18-character free format phone number.
New AO Option Controls Ship To Service Charge Default (B)
A new option is available in AO-Customers-Services that controls how the ship to
Service Charge
setting defaults when a new shipto record is added or copied, either in AR Setup Shipto, Bid Prep, Job
Management, or via an SX.api call. If you select
Yes
for the option,
Ship To Service Chg
, the ship to Service
Charge is selected (defaults to
Yes
in CHUI); if you select
No
, it is not selected (defaults to
No
); if you select
From Customer
, the ship to Service Charge setting defaults from the AR Setup Customer record.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 42 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
New AO Option for NS/DO Write-offs (B)
PO line costs allow five decimal places, so nonstock and drop shipment inventory sets can remain active due to rounding. When costing in AP and there is a costing difference, the difference currently goes to a
Variance GL account instead of the Inventory GL Nonstock Drop Ship accounts causing an out-of-balance condition. If nonstock sets close properly, the AP Costing out-of-balance condition does not come into play.
In addition, importers constantly deal with conversions from metric to standard US units of measure. When
DO type orders are processed, there can be slight rounding differences that end up in IC Entry Adjust Nonstock/Direct Order (ICEAN).
To address these two situations, a new AO-Products-Defaults and ICAOC option,
NS/DO Write-off Amount
, has been created that allows you to define a maximum dollar variance that will automatically be written off to a designated GL account. If you do not want to specify an automatic write-off amount, leave the default of zero for the
NS/DO Write-Off Amount
field. With this setting, you must manually write off any cost difference in IC Entry Adjust Non-stock/Direct Order (ICEAN).
If you type an amount in the
NS/DO Write-Off Amount
field, a transaction takes the NS/DO set quantity to zero, and the cost difference is less than the write off amount (either positive or negative), then ICEAN write-off GL postings and IC transactions are generated and the set is automatically closed. The write-off amount is posted to the ICSEG/R&D Cost of Goods Sold (COGS) adjustment account.
AO Option Controls Management of Over Receiving POs/WTs (B)
A new option,
Over Fill Tied Order Qty With Receipt Qty: PO Receipts/WT Receipts
, allows you to automatically update the quantity ordered amount on a tied nonstock OE order during OE Entry
Processing Back Order Fill with the received quantity if a PT or WT is over received (the received amount is greater than the ordered amount. This prevent broken ties when the OE order is shipped and invoiced.
For more information, refer to the Nonstock Enhancements 6.0 Project Review on Infor365.
Security Controls and WT Tie Added for DNR Products (B)
Controls have been added to SX.enterprise to limit the sale of Do Not Reorder (DNR) products. These are products you have deemed should no longer be sold and have set the status on the IC Setup Warehouse
Products record to
Do Not Reorder
.
Generally, you do not want to permit a customer sales rep from selling more quantity of a DNR product than is available. An authorization point has been added that prevents them from entering an DNR item where the quantity ordered is greater than the quantity shipped unless they have ‘grant authority’. Review each operator’s authorization in File, Authorization, Authorization Security for the
DNR Items Not Allowed
Qty Avail < Ord
authorization point.
If the product has stock in another warehouse, you can now create a tie to a warehouse transfer. A new option has been added to AO-Documents-Sales Orders-Processing which determines if your operators can sell Do Not Reorder (DNR) products from all warehouses in your company, from only warehouses within a specific region, or strictly prevents them from tying a DNR product to a warehouse transfer. The option,
Allow Do Not Reorder Whse Transfer Tie by Company/Region/Neither
, limits DNR product ties to all warehouses (Company), warehouses assigned to the operator’s region (Region), or Neither; no tie can be made for DNR product. In CHUI, this option is set up in OE Administrative Options (OEAO) F6-More
Options:
Allow ‘Do Not Reorder’ Whse Transfer Tie By
(y/n). A single WT will be created for all ties from one
OE order, including any DNRs, and the WT will be flagged as ‘Rush’.
A new Event Manager trigger has been added to notify your managers when DNR items are entered in
OEET but there is insufficient stock to fill the order, no tie is created, and the order does not backorder.
This is a short-ship situation, and the event will fire notifying the manager of the short shipment. At the same time, the operator will see a message warning them that only the shipped (available) quantity will be
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 43 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
supplied to the customer. If there is no stock available for the DNR item, the message “
Quantity
Available is Zero and Will Not be Reordered for Future Shipment (6786)
” appears.
Note:
This event is automatically activated in version 6.0, but you should review the event notification settings in SA Event Manager Activate Events (SAEA) to select the notification recipient and method, and edit the optional text if your notification method is e-mail. This event will also be triggered during OE Entry Batch Update (OEEBU) in SX.enterprise character.
For more information, refer to the DNR & OAN Controls 6.0 Project Review, available on Infor365.
New AO Option for WT RRAR Order Quantity Calculation (B)
The order quantity calculation in the WT RRAR (WTERR) is now based upon the IC Setup Product Line
Transfer - Use ROQ
setting (using the Vendor/Product Line from the receiving warehouse’s ICSW record). If no vendor/product line is set up, it uses the new option in AO-Documents-Transfer Orders-Replenishment
(WTAO in CHUI),
If no Product Line, Use ROQ
. If the AO option is selected, the WT RRAR will use the
ICSW-Ordering Order Qty or the ICSW-Seasonality Order Qty. The setting for the RRAR option,
Apply
Halfway Rounding Rules
, will also apply to this quantity.
If the AO option is not selected, the WT RRAR will use the line point minus purchasing net available formula to calculate the quantity to be transferred. No halfway rounding will be done. The default is
No
, or not selected.
Audit Manager in GUI
Audit Manager has been migrated to the Microsoft Window environment and no longer utilizes the MARC application to set up audit triggers. A new function, SA Audit Processing Program Generation (SAAAU), has been added to SX.enterprise to enable selection of the tables and fields you want to audit. Once you identify the fields you will use SAAAU to generate the dictionary schema changes and triggers for auditing.
For more information, refer to the Audit Manager Getting Started Guide version 6.0, available from
Infor365 on the Documentation page.
Authorization Point Security Records Copied in SAACS (G)
If you set the
Also, Copy Operator Security
option to
yes
in SA Administrator Cross Company System Copy, the authorization point (AuthSecure) records are copied.
Now in the graphical interface, the system will only copy the SA Setup Operator pv_secure records if the
Also, Copy Operator Security
option is set to
yes
. Prior to this enhancement, the pv_secure records were copied if the
Copy Operator Setups
was
yes,
regardless of the
Also, Copy Operator Security
setting.
DNR Products With a Net Available Included on Storefront Catalog Load (B)
The SA Commerce Catalog Load (SAAE) will now include recordsync records for do-not-reorder products with a net available amount.
Error If Not Logged into First Company for Storefront Catalog Load (B)
If you run SA Commerce Catalog Load (SAAE) with the option
Process ICSC Records
selected, the error,
Report Option #3 = Yes, But Your Not Logged Into the First Company with AO Setting
(Include ICSC In Commerce Catalog) = no
will be printed on the exception report if you are not logged in to the first company in your database that has the
Interface ICSC Records
option selected in AO-System-
General in the graphical interface, or the
Include ICSC
option set to
Y
es in ICAO in the character interface.
Catalog records cannot be included in the data load to the Storefront catalog unless you are logged in to the first company.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 44 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Event Manager Trigger Fired For Short-ship from TWL (B)
The Event Manger event, oe-shortship, will now be initiated from WL Entry Batch Shipping, in addition to the OE Entry Shipping (OEES), when the actual shipped quantity is less than the original shipped quantity.
This event, and the oe-overship event, will also be fired when a packing slip is printed in TWL and lines are over- or short-picked.
Quantity Change in OEES Fires Event Trigger (B)
The Event Manager event, oe-shipqtyover, will now be fired when the quantity is overridden in OE Entry
Shipping, in addition to the current logic where notification was sent when the shipped quantity was changed on a line in OEET.
Note: Other events that trigger on changes made to an OE Header or Line will also trigger from OEES when these changes occur.
SAPF Option 1 is Required (B)
Option 1,
Unix File Name to Print
, in SA Administrator Print Unix File is now required and the cursor will automatically default to it.
Note:
The new SASSR will not be loaded during upgrade if the SASSR for SAPF is set to
S
or "Specific".
It must be set to
A
.
SAPJ Enhancements (G)
Browse windows in SA Printing Job and Queue Status now include a column for both Client and Server Rpt
Time. To eliminate confusion, the labels for the fields that display a specific type of time now reflect clearly the type of time that is displayed (for example, Client Start Time instead of Start Time). A new column also displays the priority of a print job within a report group.
A lookup button was added to the
Group
field and the
Ctrl
+
L
hotkey was implemented. The following four
Edit menu options have been given new shortcut keys for consistency:
•
Cut Jobs —
Alt
+
Ctrl
+
X
•
Copy Jobs —
Alt
+
Ctrl
+
C
•
Paste Jobs —
Alt
+
Ctrl
+
V
•
Delete Jobs —
Alt
+
Ctrl
+
D
SAPG Character Migrated to Graphical (G)
The Report Manager group functionality (SAPG in character) is now available in the Infor ERP
SX.enterprise graphical user interface. With this enhancement, you can manage reports by assigning them to a group in the Report Wizard. While assigning a report to a group, you specify a priority for that report within the group to indicate the specific order in which the reports should be processed. The new
Priority
field on the Report Wizard screen is only enterable if you specify a group for the report.
A lookup button has been added to the
Group
field in SA Printing Job and Queue Status so you can view all jobs for a specific group. You can use SA Printing Job and Queue Status (SAPJ) to maintain the start date and time for all jobs in a specified group.
The Group lookup window has been modified so you can filter the list of groups by group name and company number.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 45 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Enhanced Flexibility of Security for Return Lines, Credits, and Correction Orders
(B)
An existing operator security setting,
Allow/Do Not Allow User to Post Credits
(
Post Credits
in CHUI), has been split into three separate security settings in SASO:
•
Allow/Do Not Allow Customer Returns Processing
(
Customer Returns
in CHUI)
•
Allow/Do Not Allow Customer Credits Processing
(
Customer Credits
in CHUI)
•
Allow/Do Not Allow Vendor Returns/Credits Processing
(
Vendor Returns/Credits
in CHUI)
Previously, the single option locked down all credit postings in Accounts Payable, Accounts Receivable,
Order Entry, and Purchase Order. The split options allow more flexibility in defining which types of credits a user can post.
Note:
The new options default to the setting of the original
Allow/Do Not Allow User to Post Credits
(
Post
Credits
in CHUI) option for each operator, if you have run the optional conversion program, qdsasoo.ant
, during your upgrade to 6.0. This conversion program checks each operator’s setting for the original option and sets the new options to be the same. If you did not run the conversion program, the new options will be set to
Do Not Allow
or
N
o for all operators. Be sure to verify that the security settings for each operator are appropriate for the desired level of credit posting and make any necessary changes.
The following SX.enterprise functions are used to process credits and are affected by this enhancement:
•
AP Entry Batch Transactions (APEBT) (CHUI only)
•
AP Entry Invoice Center (APEI) (GUI only)
•
AP Entry Transactions (APET)
•
AR Entry Batch Transactions (AREBT) (CHUI only)
•
AR Entry Transactions (ARET)
•
OE Entry Batch Transactions (OEEBT) (CHUI only)
•
OE Entry Shipping Feedback (OEES)
•
OE Entry Transactions (OEET)
•
OE Entry Transactions (OEET) - Copy - Can copy from one type to another - SO to RM
•
OE Entry Transactions (OEET) - Receive On Account
•
PO Entry Transactions (POET)
•
PO Entry Transactions (POET) - Copy - Can copy from one type to another - PO to RM
•
RF OE Entry Shipping Feedback (IBRF)
•
SA Report Operator Preferences (SARF)
A new SA Setup Operators (SASO) window, Accounting Controls (Acct Security in CHUI), has been created to accommodate the new options. This new window contains the three new options as well as a few other options from the Cost Controls window (Security Flags screen in CHUI). The following paragraphs detail the three new options and how they affect operator security to post credit transactions.
Allow/Do Not Allow Customer Returns Processing
(Customer Returns in CHUI) - Customer returns apply to the following transaction types in Order Entry and Accounts Receivable:
•
RM orders without an invoice tied at the header level (Creates Misc Credit - Type 5 ARET transaction)
•
SO orders with a return line (Creates Misc Credit - Type 5 ARET transaction)
•
CS orders with a return line (Creates Misc Credit - Type 5 ARET transaction)
•
ARET Miscellaneous Credit (Type 5) transaction
Allow/Do Not Allow Customer Credits Processing
(Customer Credits in CHUI) - Customer credits apply to the following transaction types in Order Entry and Accounts Receivable:
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 46 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
•
RM order with an Invoice tied at the header level (Creates Credit Memo - Type 6 ARET transaction)
•
RA - Receive on Account (Creates Credit Memo - Type 6 ARET transaction)
•
CR orders where the line is a 'credit' line (Creates Misc Credit - Type 5 ARET transaction)
•
ARET Credit Memo (Type 6) and Unapplied Cash (Type 3) transactions
Allow/Do Not Allow Vendor Returns/Credits Processing
(Vendor Returns/Credits in CHUI) - Vendor returns and credits apply to the following transaction types in Purchase Order Entry and Accounts Payable:
•
RM orders
•
APET Miscellaneous Credit (Type 5) and Credit Memo (Type 6) transactions
If an operator tries to process a credit transaction they do not have security for, one of the following messages appears:
•
Operator Security Prohibits Customer Credit Processing
•
Operator Security Prohibits Customer Returns Processing
•
Operator Security Prohibits Vendor Returns/Credit Processing
For more information, refer to the 6.0 Project Review, Security Controls for RMA and Credits, found on the
Infor365 support Web site.
Overpayment Refund Type Can Be Blank (G)
Blank is now an option when you select the
Overpayment Refund Type
on the Payment Type table setup in
SA Setup Table Values.
Prospect Table Types Added to SASTT (G)
Two new table types, Prospect Activity Code and Prospect Activity Result, have been added to SA Setup
Table Values to allow you to add, update, or delete options used in SX.enterprise.
Prospect Activity Code values are used to identify and categorize job tasks. Activity codes may include administrative meetings, customer collections, etc. The values you specify appear in SW Setup Jobs
Times in the
Activity
field and in SW Setup Job Types in the
TQM Activity Code
field.
Prospect Activity Result values are used when you complete and close an activity. Using consistent result codes allows you to search for all activities with a specific code. The codes set up in SA Setup Table
Values appear in the character interface in the CMET
Result Code
field.
OE Terms Discount Can be Based on Gross Amount (B)
A new field,
Gross
, in SA Setup Table Values (SASTT) - Terms allows you to calculate the terms discount based on a gross or net amount in Order Entry.
If you leave this field blank (set to
N
o in CHUI), the discount is calculated from line amounts and does not include addons or taxes. This is how terms discounts were calculated before this enhancement.
If you select
Gross
(set to
Y
es in CHUI), the discount is calculated from the total invoice amount and includes taxes, but not addons. So, if there is a taxable addon, the tax on the addon is included, but not the addon amount itself.
This field works in conjunction with the terms override (
Over
) field which allows a different terms discount on each OE line. If both the
Over
and
Gross
fields are selected (set to
Y
es), the discount amount is calculated on each line individually using the line discount percentage and the discount amount on the addons. Taxes are calculated using the terms discount percentage.
The discount amount prints on the invoice and flows to Accounts Receivable. This field is not used in AR
Entry Transactions when invoices are entered.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 47 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
Vendor Price Groups Require a Price Type (B)
The
Price Type
field for Vendor Price Groups in SA Setup Table Values in the graphical interface and in SL
Setup Vendor Price Groups (SLSV) for the character interface is now a required field. If the value is left blank, when trying to create or update the record, "
This is a Required Field (2100)
" appears.
Default Category Field Size Adheres to Processor Interface (B)
The
Default Product Category
field in the SA Setup Table Values-Payment Type, Extended window has been decreased to allow entry of a category 12 characters or less. Previously, this field allowed up to 17 characters. This field is used for Level III Purchase Card processing, and only 12 characters are transmitted to the credit card processors.
Supplier Link
Performance Improved for SLAFI (B)
Improvements were made to the SL Administrator Import File processing time. Changes were made to utilize the report temp table and to display messages every 1000 records, rather than every 200 records.
System-wide
E-mail Addresses Allowed With Special Characters (B)
When printing an SX.enterprise report to e-mail, you can now type an e-mail address that contains a single quote (‘). You can also type a subject that contains a dollar sign ($) without the text being truncated after the $.
Infor Standardized Graphics and Logos (G)
The Infor ERP SX.enterprise user interface has been enhanced to provide common graphics and logos on all windows for consistency.
SX.api
Enhancements to Calls from Storefront (B)
Improvements were made to the sxapiSFGetPriceAvail and sxapiSFGetPriceAvailV2 calls’ processing time. Also, a new call was added to enable a full page inquiry of products from Storefront. The call, sxapiSFGetPriceAvailMultiple, passes a page (10, 25, or 50) of products to be priced.
Calls to Calculate Price Honor OEIE Business Rule (G)
SX.api calls that calculate price or create orders will now honor the new OE Ecommerce Queue Inquiry
(OEIE) business rule “PromoPriceDefault” when a promo price exists. If this business rule is not defined in
OEIE, the setting for the AO-Documents-Sales Orders-Entry Settings option,
Promo Price Default:
Lowest/Promo/Regular
is used. The calls impacted by this are Order Maint and OE Pricing.
Canadian and Mexican States Now Included in States List (B)
The list of states returned in the sxapiSFGetGenericData call now include the US, Canadian, and Mexican state codes.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 48 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
New Call For Margin Data Utilizes Business Rule (G)
A new call, sxapiICECatalogItemMasterV2, was added to retrieve Item Master data for Storefront during the Item Import function. Based on a how you create the “MarginPrice” business rule in OEIE, you can define how margin data elements are returned by this call. Products with a higher margin can be positioned at the top of the list when a search is conducted by a Storefront customer that utilizes the EasyAsk search engine. This call also returns the status from ICSW (icsw.statustype).
Taxware Interface
Changes Made for Labor Products (B)
A service indicator code is no longer sent to Taxware for labor (service) type products. This value will always be blank. To set up a labor product for taxing purposes, use IC Setup Warehouse Product - Taxes.
The POO (Point of Origin or ship from) and POA (Point of Arrival or ship to) addresses will be set to the ship to address on the order. This will not apply to Counter Sale or Will Call orders, and will not affect
Canadian orders, Max Tax states, lump sum orders, addons, or restocking fees.
Canadian Orders No Longer Processed with ‘Tax By Invoice’ Designation (B)
Canada is no longer designated as a ‘Tax By Invoice’ jurisdiction. This was incorrectly eliminating line detail when transmitting order totals to Taxware. This has been changed so that Canada is treated as a
‘Tax By Item’ state. This will resolve problems where recycling fees were not applied properly to certain lines because product codes were not transmitted.
State of Arkansas No Longer Max Tax State (B)
The state of Arkansas is no longer a ‘max tax’ state and will not be designated as a ‘Tax By Invoice’ state in the Taxware Interface.
Value Add
Value Add Migration (G)
The following functionality is now available in the graphical interface of SX.enterprise:
•
VA Entry Receipt of Inventory (VAEI) allows you to receive the finished product into your inventory after your internal processing department has completed the fabrication process. If the product is fabricated in-house, no purchase order exists so the product must be received in
VA Receipt of Inventory. Once you receive it, the stage of the VA order is stage 7 - Closed, since no purchase order exists that needs to be costed. When the finished product is received, the value of the product in the General Ledger is moved from the Work in Process account to the appropriate inventory account. An inventory in (II) section can be created for surplus product and you can complete IT and IS sections from within VA Entry Receipt of Inventory.
•
Value Add Internal Labor Time Entry (VAEL) allows you to record labor charges for a Value
Add product fabricated in-house. Time can only be entered against an internal processing (IT) or an inspection (IS) inspections section which has not been completed and is on an active VA order.
•
Inventory In (II) sections can now be created when you are receiving an external (EX) section in PO Entry Receipt of Inventory (POEI).
•
When you enter a quote order in OE Entry Transactions, you can tie a VA product entered on that quote order to a VA quote order by clicking the
Sourcing
button when you are on the VA product line.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 49 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
•
The VA Tie/Arp Rollup window allows you calculate rolled price and cost information based on markups you enter and use this price for the OE line selected. You can recalculate multiple times. You must have the proper security in SA Setup Operator to view or enter prices. This window is now available from the OE Customer Pricing Inquiry (OEIP) pricing worksheet. The information entered on the VA Tie/Arp Rollup window is passed to the pricing logic and applied so the information displayed on the main OE Customer Pricing Inquiry window reflects the changes entered. The VA Tie/Arp Rollup window also appears in OE Entry Transactions when an operator copies an OE order with a VA product on one of the lines if the
Reprice
option on the Copy Order, Quote, or PD Record window is selected.
For more information on this enhancement, refer to the 6.0 project review VA Migration to GUI found on the
Infor365 support portal Web site.
Cannot Change VA Finished Product if PO Tie Exists (B)
After creating a IN/EX section for a VA order and creating the PO tie for the EX section, you will no longer be allowed to recall the VA order in change mode and change the finished good to another item. The error message "
Cannot Change Product Number After PO Has Been Created (6774)
" appears.
New Error in VAEI for Home Warehouse Setting (G)
When an operator is limited to a specific home warehouse in SA Setup Operator attempts to use a warehouse other than the home warehouse as criteria to find VA orders in VA Receipt of Inventory, a new error message "
Warehouse Must be Same as Operator Warehouse (5607)
" appears and no results are returned.
WM Bin Locations Required for Warehouse-managed Items in VAEI (C)
Warehouse Manager bin locations are now required in VA Receipt of Inventory for finished goods that are warehouse-managed.
Warehouse Transfer
New AO Option for WT RRAR Order Quantity Calculation (B)
The order quantity calculation in the WT RRAR (WTERR) is now based upon the IC Setup Product Line
Transfer - Use ROQ
setting (using the Vendor/Product Line from the receiving warehouse’s ICSW record). If no vendor/product line is set up, it uses the new option in AO-Documents-Transfer Orders-Replenishment
(WTAO in CHUI),
If no Product Line, Use ROQ
. If the AO option is selected, the WT RRAR will use the
ICSW-Ordering Order Qty or the ICSW-Seasonality Order Qty. The setting for the RRAR option,
Apply
Halfway Rounding Rules
, will also apply to this quantity.
If the AO option is not selected, the WT RRAR will use the line point minus purchasing net available formula to calculate the quantity to be transferred. No halfway rounding will be done. The default is
No
, or not selected.
Product Category Field Access in WTET Extended (G)
Access to the
Category
field in WT Entry Transactions - Extended window is now dependent upon the following conditions:
•
If the product on the line is not a Non-stock type and it does not exist in the receiving warehouse, the field is accessable and can be changed.
•
If the product is not stocked in the receiving warehouse, the AO-Products-Defaults Non-stocks
Product Category will default in this field and cannot be changed.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 50 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
•
If you change the product from a stock item to a nonstock item, the AO default will be used.
WTIT Order Amount Column Label Changed (G)
The column labeled "Ordered Amt" has been renamed to "Order Amt" on the WT Transfer Inquiry List browser. The column is actually the "total line amount" or the "order amount". It is neither the shipped amount or the "original" ordered amount all the time. Before shipping, it is the order amount (and the ordered amount); after shipping and a backorder is created, it is the order amount and the shipped amount.
Shipped WTs Must Have Shipped Date (B)
You can no longer process a shipped warehouse transfer in the WT Pre-receiving Report (WTRI) that does not have a shipped date. This edit has been added to the WT # Range and the List option.
Home Warehouse Security Checked When WT Reports are Run (B)
An operator who is restricted to a Home Warehouse in their SA Setup Operator record, can enter a range of warehouses in the following WT reports: WT Exception Report (WTRE), WT Register Report (WTRR), and WT Master List (WTRM). No edits will be performed to validate the warehouses (although the Home
Whse will default in) until the report is run.
Legend: (G) = Change Impacts GUI Interface Only; (C) = Character Interface Only; (B) = Both
Infor ERP SX.enterprise Release Overview Page 51 of 51
Copyright © 2009 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. www.infor.com.
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project