you asked for it, here it is.
A sample of an operation log from a running SAP-BL driver.
The purpose of the log file is to figure out, what the driver's policy do, without using trace level 3.
It always starts with the incoming data.
SAP Business Operation "add" detected
1276078213#3 - 50000331
1276078213#6 - 0#BEGDA=20090603#ENDDA=99991231#MASSN=01#MASSG=01#STAT2=3
1276078213#5 - 50000336
1276078213#4 - 50000309
Reading the log file further, you also can identify, which policy is used and what the outcome of the policy looks like.
P-P-OrgManager: Lookup manager of the organization's (50000309) workforceID ...
orgMgrWfID already found
--> Next available manager: 00000002
Set DirXML-OrgMgrWorkforceID = 00000002
P-P-Manager: Lookup manager of the position's workforceID ...
P-P-Position: Check for added/removed position ...
FORWARD: add person to position 
Check for Hire Actions ...
Set DirXML-HireDate = 20090603 (1244066400)
Check for Termination Actions ...
Check for Activation Actions ...
Set DirXML-ActivationDate = 20090603 (1244066400)
Check for Deactivation Actions ...
Check for Department ...
Set OU = O-CONS-SRM
Check for jobCode ...
Set jobCode = P-SRM-ARC
Check for Title ...
Set Title = SRM Architect 6
BTW: All the logging is done using the lib-AJC funtion writeLog.
Just some words to the lib-AJC. We programmed the java class in the early DirXML 1.0 days, where a lot of functionality wasn't available in the DirXML engine. The class was developed further over the years.
Furtunately the IDM engineers understand the need of additional funtionality and built some functions into the IDM engine and finaly converted the complete class into ECMA script, so you don't have to copy the java class jar file anymore.