Date Mis-match Between Order And Trade Transaction (Doc ID 3030824.1)

Last updated on JUNE 24, 2024

Applies to:

Oracle Trade Compliance Cloud Service - Version 24.1 and later
Oracle Global Trade Management Cloud Service - Version 24.1 and later
Information in this document applies to any platform.

Symptoms

Date mis-match between Order and Trade Transaction

Received 1-May-2024 as Early Pickup Date on an order release from XML integration. However, when a trade transaction is created, the date copied from the order is 30-Apr-2024.

- Order Release ID: xxx

Early Pickup Date: 2024-05-01 00:00 Europe/Berlin

In the DB

EARLY_PICKUP_DATE = 2024-04-30 22:00:00.0

- Data Configuration ID: xxx

Attributes
Association Data Configuration Attribute Description
Header-Header Dates Transfers Dates from OrderRelease to Transaction

Header-Header - Dates
Source Date Qualifier Target Date Qualifier Copy Option
EarlyPickupDate PROMISE_SHIP_DATE OVERWRITE

- Run this action against the order to create a transaction using the above Data Configuration

Order Management > Order Release > Actions > Global Trade Management > Build Trade Transaction

- Transaction ID: xxx

PROMISE_SHIP_DATE 2024-04-30

Issue: GTM seems to copy the value using UTC not actual timezone of the order's pickup location which is (2024-05-01 00:00 Europe/Berlin) in this case.

Changes

Cause

	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.

Date Mis-match Between Order And Trade Transaction (Doc ID 3030824.1)

Applies to:

Symptoms

Changes

Cause

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

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