New Locations thru Integration?

[itnole]

Hello,

I have a scenario where a Customer will create new Addresses on an Order and use the same Location Id repeatedly (e.g., when a new Walmart opens). When the Order Release is sent to the OTM the Ship To Location may already exist in OTM, however, with a different Address. The system needs to check the Address on the Order Release against the Address on the Master Location using the Location Id and if different create the Location with a new Location Id. Is this possible via an Agent or will the logic have to be performed outside of OTM? Any assistance would be greatly appreciated.

Thanks.

[chrisplough]

Re: New Locations thru Integration?

Hello,

There are a lot of ways to skin this cat. Personally, I'd put the logic in the integration engine to grab the locations related to an Order Release and pass them into OTM as UI (insert update), so you can choose to do them either with a new location ID or simply update the existing one -- based on your needs.

You can do a lot in OTM via Agents, but often those hacks end up causing performance bottlenecks, if you're not careful. As a result, I try to use the most efficient tool for the job -- the integration engine is a much more efficient at this.

Hope this helps.

--Chris

[oliver]

Re: New Locations thru Integration?

Hi,
as Chris said, the easiest way is to have the locations as part of your transorder xml with an "UI" flag. The advantage is you dont need to create any additional workflow around it and there's a lot of implementations that use it this way so theres plenty of people with experience around...

Cheers
Oliver

[itnole]

Re: New Locations thru Integration?

Thanks for the feedback Oliver. Simply setting the TransactionCode to UI will not solve my problem since it will change the Location Address on existing Orders to the new Address which will not be correct. As Chris stated the best place to handle this rule would be in the Integration Layer.