Delete Vendor Master Data in a Purchasing Organization

Hello Experts
I want to delete a Vendor Master Record that I have created, but not mark for deletion, I want to delete from the system.
I saw the transaction OBR2 to delete master redords, but I found that it is only possible to delete vendor for a Company Code. So how can I also delete the view of these vendors for the purchasing organzation?
Thank you in advance,
Best regards

Hi,
You can set the deletion at t.code via XK06 used to set the Flag for deletion .
Company code data,
Purchasing organisation data,
General data,
All area
Here,Check-box used to flagged the Vendor master to set the flag for deletion.
By using transaction OBR2 can set the deletion flag for the vendor master data not at purchasing and company code level.
Regards,
thiru

Similar Messages

Delete Vendor Master Data xk01

I have created Vendor Master in XK01 including purchase organization.
I want to delete it permanently. I have not made any POS and data.

Go to Tcode : SARA, enter the Object FI_ACCPAYB
Then :
1 Maintain write variant, it depends, if the vendor data only create for Purchasing Level only,than you can choose MM data.
When you archive MM data for vendor master records, the system automatically checks whether the following conditions have been met:
· The deletion flag is set.
· Dependent data of the following types no longer exists in the system:
Purchasing documents
Purchasing info records
Vendor partner roles
2. Maintain Deletion variant--> start deletion process --> this step will completely remove data from table.
If then some dependent data of above mention still exist,then you need also to close /archive the dependent data also.
Read below link also
http://help.sap.com/saphelp_erp2005/helpdata/en/8d/3e4c11462a11d189000000e8323d3a/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/ba/4b68b8327911d2a25c0000e8a5f24f/frameset.htm

Extract the new , changed , deleted vendor master data -urgent pls

Hi all,
I have require ment like i need to extract all new, changed and deleted data from SAP TO MAXIMO
i need to send to a windows environment which both systems share,
i am using LFA1 ,CDHDR , CDPOS Tables , i will get the reuired information , can i use gui_download
to download to windows environment which both system are mapped to a common shared folder.
i will extract the infrmation and sent to a shared folder.
this a backround job schedule daily once.and also i have to sent the file contents to spool also.
please suggent some code existing or how to do the logic behind.
shall i use open data set
read data set
close data set.
please suggest ways of doing............urgent.
regards
kodamanchili

With regards to the writing out of the data that, you are correct that you should use the Data Set commands if you are attempting to write a file out to the application server. If you are using any sort of EAI tool then there maybe are other ways specific to the tool for sending data, such as some of the tools utilize RFCs to send the data.
For the actual identifying of the changed records, it is best not to write delta interfaces directly against the change document tables (CDHDR and CDPOS). Instead you should be ustilizing change pointers. Change pointers are transient data stored in the BDCP and BDCPS tables (combiend togehter into view BDCPV) or stored in BDCP2 if configured to use this newer change poitner table for much better performance.
An instance of a change pointer in the change pointer tables will indicate the record that has changed and point to the changed document in the change document tables that can be referenced to extract more specific information.
The nice thing about change pointers are:
- They are transient, at the end of your extract you clear the ones that you've extracted so that the next time you will get the ones that have been pulled since then.
- You can setup instances of your change pointer object that are specific to an extract program so that two extract programs for similiar or even completly the same data won't itnerfere with each other.
- The CDHDR and CDPOS tables are great for extracting changes that have occured over time for a specific instance of a buisenss document (ex. Vendor) but do not perform well over time for extracting all changes associated with all instances of a buisness document (ex. All vendors that have had changes since the last run of the program). Programs that extract directly against CDHDR and CDPOS do perform delta extract functionality are oftern a performance problem as time progresses and the tables grow in size. If used properly Change Pointers are efficient becuase the tabels can be kept small and are optimized for the extracting of deltas.
For any tables that log change documents in CDHDR and CDPOS you can configure change pointers to be populated in the BDCP* tables.
Change pointer configuration:
- BD61 - Activate change pointers globally within the SAP instance
- WE81 - Need to create an ALE message type (even if you're not actaully going to connect it to an IDoc)
- BD50 - Activate change pointer functionality for your message type
- BD52 - Define the individual change documents, tables and fields that you want to have as part of your tracking
Your extract program will use two functions:
- CHANGE_POINTERS_READ - Use this to get a list of all change pointers since the last execution
- CHANGE_POINTERS_STATUS_WRITE - Use this to mark the change pointers as extracted so that they won't get picked up on the next execution
Transaction BD22 (Program RBDCPCLR) should be scheduled to run regularily to delete from the change pointer tables the records that have been marked as processesd.
Note - A common mistake that is made is that the change pointers are read, some filtering is done for specific ones that should be extracted and then only the extracted ones have their change pointer status updated. It's important to update the status on all of the change pointers because otherwise they'll be picked up again on the next run of the program and will be filtered out again, so over time the number of selected change pointers will keep growing since they will never get purged from the change poitner tables.
Note that the BDCP and BDCPS tables have a number of performance issues when the selections are done against them due to the way they are joined and the crieteria that is used for selecting. Becuase of this SAP has implimented a new change pointer table BDCP2 which is a single table as opposed to using a join. In order to utilize BDCP2:
- Used SM30 to update V_TBDME. For your message type turn on the checkbox for BDCP2.
- Run program RBDCPMIG for your message type, this will migrate existing pointers over to the BDCP2 table. If you can guarentee that there are no existing pointers then you can use SM30 to update for your message type the target of the pointers as being BDCP2
~Ian

Payment terms in Vendor Master data and purchasing info record

Hi, all, I met one trouble. While I create Purchase Order. In the header item, payment terms is automatically pop up from the data maintaining the vendor master data or purchasing info record if there is difference payment terms between in vendor master data and in purchasing info record. What happend?
Sometimes, When you create purchase order, payment terms is not automatically pop up even you maintained in the vendor master data or purchasing info record. Why? Is it meaning that I can manually to input payment terms while create each purchase order which can be difference data with vendor master data or purchase info record?
Thank you very much in advance,

Hi,
The payment terms is usually defaulted from either vendor master or purchasing master data record such as contract/outline agreement. Unless it is set through configuration that the payment terms be set as mandatory, any failure to maintain payment terms won't stop you from posting your PO as this information will only be useful during invoice receipt maintenance. Having said that if you are setting up your system with discount condition type as part of your PO pricing schema then it is necessary that the payment terms shall be maintained during PO creation.
Cheers,
HT

Can VMD_EI_API handle Create, Edit, and Delete Vendor Master records?

Hi Everyone,
I have a development that requires to create, edit, and delete vendor master records through a webportal ui. Technically, it will be a background process in SAP because it must not have a dialog screen. In my search so far, there is no standard BAPI or Function module that can handle this one.
Can the class VMD_EI_API handle the requirements?
Regards,
John

Hi,
Yes, You can use this class to create/modify/delete vendor master data. You can find in SCN documents with example how use it.
Jarek

Purchase organisation Field in Vendor master data

Hi All
During the creation of Vendor master ,Needs to make the Field Purchase organisation as a mandatory. I have checked the in the following configs.
Define Account Groups with Screen Layout (Vendors
Define Screen Layout per Company Code (Vendors)
Define Account Group and Field Selection (Vendor)
The option is not available. for the above requirement.
thanks & Regards
DP

In many companies the address data is maintained by different people than accounting data and purchasing org data.
I would not like that accountants to create my purchasing org data, and I am certain that my accountants dont want the buyer to create his accounting data.
if you could make this combination mandatory, then the user would have to maintain all screens at the same time, which may result in delays. as he can only start once he has all data available. SAP standard allows to create a vendor with general data and purchasing org data and purchasing can start buying. the company code data is only needed in the moment the goods arrive.
So you gain time to collect the data while you already started business.
Further, not all vendor master need to have purchasing org data. and not all vendors with purchasing org views need a company code view.
e.g. a restraunt may send you bills for lunch, but you do not place purchase orders with this restaurant. No purchasing org view needed here.
a goods supplier, that is needed for Intrastat purposes only, does not need a company code view, as you will never get invoices from the goods supplier.

Standard method to archive/delete all vendor master data

Hi every abap expert
Does anyone know how to archive all vendor master data
in a client?
If use T-code : SARA . The vendor master data is required to mark deletion flag before archiving.
Any standard T-code can set all vendor master data with marked deletion flag ?

Hi Boris!
Give XK99 a try. With XK06 a single change is possible and in FI also FK06 is available.
When XK99 has problems with field LFA1-LOEVM, then you can make easily a CATT for XK06.
Regards,
Christian

Can we use idoc technique to change or delete the vendor master data?

Hi,gurus,
Can we use idoc technique to change or delete the vendor master data?You know we can create vendor data using idoc CREMAS03 as the receiver adapter,but when change or delete the specified vendor data,must we use RFC adapter technique?
Another question:I found the bapi which creates a vendor master data doesn't have the parameter account group,then we turned to idoc technique.But which adapter should I use when change or delete the vendor data?
Thanks in advance.

Hi,
>>>I found the field of the segment of deletion flag at different level,and very appreaciate your help.
yes - LOEVM - but remember this will not delete the record but only mark it for deletion
>>>It's a long time to wait for your new blog,what new and interesting things do you find?
at least 4 new in my head - 2 simple but important and 2 new + I'd also like to write something for XI guys about
BO data integrator which can also work as EAI tool (BTW I know it's ETL) but how knows when they will appear
Regards,
Michal Krawczyk

Can we delete vendor master

Dear All,
can we delete vendor master records ?
if s how
regds,
CB

Hi CB,
Let me first convey you one concept that , Not only Vendor Master, We cannot delete ANY Master Data once it is created in the SAP System. The Only thing we can do is to set the Deletion Flag. That's all. For setting Deletion Flag for Each Master Record, there is respective transaction.
As you are inquring about Vendor Master
T. Code is XK06
Enter Vendor, Company Code and Purchasing Organization. In that select deletion Flag options which are A) All Areas Or B) Selected Company Code.
With option B) Selected Company Code functionality, you can block for vendor for one particular Company Code and for rest company codes, this vendor will be active.
I hope I have resolved your queries.
Regards,
Amol Joshi

Archiving of Vendor Master Data,

Hi All,
I want to Archive Vendor Master data .
For this purpose , I used two Archiving Objects - FI_DOCUMNT and FI_ACCPAYB so that I can archive data from tables LFA1 and LFB1.
After archiving using FI_DOCUMNT , I tried archiving(write) using FI_ACCPAYB.The job did not pick up even a single record with an eror - transaction figures exist.
Hence to remove transaction figure I used Archiving Object FI_MONTHLY. After Archiving using FI_MONTHLY,
when I again tried archiving FI_ACCPAYB,I faced another error - "cleared items still exist".
I found out 3 tables related to cleared Items.
BSE_CLR
BSAK
BSAS
I got cleared Items cleared form BSE_CLR through FI_DOCUMNT,but those cleared items still exist in rest two tables.For all these three tables archiving object is same i.e. FI_DOCUMNT. I don't know why it did not delete data from rest two tables.
Please clear my following doubts-
1. what is the proper data dependency and archiving Object to archive Vendor master data.
2. In DB15 -When we search tables for a particular archiving Object, does it mean that that particular Archiving object will archive data from all tables listed for that OBJECT.

Hi Deepti,
Archiving object FI_ACCPAYB is dependent on various other archiving objects such as FI_DOCUMNT, MM_EKKO and so on which means that before archiving FI_ACCPAYB, first we have to archive dependent AO if we want to keep track on all the transaction data for this Vendor.
You can directly archive VMR with FI_ACCPAYB with out considering dependent archiving object also, Prerequisites for this are:
1. There should be no open items for this vendor
2. It should be marked for archiving at company code level and Purchase organization level.
3. Deletion indicator should be marked through Preprocessing program
If a VMR have all the above criteria then you can archive the vendor.
2 Question:
When we archive then write program picks up the data from the table that is mentioned in the DB15 transaction under the particular archiving objects.
Reward if it is benifits.
-Thanks,
Ajay

Transfer data from a purchasing organization to another.

Dear all,
I am currently using two purchasing organizations: A and B. I don't want to use B anymore. There are source lists, purchase info records, suppliers, PRs, POs and maybe other data that are currently related to the purchasing organization B.
What should I do transfer the data to the purchasing organization A?
What would be the consequences of the "migration" of source lists, purchase info records on existing POs, PRs, on invoice verification, PR release strategy, PO release strategy, vendor master data, material master data...etc?
Thanks a lot
Olivier

It is like a migration from legacy, only difference is that the source is your own SAP system.
so you need extract the relevant data and do a load exchanging the purchasing org.
vendors can be extended to the new organisation via XD99 copying data from the old organisation.
material master is not purchasing org specific, hence no change needed.
Source list an info records need to be loaded, which can be done with LSMW.
you have to decide yourself what you want do with existing open orders, the vendor would not really understand and probably not even see a difference in the PO form if you cancel the order for the old organisation and send a new order for the new organisation.

Customer and Vendor Master Data.

Hi,
Can any body plz tell me how the customer and vendor master data created in real time implementation and the master data's are created by FI CO consultants.
And plz. tell me the procedure
Thank you

Hi
In Real Time Master Data team will look into Creation of the Master data.This will be as same as how you create in a training class.For every external party with whom we do business must be created as a Vendor or a Customer.The system offers seperate functions for maintaining Customer Master Records and Vendor Master Records depending on the requirements of your Organization.
A Complete Customer Account consists of General Data at the Client Level , Company Code Segment and Sales Area Segment.These Data records can be maintained Centrally for all areas or seperately for Financial Accounting and Sales and Distribution.
A Complete Vendor Account consists of General Data at the Client Level , Company Code Segment and Purchase Organization Segment.Vendor Master Records can be maintained Centrally for all areas or seperately for Financial Accounting and Materials Management.
Configuration of Creation of Vendor Master Data Centrally
1.Creation of Vendor Account Groups with Screen Layout -
OBD3
2.Define Screen Layout per Company Code -
OB24
3.Creation of Number Ranges for Vendor Account Groups -
XKN1
4.Assign Number Ranges to Vendor Account Groups -
OBAS
5.Define Tolerance Groups for Vendors and Customers -
OBA3
6.Creation of Vendor Master Data Centrally -
XK01
7.Define Document types and Number Ranges(KR,KZ,KA,KG) -
OBA7
Configuration of Creation of Customer Master Data Centrally
1.Creation of Customer Account Groups with Screen Layout -
OBD2
2.Define Screen Layout per Company Code -
OB21
3.Creation of Number Ranges for Customer Account Groups -
XDN1
4.Assign Number Ranges to Customer Account Groups -
OBAR
5.Creation of Customer Master Data Centrally -
XD01
6.Define Document types and Number Ranges(DR,DZ,DA,DG) -
OBA7
Creation in FI point of view.
Vendor Master Data -
FK01
Customer Master Data -
FD01
Creation in SD point of view.
Vendor Master Data -
VK01
Customer Master Data -
VD01
Creation in MM point of view.
Vendor Master Data -
MK01
Customer Master Data -
MD01
Regards
Venkat

Vendor Master Data fields - Description

Experts: Is there a list or a catalog that exists or someone has developed with a description of every field that can be used in the Vendor Master?
joseG
FI/CO Consultant

Hi,
As per my underStanding you want a detailed information or Notes abt each and every Field in the Vendor Master record ,as Asked by your Client. Right.
Please Use Below Table's which are related to Vendor Master Data.
LFA1 - Vendor master
LAB1- Vendor per company code
LFM1 - Purchasing organization data
LFM2 - Purchasing data
LFBK- Bank details
you can prepare a Detailed notes by clicking on F1 on each and every filed in the Vendor Master record to get the Functionality of tht Field and also show the Links in which tables tht data will updated.
Thanks
Goutam

Restrict access for Vendor Master Data

Hi all.
Our company structure is like below:
Single instance, just one mandant.
Company codes like 1001, 3001, 6002, 6006, etc... over the world.
At some companies just the central administration can create vendor for the companies using the transaction XK01.
Now we need to give access to users from one of our company from other country but we can´t give access to transaction XK01 because just the central administration can create the master data for the vendors.
I already read about the object F_LFA1_AEN that is possible to create some field groups and give access just for the rigth groups. I also read that this authorization groups don´t have effect on the vendor master data like address.
How can I restrict access for the vendor master data? I´m thinking to give access to transaction FK01 and MK01 and restrict access for create a new vendor, I only want that the users can create the data for a new company or new purchase organization.
Thank you
Darlei Friedel

among many other authorization objects, you find following three:
F_LFA1_GEN general data
F_LFA1_BUK company code data
M_LFM1_EKO purchasing org data.
If the user does not have authorization for F_LFA1_GEN , then he cannot maintain general data.

Delete Customer Master Data OBR2

Hi
I'm using LSMW to import data. I would like to delete it afterwards. Transaction OBR2 which is in spro Financial Accounting (New) -> Accounts Receivable And Payable -> Customer Accounts -> Master Data -> Delete Customer master data.
But it does not delete the sales are segment, it also does not allow me to delete general data if sales segment exists.
Can anyone please let me know if there is another way around this? Any other way to delete this test data???
Thanks in advance

Hi
Please go through the SAP documentation on how to perform deletion of customer master data.
This may help you in executing the function correctly.
<b>Delete Customer Master Data</b>
In this activity, you delete the master records for customers by using a program. Only use this program in the test phase.
Note
The company code for which master records are to be deleted, may not yet be flagged as productive.
Only master records for accounts which do not have any transaction data may be deleted.
Requirements
The general customer master data is only deleted for customers who are not also created as customers in Sales and Distribution.
Activities
Delete the master records for the required company codes.
Additional information
Refer to the SAPF019 program documentation for further information on the program.
Deleting Master Data
Description
This program deletes master data in Financial Accounting and is designed for preparing the system for productive startup. It deletes:
     Customer master data
     Vendor master data
     G/L account master data
You can run this program in three different ways:
1. Deleting general master data (in G/L accounts in one chart of accounts)
2. Deleting master data dependent on company code
3. Deleting general master data and master data dependent on company code
For each deletion run, you can specify whether or not the system should take into account the deletion flag in master records ("Delete per deletion flag only"). If it takes into account deletion flags, it uses the following standard logic:
Option 1: The "All areas" deletion flag must be set.
Option 2: The "Specified co. code" deletion flag must be set.
Option 3: It is sufficient to have the "All areas" deletion flag set.
Note: Deletion blocks are always checked at general data and company code-dependent data level. If there is a block at company code-dependent data level, then the general data is not deleted either. The deletion block takes precedence over the deletion flag.
General master data in Financial Accounting can also be used in other SAP applications:
     Customer master data in Sales and Distribution
     Vendor master data in Purchasing
     G/L accounts as primary cost elements in Cost Accounting
The program deletes the following:
     Change documents for master data
     SAPscript text files
     The following data is deleted for customers:
o     General master data
o     Bank details
o     VAT registration numbers
o     Addresses
o     Classifications
o     Credit management: across control areas
o     Credit management: centrally
o     Unloading points
o     Tax indicators
o     Contact persons
o     Licenses
o     Partner function limit
o     Shipping data
o     Master data in the company code
o     Dunning data
o     Linked data
     The following data is deleted for vendors:
o     General master data
o     Bank details
o     Contact persons
o     VAT registration numbers
o     Addresses
o     Classifications
o     Master data in the company code
o     Dunning data
o     Linked data
     The following data is deleted for G/L accounts:
o     General master data in the chart of accounts
o     Names in the chart of accounts
o     Key word list in the chart of accounts
o     Master data in the company code
o     Sample accounts, if selected
For customer and vendor contact persons, the addresses are not determined from central address management until the actual runtime. Therefore differences can arise as to the number of addresses in the detail log between the test run and the update run.
Automatic worklists for customers and vendors are also deleted with the general master data. Matchcodes are always deleted.
You may have to fix the number ranges after the program run.
The system makes changes to the database in the update run only. It will then also write a system log entry for documentation.
Requirements
General master data can only be deleted if no other application makes reference to the account. Use the resetting programs from
     Sales and Distribution (customer master data)
     Purchasing (vendor master data)
     Cost Accounting (G/L account master data)
If you want to delete only general master data, master data dependent on company code cannot have been created in Financial Accounting.
If you want to delete master data in a test company code, master data dependent on company code cannot have been created in any other company code except the test company code. The productive indicator cannot be set for the company code.
If a customer or vendor is referenced by another customer or vendor (for example, via fiscal address or alternative payee), you can only delete the referenced master record by deleting the referencing master record at the same time.
Furthermore, you can only delete master data in Financial Accounting if no transactions have been posted to the corresponding accounts. If there are transaction figures in one of the selected accounts, you have to manually access and run program SAPF020 (reset transaction data from a company code) before you can delete that account.
Output
The log lists every table which is processed in the program selection.
You can also create a detail log for each account type to find out why certain data cannot be deleted. The detail logs show you what other company codes and applications use the data and how customers and vendors are linked to one another.
Note
Since deleting or displaying even smaller volumes of data can result in runtime problems, you should run this program as a background job. Currently, the program individually deletes matchcodes for each master record in the database. Several match code IDs refer to each matchcode. This can place a considerable load on the database.
You cannot delete transaction data in individual accounts.
Important: The archiving programs in Financial Accounting are designed for the productive system.
If you are running this deletion program for the first time, then you must start program SAPF047 before deletion in order to generate link information.
I hope this may be of help to you
Good Luck
Hari

Delete Vendor Master Data in a Purchasing Organization

Similar Messages

Maybe you are looking for