Project Definition

This chapter covers the following topics:

Defining Project Parameters

The following describes the set up of project parameters.

To Set up Project Parameters

  1. Navigate to the Project Parameters window.

  2. If you are making the first assignment, enter the project or Seiban number you want to associate with a planning group. If you are updating an existing assignment, query the existing record and make the necessary changes.

    If the number you enter is a Seiban number, the Seiban Number flag is automatically enabled.

  3. Select a cost group.

    If the organization has selected Standard as its primary costing method in the Organization Parameters window, the Cost Group field is disabled. Standard costing is available only when you do not use cost collection from manufacturing to Oracle Projects. Standard costing does not require cost groups.

    If the organization has selected Average as its primary costing method in the Organization Parameters window, the Cost Group field is enabled. You must select a cost group from the list for a project in an average costing organization. The list of values includes the Common Cost Group and the cost groups you define. The list of user defined cost groups includes only those cost groups with valid accounts in the Cost Group window. See Defining Cost Groups, Oracle Cost Management User's Guide. Weighted average costing for Inventory and WIP is maintained at the Cost Group level. Therefore, if you want to keep weighted average costing at the project level, you must assign the project to its own cost group.

  4. Optionally, enter a WIP accounting class.

    If the organization has selected Standard as its primary costing method in the Organization Parameters window, the WIP accounting class is Standard Discrete.

    If the organization has selected Average as its primary costing method in the Organization Parameters window, you can choose any WIP accounting class that has been associated with the selected cost group in the WIP Accounting Classes for Cost Groups window in Cost Management.

    When you create project jobs or complete work order-less schedules for a project, this accounting class is defaulted if an accounting class, based on the assembly item's category set, cannot be found. It can be overridden, but only with another accounting class that is assigned to the cost group. See WIP Accounting Class Defaults: Oracle Work in Process User's Guide.

    Note: When you create a project WIP job either manually or through MRP, the system checks whether you've assigned a default WIP accounting class to this WIP job's item category and cost group in the Default WIP Accounting Classes for Categories window. If you have, the program uses this WIP accounting class for the job. If you have not, the program uses the WIP accounting class you entered for the project.

  5. Optionally, select the name of the planning group with which you want to associate your project or Seiban number.

    If you plan material requirements by a group of projects, rather than by each individual project, you need to define a planning group and to assign all the projects to this planning group. If you plan net material requirements only by a single project, you do not need to associate the project with any planning group.

    For more information about planning groups, see Defining Planning Group QuickCodes, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide.

  6. Choose the Invoice Transfer tab.

  7. Enter an expenditure type for IPV.

    This field is mandatory in a Project Manufacturing organization, if the Transfer to PA IPV option has been selected on the Organization Parameters window. You can use the IPV expenditure type that has defaulted from the PJM Org Parameter window, or modify it to choose any one of expenditure types that has been associated with expenditure type class Inventory. For outside processing, you must choose an expenditure type that has been associated with the expenditure type class of Work in Process. See: Defining Expenditure types, Oracle Projects User's Guide.

    If an Invoice Price Variance is generated when approving an inventory or shopfloor (outside processing) related invoice, the Invoice Charge transfer process uses the IPV expenditure type defined in the Project Parameters window along with the IPV amount, IPV account, and Expenditure Organization to transfer the IPV amount for the project to Oracle Projects.

  8. Enter an expenditure type for ERV.

    This field is mandatory in a Project Manufacturing organization, if the Transfer to PA ERV option has been selected on the Organization Parameters window. You can use the ERV expenditure type that has defaulted from the PJM Org Parameter window or modify it to choose any one of expenditure types that has been associated with the expenditure type class Inventory. For outside processing, you must choose an expenditure type that has been associated with the expenditure type class of Work in Process. See: Defining Expenditure types, Oracle Projects User's Guide.

    If an Exchange Rate Variance is generated when approving an inventory or shop floor (outside processing)-related invoice, the ERV transfer process uses the ERV expenditure type defined in the Project Parameters window along with the ERV amount, ERV account, and Expenditure Organization to transfer the ERV amount for the project to Oracle Projects.

  9. Enter an expenditure type for Freight.

    This field is mandatory in a Project Manufacturing organization, if the Transfer to PA Freight option has been selected on the Organization Parameters window. You can use the Freight expenditure type that has defaulted from the PJM Org Parameter window or modify it to choose any one of expenditure types that has been associated with the expenditure type class Inventory. For outside processing, you must choose an expenditure type that has been associated with the expenditure type class of Work in Process. See: Defining Expenditure types, Oracle Projects User's Guide.

    If you use receipt based matching for your invoice, and freight is entered on the distribution when approving an inventor or shopfloor (outside processing) related invoice, the invoice charge transfer process uses the freight expenditure type defined in the Project Parameters window It also uses the freight amount and freight account from Oracle Payables, and the expenditure organization from the purchase order to transfer the freight amount for the project to Oracle Projects.

  10. Enter an expenditure type for Tax.

    This field is mandatory in a Project Manufacturing organization, if the Transfer to PA Tax option has been selected on the Organization Parameters window. You can use the tax expenditure type that has defaulted from the PJM Org Parameter window or modify it to choose any one of expenditure types that has been associated with the expenditure type class Inventory. For outside processing, you must choose an expenditure type that has been associated with the expenditure type class of Work in Process. See: Defining Expenditure types, Oracle Projects User's Guide.

    The method you choose to match tax to your invoiced items determines which expenditure type is assigned to the tax you enter on the Payables invoice. You can allocate tax at the line match level or you can enter tax as an invoice distribution line and manually allocate it to item distributions.

    If you allocate tax at the match to line level as described below, tax entered on the invoice is charged to the IPV expenditure type:

    -- You can select the option of matching the supplier invoice to the purchase order or purchase order receipt on the shipments window of the purchase order. When you enter the Payables invoice, you select the same matching method that you chose on the purchase order.

    -- On the Match to Purchase Order window of Invoice Entry, you can check the Allocate check box next to each matching line to allocate tax, freight, and miscellaneous charges to the matched lines.

    -- Tax matched to a purchase order or receipt line on this window is designated as an invoice price variance - the difference between the tax amount allocated on the invoice and the tax entered on the purchase order line. In Oracle Projects you see the Invoice Price Variance expenditure type on the transaction for tax allocated on the invoice.

    If you allocate tax at the invoice distribution line level as described below, tax entered on the invoice is charged to the tax expenditure type:

    -- You can select the same matching method on the invoice as you selected on the purchase order as described above and perform matching to lines, but do not check the Allocate check box.

    -- You can enter a new distribution line for tax on the Invoice Distributions window and hit the Allocate button.

    -- You can manually allocate the tax to any of the item distribution lines.

    -- Tax matched on this window is designated as a tax (not invoice price variance) and is charged to the tax expenditure type which you set up on the Project Parameters window.

  11. Enter an expenditure type for Miscellaneous charge.

    This field is mandatory in a Project Manufacturing organization, if the Transfer to PA Miscellaneous option has been selected on the Organization Parameters window. You can use the Miscellaneous expenditure type that has defaulted from the PJM Org Parameter window or modify it to choose any one of expenditure types that has been associated with the expenditure type class Inventory. For outside processing, you must choose an expenditure type that has been associated with the expenditure type class of Work in Process. See: Defining Expenditure types, Oracle Projects User's Guide.

    If a distribution is generated for Tax when performing receipt based matching for an inventory or shopfloor (outside processing) related invoice, the Invoice Charge transfer process uses the ERV expenditure type defined in the Project Parameters window along with the miscellaneous amount and account from invoice distributions and expenditure organization from the purchase order to transfer the miscellaneous charge for the project to Oracle Projects.

Seiban Number Wizard

The Seiban Number Wizard allows you to define Seiban numbers and to create and modify projects using with top-level task structures only. For example, this is used for project creation in Lot Type Seiban environments.

Defining Seiban Numbers

  1. Navigate to the Seiban Number Wizard.

  2. Select Using Seiban Number.

  3. Choose the Next button. The Seiban Numbers window displays, and you are no longer be in the Seiban Number Wizard.

  4. Enter a Seiban number and name that is unique within an Operating Unit. Alternatively, query any existing Seiban numbers, choose New, and then enter a Seiban number and name.

  5. Save your work or optionally, choose Parameters to navigate to the Project Parameters window. This automatically saves your new Seiban number and name.

  6. In the Project Parameters window, select the Organization. The LOV shows only organizations that have project level control.

  7. Optionally, select values for the following fields:

    • Cost Group - Select when using Average as your costing method.

    • WIP Accounting Class

    • Planning Group

  8. Save your work.

You can use the new project and tasks in Oracle Projects and Oracle Project Manufacturing. You can use the Seiban Number Wizard to generate a project structure with only top-level tasks. This is typically used in a lot-type Seiban environment but is also usable in a non-Seiban environment.

All conditions related to Oracle Projects integration apply.

Prerequisites

  1. Define a project template. See: Creating a Project Template, Oracle Projects User's Guide

Defining a Project with Lot Type Seiban Numbers

  1. Navigate to the Seiban Number Wizard.

  2. Select Using Project Number.

  3. Choose the Next button. The Seiban Number Wizard Step 2 of 5: Project Option window displays.

  4. Choose the Create a New Project option.

  5. Choose the Next button. The Seiban Number Wizard Step 3 of 5: Project Option window displays.

  6. Select the template.

  7. Enter the following information:

    • Project Number

    • Project Name

    • Start Date (for project)

    • Completion Date (for project)

  8. Optionally, select the Submit Approval Window. Click the Next button. The Seiban Number Wizard Step 4 of 5: Task Information window displays.

  9. Enter the following information:

    Parameter Meaning Example
    Prefix (optional) All tasks generated by the Wizard begin with this value. T
    Suffix (optional) All tasks generated by the Wizard end with this value. -X
    Starting Number This is the first task generated. 1
    Ending Number This is the last task generated. The actual ending task number depends on the increment parameter you select. 1000
    Increment by The task numbers generated increment by this value. If this value is 5 then the tasks would be 1,6,11 and so on.
    Numeric Width (optional) This value causes leading zeros to appear before the task number, ensuring a fixed length for the task numbers. If you do not specify a value, there are no leading zeros. If this value is 4 then the tasks listed above would be 0001, 0006, 0011, and so on.

    The lists of tasks generated in this example would be T0001-X, T0006-X, T0011-X and so on.

  10. Choose the Next button. The Seiban Number Wizard Step 4 of 5: Task Information window displays.

  11. Enter the following information:

    Parameter Meaning Example
    Prefix (optional) All tasks generated by the Wizard begin with this value. T
    Suffix (optional) All tasks generated by the Wizard end with this value -X
    Starting Number This is the first task generated. 1
    Ending Number This is the last task that could be generated. The actual ending task number depends on the increment parameter you select. 1000
    Increment by The task numbers generated increments by this value. If this value is 5 then the tasks would be 1,6,11 and so on.
    Numeric Width (optional) This value causes leading zeros to appear before the task number, ensuring a fixed length for the task numbers. If you do not specify a value, there are no leading zeros. If this value is 4 then the tasks listed above would be 0001, 0006, 0011, and so on.

    The lists of tasks generated in this example would be T0001-X, T0006-X, T0011-X and so on.

Modifying a Project with Lot Type Numbers

  1. Navigate to the Seiban Number Wizard.

  2. Select Using Project Number.

  3. Click the Next button. The Seiban Number Wizard Step 2 of 5: Project Option window displays.

  4. Click the Add button to add an existing project option.

  5. Click the Next button. The Seiban Number Wizard Step 3 of 5: Project Selection window displays.

  6. Select the project number.

  7. Click the Next button. The Seiban Number Wizard Step 4 of 5: Task Information window displays.

  8. Enter the following information:

    Parameter Meaning Example
    Prefix (optional) All tasks generated by the Wizard begin with this value. T
    Suffix (optional) All tasks generated by the Wizard end with this value. -X
    Starting Number This is the first task generated. 1
    Ending Number This is the last task that could be generated. The actual ending task number depends on the increment parameter you select. 1000
    Increment by The task numbers generated increment by this value. If this value is 5 then the tasks would be 1,6,11 and so on.
    Numeric Width (optional) This value causes leading zeros to appear before the task number, ensuring a fixed length for the task numbers. If you do not specify a value, there are be no leading zeros. If this value is 4 then the tasks listed above would be 0001, 0006, 0011, and so on.

    The lists of tasks generated in this example would be T0001-X, T0006-X, T0011-X and so on.

  9. Click the Next button. The Seiban Number Wizard Step 5 of 5: Confirmation displays.

  10. Click the Finish button.