[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration]
[EasyDNNnews:IfExists:Payment]
[EasyDNNnews:Price][EasyDNNnews:EndIf:Payment]
[EasyDNNnewsLocalizedText:Eventdate]:
[EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent]
[EasyDNNnews:IfExists:EventLocation]
[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]
[EasyDNNnews:EndIf:EventLocation]
[EasyDNNnews:IfExists:EventRegistration]
- [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
- [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
- [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
[EasyDNNnews:IfExists:Payment]- [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
[EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage]
[EasyDNNnews:EndIf:EventRegistration]
[EasyDNNnews:IfExists:EventSignUp]
[EasyDNNnewsLocalizedText:AreYouGoing]
[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
Infor LN & Baan Tips & Tricks for EXECUTIVES
FINANCE
Ledger Account Blocked Error
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:
- Free
- Blocked for manual input (integration transactions and other automatic transactions can be posted with this setting)
- Blocked for all purposes.
OPERATIONS
Absorbing Cost Items into Projects
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:
-
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.
-
Create and Activate Projects: Ensure that the necessary projects are created and set to active status.
-
Purchasing Cost Items:
- If needed, create the cost items.
- Create a purchase order for the cost items without referencing a project number.
-
Matching PO to Costs:
- When matching the purchase orders in session
tfacp2107m000, select "Add Costs" from the specific menu on the toolbar (you'll need to be in the matching details to access this).
- This will open session
tfacp1133s000, where you will enter the previously specified ledger account number.
- Once done, the "PCS Transactions" option on the toolbar becomes available. Selecting this brings up session
tipcs3140m000 (General Actual Project Costs).
-
Disbursing Costs to Projects: In session tipcs3140m000, the PO costs for the cost items can be disbursed to any open and active project.
Since these are cost items, they won't go into stock. The key is ensuring that the cost disbursement ("Add Costs") is correctly linked to the appropriate project, giving users visibility of the cost items as general project costs.
TECHNOLOGY
Adding a Timestamp to LN Standard Tables
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:
-
Enter the Tables: In this session, specify the tables for which you want to define timestamps.
-
Convert and Reconfigure: Run the Convert to Runtime Data Dictionary (ttadv5215m000) session to convert the table definitions to the runtime data dictionary and reconfigure the tables.
-
Restart Session: Log off and log back on to apply the changes.
IMPORTANT!
To avoid issues with locked tables, ensure that all users have logged off before starting the reconfiguration.
For more information, refer to the online help of the Convert to Runtime Data Dictionary (ttadv5215m000) session.