Big4GuyWelcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.
|
SAP R3 like other modern day ERPs uses the document principle. The document principle simply means that the R/3 system records atleast one document for every business transaction. In other words, each transaction in SAP R/3 can be traced back to a unique document with the help of a document number. Each document created in SAP R3 system is assigned a unique document number. The document number can assigned by SAP R3 automatically using internal number ranges or users themselves can assign document number using external number ranges.
To help you understand better, each document in SAP can be dentified using a document number, company code and fiscal year. Some business events result in the creation of more than one document in SAP. Depending upon the type of business transaction, SAP system decides what documents need to be created. For example, receipt of inventory may result in the creation of an inventory document as well as an accounting document for tracking financial GL information. SAP R3 is unique in the sense that it links related documents so as to provide a complete picture of a transaction within the SAP R/3 system. More on the SAP documents in my next post.
Related Posts
SAP BW Infocube Guide
SAP Schedule Manager for Period Closing
ABAP 4 Programming Basics
Managing SAP R/3 Implementation
No Comments for this post yet...
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||