Deleting customer master files

hello all,
is it possible to completeley delete a customer off SAP, and not just mark it for deletion?
I need to also know how to mark them for deletion?
thnks

Hello Saping...
As per Standard, You can not delete the customer completely from the SAP Data Base,but you can mark deletion flag to the customer.
Through XD06 transaction, go to XD06 transaction,
In the Customer Flag for Deletion:Initial screen you enter the customer , Company code and sales area details of the customer which you want mark for deletion then press enter system will take you to the next screen called Customer Flag for Deletion:Details here you can select whether you mark for deletion
a.All sales ares
or
b.selected company code
or
c.selected sales areas
Then save the changes
If you create Sales order with deleted customer system will give the warrning message "The Customer 'XXXX' flag for deletion".
I hope it will help you
Regards,
Murali.

Similar Messages

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

I can't delete the master file, which is located on my external HD, through aperture

I import a folder to aperture which is stored on my external HD, and keep the originals on the HD. If I try to delete a master file with the option, file-delete master image and all versions, the photo deletes from Aperture, but not my hard drive. I have even tried to delete my trash, but no luck. Please help, otherwise I do not want to use aperture for file management, which was one of my major reasons for buying it.

After you've deleted a file it from the project it goes into Aperture Trash. When you empty Aperture Trash (Aperture>Empty Aperture Trash) you will get a dialogue box asking "Are you sure you want to permanently delete all items in the Trash?" Under this there is a checkbox giving you the option to "Move referenced files to System Trash". If you check this box it will move the master to the system trash, and from there you can permanently delete the file.
All this is to stop you from accidentally deleting work.

Can I configure to always delete the master file?

Hi!
If I want to delete a file, I don't just remove it from the cataloge, but to delete the master file, too.
If I use the remove key, I get the (annoying) pop up, what I want to do: (sorry, I've a german version, so I just try to translate it)
Delete from hard disk
Remove (default selected)
Cancel
Is there any chance to avoid this dialog? Or at least to chance the preselected button, so I've just to use the enter key?
Actually I've to
press delete
press left arrow key
press enter
That is a little bit annoying and error-prone
Thanks a lot!
P.S.: I just found out, that ALT+DELETE is a shurtcut to remove the file from the catalog. So it would be greate to have a similar shurtcut to delete the file from the filesystem.

Thanks!
But it is almost the same as CTRL+ALT+DELETE, which has a special meaning in Windows :-(
So there is no way, to get a delete action, that easiliy deletes, without pressing four keys in parallel? :-|
Perhaps, the developers of Lightroom could provide an option, so you get the pop up, but the default action is different. That would be really great.

Delete customer master data

I want to delete customer master data.There is no transactions posted yet.Also let me know how to archive.

When i goto OBR2 to delete syatem says LINKS STORED INCOMPLETELY.
THE MESSAGE SOWN BELOW :
Links stored incompletely
Message no. FG166
Diagnosis
Customer/vendor links are to be taken into consideration when archiving or deleting customers or vendors. To do this, link data from the database is required which in this case has not yet been put together.
System Response
Neither archiving nor deletion was carried out.
Procedure
Run program SAPF047 in the background at a time when no customer/vendor changes are being made. This program puts together the link information in table KLPA so that links (for example, specification of an alternative payee or dunning recipient) can be taken into consideration during deletion or archiving. You can find more information in the documentation for SAPF047.
PLEASE HELP !!!!!

Error while Deleting Customer Master

Dear Friends,
I have a Customer master record, in which not even a single transaction (SD or FI) has been posted till date.
We now want to delete this Customer Master record & I am trying through T-Code OBR2
But I am getting a Error - Reset the number ranges if necessary
Please suggest how to solve this & delete the Custoemr Master.
P.S. I dont want to block the Customer & we want to delete it. Also I have run the program SAPF047 in SE38.
Thanks,
Jignesh Mehta

Dear Jignesh,
How are You?
Just have a look in to following SAP Help file, regarding Customer Archiving.
http://help.sap.com/saphelp_47x200/helpdata/en/f7/ea0d38d89d6454e10000009b38f8cf/content.htm
You can decide whether you want to archive all the following areas together or each area separately by making the appropriate settings in the variant.
--> General area
--> Company-code specific (FI-specific) area
--> Sales + distribution-specific (SD-specific) area
I think, this will be helpful.
Best Regards,
Amit

Deleting Customer Master

Hi,
I want to delete a customer from SAP. I don't want to use XD06. This would just mark it for deletion. The users in my company created a customer as sold to party and they want to change the account group to ship to. using XD07 - "Change Account Group" some of the field pertaining to sold to party would be masked if its changed to ship to..So SAP is not lletting me do that. I want to use the same name for the ship to. The only way is to remove the customer out of the system. How do I handle this. Is there any way i can used the same customer name with a different account group.
I would really appreciate if someone can help with this........

If you want to totally remove the customer from system then you have to archive the customer otherwise mark the current customer for deletion and create new.
Unless you have some custom coding, system will not stop you from creating another customer with the same name. So I don't see an issue here.

Please help!-I deleted the master file

Ok. for the first time I accidentally deleted a sitting from the original file folder. It's not anywhere, not trash, I searched the entire computer, etc.
Is there a way to restore it thru lightroom? I still have the lightroom files but of course they say the filename "IMG_0558" is offline or missing.
Please help. I can't call this client with this huge mistake.

Yes, that is what I normally do. However, this week I lost contact with one entire side of my family due to mental illness (not mine), and then my grandmother passed away as well. Her funeral was just yesterday. This doesn't excuse my failure to back up again but I was no mind to be handeling files and I should not have been. I should have gone to bed instead. I am a responsible photographer, this has never happened in 13 years. I've just had the worst week of that 13 years almost.
It's my own fault, and a mistake that I made. I just need help in trying to fix it if possible.
I'm trying the restoration programs now.

How to delete the master data of a Customer created in a SALES AREA?

Hi All,
I've deleted a Customer (master data) by t.code OBR2. But it exists again in its SALES AREA.
Could anyone tell me how to delete it in the sales area too?
Thanks

Hi,
I dont think you can delete a customer. you can market it for deletion in XD06.
for deleting customer master data you have to setup an archiving project.
Also check the similar thread
doubt in obr2
Hope it helps you.
Regards,
Sats.

Use Referenced Masters To Avoid Accidentally Deleting A Master Image File

If you use Managed images it is possible to delete the master file accidentally. If you delete versions of an image using File -> Delete Version and the version you are deleting is the last remaining version for that image, Aperture 3 will delete both the version and the master image. If you subsequently empty Aperture Trash and then System Trash that master image file is gone forever. In Aperture 3 there is no warning that you are about to delete a master image.
A workaround (although a weak workaround) is to use Referenced Image Masters. Then when you delete the last version which includes the master image from Aperture, you can uncheck the box "Move referenced file to system trash." and no master image file will be deleted. The downside to this workaround is that when you really want to delete a master image file, it must be done via Finder.
The best solution would be for Apple to fix this bug so that when you select "Delete Version" it only deletes the version image and reverts to the master image. That way the master image can only be delete via the command "Delete Master Image and All Versions."

There is no bug there.
I had some trouble wrapping my mind around the file-Master-Version-Image-(Preview) complex that flows, sand-like, through the entire working of Aperture. (I like a thing to be represented by itself and itself alone, and to exist in one place and one place alone. I was comfortable with the seeming precision of the location-based "file+path" metaphor for the existence of these virtual things. Aperture quite cleverly moves beyond that.) Two things helped me move forward:
- understanding the difference between Projects and Albums, and
- separating my Library into a storage area and an output area.
Projects are, for me, storage containers. (I have said elsewhere that the mis-naming of "Projects" is the single worst interface decision made in Aperture.) They have a privileged relationship with your Images: every Image must "live" in a Project, and "lives" in only one Project. It may help you to think of "Image+Project{Path}" as functionaly equivalent, within the Aperture Library, to the file directory "file+path" mentioned above.
Albums are, for me, output containers. I create Albums every time I know I will output a set of Images.
In practice, I work on Images in each. In general, I develop my digital captures in the Project that holds them (and I rigorously stick to "One Project = One shoot"), I create Versions and add them to Albums as needed for output (they are automatically made the Album Pick), and I tweak them for output and then output them from Albums.
You may be wondering (if you've read this far) -- "What has this got to do with deleting Masters?" A lot. Note the difference in the context-menu between a Version in a Project and a Version in an Album. The menu for the Album contains two delete commands: "Delete Version", and "Remove from Album". The Versions live in Projects, and only visit Albums. As Terence correctly points out, if you delete the last Version, your expectation should be that you are deleting that Image from your Library. My suggestion is that you adopt something similar to what I've set up, and delete Versions from ONLY Projects (never from Albums). This way you will never unknowingly delete the last Version (because Images can be in only one Project, and if you delete the last Version from that Project you know you are expunging that Image from your Library).

Custom master page issue in subsites

Greetings!
I've run into an oddity with a custom master page on my SharePoint 2013 Enterprise server. I copied the html for the seattle master page, renamed it so it wouldn't change the seattle master, made an addition to it to add a reference to a custom css
file, then threw it back up on the site so SP would make a new .master file with it. I created a new web app and site collection, put the custom css file in the Style Library and added the custom master page to the Master Pages.
So, all that being done, I changed the look of the top level site to use the new master page and it looks great and seems to be working as expected. We've got a number of subsites planned for underneath this top level site, I'm thinking no problem, just
put the custom master file in the master pages and we'll be good. So I create a subsite, put the custom master page in the subsite's Master Pages, change the look. The master page and custom css apply and it looks good, but, then the problem starts.
When I go into a document library and change a view or add a view or delete a view I get back an odd response page from SP. In the url I see this: https://topsite/subsite/_vti_bin/owssvr.dll?CS=65001
and in the body of the message: 69|pageRedirect|owssvr|https://topsite/subsite/Shared%20Documents/Forms/AllItems.aspx|
When I go back into the subsite, whatever change I was attempting when I get these results worked fine.
So, why does my custom master page work fine on the top level, but not on the subsites? If I switch the subsite back to the Seattle.master, the oddity goes away, so that tells me it's something to do with my custom master page and/or custom css. I did
some searching for owssvr.dll?CS=65001 and didn't see anything that helped. I checked IIS and the web.config file and don't have ASP.net tracing on that I could find.
All that the custom css is doing is increasing the size allowable for the site icon (.ms-siteicon-img) to allow for a larger icon (180px square) and it pushes the side Nav Box down a bit to make room for the larger icon and changes the font size for the
side Nave Box (#sideNavBox). Since it works on the top site, I'm not suspecting the css, but, it's not making sense to me why the custom master page wouldn't work in subsites either.
I ran into this issue earlier, it was showing up when deleting folders from the document library. I thought I'd made a boo-boo somewhere in creating the custom master page, or how I'd added it, or something (kind of a learn as I go situation here), so I
deleted the entire web app and recreated it, hoping for a clean start and a good master page and everything would be good. Guess I'm still missing something.
I swear that the ONLY change I made to the seattle html file for my custom page was to add this line just below the corev15.css line: 
So, that's my sad story. Any suggestions, other than to punt on the custom master page?
Thanks!
Steven

Thanks. I've been experimenting with this for a few days now, and there's lots I don't understand about why and such, but your process above works. That's a big load off me right now and I really appreciate it. I'm going to be able to survive the initial
roll-out and implementation of the new site. Going forward, I've got lots to learn and find out, I've already heard that there's a desire to really redesign the master page for the site and subsites, way beyond the little CSS customization I did. Fun.
If you've got a little time though, perhaps you can provide some explanation. If not, no problem.
On step 6, when I do as you detail, click the System Master Page and reset all the subsites, it seems to work fine with my custom master page. If I do that with the Site Master Page settings, my custom page causes the redirect issue in the subsites again.
This is whether I do the Site Master Page by itself, or in conjunction with the System Master Page settings. If I revert back to the Seattle master page in the Site Master Page settings and my custom pate in the System Master Page, the issue goes away again.
It is completely messing with my head, trying to figure out why that would be, and this is all beside trying to figure out why adding the one little CSS reference to the Seattle master to create my master page breaks things (sometimes!).
Just fyi, what I've ended up with for now is pulling my custom master page out of the system and using the Alternate CSS URL to add my custom CSS to the Seattle master page on the sites. As I thought about all this, I decided I didn't want to leave the breakable
custom page out there for some unsuspecting site manager to accidentally pick and get everyone screaming about the broken sites.
Thanks again,
Steven

LSMW - Customer Master & BAS

Hi!
We are trying to load a Customer Master file from a flat file using LSMW and Data Transfer Workbench to load the address data in BAS (since we need to access some extra fields like email address). The problem is that LSMW also creates a new address in BAS so how do we associate the address created by Data Transfer Workbench to KNA1? Do I need an ABAP program and functions ADDR_ADOWNERREF_READ and ADDR_ADOWNERREF_DELETE? Do I then just write over the value in the KNA1-ADRNR field with the value created by Data Transfer Workbench? Can this be done automatically using LSMW?
Thanks,
Tony.

Hi Tony,
I know you have posted this a long time ago but were you able to figure this out?
If you were, can you please help me with this.
Thanks,
Kevin

About customer master record

hi
how to delete the customer master record in the company code
regards
raj

Hi Rai,
U can delete customer master record company code based by using Tcode XD06, Sales org based by using Tcode VD06.
simply if u created customer by using Tcode XD01, for deletion u can use XD06, in case if u created by using Tcode VD01, then u can use VD06 for deletion.
Regs,
Ravi Duggirala

Auto Numbering- Customer Master Records

Hello,
I am in the process of setting up Oracle AR 11i, but will not be utilizing OM in this phase of the project. To eliminate unneccesary interfaces, I was planning to import Customer Master File number and Invoice number into AR from the legacy application. If I set the set up to manual numbering for invoicing, can it be easily changed to automatic when we convert to Oracle OM?

I agree with you, and you just confirmed what I thought about the numbering...the legacy source is a good suggestion!
Thanks again,
MJK
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Milan Martak ([email protected]):
Mark,
everything is possible with Oracle Applications ;-)
If you set up AR, there is Transaction Batch Source - here You actually set Manual/Automatic numbering. From my experience from previous projects is good idea to create source "Legacy" for legacy data load. Then you can easily set different source (and never touch "Legacy" source) to continue in legacy sequence with automatic numbering.
hope it helps.
Milan
Originally posted by Mark Kane ([email protected]):
[b]Hello,
I am in the process of setting up Oracle AR 11i, but will not be utilizing OM in this phase of the project. To eliminate unneccesary interfaces, I was planning to import Customer Master File number and Invoice number into AR from the legacy application. If I set the set up to manual numbering for invoicing, can it be easily changed to automatic when we convert to Oracle OM?<HR></BLOCKQUOTE>
null

Deleting a Contact on Customer Master with that Contact on Open Sale Orders

Our current SAP system ECC 6.0 allows a user to delete a Contact from the Customer Master where that Contact is also on Open Sales Orders.
Then when our create delivery job runs, it abends saying Contact record not found.
How is this normally handled ? Are users not suppose to delete Contacts from the Customer Master if they are attached to an Sales Order ? Is there some config to turn on in SAP that checks for Open Sales Orders before deleting a Contact in the Customer Master ? Do I code this check in User Exit on the Save in the Customer Master and not let user delete the Contact if it's attached to Open Sales orders ?
Would appreciate any help on this.
Thanks,
David

Hi David,
Try this user exit.
RFDRRANZ User exits: Accounts Receivable Information System
Regards,
Vijay

Deleting customer master files

Similar Messages

Maybe you are looking for