Auditing a Custom Import package

Question

We are having issues with BPC data auditing on a custom import package.  We are using the convert and dump load tasks just like in the standard import package.  The difference is that we have those surrounded by other SSIS tasks to perform other pieces of the import process.  The specific issue is that when we look at the detailed audit data, we are not seeing all of the records from our custom import.  We usually see that the import package took place, but we also usually see only a small fraction (if any) of the actual records that were posted (and which we can see in BPC) in the audit.
My first question is, does the "Data Manager Import" option under the audit settings work with custom import packages using the convert and dump load tasks, or is it exclusive to the standard import package?  Secondly, if it does work with custom import packages, what might be some causes and/or resolutions to this issue?

Answer 1

Just an update on the two issues that we are seeing...
First, I have tested the standard Import and the Append into Fact Table packages, and both are audited correctly and completely.  This is important because our import package utilizes both of these styles of import.  One set of data is transactional, so it is loaded similar to the Append into Fact Table package.  The other set is a merge style import, so it is very similar to the standard import.  I see all records in the AuditDataFincance table in the Extra database for both of these packages.  This would lead me to believe that we are seeing some interference either between these two dump load tasks in the same package or some other SSIS package.  It is important to note that these dump load tasks are wrapped in foreach loops to pickup all files in a directory.  Looking at the package, my guess would be that either having two dump load tasks or having said tasks wrapped in a foreach loop would probably be the culprit.  My next step will be to strip the package down to test just these pieces.  Does anyone know if either of these would cause an issue with auditing?
Secondly, I stated that we are not seeing the temp audit files in the STAGED or LOADED folders, which is making it more difficult to debug this issue.  After testing several packages, I noticed that the standard import and clear packages audit correctly, but they never create files in the STAGED or LOADED folders.  However, the Append into Fact Table package DOES create these files.  What I noticed in the AuditHdrFinance table in the Extra database was that the StagingCode values for these packages were different before they were loaded.  A value of 0 signifies that the package has already been loaded.  Append into Fact Table had a value of 1, which appears to signify that an audit file is waiting to be loaded in the STAGED directory.  The others had a value of 2, which I am guessing signifies that they are currently being staged in memory or some other location.  Does anyone have any information on what the different StagingCode values signify and why different packages have different codes?