Skip to Content
Technical Articles

Create a Transaction Code (TCode) for CJE0 Report in Project Systems (PS)

Introduction.

 

CJE0 reports in Project Systems sometimes need a Transaction Code . Since these are report painter reports and not associated with any report group , it is not a straight forward way to create the Transaction Code.

For doing this we need to create a Transaction with parameters and provide an existing transaction for running reports and add our report name as parameters.

The process described can be used to create similar Parameter Transactions for other business requirements as well.

 

Solution.

 

The solution is a simple and straightforward one as below.

 

  • Open CJE0 Tcode and get the report name for which you want to create a TCode .

 

  • Go To Transaction SE93 and Create a Transaction say ZTEST of type Transaction with Parameters( Parameter Transaction)
  • On the Transaction Create Page, enter the Transaction as “START_REPORT“, Check the “Skip Initial Screen Checkbox”, Check the “Inherit GUI Attributes” Checkbox. Refer to the screenshot below.
  • Inherit GUI Attributes will inherit the GUI settings maintained in the parent transaction, in this case, START_REPORT. (The GUI support checkboxes now gets greyed out)
  • Now in the Default Values section at the bottom of the screen, add the below parameters.
    • D_SREPOVARI-REPORTTYPE = RE
    • D_SREPOVARI-EXTDREPORT = KP<<2spaces>>01RPSCO_X<<23spaces>>{REPORTNAME}
  • For example D_SREPOVARI-EXTDREPORT = KP  01RPSCO_X                       ZTEST
  • Save your transaction and execute . The report will now work as a transaction.

 

 

Thanks for visiting  the blog. Hope it helps.

 

References:

  1. https://help.sap.com/doc/saphelp_nw70/7.0.31/en-US/43/0f955bc2086ff3e10000000a422035/content.htm?no_cache=true
  2. https://help.sap.com/viewer/2b28ffa716c24348903f8ffbfeb81df8/7.5.6/en-US/bce6057811a311d295780000e82de14a.html?q=Parameter%20Transactions%20
3 Comments
You must be Logged on to comment or reply to a post.
  • Thanks for sharing, Abhilash!

    There are a couple of ways to improve these types of blogs.

    1. Add an explanation why this or that action is performed (unless it's obvious). For example, you're writing "Check the “Inherit GUI Attributes” Checkbox" but why? What does it do?
    2. Indicate that there is more to the subject than just a specific example described. What this blog post is describing is a process of creating a parameter transaction. This can be created for may other reports, not just this particular one.

    Add reference materials, e.g. this is an older Help article from the top of Google search, there is probably a newer entry somewhere: https://help.sap.com/doc/saphelp_nw70/7.0.31/en-US/43/0f955bc2086ff3e10000000a422035/content.htm?no_cache=true