How to Log Changes in Plan Data Using DataStore Object

Overview

In many planning project it is not only necessary to create new plan data but also to keep track how this new data originated. Thus a mechanism is necessary that logs all changes done in the plan data – either when new data is created or existing data is changed. Usually the logging information contains information about the user who has done the changes and the date and time when these changes where performed. This paper gives an example how the new logging BAdI delivered with SAPNetWeaver 7.0 EHP1 (SP6) can be used to log information about these changes in a DataStore Object. As the example is very generic the contained coding can be easily adapted to a given customer scenario.
 
Full Story --> Click Here
 
source: sdn. sap. com
author: sap

ABAP Transaction Codes Related to Java Administration

Overview

In a productive landscape, an SAP J2EE server/ SAP Enterprise portal or any other application based on the JAVA engine is in constant interaction with a variety of backend R/3 servers, be it UME related, internet application components (IAC's) like ESS or MSS, TREX etc. This guide describes the main TCodes from the ABAP end that can be useful to assist troubleshooting in such cases where connection is made from the j2ee server to the R/3 server or vice versa.
 
Full Story --> Click Here
 
source: sdn. sap. com
author: hemanth kumar

Step by Step Procedure to Create Logical File Name and Logical File Path

Overview

Document decribes the step by step procedure to create Logical File Path and Logical File Name.
 
for full story click here
 
source: sdn. sap. com
Author: Jaimin Soni

How to Work with F4 Input Help Effectively in BEX

Overview

This document helps to overcome the challenges while using F4 help in variable inputs and choosing filter selections. It talks about the introduction to F4 help settings and how they affect input help in Bex analyzer, Web and portal.
 
for full story Click Here
 
Source: sdn. sap. com
Author: Sreekanth S