You can create new macros in the Infor LX Configurable Enterprise Financials CEA107. 

On the Macro Definition window, you define the source file and the field in which you perform an arithmetic or special operation. For example, you can create a macro to accrue sales commission based on revenue. Your source file and field are the Invoice Line History (SIL) file and the G/L revenue (ILREV) field. 

Select Functions to access the Macro Functions window, on which you define the arithmetic, character, or special operation to process against the defined source field. In the previous example of accrued sales commission, you enter an arithmetic operation of multiply (*) and an operand value for the percentage, such as 0.05 for five percent. 

Note:  Previously created user defined macros will have to be updated to include any expanded field sizes in V84. 

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

• Determine which level each group is allowed access.

• Determine which segment values/account strings are assigned to which user groups.

• Create security rules for specific segment values/account strings and assign these groups to the created rules.

• Select the rules to be processed.  Processing can be done in either batch mode or interactively.

• The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

Companies are developing procedures for entering data into an ERP system and for archiving manuals, drawings, specs, and other hard-copy documents. However, in many cases there is no defined procedures to store historical electronic data. Archiving electronic data should be an integral part of your business processes. 

Generally, archiving is the process of moving historical data from the operational environment to a special archive environment. At home, you might move old bank statements from a closet in your study to a box in the attic. At the office, you might store old hard copies of purchase orders in a room far from your own desk. Just because you no longer need the information in your daily work, does not mean you can dispose of the information. In terms of electronic data in your ERP system, archiving means moving historic data from the operational company to a special archive company; in that way, the historic data will be out of your way and safely stored. To free up disk space on your machine after you have archived the data, you can also move the historic data to an external medium.

Archiving strategy:

You can block a warehouse for inbound procedures, outbound procedures, or both. For example, you can block inbound and outbound procedures for a warehouse if the warehouse must be closed temporarily for inspection.

You can impose these types of blockings:

• Full block: Full block on warehousing procedures.

• Interactive block: Override blocking allowed except blocks on confirm shipment or confirm receipt.

If you impose a full block on inbound procedures...