In a scenario where performing job A depends on the result of job B, it is hard to decide at what time job A must be scheduled, and how long job B runs. To handle dependent jobs, you can now create a job group. Use the Job Groups (ttaad5140m000) session to create a job group. A job group has a name, with the same characteristics as a job name, and a description. The Status and User of the job group are handled automatically.

After creating the job group, the jobs are added to the group, approximately in the order the jobs must be performed. The first job in the group (with the lowest Group Number) determines the handling of the whole job group, such as execution date and whether the job group is being repeated. If the job group is not repeating, the job group and all non-repeating jobs in the job group are deleted when the job group has run.

The dependencies of the jobs in the job group are also determined. A job in the job group can only depend on a job in the same job group with a lower job number.

You can use the specific options in the Job Groups (ttaad5140m000 andttams5640m000) sessions to change the status of the job group. The job group statuses have the same meaning as the status of the jobs and the same status changes are allowed.

Note: Job groups are only handled by the BSE service Job Scheduler Service.

A/P Payment Update in LX 8.3.4. ACP660B creates a file using a layout required by the bank; the file informs the bank to pay invoices. These conditions must be met to create the file:

• FIM is an installed product in SYS821  ­
• The user is authorized to FIM in SYS600 ­
• The company is active in FIMCOMIT in SYS105  ­
• The payment type is in BONPAYTP (SYS105)

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.

Crossroads RMC is pleased to announce that our Baan IV integration to AvaTax has officially been certified by Avalara! This means that all Baan IV, Baan V and Infor LN customers now have an automated solution for sales and use tax!

AvaTax provides sales and use tax calculations in real time including rate determination, returning filing, remittance and exemption certificate management. 

We are proud to announce our first Infor LN 10.7 implementation in partnership with Infor Consulting Services for LOOP, Inc. (Louisiana Offshore Oil Port Services). As part of this project, Crossroads RMC will be providing Finance and Data Migration as well as Infor OS / Ming.le consulting services.

Learn More about Crossroads RMC Consulting Services and our knowledgeable Consultants!

Did you know that you have several options for credit checks for your business partners?

Action-several options are available:

• Always Hold (Credit)—the order will always be held until released
• Never Hold (Credit)-the order will never be held
• Check Credit—a credit check is performed at time of sales order entry, release to invoicing or at confirm shipment.  When this status is used, the check can be performed at one or all three steps.  The steps are only visible with this status.
• Always Hold (Overdue Invoices)—the order will be held for overdue invoices until released.

Link the credit rating to the invoice to a business partner in the credit control session. You may also enter a credit limit. A credit limit of zero means unlimited credit.

IBM announced that it will no longer support the AFP Print Utility on the IBM i after version 7.2 of the IBM i OS.

See why TLAForms is a better solution!

Contact Anthony Etzel at aetzel@crossroadsrmc.com for more information.

By applying security to an object, you can control which users can view the object and which users can create, change, delete or copy the object.

Basic object security allows you to control who can display or maintain an object. Advanced object security allows you to control selectively who can create, change, delete, or copy an object.

In the basic model, all of the maintenance activities are permitted to those users who are authorized to maintain the object. Use the basic security model if you want a user who can change an object to also be able to create or delete the object. Use the advanced security model if you need to restrict some users to changing the object but not creating or deleting the object.