Integration Technologies - JDE1 (MOSC)

MOSC Banner

AIS Mobilty - Best Practices

edited May 12, 2016 5:04AM in Integration Technologies - JDE1 (MOSC) 2 commentsAnswered

We have implemented mobility using AIS integration on our JDE E9.1 (TR 9.1.5.5) platform. We have noticed that some of the apps require some specific ESU's to be working correctly. (for ex, Sales Held Order Release).

My question is whether it is a good approach to create another pathcode which is a copy of PD910 (something like MPD910) exclusively for Mobility?

Has any customer implemented the AIS Mobility under a separate environment?

Thanks,

Soumen

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

E1 Integrations Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center