In this case, the client field is treated like a normal field to which you can assign a value in the work area. Effect Inserts new lines or updates existing lines in a database table s. Normally, records are inserted or updated only in the current client.
Data can only be inserted or updated using a view, if the view refers to a single table and was created in the ABAP Dictionary with the maintenance status "No restriction". Every effort is made to ensure the content integrity. Information used on this site is at your own risk. All product names are trademarks of their respective companies.
Learn more. Asked 8 years, 3 months ago. Active 2 months ago. Viewed 43k times. Improve this question. Madalina Taina 4, 4 4 gold badges 17 17 silver badges 47 47 bronze badges. I prefer New for creation, and Edit paired with Save for modification. New Group. Remove can be removal from a list while not deleting the item itself.
I'd never use delete for "just" removing something from a list, but I'd use delete if the intention is to delete the item and removal from the list is a "side effect" of that deletion. Add a comment. Active Oldest Votes. What's best calling these things depends on: Who is using the system; what is the nature of the action really being performed; what other actions may be performed.
Everyday Language You can argue that people will agree on these definitions: You create something from scratch.
Like create a new report. By modifying something you change its properties. Like modifying a design. My Recommendations Prefer Add over Create unless there's a clear create-then-add mechanism. Although technically and as you said create means it never existed before, while programmers think about 'records' users think about the abstraction these stand for.
While for you adding a person's record makes perfect sense, 'creating a person' or 'creating a task' is less intuitive than 'adding a person' to the system or 'adding a task' to the task list. Obviously, if your users are IT professionals and fluent with what a database and records are, prefer create over add. If persistance is involved, prefer update over change. Having said that, users are accustomed to 'save changes'. Don't use modify. Prefer Remove for non-permanent removal, and Delete for permanent removal.
Improve this answer. Izhaki Izhaki Very nice write up of the nuances involved. Nice breakdown. A good sign of a complete and thorough answer is that there are no other answers. Thank you for this answer. I know it is a high level description, but we obviously need some precision when naming class methods at the source code level to keep the mess self documenting.
This is a better run down of these operational descriptions than anything else I found. I can Show 1 more comment. My recommendation: Add to a list Remove from a list Create a new entity Non-permanently hide or archive an entity Permanently delete an entity Irreversibly shred or obliterate an entity Update , modify , or edit an entity or value Update , modify , edit , or change a value Read or view an entity or value. Solomon Ucko Solomon Ucko 1, 7 7 silver badges 13 13 bronze badges.
Sign up or log in Sign up using Google.
0コメント