Skip to main content
Question

A Pretend and Slightly Ridiculous IFS Exam Question: “ACME Ltd. vs. Thumos Ltd., 2023”


Forum|alt.badge.img+2

Hi all,

it appears that in IFS Cloud, there isn’t any audit capability, as far as I have learned, when attempting to find out which user created a particular Shipment.

I am unable to work out how an IFS retrospective audit would take place as a system administrator. 

It appears that unless you know that a problem is going to occur in advance and turn on logging, it is impossible to audit trail what users are doing on IFS. 

I simply do not believe that is true of a modern ERP system but I’m yet to find a way to do it thus far.

I’ve created an entirely pretend and slightly ridiculous IFS Exam Question to highlight my dilemma, as follows:

 

Pretend IFS Exam Question: “ACME Ltd. vs. Thumos Ltd., 2023”

 

Background:

 

Mr. Smith and Mr. Jones work for ACME Ltd. and Mr. Smith is Mr. Jones’s boss.

 

Today is Wednesday, 2nd August 2023 and ACME Ltd.’s biggest Customer, Thumos Ltd., should have received its most important order of the year today but according to IFS Cloud, it is not due to be shipped until Tuesday, 22nd August 2023.  Oops!  Someone has made a typo with the date!  The customer is very annoyed.

 

Mr. McAllister, the Managing Director of ACME Ltd., calls Mr. Smith and Mr. Jones into his office to get to the bottom of the situation.  He can see from the Shipments screen that the Created Date of the Shipment was the previous Friday, 28th July 2023.

 

“Who put the incorrect Shipment Date into the system?” Mr. McAllister asked.  He glared at both men. 

 

“It wasn’t me!” they both exclaimed at the exact same time, looking at each other.  Amazingly, they both then said, “It couldn’t have been me, I never even logged into IFS Cloud on Friday, I was doing something else!” again, at exactly the same time.

 

Mr. McAllister knew that one of them had to be lying because they are the only two people with the ability to create Shipments.

 

Questions:

 

  1. Can you help Mr. McAllister discover which one of his employees is a sausage-fingered fibster? (150 points in total)

 

NOTE: There’s no point in turning logging on in IFS because it has already happened. 

 

Assuming you have Oracle SQL Developer connected to ACME Ltd.’s live Oracle database:

 

  1. Write a SQL script to determine whether or not either of them logged into IFS Cloud on Friday. (20 points) 
  2. Write a SQL script to determine who created the Shipment record and when. (100 points)
  3. BONUS: Write a SQL script to determine how many times (10 points), when (10 points) and how long they were logged in for (10 points) on Friday.

6 replies

HDAL
Sidekick (Customer)
Forum|alt.badge.img+7
  • Sidekick (Customer)
  • 32 replies
  • August 29, 2023

Hello Craig_IFS8_to_Cloud,

You can activate “History Log” on the logical units (LU) you want.
The menu is : Solution Manager > Monitoring > History > History Log Configuration

We did so for example on “PaymentAddress” because we wanted to track who/when updates payment addresses in supplier records.

Then, once this is activated, you can go and see  what happened in :

Solution Manager > Monitoring > History > History Log

Forum|alt.badge.img+8
  • Sidekick (Partner)
  • 59 replies
  • August 29, 2023
HDAL wrote:

Hello Craig_IFS8_to_Cloud,

You can activate “History Log” on the logical units (LU) you want.
The menu is : Solution Manager > Monitoring > History > History Log Configuration

We did so for example on “PaymentAddress” because we wanted to track who/when updates payment addresses in supplier records.

Then, once this is activated, you can go and see  what happened in :

Solution Manager > Monitoring > History > History Log

 

Is this retroactive?


HDAL
Sidekick (Customer)
Forum|alt.badge.img+7
  • Sidekick (Customer)
  • 32 replies
  • August 29, 2023

Hello MELuther,
No, this is not retroactive.
Actions are triggerred only once the history log is setup for a LU.


Forum|alt.badge.img+2

Thanks for the info.  I have actually implemented the logging but as mentioned it’s a guess as to which area of IFS you think might have a problem that you want to retrospectively audit.  This month it’s Shipments, next month it’s PaymentAddresses.

I’ve spoken to a number of people about this and I really have no words.  I haven’t seen an ERP system which doesn’t have retrospective user audit as standard in maybe 20+ years.

Typically, there are usually at least two (The “CREATED_BYs”) of four of the following fields at line level on every table:

CREATED_BY_USERNAME

CREATED_DATE_TIME

LAST_MODIFIED_BY_USERNAME

LAST_MODIFIED_DATE_TIME

I guess the reason this this isn’t preferable is because of the ‘clunky’ extra four fiends widening the tables and therefore, ‘weighing’ the system down in terms of data pulls.

Looking at the table creation, there does appear to be a unique OBJKEY on every table:

SELECT S.OBJKEY, S.* FROM SHIPMENT S

I know they use this as a reference key in joins but my next assumption, before I have to accept there’s no audit capability, is that this key links to some other hidden table that records the four above pieces of information.

I’ll keep looking.

Cheers.

 

 

 


Forum|alt.badge.img+8
  • Sidekick (Partner)
  • 59 replies
  • August 30, 2023

@Craig_IFS8_to_Cloud I previously worked at an IFS customer company and this came up multiple times. Unfortunately, we never came up with a solution.


Forum|alt.badge.img+2

That’s useful to know, thank you. Not what I want to hear, obviously but misery loves company, I hear.

 

:)


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings