Inforln.com ERP LN 10.3 & 10.4 Project Peg Audit History Differences

1Copyright © 2013. Infor. All Rights Reserved. www.infor.comCopyright © 2013. Infor. All Rights Reserved. www.infor.com 1

LN: v10.3 -10.4 Project Peg Audit History DifferencesRollout trainingCampus Course Code: 02_0021040_EEN0442_ELN

July 2014

Patrick Noblett, Business Analyst, [email protected]

mailto:[email protected]

2Copyright © 2013. Infor. All Rights Reserved. www.infor.com

Intended Audience• Pre-Sales• Consulting• Support

• Pre-Requisites• Project Pegging Solution introduced in LN 10.2


Agenda• Why

• Big picture

• Business Problem & perspective

• Business Requirement

• How• Solution Overview

• Solution Process

• What• Solution Details

• Solution Non-Functional Aspects

• Summary


Big Picture• In an Aerospace & Defense environment it is required to track costs to

contracts in a fair and unbiased manner. • A Government Agency can come in an audit a contract/project at any time.• Systems tend to have the ability to define specific rules for commingling

requirements on supply orders across projects.• Manipulating which projects/contracts get costs should not occur as that would not

be unbiased or fair distribution of costs. (causing higher costs on Cost Plus Contracts versus Fixed Price). If any changes to system logic occurs then have to explain why.

• Production and Purchase Receipts are not always full receipts because of delays, resource issues, etc.• When partial receipts occur, project pegs are selected based on system

requirement dates and should have some information about the basis for the system data


Business Problem• A&D companies need the ability to capture why manual changes to

project pegs on supply orders occur to show internal and external auditors

• A&D companies are audited by their customers and must show• Why project pegs were modified, changed

• Why project pegs were selected when partial receipts occur

• This should all be based on fair and unbiased logic

• Failing Audits can cause fines and could cause loss of contracting privileges to the government agency for a period of time.


Business Requirement• Project Peg Audit Reason Codes should cover why users manually added, removed or

changed existing project pegs

• History of project peg changes by project

• Partial Receipts should have information as to why the project pegs selected were selected.


Solution• Parameter to implement• Specific Reason Codes for Capturing changes to Project Pegs• Capturing the reason code and the historical information• Capturing the logic of what project peg was received


Solution Details• Parameter to implement

• Project Pegging Parameters (Audit)• Manual Project Peg Modification

• Project Peg Receipt Transactions

• New Reason Code Type• Project Peg Audit History


Solution Details• Supply Order Origins

• Production Orders

• Requisitions

• Request for Quotations

• Purchase Orders

• Service Depot Repair Orders

• Cost Peg Transfers

• Adjustment Orders/Cycle Count Orders


Solution Details• Project Peg Audit History (Central Session)

• Found in Project/Contract Management/Cost Peg Audit History

• Reviewing which project pegs have been impacted by a user

• Change Type• Created/Modified/Deleted/None

• Project Peg Audit• Project/Project Peg/Quantity/None


Solution Details - Project Peg Audit History (tpctm2500m000)


Solution Details -Project Peg Audit History (tpctm2500m000)• Reviewing which project pegs have been

• Filter Options• Date, Order

• Order, Date

• Order, Distribution Line

• Item, Order

• Contract Line, Order

• Project, Order

• Old Project, Order

• User

• Print Options


Solution Details – Receipt Line Project Peg Audit Session (whinh3579m000)


Solution Details – Adjustment Order/Cycle Count Line Project Peg Audit Session (whinh5127m000)• When system generated project peg• Identifies the origin of the project peg

• Loss, Gain and Multiple version of Loss Gain

• Identifies• Excess Balance

• Available to Transfer (ATT) Balance

• Gain Balance

• Loss Balance

• Print session for Review


Solution Details – Adjustment Order Line Project Peg Audit Session (whinh5127m000)


Mention limitations / items out of scope• Deleting/Cancelling whole supply orders does not require a project peg

reason code


Summary• A&D customers need a way to show auditors

• who changes project pegs

• What pegs were selected for partial receipts (snap shot of the project peg need dates)

• Solution• New Reason Codes

• Central session to review all project peg changes

• Sessions to show what project peg received what items and why

Inforln.com ERP LN 10.3 & 10.4 Project Peg Audit History Differences

Software

Transcript of Inforln.com ERP LN 10.3 & 10.4 Project Peg Audit History Differences