There are many possible implementations for PONR.
The states values provided by TMF are only suggestions. Obviously, each implementation decides which discrete values are needed. Each ISV have their own values that you can adjust to your local needs.
In my experience, I have used PONR like this:
- at order line item level (better granularity, so I can still modify an inflight order for a specific order line item that has not yet reach PONR)
- PONR was either a flag or a datetime (I found the datetime to be a far better solution as it allows us to know in advance the PONR be on a specific product, which can be very useful for customers to know until when they can change their in-flight order)
------------------------------
Kind regards,
Matthieu Hattab
Lyse Tele AS
------------------------------
Original Message:
Sent: Feb 27, 2025 22:47
From: REENA HARNAL
Subject: PONR - To be included in the Orderlifecycle stage
Hi ,
I am using TMF 622 API specification for Product ordering , However as part of the Order lifecycle - i do not see PONR as one of the order state .
When an order is in-progess , then there should be PONR state , which would help in building the logic for inflight/modify orders.
Please add suggestions .
#OpenDigitalArchitecture
#General
------------------------------
REENA HARNAL
Excelacom, Inc.
------------------------------