This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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 – Adjustment Order/Cycle Count Line Project Peg Audit Session (whinh5127m000)• When system generated project peg• Identifies the origin of the project peg