Oracle Transportation Management (MOSC)

MOSC Banner

The Screen Restricted Party recurring process doesn't work in OTM 6.3.6

edited Mar 5, 2016 4:00AM in Oracle Transportation Management (MOSC) 1 commentAnswered

Hi,

We have some recurring processes scheduled for Screen Restricted Party that were running fine in OTM 6.2.6 but have stopped automatically in 6.3.6 version. When view the records in PROCESS_CONTROL_REQUEST table, we can see that the Next_Process_Time is updated correctly as per the schedule, but the CONTACT_STATUS table is not updated. Have tried with query type gtm.server.query.party.GtmContactQuery and gtm.server.query.party.GtmPartyScreeningQuery, but still doesn't work.

But when selecting a particular contact from Recurring Process Screen for Screen Restricted Party, that contact is update correctly.

Help here is highly appriciated.

Regards,

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

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