-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- Re: need of commit work statement
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
need of commit work statement
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2016 Jun 08 8:01 AM
- SAP Managed Tags
- ABAP Development
Hi everyone,
Can you please guide me know when we need to use Commit work statement in SAP-ABAP, and when can we avoid Commit work statement.
Thanks & regards,
Shravan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2016 Jun 08 8:38 AM
- SAP Managed Tags
- ABAP Development
From the Keyword Documentation:
The COMMIT WORK statement closes the current SAP LUW and opens a new oneThis is very important if you have Situations where multiple datasets have to be modified. If one of the modifications fail, you want to do a ROLLBACK.
But If you made other changes to the database those would be rolled back as well. So COMMIT WORK is basically just doing what the Documentation says:
- Closing the current SAP LUW
- Opening a new SAP LUW
This helps you to keep databse changes that have to be executed together to be in line even when there is a lock on the table or techical issues appear.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2016 Jun 08 8:05 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2016 Jun 08 8:38 AM
- SAP Managed Tags
- ABAP Development
From the Keyword Documentation:
The COMMIT WORK statement closes the current SAP LUW and opens a new oneThis is very important if you have Situations where multiple datasets have to be modified. If one of the modifications fail, you want to do a ROLLBACK.
But If you made other changes to the database those would be rolled back as well. So COMMIT WORK is basically just doing what the Documentation says:
- Closing the current SAP LUW
- Opening a new SAP LUW
This helps you to keep databse changes that have to be executed together to be in line even when there is a lock on the table or techical issues appear.
Bluesky