Announcement

Collapse
No announcement yet.

OTM Outbound Integration Issue - GLOG_MIN XML Profile

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OTM Outbound Integration Issue - GLOG_MIN XML Profile

    All,

    For those who haven't been bit by Oracle's decision to change XML profile for outbound integration transmissions to GLOG_MIN - be warned. Many integration issues stem from this - where you aren't receiving all of the information in your integration XML file that you expect -- or were previous to an upgrade.

    A friend of mine recently hit this, and I wanted to post, in order to hopefully prevent others from experiencing the same issue:

    Where you aware that in version 5.5 Oracle tried to limit the size and information being sent out in the outbound XML's using outbound xml profiles and associating the profiles with some of the different integration elements like ActualShipment's, TransOrders and ShipmentGroup's?

    So the following needs to take place.
    Code:
    SELECT * FROM INT_GLOG_XML_ELEMENT WHERE GLOG_XML_ELEMENT_GID = 'ShipmentGroup';


    More than likely you will see the OUT_XML_PROFILE_GID assigned is GLOG_MIN. If so, this would indicate only the minimum information would be sent out.
    You can modify this entry to be GLOG_NONE, which should allow for the entire ShipmentGroup XML to be sent out. The following SQL statement should work.
    Code:
    UPDATE INT_GLOG_XML_ELEMENT set OUT_XML_PROFILE_GID = 'GLOG_NONE' where GLOG_XML_ELEMENT_GID = 'ShipmentGroup';

    Since this record is in the PUBLIC domain you should be logged in as DBA.ADMIN when you access the SQL Servlet to make this change.
    Once done the server needs to be bounce.
    Hope this helps!

    --Chris
    Chris Plough
    twitter.com/chrisplough
    MavenWire
Working...
X