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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Facility Period Close

The Facility Period Close process, as introduced in Infor LX 8.3.4, was designed to function interactively. 

The expectation was that clients with a continuous or 24-hour worldwide operation in multiple facilities would submit the Period End Close jobs for each facility as daily operations ceased or shifts ended for each facility. This process was designed to function interactively so that validations of users performing transactions that conflicted with period end processing, and resulting messages, were immediately sent to the period end user. 

This enhancement provides a batch mode for the Facility Period Close (INV930) process and allows the Update IIM Inventory from IWI (INV931) process to be submitted from the INV930B program. The enhancement also provides a batch mode for the INV931 process. For example, a user has a 24-hour operation in facilities around the world, but a centralized IT operation. With this enhancement the user can submit the individual facilities to be closed to a batch process that can be managed by a scheduler, automatically releasing each facility to be closed at a predetermined time.

Previous Article Flexfab Expands Their Use of Crossroads RMC Data Collection for All LN Installations Globally
Next Article Pushing Forward In the Face of Adversity. Soundview recently suffered a major loss when fire struck on January 30, 2019.
Print
31099 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

I recently came across an article from CIO Magazine that talked about the various ways that your ERP system could be hurting your business. The single most important item on that list referenced ERP systems that weren’t integrated with other systems that housed mission-critical business data.

Having data in two (or more) systems that don’t talk to one another is like baking a pizza crust in one oven and the toppings in another. Once baked, you may have some good food to snack on, but it sure isn’t pizza! Pizza requires the cheese and sauce and spices to bake with the crust. One takes on the flavor of the other and when you take a bite, you get a complete representation of the flavors.   

That’s the value of an integrated ERP system. When you take a bite, you get a complete representation of the flavors…meaning, you get one version of the truth. Everything comes together to allow you to analyze critical business data in an efficient way with no disconnects.

Crossroads consultants have spent years developing integration expertise to tie countless different systems to Infor ERPs.

Here are some examples…

First4849505153555657Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories