Executing Oracle Projects ASCP, Inventory and Manufacturing

Session ID:

Prepared by:

Executing Oracle Projects –ASCP, Inventory and Manufacturing

10181

Chris Steuer

[email protected]

Enterprise Applications Architect, IT

Crane Aerospace & Electronics

April 2-6, 2017 in Las Vegas, NV USA #C17LV

Agenda

Crane Aerospace and Electronics Overview Oracle Solution and Footprint Project Setup and Basic Configurations Impact to Inventory Transactions Impact to Purchasing Impact to Work In Process ASCP functionality with Oracle Projects


Crane Aerospace and Electronics:

Crane Co was founded in 1855, with locations world-wide.

Crane Aerospace and Electronics Division was officially established in 1999. 2,800 employees Headquartered in Seattle, Washington Area 10 main production locations

Business Segments: Sensing & Utility Systems, Fluid Management, Power Solutions, Landing Systems, Cabin Systems, and Microwave Solutions.

These products are backed by leading technical expertise and world-class design and manufacturing processes. Our technical

strength, product reliability, innovative solutions, and commitment to lean manufacturing bring The Crane Advantage to customers

Markets: Commercial: Aircraft, Engines, Space, and Transportation Defense: Military Aircraft, Rotorcraft, Maritime, and Ground Based Defense


Oracle Solution Overview: Electronics:

• Red boxes indicate – Oracle product currently deployed (Some partially)

• There are two solutions that we own for operational reporting:

• Polaris reporting tool – Deployed

• Oracle Endeca extensions for EBS – Not deployed


Project Manufacturing Overview

• Oracle Projects is primarily used to provide a single view of all project-related activities, including all manufacturing related transactions, within an Oracle suite of applications.

• All standard Oracle transactions are impacted by how you choose to define, structure and implement one or many of the Oracle Projects Module:



• Project Types and templates are defined to represent various potential projects:

• Project Types, similar to item templates, are created to assist with project creation with common project attributes or structures.



• Project number is at the parent level• Tasks at child level give you granularity to project activities



• Cost Groups are created and tied to Projects• Cost Groups represent a set of accounts where inventory is valued and the average cost of an

item can be unique within each cost group.



• Expenditures are group of expenditure items, or transactions, incurred by an employee or an organization for an expenditure period.

• Charge expenditures via mapping from standard Oracle MFG transactions



• Oracle MFG Transactions > Expenditures > Projects



• Project Expenditures in Projects will display your consolidated accumulated costs from various sources:



• Inventory Organization Parameters• Cost Type Average• Project Cost Collected• Default Cost Group

• Subinventory Configurations• Locator Control at Dynamic entry


Project Manufacturing Overview• PO Receipt and Receiving Transaction:



• Item Locations Dynamically Created with Project and Task reference as transactions occur

• Project / Task appear by default if PO Line (or WIP Job) configured with Project/task reference

• Locator Segments• Segment1 = Locator• Segment3 = Project• Segment3 = Task



• On Hand Inventory stored at Project / Task Granularity is Hard Pegged

• On Hand not stored by Project / Task is Soft Pegged



• Hard Pegged Inventory Costs will display as a Project Expenditure

• Inventory costs are displayed as Expend Type Material and OH: Material due to expenditure configurations



• Inventory can moved via Project Transfer, similar to a subinvenory transfers, for the following cases:• Soft Pegged to Hard Pegged• Hard Pegged to Soft Pegged• Project A to Project B

• Transaction Type = Project Transfer



• Asset Inventory Moved from Project A to Project B via Project Transfer will move the expenditure costs from Project A to Project B at the value of the inventory



• PO Receiving Costing:• As Unit is put into Project Controlled location, Project Cost Import

Processes creates Project Expenditures



• Purchase Order• Project Number added to Distribution Line• Project number will transfer to receiving transaction by default



• Work order• Project Number and Task Entered on Work Order• WIP Accounting Class LOV determined by Cost Group tied to Project



• Work order Transactions

• As WIP Incurs value, background concurrent programs will send these records to Projects as expenditures.

Transaction Types:

• *WIP Issues of “Soft Pegged” Material• Resource Transactions (Appear as “Labor” expenditure types)



• Planning Items in ASCP can allow the recommendations to include the project number and task prior to release



• Planning system will determine whether an Item’s Planned Orders contain a project number based on ORG Item Attribute:

• Pegging Method must contain “Hard Pegging”



• Upon “Release” from ASCP for “Hard Pegging” Items

Buy Items:

Requisition Created with Project Task Reference

Buyers Use AutoCreate to transform Requisition to PO

Purchase order distribution line is Populated with Project/Task

Make Items:

Work Order Created with Project/Task Reference

Work Order WIP Accounting Class / Task determined by Project Parameters



• ASCP Plan Options

• Two Main Settings will impact how the system will peg and net existing supply• Reservation Level• Hard Pegging level



• ASCP Reservation Level

• Planning Group: – You can add multiple Projects to a single planning group so that all hard pegged supply in those projects can be shared among the planning group during the netting calculation. If no planning group is assigned to project, will share with everyone.

• Project: – Share supply within a project and across multiple tasks during the netting calculation.

• Project - Task: - Do not share hard pegged supply with any other project / task when system is determining planning requirements



• ASCP Hard Pegging Level

• Pegging Level should align with your project configurations• Impacts item planned orders for items coded as “Hard Pegged”

• Project – Planned order generated with Project Number only

• Project - Task: - Planned orders generated with Project and Task



• Consider combination of plan type, Item planning method, plan pegging method, and plan reservation level when designing your planning architecture.

• Various combinations can support multiple supply strategies in a single organizations

• Use of Hub and Spoke Planning is another way to have multiple plans behave and generate recommendations differently giving you greater flexibility



• Use Case

• “Hard Peg” all make items so WIP costs are transferred to the projects during build

• Share supply of buy components across all projects, regardless of pegging, as we can transfer components from one project to another

Configure two plans to support each



• Make Plan Collective Settings:



• Buy Plan Collective Settings:

If Item is “Hard Pegged” planned order will contain Project/task

• Planned orders from “Make” Plan can become demand in “Buy” plan

Q&A

Please Complete Your Session Evaluation

Evaluate this session in your COLLABORATE app. Pull up this session and tap "Session Evaluation" to complete the survey.

Session ID: 10181

Documents

Executing Oracle Projects ASCP, Inventory and Manufacturing