2008 Jun 11 12:10 PM
Pls comment on how to add a user exit in T-code 'MIRO' wherein " Invoice date should be greater than GRN date".
How to use breakpoints (to find the right FM).
s dsilva
2008 Jun 11 12:56 PM
Dear S dsilva
The use the following function Modules for your purpose which will definitely give you an edge
1) EXIT_SAPLMR1M_002 - Customer Exit: Change Proposed Account Assignment
2) EXIT_SAPLMR1M_003 - Customer Exit: Pass On Document Header Data
3) EXIT_SAPLMRMP_010 - Customer Exit: Analyze Document Header and Item Data
The way of implementing and getting to know whether you do get the right functionality as desired for Invoice date and GRN date comparision is to go into each function module.
Click on the respective Include - it will generate a Warning message - do press enter and then for the time being do not store this into any transport request bu store the new include into a $TMP Package.
Here into the Include put a Static Break Point ' BREAK-POINT' but be sure that no body else is using MIRO transaction for the time being OR
put a dynamic break point 'BREAK UERID(SILVA01)'
and then run MIRO Transaction and look for values of parameters Invoice date and GRN date during debugging.
Hope this would give you enough clues how to tackle the issues and may be it will definitely resolve you issue.
Hope this helps you a lot.
Encourage others to answer you queries by suitably rewarding them
Thanks
Venugopal
Pls comment on how to add a user exit in T-code 'MIRO' wherein " Invoice date should be greater than GRN date".
How to use breakpoints (to find the right FM).
s dsilva
2008 Jun 11 12:44 PM
hi,
to check particular exit ,open function module of tht exit and double click on zinclude avilable in that and put breakpouint as break username.
these r exits avilable for miro transaction.
Transaction Code - MIRO Enter Invoice
Enhancement/ Business Add-in Description
Enhancement
LMR1M001 User exits in Logistics Invoice Verification
LMR1M002 Account grouping for GR/IR account maintenance
LMR1M003 Number assignment in Logistics Invoice Verification
LMR1M004 Logistics Invoice Verification: item text for follow-on docs
LMR1M005 Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006 Logistics Invoice Verification: Process XML Invoice
MRMH0001 Logistics Invoice Verification: ERS procedure
MRMH0002 Logistics Invoice Verification: EDI inbound
MRMH0003 Logistics Invoice Verification: Revaluation/RAP
MRMN0001 Message output and creation: Logistics Invoice Verification
Business Add-in
INVOICE_UPDATE Business Add-In: Logistics Invoice Verification
reward points if hlpful.
2008 Jun 11 12:56 PM
Dear S dsilva
The use the following function Modules for your purpose which will definitely give you an edge
1) EXIT_SAPLMR1M_002 - Customer Exit: Change Proposed Account Assignment
2) EXIT_SAPLMR1M_003 - Customer Exit: Pass On Document Header Data
3) EXIT_SAPLMRMP_010 - Customer Exit: Analyze Document Header and Item Data
The way of implementing and getting to know whether you do get the right functionality as desired for Invoice date and GRN date comparision is to go into each function module.
Click on the respective Include - it will generate a Warning message - do press enter and then for the time being do not store this into any transport request bu store the new include into a $TMP Package.
Here into the Include put a Static Break Point ' BREAK-POINT' but be sure that no body else is using MIRO transaction for the time being OR
put a dynamic break point 'BREAK UERID(SILVA01)'
and then run MIRO Transaction and look for values of parameters Invoice date and GRN date during debugging.
Hope this would give you enough clues how to tackle the issues and may be it will definitely resolve you issue.
Hope this helps you a lot.
Encourage others to answer you queries by suitably rewarding them
Thanks
Venugopal
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |