DOC

Bills of Material

By Oscar Henry,2014-10-06 16:17
9 views 0
Bills of Material

    Setting Engineering Profile

    Values and Security

    Functions

    Overview

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC Effective mm/dd/yy Page 1 of 20 Rev 1

Setting Engineering Profile Values and Security Functions

    System References

    None

    Distribution

    *Job Title

    Ownership

    The Job Title [list@YourCompany.com?Subject=EDUxxxxx] is responsible for ensuring that this document is necessary and that it reflects actual practice.

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC Effective mm/dd/yy Page 2 of 20 Rev 1

    Setting Engineering Profile Values and Security Functions

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC

    Effective mm/dd/yy Page 3 of 20 Rev 1

Objectives

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC Effective mm/dd/yy Page 4 of 20 Rev 1

Agenda

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC Effective mm/dd/yy Page 5 of 20 Rev 1

Engineering Setup Flowchart

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC Effective mm/dd/yy Page 6 of 20 Rev 1

Setup Steps

Setup Steps

    1. Set Profile Options (Required) - Profile options specify how Oracle Engineering controls

    access to and processes data. In general, profile options can be set at one or more of the

    following levels: site, application, responsibility, and user. Use the Update Personal

    Profile Options form to set profile options at the user level. System administrators use the

    Update System Profile Options form to set profile options at the site, application,

    responsibility, and user levels. Perform this step once for each entity, that is, site,

    application, responsibility, or user.

    2. Enter Employee (Required) - Define employees for your organization. ECO requestors

    and approvers must be defined as employees. If you do not install Oracle Human Resource

    Management Systems with Oracle Engineering, use the Enter Employee form to define

    and maintain employees in Oracle Engineering. If you install Oracle Human Resource

    Management Systems, use the forms in Oracle Human Resource Management Systems

    instead to enter and maintain employees. Perform this step once for each entity

    organization.

    3. Define Change Order Types (Optional) - You can assign a change order type to your

    ECOs, either using the ECO change order type that Oracle Engineering provides or

    choosing a change order type from any number of types you define using your own

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC

    Effective mm/dd/yy Page 7 of 20 Rev 1

    terminology, such as Design Revision, Manufacturing Change Order, or Substitution Waiver. You can create change order types for ECOs with manufacturing items, or manufacturing and engineering items. If you skip this step, Oracle shipped change order types will be used as the default values. Perform this step once per installation. 4. Define ECO Departments (Optional) - You can group users that use the engineering change order (ECO) system through ECO departments, creating multiple ECO departments within your Inventory organization. You can restrict access to ECOs by ECO department and require an ECO department on all ECOs-changing the responsible ECO department as the ECO moves through multiple departments. Perform this step once per organization.

    5. Define Autonumbering (Optional) - You can define customized autonumbering (for a user, organization, or site) for new ECOs or mass change orders. You can use the autonumber default value when you define an engineering or mass change order, or you can override the autonumber default and assign your own number. Perform this step once per organizational user.

    6. Define Approval Lists (Optional) - You can define lists of approvers required to approve an ECO before it can be released. Oracle Engineering notifies the people on the list, using an alert, that the ECO requires their approval. Perform this step once per installation. 7. Define Material Dispositions (Optional) - You can define your own customized material dispositions, and then assign them to revised items when defining ECOs.

    8. Define Reasons (Optional) - You can define reasons for engineering change orders using your own terminology, such as Model Year, Design, Safety, and Ergonomic. ECO reasons are for your reference use only. If you skip this step, Oracle shipped reasons will be used as the default values. Perform this step once per organization.

    9. Define Priorities (Optional) - You can define scheduling priorities for engineering changes to describe the urgency of your ECO. Priorities are for your reference use only. If you skip this step Oracle shipped priorities will be used as the default value. Perform this step once per organization.

    10. Start AutoImplement Manager (Optional) - If you automatically implement ECOs, you must specify the frequency that you want the AutoImplement manager to run. Once an ECO has been released to the autoimplement manager, you can automatically implement all scheduled ECO revised items whose effective date is less than or equal to the current date.

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC

    Effective mm/dd/yy Page 8 of 20 Rev 1

Profile Options

Profile Options

    ENG: Change order Autonumbering-System Administrator Access

     Indicate whether you can define ECO autonumbering for all users or for yourself only. ENG: ECO Department

     Indicate the default department Engineering uses when you define an ECO. An ECO

    department is the department currently responsible for an ECO. It restricts departments

    from updating ECOs for which they are not responsible.

    ENG: ECO Revision Warning

     Indicate whether to raise a warning but still implement ECO revisions with pending lower

    level revisions (Yes), or to raise an error and not perform the implementation (No or

    blank). A blank (or “null") value is equivalent to No.

    ENG: Engineering Item Change Order Access

     Indicate whether you can revise engineering items on ECOs.

    ENG: Mandatory ECO Departments

     Indicate whether it is mandatory to assign a department to each ECO so you can enforce a

    security policy.

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC

    Effective mm/dd/yy Page 9 of 20 Rev 1

ENG: Model Item Change Order Access

     Indicate whether you can revise model and option class items on ECOs. ENG: Planning Item Change Order Access

     Indicate whether you can revise planning items on ECOs. ENG: Require Revised Item New Revision

     Indicate whether it is mandatory to assign a new revision to revised items on ECOs. A

    blank (or “null") value is equivalent to No.

    ENG:Standard Item Change Order Access

     Indicate whether you can revise standard items on ECOs. ENG:Allow ENG COMPS for MFG Items in ECO

     Indicate whether you can allow engineering components for MFG revised items in ECO.

    ENG:MRP Active flag default for ECO

     Indicate the default active flag for ECO revised items. ENG:Update Unreleased WIP Jobs

     Indicate if you can update unreleased WIP jobs.

     Copyright ? Oracle, 2007. All rights reserved.

    Setting Engineering Profile Values and Security Functions 85858427.DOC Effective mm/dd/yy Page 10 of 20 Rev 1

Report this document

For any questions or suggestions please email
cust-service@docsford.com