How to pass multiple parameters in REST API web service
Introduction: The purpose of this document is to demonstrate how we pass multiple set of parameters in REST API through Postman. Cause of the issue: Whenever we test any REST…
Read MoreExploring the New Security Features in Oracle Database 23ai
Oracle Database 23ai introduces advanced security features designed to enhance data protection, simplify configurations, and align with modern security standards. These updates strengthen the database’s security posture and improve usability…
Read MorePurchase Invoice GL to AP Drill down for Account Analysis Reconciliation
Introduction: This document outlines how to reconcile Oracle General Ledger (GL) and Oracle Payables (AP) for Purchase Invoice analysis by using a specific SQL script to drill down to the…
Read MoreAP: Create Accounting Completed In Warning with Offsets Error
Issue Overview: The error “The accounting program cannot create this journal line because the debit or credit that offsets it cannot be found” occurs when attempting to run the Create…
Read MoreAR Invoice Created Through Autoinvoice Cannot Be Completed Due To Error
AR Invoice Created Through Autoinvoice: Cannot Be Completed Due To Error Error ORA-01407: cannot update (???) to NULL ORA-06512: at “FUSION.ARP_UTIL”, line 6272 ORA-06512: at “FUSION.ARP_UTIL”, line 6242 ORA-06512: at line 1 Solution – Navigate to AR System Options (Manage Receivables System Options) – Change the field ‘Document Generation Level’ to ‘When Saved’ – Save the changes
Read MoreSLA Customization in Oracle Fusion.
What is Subledger Accounting? Oracle has provided standard accounting derivation for all the possible events of different aspects of business. However, there could be requirements of deriving custom accounting on certain conditions or business events. Subledger Accounting (SLA) is a rule-based accounting engine that centralizes accounting for Oracle Fusion products. Subledger Accounting is not a separate product in itself, rather it is Oracle’s engine catering to the accounting needs of both Oracle and external modules. Together with the ledger support, Subledger Accounting enables support of multiple accounting requirements concurrently in a single instance. Different accounting regulations can be satisfied by maintaining and applying different sets of rules to different sets of transactions, or accounting for the same transaction with multiple methods. Subledger accounting options define how journal entries are generated from subledger transactions at the subledger application level. Subledger accounting customizations comes in handy for such requirements. It has been first introduced in Oracle Applications e-business suite. Oracle fusion has leveraged the same functionality and extended it to a greater flexibility to derive accounting, descriptions, references and other components by using various conditions and even formulas which makes it even more flexible and result oriented. The different components to achieve such complex accounting derivations are as given hereunder: Mapping Sets Account Rules Journal Line Rules Description Rules Events Subledger Journal Entry Rule Sets Accounting Method Ledger Mapping Sets Mapping sets provide an efficient way to define a segment or account combination value for one or more transaction or reference attribute values. Using such input and output mappings is simpler than using complex conditions on account rules. Based on the value of the source input, a single segment or a full account is derived. Account Rules These are the rules that determine from where an accounting flexfield value is taken or how it is derived. Oracle does provide seeded rules, however one can create one’s own rules to derive accounting flexfield segment values. The following rule types are available: Account combination Segment Value Set Journal Line Rules These are the rules that determine whether a subledger journal line will be a debit or a credit line, whether lines with the same account should be merged and what the accounting class of the line is. The Link Journal Lines option determines whether the journal line rule is set up to establish a link between the accounting of transactions that are related both within the same application, and across applications. In the seeded definition, no link is established. Description Rules These are the rules that determine what appears on the subledger journal entry at the header and/or the line. The definition determines both the content and sequence in which the elements of the description appear. Event Events are used to process transactions, i.e. the transaction drives the accounting event. E.g. the SLA setup for the transaction Addition, e.g. is built under the event Addition and the event CIP Addition. There are also non-accountable events, like an amortized life change where no subledger journal entry is created from the event. Subledger Journal Entry Rule Sets The component rules (Account Rules, Journal Line Rules, Description Rules, and Supporting References) are now combined under the Subledger Journal Entry Rule Sets to form the complete set of rules per accounting event for the subledger.…
Read MoreResolving the Issue about , User PC not connecting to Wireless access point network
Resolving the Issue about , User PC not connecting to Wireless access point network
Read MoreResolving the IP address Setup and IP reserved process in the SolarWinds server.
Resolving the IP address Setup and IP reserved process in the SolarWinds server.
Read MoreUsage Metrics in Power BI
INTRODUCTION: Knowing how your content is being used helps you demonstrate your impact and prioritize your efforts. Your usage metrics may show that one of your reports is used daily by a huge segment of the organization. It may show that nobody is viewing a dashboard you created at all. This type of feedback is invaluable in guiding your work efforts. If you create reports in workspaces, you have access to improved usage metrics reports. They enable you to discover who’s using those reports throughout your organization, and how they’re using them. You can also identify high-level performance issues. The improved usage reports for shared workspaces replace the usage metrics reports documented in Monitor report usage metrics. Note You need a Power BI Pro or Premium Per User (PPU) license to run and access the usage metrics data. However, the usage metrics feature captures usage information from all users, regardless of the license they’re assigned. To access usage metrics for a report, you must have edit access to the report. Your Power BI admin must have enabled usage metrics for content creators. Your Power BI admin may have also enabled collecting per-user data in usage metrics WHY DO WE NEED THIS SOLUTION: Usage metrics in Power BI are important because they provide insight into how users are interacting with your reports and dashboards, allowing you to identify which content is being used most frequently, by whom, and when, which helps you optimize your reports, prioritize development efforts, and understand the impact of your BI initiatives within the organization. Key benefits of using Power BI usage metrics: Identify valuable reports: Understand which reports are most frequently accessed and used by users, allowing you to focus on improving and maintaining those key reports. Improve report design: Analyze user behavior to identify areas where reports may be confusing or lack necessary information, leading to better design and user experience. Monitor user engagement: Track which users are actively engaging with your reports and dashboards, identifying potential gaps in training or areas where specific user groups may need additional support. Prioritize development efforts: Allocate resources effectively by focusing on developing new reports or features that address the most pressing user needs based on usage data. Demonstrate impact: Use usage metrics to showcase the value of your Power BI reports to stakeholders by highlighting how widely they are being used HOW DO WE SOLVE THIS: Only users with admin, member, or contributor permissions can view the usage metrics report. Viewer permissions aren’t enough. If you’re at least a contributor in a workspace in which your report resides, you can use the following procedure to display the usage metrics: Open the workspace that contains the report for which you want to analyze the usage metrics. From the workspace content list, select More options (…)for the report and select View usage metrics report. Or open the report, then on the command bar, select More options (…) > Open usage metrics. The first time you…
Read More