Duplicate vendor check during supplier registration

Hi Gurus,
Does SAP SRM ROS check for duplicate vendor during supplier registration? if it is not done in standard, can it be enhanced to do so?
Thanks and regards,
Ranjan

Hi Ranjan,
Every supplier who registers will have a unique BP number in the ROS client. However checking for duplicacy by name is not supported in standard ROS.
One option is that when a strategic purchaser accepts these suppliers and creates a BP in SRM, he notices a duplicacy and informs the vendor. However this will fail if there is a huge volume of vendors registering everyday.
Possible workaround: When the new vendor fills in the registration form, he provides the name of organisation and this is stored in tables using BAPIBUS1006_CENTRAL_ORGAN. May be you can sit with an ABAP guy and find out in which table this entry sits. You can then have a Z table where you store all these organisation names whenever a new vendor registers and for checking duplicacy you could run a loop through this Ztable Column which stores the name and display a message on 'ROS_SELF_REG' BSP reg page whenever a duplicate entry is found.
PS : Entries like 'IBM' and 'IBM Ltd' will still be created as 2 different entities even though they mean the same.
Nikhil
Edited by: Nikhil RGupta on Jun 21, 2011 11:31 AM

Similar Messages

Duplicate Vendor check

Hi,
Want to configure e a warning message for Duplicate Vendor master creation.
I can see a message F2144 configred, but this is only applicable if we create Vendor from FK01.
In spro>Logistics general>Business partner>Vendor> message control for Vendor master ....can we configure a message here, which will be applicable if I create duplicate Vendor master from transaction XK01.
Regards,
Rajesh Satope.

For normal vendor you can maintain duplicate check in OBA5
Application Area F2
Message No.144 for Vendor and 145 for customer, making it as information.
Reference : [Duplicate vendor check??????|Duplicate vendor check??????]

Using Portal Surveys within iSupplier during supplier registration

I'm exploring using Portal Surveys within iSupplier during supplier registration. Can you confirm and explain this possibility (having suppliers take a survey during self-registration) and whether or not the surveys can be enabled by operating unit (having different surveys based upon operating unit assignment).
I’m unfamiliar with this functionality and any insight or clarification on your part will be greatly appreciated.

Hi All, got the solution for this.
While debugging the procedure "FND_REGISTRATION_UTILS_PKG.publish_event" we found that it is calling a business event. We followed the below steps to resolve the issue:
1)     For the business event “oracle.apps.fnd.umf.reg.user_approved” we need to disable existing seeded work flow subscription
2)     Keep the internal name of workflow as same, modify the standard workflow by adding new custom process to it.
3)     Create a new subscription under the business event to call custom process of work flow from it.
4)     Create custom package of “POS_URL_PKG” and call this from the above created custom work flow process
5)     Custom package “POS_URL_PKG” gets the Custom URL which needs to be send to user
Regards,
S.K.

Duplicate Invoice Check during Invoice Parking

Hi All,
We have activated duplicate invoice check for our company code. All the required pre-requisites have been activated w.r.t configuration and master records. In our case we had checked only Reference document number and company code for considering duplicate invoice check.
So during invoice parking the system is checking the gross invoice amount also for validation.
For example, we had parked an invoice document with gross invoice amount 100 USD, reference doc number 123, vendor code X, company code Y and currency USD. We are trying to create another invoice document with same parameters as created for first document except gross invoice amount (for this new document the gross invoice amount is 150 USD) In this case the system is not showing the message number M8-462 (Check if invoice already entered as logistics inv. doc. number & &). If the Gross invoice amount is same, then the system is showing the message.
But if we post the invoice and then try to create another invoice with same reference with different gross invoice amount, then system is showing message M8-108 (Check if invoice already entered under accounting doc. no. & &)
Please provide your inputs on why system is considering gross invoice amount for parked invoices.
Thanks

If it's User specific it's probably the message setting . . .
MM \ LIV \ Define Attributes of System Messages
Help text:
Define Attributes of System Messages
In this step, you can define the category of message received by individual users for certain messages in Invoice Verification. This allows you determine whether a user receives a message as an indication of:
Information
Warning
Error
Or whether no message should be issued at all
Regards,
Nick

Information message for duplicate vendor check( message 144)

Hello everyone, i am trying to configure information warning message in vendors. The configuration for this is SPRO-IMG-FA-AR/AP-vendor accounts-master data-preprations for creating vendor master data-change message control for vendor master data.
I need to configure
message: 144
message text: vendors with the same address:check
online: I information message
When i enter the new entry, i can see MsgNo 144 under the MsgNo but under "online" i need to use I: informational message but i dont see that option under there. I think i need to configure that message ( I: information message) under "online". Does why one know how to configure that? Any suggestions will be appreciated.
Regards

Hi there ,
By default it will show Information message only.
Why there is any need of changing anything?

Validation Check - Duplicate vendor Invoices

Hi,
We have a situation where the Duplicate Vendor Invoices have been entered by the users, bearing the same date and reference nos. as the original ones. When we checked we observed that, the system gives the warning message, but the same is ignored by the users. To prevent the same from happening again, we want to convert the warning message into the error message.
Could any one guide as to how can we set up the validation checks, such that the system would throw an error message. In the vendor masters, we have set up the check for Duplicate Invoices.
Thanks in advance.
Best Regards,

Hi,
If you already know the message number, then go to T.code:OBA5 or
T.code:SE91 (if its an custom message class) and change the message from waring to Error.
If you are not aware of Message, and try to post a duplicate invoice & when the warning message comes, double click on the same, it will give you the message number.
This will resolve your issue.
Please let me know the result of the same
Thanks
Kalyan

How do i check ensure that SAP checks for duplicate vendor invoice numbers?

Hi Experts -
How do I verify that SAP checks for duplicate vendor invoice numbers and blocks duplicate invoices from being paid?
Thanks!

Hi
Pls chek the settigs by following the path
IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoice.
Here you make the settings for creating a duplicate invoice check.
Moreever, in the vendor master, you need to tick the check box for duplicate invoice check.
I suggest you search the Forums before posting a query. There are lots of postings on this issue.
Thanks & regards
Sanil K Bhandari

Duplicate Invoice Check -Vendor

Hi everyone,
I found out that I posted an invoice(FB60) for the same vendor with same, amount, reference,invoice date,same company code.one invoice was posted on 3rd march and other was posted on 25th march,I checked in the vendor master record indicator" chk double inv" is checked.Why system didn't give any error or warning message.Please guide.
Regards
Shaun

Hi,
Good Day,
Please follow the below steps ( taken from another post and its working fine for me)
The following fields must be identical for Duplicate invoice check
Company code (BUKRS)
Vendor number (LIFNR)
Currency (WAERS)
Reference number (XBLNR)
Amount in document currency (WRBTR)
Document date (BLDAT)
If the document is having any one of the above filed different then the
system does not consider it as a duplicate invoice.
and also It will check duplicate invoice check in vendor master data
and in posting key is there check box selected for sales related
The setting you making in OMRDC i.e Materials management->Logistics
Invoice Verification->Incoming Invoice ->Set Check for Duplicate
Invoices is only valid for MM and not FI invoices posted via FB60/FB65.
You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
in the relevant vendor master record (transaction FK03).
Please also check, that message F5 117 has been set correctly in the
IMG using this path:
Financial Accounting -> Financial Accounting Global Settings ->
Document -> Default Values for Document Processing -> Change Message
Control for Document Control For Document Processing
Finally & mainly, go to the relevant posting key is defined as sales
related in transaction OB41. You have to flag this field if the
duplicate invoice check should work.
Best Regards,
KSK

Duplicate vendor Invoice check in FB60

Hi Experts,
I want to put the duplicate invoice check while posting the vendor invoice through FB60. I want the system to check the duplicate invoices in combination of the Vendor code and vendor invoice number ( we put the vendor invoice no. in the reference field of FB60 ). How to make this possible. I do not want to make the FI validation for the same. Can you please suggest how to go ahead with this.
Thanks,
BABA

Hi Shailesh,
phuu, ok, let's start from the beginning then.
Some theory first:
you need the validation because the standard check takes the doc.date ito consideration and this is not wanted. And you need the exit from the validation (! not a separate exit! not the original), locate the IF-statements where there is an ELSE option ending with function CUSTOMIZED_MESSAGE. It is up to you what to do here. In the original functoin module, the messages are issued here immediately. It can be an error or a warning, depending on the setting in table T100C. If my understanding is correct, you always want to see an error message, bt this should be done in the validation, not in the function module. So you should skip the customized_message function call and just issue the messages here as info message regardless of T100C settings. In this case, remove the function call customized_message (as many times as it occurs) and issue the message included directly as an information. Right after the message was issued, set E_RC to 4, infoming the validation that the check has failed. (Note that the customized_message function is only called if the check has failed, so no worry that you always get the message.
4. Define the exit for the validation
=========================
Go to your form pool Z_RGGBR000 (defined in V_T80D) and locate the statement APPEND EXITS. It should appear few times, locate the last occurence.
Right after that, enter the following:
exits-name = 'U901' .
exits-param = c_exit_param_none.
exits-title = text-901.
append exits.
This will define a new exit namd U901 for the validation routines. If in V_T80D, you already had a Z (or Y) report, check if the string U901 is used in that code already (check for the main program). If this is the case, instead of U901, use another name, it should begin with U followed by 3 digits. Also, you make sure the text symbol text-901 (or the 3 digits you are using) is existing, doubleclick it and enter a description like "Duplicate invoice check validation" or similar.
Well, the exit is published, we have to write the main code now.
go to the very end of your Z_RGGBR000 report and add a new form U901 like follows:
Duplicate invoice check validation
FORM U901 USING B_RESULT.
Vendor master flag
data: l_reprf like lfb1-reprf.
Result of function module
data: l_rc like sy-subrc.
Check vendor master first
select single reprf into l_reprf from lfb1 where bukrs = bkpf-bukrs and lifnr = bseg-lifnr.
Do not continue if flag is not set.
if L_REPRF is initial.
b_result = b_true.
endif.
check not L_reprf is initial.
Call modified function module
CALL FUNCTION 'Z.....your function'
    EXPORTING
      i_bukrs = bkpf-bukrs
      i_lifnr = bseg-lifnr
      i_waers = bkpf-waers
      i_bldat = bkpf-bldat
      i_xblnr = bkpf-xblnr
      i_wrbtr = bseg-wrbtr
      i_koart = bseg-koart
      i_reprf = L_reprf
      i_shkzg = bseg-shkzg
      i_xumsw = bseg-xumsw
      i_bstat = bkpf-bstat
      i_belnr = bseg-belnr
      i_gjahr = bkpf-gjahr
      i_blart = bkpf-blart
EXPORTING
      e_rc = L_RC.
Decide if validation message must be issued or not
if L_RC = 4.
b_result = b_false.
else.
b_result = b_true.
endif.
endform.
After this, activate the source code. Make sure you have defined the text-symbol 901 before!
5. Define the validation
=================
Go to OB28 now, and enter your company code(s) and the call-up point 002 (line item). If there is a validation defined already, you have to add a new step only, if not, you have to create the validation anew.
I assume there is no validation defined yet, so enter a name for the validation like FI_2 or similar. It should NOT be named DUPLIC or similar, i.e., you should not include the purpose in the validation name. This is because the validation is defined on company code / call-up point level and it may contain many steps for different purposes later. A generic name FI-2 or probably your company code followed by 2 (2 is the call-up point) is the best choice.
Before presing enter go to the last column Validatin active and enter 1 here.
Then press enter and you will get an error that the validation does not exist. No problem, go to menu path Environment --> Validation and let's create a new validation.
First, enter a description for your new validation in the right hand panel. Again, this should be a generic description, tell nothing about duplicate invoice checks here.
You may be asked here to assign a message class to the boolean class 009. You should enter here a Z message class where the validation message should be issued from. If no appropriate message class exits, open a new session go to SE91, enter a new message class Z... press create, enter a description. Then go to the Messages tab there, and create a new message with number 001 (NOT 000) and enter the message text there. E.g. Duplicate entry not allowed.
Coming back to the validation, if the message class was already assigned (this is the case if there was a validation defined earlier), you can create a new step. In case of a new validation, it will become the first step. But if there was already a validation in OB28 for your company code and call-up point 2, then it will be the last step. In the left hand panel, make sure the new (or existing) validation is selected and press the Create Step button (Ctrl-Shift-F5).
In the right hand panel, enter a description for your step. This is the point where you can enter Double invoice check or similar.
We have three parts here, a Prerequisite and a Check part, finally a message.
In the left hand panel, select the Prerequiste. This will activate that screen block in the right side. We have to make sure that our validation is called only for the relevant vendor line items, so press Ctrl-F3 to hange to expert mode ) and enter the following in the Prerequiste window in the right hand panel:
BSEG-LIFNR <> '' AND BSEG-XUMSW = 'X' AND BSEG-KOART = 'K' AND
BKPF-BSTAT = ''
Beware '' is a ' followed by another ' and not a single " !!
Then switch back to normal mode using Ctrl-F1 and check the small lamp below that should be green now. Also, you can see the field descriptions now. If the lamp is red, press Ctrl-F3 again, delete all and copy the above again. Do not bother with line breaks. Switch to Ctrl-F1 again until the lamp is green. OK, what we have told here was please call the validation only if we have a vendor number and if this is a sales relevant item (invoice or credit memo, but not a payment or similar, this is the standard logic as well), and the account type is vendor (K) and this is a normal document.
WHen you are done here and the lamp is green, then go to the left side again and select the Check part. Now you should be able to edit the Check screen lock in the right hand side again. Switch to expert mode and enter simply U901
This is the name of the form in your Z_RGGBR000 report. NO brackets, no spaces, only U901 here. Switch back to Ctrl-F1 and instead of U901, you should see the text of your form (text symbol 901 in report Z_RGGBR000).
Finally, click the Message part in the left side to be able to maintain the message in the right side. If you issued an error from the function module already, you can give here an information, or you can give it as an error if you like. The message number is one of the messages from your Z message class, you have to define the text in SE91 (see above).
When done, save the validation and you can test it immediately.
Here a brief summary what is happening:
OB28 setting defines that in your company code a validation like FI-2 or similar is active on line item level. Whenever a line item is abut to be created, the validation will be called.
However, the prerequisite of the validation is quite strict: only a limited number or vendor items will allow to continue, other line items (G/L, customer, not sales relevant vndor, etc.) will just skip the whole validation.
If the prerequsite was met, the Check part is carried out. Here we have the exit U901.
In the exit, first we check if the vendor is flagged for double invoie checks. If not, we quit and processing can be continued. B_TRUE means it is OK. If the vendor is flagged, we call the new Z function which is almost the same as the original one.
The Z function will check table BSIP, but it will skip the document date comparison. If the current invoice seems to be entered earlier (regardless of the doc.date), instead of the standard customized message (which can be E or W for instance), the very same standard message will be issued as an information. So the user will be informed about the previous document number but the processing won't be stopped. In addition, a return code will be set to 4, meaning check has failed.
Jumping back to the exit, if the return code is 4, we have to tell the validatin that the check has failed (B_RESULT = B_FALSE), otehrwise we can tell the validation that the check was OK (B_RESULT = B_TRUE).
Now we are back in the validation, and, depending on B_RESULT, we just continue processing (B_TRUE), or issue an error message from a Z message class (B_FALSE). As the main standard message was isued already from the Z function, the user should know at this stage what the matter is. Your Z message can be a bit generic one, no need to include the vendor number or the previously issued invoice, etc.
Hope that helps, points welcome
Csaba

Vendor duplicate invoice check ???

Dear Expert.
Since in for FI documents will check double invoice when we post invoice with the same
- Company code
- Vendor
- Currency
- Document date
- Reference number
But our client would like to see or check double invoice if it is raised by different
VENDOR
For example, if we post invoice in FI with
- company code: 1000, vendor code: A, Currency USD, Document date: 01.04.2009 and invoice no. 1234
and we also post invoice in FI with
- company code: 1000, vendor code: B, Currency USD, Document date: 02.04.2009 and invoice no. 1234
So is there any Standard report or standard Configuration check available ?? Or How I can achive this ?

Hi Uday,
Please check the steps again:
SPRO --> Materials Mangemnt ...> Purchasing ...> Partner Determination
A. Define Partner role
B.Define Permissible Partner Roles per Account Group( In this step, you can specify for each account group of the vendor which roles the vendor may assume.)
C.Partner Settings in Vendor Master Record
In this section, you define partner determination schemas and assign them to account groups.
D.Define Partner Schemas
In this step, you define partner determination schemas.
E. Assign Partner Schemas to Account Groups
F. You need to include the Partner Function PI in the Partner Schema assigned to your PO document type.
MM-Purchasing -partner Determination - partner settings in purchasing documents
Apart from the above setting if you have set duplicate invoice check in a particular Vendor Master record and there is an entry in the Reference field when you enter an invoice for this vendor, the system always checks if there is an invoice containing same data as which just entered.
The following check criteria can be used
- Co, Code.
- Vendor
- Currency
- Reference
- Invoice Date
- Amount
You must specify in customizing whether the Co. Code, reference and Invoice date are included in the check.
If it finds an invoice that matches all these attributes (Message # M8 108) is issued as error or information.
All these are SAP standard settings; and they should work. You can always look to enhance the check logic with the help of a BADI or FM Exit.
Hope this is useful.
Thanks,
Reetesh

Check duplicate asset number during MIGO

Hi MM/Abap Gurus ,
What user exit can be used to check duplicate asset number during GR. E.g: I have a PO with same asset number for item line 1 and 2. What user exit can be used to set warning msg if duplicate asset number exits during MIGO. Please advise if there any user exit can be used for my requirement?
Thanks
Mitra

Hi Puspha,
Actually, the scenarios as below:
1. PO created with 1 line item with Acc Assign Cat = A and multiple account assignment. Therefore, under the account assignment tab there are duplicate asset number inputted.
2. Hence, when do GR, the system should prompt warning message " Duplicate asset number exists".
Above are the requirement. I need any user exit that I can use in MIGO, where there is checking on duplicate asset number or during the sving of MIGO, I could inforce a logic on the checking.
Your help appreciated.
Thanks

Disable duplicate email check for external candidate registration

Hi,
I am working with eRecruitment 6.0 and I would like to disable the duplicate email check on the external candidate registration page. Has anyone done this before? I have chased the code down to where it check for correct email syntax but I can't find where it does the duplicate email check. I debugged to where I was starting to see BP type function modules and bapis but I still can't find the check. I just want to turn it off for testing then turn it back on and test more. I have searched OSS and SDN and still no answers. I thought about using an enhancement point to 'ignore' the message but by the point the system has already decided not to create the user so ignoring the message is a mute point.
Anyone been down this road and can point me in the right direction that would be greatly appreciated.
Thanks!

Hola,
Ok a small 'enhancement' to CL_HRRCF_ADDRESS_SERVICE->IS_EMAIL_UNIQUE has done the trick. Not exactly a best practice but will get me through this testing. NO this will not be going to production. This is strictly a test.
Cheers!

Supplier Registration - Is it possible to push new created vendor in SRM?

Hi SRM / SUS experts,
We are defining Supplier Registration processes and had a question with regards to it. After getting supplier information through forms and questionnaire, let's say I approved it and then converted it to Vendor in SRM. Then, is it possible to push newly created vendor back to ECC? I see (database) icon to push vendors to ECC in monitor Business partners transaction, but it is disabled. I am thinking since I have not set up XI integration with ECC, the icon is disabled.
Will you please share your experience with this functionality?
If it can be pushed, then which account group will it take when it is created inECC and which views are created (General data views?)? Is it created under same number as SRM business partner?
Your inpur is highly appreciated.
Thanks,
Chandra

please refer to the following SAP help for more details on the Montior Business Partners --> and what can be done there
http://help.sap.com/saphelp_srm50/helpdata/en/e6/4b4b3c99c53c33e10000000a11405a/frameset.htm
--> you have to open the tree --> Business Partner Monitor..
and for the option --> to be enabled --> to transfer to backend -> it is looking for two flags
1) Xi should be active in your system
and please refer to the following code --> which decides wether the backend transfer should be enabled (or) disbaled...
technically i know where it happens
transaction se38 --> enter --> LBBP_SUPP_MONIF05..
find the code which starts with -->
Enable Icon For XI backend Transfer

Supplier Registration in ESourcing ( Vendor integration with ECC or MDM )

Hi All,
SAP ESourcing has the functionality of Supplier Registration. As per the functionality, Supplier will provide all the required information in the registration form. The Supplier form will go for approval to the Buyer / Purchaser. Once approved, the supplier will considered for RFx event. My questions are :
1 :Is there OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with ECC so that system will automatically create new vendor in ECC.
2 : Is there OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with MDM (Master Data Management system ) .
Please through some pointer on this ?
Regards,
Kalandi

Hi Kalandi
For your first question, if you deploy standard integration package provided by SAP for e sourcing-ECC integration, you can replicate approved e sourcing vendor to ECC using standard script (I think script name is "Publish to ECC" ).
In case you prefer a custom option,you can write a customized script to get a flat file (.CSV) download of e sourcing vendor whcih can be used to update ECC
As far as OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with MDM (Master Data Management system ) is concerned, there is no standard solution provided by SAP but again since it is possible to get a CSV export of vendor field, it can be used to update MDM as well
Hope this helps!
Regards
Mudit Saini
Edited by: Mudit_UCB on Jun 28, 2011 1:20 PM

Supplier Registration without SUS or XI?

Can I do Supplier (Vendor) Registration without SUS or XI? If not, what are my limitations?
I am using SRM server 5.5, and am not using CCM as the supplier directory. I am not using questionnaires. ROS_SELF_REG works. However, I cant notify vendors via email of acceptance. Because I dont have SUS, I cant use SRMSUS_SELFREG and SRMSUS_SELFEDIT, correct? To do User Registration, can I use ROS_SELF_EDIT?
How is workflow WS10000209 (Approving External User Master Record) used?
I appreciate any feedback.

Hi Scott
It's difficult to give a reply hre, but let me give it a try...For more details, try the links given above by other friends.
You do not need SUS for Self-registration.
COnfig
1)Create another client for ROS.
2)Create RFC destination for EBP system in new client. Similarly, maintain RFC dest for ROS client in EBP system.
3)Maintain backend systems for ROS system in EBP and EBP system in ROS.
4)Configure some product categories (need not replicate from ERP) to be used during registration.
5)Configure the IMG settings for Supplier Self-registration (they are easy..just go through them once.
6)Configure SCOT settings (check notes 455140) for outbound & inbound mails.
7)Maintain org plan for purchasing org (ppoma_bbp)& vendor group(ppomv_bbp). No need for elaborate org plan like in EBP...just simple org plan.
8) Maintain table BBP_marketp_info (Txn:SM30)
9) Activate ROS_SELF_REG, ROS_prescreen etc ROS services in SICF
10) Maintain client and logon info in ROS_SELF_REG service (SICF)
11) In EBP client, maintain SAP client parameter for role SAP_EC_BBP_ST_PURCHASER for BSP link preselect suppliers (right click and change node details).
12) Maintain catalog call structure settings in EBP client IMG for the ROS supplier directory. The URL shd be taken from ros_prescreen attributes in ROS client.
Process:
1) With the service ROS_SELF_REG, a partner can register. System creates a BP (prospect) in the ROS client.
2) An email is sent to the given email id
3) Fill the attachment and click 'send survey' button. An email is sent to the system and system copies the survey response to the registered business partner
4) From EBP client, click on preselect suppliers. System launches the ROS client registrations listing screen.
5) Check the suppliers registered, check the data and accept/reject the supplier registration
6) Accepted suppliers data can be pulled into EBP through 'Maintain Business Partners' transaction and create supplier (bidder/vendor) in EBP client.
Hope it helps
Best regards
Ramki

Duplicate vendor check during supplier registration

Similar Messages

Maybe you are looking for