Problem while customizing Portal MastHead.

Hi,
I am unable to customize my portal masthead.
I can't download the par file like "System Administration -> Support -> Portal Runtime -> Browse Deployment -> WEB-INF -> deployment -> temp (or) pcd -> com.sap.portal.navigation.masthead.par.bak ".
I'm using 2004s, EP7.0 , SP6
Unable to find the com.sap.portal.navigation.masthead.par.bak in the ZIP FOLDER.
Any valuable inputs to solve the prob are most welcome.Are there any blogs ?
thanks in advance.
Regards ,
Tilak

Hi,
Try to get the par directly from your server at:
\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
Also, please checkout <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d07bf112-1705-2a10-1a9f-d0a705e550fa">this link</a> for detailed explanation of changing the masthead.
Hope it helps,
Roy

Similar Messages

Problem while starting Portal Service from service configuration

While starting Portal service i am getting following error message:
"Server xxxxx:Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of handleTopic"
Please help me to reolve this error
Edited by: Pande Sagar on Jul 15, 2010 11:46 AM
Edited by: Pande Sagar on Jul 15, 2010 11:49 AM

Following is the PortalApp.xml file
<?xml version="1.0" encoding="UTF-8"?>
<application alias="sample">
<application-config>
 <property name="ServicesReference" value="com.sap.portal.ivs.connectorservice,com.sap.portal.ivs.internalconnector"/>
</application-config>
<components/>
<services>
 <service name="sample">
 <service-config>
 <property name="className" value="sample"/>
 </service-config>
 <service-profile>
 <property name="test" value="na"/>
 </service-profile>
 </service>
</services>
</application>
sample.java file
package samp;
import com.sapportals.portal.prt.service.IServiceConfiguration;
import com.sapportals.portal.prt.service.IServiceContext;
public abstract class sample implements Isample{
private IServiceContext mm_serviceContext;
 public void init(IServiceContext serviceContext)
 mm_serviceContext = serviceContext;
 public void afterInit()
public void configure(IServiceConfiguration configuration)
 public void destroy()
public void release()
public IServiceContext getContext()
 return mm_serviceContext;
 public String getKey()
 return KEY;
Isample Interface
package samp;
import com.sapportals.portal.prt.service.IService;
public interface Isample extends IService
 public static final String KEY = "MySample.sample";
 public String hi();
Edited by: Pande Sagar on Jul 19, 2010 2:04 PM
Its getting deployed properly but from system administration >> system configuration >> service configuration >> from application >> administrate service >> List of services >> HERE ITS GIVING AN ERROR >> Error in the listener class com.sap.ip.portal.admin.portalanywhere.QueryHandler during the process of handleTopic
Edited by: Pande Sagar on Jul 19, 2010 2:06 PM

Problem accessing custom Portal DB Table using default Datasource in VA

Hello,
I have a PAR application which tries to connect to a custom DB table defined inside the Portal DB Schema. The application uses a JNDI lookup to JDBC Connection service and uses the default DataSource (SAPJ2EDB/SAPSR3DB) defined in Visual Admin. However it gives the folowing exception while running a SQL query on the custom table,
SQLException::The SQL statement "SELECT COUNT(*) "ROWCOUNT" FROM "<Z Table Name>"" contains the semantics error[s]:
- 1:34 - the table or view >><Z Table Name><< does not exist.
I can connect and execute a SQL using the same defualt DSN on any of the standard Portal Tables like, ume_strings
Any ideas where its failing for the custom table??
I can create a new DSN in Visual Admin but would like to use the default DSN privided by the J2EE engine.
Thanks
Sandip Agarwal

Hi,
So you can execute that exact SQL statement for example via the SQL Query tool? Does that Z table actually exist in the DB? Are you just using the table name or do you fully qualify it like master.ztable (e.g. are you telling it what db to use?).
Hope this helps,
Simon

Problem while opening Portal

Hi,
When i click on any link on my portal home page, the status bar showing the message, "Done but Error on page" and nothing is getting opened.The address bar showing the following URL....
"http://ps5207:50300/irj/portal?standAlone=true&InitialNodeFirstLevel=true&windowId=WID1196673533980"
Any one can help to resolve this.
Thanks
Sri.

Hi,
As you suggested i used fully qulalified domain name like host.companyname.co.in, but still the no further link is getting opened. Can you identify the problem at least by look at the URL it is giving when click on any link...here is the URL.
"http://ps5207.persis.co.in:50300/irj/portal?standalone=true&initialnodefirstlevel=true&windowid=wid1196673533980"
Thanks
Sri.

Customizing portal masthead

Hi Team,
We have a requirement where in the user can change the portal language (English and German) after logging into portal by clicking on respective country flags which should be enable on masthead. Portal personalization role is already enable for the users but they want a link directly on masthead for changing to language English and German.
Incase anyone of you worked on similar requirement can you please share the process/feasibility of the task and any cons in implementing this on masthead.
regards
Bharadwaja

Well i have not done simillar requirement but you can refer to SDN itself. If go to SDN masthead, there is any option for language change. On click of that option an url parameter is added and portal is redirected to it. Probably you can take idea from here.
It is actually calling a java script function ... below one
function changeLanguage(language){
        var url = document.location.pathname;
        var url1 = document.location.href;
        var langParameterName = 'language';
         var langParameter = langParameterName + '=';
        var lan = getUrlParameter(langParameterName, url1);
        var newUrl;
        // no language paramater set
        if (lan == null) {
            newUrl= url += '?' + langParameter + language;
        } else {
            newUrl = url1.replace(langParameter + lan, langParameter + language);
        document.location.replace(newUrl);
Edited by: Mahesh K on Nov 29, 2011 6:22 AM

Problem while uploading Portal Theme into R/3 System?

Hello Guru's
I am trying to upload Portal Theme into R/3 system.
We have a program which will upload to a given path.
T.Code SE38 Program name BSP_update_mimerepos.
When I upload the theme using the program I get some folders,
like Common, r, UR
when cross checked with the standard I see css files are missing when uploading.
please help me on resolving this.
Thanks in Advance.
Points will be rewarded for helpful inputs.
Regards,
Pramod

solved went with WD_THEMES report to upload the theme to R/3 system.
search in forum to find out the solution.
cheers-
Pramod

Welcome Area Padding in Portal Masthead

I took a copy of the SAP Tradeshow theme and began to modify it based on my requirements. The background is white with Welcome Area displaying text in bold / italics / gray. However, I can't seem to get rid of a dotted rectangular box that appears to adjust its size whenever I change the settings for the "padding" in the Welcome Area. After login, it seems that the cursor focus is actually on this padding box considering the dotted lines go away if I click somewhere else on the page.
Has anyone seen this issue before? Suggestions?

Hi all
The focus set for the Welcome Area is set due to the javascript function document.<some_element>.focus()
In the masthead this is set for the Welcome Area. Now if you have a closer look at the portal component com.sap.portal.navigation.masthead you will notice the jsp page for the masthead: HeaderiView.jsp under PORTAL-INF\jsp
In this jsp page is the function:
function setFocusOnHeader()
 if (document.getElementById("welcome_message").currentStyle.display != "none")
 document.getElementById("welcome_message").focus();
 else if (document.getElementById("header_notch").currentStyle.display != "none")
 document.getElementById("header_notch").focus();
Here you can see exactly where Welcome Area is getting the focus...so how do you "FIX" it?
- Create a copy of the masthead portal component
- Change the jsp function to not set the focus
- Re-package the new custom portal masthead component (com.yourcompany.portal.navigation.masthead) and deploy
- Create a new iView based upon this par file and attach to the framework page
Voila!
Cheers
Ankit
PS - If this isnt easy enough to follow then I may look at putting together a blog at some stage with this and other enhancements to the masthead!

I face a problem while making a confirmation on portal.

Hello ,
Can anyone help me I am facing a problem while making confirmation in the portal.
the system pops up an error as mentioned below. Please help
 Folgender Fehlertext wurde im System SRP prozessiert: Speicherungsform der Produkt-ID ist im Customizing noch nicht definiert
 Der Fehler trat auf dem Applikationsserver eccprd-srp_SRP_50 und im Workprozess 3 auf.
 Die Abbruchart war: TH_RES_FREE
 Die ABAP-Aufrufhierarchie war:
Form: READ_SETTINGS of program SAPLCOM_PR_CONVERSION
Function: CONVERSION_EXIT_PRID1_INPUT of program SAPLCOM_PR_CONVERSION
Function: BBP_PDH_PRODUCT_READ_BUFFER of program SAPLBBP_PDH
Form: GET_LOCAL_PRODUCT of program SAPLBBP_ECI
Form: APPLY_OLD_MAPPING of program SAPLBBP_ECI
Function: BBP_PRODUCT_MAP of program SAPLBBP_ECI
Function: B31I_PO_GETDETAIL of program SAPLBBP_BD_DRIVER_31I
Function: META_PO_GETDETAIL of program SAPLBBP_BD_META_BAPIS
Function: BBP_BE_PO_GETHISTORY of program SAPLBBP_PDH_HISTORY
Function: BBP_PDH_SEARCH_PO_SUBLIST of program SAPLBBP_PDH_SEARCH
Best Regards,
Sairam

Hi,
Pls see if the foll notes are useful.
Note 911217 - Copy vendor product number from contract search help to PO
1047769 - No returns for search by Product ID in Monitor Shopping Cart
Note 1023012 - BBPSC: Long product ID triggers short dump
BR,
Disha.
Pls reward points for useful answers.

Problems while migrating PDK applications from Portal 7.1 to Portal 7.3

Hi All,
I am facing a problem while migrating a PDK application from Portal 7.1 to Portal 7.3.
Since Portal 7.3 doesnt support PAR files any more it provided with a tool to convert the PAR to an EAR file and deploy the resultant EAR to the new portal.
I converted the PAR into EAR and deployed the file but the application is not executing. When I looked into the log files i found the following exception. The application is not able to identify the tag "documentBody". I checked the protalapp.xml and the "SharingReference" is properly maintained in the file but the error message suggests that its not able to fine the reference to the tagLib uri maintained in the portalapp.xml
Now my question is why is it not able to obtain a reference to the taglib? Did any one face similar problem previously. Can you please provide me with any document for migrating / developing PDK application for Portal 7.3
Parser [PRT] - JspParseException is thrown while parsing JSP file </SAP/sap/POD/J00/j2ee/cluster/apps/TestOrg.co.uk/TestOrg~cas~ptlsvc/servlet_jsp/CASPortalService/root/WEB-INF/pagelet/CASFramework.jsp> :
com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name [documentBody].
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:969)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:994)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:994)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:69)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.GenerateJavaFile.generateJavaFile(GenerateJavaFile.java:72)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:272)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.generateJavaFile(JSPProcessor.java:196)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:128)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassName(JSPChecker.java:377)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.compileAndGetClassName(JSPChecker.java:306)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassNameForProduction(JSPChecker.java:236)
Thanks in advance
PK

Hi Amit,
Thanks for your reply. I could see some progress after "thoroughly" going through those links. Thanks a lot (gave points too )
Now I am facing another problem. The application did deploy successfully but with a warning. When i checked the warning it says that the deployment was successful but can not be started.
The log file has the following error message.
Global [startApp] operation of application [newsint.co.uk/newsint~cas~ptlsvc] finished with errors for [5] ms on server process [2721950] [
>>> Errors <<<
1). com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application newsint.co.uk/newsint~cas~ptlsvc cannot be started. Reason: it has hard reference to the following resources, which are currently not available on the system: hard to SAPPORTAL/com.sapportals.htmlb (public) (f=true, cl=false); .
In order to start the application, components that provide the missing resources should be successfully deployed.
at com.sap.engine.services.deploy.server.ReferenceResolver.isResolved(ReferenceResolver.java:137)
at com.sap.engine.services.deploy.server.LifecycleController.startReferencedComponents(LifecycleController.java:173)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:200)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:166)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhases(ParallelAdapter.java:465)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:605)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1828)
I dont understand why is SAPPORTAL/com.sapportals.htmlb is not available. As per my understanding it is some thing that should be available with the portal server by default.
Any hints from any one?
thanks in advance
PK

Problem while logging in Portal

Hello,
I have encountered a problem while logging on the portal, the error is :
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/every_user/general/defaultDesktop/frameworkPages/frameworkpage/com.sap.portal.layoutPortal1_Framework
Component Name : com.sap.portal.layouts.framework.framework
Error occurs during the rendering of jsp component.
Exception id: 01:14_23/03/09_0012_44078550
Please suggest how to solve this problem.
Thanks in Advance
Rakesh

Hello Jan,
please find below the trace log of the error generated -
#1.5#02004C4F4F50005C000000C800000ADC000465BA62822BB5#1237751097296#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#SAP#441##ecc6.myecc.com_ECC_44078550#SAP#ec23e450171911de946902004c4f4f50#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Exception ID:01:14_23/03/09_0012_44078550
[EXCEPTION\]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : pcd:portal_content/every_user/general/defaultDesktop/frameworkPages/frameworkpage/com.sap.portal.layoutPortal1_Framework
Component class : com.sapportals.portal.pb.layout.PageLayout
User : SAP*
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
     at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
     at com.sapportals.portal.pb.layout.PageLayout.doContent(PageLayout.java:44)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.pb.PageBuilder.includeLayout(PageBuilder.java:936)
     at com.sapportals.portal.pb.PageBuilder.doContent(PageBuilder.java:479)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.component.CachablePortalComponent.service(CachablePortalComponent.java:273)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.navigation.PortalLauncher.doContent(PortalLauncher.java:60)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sap.portal.navigation.Gateway.service(Gateway.java:126)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
     at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:116)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
     ... 56 more
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
     at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
     at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
     at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
     at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
     at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
     ... 59 more
thanks in advance.
Rakesh

Error while loading the custom portal transaction

Hi,
After the recent ITS Patches applied, our custom portal transactions are not work fine.
Some of the fields are displaced from their position and printing in abrupt position of the screen.
Transaction like address change, direct doposit screen... their fields like country key, bank key are not printing in the exact position in the screen.
This problem started only after appling the recently released ITS patches.
It's highly URGENT.. please help.
Saurabh Garg

Resolved

Problem while creatin a site customer

dear all,
I m facing a problem while creating Customer for the Site from WB01.
The following Error is coming " KNVV_CHSPL does not exist in the status table (TMOD*)".
Kindly help me solving this issue.
Regards
Harshita Saxena

Hi Arshita,
This issue is corrected. You should make a search in SAP Marketplace. There is a note to correct that issue.
I cannot search from my place (mobile handy device) but you should be able to find it easily in LO-MD-BP-CM or FI-AP* or FI-AR* + TMOD* or the error number.
The note is quite recent. Probably less than 6 months.
reward points if helpful.
BR

Problem while saving date field in custom table

Hi,
Iam facing the following problem while saving a date field in custome table
i have a date field zdate in which the value is 02082010.
now when i try to insert this value in the custom table it is getting updated as 20/10/0208 , but it should be 08/02/2010
How can i correct it..
Regards
Kumar

just before saving u might have to use a string reverse FM and then save it..
CALL FUNCTION 'STRING_REVERSE'
EXPORTING
    STRING          = p_string
    LANG            = sy-langu
IMPORTING
   RSTRING          = r_string
EXCEPTIONS
   TOO_SMALL        = 1
   OTHERS           = 2

Strange problem while clearing a customer

Hi everybody
I am encountering this strange problem while trying to clear some open items for certain customers. Though these customers have open items on them (checked in BSID and FBL5N), the system is giving a warning message saying that there are no open items on the customers while trying F-30 and F-32.
The only thing that was different for these customers from the rest was that these customers had some transactions which were supposed to be cleared through AP payment run. (transactions for customer payment).
Can anybody explain why the system was not considering these line items as open while accessing F-30 and F-32??

Hi,
- check SAP Note 136754
some table fields in the missing documents using Transaction SE16. The following conditions must exist:
BSIS-XOPVW = X (Indicator: Open item management, only for G/L accounts)
BSEG-XOPVW = X (Indicator: Open item management)
BSEG-AUGBL = space (clearing document number)
BSEG-DISBN = space (discount document number)
BKPF-BSTAT = space (document status)
BKPF-XSTOV = space (indicator reversal flag)
REGUS/REGUP -> see below
Should one or more conditions not exist, please note the following information:
1. BSEG-XOPVW <> X or BSIS-XOPVW <> X for G/L account line items:
 The line item presumably comes from a time before you activated the open item management of a G/L account. Documents before this master record change do not contain this technical information. Use report RFSEPA02 if you want to bring the documents in line with the new master record. You must refer to the documentation of this report.
 Because there may be problems subsequently acivating open item management, RFSEPA02 was changed as of Release 4.5A so that it cannot be started without modifications. SAP wants to make sure you are familiar with the problems, which may result from activating open item management. You can however restart RFSEPA02 when you have deactivated the line:
 leave program.
2. BSEG-XOPVW <> X for open item account line items:
 This data status is not allowed. Contact the SAP Hotline.
3. BSEG-DISBN <> space.
 The line item has already been used within bill of exchange accounting.
4. BKPF-BSTAT <> space.
 This is a document with a special function, for example a sample document or recurring entry document. Generally these are not taken into account in clearing transactions.
5. BKPF-XSTOV <> space.
 The document was flagged for reversal. Only if you cancel the reversal flag, can you clear the document again. You can do this by removing the planned date for the reverse posting (BKPF-STODT) in the document header using Transaction FB02 (Change document).
6. REGUS/REGUP:
 Look at table REGUS using Transaction SE16. Enter the account (KONKO) in the selection screen. If you selected an entry, use the information Run date (LAUFD) and Identification (LAUFI) in Transaction F110 (payment program). Check the status of the payment run. If only the proposal was carried out, the documents proposed for payment are blocked for other clearing transactions. It is only when you delete the proposal run that the items are taken into account again in the clearing transaction.
Rgds.

Facing a small problem while executing WDA application from portal

Hi Experts,
I developed web dynpro for ABAP application and placed table UI control, which contains 270 records. Executing from SE80, it is working fine and showing clearly all records.
This application integrated in portal, while executing this applicaiton from portal, it is working fine and showing all records.
Here I facing a small problem i.e Pager ( footer area ) of table.
When the table is displayed there are the small box in the below of the table showing ROWS 244 of 270.
244 will be available in a small box. this 244 is not showing clearly, while executing from portal ( last digit 4 displying half part only). but 244 showing clearly while executing from SE80.
Kindly suggest how to resolve this problem.
Thanks & Regards
Sridhar

Hi Gopi Krishna,
Thanks for your time. From SE80, it is working fine and showing clearly row number. There is no property for increase width of small box, which contains current row number).
Facing problem while executing from portal.
Thanks & Regards
Sridhar

Problem while customizing Portal MastHead.

Similar Messages

Maybe you are looking for