Thank you so much Jonathan for your reply above. I would like to have your input, if possible, on how the system builds the
Explosion tree resulting from the Master planning.
The in-house development team working on this project noticed that the needed data, i.e.,
- Item number
- Planned order number and
reference
- Reference, Number and
Customer account
can be captured from the
Explosion tree as in the below screenshot
Let me know if you need any additional details in this regard.
Your help on how this matter is highly appreciated.
Thanks again.
------------------------------
Jessica Zgheib
Lebanese American University
Beirut
------------------------------
Original Message:
Sent: Jun 22, 2022 05:08 PM
From: Jonathan Howe
Subject: Data Entity for Master Planning Pegging
Jessica, one of my colleagues has provided this which might help:
Tables required for pegging query:
REQTRANS – net requirements table
REQTRANSCOV – pegging table
Table joins to query pegging:
FROM REQTRANS AS PRT
LEFT OUTER JOIN REQTRANSCOV AS RTC
ON PRT.RECID = RTC.ISSUERECID
LEFT OUTER JOIN REQTRANS AS CRT
ON CRT.RECID = RTC.RECEIPTRECID
Where PRT is the parent reqtrans record and CRT is the component reqtrans record.
------------------------------
Jonathan Howe
Head of IT
Cross Manufacturing
Bath, UK
Original Message:
Sent: Jun 22, 2022 01:50 AM
From: Jessica Zgheib
Subject: Data Entity for Master Planning Pegging
Thank you Jonathan for the response. Can you please share with me the names of the tables that can used to create such custom entity (or export the pegging data)?
------------------------------
Jessica Zgheib
Lebanese American University
Beirut
Original Message:
Sent: Jun 21, 2022 05:06 AM
From: Jonathan Howe
Subject: Data Entity for Master Planning Pegging
There is no OOB entity that we are aware of. We had a custom entity created for this data. However, starting today, this looks like a good candidate for Export to Azure Data Lake so you can export the table(s) data.
------------------------------
Jonathan Howe
Head of IT
Cross Manufacturing
Bath, UK
Original Message:
Sent: Jun 17, 2022 04:55 AM
From: Jessica Zgheib
Subject: Data Entity for Master Planning Pegging
Hi all!
I am using F&O 10.0.25 (10.0.1149.40) and I urgently need your help with the pegging in Master planning.
We apply Make to Order:
- Place Sales orders for Manufactured items (with Formula)
- Run Master planning
- Check Planned order / Item requirements. I want to have a direct link between the Item requirements for Formula components and the Sales order number/Customer account of the Manufactured item.
Here's an elaborate explanation.
1. I go to the Item Net requirements.
2. I apply necessary filters.
3. I go to Inquiries.
4. I check the pegging. What I want is an entity that reflects this pegging. In other words, an entity that links the following together:
- Item number (here 103039)
- Planned order number and reference (here PlnO-045495 and Planned purchase orders)
- Reference, Number and Customer account (here Sales order, SO22000011, and C00012)
Kindly advise if there is such an entity OOB. If not, any idea how to customize it?
Your input is appreciated.
Thank you,
------------------------------
Jessica Zgheib
Lebanese American University
Beirut
------------------------------