BI_PERSISTENT~FIND_BY_LPOR and LPOR-INSTID is blank

[Dart, Jocelyn]

Hi Sue, 
Yes read the whitepaper again - you populate the field in the
CONSTRUCTOR method based on your key,  
and you have to fill in the relevant code in both the LPOR and
FIND_BY_LPOR methods to complete 
the information. 

If your key is longer than 32 characters you should generate a GUID
using fm GUID_CREATE
and then hold the relationship between the GUID and your key in a table
somewhere. 
 


Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 


-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
Of Susan R. Keohan
Sent: Saturday, 04 February 2006 2:22 AM
To: SAP Workflow Users' Group
Subject: BI_PERSISTENT~FIND_BY_LPOR and LPOR-INSTID is blank

System: SRM 5.0 Ramp-up, WAS 7.0

Issue: BI_PERSISTENT~FIND_BY_LPOR and LPOR-INSTID is blank.

Class: CL_SWF_FORMABSENC

We are trying to get an understanding of BI_PERSISTENT~FIND_BY_LPOR.
>From the white paper from 
Jocelyn Dart, "the LPOR-INSTID field contains all attributes marked as
'Key' fields".

When testing the class
1)    I create an instance using a key found in table SWXFORMABS.
2)    Under Interfaces, I choose BI_PERSISTENT
3)    Under Methods, I execute FIND_BY_LPOR
4)    Then I click the Execute Debugging Icon
5)    When I check the value of LPOR, it is blank.  The CHECK statement
causes the code to be 
skipped and the object instance is not created.

How should LPOR be populated?

Many thanks,
Sue

-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug