ClickOnce is a runtime, you need the SP 16 "Install Executable" which is in the first column on the left.
-Dell
ClickOnce is a runtime, you need the SP 16 "Install Executable" which is in the first column on the left.
-Dell
Anne, have you found a solution for this issue? I am having the same problem.
Hi Gurus
We have a field defined as type base64binary - to which we need to cast an attachment as an XOP: Include MTOM attachment - how can I achieve this in the below UDF.
As we are able to get the attachment created - however, it needs to be cast as XOP Include as seen below.
The field name is FileAttachmentHandler - IF devlivered correctly the field should show like below on the target XML.
<ns0:FileAttachmentHandler>
<xop:Include href="cid:0aa38897-1525-44bc-93d8-05789234@example.jaxws.sun.com" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
</ns0:FileAttachmentHandler>
Is it possible to cast it to this field in the below UDF by modifying or is it something which can be achieved by XSLT or some other way ?!
Is it possible to get CID: from the below runtime - messages?! and insert it in to cid: xop
-<SAP:Payload xlink:href="cid:payload-00505696159F1EE5BFB5CDF1DA2D6E5A@sap.com">
Your help is greatly appreciated!!
Thank you,
Ritu
Below UDF which I got from earlier forums posting - helps to create attachment successfully:
GlobalContainer globalContainer = container.getGlobalContainer();
String decodedContent="";
byte[] decodedValue = DatatypeConverter.parseBase64Binary(var1);
decodedContent=new String(decodedValue);
byte[] convertedInput = decodedContent.getBytes();
OutputAttachments outputAttachments = globalContainer.getOutputAttachments();
Attachment outputAttachment;
String contentType= "application/octet-stream";
outputAttachment = outputAttachments.create("Myfile.pdf", contentType, convertedInput);
outputAttachments.setAttachment(outputAttachment);
return "";
Hi Sathish,
thanks for your answer. I already solved the problem. Generally the coding for the getData()-Method is correct. It was just a little timing problem. The application still has to wait until the datasource is initialized and only than you'll be able to get Data. That's it ;-)
But now i have another problem:
Some of the Hana Live Views for Utilities (e.g.: sap.hba.isuecc/InstalledUtilitiesDeviceQuery) have a direct input parameter, witch has no relationship to a database column:
Using the following code does not work: DS_1.setVariableValueExt("P_UtilsDeviceKeyDate", "20160408");
You'll get the following error at runtime:
I also tried the date values "2016-04-08", "08.04.16", "08.04.2018" and "2016/04/08", but the result is always the same.
So i temporary switched the parameter type to "column" and assigned a date column from the associated hana view. This works ... but this is only a workaround. In this case i only can choose values, that are stored in this column. But often you want to set a key date, independently of the real date values.
It seems, that it is absolutely necessary to have master-values/-data in the hana view. Is this right? If so, i had to open an incident. This feature is a must have in reporting:
E.G.: You have a start date and an end date for an contract and you want to count all active contracts at a specific key date.
kind regards
Berndt
Hi:
Thank you in advance for your support.
It is possible to hide a package?
If its possible, how can you hide a package?
It is possible to hide a package and avoid that others developers can see it?
If its possible, how can you do it?
It is possible to hide a package and avoid that others developers can edit it?
If its possible, how can you do it?
We are planning to upgrade our SAP Portal which is on NW 7.0 EHP2 to NW 7.4 . Our backend is ERP6.0 EHP6. We are using portal for ESS/MSS package and SSO to SAP.
Need some information on this area.
1. Can we directly upgrade Portal to NW7.4 without any need to upgrade our backend system component.
2. Does TREX also need to be upgraded when upgrading portal .
Can some one share a step by step guide on how to upgrade portal on things . Yes i have am going through upgrade guide but someone who has done it before and capture steps will be helpful as i have not done portal upgrade before
Thanks
E o pessoal responde? a comunicação flui bem entre o pessoal por aqui?
Achei muito legal, quero aprender mais e mais sobre o ERP.
Alguma dica?
I have a request where I need to create an integrity report where I am looking at sales data and verifying that the payment terms are consistent on all items (rows).
Sample data:
Sales # | Line # | Terms Code
100 | 1.0 | N90
100 | 2.0 | N90
101 | 1.0 | N60
101 | 2.0 | P45
101 | 3.0 | N60
Notice that on SO 101, line 2.0 has a different terms code. I need to detect that and only display order 101 on the report.
I was looking at using the PREVIOUS operator in a variable like this:
=If(Previous([Payment Terms Code])=[Payment Terms Code]) Then 0 Else 1
but that looks at the Order 100 line 2.0 and would flag it incorrectly.
I am not sure how I can do this, but maybe using the IN operator some how. Suggestions?
Hi Swapnil,
that was not the problem. See also my reply to SATHISH BABU.
If you have a solution for my new problem ... just tell me.
best wishes
Berndt
If you explain what "I can not get this to work" means, it may be easier to provide help.
What do you mean? Do you want to increase the size of the rectangle you are showing in red color in the screen capture? I think it's not possible by using the parameters, you must do a modification of the standard.
Hi gurus,
I'm writing a SD custom report and I need to read pricing conditions from invoices. Everithing was going right until I've found an unexpected scenario which is causing wrong numbers in my report.
Let's say I have the following logic:
From A650 table, I'm reading a custom princing condition for the KUNNR. This gives me a KNUMH value.
According to the image, for tis KUNNR and Z320 condicion I can find two differente KNUMH values, validity dependent. This is OK.
KONP tables gives me the value to take into account for calculations for each KNUMH:
So I'll calculate based on 33,10% for 9032 and 34,10 for 39292. This is also OK for me.
However, here comes my problem. In KONV table I can find the following:
- Records for 9032 condition number and the value from KONP (33,10%). OK.
- Records for 39292 condition number and the value from KONP (34,10%). OK.
- And finally, records for 9032 condition number BUT 34,10%, which is not the value from KONP for this condition.
How is this possible? In my understanding, if the value is 34,10% the condition number should be 39292, right?
Is there a way to fix this? Am I wrong?
Thanks in advance.
Hi Jin,
It is not possible to upgrade the system without stack.xml .
Also I see that this is a IDES system. Upgrade of IDES system is not supported by SAP !!
Best Regards,
Gaurav
Hi Riz,
Fields from related nodes can be non-editable on UI in case if they instances don't exist.
In your case ROOT node instance exists but association on DESCRIPTION node doesn't return any instance and as a result corresponding fields are non-editable.
Kind regards, Aliaksandr.
I am not getting any program error
Its jus that sy-subrc = 8
Its failing at open dataset statement
Hi Raj,
Yes, that is possible.
DR AR-Customer CR Revenue + WBS
Regards,
Paulo
Hi Guys,
Can any one suggest regarding US Payroll Add - On for SAP Business One
http://help.sap.com/abapdocu_702/en/?url=ABAPOPEN_DATASET.htm
oh, you forgot LOWER CASE in the PARAMETERS. The consequence is that the full access path is changed to upper case i.e. /USR/SAP/TRANS/ECC/TMP/POONAM.TXT, which surely is not valid (USR doesn't exist, but usr exists.