Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

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

Subscribe to newsletter

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
20034 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

Read more

Understanding: How many hours remain in total and at each operation?

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up th

Read more
FirstLast

Tips: LN | Baan

Categories