Infor LN & Baan Tips & Tricks for EXECUTIVES
FINANCE Tip: Remap Posted Integration Transactions (tfgld4282m100)
Use this session to remap Posted transactions that were mapped incorrectly.
To remap integration transactions successfully, several conditions must be fulfilled. For details, refer to To remap integration transactions.
Enter the ranges of selection criteria for the integration transaction or range of integration transactions to be remapped. You can select the integration transactions of a range of business objects or of a specific business object.
You must select a specific integration document type or an integration document type group.
To evaluate the remapping before you perform the actual remapping, you can select the Simulate check box and the Error Report check box. After you solve the errors, you can run the session again and clear the Simulate check box.
After remapping the integration transactions, you can use the Post Integration Transactions (tfgld4282m000) session to create the postings in the General Ledger.
OPERATIONS Tip: Using Country of Origin for Purchase Orders
For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.
When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.
After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.
You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.
In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.
TECHNOLOGY Tip: Impact of Configuration Changes on Audit Trails:
Impact of Configuration Changes on Audit Trails
The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.
Changes in User Profiles
Below is a summary table that illustrates the effects of these changes for a specific table within a company:
| Change Description |
Impact |
| Add a table |
Users that still use the old settings do not audit some transactions. |
| Remove a table |
Some transactions that must not be audited with the new settings are still audited by users that use the old settings. |
| Change the audit type for a table or field |
Some transactions are audited according to the old settings, and other transactions are audited according to the new settings. |
| Add or remove a field |
After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN. |
Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.