FW: Problem linking Status Management to Custom Object in EH&S

[Keohan, Susan]

Okay, well this was an oldie (but a goodie, since I am encountering this
now)...
A talented person once wrote:

'A temporary and very unofficial workaround if you really need to get on
with things while OSS get back to you: 
Check the contents of the Appropriation Request table - it contains the
two id fields used by the two objects. *IF* they have the same contents,
go to the BSVX input screen, enter IQ0/BUS2204 debug with /h, hit save
and bypass the check - not too hard to debug, it pokes around the object
definitions and data dictionary and compares the data types I think,
just change sy-subrc back to 0. It will save and work as long as both ID
fields contain the same data. Shout if you get stuck, I've done it
before (as if you couldn't tell, but with different objects) and can
find the exact spot again quite quickly if you need.'

So, while I have been able to get the linkage from my object (for
inspections) to the status object IAL, and save it, and the event even
gets triggered, the key value in here is all 0. 

Has anyone successfully (and unhackfully?) raised an event on an EH&S
object via status management ?  if so, can you please share some tips ?


-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Dart, Jocelyn
Sent: Thursday, July 08, 2004 2:33 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Problem linking Status Management to Custom Object due to
Key Field incompatibility

Hi Partha,
Sorry misunderstood you.  Check your custom object implements interface
IFSTATUS.
If you still have problems run function module
BSVW_OBTYP_BOROT_COMPATIBILITY in test mode
and see what error it is giving you between the status object type and
the business object type.
Jocelyn

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Chatterjee, Partha (US - San Ramon)
Sent: Thursday,8 July 2004 10:49 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Problem linking Status Management to Custom Object due to
Key Field incompatibility


Hi Jocelyn,

There is no SAP delivered object in this area.  Hence there is no
delegation possibilities.  IAL is an object type in the status mgmt area
but there is no related business object in SAP.

Best regards,
Partha


>Partha Chatterjee
>Enterprise Applications
>Deloitte Consulting LLP
>
>Tel: +1 650 372 4594
>Fax: +1 925 365 2170
>Mobile: +1 310 701 1119
>pchatterjee at deloitte.com
>www.deloitte.com
>
>

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Dart, Jocelyn
Sent: Wednesday, July 07, 2004 5:43 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Problem linking Status Management to Custom Object due to
Key Field incompatibility

Partha,
Is your custom object a ** delegated ** subjobject type of the IAL
object?
Use the standard object type IAL to create your event entries, and
delegation will pick up
your custom events/attributes.
Jocelyn


-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Chatterjee, Partha (US - San Ramon)
Sent: Thursday,8 July 2004 10:24 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problem linking Status Management to Custom Object due to Key
Field incompatibility



Hi All,

I am trying to use status management with EH&S to create a custom object
and workflow.  There is an object type delivered by SAP called 'IAL' for
Incident/Accident log.  In table TBO00 this object type has key fields
of CCIHT_IAL-RECN and CCIHT-ACTN.  I created my custom object with the
same key fields.

When I try to link the object type IAL with my custom object that has
the same key fields in Status Management (t-code 'BSVX') I get the error
'Status object and business object type incompatible'.  This is clearly
not true.  Any ideas on how to resolve the problem?  There are 2 related
OSS Notes 86020 and 44544 but they are for much earlier releases than
the version we are on (4.7 Enterprise).

Best regards
Partha Chatterjee



This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  If you are not the intended recipient, you should
delete this message.  Any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly
prohibited.




This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  If you are not the intended recipient, you should
delete this message.  Any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly
prohibited.