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
12991 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

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

  • Arrange application information into multiple groupings and sequences that make sense for the job.
  • Hide information that does not apply to a particular job or task.
  • Filter records to show only the information that applies to the job or task that the user is performing.
  • Customize the information for an individual user, for a group of users, or for all users.
     

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

  • The name of an Infor LX program that contains a user exit to an add-on program
  • The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
  • The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
  • The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

First3637383941434445Last

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:

12345678910Last

Theme picker

Categories