on 12-05-2007 9:22 PM
Hi
I am trying to set up a custom error message for duplicate invoice based on Vendor number (LIFNR) and Reference number (XBLNR) alone. The system presently considers a bigger set of fields to check for duplicate invoices which are
Company code
Vendor number
Currency
Reference number
Amount in Document currency and
Document date
I need to override this setting and have duplicate invoice check based on vendor and reference no. combination.
I have seen some threads which talk about BTEs where an FI interface - SAMPLE_PROCESS_00001110 can be customized by copying the sample function module and make customizations in the BTE.
Can somebody throw more light on how to approach this.
Any kind of approach solution would be appreciated
Thanks
Nag
Was able to get into FIBF and create a product and attach custom function (copy of sample function found in BERP) of the BTE against the product... Problem resolved.
thanks for your inputs kylie...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nag
I have configured a validation step to check duplicate documents in the past. Very quick and easy to use.
Kylie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kylie
Thanks for the update. I have already tried using validations through GGB0 and activating the same in OB28. I need the validation to be triggered at Complete Document level in GGB0. Unfortunately the background code corresponding to FV60/65 is only hitting the header portion where the line item details (BSEG) are not populated.
The vendor number is available at the line item level (BSEG) where as the reference number is available at the header level (BKPF). In order to access both these segements simultaneously, i need the program to trigger at the entire document level which is not happening.
Any inputs?
Thanks
Nag
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.