Systems and methods providing a soft exit state for secondary business objects locks

1. A method implemented by a computing system in response to execution of program code by a processor of the computing system, the method comprising:

establishing, in a storage device in communication with the processor, a primary business object along with a plurality of secondary business objects that depend from the primary business object in a hierarchy;

placing, by the primary business object under control of the processor, a lock on a secondary business object and facilitating an update of data associated with the secondary business object;

detecting, by the secondary business object under control of the processor, that a database commit has been executed; and

responsive to said detecting, removing, by the secondary business object, the lock associated with the secondary business object.

2. The method of claim 1 , further comprising:

determining, by the primary business object, that the secondary business object is to be associated with a soft exit state, wherein the secondary business object is only to remove the lock, responsive to said detecting, when in the soft exit state.

3. The method of claim 1 , further comprising:

determining, by the primary business object, that an additional business object of the secondary business objects is to be associated with a hard lock;

placing, by the primary business object, a hard lock on the additional secondary business object and facilitating an update of data associated with the additional secondary business object;

executing, by the primary business object, a database commit; and

removing, by the primary business object, the lock associated with the additional secondary business object.

4. The method of claim 1 , wherein the database commit is associated with a copying of information from a server memory to a storage device.

5. The method of claim 4 , wherein the update of data associated with the secondary business object and the database commit are associated with a single business process change transaction.

6. The method of claim 1 , wherein the hierarchy is associated with line items between the primary business object and the secondary business objects.

7. The method of claim 1 , wherein a single secondary business object may be associated with several primary business objects.

8. A non-transitory, computer-readable medium storing program code executable by a computer to perform a method, said method comprising:

establishing a primary business object along with a plurality of secondary business objects that depend from the primary business object in a hierarchy;

placing, by the primary business object, a lock on a secondary business object and facilitating an update of data associated with the secondary business object;

detecting, by the secondary business object, that a database commit has been executed; and

responsive to said detecting, removing, by the secondary business object, the lock associated with the secondary business object.

9. The medium of claim 8 , wherein the method further comprises:

determining, by the primary business object, that the secondary business object is to be associated with a soft exit state, wherein the secondary business object is only to remove the lock, responsive to said detecting, when in the soft exit state.

10. The medium of claim 8 , wherein the method further comprises:

determining, by the primary business object, that an additional business object of the secondary business objects is to be associated with a hard lock;

placing, by the primary business object, a hard lock on the additional secondary business object and facilitating an update of data associated with the additional secondary business object;

executing, by the primary business object, a database commit; and

removing, by the primary business object, the lock associated with the additional secondary business object.

11. The medium of claim 8 , wherein the database commit is associated with a copying of information from a server memory to a storage device.

12. The medium of claim 11 , wherein the update of data associated with the secondary business object and the database commit are associated with a single business process change transaction.

13. The medium of claim 8 , wherein the hierarchy is associated with line items between the primary business object and the secondary business objects.

14. The medium of claim 8 , wherein a single secondary business object may be associated with several primary business objects.

15. A system, comprising:

a server memory unit;

a storage device; and

a server processor coupled to the server memory unit and to the storage device, wherein the server processor is to:

establish a primary business object along with a plurality of secondary business objects that depend from the primary business object in a hierarchy;

place, by the primary business object, a lock on a secondary business object and facilitate an update of data associated with the secondary business object;

detect, by the secondary business object, that a database commit has been executed; and

responsive to said detecting, remove, by the secondary business object, the lock associated with the secondary business object.

16. The system of claim 15 , wherein the server processor is further to:

determine, by the primary business object, that the secondary business object is to be associated with a soft exit state, wherein the secondary business object is only to remove the lock, responsive to said detecting, when in the soft exit state.

17. The system of claim 15 , wherein the server processor is further to:

determine, by the primary business object, that an additional business object of the secondary business objects is to be associated with a hard lock;

place, by the primary business object, a hard lock on the additional secondary business object and facilitate an update of data associated with the additional secondary business object;

execute, by the primary business object, a database commit; and

remove, by the primary business object, the lock associated with the secondary business object.

18. The system of claim 15 , wherein the database commit is associated with a copying of information from the server memory unit to the storage device.

19. The system of claim 18 , wherein the update of data associated with the secondary business object and the database commit are associated with a single business process change transaction.

20. The system of claim 15 , wherein the hierarchy is associated with line items between the primary business object and the secondary business objects.

21. The system of claim 15 , wherein a single secondary business object may be associated with several primary business objects.