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:

When the originating order or order line of an outbound order line is canceled or changed, this affects the outbound order line and may affect the related outbound advice, shipments, or shipment lines.

For most order origins, warehousing order-type parameters determine whether these actions are allowed:

• Update the outbound order line if the originating order is changed.
• Cancel the originating order line and the outbound order line.
• Delete the canceled outbound order line.

If updating is allowed...

Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps...

Operations: To absorb the cost of cost items into specific projects, you'll need to handle them as customized items. However, cost items cannot directly be defined as customized items. Customized items must be physical, either manufactured or purchased.

That said, it's still possible to absorb cost items into a project, although indirectly. Here's how:

1. Set Up Ledger Account: First, create a new ledger account in session tfgld0508m000 and set the type to "PCS" (project) in the operations management integrations. This account will be used for matching and approving purchase orders for cost items.

2. Create and Activate Projects: Ensure that the necessary projects are created and set to active status.

3. Purchasing Cost Items...

FINANCE
Ledger Account Blocked Error

OPERATIONS
Absorbing Cost Items into Projects

TECHNOLOGY
Adding a Timestamp to LN Standard Tables

When attempting to post to a ledger account, users may occasionally encounter an error indicating that the ledger account is blocked. To resolve this issue, navigate to the Chart of Accounts session (tfgld0508m000) and select the Miscellaneous tab. Once there, review the Blocking field. The available settings are:

1. Free
2. Blocked for manual input (integration transactions and other automatic transactions can be posted with this setting)
3. Blocked for all purposes.

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:...

FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value...

TECHNOLOGY: Infor LN Rest API
Frequently Asked Questions (KB2316174)

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

• The source financial company.
• The destination financial company.
• The transaction type and series.
• The ledger account and dimensions.
• The transaction currency.
• The fiscal year and the financial period, the tax period, and the reporting period.
• The integration document type and the Debit/Credit indicator.
• If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.