SAP Financials - Cash Journal Overview

-
In SAP, Cash Journal is used to record day-to-day cash transactions. This capturing of cash transactions is done with one screen which can be reached by menu path: Accounting → Financial Accounting → Banks → Incomings → Cash Journal or using transaction code FBCJ.
The most important concept of cash journal is cash journal code. Each cash journal (or register) is identified by its cash journal code. The above transaction (FBCJ) is opened in the context of a particular cash journal. With above transaction (FBCJ), cash journal (or the entries within it) can be seen with specified date range and based on that date 'Opening balance' and 'closing Balance' are displayed (along with total receipts and payments).



Please note that at a time same cash journal cannot be opened more than once unless it is opened in display-only mode.
In cash journal, entries are done in the context of Business Transaction type. Business Transaction indicates the type of transaction/entry and carries out certain validation checks. For example, if the transaction is a vendor transaction (payment to vendor), it makes sure that a valid vendor is entered. In other possible scenarios it can bring a default G/L account and allow or disallow modifying this account code (depending on the configuration settings of that business transaction).
Each transaction posted in cash journal creates a corresponding accounting document. One line of that document is recorded with the G/L account entered with the cash journal entry, while the other line (of the accounting document) is recorded with the G/L code that is mapped with the cash journal (in cash journal configuration); and this is one of the most important concepts that each cash journal must mapped to one and only one G/L account, although one G/L account can be used in multiple cash journals.

Popular posts from this blog

Medical Codings – An Overview

-
Image
Bertillon Classification of Causes of Death, introduced by a French physician in 1893 at a congress of International Statistical Institute in Chicago, is generally considered the origin of the most well known medical coding ICD - 'International Classification of Diseases', currently being used to classify the causes of mortality as well as morbidity (diseases and other health related problems). The primary purpose of a medical coding is to apply codes to clinical terms or information. In its simplest form you can think of it as a dictionary mapping clinical terms to codes (where each term is associated with a unique code). It is an integral part of clinical documentation. Classically it's being used to generate statistical reports. Coding the diagnostic and treatment information in insurance claims is another common use of it. Medical classification is being used internationally for more than hundred years, but it is the advancement in information technology that opened up
Read more

Brightpearl and Spree Commerce

-
Introduction We recently did a project for a client in the Middle East. They were looking for an ecommerce system along with a business management application for inventory management, purchasing, sales order management and financial accounting. Believing Spree Commerce as one of the most exciting ecommerce platforms, we simply proposed it. However for other business management needs we had no obvious choice. We found various open source and cloud based solutions but surprisingly there were very few (or may be none) which were satisfying our criteria:  cost effective, easy to implement with minimum configuration and implementation effort/time, and easy to integrate with third party systems (Spree Commerce in our case).  In short we found Brightpearl the most suitable for our need. The most useful feature of it is its intuitive and easy to use UI and API. API enables it to be integrated with third party systems. In this post I am going to share with you my experience of integ
Read more

Clinical Decision Support and Meaningful Use Stage II

-
I have just completed the design/specification of clinical decision support feature for an EHR system. The EHR vendor I am working for these days is seeking to have their system certified for Meaningful Use stage II. Hence the objective was to design clinical decision support that fulfils EHR certification criteria as mentioned here:  http://www.healthit.gov/sites/default/files/170_314a8cds_2014_tp_approvedv1.3.pdf Another objective was to design it in a way that makes it possible to create clinical decision support interventions declaratively in order to support clinical quality measures (instead of coding the logic in the system through programming in order to show an alert for example). Certification requirements says that the users should be able to select CDS interventions based on each one and at least one combination of the following data: Problem list Medication list Medication allergy list Demographics Laboratory tests and value/results Vital signs Th
Read more