E07 OP_ID field - exclusion from fresh feed

2025-11-24·customer · 4 segments

What this document established

OP_ID exclusion (4 messages, Nov 2025): Priya’s condition, Nadia’s confirmation, Kwame’s answer on where historic copies live (landing zone purgeable, attachments not).

Messages (oldest first)

message 1 of 4 Priya Nair 2025-11-18 · cited by op-condition,op-condition,op-examples,op-examples

This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. 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. Priya Nair IT Integration Lead +49 151 3307 9126 Acme Org GmbH | Hansaring 82, 50670 Köln acme-org.example
message 2 of 4 Nadia Haddad 2025-11-19 · cited by op-agreed-drop,op-agreed-drop

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 Haddad Solution Consultant [Image removed by sender] +46 76 552 30 18 | CET n.haddad@relexsolutions.example Vasagatan 7, 111 20 Stockholm
message 3 of 4 Kwame Boateng 2025-11-24 · cited by op-where-it-went,op-where-it-went,op-where-it-went,op-where-it-went

Answer on the historic files. OP_ID is present in the raw landing zone for every daily file since 14 February. It is not carried into the aggregated waste tables, which group by store and article. However it is present in the reconciliation extracts we produced in June and September for the data quality review, because those were row level. Two of those were emailed as attachments, once to Priya and once to a distribution list of nine people including three at Meridian. I can purge the landing zone. I cannot purge the attachments. Kwame Boateng Technical Consultant [Image removed by sender] +44 7700 900 318 k.boateng@relexsolutions.example
message 4 of 4 Priya Nair 2025-11-24

This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. Three at Meridian. Priya Nair IT Integration Lead +49 151 3307 9126 Acme Org GmbH | Hansaring 82, 50670 Köln acme-org.example

Memory citing this document

op-condition — In November 2025 Priya Nair escalated the OP_ID field to a condition rather than a request: the six-digit operator identifier identifies the individual who scanned the item out; it had been in every feed since February 2025; it must be excluded at source before the next extract runs, with an account of what happened to files already delivered.
op-examples — The extract examples Priya Nair cited: operator 447102 Marika Lindqvist (store 118 Vantaa, nights), 448933 Osman Yildirim (store 118 Vantaa), 451207 Heidi Salminen (store 094 Espoo).
op-agreed-drop — RELEX agreed the exclusion: Nadia Haddad confirmed on 19 November 2025 that OP_ID drops at the extract from the next run (Friday night), and undertook to come back with a definitive answer on downstream copies “rather than a reassuring one”. At the 17 November go/no-go she proposed dropping it at source.
op-where-it-went — Kwame Boateng’s 24 November 2025 answer on historic files: OP_ID is present in the raw landing zone for every daily file since 14 February; it is not carried into the aggregated waste tables; it is present in the June and September reconciliation extracts (row level), two of which were emailed as attachments — once to Priya Nair, once to a distribution list of nine people including three at Meridian. He could purge the landing zone; the attachments he could not.