FM to delete characteristics DMS

Hi Folks,
I need to delete a few characteristics (classification) of a DMS document (CV02N). Can anybody please suggest any FM or BAPI for this?
Thanks
Sagar

Hello,
I saw your message and I have a question, could you be so kind you could help me.
I am using bapi BAPI_DOCUMENT_CHANGE2 to delete characteristics values in a DMS document and I am having alot of trouble.
did you manage to make it work?
Thanks in advance,
Catarina

Similar Messages

Original Document is deleted from DMS

Dear Team,
Document (Excel file) was initially attached in DMS against WBS.
The document in DMS is opened for editing and Data was saved in the excel and subsequently when the application is closed the following message appears.
In this screen when we press u201CNou201D and then press u201CSaveu201D button u2013 the following error happens
1. Original file is deleted in the physical location.
2. Document stored in the DMS system also gets deleted.
Regards,
Rajan

Dear Pradeep,
By Using the T-Code CV02N, we are not filling any details in the Change document scree, which asks for "Data Carrier" & "Original "
Subsequently the relevant file is opened in the application (excel), we are doing the change and saving the file,
"Change in Original " Dialogbox appears, with Original is changed - Do you want to save the original with "Yes" & "No".
When we press "No", and press teh "Save" option (in SAP Screen), An error message appears in status bar,
Original file is deleted in the physical location C:\Documents and Settings\raghavan_s\Desktop\Vestas-Supply.xls
And we try to access the by thru CV04N,
Error appears in status bar,
File C:\Documents and Settings\raghavan_s\Desktop\Vestas-Supply.xls could not be accessed
Regards,
Rajan

Hide or delete Characteristics? how to, please help

Hi there,
I have an ODS with 400 Char - they are options on a part. For each option there is only a value of Y or N.
When I run a query I want to hide or delete all characteristics that are equal to N (I don't want to show the characteristic or the value so really want to hide or delete the row).
Is there a way of doing this in BEX?
Should I do this in data load and delete all Char equal to N, if so what would be the code?
Have tried to filter and restrict etc but that is not going to work
Am struggling to find a solution
Any help would be much appreciated
Thanks
helen

Hi Olivier,
Thanks again for you help.
Yes - I think to delete in start routine is the best way to go.
Tried your code but it deleted whole row I only want to delete the N's from the InfoObject.
I have a primary key Works Order
Source: Flat File
EG
W/O    Rad     AVR PVR   A1   A2
123      Y        N       N      N     N
456      N       Y        N      Y     N
When I produce query (source: ODS) it is displayed as
Selection W/O - 123
Rad   Y
AVR N
PVR N
A1     N
A2     H
So for W/O 123 I would only want to see Rad in the query, only values equal to Y
I don't mind putting code in the start routine but am unsure what the code should be.
I tried to use exclude in the query but it is not working
Any extra help would be much appreciated!
Many Thanks
Helen

Auto population of characteristics-DMS

Hi Friends,
I have a requirement to auto populate the characteristics in additional tab of cv01n whenever the document is created .This has to be done before saving the document.The values are to be populated when the attional tab comes up , the values are to be populated from a custom table based on the sapid , so that user may also have the option of changing the default values before saving .Kindly help.
Thanks and Regards,
Pratap.

HI Maria,
You are correct as this exit triggers when saving the document but we need to see the populated data in additional b tab so that user can have the option to change the autopopulated characteristics.
Can you plz suggest a way to autopopulate the values in the additonal B tab when clicked on cv01n .
Thanks and Regards,
Kanti

Document delete BAPI in DMS

Hi,
Could you please let me know BAPI for document's contents deletion in DMS
Thanks
Moderator message: please (re)search yourself before asking.
Edited by: Thomas Zloch on Jul 12, 2010 2:55 PM

Hi,
I thought you want to delete the document.... OK..
If you want to delete the originals, please check the below link(answers given by me)
[Re: Search for a function module for deleting document originals (DMS)]

Delete COPA characteristics which not used in any operating concern

Hello SAP experts,
Please advise me on how to delete PA characteristic "WW001" created by mistake that we are hoping to delete if possible. However, when attempting to delete in KEA5, the error log appear as
Data element RKEG_WW001 is used in these table/view
CACS_S_COND_MA
JVKOMP
KOMG
KOMGF
KOMGFNEW
KOMGFOLD
KOMP
KOMPAKE
STR_KOMG
TRCON_IT_KOMP
WB2_EKOMP
And does not allow the deletion
WW001 have already been delete from the operating concerns.
Please shed some light on how to do this?
Thanks in advance for your help
Yang

Hi,
In order to delete a characteristic you should perform
the following activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
It is not possible to transport information about 'deleting of
characteristics (value fields)' with transaction KE3I. Only
characteristics and value fields included in operating concern (to be
transported) are transported with KE3I. Deleted characteristics and
value fields are ignored. You have to delete these characteristics and
value fields manually in each system.
Best regards,
Maria Luisa

Since CT04 is hanging, how to delete a characteristics ?

Hello to you all,
I have a query. CT04 has some performance problems and the characteristics which has been created can not be changed or deleted. This characteristics does not have any allocations to classes or etc.
Is there a program which can be taken to delete it?
Thanks in advance.
Esra

Hallo Jürgen,
I already opened a message at SAP which recommended a lot of updates which my company doesn`t want to do it in the near future.
Generally I don`t want to go for deletion of any tables. Like you said, I would create some inconsistent data.
I searched a little and found out two programs which can delete characteristics.
CL6K RMCLMDEL Delete Characteristic (Class w. Obj
CL6M RMCLKDEL Delete Class (with Assignments)
I also read that it is possible to delete characteristics directlyl from class if there is no value in the characteristics. Does anyone know if it is possible to allocate a characteristics to a class and delete it in there afterwards?
Regards,
Esra

How to delete the rule in transformation

Hi all ,
I have remodeled the info-cube and added one characteristics ZRMACTTRS. This characteristics got updated in transformation rule..Now i want to delete it from transformation but i am unable to do so ..
I tried deleting the rule and message was populated "one rule is successfully deleted " but yet it is not removed from transformation structure (this rule has a key,can i remove key from rule ?).
I have tried to remove the characteristics through remodeling but delete characteristics request is not getting active...
Please help

yoiu can try by putting the rule to 'initial' (in rule details)...ignore the subsequent warning and delete the arrow with a right-click. Then activate your rule again...maybe this will work.
M.

How to change the characteristics of a Batch

Dear All,
We have maintained a batch sort sequence based on Batch Manufacturing date.
But now customer wants the batch to be sorted out based on Batch Number.
How to change the Characteristics from Batch Manufacturing date and Batch Number?
Please do suggest.
For example, we have two characteristics assigned to the Class One is Manufacturing date and another is Batch Number.
How system will sort out a batch based on these two logic.
Kindly explain.
Regards,
Mullairaja

Hi Mullai,
I hope you know what do you mean by "Dependencies" in variant configuration. These are created for automatic update of characteristic values. If you want to delete the characteristic from the class, please do teh following.
1. Find out that there are any dependencies assigned to this characteristic. If so remove the assignment
2. Then you have to check if this characteristic is used in any dependency in the code. If so, find the implications of the same.
In case, you dont know what is dependency, may be they are not used in your project. In this case, you can just remove the characteristic from the class.
It has got one effect.
At present, a configured batch will have this characteristic. If you go to the batch master in change mode, then the old classification will be replaced by the new classification. So the deleted characteristics will not be available to you anymore. I hope that is fine with you. If this is fine, then you dont need to worry about removing the characteristic from the class.

Delete Button in Class

Hello All,
I am unable to delete characteristics from a class as the delete button has got disabled. The problem I guess is due to usage of change number. Once I go to the class after giving the change number, I see that the delete button has got disabled.
Can somebody throw some light on how to come out of this issue?
PS:
I want to archive the change master records too!!!
Thanks and Regards
Adithya

Hi Adithya,
you can undo (revert) all changes related to a change number with CCUNDO transaction.
See docs:
Undoing of Changes - Engineering Change Management (LO-ECH) - SAP Library
You have to give the change number and it will delete all modifications which are related to that. You also have a simulation mode I propose to simulate it before undoing.
Best regards
Tamas

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

DMS Document relationship with company code

Hi All,
I have to delete all DMS Documents for Document Type AAA and company code 8200. I am not able to find relationship between Document info records and company code in table level so can you please guide me How to get the relationship.
I checked with tables : DRAW, DRAD, AUSP... but not got proper answer.
-Thanks,
Ajay

Hi All,
Thanks for your replay. This issue is resolved.
In transaction CV04N with classification tab I have to option of Company code. I am able to get list of DIR's with company code and document type.
-Thanks,
Ajay

Hiding characteristics in the BEx reporting

My query is Hiding characteristics in the BEx reporting.
I want to see only query title, variable and result.
I want Hide or delete characteristics ( which are free characteristics and rows in Design mode of query) at query level.
can I do this ?

Ok. I was thinking you were in 7.0.
anyway, in your query remove all the characteristics in your rows and the query will show only the result then. (no drill-down)
For technical name and variable info. in analyzer, go to Layout and choose Display text elements.

Deleting derivation rule for the existing characteristic in operating conce

Hi all
My customer has two characteristics" Billing Doc(VBELN)" and" Warranty status" in the development and testing client and not in the production now.
Option 1 : Is to delete them but as the data is already posted for the same in the test and development client,it is lot more complex( involves implementation of OSS notes-SAPNET note 21207) .
Option 2: If we decide to keep them for now:These two have a derivation rules too. So can we simply delete the derivation rules so that data will not get posted to them( So will not effect the PSG i.e ce4xxxx table in production once the same transport is moved to production). There are no dependencies on this derivation rule.
Option 3: Can we also remove them from segment level characteristics?
Please let me know pros and cons ?
I really appreciate your time and effort.
Thanks & Regards
Sri

Hi,
If the characteristics have not been transported to production then why don't you delete them in the dev/test system ? Here you can take the risk.
To delete characteristics or value fields, perform the following
activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings (TA KECM).
You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
regards
Waman

Disable characteristics used in a VC class

Dear Gurus,
We have a general VC class - time period class with type 300. It has be used and shared among several type of materials. Among about 10 characteristics, there are two unhidden characteristics named "start date" and "end date" with the description "Start Date" and "End Date".
Now user would like give a more meaningful display name for different type materials. For example
For consultant materials: the describe name will be
   Consulting Service Start Date
   Consulting Service End Date
For training materials: the describe name will be
     Redemption Start Date
     Redemption End Date
We are thinking to use specific classes to replace this shared class to solve this problem. It is also benefit for us to flexibly to add characteristic in a separated class without thinking side effect on other types of materials.
I did some investigations:
1. We can't delete characteristics once it is used in a sales order.
2. We tried to lock the shared class and assigned a new specific class with new characteristics to the configuration profile. However, the visible characteristics in the locked class still show up when I try to create a sales order.
3. We tried to lock the old configuration profile and assign a new configuration profile with new class to the material masters. However, the visible characteristics of the class assigned to the locked configuration profile still show up when I try to create a sales order.
So far, my bottom line is :
create all specific classes to replace this shared class. Change all visible characteristics as "Not Display" and "Not for Input".
I'm a newer to the VC area. So I wander
1. Is my bottom line doable?
2. Is there a better solution to meet our user's requirement?
Regards,
Thanks in advance!
Yan Lin

Hi Nick,
          Free characteristics are used for the navigations or drill down so when you execute your query they will not be present in the initial display of the query in BEx Analyzer.The initial display contains objects from Rows and Columns.Later you can drag free char from the filter and Navigation Pane which is on LHS of your query result.
                  You can drag and drop on the fields in display of the report to further expand the query output.
     So from LHS of the query output you could come to know what all free char are used in while designing the query in Query Designer
Regards,
Varun

FM to delete characteristics DMS

Similar Messages

Maybe you are looking for