BO Attribute Issue

Rick Bakker rbakker at gmail.com
Thu Jan 16 21:43:28 EST 2014


Hi Sue,

Another idea: add a step to copy <object>.companycar to a new container
element companycar and then test that new element (instead of the object
attribute) in the condition step.

At the very least you can then be sure of what the value was at the time of
the comparison.

regards
Rick


On Fri, Jan 17, 2014 at 1:37 PM, Rick Bakker <rbakker at gmail.com> wrote:

> Hi Sue,
>
> That's a mystery to me as well - setting a default on a BOR attribute.
> What happens if you create another container element of that BOR type in
> the workflow, does its attribute have that same default value?
>
> regards
> Rick
>
>
> On Fri, Jan 17, 2014 at 12:50 PM, Sue Doughty <Sue.Doughty at odfl.com>wrote:
>
>> Hi Mark,
>>
>>
>>
>> Thanks for your response.
>>
>>
>>
>> The default value is on the object attribute.  I didn’t develop the BO,
>> so I don’t know how it got that way.  When I double click it in the
>> workflow, it won’t let me change it.  When I go to SWO1 and look at the
>> attribute, I don’t see where the default value is set.  I’ve never seen a
>> default value on an object attribute before.
>>
>>
>>
>> I haven’t tried debugging that way….our Basis team doesn’t let us mess
>> with WF-BATCH….even in DEV.
>>
>>
>>
>>
>>
>>
>>
>>   Sue Doughty
>> SAP Workflow Analyst Office: (336) 822-5189
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
>> Behalf Of *Mark Pyc
>>
>> *Sent:* Thursday, January 16, 2014 8:39 PM
>> *To:* SAP Workflow Users' Group
>> *Subject:* Re: BO Attribute Issue
>>
>>
>>
>> Have you tried setting WF-BATCH as dialog and debugging that method via
>> external break-point?
>>
>>
>>
>> Have you removed the default value on the container element?
>>
>>
>> Sent from my phone
>>
>>
>> On 17/01/2014, at 12:19 PM, Sue Doughty <Sue.Doughty at odfl.com> wrote:
>>
>> Hi Mark,
>>
>>
>>
>> I directly reference the object attribute in the condition.
>>
>>
>>
>> I decided to try just making a method instead of using the attribute and
>> executing that.
>>
>>
>>
>> When I test it in SWO1, it works correctly.
>>
>> <image001.png>
>>
>>
>>
>> But when I run it from the Workflow, it comes back with a N.
>>
>> <image002.png>
>>
>>
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> Office: (336) 822-5189
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu<sap-wug-bounces at mit.edu>]
>> *On Behalf Of *Mark Pyc
>> *Sent:* Thursday, January 16, 2014 8:08 PM
>> *To:* SAP Workflow Users' Group
>> *Cc:* SAP Workflow Users' Group
>> *Subject:* Re: BO Attribute Issue
>>
>>
>>
>> G'day Sue,
>>
>>
>>
>> The initial value is the WF container elements initial value. Nothing to
>> do with SWO1.
>>
>>
>>
>> Where do you bind the Object attribute to that container element? Do you
>> need the container element or can you just directly ref the object
>> attribute in the condition?
>>
>>
>>
>> Have fun,
>>
>> Mark
>>
>> Sent from my phone
>>
>>
>> On 17/01/2014, at 11:54 AM, Sue Doughty <Sue.Doughty at odfl.com> wrote:
>>
>> Hi Rick,
>>
>>
>>
>> I think I found it!  I looked at the data type in the attribute from the
>> workflow and it has an initial value set.  I can’t change it in the
>> workflow.
>>
>> <image006.png>
>>
>>
>>
>> But when I go to SWO1 look at it there I don’t see where to remove it, I
>> don’t see where to change it.
>>
>> <image001.png>
>>
>>
>>
>>
>>
>>
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu<sap-wug-bounces at mit.edu>]
>> *On Behalf Of *Rick Bakker
>> *Sent:* Thursday, January 16, 2014 7:39 PM
>> *To:* SAP Workflow Users' Group
>> *Subject:* Re: BO Attribute Issue
>>
>>
>>
>> Hi Sue,
>>
>>
>>
>> Thanks. What datatype is the attribute? Clutching at straws here...
>>
>>
>>
>> Often when something strange happens in workflow (which isn't often) I
>> delete the step and re-create it.
>>
>>
>>
>> regards
>>
>> Rick
>>
>>
>>
>> On Fri, Jan 17, 2014 at 11:27 AM, Sue Doughty <Sue.Doughty at odfl.com>
>> wrote:
>>
>> Hi Rick,
>>
>>
>>
>> I went ahead and put a wait for 60 seconds and it still did not work.
>>
>>
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> Office: (336) 822-5189
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> Office: (336) 822-5189
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
>> Behalf Of *Sue Doughty
>> *Sent:* Thursday, January 16, 2014 7:20 PM
>>
>>
>> *To:* SAP Workflow Users' Group
>>
>> *Subject:* RE: BO Attribute Issue
>>
>>
>>
>> Hi Rick,
>>
>>
>>
>> I thought of that too.  J  So, I put in an instantiate object method
>> right before I check that flag.  Still does not work.
>>
>>
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu<sap-wug-bounces at mit.edu>]
>> *On Behalf Of *Rick Bakker
>> *Sent:* Thursday, January 16, 2014 6:47 PM
>> *To:* SAP Workflow Users' Group
>> *Subject:* Re: BO Attribute Issue
>>
>>
>>
>> Hi Sue,
>>
>>
>>
>> Maybe the attribute hasn't been set at that point. Try putting a 1 minute
>> wait step beforehand, just to test.
>>
>>
>>
>> regards
>>
>> Rick
>>
>>
>>
>> On Fri, Jan 17, 2014 at 10:01 AM, Sue Doughty <Sue.Doughty at odfl.com>
>> wrote:
>>
>> Hi Mark,
>>
>>
>>
>> It is a custom field.  It is ‘Y’ on the ztable where the data resides.
>>
>>
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
>> Behalf Of *Mark Pyc
>> *Sent:* Thursday, January 16, 2014 5:53 PM
>>
>>
>> *To:* SAP Workflow Users' Group
>> *Subject:* Re: BO Attribute Issue
>>
>>
>>
>> G'day Sue,
>>
>>
>>
>> Is that field a custom field or a standard SAP one? Does it have input
>> conversion routines on the Domain where 'Y' might actually be 'J' on the
>> database??
>>
>>
>>
>> Have fun,
>>
>> Mark
>>
>>
>>
>>
>>
>> On 17 January 2014 09:39, Sue Doughty <Sue.Doughty at odfl.com> wrote:
>>
>> Hi Rick,
>>
>>
>>
>> Yes.
>>
>>
>>
>> <image007.png>
>>
>>
>>
>> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
>> Behalf Of *Rick Bakker
>> *Sent:* Thursday, January 16, 2014 5:31 PM
>> *To:* SAP Workflow Users' Group
>> *Subject:* Re: BO Attribute Issue
>>
>>
>>
>> Hi Sue,
>>
>>
>>
>> I have to ask: does False lead to "No"?
>>
>>
>>
>> regards
>>
>> Rick
>>
>>
>>
>> On Fri, Jan 17, 2014 at 9:18 AM, Sue Doughty <Sue.Doughty at odfl.com>
>> wrote:
>>
>> Hello,
>>
>>
>>
>> I am at my wit’s end….which isn’t difficult to do.  J  I have working on
>> this all day…..it has to be something simple, but I cannot find it.  Any
>> help would be greatly appreciated.
>>
>>
>>
>> I have a new workflow (we are on Release 731) ECC 6.0.  The BO (ZLCCLAIM)
>> has an attribute called Company Car and it will be Y or N.
>>
>>
>>
>> When I trigger the event, the event shows it as Y
>>
>> <image008.png>
>>
>>
>>
>> In the workflow that gets triggered, the attribute still shows as Y
>>
>> <image009.png>
>>
>>
>>
>> But when it hits the condition in the workflow to check if
>> &ZLCCLAIM.COMPANYCAR& = Y, it fails
>>
>>
>>
>> <image010.png>
>>
>>
>>
>> Here is the condition in the workflow.
>>
>> <image011.png>
>>
>>
>>
>> What am I missing?
>>
>>
>>
>>
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> <http://www.odfl.com>
>>
>> Office: (336) 822-5189
>> Email: Sue.Doughty at odfl.com
>>
>> Helping the World Keep Promises.®
>>
>> Old Dominion Freight Line, Inc.
>> 500 Old Dominion Way
>> Thomasville, NC 27360
>> www.odfl.com
>>
>> <http://www.facebook.com/OldDominionFreightLine>
>>
>> <http://twitter.com/ODFL_Inc>
>>
>> <http://www.youtube.com/ODFLInc>
>>
>> <http://www.linkedin.com/company/old-dominion-freight-line>
>>
>> CONFIDENTIALITY NOTICE: The information contained in this message may be
>> confidential, privileged, proprietary, or otherwise legally exempt from
>> disclosure. If the reader of this message is not the intended recipient, or
>> an employee or agent responsible for delivering this message to the
>> intended recipient, you are hereby notified that you are not authorized to
>> read, print, retain, copy or disseminate this message, any part of it, or
>> any attachments. If you have received this message in error, please delete
>> this message and any attachments from your system without reading the
>> content and notify the sender immediately of the inadvertent transmission.
>> Thank you for your cooperation.
>>
>>
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> Office: (336) 822-5189
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> Office: (336) 822-5189
>>
>>
>>
>> *Sue Doughty*
>> SAP Workflow Analyst
>>
>> Office: (336) 822-5189
>>
>>  _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140117/85646997/attachment-0001.htm


More information about the SAP-WUG mailing list