SOLUTION: Error OL 826 - change status of PDOTYPES subtype

[Wim Hilven]

of the B.O are specified wrongly...
If forgot that within the subtypes of PDOTYPES you need to specify the plan
variant as part of the objectkey when you create an event...
 
Thanks anyway Viveka and Heinz...
 
Kind Regards / Vriendelijke groeten / Amicalement,
 
Wim Hilven
 
 
 
-----Original Message-----
From: Viveka Schwartz [mailto:viveka.schwartz at implema.se]
Sent: 06 March 2003 11:11
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Error OL 826 - change status of PDOTYPES subtype
 
 
Hello Wim,
I've received this error once (after transport). Check the subtype for
syntax error and regenerate it. Have you tried to debug the method to
verify that the FM is called properly ?
Best regards
Viveka
 
 
 
 
 
Wim Hilven <wim.hilven at belgacom.be>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
2003-03-05 17:44
Please respond to SAP Workflow Users' Group
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Error OL 826 - change status of PDOTYPES subtype
 
 
Does this error code ring a bell for you?
It states that the object does not exist... but I can't seem to figure out
why???
 
Situation: I am trying to call a self made method (change status) which
calls a function module (RH_OBJECT_STATUS_CHANGE) in my self made subtype
of
PDOTYPES.
 
 
 
Kind Regards / Vriendelijke groeten / Amicalement,
 
Wim Hilven
 
 
 
**** DISCLAIMER ****
"This e-mail and any attachments thereto may contain information
which is confidential and/or protected by intellectual property
rights and are intended for the sole use of the recipient(s) named above.
Any use of the information contained herein (including, but not limited
to,
total or partial reproduction, communication or distribution in any form)
by persons other than the designated recipient(s) is prohibited.
If you have received this e-mail in error, please notify the sender either
by telephone or by e-mail and delete the material from any computer.
Thank you for your cooperation."
 
**** DISCLAIMER ****
"This e-mail and any attachments thereto may contain information
which is confidential and/or protected by intellectual property
rights and are intended for the sole use of the recipient(s) named above.
Any use of the information contained herein (including, but not limited to,
total or partial reproduction, communication or distribution in any form)
by persons other than the designated recipient(s) is prohibited.
If you have received this e-mail in error, please notify the sender either
by telephone or by e-mail and delete the material from any computer.
Thank you for your cooperation."