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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: What is the purpose of document sequencing? How does it work?

Document Sequencing (ACR160) is a feature that allows the BPCS/LX system to assign a unique document number to every document created through ACP, ACR, and BIL. It is required for use with ATP (the general ledger posting engine) for ACR and BIL and is strongly recommended for use with ACP. Historically, we have experienced seemingly unexplainable events when Document Sequencing is not used and those events get cleared up once it is turned on.

Document Sequencing in ACP does not affect the Vendor Invoicing process for the user. You will still enter the Company, Vendor, and Invoice Number when you create invoices or memos. It provides the system with a better and more unique document number for the invoices so that the system can locate, identify, and link to the correct invoices during the processing of transactions and afterward when trying to trace transactions from ACP to CEA and back.

Document Sequencing is turned on in ACP180 Prefix Specific Numbering by setting it to a ‘1’ to assign the number at invoice entry and logging, or ‘2’ to assign the number at invoice entry and un-logging.

When Document Sequencing is turned on, the Document Sequence setup has to be defined in the system. For ACP, this is done in ACR160B, which is found in the ACP02 Accounts Payable Maintenance Menu (don’t confuse this with ACR160D which is found in the ACR01 menu and is used for ACR and BIL document sequence setup). Document Sequencing is defined by Company and Prefix Code. Blank is a valid Prefix code that can be defined and used, but most customers use a Prefix Code to differentiate certain types of transactions as it gives them a unique way to identify different types of invoices in the system and the prefix can be pulled into a journal entry to help determine account strings, or into reference or analysis field information.

The document sequence can also be set as a perpetual sequence where you will never need to do the roll (ACR920) and will not need to maintain the file in the future. (This is common for most of our clients).

  • Document Sequence Maintenance ACR160, set the End Date for the current year to 99/99/9999 (this is the default when creating a new doc sequence) and leave the next year start and end date at 00/00/0000.
Previous Article Reskilling and Upskilling Your Staff – Why You Shouldn’t Ignore This
Next Article Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item
Print
12806 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories