Deliverables of clients(Sandia National Laboratories) project and services: Modules: AP, AR, FA, CM, PA, GL, Procurements,

Adv Collections, iExpense Project Type: Implementation, Upgrade and Support Oracle Version: R12.2.1 During Sandia Project implementation/upgrade/Support, I was able to accomplish in the following phases and signed off necessary documents in the sequential order Analysis Phase: Gather Business Requirements (RD.050), Identify Reporting Requirements (RD.080), Analyze High Level Gaps, Map Business Requirements (BR030), Establish Sandbox Instance, Identify Test Scenarios, Define Transition (Go-Live/Release) Strategy Solution design phase: Define Application Set Ups (BR.100), Defined Security Profiles (BR.110), Revised Future Process Maps, Identify & Resolved Detailed Gaps, Defined Design & Build Standards, Created RICEW Functional Designs (MD.050), Defined Conversions (MD.050), Developed CRP1 Test Scripts, Conducted CRP1 Testing, Conducted End User Training Needs Analysis (AP.130/140) Build Phase: Created and Update configuration documentation(BR100) , Prepared CRP2 Environment, Prepared Development Environment, Created RICEW Programs, Perform RICEW(Report, Interface, Conversion, Extension, Workflow) Validation Tests, Created User Reference Manuals, Prepared CRP2 Test Scripts, Conducted CRP2 Testing, Conducted Performance Tests, Prepared User Training Documentation, Developed Transition and Contingency Plans Transition Phase: Install Conversion Programs, Converted and Verify Data, Completed Integration Testing (CRP3), Completed UAT Testing, Conducted User Training Events, Prepared Production Environment, Set Up Applications, Implement Production Support Architecture, Verify Production Readiness, Start Production/Go-Live

Analyze and document application setup steps, process changes, and test scenarios necessary to in the following details: Deploy Buyer's Work Bench for Procurement Implement Smart Forms and Templates Implement AME for Special Approvals

Move Inventory Items into iPro catalogs to retire Core Apps PR form Implement Global Purchase Agreements Migrate Blankets and Releases to Global Purchase Agreements Migrate CPAs to Global Purchase Agreements Implement Category conversion to UNSPSCs Implement iPro Catalog Migration Implement Sourcing Abstracts to replace Opportunities Website Implement Contingent Worker functionality which allows contract workers to enter PR in iPro Structural changes to data tables Impact to banking processes and customizations Impact to payables payment processes and customizations Potential impact resulting from Bank change after R12.1 upgrade ( From BoA to US Bank) XML publisher strategy to manage forms change to XML for payments

Documented strategic analysis with the goal of identifying Oracle Subledger Accounting module including: Creation of double-sided accounting entries to be transferred to the General Ledger Account Analysis & Drilldown from GL to view Account Balances from the General Ledger and drill down to supporting Journal Entries in SLA and the underlying transaction from each Subledger (Oracle 12.1.3 feature expected to improve audit trail and traceability) Online inquiry from the transaction: the Journal Entries created can be viewed (Oracle 12.1 feature expected to improve audit trail and traceability) Reduced manual efforts for the Primary Ledger Reconciliation to the Subledgers Analysis regarding the use of the secondary ledger for reporting to DOE HQ Analysis regarding the use of fund type in the accounting key as it relates to Project Accounting Analysis of how Sandia can simplify the use of fund type in the accounting key for General Ledger and Project Accounting. Modules that should be converted to Oracle Subledger Accounting during the upgrade to version 12.1.3 and which modules the implementation of Subledger Accounting should be deferred structured in a time line. Recommendations when the conversion should be performed related to a new fiscal year. Detailed lookup tables, accounting rules, and custom sql code to do the conversion from Auto Accounting and Account Generator to Subledger Accounting

 A list of common or expected problems that might be encountered during the implementation, testing and post deployment efforts A detailed task plan for the upgrade from both Oracle Account Generator and Oracle Auto Accounting Detailed set-up steps to customize with pl/sql Oracle Subledger accounting to create a secondary ledger for DOE reporting. Assist in the deployment and setup in OADV1 (test) environment: Implementation plan deployed into the OADV1 (test) environment. Demonstration of conversion using detailed lookup tables, accounting rules and custom sql code identified in conversion strategy. Define the sub ledger accounting events. Setup sub ledger accounting in Oracle Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger, Inventory(cost management), Projects, and Purchasing modules. Map the main ledger to the STARS ledger. Setup the accounting derivation rules for building accounting. Add necessary reference data to all accounting transactions. Setup the ledgers in the general ledger. Demonstrate the viability of subledger accounting with at least one module for a conference room pilot. Document all the setup of the subledger accounting in every subledger and the general ledger. Implementation plan documented and deployed into the OADV1 (test) environment that mitigates risk for AP structural changes to data tables, AP impact to banking processes and customizations, AP impact to payables payment processes and customizations, AP potential impact resulting from Bank change and XML publisher changes. Implementation plan documented and deployment of iExpense to replace existing home grown expense report. Also, it requires credit card setup, configurations and interfacing with US Bank. Implementation plan documented and deployment of Advanced collection to replace existing AR base collections.