Enter Project Pre-posting

Explanation

Pre-posting is designed to track the expenses accumulated during projects. The intention is that you design a default code string where the code parts are present in IFS/Accounting Rules. This code string will be used in IFS Financials and the project can be pre-posted.

Pre-posting can be applied at project and subproject levels. If you intend to use the same code string on all subprojects below the project node, enter an asterisk (*) in the Sub Project ID field. It is possible to make a hierarchy where you overload the project’s code string with an alternate code string for the subproject.

For connected objects, pre-posting will insert the first subproject's code string or, if none is found, the project’s code string from *2 into *4. Companies and alternative code parts must be registered in IFS Financials. Once this is done, you can fill in the desired values for the code parts and build your own code string which can be used for pre-posting the project and/or subproject. All objects connected to a project should take advantage of this project-specific code string information.

When manually connecting a project activity to an object, if pre-posting on the code part already exists, they will be replaced by the project pre-posting. If the project pre-posting has no value for a code part then the existing pre-posting on the object will remain unchanged. Also the project and activity sequence will be posted.

If the project connection is automatic, child object will inherit parent object's pre-posting values on the code part rather than fetching code part values from project pre-posting in object conversion.
E.g.: If a demand is initiated from a project, Purchase Requisition will fetch code part values from project pre-posting. When converting Purchase Requisition to Purchase Order, pre-posting of code part values in Purchase Requisition will be inherited to Purchase Order rather than fetching code part values from project pre-posting.

 

Workflow

Creating: Pre-posting data is inserted by using Project Details/Project PrePosting. All data inserted, except for the project and subproject identifications, can be changed later.

Modifying: Pre-posting information is normal data and can be edited for a running project. Therefore, changes made in this information will affect the results that occur in IFS Financials.

Removing: Before you remove a code string, ensure that affected data in IFS Financials is considered obsolete and, therefore, invalid. Also, be sure that the code string is not being used by an active project.

Prerequisites

System Effects

Window

Project Details/Project PrePosting

Related Window Descriptions

Project Details/Project PrePosting

Procedure

  1. Select the appropriate project.
  2. Insert a new row in the table.
  3. Enter the subproject ID for which the codestring should apply. Enter an asterisk (*) if the codestring should apply for all subprojects that do not have a specified codestring.
  4. Select a system defined value from the list in the Create Cost Accounting field to specify whether cost accounting should be created and if used cost should be updated on the project activity when using IFS/Project Reporting.
  5. Enter the codestrings; nine codes are available (B-J). Click-on the List of Values option to choose the code.
  6. Save the pre-postings.