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...