Whenever a financial transaction takes place in the system the postings concerning it are created by the predefined posting types and rules defined in IFS/Accounting Rules. This means that you do not have to do anything manually as long as you have defined your rules correctly.
However, sometimes you want to decide a code part value, depending on specific purchase order information, i.e., you choose not to decide a rule for this code part for all posting types affected or it is not possible to decide a rule. In these cases, you must manually establish the relationship between the code part and the purchase order line by entering a pre-posting connected to the purchase order line. The code part value that you enter as a pre-posting for the purchase line will then affect several postings created for this purchase line. One example where pre-posting is used is customer orders where you often want the postings to include a specific project in the code part project for all postings concerning the selling. Another example is a purchase order where you want the postings for purchasing to charge a specific cost center.
The postings that will be affected by the pre-posting are generally all postings
concerning expenses, revenues, and WIP. This is determined on
Business Event/Posting Info
tab,
where you can see whether a posting for a specific system event is affected by the
pre-posting on the purchase order line, or not. Note that pre-posting will
generally not affect the inventory cost postings (M1 posting). Pre-posting will
be used when posting transactions registered for non-inventory parts, no-number
parts and eventually overheads. An exception to this are transactions related to
material connected to a project. Pre-posting will also be
used for inventory parts with ownership Company Rental Asset since the postings
for these are the same as for non-inventory parts. When mandatory pre-posting is set up for
posting type M102 this implies that only non-inventory parts will be considered.
Basic financial data and sets of rules for IFS Business Systems are managed in the
IFS/Accounting Rules. Besides the regular rules you also have to define whether you want
to use the pre-posting functionality in IFS/Accounting Rules. This is done by entering a
specific posting type for each order type (see Prerequisites) and what code parts for
which it should be possible to enter pre-posting.
If you try to enter a pre-posting on a purchase order line and have not defined the use of pre-posting in IFS /Accounting Rules you will receive a message that tells you that pre-posting is not entered for this order type in the posting control. Initiate the pre-posting function on Posting Control page. Indicate the appropriate posting type for the code parts you intend to alter.
The pre-posting can either be entered on the header or the line. The advantage of using the pre-posting on the header is that the pre-posting value is valid for the lines as well. However, this assumes the lines are added afterwards. If both header and lines are already entered, you must do the pre-posting on each line.
Pre-postings can be added by using Pre-posting on both Purchase Order and Purchase Order Lines pages.
A relationship is established between the code part and the purchase order line by entering a pre-posting connected to the purchase order line. The code part value that you enter as a pre-posting for the purchase order line will then affect several postings created for this purchase order line. The postings that will be affected by the pre-posting are generally all postings concerning expenses, revenues, and WIP. A record will be created in the line history to indicate that pre-posting was changed. Postings for non-inventory parts and no-number parts will be affected. The postings for inventory parts will not be affected unless they are connected to a project or if the ownership of the part is Company Rental Asset.