Problems with the planning modeler and the planning wizard

Symptom:
You cannot start the planning modeler or the planning wizard, or they terminate with error messages.

This note describes the basic procedure for isolating problems with the planning modeler or the planning wizard and for providing information that SAP support requires to solve such problems as efficiently as possible. Below, the term planning modeler is used to refer to both the modeler and
the wizard.

Solution:

1. The ABAP back end and Web Dynpro Java must have the same Support Package version. You can determine the Support Package version for Java as follows:

a) Go to the start page of the J2EE Engine: http://server.company.com:port (Note that you must adjust the host server.company.com and the port accordingly).

b) Choose "System Information" and log on with the administrator user.

c) Under "Software Components", choose "all components".

d) In particular, check the version of the BI-REPPLAN and BI-WDALV software components.

2. When you start the planning modeler, the web browser issues one of the following messages "The page cannot be displayed" or "Application stopped" and it does not even display the initial screen of the modeler. There may be several reasons for this problem. To analyze this problem, proceed as follows:

a) If you used Transaction RSPLAN in the SAP GUI to start the planning modeler, then you must appropriately maintain the "Settings for Starting the Planning Modeler" in the Implementation Guide under 'SAP NetWeaver' -> 'Business Intelligence' -> 'BI-Integrated Planning'.

b) Check if the J2EE Engine is running. To do this, call the start page of the J2EE Engine (for example, http://server.company.com:port). If the system issues the message "The page cannot be displayed" at this stage, the J2EE Engine is not running.

c) Check if the Web Dynpro framework is running: Call a Web Dynpro application from the Web Dynpro framework, for example, the Web Dynpro test application
http://server.company.com:port/webdynpro/dispatcher/sap.com/tc~wd~samples~testsuite~uuie/TestSuiteUUIE. If you cannot start this test application, there is probably a problem with the Web Dynpro framework.

d) Check if the related software components are deployed: Call another Web Dynpro application from the software components BI-REPPLAN or BI-WDALV. If you cannot start the modeler http://server.company.com:port/webdynpro/dispatcher/sap.com/bi~plan
~workbench1/Modeler or the wizard
http://server.company.com:port/webdynpro/dispatcher/sap.com/bi~plan~workbench1/Wizard
or the ALV test application http://server.company.com:port/webdynpro/dispatcher/sap.com/bi~alv~
sample/TestALV the reason may be that the respective software components are not
deployed on the J2EE Engine. If necessary, contact your system administrator.

3. You have started the planning modeler,



o However the system displays only the empty tab pages of the planning modeler and the error message "Error obtaining JCO Connection".

o The system issues the error message "Password missing".

o The error message "Name or password is incorrect (repeat logon)" is displayed.

o The system issues the error message "com.sap.mw.jco.JCO$Exception:
(103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)".

In this case, the settings in the Implementation Guide for Integrated Planning may not have been maintained completely or correctly. Check the steps specified in the Implementation Guide under 'SAP NetWeaver' -> 'Business Intelligence' -> 'BI Integrated Planning' -> 'Maintain JCo Destinations'. In the Web Dynpro Content Administrator, ensure that the following JCo connections mentioned in the Implementation Guide function correctly:

o BI_METADATA and BI_MODELDATA
o WD_ALV_METADATA_DEST and WD_ALV_MODELDATA_DEST

To do this, use the test function in the Web Dynpro Content Administrator for JCo connections. The following settings are required for the two JCo connections BI_METADATA and WD_ALV_METADATA_DEST:

o The data type must be set to Dictionary MetaData.
o The connection type must use load balancing.

o Authentication must be set using a user/password.

o The user defined in the authenication must have authorization for
the adaptive RFC (see Note 677732 for further information).

The following settings are required for the two JCo connections BI_MODELDATA and WD_ALV_MODELDATA_DEST:

o The data type must be set to Application Data. Delete any incorrect JCo connections that may exist and create them again.

For detailed information about the Web Dynpro Content Administrator, see the SAP library under SAP NetWeaver -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Java -> Administration Manual -> Administration/Configuration of Web Dynpro Runtime Environment -> Web Dynpro Content Administrator.

In some cases, the error may be caused by a missing or incorrectly configured System Landscape Directory (SLD) connection. For information about this, read point 8 in this note.

4. The planning modeler issues an error message "RFC_ERROR_SYSTEM_FAILURE". This is probably due to an ABAP runtime error in the back end. Search for this runtime error in Transaction ST22 and add it to the problem message, as described in Note 46962. In
addition, use the Trace Tool (Transaction RSTT) to record a trace, as described in Note 899572.

In this case, note the following: Depending on how the JCO destinations are maintained, the ABAP username does not have to be the same as the user with which you have logged on to the planning modeler. This only applies for Single Sign-On (SSO). If a fixed ABAP user is entered in the BI_MODELDATA JCO destination, the ABAP runtime errors and the traces appear under this user name.

5. Th
e planning modeler sends an error message, which you cannot solve yourself. Use the Trace Tool (Transaction RSTT) to log a trace as described in Note 899572.

6. The planning modeler terminates with a Java runtime error: "Internal Server Error", "Failed to process request. Please contact your system administrator".
In this case, add the detailed Java error information to the problem message.

7. You start the Web Dynpro Content Administrator and you want to maintain required JCo connections for Integrated Planning. However, you require the buttons "Create JCo Destination" and "Maintain JCo Destinations", and the link "Create" to do this but they are inactive.

In this case, the System Landscape Directory (SLD) may be configured incorrectly or it may not be configured at all. For information about this, read point 8 in this note.

8. General information about JCo connection and System Landscape Directory (SLD)

The connection to the System Landscape Directory (SLD) is a basic prerequisite for creating JCo connections in the Web Dynpro Content Administrator. If an SLD server has not been defined, connect your system to the SLD before you begin to create JCo connections. Note that the used Web AS Java and Web AS ABAP are defined in the SLD as
the technical sytems.

You can find general information about SLD in the SAP Library under http://help.sap.com/saphelp_nw04s/helpdata/en/31/f0ff69551e4f259fdad799a229363e/content.htm

You can find general information about the connectin of technical systems in the SAP Library under http://help.sap.com/saphelp_nw04s
/helpdata/en/11/0dfe55e0c8fc4e910706a47ca6859b/content.htm.

Check if the SLD server is online and also if your system is connected to the SLD correctly. Use the "Check SLD Connection" function in the Web Dynpro Content Administrator to display and test the SLD settings in your system. The test display contains the SLD host name, the port, the SLD user and the SLD URL. Check if this information is correct.

You can also refer to point 2 in Note 947376: Troubleshooting JCo and AdaptiveRFC in Web Dynpro for Java.