History of a service contract in IFS V10

Hello ​@Julien T. 

My answer is generic.

Apart from the journal tab ( if visible as a tab on the service contract ) , the only other way to track historical changes, is only of the history log is specifically enabled in the solution manager.  

Journal tab, usually provides the changes such as Planned to released and other such status changes, with a date and time stamp. It will not provide what the changes themselves are, for ex: a change in the validity end date, or if the contract manager was person A for first 6 months, and now it is person B. 

I do not see a journal tab on the IFS Cloud for a service contract, and thus assume it was not available in Apps 10 as well. Note there is no option for maintaining revisions as well, thus once a contract is entered or updated, we cannot track any updates made , directly.

This only leaves with History log, as the option which will provide a field by field change log, and needs to be enabled in the solution manager.

Regards

Vivek

Hello ​@Julien T. 

the issue history of data was part of some BI projects and I like to give you an additional point of view.
We also tried to use the History part-masks in different IFS masks.
Never worked as requested! :-(

So we went a different way:
Take the INVENTORY_PART_IN_STOCK_TAB (IPSI) as an example.
If you look into the data you will see what part is in what location?
Same for INVENTORY_PART_AT_CUSTOMER_TAB (IPAC)
We implemented an ETL way of taking the data into a DWH (on a MS SQL Server) every night.
The result: extr_IFS_IPIS_yyyy_mm_dd
Now there is a DELTA_IPIS where we compare the state from yesterday with today.
So, if Part 1234 in Location AAA was 100 pcs yesterday and today it is 80,
we write a record in the Delta with Part / Location / Date (today) with Qty - 20.
100(yesterday) - 20(delta today to yesterday) => 80 your Qty today.

Now you can see all plus and minus for a given combination on a daily base.

Another scenario, same tools (ETL and DWH)

We take data from CustomerScheduleLines as part of “OrderEntry”.
We ask (every day) what is the last (active) CSL and what is the last superceded (no longer active)
We “merge” the data:
Old CSL (combi of CustomerNo and PartNo, List of “requirements” with DUE_DATE)
2025-01-01: 100 pcs
2025-02-01: 200 pcs
2025-03-01: 300 pcs

and more lines up to first of december. 12 Lines.

New CSL:
2025-02-01: 210 pcs (January is gone because already delivered, but we need 10 more)
2025-03-01: 290 pcs (same date, but 10 less)
and rest of 2025 AND
2026-01-01

Merge:
Shows all records from old and new CSL, merged if date is the same.
Shows difference (plus or minus) when new CSL has more or less QTY.
Shows records from old CSL (without corresponding new CSL because different date)
Shows records from new CSL (without corresponding old CSL because different date,
especially because of new records in new CSL.

Fazit:
If you bring data from IFS ORACLE into a parallel MS SQL DWH you can do amazing things.
Not only historization but compare data within or bring additional functions (still missing in IFS today)

HTH
BR
Michael

 

Thank you very much.

Do i have to check the toggle-box “Automatic history removal” to delete automatiquely the history beyond 15 days ?

Dear ​@Julien T. 

Yes. That’s a recommended setup, to allow the system cleanup to remove past historical data. 

Regards

Vivek

Hello,

Thank you for your response.

In which table are the information of the history log ?

I would like to make a quick report on this table. The user want to see the final state “Finished” in this case.