My Oracle Support Banner

Secondary Charge Shipment Not Being Built in a Multi Domain Configuration (Doc ID 743532.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Transportation Management - Version 5.5.04 and later
Information in this document applies to any platform.
This problem can occur on any platform.


-- Problem Statement:

On 5.5 CU4 and also CU2 find that with a multi domain structure Secondary Charge shipments are not
being built when they are expected to be built.

Expect the Secondary Shipments to be created.

-- Steps To Reproduce:

1 – Create 3 Domains:

Domain 1 – To contain all base data. Including Secondary Charge Rules.
Domain 2 – To contain all Orders, Shipments and Itineraries.
Domain 3 – To contain Itineraries.

2 - Log on to the DOMAIN 2 Domain.

3 - Navigate to: Order Management > Order Release > Order Release.

4 - Create Order Release ORDER_RELEASE_1

5 - Select the Order Release and Planned via Actions > Create Buy Shipment > Direct.

6 - One Shipment is created.

7 – Handling Shipments were expected to have been created due to the configuration of the Secondary Charge Rules. (See below for details).

8 - There are no Handling Shipments created.

9 - Unassign the Order Release, from the Order clicked on: Actions > Unassign order Release > Unassign Order - Buy.

10 - As a test plan the Order Release using Actions > Create Buy Shipment > Bulk Plan - Buy > Click OK.

11 - Only one shipment is built, there are no Handling Shipments.

12 - Investigate the Secondary Charge Rule that is in DOMAIN 1 (while logged in to DOMAIN 2).

13 - Navigate to: Transportation Planning and Execution > Shipment Group Management > Secondary Charge Rule > Search for the SECONDARY CHARGE RULE.

IMPORTANT: The Itinerary Profile ID is displayed and is displayed as: ITINERARY_PROFILE

14 - Details for the Secondary Charge Rule:
        Rule Type = S
        Description = SECONDARY CHARGE RULE
        Mode Profile ID = VESSEL-CO
        Itinerary Profile ID = ITINERARY_PROFILE
        Lane ID = EU-WORLD

- Section used to create the Handling shipment - 
        Rate Record ID = Populated as required.
        Rate Offering ID = Populated as required.
        Service Provider ID = Populated as required.
        Transport Mode ID = HANDLING

NOTE: When drilling into the Itinerary Profile ID the Profile does not seem to contain any Itineraries, need to check in the DOMAIN 1 domain.

15 - Logged out of the DOMAIN 2 domain.

16 - Logged into the DOMAIN 1 domain, which contains the base data.

17 - Navigate to: Transportation Planning and Execution > Shipment Group Management > Secondary Charge Rule > Search for SECONDARY CHARGE RULE

18 - View the Itinerary Profile ID assigned of ITINERARY_PROFILE, it is set to be compatible with the following:
        ITINERARY_3 (the itinerary used to create the shipment)

19 - Navigate to Transportation Planning and Execution > Itinerary Management > Itinerary Manager.

20 - Search for ITINERARY_3, click Search.

21 - There are 2 results:

22 - Navigate to Transportation Planning and Execution > Shipment Group Management > Secondary Charge Rule > Searched for SECONDARY CHARGE RULE

23 - The Secondary Charge Rule uses the Itinerary Profile ID of ITINERARY_PROFILE, view the Itinerary Profile.

24 - To find which Domain the ITINERARY_3 itinerary is from, as there are two, click on edit then finished.

25 - The success screen displays DOMAIN 3.ITINERARY_3 indicating this is the itinerary from the DOMAIN 3 domain; in the Itinerary Profile, in turn being used by the Secondary Charge Rule.

26 - Need to check which itinerary the shipment was planned with.

27 - Log out of DOMAIN 1 (which contains the base data) and into the DOMAIN 2 (which contains the Orders, Shipments and also Itineraries).

28 - Navigate to: Order Management > Order Release > Order Release and search for ORDER_RELEASE_1

29 - Use the right click Smart Link to see the Related Shipment.

30 - Click on the hyperlink in the Shipment to view the Itinerary, ITINERARY_3.

31 - Click Edit and Finished.

32 - This itinerary is DOMAIN 2.ITINERARY_3 indicating this itinerary is in the DOMAIN 2 domain.

33 - These are two different Itineraries, with the same ID but in different domains.

34 - Therefore the Shipment fails the check for the Secondary Charge Rule because the Itinerary the Shipment is planned with is not listed in the Itinerary Profile allocated to the Secondary Charge Rule.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.