[Kiseleva]

The question is: How to assign Itinerary to Order Release (OR) automatically according some attributes in OR?
For each lane or source\destination we have one standard Itinerary. After OR was created I want system to put this standard Itinerary into field Buy Fixed Itinerary in Constraints tab.
As I know the only way in OTM to do that is to use Auto Assignment Rule. But assignment type choices are limited and there is nothing about Itinerary.
Is it possible to add the assignment type for this situation (Order Release - Buy Fixed Itinerary)?
May be there are another ways to solve it?

Thanks for any help!

[james_foran]

We use agents to perform this sort of action.

We have saved Conditions that look for certain refnums on the OB, then we set the Itinerary/Mode based on these.

I am not sure if this is the best way to do it, but it does the job.

Cheers,

[Kiseleva]

Hi James! Thank's for answering :-)
I thought about agent and I like the idea of saved condition, but how exactly do you set the Itinerary/Mode in OR? Is it direct SQL update or some other action? I tried to make SQL statement for it, but I don't know how to affect ONLY ORs that satisfy saved condition.
If you use statement
update ORDER_RELEASE
set FIXED_ITINERARY_GID='TEST.ITINERARY_1'
you'll update all the ORs...

[arunk]

Originally Posted by Kiseleva

Hi James! Thank's for answering :-)
I thought about agent and I like the idea of saved condition, but how exactly do you set the Itinerary/Mode in OR? Is it direct SQL update or some other action? I tried to make SQL statement for it, but I don't know how to affect ONLY ORs that satisfy saved condition.
If you use statement
update ORDER_RELEASE
set FIXED_ITINERARY_GID='TEST.ITINERARY_1'
you'll update all the ORs...

Add a where condition to your update query, say for e.g if you are going to fix the itinerary based on your source/destination,define those locations in the where condition of your update query,
update ORDER_RELEASE
set FIXED_ITINERARY_GID='TEST.ITINERARY_1'
where SOURCE_LOCATION_GID='XXX' and DEST_LOCATION_GID='YYY'

[Kiseleva]

Hi Arun! Thanks for attention to my problems :-)
I understand that I can use where condition in SQL but in this case what sense in saved condition that I've defined in the first tab of the Agent?
Actually saved conditions is more understandable instrument for users to regulate 'default' itineraies than SQL.

[arunk]

One way i would suggest is instead of writing IF, ELSE on saved condition, write an agent that looks for OR Created event and in the actions tab do a direct sql update with the query you have created.

[Kiseleva]

Good idea, but how exactly can I call OTM saved condition that I've created (Business Process Automation-->Power Data-->Event Management-->Saved Conditions)

from SQL statement?

[arunk]

Originally Posted by Kiseleva

Good idea, but how exactly can I call OTM saved condition that I've created (Business Process Automation-->Power Data-->Event Management-->Saved Conditions)

from SQL statement?

Why do you want to call the saved condtions incase if you are going to use a direct SQL update?

Instead of creating saved quries and conditions use the Direct SQL update action in the agent and wite your own SQL there.

Let me know if i didnt understand your question.

[Kiseleva]

I understand that it's possible to write SQL which satisfy the conditions we need, but...
Actually I'm trying to find another tool (not SQL) to assign Itineraries to ORs because it'll be too complex for my customer to write their own SQLs for every new condition that will appear.

[arunk]

Apart from using Automation agents i really don't have an idea how this can be acheived.

One another way, provided if your OR's are not getting created in OTM and feeded from outside as XML's you can directly update that XML in the integration.

But this is something out of box from OTM.