cancel
Showing results for 
Search instead for 
Did you mean: 

Start conditions not copied when copying the standard WF

Former Member
0 Kudos

Hi

I have to copy the standard WF WS10400002 into a custom one having same start conditions

but only with an additional step.

but the start conditions are not copied on doing so.

and when trying to create the start conditions similar to the original one

i dont find the container element Gross Amount(USD) in the copied one

How can i resolve my issue , what else do i need to take care when copying the standard WF.

Please suggest.

Thanks in advance

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member193382
Active Contributor
0 Kudos

hi Kittu,

Try giving the start conditions for your workflow using the tcode SWB_COND.

Regards,

Raj

Former Member
0 Kudos

Hi Raj

Thanks for the answer

but even tcode swb_cond doesnt help

The container gross amount still cant be seeninthe container elements

Please suggest

Former Member
0 Kudos

Any Suggestions?

former_member193382
Active Contributor
0 Kudos

Hi kittu,

create a custom attribute in your BO and then use this attribute in a check condition step. If condition is

true then let the workflow proceed and if false use a process control step and complete workflow.

Regards,

Raj

former_member185167
Active Contributor
0 Kudos

Hello,

Where does Gross Amount come from? Is it an attribute of the BOR object associated with the workflow? If so, it should be available in the copied workflow - assuming you didn't change the object.

Are both the copy and the original using the same object?

regards

Rick Bakker

Hanabi Technology

Former Member
0 Kudos

Thank you Rick Bakker

I am not sure from where this Gross Amount (USD) has come from.

the copied WF is also using the same BO.

but still i dont see the contaer Gross AMount(USD) .

This container elment should be visible to me when creating the start conditions for the original WF.

Please suggest .

former_member193382
Active Contributor
0 Kudos

Hi Kittu,

As i said earlier, check in which table the gross amount is stored for the particular document? Then create a database attribute for with reference table and field name as the table and field name where the gross amount is stored. Then save and generate BO. Try testing the BO and check if the value is populated in the attribute. IF it works the use this attribute in a check condition step after the event gets triggered and divert the workflow as per the requirement.

Let me know if you have any queries.

Regards,

Raj

Former Member
0 Kudos

Please check whether the Business Object that you have created is delegated to the standard. If you are using standard BO check whether the respective element exist in the attribute section of the BO

Former Member
0 Kudos

Yes it is delegated but i dont see that attribute in the standard BO too.

I just see that container(Gross Amount(USD)) when viewing the start conditions of the standrd WF WS10400002.

Please suggest

Former Member
0 Kudos

hi Raj

Thank you for the answer

I m first looking out for simpler solution,would try this and get back to you ASAP.

Thanks once again.

former_member193382
Active Contributor
0 Kudos

Hi Kittu,

can you give me the BO name you are using so that i can diagnose the std workflow and get back to you. I am not able to find WS10400002.

Regards,

Raj

Former Member
0 Kudos

Hi Raj

The BO name is BUS2203,WS10400002

This is in SRM system.

Former Member
0 Kudos

Hi Raj

Any suggestions please?

former_member193382
Active Contributor
0 Kudos

Hi Kittu,

Sorry, but i dont have access to any SRM system. Check if BO BUS2203 has any attribute for gross amount or try creating your own attribute. Let me know if you face any problem in this. This is easy and fast solution.

Regards,

Raj

Former Member
0 Kudos

Original WF is using BUS2203.

1.we have Gross amount and also Gross amount(USD) in the container variables of start conditions

2.but we have only Gross amount in the attributes of BUS2203 with out (USD) tag.

Copy WF is using BUS2203

1..Gross amount(USD) is not there in the container elements

2.but we have only Gross amount in the attributes of BUS2203 and also start conditions with out (USD) tag.

so do you still recmmend me to create a new attribute.

If so then i need to create a sub type Zbus2203 and create the new attribute.

Please suggest

Former Member
0 Kudos

I think this start condition was created when the standard BO was delegated to custom BO which had the gross amount(USD) attribute created in it. You can just deactivate this condition or delete it and create your own.

Thanks

Arghadip

Former Member
0 Kudos

Hi Arghadip

The start condition Gross amount(USD) is in the standard WF(using std BO BUS2203) but not in the custom WF

former_member193382
Active Contributor
0 Kudos

Hi Kittu,

Can you tell me what start condition is defined in std wf?

Also can make it clear whether the BO BUS2203 has any attribute labeled gross amount?

Regards,

Raj

Former Member
0 Kudos

Hi Kittu,

You can create this field in the delegated BO and implement the same in the custom workflow in the start conditions.

Regards,

Kanika

Former Member
0 Kudos

Hi Raj

The start condition defined in the std WF is

Gross amount(USD) < 9,999.00

and the in the container varaibles that i can see while defining the start conditions there are two varaibles for gross amount

they are

->EC Confirmation goods

->Gross amount Gross Confirmation Amount in Document Currency

->Gross amount(USD) Gross Confirmation Amount in Document Currency (Currency:USD).

and the BO BUS2203 has only Gross amount in the below format

ProcConfirmationEC.GrossAmount Gross Confirmation Amount in Document Currency

The std BO doesnt have Gross amount(USD)

Copied WF

In the container variables i can see only

->EC Confirmation goods

->Gross amount Gross Confirmation Amount in Document Currency

So i dont have the variable Gross amount(USD) to use it as in the std WF.

Please suggest.

former_member193382
Active Contributor
0 Kudos

Hi Kittu,

What i understand is some of the container elements are missing that are available in the std workflow.

You can create your own workflow container/ task container and do the binding as in std workflow.

create your own workflow containers and use the data element similar that in std workflow. In case if you need to create a task container, copy the std task that are used in the workflow you just copied using pftc tcode and then create the task container as per the requirement. Then use this task in place of std task in your workflow and do the binding as in std workflow/ as per your requirement.

Correct me if i just went out of track.

Let me know if you have any queries.

Regards,

Raj

Former Member
0 Kudos

This Gross amount(USD) seems to have been populated even before the WF is started

that is why there is a start condition mentioning its limitation

Gross amount(USD) < 9,999

So does adding this as a WF container solve our issue.

Or do i need to add this a BO attribute and try out?

former_member193382
Active Contributor
0 Kudos

Yes,

You need to create a attribute to solve this problem.

Regards,

Raj

Former Member
0 Kudos

Start Condition does not get created automatically. Please note that the Start condition is always created customwise. I checked in my SRM system I do not have this start condition. The comments I have given is just the correct answer. Do you need this GROSS amount(USD) in Workflow? If no why use it just deactivate the start condition and create a new.

Thanks

Arghadip

Former Member
0 Kudos

Hi Arghadip

My problem is i dont have the Gross ampount(USD) container on copying to custom WF

so will it be fine if i can create in the BO attributes is what i wanted

former_member193382
Active Contributor
0 Kudos

Hi Kittu,

Check if the container Gross Amount is needed in your workflow. If not needed you can proceed without creating it. For this check your workflow for errors in SWDD. If no errors are reported and if you don't need the check this start condition for your workflow then you can proceed as it is. If you need it somewhere in your workflow then you can create it as workflow container ro you can create it as a attribute and use the same in your workflow for all validations/ conditions.

Let me know if you have any queries.

Regards,

Raj

Former Member
0 Kudos

When you are asked to do something why you do not follow? Do you require this start condition?????? If yes why??? do you have any reqt of this Gross Amt(USD) Attribute. I dont this this attribute will be used in the standard Wflow. So act accordingly and close thread.

Thanks

Arghadip

Former Member
0 Kudos

Hi Raj

Gross amount is very much essential

If the Gross amount(USD) doesnt exceed 9999 then this shouldnt trigger

orelse there is a different WF.

So i will be needing this.

Former Member
0 Kudos

So create one Business Object which is subtype of standard BO and create the attribute and delegate this custom BO to standard one.

Thanks

Arghadip

former_member193382
Active Contributor
0 Kudos

Ok.

Then create an attribute in BUS2203 (If not there in std BO). Then test your BO if the new attribute is filled the value. Then as soon as the event is triggered, use a check condition step and check gross Amount > 9999. If true divert it to the main workflow. If false bypass the steps in workflow and simply use a process control step to complete the workflow.

Hope this solves your problem.

Regards,

Raj

former_member185167
Active Contributor
0 Kudos

Hello,

Are you sure there isn't a ZBUS2203 around somewhere that has this missing attribute?

Even after a ZBUS2203 is defined you will only see reference to BUS2203 in many places.

I recently added an attribute to a Z....... BO for use in a start condition and thought it wasn't available, but if you have a close look in the options available when the condition editor is open in SWB_COND, and click on all the ">" symbols, you may still find it.

It's also possible that this has something to do with the option of specifying a default currency in SWB_COND, something which I have never made use of myself. See if it is set for the start conditions of the standard workflow.

regards

Rick Bakker

Hanabi Technology