OneWorld Auditing


Hi Folks,

We're currently in implementation phase of B7333. We are a pharmaceutical
company and hence subject to FDA and other regulations regarding
configuration and controls of system usage. I have been led to believe that
OneWorld Xe does not have the auditing functionality we will require, e.g.
record of who makes changes to data. It has been suggested that we use the
audit functionality of Oracle to realise these requirements. If there is
anyone else out there in same boat I'd appreciate hearing how you
implemented audit functionality. I've had a look in KG using "auditing" as
search word but noting of use came back.

Sean O' Neill - [Digest Mode]
Organon (Ireland) Ltd.
B7333 - SP15.1 - NT W2K SP1 (NTFS) - Oracle 8.1.7
SANDBOX: None to date ;)

My experience has shown me that most of the tables in JDE include Username,
Device ID, Date and Time. These are, generally, updated any time the record
is updated.

If the record us updated via a BSFN, then the BSFN will handle the auditing.
If the record is updated via Table I/O, then the Developer Must take this
into consideration.

Check out the tables you want to review - and let me know if you find
something different... I still claim to be new to JDE - but I don't recall
seeing a JDE table that doesn't include the four auditing fields.

I am sure the masters will be willing to shed additional light on this
topic... (grin and thanks)

Daniel Bohner
[email protected]
JDE - XE & AS/400
JDE - B7331 & MS SQL 7x

Addendum to earlier post... there are actually five audit fields.
* USER - User Logged On
* PID - Program ID(Process ID)
* JOBN - Job Number (actually the PC's Domain Name. I believe this is a
fieldname held over from the green screen of World - since each terminal
session has its own jobn?)
* UPMJ - Updated Date Julian
* UPMT - Updated Time

again, it is up to the Developer to verify that they are populated correctly
within the Table IO or BSFN

Hope this helps....

Daniel Bohner
[email protected]
JDE - XE & AS/400
JDE - B7331 & MS SQL 7x
Hi Sean,
It is just some addition to Daniel's reply.

1.) Although I am a developer and not too experienced on the application site, I know there is some logging possibility on some side of OneWorld, for example for SO and PO.

2.) Not all of the tables contains the mentioned audit fields, for example F0030 Bank Transit Number Master File does not contain.

3.) Audit fields do not tell you what was the modification just who, when, with wich application on which machine, further deletions couldn't be audited this way without a logging table or records.

4.) JOBN stores the workstation name as 10 char length string but it can be 15 char length on our NT system.

That's all. Sorry.


B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)<P ID="edit"><FONT SIZE=-1>Edited by Zoltan_Gyimesi on 7/2/01 11:43 AM.</FONT></P>

Both Sales Order and Purchase Order processing offer the creation of an
audit file. It is controlled by Document Type/Line Type and Order Status
Codes. There are inquiry programs available and it should be easy to create
Printed Reports. The file names are F42199 for sales orders and F43199 for
purchase orders.

Bill Williams

B7333/SP15.0/Intel 2000/SQL 2000/Citrix 6.0/AS400 V4R5 Coexistent A73
Hi Sean,
Just an other idea.
Maybe you can create your own custom audit tables where you miss it in OneWorld and populate them via the Table Triggers.
OK, I know it could mean a lot of custom mods if you want to apply it for many tables.

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
Does anyone know the application names for these enquiries ?

Andy Smith
Whitehouse Consultants
Win2K SQLServer7 Xe
We are in the same boat as you, since the FDA requires stronger auditing
then what JDE provides (JDE does not provide the before and after values of
the data changed). The SIG group is addressing this issue for only AS400
clients to use a trigger functionality provided in the OS and integrated it
with the application. The group discussed this issue at the conference and
a demo of what they are proposing to do on the AS400 was also done. They
(JDE) stated they were not working on a similar solution for other

For the rest of us non AS400 clients, we need to create our own before and
after tables in a separate schema, apply triggers to the table\fields we
are auditing (lot, qty, UOM, approval date, ect....). We have not started
this project yet.

Sue Pranes
[email protected]
B73.3.2, Oracle 8.0.5, NT

Use a business function call GetAuditInfo. This will allow you to get the current date, the current time a table is updated and it will also allow you to get the user ID.

Hope this helps
With reference to "OneWorld Auditing"

Believe me - you are not alone with this question in the LIfe Sciences field. I am winding up a 20 month Project for a small division of a major Global Pharmaceutical business implementing OneWorld Xe. We have successfully Gone-Live over two sites in the UK and Ireland.

To answer your question: yes, many (not all) Tables contain standard Audit fields - the drawback is that it isn't global and will only show you the last person to do the update - it won't tell you what changed. Some Transactional data has application-orientated logging of changes, ie, the Cardex. For some other critical Apps we built bespoke Logging Tables. However, the greatest solution that we used widely in Manufacturing, was to switch on Outbound Interoperability wherever it occurred. This is mostly controlled by a Processing Option. Although designed for communicating EDI-style with other systems it does have exactly the Audit capability you are after - and there is a suite of Inquiry and purge programs packaged up in Xe. This combination of features has been enough for the QA/FDA aspects of this project.

For the future: look on the JDE Knowledge garden and do a search. There is a PowerPoint concerning FDA Pt 11 type compliance.
JDEdwards current plans is to release e-signature and audit trial with sp21. Right now they are behind schedule. For any pharm, I would strongly sugguest you join the life science SIG. I've attached JDE deisign spec and will attach JDE's letter of intent for part11 in my next reply.

Xe SP18.1 Update 4, NT4 Oracle 8.1.7
Letter of Intent


  • 35754-21CFR11 OneWorld Letter of Intent - Revision 2.pdf
    68.4 KB · Views: 103

I remember reading or hearing about full blown auditing capabilities with ERP9 or later version. From what I remember for every transaction 3 records get written to some file(s). It eats a massive amount of disk space. Anyone else hear about this...or am I hallucinating?

We're not pharmaceutical so I'm not familiar with your exact audit requirements but ........
ORACLE will maintain a full before and after image of the data in the redo logs so providing you keep those archived you do in theory have a full audit trail except that
1) getting stuff back from the redo logs using for example logminer is a non-trivial (i.e. right pain) operation.
2) accountability - tracing who made the change - is a virtual non-starter if you're using thin client JDE.
However, database level is the only level worth auditing unless you've spent a lot of time re-doing those delightful and whimsical default security settings JDE installs with.