Friday, May 23, 2008
Monday, September 03, 2007
The metadata of "ITE" "TEMPLATE_PARAMETERS" are incorrect for parameter "START_STATELESS_INTERVAL"
activate Bex items from BI Content. Bex Web template (BTMP) and Bex Web Item (BITM)
RRI report to report interace RSBBS transaction
The url is maintain in the portal system -ITS
ITS - protocol
ITS server : ex - hjoybw.hjoy.com.tw:8000
for connect to R/3..u might have to maintain R/3 system in protal
Thursday, August 30, 2007
Monday, August 13, 2007
Calculation of result package via end routine
Note: All not overwritten field values within the routine are transferred from the corresponding source fields. This means, all fields not supplied by the transformation source are send with initial values to the transformation target.
The structure of Result_package is same as target structure and can not be changed.
Be careful when a target supplied data with 2 transformations which both supplied only partial fields of the data target, if you use end routine the data will be overwritten with initial value.
Sunday, August 12, 2007
Delete overlap request in bw 7.0
Pls create a process chain.
1. Add Delete Overlapping Requests from InfoCube .
2. In the deletion selection check : Conditions:
mark : Only delete request from same DTP
Only delete full DTP request
Only delete full DTP request from Same source
Then Mark : Overalapping.
In the DTP : Add date in the Filter .(Cal/Year Mth) ..You can use variable also.
Without this it won't work.
According to our developer, please note:
It is not supported to use the 'overlapping deletion process' with
DTP-Requests. It will not work and is not nessessary anymore.
Monday, June 25, 2007
BIIP Planning modeler missing password
Note 919850 - Problems with the planning modeler and the planning wizard
edit the 4 rec connection mentioned in note
Sunday, June 24, 2007
J2ee run in safe mode
J2ee run in safe mode...use config tool to to switch
Safe Mode in the J2EE Engine Locate the document in its SAP Library structure
When upgrading/patching the J2EE Engine and the components running on top of it, the system automatically sets the J2EE Engine in safe mode for precaution reasons. That is, on the next restart the system will leave stopped all the server processes and dispatchers in the cluster, leaving only the central instance with one dispatcher and one server process running. This makes it faster and less resource-heavy to perform the desired operation.
Thus, after the upgrade/patching procedure, you may need to manually disable the safe mode of the J2EE Engine and to restart the whole cluster.
If the J2EE Engine is in safe mode, you will see a warning message or an indicator:
· In the SAP MMC, you will see an indicator in the Status field of the JControl process.
· In the Visual Administrator when you log on to the J2EE Engine, a warning message will be displayed.
· If you are using Telnet client to connect to the J2EE Engine, you will see an indicator.
· In the Config Tool, you can check the mode in which the J2EE Engine is running by choosing File ® Safe Mode.
Use the Config Tool to enable/disable the safe mode function of the J2EE Engine:
1. Start the configtool script file from the /usr/sap/
2. Choose File ® Safe Mode.
A dialog box appears.
3. From the Safe Mode Enabled drop-down list, choose:
¡ Yes to enable safe mode.
¡ No to disable safe mode.
4. Choose OK.
5. Save the settings and confirm all the messages that are displayed.
6. Restart the J2EE Engine.
End of Content Area