Académique Documents
Professionnel Documents
Culture Documents
Posting Rules
• Posting engine can generate multiple GL transactions (one in each book) out of the
single business transaction document.
• Two ways of producing GL transactions in multiple books:
Apply posting rules to the business transaction document. Each book has a separate set of rules
that defines how GL transaction will be created in this book.
Apply COA mapping between two books so that GL transaction generated in main book flows into
the other book.
• If neither posting rules nor mapping is defined for a book, no transactions will be
created for that book.
Posting Engine – Process Stages
1) Revisions
2) Incoming Document Templates
3) Posting Codes
4) Amounts
5) Rules
6) Book Rules Node
7) Functions
8) Posting Rules
9) Reference Rules
10) Pre-Posting Rules
Revisions
• Defines the overall error handling options for journals posted to a specific
book.
Book Validations – Auto correction
Transaction Summarisation
• The Posting Engine Log tracks the results of your posting rules. You can then
evaluate how effective the posting rules are processing transactions.
• The data generated by the posting engine is traced by this log.
• Log Options:
Clear PE File - Click this button to clear the log results.
Show Details - Select this check box to display all the posting transaction information
recorded by the log.
Show Warning on Parent - Select this check box to display posting warnings on parent
records.
Use Bold Font for Details - Activate this check box to display the transaction details using a
bold font.
PE Log Viewer
• If you need to copy a posting rule or a set of posting rules, first highlight a node on the Tree View. Then
click on the Actions menu and select either Copy Rule or Copy Ruleset.
• All rules are based on the GL controls.
• Do not use a single quote ( ` ) in any context. It generates an error.
• Each selection criterion is case sensitive, so be sure to enter items using the correct case
• Once a revision is defined as Active, you can no longer change it. Instead, you will need to create a new
revision based on the active revision.
• Only parent-child relationships are available for a GL transaction type. For example, you can use a GL
control from the header for use within a line rule. You cannot, however, use GL controls across child to
child or from child up to parent.
• When you create an If-Else condition, make sure this condition displays on the node below the operation
you need, and not on the same node level. If you do not, the If-Else condition will not receive the data
generated by its parent operation.
Questions?
Thank You