Urgent!!! : To delete table entries in COKA,COSP,COSB from FY2010

Problem:
Business needs to limit the validity of certain cost elements to 31st
March 2007. But not able to do the same due to updation of Tables
COKA,COSP and their dependent Tables.
Reason:
The business is currently in fiscal year 2007.Some tables were updated
till fiscal year 2010 due to future date(Example March 20th 2009)
mentioned in scheduling in Production Order/Process Order.
In certain Production Orders/Process Orders, scheduling date was
erroneously updated referring future fiscal years up to FY2010.
This has caused the updation of CO tables COKA ,COSP and their
dependent tables COKP, COKS,COSS,COKL,COEJ,COBK,COEP,COVP.
Even if we revert the scheduling dates back to current year in the
Process Order/production order, the table information is present in the
future fiscal years which prevents deletion of cost elements for the
future period.
Steps for the Reconstruction
Solution required:
We need to know the systematic procedure/program/process through which
we can delete the entries in main tables COKA, COSP and the dependent
tables (COKP, COKS, COSS, COKL, COEJ, COBK, COEP, and COVP.)without
affecting the integrity of information present in the production
order/Process Order for the current period.
Ultimately we should be in a postion to restrict the validity period of
cost elements to 31st March 2007.

Hi,
I am not sure, whether this will help you or not. I think you can archive the data in the first stage.
Then try to work on the validity periods.
Rgds,

Similar Messages

How to track , who has deleted table entry

Hi Experts,
Is there any way so that i can know that who has manually deleted few entries(data records) from my table,actually my table has "Display maintenance allowed" property set.
Can we track it anyway that when and who has deleted that table record.
Regards,
Abhishek

Hi Abhishek,
Actually the changes made for an entry into table will have two effects.
Changes at the data element level and another at the entire db table level all these changes will have an entry only if the change documentation is activated.
Table logging concept wherein SAP records all insertions, deletions, and changes in tables
OSS note 139418 will gibe you general information on logging user actions.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eaf9446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/Helpdata/EN/7e/c81ebb52c511d182c50000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a0/7d1020dac8994fa63ff270dbceb87f/content.htm
revert for further clarification,
Thanks and Regards
Srikanth.P

How to delete table entries with SE16 in debugging mode?

We are trying to delete some table entries which cause our InfoPackage short dumps in BW system. The problem is that we can only see the Display menu item with SE16 and the Delete menu item is dimmed that we are unable to conduct the deletion. SAP Support suggest to use debug with SE16 to do the deletion, but we can't figure out how!
Anyone's idea is greatly appreciated!

Then you are not at the right place. Lets start at the begining.
Go to SE16.
Enter table name.
Hit F7.
Enter selection criteria.
hit F8.
Double click the specific record that you want to delete.
In the transaction code field at the top, enter "/H" and hit enter. Debug is switch on.
Now hit enter again.
You should now be in debug and you should see this code..
form set_status_val tables ntab structure x031l
 using code name next for_lines.
field-symbols: <field>.
refresh exclude_tab.
if code = 'SHOW'.
 set titlebar 'TAB' with name 'anzeigen'(100).
elseif code = 'EDIT'.
 set titlebar 'TAB' with name 'ändern'(101).
elseif code = 'INSR'.
 set titlebar 'TAB' with name 'einfügen'(102).
elseif code = 'ANVO'.
 set titlebar 'TAB' with name 'einfügen'(102).
elseif code = 'DELE'.
 set titlebar 'TAB' with name 'löschen'(103).
Notice that there is a field called CODE in the IF statement.
Now enter the word "CODE" in the field names list, change the value to DELE and click the pencil. Hit F8. Now you can delete the entry.
Regards,
Rich Heilman

How to transport a Deleted Table entry

is there a way of transporting deletions of table entries.
For example. I'm dealing with a table say such as T529U. So we already have value there for active, inactive, retiree, withdrawn. Say I wanted to delete retiree from the selection list.
I go to our DEV and make the deletion. I manually create a transport of the entire table and transport it to our QA system. When I do so, the table still remains the same. The only way the record would be changed would be if it was new or had the same key (thus overwriting). How do you remove and transport (so you don't have to do it in all instances).
any help would be much appreciated.
Thanks

Hello
A delete should be a change just like any other change and should be recorded on a change request. After releasing the change request you should be able to transport that delete to your QA and PRD systems as needed.
As a general rule I would not transport the complete table. There is too much risk that unintended changes get transported.
Are other changes to your table being recorded on a transport request?
If you have another environment(sandbox or project?) try the delete in that environment to convince yourself that it does(or does not )work.
Regards
Greg Kern

Check who's deleted table entries without SCU3

Hi,
we need to find out which program or user deleted some table entries. The Where-used-list doesn't show anything, so it must be a dynamic call. The table has 'Log data changes' switched on, but we don't have the system logging set due to performance reasons. Is there nevertheless a chance to find out who deleted the entries?
Regards
Nicola

Regarding where-used-list, maybe the table is part of a maintenance view, you should check this as well.
If there is no table logging and the changes are not recorded in transport requests, then I'm afraid there is no way to find out.
Thomas

Deleting Table Entry

Hi
How can I delete a table entry which was entered in the Table through a Std Txn?
I have heard that there are 3 ways:
1) SM30
2) SE16
3) Debugger
What are the necessary requirements for using each of the above methods? Please guide me through the steps on each.
Thx

Hi Santo,
1) To Delete a entry form SM30 Transaction .
GOTO SM30 - > Enter the table name -> display -> display / change push button ->
Click on entry which u want to delete -> click the delete button.
2)SE16 -> table name -> click execute -> double click on the required entry which u want to delete ->
on command field enter /h -> enter ->in debugging mode -> Change the value of code to 'DELE' -> Enter
Be careful before deleting any entry.
Regards,
Sachin

How to use transport request to delete table entries on target system

I released a request from DEV system to QA system , the request(request 1) delivered some table content,
but some of contents are incorrect, is that possible to release another request(request 2) to QA system,in
the request 2, I can specify which records needs to be deleted, so when request 2 is imported into QA
system, all the incorrect records are deleted?
Is there any API for me to create such a request 2?
The problem is we delivered some redundant table enties when project released to customer,
we want to delete these redundant records in support package, when customer installed support
package, all the redundant records are deleted, so no manual actions are needed on customer side.
thanks very much.

Hi
It should be as simple as deleting your entries, saving as a transport and then sending the transport to the client and this should override what is there
Frenchy

Problem in table entry deletion

Hi
i have deleted table entry in VBRK and vbrp
is there any facility to get back the deleted entry .
pls let me know

Hi
when ever your doing some changes to existing one don't delete directly, you need to make new vertion or copy that into another and made changes to that one
now u don't get that fields any where
you need to append that field to that table by creating a structure for that field
reward if usefull

Cost element deletion-COEP entries deletion originated from Spl purpse ledg

Hi Folks,
We have created RA GL account by mistake as cost element and some entries have already gone into table COEP table. To delete cost element the prerequisite is that cost element shouldn't contain any entries. We have deleted COEP entries by using program "RKACOR20 : to delete CO documents for the GL doc and its reversal document" generated from FI, but unable to delete one entry which has got originated from Special purpose ledger. Can any one suggest way to delete this entry from COEP table.
Thanks in advance.
Thanks
Rajesh Angadala

Hi
Check the below program, may be it works :
Function Module: K_OBJECT_DATA_DELETE
Program :
RGUREP03                       FI-SL: Delete Line Items and Correct Totals Reco
MGCU3TOP                       FI-SL: Delete Transaction Data
SAPMGCU3                       FI-SL: Delete Transaction Data
SKS

Delete tables (cleanly)

hi guys,
How do we (1) delete tables (2) delete table entries
and together deleting the other entries with corresponding foreign key?
Thanks
Message was edited by:
 TY Ng

Hi ,
U can delete entries from the table using the following syntax.
DELETE FROM <TABLENAME>.
Variants:
1. DELETE FROM dbtab WHERE cond.
DELETE FROM (dbtabname) WHERE cond.
2. DELETE dbtab.
DELETE *dbtab.
DELETE (dbtabname) ...
3. DELETE dbtab FROM TABLE itab.
DELETE (dbtabname) FROM TABLE itab.
4. DELETE dbtab VERSION vers.
DELETE *dbtab VERSION vers.
Effect
Deletes lines from a database table (see Relational Databases ). You can specify the name of the database table either in the program itself with DELETE FROM dbtab ... or at runtime as the contents of the field dbtabname with DELETE FROM (dbtabname) .... In both cases, the database table must be known to the ABAP Dictionary. Only data from the current client is usually deleted. You can delete data using a view only if the view refers to a single table and was created in the ABAP Dictionary with the maintenance status "No restriction".
DELETE belongs to the Open SQL command set.
Notes
The DELETE statement does not perform authorization checks. You must program these yourself.
The final (irrevocable) deletion of lines with the DELETE statement is not performed until after a database commit (see Logical Unit of Work (LUW)). Prior to this, you can reverse any database update with a database rollback (see Programming Transactions).
You cannot rely exclusively on the locking mechanism of the database system to synchronize several users trying to access the same dataset at the same time. You should therefore use the SAP locking mechanism.
Variant 1
DELETE FROM dbtab WHERE cond.
DELETE FROM (dbtabname) WHERE cond.
Addition:
... CLIENT SPECIFIED
Effect
Deletes lines in a database table that satisfy the WHERE clause cond. With this variant, specification of a WHERE condition is obligatory .
When the statement has been executed, the system field SY-DBCNT contains the number of deleted lines.
The return code is set as follows:
SY-SUBRC = 0:
At least one line was deleted.
SY-SUBRC = 4:
No lines were deleted, since no line was selected.
Example
Delete all bookings for the Lufthansa flight 0400 on 02.28.1995 (in the current client):
TABLES SBOOK.
DELETE FROM SBOOK WHERE CARRID = 'LH' AND
 CONNID = '0400' AND
 FLDATE = '19950228'.
Note
To delete all the lines in a table, you must specify a WHERE condition that is true for all lines. You can achieve this with
... WHERE f IN itab
If the internal table itab is empty, such a condition would select all lines.
Addition
... CLIENT SPECIFIED
Effect
Switches off automatic client handling. This allows you to delete data across all clients in the case of client-specific tables. The client field is then treated like a normal table field, for which you can formulate suitable conditions in the WHERE clause.
You must specify the addition CLIENT SPECIFIED immediately after the name of the database table.
Variant 2
DELETE dbtab.
DELETE *dbtab.
DELETE (dbtabname) ...
Additions:
1. ... FROM wa
2. ... CLIENT SPECIFIED
See Short forms not allowed and * work areas not allowed.
Effect
These are SAP-specific short forms used to delete one line of a database table. If the name of the database table is specified in the program, the primary key of the line to be deleted is taken from the specified work area - dbtab or *dbtab. If the name of the database table is not determined until runtime ( DELETE (dbtabname) ...), the addition ... FROM wa is obligatory .
When the statement has been executed, the system field SY-DBCNT contains the number of deleted lines (0 or 1).
The return code is set as follows:
SY-SUBRC = 0:
The line was deleted.
SY-SUBRC = 4:
No lines could be deleted, since no line exists with the primary key specified.
Example
Delete the booking with the booking number 3 for the Lufthansa flight 0400 on 28.02.1995 (in the current client):
TABLES SBOOK.
SBOOK-CARRID = 'LH'.
SBOOK-CONNID = '0400'.
SBOOK-FLDATE = '19950228'.
SBOOK-BOOKID = '00000003'.
DELETE SBOOK.
Addition 1
... FROM wa
Effect
Takes the primary key for the line to be deleted not from the table work area dbtab, but from the explicitly specified work area wa. Here, the key values from left to right are taken from wa according to the structure of the primary key in the table work area dbtab (see TABLES). The structure of wa is not taken into account. Therefore, the work area wa must be at least as wide (see DATA) as the primary key in the table work area dbtab and the alignment of the work area wa must correspond to the alignment of the primary key in the table work area. Otherwise, you get a runtime error.
Note
If a work area is not explicitly specified, the values for the line to be deleted are taken from the table work area dbtab, even if the statement appears in a subroutine (see FORM) or function module (see FUNCTION) where the table work area is stored in a formal parameter or a local variable of the same name.
Addition 2
... CLIENT SPECIFIED
Effect
As with variant 1.
Variant 3
DELETE dbtab FROM TABLE itab.
DELETE (dbtabname) FROM TABLE itab.
Addition:
... CLIENT SPECIFIED
Effect
Mass deletion: Deletes all database table lines for which the internal table itab contains values for the primary key fields. The lines of the internal table itab must satisfy the same condition as the work area wa in addition 1 to variant 2.
The system field SY-DBCNT contains the number of deleted lines, i.e. the number of lines of the internal table itab for whose key values there were lines in the database table dbtab.
The return code is set as follows:
SY-SUBRC = 0:
All lines from itab could be used to delete lines from dbtab.
SY-SUBRC = 4:
For at least one line of the internal table in the database table, there was no line with the same primary key. All found lines are deleted.
Note
If the internal table itab is empty, SY-SUBRC and SY-DBCNT are set to 0.
Addition
... CLIENT SPECIFIED
Effect
As with variant 1.
Variant 4
DELETE dbtab VERSION vers.
DELETE *dbtab VERSION vers.
This variant is not allowed in an ABAP Objects context. See VERSION addition not allowed.
Note
This variant is now obsolete, since variants 1 - 3 allow you to specify the database table name dynamically.
Effect
Deletes a line in a database table, the name of which is taken from the field vers at runtime. The database table must be known to the ABAP Dictionary and its name must conform to the following naming convention: It must begin with 'T' and can consist of four additional characters. The field vers must contain the table name without a leading 'T'. Only lines in the current client are deleted. The line to be deleted is taken from the statically specified table work area dbtab or *dbtab.
The return code is set as follows:
SY-SUBRC = 0:
The line was deleted.
SY-SUBRC = 4:
No lines could be deleted because no line existed with the specified primary key.
Reward points if this helps,
Kiran

Maintaining Table Entries directly in production

Hi All,
I have created a Z table. This table has been moved to production. Currently table entries are transported to production from development client. But this table regularly gets changed and so this needs to be maintained day to day basis. As per the policies transport request to production is moved only at specific times. Client in the production is not modifiable (Closed Client where no change authorization). To maintain the entries in the table every time client in the production should be opened.
Can you please let me know is there any way we can maintain the entries without opening the client for changes and without moving the entries with the transport request? Is there any other way to maintain the entries?
Thanks in Advance,
Shravan G.
Moderator message: please use more descriptive subject lines from now on, changed for you this time.
Edited by: Thomas Zloch on Nov 30, 2010 2:26 PM

Dear,
Create a maintainence view on that Z table. In that Maintainence table select Maint status->Delivery class-> select "Customizing" option. If any one creates new entry in Dev, system popsup for a TR. Those new entries will be saved in to TR. You can transport that TR across landscape.
The above one general practice for customization.
If you dont want that, create a table maintainence dialog on that z table and hence create a tcode with SM30 from SE93 transaction code.
Go to SE93-> select transaction with parameter
                      Enter transaction SM30
                      check Skip initial screen
                      In default values maintain below:
                  VIEWNAME     Z table name
                  UPDATE     x
Using that tcode you can maintain values directly in production
Thanks and Regards,
Edited by: chandra madapati on Nov 30, 2010 6:17 AM

Delete all entries from the following tables - Follow-up Activities (oracle)

Hello,
I performed a homogeneous system copy of our development BW system with the database (oracle 11.2.0.3) from the BW production system!
I already start the oracle database and the SAP system in the target system/server (development BW system) and I´m doing some follow-up activities. One of this activities is (at the system copy guide 6.2.3.2 Activities at Database Level) is to delete all entries from the following tables:
DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA
I tried to delete them using SQL Plus:
sqlplus /nolog
SQL> connect /as sysdba
SQL> delete from DBSTATTORA;
delete from DBSTATTORA
ERROR at line 1:
ORA-00942: table or view does not exist
... and it show me that error message.
This is strange because when I go to transaction SE14 and check the DBSTATTORA I see that table exist and contain a lot of entries!
Why this is happened in SQL Plus!? I´m running the correct SQL statement for doing this type of task or not?
How can I delete the entries of that tables? Can I do that using the transaction SE14?
Can you help me please?
Thank you,
samid raif

Hello
sqlplus /nolog
SQL> connect /as sysdba
SQL> delete from DBSTATTORA;
delete from DBSTATTORA
ERROR at line 1:
ORA-00942: table or view does not exist
It doesn't surprise me as you are not mentioning the schema name here. Instead it should be
delete from SAPSR3.DBSTATTORA;
Assuming the schema owner is SAPSR3. if the owner is different then replace that with the correct one.
Regards
RB

To delete multiple entries in table control in module pool

Hi,
Please help me out to know , how to delete multiple entries from table control when multiple lines in table control are selected.
Regards,
Irfan Hussain

hai,
you can do it inthis way.
in the PAI event.
loop at <table control name>
module del_itab.
endloop.
in the nodule,write the folowing code.
if <tablecontrol>-fieldname = 'X'.
delete <tablecontrol-itab>
endif.
cheers

How to delete the entries in internal table

Hi Experts,
I have 2 internal tables ,
if i find any same entries of 2 internal tables, i have to delete that entries in first internal table.
Regards,
Srinivasu

hi check this..
report .
data:begin of itab occurs 0,
     f1 type c ,
     f2 type i,
     end of itab .
data:begin of itab1 occurs 0,
     f1 type c ,
     end of itab1 .
     itab-f1 = 'A'.
     itab-f2 = 12.
     append itab .
     itab-f1 = 'b'.
     itab-f2 = 12.
     append itab .
     itab-f1 = 'c'.
     itab-f2 = 12.
     append itab .
     itab1-f1 = 'A'.
     append itab1 .
loop at itab1 .
read table itab with key f1 = itab1-f1 .
if sy-subrc = 0.
delete itab where f1 = itab1-f1 .
endif .
endloop.
loop at itab.
write:/ itab-f1,itab-f2.
endloop.

How to delete obsolete entries in SID table

I have an Infoobject (0PCA_ITEMNO) without master data and is used in a DSO. The sid table of the info object and its index has grown very large to about 207 gB. The DSO is periodically selectively deleted to hold the last 3 months data. How can I delete the the old and unused sid table entries to reduce the size.

Correct...you wouldn't want to delete the SID table values using custom code. This would potentially cause inconsistencies because you may inadvertently delete a SID value that is located elsewhere in your environment.
For example, if you have an InfoObject with SID value 1 for actual value of A1 and it's deleted. However, there is an InfoCube that has SID value 1 for this InfoObject in a dimension table.
To remove the values from the SID table for this InfoObject, your best bet is to use RSRV as stated before.

Urgent!!! : To delete table entries in COKA,COSP,COSB from FY2010

Similar Messages

Maybe you are looking for