Example ABAP / SAP Error Code : 0FILA

Filename: 0-F-I-L-A

SAP Program / SAP BW Program: SAPLFILACUST

SAP Transaction Code Description: Customizing LAE Initial Screen

SAP Transaction Code Tag: 0FILA

SAP T-Code ID: 1

read more...

Inventory Accounting Entries

Inventory Accounting Entries
For Example: during Goods Receipt

Stock Account - Dr
G/R I/R Account - Cr
Freight Clearing account - Cr
Other expenses payable - Cr

During Invoice Verification

G/R I/R Account - Dr
Vendor - Cr

When the Goods are issued to the Production Order the following transactions takes place:

Consumption of Raw Materials - Dr
Stock A/c - Cr

When the Goods are received from the Production Order the following transactions takes place:

Inventory A/c - Dr
Cost of Goods Produced - Cr
Price difference - Dr/Cr
(depending on the difference between standard cost and actual cost)

When the Goods are dispatched to customer through delivery the following transactions takes place:

Cost of Goods Sold - Dr
Inventory A/c - Cr

When the Goods are issued to a Cost Center or charged off against expenses the following transactions takes place:

Repairs and Maintenance - Dr
Inventory A/c - Cr

When the Goods are stock transferred from one plant to another, the following transactions takes place:

Stock A/c - Dr (Receiving location)
Stock A/c - Cr (Sending location)
Price difference - Dr/Cr
(due to any difference between the standard costs between the two locations)

When the stocks are revalued, the following transactions takes place:

Stock A/c - Dr/Cr
Inventory Revaluation A/c - Cr / Dr

When the Work in Progress is calculated the following transaction takes place:

Work in Progress A/c - Dr
Change WIP A/c - Cr

Physical verification /shortages and excesses : Shortages/excesses on authorizations shall be adjusted using the physical inventory count transaction.

read more...

SAP BADI Program Interface

Besides program and menu enhancements, you can also create screen enhancements for business Add-Ins. Screen enhancements are not supported, however, for Business Add-Ins designed for multiple use.

With the old enhancement technique based on customer exits, X function groups were used for data retention and data processing purposes. These tasks are now performed by a user function group or a module pool if you implement a screen enhancement using BAdIs. The instance of the implementing class is only used for data transport.

The name of the function group lies in the namespace of the implementing person/user. The 'X' which was necessary at the beginning of a function group in case of customer exits is now no longer required and therefore eliminated.

An instance of the BAdI class must be passed to the user of the BAdI to allow that user to get the data to be displayed on the screen. For this purpose, the instance is saved in a public static readomly attribute DYNPRO_INSTANCE of the BAdI class. This attribute is generated.

A public static method SET_INSTANCE_FOR_SUBSCREEN sets the attribute on the application side to the parameter passed. Using the method GET_INSTANCE_FOR_SUBSCREEN the parameter is then read on the user side.

Different sub screen states can be represented by different instances.




The relationships shown between the calling program, the classes and the user function group or module pool are illustrated below by means of an example.

Example:

A user wants to display flight data in a transaction and enters the airline carrier, the flight number, and the flight date first.


At the specific request of the customer, you are to enhance this function to allow the user to additionally display the time of departure and arrival as well as the departure and destination airport.

The definition of a Business Add-In containing the functionality required is then delivered to the customer. If the customer creates an implementation, the system displays additional fields.

read more...

Information model for SAP BW

SAP BUSINESS WAREHOUSE information model is based on the core building block of InfoObjects which are used to describe business processes and information requirements. They provide basis for setting up complex information models in multiple languages, currencies, units of measure, hierarchy, etc. The key elements in the SAP BUSINESS WAREHOUSE information model are:

• DataSources
• InfoSources
• ODS Objects
• InfoCubes
• InfoProviders
• MultiProviders

Data Sources

Data Sources are flat data structures containing data that logically belongs together. They are responsible for extracting and staging data from various source systems.

InfoSources

Info Sources are the group of Info Objects that belong together from a business point of view. It contains the transactional data obtained from the transactions in online transactional processes (OLTP) and master data such as addresses of customers and organizations, which remain unchanged for longer time period.

ODS objects

An ODS object is a dataset which is completely formed as a result of merging data from one or more info sources. In it information is stored in the form of flat, transparent database tables that are used for preparing reports and quality assurance purposes.

InfoCubes

Info Cubes are multidimensional data storage containers for reporting and analysis of data. They consist of keys figures and characteristics of which latter is organized as dimensions facilitating users to analyze data from various business perspectives such as geographical area or types of sales channel.

InfoProviders

Info Providers refer to all the data objects available in the SAP BUSINESS WAREHOUSE systems. These include all the data targets viz. Info Cubes, ODS objects and also master data tables along with Info sets, remote Info cubes and Multi Providers.

MultiProviders

MultiProvider is a virtual information provider that is a combination of any two physical or virtual info providers. Multi Providers which doest not contain any data and are used to combine data from different info providers. Their main purpose of this is to make this data accessible for reports and analysis.

read more...

SAP QM in Logistics

Thë QM componënt is intëgratëd in crucial phasës of thë procurëmënt procëss. It supports thë procurëmënt activitiës by mëans of functions such as:

• Vëndor Ëvaluation
• Vëndor block
• Vëndor Rëlëasë for rëquësts for quotation and purchasë ordërs
• Assigning tëchnical dëlivëry tërms and quality assurancë agrëëmënts
• Cërtificatë procëssing
• Status administration of thë supply rëlationships
• Incoming inspëctions
• Goods rëcëipt inspëctions

If your company purchasës matërials from ëxtërnal vëndors, you can implëmënt thë QM in Procurëmënt (QM-PT-RP-PRC) componënt to support your procurëmënt procëssës for quality assurancë purposës.

If you want to implëmënt thë QM in Procurëmënt componënt, your company must also usë thë Purchasing (MM-PUR) componënt. If you rëquirë functions for procëssing goods movëmënts, you must also install thë Invëntory Managëmënt (MM-IM) componënt.

You can implëmënt thë QM in Procurëmënt componënt as a stand-alonë componënt or togëthër with thë Quality Inspëction (QM-IM) componënt. As a stand-alonë componënt, you can usë all procurëmënt functions ëxcëpt thosë for procëssing goods rëcëipt inspëctions. To procëss such inspëctions, you nëëd thë Quality Inspëction componënt.

Using thë functions of thë QM in Procurëmënt componënt, you can:

• Managë quality-rëlatëd information for matërials, vëndors, and manufacturërs in quality info rëcords
• Rëlëasë or block vëndors and manufacturërs
• Monitor thë QM systëms of vëndors and manufacturërs
• Supply quality documënts with rëquësts for quotations and purchasë ordërs
• Ëvaluatë vëndors on thë basis of quality
• Cërtify vëndors or manufacturërs that havë QM systëms implëmëntëd, to rëducë thë inspëction rëquirëmënt
• Managë and rëlëasë supply rëlationships
• Rëquëst that quality cërtificatës bë submittëd with thë dëlivërëd goods and monitor thë rëcëipt of thësë cërtificatës
• Inspëct vëndor goods at vëndor sitës (sourcë inspëctions)
• Inspëct vëndor goods upon rëcëipt (goods rëcëipt inspëctions)
• Managë thë postëd goods in inspëction stock
• Block thë paymënt of invoicës until thë goods havë bëën inspëctëd and accëptëd
• Procëss goods rëcëipt inspëctions for manufacturër-spëcific matërials
• Inspëct goods that havë bëën ëxtërnally procëssëd whën thëy arë rëturnëd in a goods rëcëipt

read more...

All About BAPI (SAP Interface)

In SAP, BAPI IS A STANDARD SAP INTERFACE ,., IT IS PRECISELY DEFINED INERFACE PROVIDING ACCESS PROCESS AND DATA IN BUSINESS APPLICATION SYSTEM SUCH AS SAP R/3,.,THE SAP BUSINESS OBJECTS STORED IN THE BUSINESS OBJECT REPOSITORY(BOR) ENCAPSULATES THEIR DATA AND PROCESS,., EXTERNAL ACCESS TO THE DATA AND PROCESSES IS ONLY POSSIBLE BY MEANS OF SPECIFIC METHODS,., BUSINESS OBJECT TYPES AND THEIR BAPI's ARE DESCRIBED AND STORED IN AN BOR(BUSINESS OBJECT REPOSITORY)


BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces,., They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components,., BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet,.,

BAPIs allow integration at the business level, not the technical level,., This provides for greater stability of the linkage and independence from the underlying communication technology.

read more...

SAP Service Management Introduction

Here is a big growth in trend for companies to provide certain services for other companies, either in conjunction with a specific product that they manufacture, or simply as a main line of business.,. Consequently, customer expectations of improved after-sales service have risen.,. Due to rapid expansion, an increasing number of companies no longer has the capacity to cover all requests for maintenance and service in-house.,. Even where capacity exists, the specialized technical knowledge required to service a wide range of what may include highly complex equipment is seldom available under one roof.,. Many companies are finding, moreover, that it can be more cost-effective to outsource at least part of their service capacity.,.


SAP R/3 Service Management gives an integrated approach to manage activities of various service providers.,. The services may be internal like providing maintenance support to external like servicing of an equipment at client’s site.,. The service management covers wide range of services from a simple process of providing on-line support to erection and commissioning of a machine.,. It covers services covered under warranty, under annual maintenance contract and chargeable services.,. The services may be rendered to an equipment or a functional location.,.
SAP R/3 Service Management (SM) Module handles ‘Call Management’ very efficiently.,. The process flow from ‘call logging’ to ‘call processing’, ‘call monitoring’, ‘call closing’ and billing is handled in very systematic way.,. ‘Call Logging’ function is very effective and can be used for the ‘Front Office’.,. Various default tasks like ‘Call back to customers in specified time’ are taken care.,. The Service management Module is integrated with Sales Management Module and the calls can be handled using Sales Order.,.
Allocating the Service Tasks and Resource Capacity Planning is also possible in the Service management (SM) Module.,. Real time cost of call processing can be monitored.,. Various activities required for the processing can be maintained with their labor costs.,. Components Costs also can be captured.,. The Materials Management (MM) module is also integrated and the components used from the stock will be reduced from the inventory.,.
SAP R/3’s excellent reporting functionality is also available for this module and reports from various angles can be generated.,. These reports help Management to locate the areas for improvement in their work.,.

read more...