Duplicate Vendor creation

Hi ,
We are Creating Vendors through LSMW using Standard/Direct input Method.but a problem is that some vendors are created twice for a single previous account number(ALTKN) FROM database for some records.
Can anyone Tell me the reason why this happened and what needs to be done to rectify it?
also,any pointers to avoid it from next time will be highly appreciated.How can we avoid it?
Regards,
Rahul

Hi Jurgen,
I agree with you on this front and i am aware of this fact that ALTKN is there in LFB1.
The point is that for one ALTKN there are two SAP vendors Created for Same company code.
But,Second one is not needed.
What i have done right now is that i have marked the duplicate SAP vendors for Deletion so that it is not Used for Further procurement.
Is there a better way?
Edited by: Rahul Kumar Sinha on Sep 28, 2010 7:55 AM

Similar Messages

Duplicate vendor creation blocking in XK01 Transaction

Hi all,
I want to block the duplicate vendor creation in the vendor creation transaction
XK01.If any solution kindly reply to this message.
Jyoti

hI
So u can use the exit EXIT_SAPMF02D_001, here insert the code you need to check the duplicate vendor.
Perhaps the problem you can have is this exit is triggered at the end only.
U can try to use the BTE 1360 (it's to check the account group), but I believe here those fields are not filled yet.
Max

Duplicate Vendor Master

Hi Experts,
I am purposing vendor master to be created centrally to the client. How can I make it sure the same vendor is not created duplicate. What are the primary fields which i maintain so that system pops up a message for duplicate vendor entering. I checked with VAT number, Tax number nothing works. even the same name you can enter with all details same. What is the mechanism to prevent the creation of duplicate vendor other than the Zprogram or any exit.
Thanks in Advance,
Lekhram

hi lekhram
there is no need for a z program for duplicate vendor creation check.
add these 2 message control for vendor master data
goto financial accounting - accounts receivable and accounts payable - vendor accounts-master data - preparation for creating vendor master data - change message control for vendor master data
add message no 144 i i for both online and batch
add message no 272 i i for both online and batch
kind regards
Arman
SAP FICO

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??????]

Duplicate Invoice Creation MIRO

Hi All,
Our client has an special requirement. Currently we have an issue with duplicate invoice creation with MIRO transaction. The 'Check doub inv' check box in the vendor master data is already checked. For MM, there are three configurable check boxes i.e. T-Code OMRDC (Co.Cd, Ref. No. and Check Inv. Date.). Per our system configuration, we have the first two boxes checked and the 'Check Inv. Date' unchecked. The Ref. No. field is used to capture the invoice number. This way, if a vendor invoice has already been entered, when trying to enter another vendor invoice with same invoice number, amount, currency, company code and vendor number, irrespective of the date, the system displays a message as "Check if the invoice has already been entered...". As per our requirement, the client basically wants to distinguish between the two invoices purely based on Invoice Number (Reference Number-XBLNR). That is if an invoice has already been entered with a 'Reference Number = 123' for example, the user should not be able to post another invoice with same 'Reference Number = 123', for same vendor, same company code, irrespective of the invoice date and invoice amount. I really appreciate if someone could help me ASAP.
Thank you,
Jitesh

Dear
Please set the following in MM Logistics Invoice Config so that when MIRO/MIR7 is done twice then qty of MIGO exceeds then you get an error message.
T.Code : OMRM
Material Management>Logistics Invoice Verification>Define Attribute of System Messages
In the above node keep message number 504 Quantity invoiced greater than goods receipt quantity and keep online and batch as error and standard as W.
Hope this solves your problem.
Regards

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

Error in Vendor Creation

Hi,
In Vendor creation , while selecting the Country as United States ( US) in Vendor address the following error message is displayed
"Communication error with the external tax system (VERTEX_MS0018)
Message no. TAX_TXJCD864 "
How to solve this issue?????
Regards,

Hi,
Check the following entries.
OBCO : Check the schema TAXUSX (VERTEX Standard Jurisdiction Code)
OBCP : Select the costing sheet TAXUSX, check the tax jurisdiction codes
IMG>Financial accounting new > Financial accounting Global settings > Tax on sales/puchases >basic settings > External tax calculation.
Take FI consultant help make necessary settings.
Regards,
Chandra

Workflow for Vendor Creation through a portal.

Hi All Workflow Experts,
I have a scenario here.In my project vendor is created through a portal.On submit button from portal the workflow is to be triggered.I have to design the workflow process.So can you please guide me through what all should i consider while i design this workflow?
This is my first workflow assignment so if you explain in detail it will be a great help.
I will just pen down what all scenarios i can think of:
1.Start workflow after vendor creation or modification.
2.Check whether approver are maintained in Org structure through standard FMu2019s.
3.Check If approvers are maintained ?
4.If yes,approve or reject the vendor.
5.If no,get the agents from the custom table who can take an action on this.
This is what i can think of.
Please guide me.
Thanks in Advance,
Saket.

The corresponding BO related with the vendor creation or changing is LFA1 but this Business object doeanot have any events that are related to Create and Change , so try to create a ZLFA1 and add you own events or make use of delegation concept where you will create a delegation for LFA1.
For your first isssue
Start workflow after vendor creation or modification
EXIT_SAPMF02K_001 Vendors: User Exit for Checks prior to Saving is the user exit where in you can call the workflow when ever you change or create , because this user exit will trigger when ever you try to save the vendor. so i think you can make use of this user exit
For your second Issue
Check whether approver are maintained in Org structure through standard FMu2019s.
Make use of SWI_GET_USERS_OF_ORG_UNIT this fucntion mdoule to get the user of the ORG unit
or you can create a Rule(for determining the agents dynamically) to find the approvers.

How to restrict Duplicate Customer Creation in SAP

Dear all,
How can we restrict duplicate customer creation in SAP SD.
We are into retail sector, across the store customers are being created by different employees.
in this way for many customers more than one business partner records are being created.
we are looking for a sytem wise functionality to restrict the customer master creation (for Sold to party only) if name1, telephone number and street field values are same, then system has to stop customer creation by giving an error message.
Is there any standard functionality to address these requirement. If so how could we configure it.
Any of you can help us to solve the issue. your solutions and help will be highly appreciated.
thank you.
Raghu ram.
Edited by: Raghu Ram on May 26, 2008 5:34 PM

Hi,
2 solutions :
- Procedure manually (no SAP) ;
- Use extension SAP (SMOD : SAPMF02D) to check with differents data before recording.
No solution in standard.
Regards,
Lionel

Detect potential duplicate vendor master records

Hi all,
Our external auditor has the following comment:
'Match codes and message control can be used to help identify duplicate vendor records. Fields such as Name, Address and Country can be set as searchable fields in order to detect potential duplicate vendor records. The message control (with identifier 144) in SAP can give a message prompt when duplicate vendors are identified.
We noted that your system had not been configured to display a warning message if the name or address, etc of a new record is identical to an existing vendor record.'
Any idea to implement this?
I searched for message 144 and found that there is a similar message in message class F2: 'Vendors found with same address; check', but I cannot find where to trigger this error message.
Please help.
Best Regards,
Chris.

Goto SPRO-Financial accounting-Accounts Receivable and Accounts Payable
-vendro account-master data- Preparations for Creating Vendor Master Data
- Change Message Control for Vendor Master Data
here you can maekk the messge 144 to Error

Vendor Creation ,Partner role OA not allowed for Vendor of a/c group ZLOV

Dear Freinds,
I am facing problem of Vendor creation , i am getting message PARTNER ROLE OA NOT ALLOWED FOR VENDOR OF ACCOUNT GROUP ZLOV.
While creation of Vendor in Partner function i could not enter partner number, system is not accepting any data, message is getting as above.due to which i could not create any vendor.
Presently I am in process/ setting of ERS functionality in MM,
now all my Vendor creation is stuck up ,
please help me how to solve the problem
Regards
Dilip

Hi Dilip,
Check first have you Define Permissible Partner Roles per Account Group..
Check the path:
SPRO-Materials Management-Purchasing-Partner Determination-Define Permissible Partner Roles per Account Group
Here check whether OA is assigned with ZLOV or not...If no then click on new entries and enter partner function as OA and Vendor account group ZLOV...Save nd come out...
Now proceed...Hope it helps..
Utsav

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 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

Function module for offline vendor creation.

Hi Xperts,
I have searched all threads but i didn't find it, plz help me its urgent,
Is there a Function Module or BAPI for vendor creation. The BAPI_VENDOR_CREATE works online. I am looking out for an offline. This is for avoiding the use of BDC that we are currently using.
thanx in advance
Regards,
Naresh.

Hey whats up xperts............

Need Sample Code for Vendor creation using JAVA API

Hi,
I have a scenario like Vendor creation using Java API.
1.I have Vendors (Main) Table.
2.I have look up tables like Account Group.
3.Also Qualifier table(Phone numbers) too.
Could you please give me the sample code which helps me to create Vendor records using Java API?
I need Code samples which should cover all of the above scenario.
Marks will be given for the relevent answers.
Best Regards
PK Devaraj

Hi Devraj,
I hope the below code might solve all your problem:-
//Adding Qualified field
//Creating empty record in Qualifed table
//Adding No Qualifiers
Record qualified_record = RecordFactory.createEmptyRecord(new TableId(<TableId>));
try {
qualified_record.setFieldValue(new FieldId(<fieldId of NoQualifier), new StringValue(<StringValue>));//Adding No Qualifier
catch (IllegalArgumentException e2) {
// TODO Auto-generated catch block
e2.printStackTrace();
catch (MdmValueTypeException e2) {
// TODO Auto-generated catch block
e2.printStackTrace();
//Creating Record in Qualified table
CreateRecordCommand create_command = new CreateRecordCommand(connections);
create_command.setSession(sessionId);
create_command.setRecord(qualified_record);
try
create_command.execute();
catch(Exception e)
System.out.println(e.toString());
RecordId record_id = create_command.getRecord().getId();
//Adding the new record to Qualifed Lookup value and setting the Yes Qualifiers
QualifiedLookupValue lookup_value = new QualifiedLookupValue();
int link = lookup_value.createQualifiedLink(new QualifiedLinkValue(record_id));
//Adding Yes Qualifiers
lookup_value.setQualifierFieldValue(0 , new FieldId(<FieldID of Yes Qualifier>) , new StringValue(<StringValue>));
//Now adding LookUP values
//Fetch the RecordID of the value selected by user using the following function
public RecordId getRecordID(ConnectionPool connections , String sessionID , String value , String Fieldid , String tableid)
ResultDefinition rsd = new ResultDefinition(new TableId(tableid));
rsd.addSelectField(new FieldId(Fieldid));
StringValue [] val = new StringValue[1];
val[0] = new StringValue(value);
RetrieveRecordsByValueCommand val_command = new RetrieveRecordsByValueCommand(connections);
val_command.setSession(sessionID);
val_command.setResultDefinition(rsd);
val_command.setFieldId(new FieldId(Fieldid));
val_command.setFieldValues(val);
try
 val_command.execute();
catch(Exception e)
RecordResultSet result_set = val_command.getRecords();
RecordId id = null;
if(result_set.getCount()>0)
 for(int i = 0 ; i < result_set.getCount() ; i++)
 id = result_set.getRecord(i).getId();
return id;
//Finally creating the record in Main table
com.sap.mdm.data.Record empty_record = RecordFactory.createEmptyRecord(new TableId("T1"));
try {
 empty_record.setFieldValue(new FieldId(<FieldId of text field in Main table>),new StringValue(<StringValue>));
 empty_record.setFieldValue(new FieldId(<FieldId of lookup field in Main table>), new LookupValue(<RecordID of the value retrieved using the above getRecordID function>));
empty_record.setFieldValue(new FieldId(<FieldId of Qualified field in Main table>), new QualifiedLookupValue(<lookup_value>));//QualifiedLookUp value Retrieved above
} catch (IllegalArgumentException e1) {
// TODO Auto-generated catch block
 e1.printStackTrace();
} catch (MdmValueTypeException e1) {
 // TODO Auto-generated catch block
 e1.printStackTrace();
//Actually creating the record in Main table
CreateRecordCommand create_main_command = new CreateRecordCommand(connections);
create_main_command.setSession(sessionId);
create_main_command.setRecord(empty_record);
try
 create_main_command.execute();
catch(Exception e)
 System.out.println(e.toString());
Thanks
Namrata

Duplicate Vendor creation

Similar Messages

Maybe you are looking for