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

OPERATIONS:
Shelf Life Days and Retest Days
This feature provides the ability to enter information in the shelf life days and retest days fields for non-QMS lot controlled items, even when the QMS product is installed. The purpose of this enhancement is to allow the user to enter information for non-QMS lot controlled items even when QMS is activated in Parameters Generation, SYS800D.

In previous versions, when QMS was activated, the Shelf Life Days and Retest Days fields in Facility Planning Maintenance (MRP140) and Item Master Maintenance (INV100) were not maintainable for non-QMS lot controlled items.

FINANCE
Inventory Transaction Post to G/L by Cost Type
This enhancement provides a method to post material, labor, and overhead values on inventory postings to the general ledger to meet financial reporting requirements. The solution provides an optional further breakdown of cost by cost bucket using the new G/L Cost Type.

TECHNOLOGY:
Role-Based Security
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.

This feature provides the ability to enter information in the shelf life days and retest days fields for non-QMS lot controlled items, even when the QMS product is installed. The purpose of this enhancement is to allow the user to enter information for non-QMS lot controlled items even when QMS is activated in Parameters Generation, SYS800D.

In previous versions, when QMS was activated, the Shelf Life Days and Retest Days fields in Facility Planning Maintenance (MRP140) and Item Master Maintenance (INV100) were not maintainable for non-QMS lot controlled items.

123468910Last

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