22-07-2014, 10:35 AM
4G TECHNOLOGY
“4G TECHNOLOGY.doc (Size: 169 KB / Downloads: 8)
INTRODUCTION OF SAP
SAP was founded in 1972 by five people: Wellenreuther, Hopp, Hector, Platter and Tchira. Wellenreuther, while working at IBM, developed a financial accounting package running in batch for and IBM customer - Naturin. SAP bought rights from Naturin and started to design and implement the real time finance system as a standard package based on Wellenreuther’s experience in the application they sold the first copy of the standard system to ICI.
Simultaneously, they developed a material management system as bespoke software for ICI by reserving all property rights
SAP MODULES
SAP R/3’s applications have different modules. They can be used either alone or combined with other solutions. These modules also support each other for easy flow of business
DATABASE LAYER
The database layer consists of a central database system containing all of the data in the R/3 System. The database system has two components – the database management system (DBMS), and the database itself. SAP does not manufacture its own database. Instead, the R/3 System supports the following database systems from other suppliers: ADABAS D, DB2/400 (on AS/400), DB2/Common Server, DB2/MVS, INFORMIX, Microsoft SQL Server, ORACLE, and ORACLE Parallel Server.
The database does not only contain the master data and transaction data from your business applications, all data for the entire R/3 System is stored there. For example, the database contains the control and customizing data that determine how your R/3 System runs. It also contains the program code for your applications. Applications consist of program code, screen definitions, menus, function modules, and various other components. These are stared in a special section of the database called the R/3 Repository, and are accordingly called Repository objects. You work with them in the ABAP Workbench.
INTRODUCTION OF PROGRAMMING ABAP/4
ABAP/4 is short for ADVANCED BUSSINESS APPLICATION PROGRAMMING 4GL. ABAP/4 is SAP’s forth generation language and it is the backbone of the R/3 system. All of the R/3’s application and even parts of its basis system where developed in ABPA/4. The language’s flexibility and ease of use combined with its specially designed commends enables you to quick design and implement both small-and large-scale business solutions for R/3 systems
More about ABAP/4
ABPA/4 is the programming language used by SAP’s developers to build the transaction that make up the R/3 application. Corporations to customize the R/3 application also use it. In general, isn’t used by customers of SAP to develop complex applications from scratch, but instead to provide additional business functionality don’t use ABAP/4. For example, it’s not necessary for a customer to write a program in ABPA/4 to manage inventory levels, because SAP has already written transaction to accomplish this objective.
The two most common uses for ABAP/4 are producing custom report and developing custom interfaces for SAP. In this context, a report is an ABAP/4 program that reads specific data from SAP’s database and then displays the data via a computer screen or a printed page. An interface, on the other hand, is an ABAP/4 program that moves data into SAP, or reads data from SAP and write it out to a system file to be transferred to an external computer system, such as a legacy mainframe. Other uses for ABPA/4 include conversion programs that change data into a format usable by SAP, and custom transaction similar to the SAP transactions that make up the R/3 application, but are written by users to fulfill some business function not provide SAP.
COMPILATION AND RUNTIME BEHAVIOR
At run time source code of an ABPA/4 program is compiler to a program code that runs interpretive. This compilation process is also called generation. The generated form of a program is stored in the ABPA/4 repository. Once a program has been generated, it is automatically re-generated if the source code or one of program’s referenced Dictionary objects is change. The ABPA/4 runtime system generated a program automatically when it is needed, so you don’t have to bother with it.
ABPA/4’s interpretive nature has some significant advantage for the developer.
We can rapid created and test a prototype of an application.
Change to dictionary object only affected those programs that use the object and are executed after the changes the edit-debug cycle is shortened.
The generated forms of programs can be distributed across a network, such as a distributed R/3 system. Whenever a runtime system is available on the network node, any program that has been put on the network can be executed. Therefore, the program don’t have to be run from a single server, but can instead be run on local servers, to optimize the use of local resources
Requisitions can be created indirectly in the following ways Via materials planning and control
The component Consumption-Based Planning suggests materials that needs to be the basis of past consumption or usage figures and existing stock levels. The order quantity and the delivery date are determined automatically.
Materials planning and control can stipulate that a purchase requisition is to be resubmitted to the purchasing department if it has not been processed after a predefined period of time.
Via networks from the R/3 project system)
Requisitions are generated automatically from network if:
• A material component with non-stock material or an external service component has been assigned to an operation and
• The indicator allowing automatic generation of requisitions immediately the network is saved has been set in the network.
In this way, requisition can be forwarded to Purchasing early in the Planning phase
If the indicator has not been set the system passes the data on to materials planning and control when the network is released. The latter component then creates the requisition.
Via maintenance order (from the R/3 components PM Plant Maintenance and Service Management)
Requisitions are generated automatically from maintenance and order if:
• A material component with non-stock material has been assigned to an operation, or
• An operation with the control key for external services has been created.
Via production order (from the component PP Production Planning and Control).
Requisitions are generated automatically from production order if:
• They contain an external processing operation. A precondition is that the control key for the operation allows or prescribes external processing.
They contain non-stock components
Purchase order (PO)
The buying entity’s request or instruction to a vendor (external supplier) to supply certain materials or render/perform certain service/works, formalizing a purchase transaction.
Purpose
The purchase order can be used in various procurement processes. You can procure both material (for direct consumption or stock) both external services. Furthermore, the special procurement type “subcontracting”, “third-party” (involving triangular business deals and direct-to-customer shipments) and “consignment” are possible.
You can use purchase order to cover your requirement using external sources (i.e. a vendor supplies a material or perform a service). You can also use a purchase order to procure a material that is needed in one of your plants from an internal source, i.e. from another plant. Such transactions involve longer-distance stock transfers. The activities following on from purchase order (such as the receipt of goods and invoice) are logged, enabling you to monitor the procurement process.
You can use purchase orders for once-only procurement transactions. If, for example, you wish to produce a material from a vendor only once, you create a purchase order. If you are thinking of entering into a longer-term supply relationship with this vendor, it is advisable to set up a so-called outline agreement, since this usually results in more favorable conditions of purchase.
Integration
MM External Services Management is completely integrated into the Materials Management system. The master data for the procurement of services can be stored in service master record, for example, which subsequently provide default data for the purchasing documents. Service specification for a concrete procurement project are not created and processed separately each time (e.g. as bid invitation or contract specifications), but entered directly in the purchasing document (e.g. in a request for quotation, purchase order or contract).
Accounting document
If the movement is relevant for Financial Accounting (that is, if it leads to an update of the G/L accounts) an accounting document is created parallel to the material document.
In some cases, several accounting document are created for a single material document. This might be the case, for example, if you have two material document items with different plants that belong to different company codes. The G/L accounts involved in a goods movement are updated through an automatic account assignment.
For goods receipt for purchase orders, good movements for stock transport order and consignment with drawls, business partners may have different local currencies. Therefore, as well as the local currency, the accounting document must also contain another currency for processing and postings. For this purpose, accounting documents created as a result of these goods movement will automatically be managed in the local currency and in the document currency.
CONCLUSION
As we know that the SAP R/3 is an integrated business system designed to help organization run such business process as managing inventory, creating requisitions, processing sales orders, paying invoices and so on.
SAP R/3 provides a single integrated system to handle the needs of all departments in a corporation. This integration is the single biggest advantage to SAP R/3.
As per the discussion in the study we conclude that:
SAP R/3 is rich in functionality & highly configurable.
With the help of SAP R/3 a minimum data redundancy & maximum data consistency is possible.
With the help of SAP R/3 Online information of customers, stocks, sales etc. is possible.
Availability of complete details of all equipment across the company with maintenance history is possible through SAP.
With the help of SAP R/3 seamless handing of database is possible.