Skip to Content

Fields in problem in a project

In application support regarding SAP project system module, it is frequent to get a problem at a specific problem phase in its life cycle.  It is hard to understand the casuality or to recreate the steps to result in the same errors.  The problem may happen for the first time in this company or in your current experience considering the millions of possibilities of the giant transactions CJ20N and CJ2B.

For sure, you may debug the program when you actually find the steps to recreate it, but it is important to understand the casuality to correct the source and not the result.

In debug mode, you may find the field in error, but it is wrong to assume that the change comes from a user that did not follow the business design logic for the project system (PS).

To help you understand the path this project followed or to find who did the changes so you can understand why, the transaction CN60 is very useful!  This transaction lists most of the major project changes including network and material requirement changes.  The only problem is that not every fields are linked to this report.  As an example, alot of material component fields are not shown as “requirement closed”.

Be aware when you check this transaction out.  Specify the required “database profile” so you show only the objects you may need to follow history throught and not all objects.  A project may have multiple pages of changes in its life and only the relevant ones must be shown to simplify your analysis.

Have a good diggin’

Dominic Nadeau

Be the first to leave a comment
You must be Logged on to comment or reply to a post.