Sunday 2 August 2015

BADI (Business add ins)

Scenario 4 :


When ever we create a Purchase order the vendor supply's goods to the warehouse department.
The warehouse department check the goods against  the our purchase order whether the goods which we requested supplied or not if the goods are matched then the ware house people create goods receipt (GR) with MIGO transaction with 101 Movement type. The plant finance people physically verify the goods against the GR and prepare the IR(invoice receipt) document.
           Against IR document the account payable department pay the amount to the vendor with the deduction TDS of amount. After few days the vendor asks the Form 16A to finance people so that he can get (TDS) money back. At the time of generating form 16 the finance department must provide LR Number, Vehicle number, Transport name. These information is not  captured in the entire MM life cycle. Here we implement the BADI to attach additional subscreen which contains above fields to MIGO transaction.






So that we can easily save all these details in one Z_table and we can get these data any time we want. this will improve the performance and it is easy for maintain these details.

Scenario 5: -
            The warehouse people issue the goods against cost center by using MIGO or MB1A transaction code with 201 movement type. Some times they entered invalid cost center. To avoid this we implement the BADI to thrown an error message if they pass invalid cost center or cost center not belongs to that plant.



No comments:

Post a Comment