How many implementations out there.........
Are developed without the benefit of Lock Objects ?
Judging by the type of questions being asked in the ABAP developers forums can it be inferred that if people ask how to program in ABAP that they do not know anything about programming in multi-user systems ??
<shudders>
Rich
10 Comments
-
Jun 08, 2017 at 08:42 AM
Locking belongs in the same category as authorisations: Optional fluff. Doesn't add to the functionality, it works on DEV with or without, so why should we care?
-
Jun 08, 2017 at 10:00 AM
Not really important then ?
-
Jun 08, 2017 at 10:24 AM
No, as long as it works in dev and QA it's on time and on budget.
How else are we supposed to offload escalating project costs if not onto a support budget?
-
Jun 08, 2017 at 12:11 PM
True... True
-
-
-
-
Jun 08, 2017 at 03:54 PM
Ran into this previously quite a bit in the MM/WM arena. SI did not care to use and it worked wonderfully in dev and q but those systems did not nearly approximate the volume of concurrent users.
-
Jun 12, 2017 at 05:30 PM
You mean two users testing in sequence is not enough? It proves that multiple users can use the system.
-
-
Jun 08, 2017 at 04:06 PM
Let's perform all development directly in Prod :)
-
Jun 08, 2017 at 05:05 PM
You don't?
-
Jun 09, 2017 at 09:45 AM
It is the perfect test environment with lots of current data
-
Jun 09, 2017 at 02:25 PM
Ah yes, the good old' Call <FM> Destination via Local Workflow RFC. *sips coffee*
-
