Hello
You can get the approver of the PR from rule 20000026 (Go to Transaction PFAC) or FM ME_REL_GET_RESPONSIBLE.
Regards
Sandy
Hello
You can get the approver of the PR from rule 20000026 (Go to Transaction PFAC) or FM ME_REL_GET_RESPONSIBLE.
Regards
Sandy
Hi Fred,
Yes, I was able to activate the XBO.
1508 has this enhancement of adding nodes to standard BOs.
Just the definition
var thissegmentsobj : elementsof this.SegmentCombos;
is causing error during activation.
Are there any other ways of populating nodes other than using elementsof?
-M
Hi everyone!
I have problemes created a SaleOrder in B1if.
I have a scenario where I read xml file to create the order. First, I do a sql query from a table to get the values I'm going to use. Then I have a conditional atom to decide if I can read the xml file. Then I read the xml file and then I have other conditional atom to decide if I have to create a Sale order or an Invoice, then I have a transformation atom to prepare the info to generate the order sale or the invoice. When I test my scenario I don´t recibe any error, in fact the info says all are fine, but the order sale or the invoice doesn´t exist. I don't know what is the problem with this. Can anyone help me please? Thanks in advanced
Hello Davide
Currently we only support upload of around 1000 - 2000 entries via the CSV file. In case you would have to upload more entires, please get in touch with the Support colleagues and then we could upload the data from the backend.
Regards
Viswa
Hi Mahesh,
Where are you writing this code?
What is the error message?
Can you try with "elementsof Opportunity.SegmentCombos;"?
Best Regards
Fred
NB ABAP can work as a service provider (consumer of IdP) not as an IdP which NW Java can do. There is a significant difference.
NW Java, can however be configured to use ABAP user store, which you then could consume in the ways you mentioned above.
Generally it has been my experience that when companies start thinking about SSO they rise above just thinking about SAP now-a-days, so haven't seen this implemented nor know of any specific doco.
Cheers,
Chris
Hello
Yes it it is possible.Refer to links below
Spool Data as PDF In a Work Item
downloading and sending report output as pdf and mail to different vendors
Convert ABAP Report's Output into PDF Format..
Generate PDF from ABAP List Output - Code Gallery - SCN Wiki
Converting Print spool output in to a PDF in SAP
Regards
Sandy
Hi Madhu
Speak with your Basis Team,
Ensure they have all services for your process activated as well as all relevant configuration from the '000' client copied to your development client.
Regards
Arden
Hi Fred,
I am writing this in Root->AfterModify and also in an event.
Also tried Opportunity.SegmentCombos;
The errors I see are
Error 41 [Activate] Root: Error in activation of runtime object \XBO_Opportunity-Root-Event-AfterModify.absl
Error 42 [Activate] Syntax error in generated ABAP method \XBO_Opportunity-Root-Event-AfterModify.absl
thanks
-M
Hi All,
We need to hide the buttton Change and Approve button in UWL that button is available in backend aswell i was unable to find the ActionId of that button in Supported Action for this item.How to hide that button?
Please provide your inputs............
Regards,
Rahul.
Hi Martín,
Make sure your UI component matches the requirement of your BPC component.
Also try a new patch level.
Andy
Hi experts,
I have this error when i try run my Job:
2716 5024 CON-120302 06/08/2015 20:44:58 ODBC call <SQLDriverConnect> for data source <xxxxx> failed: <[Microsoft][SQL Server Native Client 10.0][SQL Server]Login
In my datastore, i can read the tables of my database, but when i put this table with a target in my Job, start the error.
I have installed sap data services 4.2 sp5, but the server is in a diferent machine, but the comunication it is ok.
The database who i use in my job is in other server, but can connect into the database using de SQLServer client and i make queries,inputs of data and deletes.
I tried create a new datastore, i remake the connection, restarted the database server, created a new job server, a new repositoie and anything fix the error.
Regards,
Elton
Hi Martín,
have a look at note 2058257
solution is in note 2068917
Andy
Try the close button and see if that makes any difference.
I think your SP level might be old, try a later version of SP.
Andy
It appears the xml returned by HANA XS App isn't the expected format for Lumira.
|D1120BCB1C154110BB79B3EA35558E2E12fb|2015 08 06 19:27:59.902|-0500|Error| |>>| | |TraceLog| 8432| 41|qtp332051528-41 | ||||||||||||||||||||CS||EXCEPTION [OData |Generic OData 2.0 |ID:0]com.sap.connectivity.cs.java.ConnectionManager{com.businessobjects.connectionserver.ConnectionManager}.TestConnection: [com.sap.connectivity.cs.java.drivers.CSDriverError: A problem occurred while communicating with the provider. Detailed message: The element type "meta" must be terminated by the matching end-tag "</meta>".
at com.sap.connectivity.cs.java.drivers.DDKExceptionImpl.convertToCSException(DDKExceptionImpl.java:156)
at com.sap.connectivity.cs.java.JAVAGenericJob.<init>(JAVAGenericJob.java:75)
at com.sap.connectivity.cs.java.JAVAJob.<init>(JAVAJob.java:32)
at com.sap.connectivity.cs.java.JAVAOpenJob.<init>(JAVAOpenJob.java:39)
at com.sap.connectivity.cs.java.OpenJob.<init>(OpenJob.java:57)
at com.sap.connectivity.cs.java.ConnectionServer.getJob(ConnectionServer.java:382)
at com.sap.connectivity.cs.core.ConnectionServer.CreateJob(ConnectionServer.java:73)
at com.sap.connectivity.cs.core.ConnectionServer.CreateJob(ConnectionServer.java:120)
at com.sap.connectivity.cs.core.ConnectionManager.TestConnection(ConnectionManager.java:155)
at com.sap.connectivity.cs.api.trace.ConnectionManagerLogger.TestConnection(ConnectionManagerLogger.java:596)
at com.sap.hilo.datasource.freehandsql.internal.FreeHandSQLCnxSrv.testConnection(FreeHandSQLCnxSrv.java:453)
at com.sap.hilo.desktop.datasource.v2.freehandsql.services.CatalogService.execute(CatalogService.java:144)
at com.sap.hilo.desktop.h5v2.common.service.BaseService.execute(BaseService.java:33)
at com.sap.hilo.desktop.embeddedserver.httpservice.HTTPAdapter.execute(HTTPAdapter.java:89)
at com.sap.hilo.desktop.embeddedserver.DispatcherServlet.handleRequest(DispatcherServlet.java:107)
at com.sap.hilo.desktop.embeddedserver.DispatcherServlet.doPost(DispatcherServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1367)
at com.sap.hilo.desktop.embeddedserver.JsonPaddingFilter.doFilter(JsonPaddingFilter.java:80)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)
at com.sap.hilo.desktop.embeddedserver.configurator.internal.SecurityFilter.doFilter(SecurityFilter.java:59)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:484)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
at org.eclipse.jetty.server.Server.handle(Server.java:350)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)
at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:900)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:954)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:851)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
at java.lang.Thread.run(Thread.java:812)
Caused by: com.sap.connectivity.cs.java.drivers.odata.exception.CommunicationException: A problem occurred while communicating with the provider. Detailed message: The element type "meta" must be terminated by the matching end-tag "</meta>".
at com.sap.connectivity.cs.java.drivers.odata.helper.XMLHelper.parseXMLtoDOM(XMLHelper.java:65)
at com.sap.connectivity.cs.java.drivers.odata.ODataDriver.parseMetadataModel(ODataDriver.java:291)
at com.sap.connectivity.cs.java.drivers.odata.ODataDriver.connect(ODataDriver.java:219)
at com.sap.connectivity.cs.java.JAVAGenericJob.<init>(JAVAGenericJob.java:71)
... 42 more
Caused by: org.xml.sax.SAXParseException; lineNumber: 64; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>".
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347)
at com.sap.connectivity.cs.java.drivers.odata.helper.XMLHelper.parseXMLtoDOM(XMLHelper.java:47)
... 45 more
]
Hi Prithviraj,
Thanks, It worked perfectly, just what I needed.
Regards,
S. Gordon
Hi Nick,
So any other detailed error information is reported in the log file SAPupConsole.log?
And if you run the 2 commands below with user <sid>adm, what are the outputs of them?
sapcontrol -nr <instance number> -function GetSystemInstanceList
sapcontrol -nr <instance number> -function GetProcessList
Best regards,
Charles
Hi Jinwoo
I've already built a v12 SA MSI client install using the wizard which works fine but unfortunately unless I also run a v16 SA client MSI on the client machine, I get an issue with the v16 SA assembly not being found. I'm looking for a way to roll out an ADO.NET program that was built targeted to v16 SA on a v12 SA client machine that doesn't require me to install a full v16 SA client as well.
I'm trying to avoid having to build a project for SA v16 and another to support v12 of SQL Anywhere ie with a build assembly referencing ianywhere.data.sqlanywhere.v.4.5.dll v12.
Cheers
Allan
Dear vasanth,
Thanks for your reply.I have got it by thread mentioned program..
Best Regards.