Best Practices for Oracle technology and applications
20
page-template-default,page,page-id-20,ajax_fade,page_not_loaded,,qode_grid_1300,footer_responsive_adv,hide_top_bar_on_mobile_header,qode-child-theme-ver-1.0.0,qode-theme-ver-16.7,qode-theme-bridge,wpb-js-composer js-comp-ver-5.5.2,vc_responsive
 

Best Practices

"A case study considered to be a good example of a business discipline."

According to DMReview, Best Practices can be defined as “A case study considered to be a good example of a business discipline.”

According to the Government Accountability Office (GAO), Best Practices can be defined as “the processes, practices, and systems identified in public and private organizations that performed exceptionally well and are widely recognized as improving an organization’s performance and efficiency in specific areas. Successfully identifying and applying best practices can reduce business expenses and improve organizational efficiency.”

Our hope is to bring together users of Oracle technology and applications and other key stakeholders such as consultants and other third party vendors to share their collective experiences and, by doing so, identify Best Practices for the implementation and use of Oracle technology and applications.

GL_SU_CONSOLIDATIONS submenu anomaly

This blog focuses on a design flaw in this submenu whereby you cannot maintain the Consolidations mapping using the standard Consolidations submenu.  You need to identify a function in order to give the user the ability to maintain consolidation mappings.

AR Adjustments design flaw

This blog demonstrates a critical design flaw in how AR adjustments are processed. We’ll show how a user can post more than one adjustment per transaction as long as it is within their approval limit.

Impact of using custom applications associated with Responsibilities

Use of SLA: Alternate Application Id to solve issues with SLA programs not  being able to run because they don’t know what ‘application’ is running the  program

Risks and recommendations related to Personal Profile Values form

User access to the Personal Profile Values form causes significant risk to the  integrity of the system, business process, security, and controls.  We discuss  these risks and make recommendations on how to mitigate such risks in this web blog

Basics of MOAC and current limitations

Focusing on basics of MOAC functionality and current limitations

Risks and recommendations related to AZN

Focusing on what are AZN menus and how to mitigate risks related to them.

SLA Process Design Flaw_Allowing Manual Journal Entries in Subledgers

Oracle introduced SLA in R12 and in doing so introduced a significant control weakness – the ability to enter a manual journal entry through various subledgers. This blog reviews how this is done and some related security flaws in standard menus and responsibilities.

Value Set Values Control Considerations

Values can be added to values sets in three functions – Value Set Values, Key  Flexfield Values, and Descriptive Values (same underlying form).  In this blog,  we look at controls considerations related to this form and recommendations  from a control perspective.

On-Hand Quantity form bug

The on-hand quantity form allows a user to do a Mass Issue or Mass Move. This blog illustrates this risk and suggests a personalization when necessary to make this form a ‘query-only’ form.

R12 New Copy Menu functionality

Focusing on new copy menu functionality available in R12’s Functional  Administrator responsibility.