Create a validation for check double invoice

Hi,
I have read here on SDN for check double invoice on reference number. We want to create an warning message if same reference number is posted twice, not depending on invoice date. So if I, on 1st of October have posted an invoice with reference number 123 and then want to post with same reference number on 2nd of October I want to have an warning message. If I had understand right I need to make a validation for that. Is it true that I need to have a programmer to do that or how am I doing (one thread said that this was the solution, see; )?
I suppose that my prerequisite will look as follows:
BKPF-BLART = 'KR' OR BKPF-BLART = 'RE' (I want the check when entering both an invoice in FB60 and MIRO)
How will my "check step" look like when I want to check if this reference has been entered before? Please describe in technical name.
Is it possible to do a validation for getting a warning, or is it just possible with error message?
I have also tried to change in IMG, in Material management > Logistics Invoice Verification > Incoming invoice > Set check for Duplicate invoices. Here we have all fields selected (check co. code, check reference, check inv. date). I changed to just select check reference, but this doesn´t solved my problem.
Best regards Lisa

Hello Lisa,
Your first question,
Yes system does not check MIRO invoice while posting FB60 invoice. Because when you post invoice with using FB60 transaction, system check BSIP table for duplication. But when you post MIRO invoice system doesn't fill BSIP table.
So that your question answer is YES, you can register an invoice in MIRO with same reference without a warning.
Your second question,
BTE means Business Transaction Event. Those events are known as FI user-exit.
So that when you posting an invoice with using FB60, system triggered on BTE 00001110 as i said on my previous message.
I try to explain step by step how can you activate this BTE. But you need to ABAPer for giving warning message on this exit.
Call FIBF transaction -> Settings -> Products -> ...of a customer
Create a new line,
Product : ZXX
Text : BTE Products for FI Exit
Product active : tick checkbox.
Call SE37 for exit function and copy from FM SAMPLE_PROCESS_00001110 to ZFI_PROCESS_00001110. Then active your FM and go to FIBF transaction again.
FIBF -> Settings -> Process Modules -> ...of a customer
Define a new line.
Process : 00001120
Function Module : ZFI_PROCESS_00001110
Product : ZFI
And then you can some write ABAP code for validation and give warning message.
In this FM, If you don't want to check duplicate invoice for your cases you can set export parameter e_nostd = 'X'.
I hope it helps to you,
Regards,
Burak

Similar Messages

MM-Check Double Invoice functionality for Vendor Invoices

Dear All,
How Check Double Invoice functionality for Vendor Invoices can be implemented in SAP?
We have implemented Check double invoice with the standara sttings for it however if i give my referenece text differently it will aloow me to post double invoices and against vendor open items are shown for payment?
Is there any other efficient way to do it?
Thanks and Regards
Shrinivas

dear SAPian friend,
go through the below link and you will find the solution with the screenshots.
http://sapfunctional.com/MM/Duplicate/Invoices.htm
U can also do the setting using the SPRO t-code:-
path is
>>SPRO
>>SAP Reference IMG
>>Materials Management
>>Logistics Invoice Verification
>>Incoming Invoice
>>Set check for duplicate invoices

How to create a validation for the project coding mask

Hi,
Would just like to ask how to create a validation for the project coding mask wherein the WBS elements hierarchy will be checked against the template saved. For example,
project coding mask is XXXX-XXXXX-XX-X-X-X-00-X
mother WBS should be XXXX-XXXXX-X and lower level WBS would be XXXX-XXXXX-XX.
The validation should not allow a mother WBS to be XXXX-XXXXX-XX.
How can we go about this?

Hi Jacquiline Bersamin,
You can use validation with the combination of the level and the coding mask.
In the validation:
Pre requisite: WBS level = 1
Validation: Prps-posid = prps-posid :1-12:
Message : Error
If required you can give the parameters for your detail error message.
Please let me know if this does not work.
Thanks
Regards
Srinivasan Desingh

How to create a validation for a certain document number range?

Good Day!
May I just seek assistance on how to limit a certain document number range from normal posting via F-65?
The scenario is I would like to restrict, say for example Document Number range 07 from transaction FBV1. How do I create a validation for that? I was thinking what to put up in the Check field in the validation.
This is how I set up the pre-requsite for the validation rules:
Pre-requisite: Transaction Code = FBV1
Thanks!

Ok great.. Thanks a lot for the help.If I may just ask one more? =)
What if the scenario is say creating a validation for a certain GL account group?
Scenario: User would like to restrict the transaction FBV1 from posting to a GL account group (e.g. G007) ?
I checked the list of tables and fields in validations, but it seems that the GL account group is not part of the list.
Any help would be greatly appreciated.

DRM Validation for checking existence of nodes in a different Hierarchy as a property value

Hello Gurus,
I have two hierarchies named A & B respectively. I need to create a validation for nodes in hierarchy A which checks value of a property such that the node should have property value equal to any node name in Hierarchy B.
Means the values for that particular property for nodes in hierarchy A should exist as a node in hierarchy B.
It would be very grateful if some one can provide an idea to achieve this.

Hi,
Try this in a formula type validation-
NodeInHier(PropValue(Custom.PropName),B)
This would return false if the property value is not a node in Hierarchy B and True if it is.
So you will get a validation message every time the property is loaded with a value which is not node in Hierarchy B.
Thanks, Let me know
Denzz

Issue in creating Credit Note for road carrier invoice from SAP TM system

Dear All,
I am facing issue in creating Credit Note for road carrier invoice from SAP TM system.
The following steps I have performed:
1)
1)    1) Create Freight order with Amount 20,100
2)     2) Create Freight Settlement Doc and send it to ECC. Hence PO and SES will be created in ECC with Amount 20,100
3)     3) Invoice verification (MIRO) done w.r.t. FO in ECC with Amount 20,100 and following entries posted :
Carrier A/c - 20,100Cr
GR/IR A/c – 20,100 Dr
4)    4) Created Credit Note in SAP TM against freight order with Amount 1,010 and transfer it to SAP ECC.
5)    5) By this a new PO and SES was created with negative values (with amount 1,010) in SAP ECC
6)    6) In transaction MIRO, Credit Memo was created against the freight order.
7)    7) By this it is showing value 21,110 by adding the line items of Original Purchase Order and Credit Note Purchase Order as 20,100 and 1,010 respectively.
8)    8) By posting this following are the accounting entries which is not correct:
Carrier A/c – 21,110 Dr
GR/IR – 20,100 Cr
GR/IR – 1,010 Cr
9)    9) In report FBL1N which is showing the remaining liability of value 1,010(21,100 – 20,100) instead of 19,090 (20,100-1,010=19,090) for the carrier.
Please suggest how to resolve the issue and get the correct accounting for credit memo?
Regards,
Vibhu Gupta

Hello,
Like my reply in Linkedin group, I got the same issue and solved with BADI in TM side(REQREQ...).
Regards, Marcelo Lauria

How to create a validation for version in planning

Hello all,
i would like to create a validation for the field 'version'. I have defined 8 different versions, one of them just for planning in orders.
How can i create a sustitution in order to validate that always that they are going to plan in orders, only they are going to allocate the plan in the proper version?
Is there another different way to do this?
Thanks in advance.

Hi,
For planning transactions (except for planned settlement), the validation OKC7 (or substitution OKC9) won't work.
Regards,
Eli

Validation for duplicate AP invoice

We would like to prevent duplicate AP invoices from being posted through FB60.   We created an FI validation in OB28 in which the prerequisite = Tcode FB60, and the check is a user exit to check the values in vendor / company code / reference fields and if those 3 fields have the same values as in an existing document, to generate an error message preventing the duplicate document from being posted.
The above works well for creating new invoices.   However, when we have to make changes to an existing invoice (created through FB60), the system also calls on that validation and generates the error message, even though the only fields we can change on the invoice is payment terms, payment method, payment method supplement and text.
Other than modifying the user exit, does anybody know of a better way to do this validation or to prevent duplicate manual invoice from being created?
thank you.

This has already been answered before so extracted part of the reply
there are two duplicate checks in SAP:
1. the one for FI documents, this is relevant for all F... postings (but nor for MIRO!)
this can be turned off or on (in vendor master record) and 6 fields are checked:
Check Flag for Double Invoices or Credit Memos
Indicator which means that incoming invoices and credit memos are checked for double entries at the time of entry.
Use
Checking Logistics documents
Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
Checking FI documents
The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
Checking Logistics documents
In checking for duplicate invoices, the system compares the following characteristics by default:
Vendor
Currency
Company code
Gross amount of the invoice
Reference document number
Invoice document date
If all of these characteristics are the same, the system issues a message that you can customize.
When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
No message is issued if you enter a document that has previously been reversed.
Dependencies
The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
Reference document number
Invoice document date
Company code
This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
Example
The following document has already been entered and posted:
Reference document number: 333
Invoice date: 04/28/00
Gross invoice amount: 100.00
Currency: EUR
Vendor: Spencer
Company code: Munich
You have made the following settings in Customizing:
The field "Reference document number" and "Company code" are deselected, which means that these characteristics will not be checked.
Now you enter the following document:
Reference document number: 334
Invoice date: 04/28/00
Gross invoice amount: 100.00
Currency: EUR
Vendor: Spencer
Company code: Berlin
Result
Because you entered a reference document when you entered the invoice, the system checks for duplicate invoices.
The reference document number and the company code are different from the invoice entered earlier, but these characteristics are not checked due to the settings you have made in Customizing.
All other characteristics are the same. As a result, the system issues a message that a duplicate entry has been made.
If the "Reference document number" had been selected in Customizing, the system would have checked the document and discovered that it was different from the invoice entered earlier, so it would not have issued a message.
Checking FI documents
Depending on the entry in the field "Reference", one of the following checks is carried out:
1. If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
Company code
Vendor
Currency
Document date
Reference number
2. If no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
Company code
Vendor
Currency
Document date
Amount in document currency
2. the one for LIV.
this can be customized (as stated above) and is relevant for MIRO (and not for F... postings!).
Company, Reference and Invoice date
Set Check for Duplicate Invoices
In this step, you can configure for each company code if the system is to check for duplicate invoices when you enter invoices.
This check should prevent incoming invoices being accidentally entered and paid more than once.
You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice. The Accounting documents are checked first, followed by documents from Logistics Invoice Verification (only incorrect invoices or those entered for verification in the background).
When checking duplicate invoices, the system compares the following
attributes in the standard system:
Vendor
Currency Company code
Gross invoice amount Reference document number
1. Invoice date If the system finds an invoice that matches all attributes, the system
displays a customizable message.
If you are entering credit memos, subsequent debits, or subsequent
credits, the system does not check for duplicate invoices.
The exception is the Argentina country version, where the system checks
for duplicate invoices and credit memos.
If a previously processed document is later cancelled and then entered
again, no message is displayed.
Requirements
The system only checks for duplicate invoices in Materials Management
if you specify a reference document number when entering the invoice.
In Customizing (IMG) for Invoice Verification, you can specify that the
system check the following attributes

Check double invoice with GL account and Reference field

Dear SAP GURU's,
I am very new to SDN. I have one query.
I know we have the option of control double invoice against Vendor/Customer by using reference field. But here my client is asking that control has to be from GL account and reference field, becoz some times he will receive the shipping bills 3 or 4 times agianst one billing document ( i am booking Transporter Vendor invoice by using FB60) with same bill number but expense GL's will be different most of the times. Some times knowingly or unknowingly same GL Expenditure account will be repeated with the same shipping bill number. This was happend most of the times.
So can i know how can i get the GL account and Reference field checking and error message for the same.
Thanks & Regards,
Shobha.

Dear Shobha,
I feel that having a check on GL is not a good idea. If your client insists you can go for an exit or BTE.
We used BTE to have the same functionality of Logistics for FI documents also in our office.
Duplicate Invoice check process documentation is given below for your ready reference --
with Regards
Check Flag for Double Invoices or Credit Memos
Indicator which means that incoming invoices and credit memos are checked for double entries at the time of entry.
Use
Checking Logistics documents
Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
Checking FI documents
The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
Checking Logistics documents
In checking for duplicate invoices, the system compares the following characteristics by default:
Vendor
Currency
Company code
Gross amount of the invoice
Reference document number
Invoice document date
If all of these characteristics are the same, the system issues a message that you can customize.
When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
No message is issued if you enter a document that has previously been reversed.
Dependencies
The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
Reference document number
Invoice document date
Company code
This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
Example
The following document has already been entered and posted:
Reference document number: 333
Invoice date: 04/28/00
Gross invoice amount: 100.00
Currency: EUR
Vendor: Spencer
Company code: Munich
You have made the following settings in Customizing:
The field "Reference document number" and "Company code" are deselected, which means that these characteristics will not be checked.
Now you enter the following document:
Reference document number: 334
Invoice date: 04/28/00
Gross invoice amount: 100.00
Currency: EUR
Vendor: Spencer
Company code: Berlin
Result
Because you entered a reference document when you entered the invoice, the system checks for duplicate invoices.
The reference document number and the company code are different from the invoice entered earlier, but these characteristics are not checked due to the settings you have made in Customizing.
All other characteristics are the same. As a result, the system issues a message that a duplicate entry has been made.
If the "Reference document number" had been selected in Customizing, the system would have checked the document and discovered that it was different from the invoice entered earlier, so it would not have issued a message.
Checking FI documents
Depending on the entry in the field "Reference", one of the following checks is carried out:
1. If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
Company code
Vendor
Currency
Document date
Reference number
2. If no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
Company code
Vendor
Currency
Document date
Amount in document currency

Creating a Validation for WBS Element in the Asset Master Record

I would like to know how to create a validation in the AMR for the WBS Element field. I would like to have a particular Business Area when used be required to only use a WBS element that starts with, let's say, AL. Can someone shed some light on how I would set up my check in OACV?

Hello
You can validate or substitute data directly at the input stage. You make the settings for validation and substitution in the Implementation Guide (IMG) for Controlling, under Controlling General ® Account Assignment Logic ® Define Validation or Define Substitution
Substitution and validation are only intended for actual postings
For a complete description of validation and substitution, see the SAP Library under Accounting - FI Financial Accounting ® Special ledger ® Tools ® Validation and Substitution Rules
Coordinate with ABAPer and make settings.
Reg
*assign points if useful

XK01-check double invoice field should be checked by default.

Hi,
Is there any way in which I can make the defult value in the "Check Flag for Double Invoices" (Program SAPMF02K & Screen 215) which is in the Vendor creation transaction XK01 always ticked?
Thanks
Nirupam

Hello Nirupam,
If you use OBD3 tcode, you need to select that fieild as "Req. Entry", you will not get default value for that field as "Checked" but user has to check that field becuase you are making it mandate.
If you use the second option, Screen / transaction variant (take help from technical guy in case of find it difficult), you can put the default value as "checked"
Now, it's upto business in which way they want to work.
Hope this helps.
Regards
Arif Mansuri
Reward if answer is helpful.

Create a validation for SQL Query (updateable report)

Hello
I have a need for creating a validation on a SQL Query (updateable report)- type region
1)
When a row get populated i don't want same values to be populated in the second row.(as shown in first 2 rows)
Also, I don't want to have a value that falls in range in between 100 and 1000 for the period falls in the previous. (as shown in third row)
i.e
Type_id
Lower_Limit        Upper_Limit           Date_From       Date _To
1
100                      1000                   1/1/2013        12/31/2013
2
100                      1000                    1/1/2013        12/31/2013
3
101                       500                    2/1/2013        10/31/2013
appreciate any help
thanks
kp

This example could help:
http://apex.oracle.com/pls/otn/f?p=31517:214
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

LMS 4.2.4 - Creating daily report for checking mac-adress list (IP hone) existing on the network

Hi,
we would like to create a daily report for checking (by user-tracking function) mac-address list on the network.
I try to use “report designer” on “report” dashboard without any success. Could you help us to provide or create a method for applying a report job every day for checking our mac-address list
Thanks in advance.

you can do the following
1. -create a quick report {Reports > Inventory > User Tracking > Quick Report}
2.export the last report which I suggested and filter the MAC address you are interested in
3. you can create a Custom report {Reports > Report Designer > User Tracking > Custom Reports } as per your need.
Thanks-
Afroz
*** Ratings Encourages Contributors ****

XSD or RELAX-NG validation for check-in form

Hi,
I have a set of XML files that I want to check in to content server and also have validated against an
XSD schema (or RELAX-NG schema). If the validation of the XML file fails, the checkin should
fail. The XML files would need to be updated on a regular basis.
I am using 10gR3. I'm not so familiar with extending the content server to do
this, and would appreciate any general guidelines or pointers to relevant
documentation.
Thank you
Edited by: user4863684 on Nov 12, 2010 8:32 AM
Edited by: user4863684 on Nov 12, 2010 8:33 AM

XML converter (an add on to Inbound Refinery) could be used to display the contents with your XSLT choices but analyzing the file to prevent checkin would take data validation that would be custom. The CS does not care the file format or file type for checkin. Others have looked for analysis of file extension to stop checkin of certain extensions. This has been custom. I think there may be enhancement requests from customers for this kind of validation for the CS but it does not exist in the core yet.

Visio 2010 Validation for Checking the number of a specific type of shape.

I have written a rule for flowchart for checking the number of Start/End Shapes in a document.
The FilterExpression is as follows:
AGGCOUNT(FILTERSET(SHAPESONPAGE(), HASCATEGORY("Start/End"))) > 0
The TestExpression is as follows:
AGGCOUNT(FILTERSET(SHAPESONPAGE(),HASCATEGORY("Start/End"))) = 2
(Since totally there are 2 shapes: 1 Start and 1 End Shape)
However, it is not working. Can anybody tell me what is wrong in the expressions.

Well, it worked for me, so I want to check that you modified the Start/End master to have the User.msvShapeCategories row with the value "Start/End", as I did?
A Category is not a Master
David J Parker MVP (Visio) http://blog.bvisual.net

Create a validation for check double invoice

Similar Messages

Maybe you are looking for