Capping IT Off

Capping IT Off

Opinions expressed on this blog reflect the writer’s views and not the position of the Capgemini Group

SAP PRA Roadmap Upgrades & Lessons Learned

Category : Applications

With a sleeker design, upgraded user interface and a better data model, the recent update to the SAP Production Revenue Accounting (PRA) module of the SAP IS-Oil solution set is akin to the newest model of your favorite car. Commonly referred to as the PRA Roadmap, it replaces what has traditionally proved to be the choice for upstream Oil & Gas companies seeking a fully integrated platform.  As Capgemini progresses through two separate PRA Roadmap Upgrade Projects, our team wanted to share some lessons learned.

Lessons Learned:

1.       Utilize the BRIO Portal and reconcile in reverse chronological order 

a.       The ONRR to MMS reconciliation is a prerequisite to the data model upgrade, and all previously reported months need to be reconciled between the old reporting engine and what has been submitted to the ONRR.   The ONRR’s BRIO database houses the production and royalty data reports submitted by E&P companies.  The most effective and sensible approach is reconciling in reverse chronological order. This allows the clean up to target the most recently filed months, which are most likely to process a PPA.

2.       Begin Business Process Mapping early in the project

a.       The three major transactional changes are the updated PRA Partner transactions, the new JIB Netting Payment Processing and the new Annual Withholding Workplace. Establishing the business and transactional mapping before testing is a big advantage to the project and will save you a lot of time and training down the line.

3.       Keep an  ABAP resource handy

SAP provides and supports the standard migration programs to transition to the new data model.  However, beefing up the migration logs or adding details in identifying faulty data can streamline the overall process. Whether it’s modifying the selection parameters to narrow down data to be migrated, or it’s handling the error resolution process through the programs rather than maintaining it post-migration, ensuring an ABAP resource is allocated to your project can help or exceed timelines.

4.       With that ABAP resource, plan the custom object remediation

a.       Data model changes spell trouble for custom programs.  Tables may change from one-to-many or many-to-one, so plan the remediation effort early if possible.

5.       Test this, test that, test it all

a.       Roadmap version of PRA requires testing the new functionality as well as scenario testing and regression testing.

Overall, the PRA Roadmap version is a substantial upgrade.  The new capabilities in reporting and functionality provide the end users with some pretty great improvements. The ONRR and data model update require planning, testing and development.   Capgemini not only has the PRA expertise in house, but can also lend assistance in custom program remediation and testing while keeping your costs predictable and stable.

About the author

tpetraki

Leave a comment

Your email address will not be published. Required fields are marked *.