Parallel table maintenance..

[Becker Stephan (extern)]

..slightly off topic, but I have received a request for custom tables =
used
in a workflow to be maintained in parallel by several users, albeit for
separate parts of the table; i.e. the person responsible for plant 1
maintains records with key plant 1, and another person maintains the =
records
in the same table for plant 2 at the same time.
 
My guess is that there is a solution out there somewhere, and no need =
to
reinvent the wheel. Any pointers would be greatly appreciated. I have =
looked
at the event mechanism with which one can override certain parts of the
generated table maintenance, but the enqueue/dequeue function is
unfortunately not one of them, and will always lock the whole table or
view..
 
Thanks in advance,
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Kjetil Kilhavn [mailto:kjetilk at statoil.com]
Gesendet: Dienstag, 6. August 2002 07:28
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Object Method Usage
 
 
Well, there is always the "easy" way of making a subtype and changing =
the
method from dialog to background. If you have some nice function =
modules to
call which do their tricks nicely you shouldn't have a problem. =
However,
all kinds of problems _may_ occur.
 
I tried to make a background method to release a LIV invoice with =
payment
blocking (no, I still haven't completely solved the good old case I =
asked
about here a while ago) due to amount limits on invoices without =
reference
to purchase orders. This is necessary as none of the BUS2081 methods =
will
release these invoices. The method used batch input to start MRBR, =
enter
the required data and release the blocked invoice. No-go since SAP uses
Fancy Tables (FT (tm)) in the implementation of MRBR. The reason is =
that
for these tables you can not address rows etc in the way you could with
"old-style" tables.
 
After a while (depressing, but true, it took quite a while) I realized =
that
I could use the "Select all" button since I would only have one row (as =
I
specified the invoice number). That should do the trick, right? Not at =
all,
SAP developers have ensured that life will be a pain no matter what you
try. So in the end I had to make it a dialog method, and thus someone =
has
to execute that step. All they do is execute, and it is gone without =
the
executing agent seing anything happening.
 
You have been warned :-)
--
Kjetil Kilhavn
 
 
 
 
 
 
                    "Nobles, Diane"
                    <nobles_dh at naptheon.        To:
SAP-WUG at MITVMA.MIT.EDU
                    com>                        cc:     (bcc: Kjetil
Kilhavn)
                    Sent by: SAP                Subject:     Object =
Method
Usage
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    05.08.2002 18:26
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
Good afternoon all.  We want to use an object type method to create a =
SAP
record.  We want to call the method in the background and create the =
record
without user intervention.  The current method we want to use is a =
dialog
method.  Does anyone know of a way to change a method from a dialog to
allow
use of method in background or is this an impossibility.  There is a
CreatefromData method, but apparently it does not provide the same =
screen
sequence.  Has anyone else ran into this problem and if so what was the
solution???  Thanks in advance for any help or suggestions in this =
matter.
 
Diane H. Nobles
Northrup Grumman-Naptheon
SDE PM Team
(757) 380-7250
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of =
the
information or copying of this message is prohibited. If you are not =
the
addressee, please notify the sender immediately by return e-mail and =
delete
this message.
Thank you.