Costpoint Online Help

Using the Help Search
Using the Help Search
  • Phrase:Returns all topics that contain the exact phrase in the search criteria. Use quotation marks around the phrase.
    Ex."system administration"
  • And:Returns all topics that contain all the words in the search criteria, in any combination. Insert a plus sign between all words in the search criteria.
    Ex.system + administration
  • Or:Returns all topics with any combination of words in the search criteria. This is the default.
    Ex.system administration
For more information:Searching Online Help

Create IWO Allocations

Proceed with the transfer process as soon as you have calculated and posted the bills for IWO projects.

All untransferred records (IWO_XFR_FL=N) in the Billing Detail History (BILLING_DETL_HIST) table are used as the basis for the IWO allocation. The creation process is run by the performing database and is a Period-to-Date (PTD) calculation. When IWO entries are created, they are marked with a location. This location identifies the receiving database. It may or may not be the same as the sending database. The process produces two journal entries: one for the sending database and one for the receiving database. The accounts to be used in the journal entry are designated on the Manage IWO Projects screen. The two entries are stored in the IWO Allocation Header (IWO_ALLOC_HDR), IWO Allocation Transaction (IWO_ALLOC_TRN), and IWO Allocation Labor (IWO_ALLOC_LAB) tables. If labor is also transferred, it is stored separately in the third of these three IWO staging tables. Costpoint uses the tables to send the data to another database, if necessary, or to hold the data for posting if the sending and receiving databases are the same. In the receiving database, the data is posted to the Open Billing Detail table, all the general ledger tables, and the Labor History table of the receiving database. The S_JNL_CD in the GL_POST_SUM table is shown as IWO.

If you set up sales/VAT tax to be included in the IWO allocation (as configured on the Manage IWO Projects screen), Create IWO Allocations runs and creates the IWO allocation using the BILLING_DETL_HIST table for the sales/VAT tax and applies that value to the appropriate account based on the sales tax code for the sending and receiving companies for internal transfers, or to the account/organization selected for external transfers. Costpoint then updates the records used from BILLING_DETL_HIST, marking IWO_XFR_FL as Y so that these records will not be used in another IWO allocation.

If you set up the IWO project to transfer to a single employee (that is, you selected To Single Employee for Labor Transfer on the Manage IWO Projects screen), Create IWO Allocations changes the general labor category (GLC) of labor transactions for the IWO receiving entry using the following hierarchy:

  1. Costpoint checks the GLC field on the Timesheet Defaults tab of the Manage Employee Information screen. If the field is not null, this is the GLC that replaces the GLCs in IWO labor transactions.
  2. If the GLC field above is null, Costpoint checks the GLC field on the Salary Info tab of the Salary Details subtask of Manage Employee Information. If the field is not null, the GLC with the latest effective date is the GLC used to replace the GLCs in IWO labor transactions.
  3. If both fields above are null, Costpoint retains the GLCs in the original billing transactions.
Note: Create IWO Allocations uses this hierarchy for internal IWO transfers only. For external IWO transfers, the Validate IWO Allocations application replaces the GLC in labor transactions for a single employee.

This screen is the fourth step in the IWO process.