Failover issues in Always-on AG
Failover issues in Always-on AG What is failover in always-on AG in SQL server.? In SQL Server Always On Availability Groups (AG), failover is the process of switching the…
Read MoreFailover issues in Always-on AG What is failover in always-on AG in SQL server.? In SQL Server Always On Availability Groups (AG), failover is the process of switching the…
Read MoreIntroduction SQL Server Query Store is enabled to assist in monitoring query performance and identifying query plan regressions. Query Store captures a history of query plans, making it an excellent…
Read MoreIntroduction In SQL Server, the tempdb system database can grow significantly due to heavy workloads, temporary objects, or large queries. Sometimes, even after reducing workload or removing temporary data, tempdb…
Read More1.Click on agent software once the connection mode set to offline. 2. Click on agent software. 3.Click on appropriate software that you need to download 4.Click download option 5.Click on check…
Read MoreFrom a Fresher to Project Manager: My 12-Year Journey at Doyensys “Do your work and the rest will follow.”– These simple words reflect the career journey of Akhash Ramnath—a story…
Read MoreAR 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 MoreWhat 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 MoreFixing Node Not Ready in Kubernetes Introduction/Issue: One day, while working on our Kubernetes cluster, we noticed that one of the nodes went into a NotReady state. This caused some…
Read MoreHow to give read permission on secondary replica in always-on AG Purpose of Log shipping: Always On availability groups feature is a high-availability and disaster-recovery solution that provides an…
Read More