The purpose is to describe the manual configuration need to be performed before running post scripts.
Use this page when you run manual post-scripts.
There are number of manual steps to be performed for proper upgrade of cost, revenue, hours and progress on project activities. The upgrade process has three main sections as follows,
Depend
on the version
upgrading from, following section should be executed.
Note: This section is mandatory for anyone who is upgrading from (IFS Applications 7.5) to IFS Applications 10.
Special consideration must be taken so that objects will be able to report revenue on activities, based on user-definable project revenue elements. Before the upgrade, revenue reported by objects are not categorized by any type of elements (corresponding to cost elements), and are not shown on activity level. There are different approaches to how to find the project revenue element to which the revenue should be reported, depending on the type of object reporting the revenue. There are:
- Objects where the project revenue element is manually entered in some way by the user.
- Objects where the revenue is manually posted to an account.
- Objects where the project revenue element is determined by applying the accounting rules to find the accounts to which the revenue most likely will be posted on the final transactions and vouchers later in the flow.
To make sure that the objects in category 2 and 3 are able to report their revenue, the user needs to perform manual steps. The desired revenue elements must be defined, and also the mapping between these revenue elements and the accounts that are used for reporting project revenue must be defined.After these manual steps have been performed, post-script should be executed which basically tells all project-connected objects to update their cost, revenue and progress information back to the project. When all objects have updated their information according to the posting control and other basic data, the upgrade is completed.
The following steps must be performed to achieve a successful upgrade of revenue elements:
Step 1. Determine which accounts are needed to be mapped to Revenue Elements
Suggested approach here is to list all accounts that previously have been posted to any projects, and do mapping for these accounts. The following SQL-statement can be used to get this information:
SELECT DISTINCT company, account, ifsapp.account_api.get_description(company,account)
FROM ifsapp.gen_led_proj_voucher_row t
WHERE ifsapp.account_api.Get_Accnt_Type_Db(company,account) = 'R'
ORDER BY company, accountHere we assume that IFSAPP is the application owner in the database, if not adjust the statement accordingly. This statement can for example be added as a IFS quick report, or be executed as an External Data query in Microsoft Excel, or be run in Oracle SQL*Plus.
Step 2. Enter new project Revenue Elements as desired and do the mappings
In the upgraded application, use the new forms for defining project Cost/Revenue elements with the Type Revenue, and map these to accounts.
- Define new Cost/Revenue elements with Element Type "Revenue".
- The validity date of these new elements must be earlier than the earliest transaction.
- Map accounts found in step 1 to project revenue elements.
Note: This section is mandatory for anyone who is upgrading from (IFS Applications 7.5) to IFS Applications 10.
Perform Cost Calculation and Copy to Cost Set 1
In order to update cost and hours related details for manufactured parts, it is required to perform a cost calculation and a copy to cost set 1.
The recommendation is to run the jobs:
- Costing / Cost Calculations / Calculate Cost - All Parts
- Costing / Cost Calculations / Copy Costs to Cost Set One