Front-end printing with control technology

SAP has introduced a new front-end printing method recently. Have a look at note 821519. This method does not use SAPLPD and communicates directly with the Windows Spooler. You can now also choose which local printer to print to.Given you have the latest support packages it can even be used from 46C systems.

Functional Enhancements Schedule for BI in SAP NetWeaver 7.0

SAP regularly updates this nice document with the planned new capabilities of BI in Netweaver 7.0 in future support packages. It nice to see what they have in stall for us!

Netweaver 7.0 Support Stack 13 : Get All New Data in Source Request by Request

In SAP NetWeaver 7.0 SPS 13, the following enhancements are available in the data transfer process (DTP) in BW which is quite helpful in loading large datasets :

In DTP maintenance, you can specify that a DTP request is to get only one source request. By doing this, you can prevent DTP requests from becoming too large. Until now, when this option was used, only the first source request was retrieved. To get all source requests one after the other, the DTP had to be executed manually a number of times. You can now specify in DTP maintenance that the DTP is to get all new data from the source, one request after another. This makes it easier to process mass data using process chains and helps to reduce the total cost of ownership (TCO). The function also has a positive effect on the process monitor display in the process chain log view: When a DTP retrieves all new data request by request, rather than displaying just one request, the system displays a list of DTP requests.

Source

ST03 Statistics Retention Times

When you install a new SAP system, it does not keep the ST03 statistics for very long times.
You can change the retention times , see the screen shot below.

Single-Sign-On : New Wizard

SAP recently released a new (web dynpro based) wizard to help you in stetting up Single-Sign-On (SSO2) in your WebAS Java system. You can download the wizard and it documentation from SAP Note 1083421.

BW upgrade to BI 7.0 - New Web Reporting

You've probably heard about all the new functionality that comes BI 7.o , especially around web reporting. You can actually upgrade to BI 7.0 "as is" without having to do all the BI-JAVA stuff but then you won't be able to use the new web reporting functionalities that come with BI 7.0 like :

• New BEx Web Application Designer (Unicode, Command Wizard, ...)

• Exporting to PDF and Printing

• Integrated Planning

• Drag&Drop (Analysis Web Item)

• Web Items (Container Layout, Menu Bar, Tab Pages, Button Group, ...)

• Formatted Reporting with BEx Report Designer

• Document Integration with storage in Knowledge Management

To use the new functionalities you need a BI-JAVA stack, in essence a Netweaver Portal with BI business packages installed on it. You can either utilize your existing Portal or install a dedicated Portal for BI Web reporting.

SAP has a comprehensive note regarding setting this, see Note 917950 - SAP NetWeaver 2004s: Setting Up BEx Web. Also check the handy attachments to the note .

One thing I can add to this : Please try and run this on a 64bit Portal as the BI reports use a lot of memory on the Portal's J2EE. The reason for this is that the query data is transferred to J2EE as a whole during runtime, and we how big BI queries can be! (Note 996600 - 32 Bit platforms not recommended for productive NW2004s apps, Note 1044330 - Java parameterization for BI systems)

List of SAP Network Ports

Struggling to remember all the network ports used by SAP? On the SDN there's this helpful document on all the SAP Network Ports.

Import/Export Configuration Objects in XI

When you export/import XI configuration objects from one XI system to another you need to define transport targets in the SLD.See this SAP Help document : http://help.sap.com/saphelp_nw70/helpdata/en/ef/a21e3e0987760be10000000a114084/frameset.htm

Enable Debug Mode in J2EE Server Node

Sometimes a developer asks you to make a J2EE server node debug able. To do this, launch the J2EE Config Tool (usr/sap//instance/j2ee/configtool) . Then click on server instance node and in the right pane navigate to the Servers Debug tab. There you must select the Debuggable tick box as well as the Enable Debug Mode tick below it.See the screen shot below.

Check if the integrated J2EE is running from SAPGUI

If you run a dual stack system (ABAP + Java) and want to check if the integrated J2EE is running (without logging onto the O/S or using web browser) you

can do it in SAPGUI.

Execute transaction SMICM, Menu GoTo -> HTTP Server -> Display Data

In the next screen look for the line 'J2EE Server operational = TRUE', this means it’s running, if not it will be FALSE.

Migration of ST03N statisitics during upgrade to Basis 7.00

In Basis release 7.00 SAP developed a completely new workload statistics collector to meet the requirements of large systems. After you upgrade to Basis 7.00, you can no longer display workload statistics data in ST03N that has been entered before the upgrade.

To keep the ST03N history data you need to export it before the upgrade and import it afterwards. See Note 1005238 and 1006116.

After importing the old data (for instance you old 46C system) the ST03N data will look like this :

I took about 45 minutes to export the data before the upgrade and about the same to import it again after the upgrade.