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. 

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.

Currency differences can make the financial analysis and reconciliation more complex. These types of currency differences can occur:

• Currency differences
  Currency result caused by fluctuations in the exchange rate, for example, if the rate differs between the invoice date and the payment date.

• Exchange gain and loss
  Currency result caused by the use of different exchange rate types, for example, the Sales rate type and the Internal rate type, or if using the rate determiner you have changed the exchange rate for a transaction during the order handling procedure.

• Translation gain and loss
  Currency result caused by the use of different currencies during the order handling procedure, for example, if the order currency or the payment currency differs from the invoice currency.

• Destination gain and loss
  Currency result caused by different results when the transaction currency is converted to the various home currencies. Destination gain and loss can only occur in an independent currency system.

To support good reconciliation possibilities, currency differences and exchange gain and loss are posted to these accounts: