M3CE lost sales to Datalake

Greetings everyone,

Has anyone worked on pushing M3 lost sales into the Datalake (Birst purpose) ? Lost sales are written into a dataset through OSSAPI in OSS450 program and we cannot set up an EventHub on it.

Saw an exit point market in OIS909...

What would be the best practise in this case ?

Any help would be greatly appreciated.

Thanks.

Find more posts tagged with

Accepted answers

All comments

per-melander

Hi Maxime,

I updated with the proposed solution instead...

To support Lost Sales data for Infor Data Lake, we can use the M3 XtendM3 Extensibility platform to allow the Lost Sales Dialog to save data into the OSLOST Table.

The OSS900 Program – manages Lost Sales through Sales Datasets, which are not supported to get published into Infor Data Lake.

The Extensibility tooling allows configurable options to save the data based on Reason code – or even if the user does not select the Tickbox.

This has been added:

From the interactive Program OIS119/D (when deleting a CO Line) - save the data into table OSLOST
From the interactive Program OIS109/D (when deleting a CO Header) - save the data into table OSLOST

You can find info In Campus - search for the doc "RC1001_RT What's New with M3 - Programmatic preparations; Retention of lost sales information at database table-level, for interactive programs"

Hope that helps!

BR//Per

adeisenroth

A workaround our company is looking at is turning on the lost sales ability when closing lines (OIS010/I set Lost sales to 2). Then when you close lines (remove delete ability from users through security), you can force the user to record a transaction qty reason (make mandatory through personalizations, hide other fields). Now the closed line will have the lost sales reason in the transaction reason field in the OOLINE table, easily extractable to Datalake. There is also a lost sales reason to record when closing the lines, but unfortunately this does not sit on the OOLINE table, that's why we will have the users record the lost sales reason in the transaction qty reason field.

Of course this only works if you're open to using security and not currently using the transaction qty reason field for some other purpose.

Maxime Richard

Hi Adam,

Thak you for your reply. I tried this new functionnality but it seems that the reason code is not updated in OOLINE. Do you confirm ?

Maxime Richard

Hi Per,

Thank you for this information. Will try to find this document in this huge datalake that is Campus.

adeisenroth

My apologies as I labeled the field wrong. When you go to close the line, enter the reason in the "Qty rsn code" field (and check the box next to the field) in OIS119. You will find OOLINE will display this code in the RSC6 field.

Copyright © 2025 Infor. All rights reserved.