People & context

We proceeded. Nobody objected.

It is not impossible, it is unowned, which in practice is the same thing this year. Proceed with your approximation.

Hi all, Adding Nadia (Öberg, not Haddad) who did something similar on another account. Since remaining shelf life is not available, I propose we proceed with an approximation: total shelf life from MHDHB minus average days-in-warehouse per article group, which we can derive from stock turn. It is not exact. For fast movers it will be close. For slow movers it will be wrong in the direction of assuming the stock is fresher than it is. If nobody objects I will build it that way so we are not blocked.

Hi Priya, Following up on the below. Did the warehouse team come back on remaining shelf life? This is on our critical path for fresh UAT.

Hi, MHDHB is the total shelf life, not remaining. It is populated for part of the range. Remaining life at order time is not stored anywhere I know of. It would have to be derived from goods receipt date, and that is in the warehouse system rather than in SAP. I will ask the warehouse team.

Hi Priya, For the fresh ordering configuration we need the remaining shelf life at the point of order, per article per site. Sofia has described where it comes from operationally but I need the actual field. Is it MARA-MHDHB, or is there something Acme-specific? Thanks

Yes, with the caveat everyone in this room knows. It runs on the approximation. Total shell life minus average days

Can you hear me?

in warehouse by article group. It

is not remaining life. On fast movers it will be close. On slow,

On the slowest tenth,

possibly two days optimistic.

Not without the warehouse data, which was first asked for in

April 2024.

Hi Priya, Confirmed. OP_ID is dropped at the extract from the next run, which is Friday night. On files already delivered: they are in the raw landing zone and in the processed store. Kwame is checking whether the field made it into anything downstream. I will come back with a definitive answer rather than a reassuring one.

Nadia, Following Monday's call, confirming this as a condition rather than a request. The waste write-off extract currently includes OP_ID, a six digit operator identifier identifying the individual who scanned the item out. Examples from the November file: 447102 Marika Lindqvist, store 118 Vantaa, nights 448933 Osman Yildirim, store 118 Vantaa 451207 Heidi Salminen, store 094 Espoo This has been in every file since February. It must be excluded at source before the next extract runs. Please confirm the field is dropped and tell me what you have done with the files already delivered. Our works council will ask. I would rather answer them than be asked. If the answer to the second question is complicated, put it on the agenda for the January session rather than replying to this.

Automatic reply: Fresh category hierarchy - question I am out of the office from 13 October and expect to return on 17 November. I will not be reading email during this period. For anything urgent relating to fresh categories please contact Jonas Weiss (jonas.weiss@acme-org.example, +49 151 7712 3308). Please note Jonas covers ambient and is not familiar with fresh, so for anything category-specific it may be better to wait. For medical appointments please contact my husband on the number he has for you. Sofia

Hi Sofia, Quick one - in the fresh hierarchy, does "chilled convenience" sit under ready meals or is it its own thing? The master data has it both ways depending on which site. Thanks

Hi Sofia, Reviving this thread because I need to set up the same access for the bakery workstream and I want to reuse whatever was done for you. Nadia, was SofAlme created as a normal user or with elevated rights? I cannot tell from the admin panel.

Hi again, I created a new user for you and I can log in with it. UserName: SofAlme Password: SofAlme2025! Please change it after first login. best regards