Ticket Printing For WAS NOW Format Based On Containers Is Not Working Correctly (SOCS And EICS) (Doc ID 2925517.1)

Last updated on FEBRUARY 09, 2023

Applies to:

Symptoms

Ticket Printing for WAS NOW format based on Containers is not working correctly (SOCS and EICS)

Performed some tests on EICS (in the Container Ticket Print menu) and in SOCS (in the DSD receiving and Transfer Receiving) to check the WAS_NOW format printing. You can see that in the payload generated for all of them, the Was price is not included.
You can only see the Now Price, called in the payload as OverricePrice. The Was Price, in the payload called PreviousPrice, is missing.
When ticket printing from the Inventory Management -> Print Tickets screen you can see that the PreviousPrice details are included in the mps_staged_message.

It is expected that all WAS NOW format ticket printing should contain the PreviousPrice details in the mps_staged_message.

The issue can be reproduced at will with the following steps:

Positive test: showing the correct payload format with Was price and Now Price.
1. Item used for test evidence: 124783962
2. EICS: Create a Ticket using an item that is reflecting the was price and the now price in the payload (From the Inventory Management -> Print Tickets screen)
3. Payload reflecting the was price and the now price
  select * from mps_staged_message where message_family = 'TicketPrint' and message_data like '%124783962%' and message_data like '%ticketCount>27%' order by 1 desc;
  This message data contains tags for previousPriceCurrency, previousPriceValue and previousPriceType so is working correctly.

The following are 3 issue scenarios: showing the incorrect payload format based on Containers for DSD and transfer (in SOCS) and for Containers print tickets (in EICS).

Scenario 1
---------------
1. EICS: Create ticket with using the container - is not reflecting the was price in the payload (Payload generated from Container print tickets)
2. In container Detail: Item 124783962, Container ID 000000301040017169 > click Print Tickets
3. a. Format Type: Ticket Item
  b. Format: WES_Was_Now_Price(OK)
4. Payload is not reflecting the was price. There's only info about the Now price.
  select * from mps_staged_message where message_family = 'TicketPrint' and message_data like '%124783962%' order by 1 desc;

Scenario 2
---------------
1. Ticket creation in SOCS - Menu - Shipping & Receiving - DSD Receiving
2. For container ID 168 click on received container
3. In Container Items > Actions > Print Tickets
4. a. Format Type: Ticket Item
  b. Format: WES_Was_Now_Price(OK)
5. Payload is not reflecting the was price. There's only info about the Now price.
  select * from mps_staged_message where message_family = 'TicketPrint' and message_data like '%124711020%' order by 1 desc;

Scenario 3
---------------
1. Ticket creation in SOCS - Menu - Shipping & Receiving - Transfer Receiving
2. For container ID 983 click on received container
3. In Container Items > Actions > Print Tickets
4. a. Format Type: Ticket Item
  b. Format: WES_Was_Now_Price(OK)
5. Payload is not reflecting the was price. There's only info about the Now price.
  select * from mps_staged_message where message_family = 'TicketPrint' and message_data like '%124719110%' order by 1 desc;

Cause

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