Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan / LN Tip of the Week: Sales Order Returns & Credit Invoices

This tip shows the procedure to process a return sales order and the resulting credit sales invoice.

A normal sales order was completed (200010016) prior to processing the return sales order.

Set up sales order with sales order type of “Return Inventory”.
-----------------------------------------------------------------------------

A return order requires a return reason.
-------------------------------------------------
The return sales order has all steps automated.
The last step is to produce the invoice in Central Invoicing.
---------------------------------------------------------------------

The invoice is confirmed in Central Invoicing for the amount of the sales order.
--------------------------------------------------------------------------------------------

Set up the billing request-Common Tab
-----------------------------------------------

Sales/Rebate Tab
---------------------

Process the billing request
--------------------------------

Compose/Print/Post
------------------------

Success message
---------------------

Sales Credit Invoice
-----------------------

The original invoice and credit invoice can be viewed in open entries.
---------------------------------------------------------------------------------

Previous Article BPCS / LX Tip of the Week: Purchase Order Print Security Validation
Next Article Data Collection: Are you able to perform a full cycle count of your inventory in one day?
Print
41278 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third-party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

First122123124125127129130131Last

Theme picker

Categories