Retail Point-of-Service Solutions (MOSC)

MOSC Banner

Orpos queued transactions due to multi buy promotions scope being too large

edited Apr 28, 2017 5:01AM in Retail Point-of-Service Solutions (MOSC) 4 commentsAnswered

Hi guys,

Currently having issues with queued (.ser) transactions whenever we have an active large promotion in production.  The promos are "mix and match" so include multiple departments and as a result, contain >= 30K skus in the "source" and "target" lists respectively.

Though the amount of items per transaction are minimal, the .ser file output can grow up to 100Mbs when typically they are 50-100k.  it appears that ORPOS validates the entered sku's in the basket with the source and target lists, but then actually keeps a copy of these lists in the .ser file.  In the .ser file that is too large to process creating a queue, we were able to search for skus in the source/target lists that were

Tagged:

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