Sending Process Message from PI Sheets without "Completing" it

Question

Hi,
We have long running process orders in our scenarios (typically lasting 3 days).
We are planning to use PI sheets to manage our goods issue/receipts/confirmations. During the brief evaluation of characteristics based PI sheets, we found that all the GI/GR process messages are created only when the entire PI sheet is "Completed".
Since ours is a long running process, we need that the GI/GR entered by the operator is posted immediately in the system (without waiting for PI sheet completion). We can not wait till all the data is entered and the process order is completed three days later.
How do we handle this problem?
We thought of using custom function modules. However, that will mean that we will loose the benefits of the standard GUI elements of PI sheets and complications of custom development.
Any response will be highly appreciated.
Regards,
Kundan

Answer 1

Here is something you can try.
With the browser based sheets, try putting in a signature PI category (SAP provide "SIGN") which tends to create a message and place it in the message monitor.  By scheduling the message send background job to run periodically you can pick up and send the messages.  You can schedule this job to run after the event "NEW MESSAGE" but beware the system performance - every 5 mins or so tends to be almost as good with less strain on system resources!
I tend to create a table based PI category to contain each reservation plus room to add actual goods issues/receipts.  Once these are entered, a signature category sends all the messages for the particular phase.  Thus good structure of phases is important.
For goods receipts, you may need to have a phase for each day against which to post a confirmation and/or goods receipt and this together with signature will send the messages.  Alternately, use a PI Category to call the transaction for performing goods receipt - or a bespoke transaction to "front end" the goods receipt - you can pass parameters when you call transactions so you can could pre-populate some information.
Final point on signature - you can set a simple signature that just accepts whatever the user enters on the screen - typically their initials.
Regards
Laurence