INCOTERMS Qualifiers
Hi Experts,
can you please explain the difference, if the INCOTERMS have one of the below two qualifiers
'001' INCOTERMS part 1
'002' INCOTERMS part 2
does it have a significant difference?
Please suggest.
Thanks in advance.
MK
ca it be that your info record is a different level than your vendor master?
e.g. vendor master purchasing org data with inco terms is maintained at purchasing org level.
Info records can be maintained at puchasing org level or at plant level.
e.g. if you execute ME11 with plant entered, then you create the info record at plant level, without plant entered you create an info record at purchasing org level.
What level does your info record have? how was it created manually or automatic from a PO.
if from PO, had this PO Incoterm maintained, or was the incoterm added after the initial save step?
Similar Messages
-
Does incoterms can be used to refer the ownership transfer of goods?
Define Incoterms?
INternational COmmercial TERMS - Codification of international rules for the interpretation of the most commonly used terms in international trade. They define the terms of sale and the passing of risks for import and export of merchandise
Incoterms are the internationally recognized shipping terms that establish the respective liabilities of both the shipping party and the recipient. For example, a common shipping term is FOB (Free on board). The term can be further qualified by adding the loading port, for example, FOB Boston.
You can create condition records either:
Based solely on the first part of the Incoterm (for example, FOB)
Based on the combination of parts 1 and 2 (for example, FOB and Boston)
Freight Conditions
Freight condition type KF00 applies to each item in a sales document. During automatic pricing, the system searches for valid condition records that apply to this freight condition.
Freight condition type HD00 can only be applied to an entire document. You enter this freight manually during sales order processing. -
Control of Incoterms in creation of Shipment Costs
Dear All,
We calculate shipment costs (Through Transportation module in SD-Freight payment-Outwards) on calculation base A (Delivery) or B
(Delivery item) and do not want to calculate deliveries that have certain
Incoterms (for example, TOP-To Pay, where Customer makes payment to Transporter).
By default, the system always creates a subitem in the shipment cost
document for the corresponding calculation base for every delivery item or for every delivery involved.
We want to have Control over certain Incoterms where we don't pay to the customers. We want to restrict the users not to calculate Shipment Costs in TOP-To pay cases. Kindly help if any Userexits available for this scenario to handle.
Regards
SubratHi,
I think we have a similar requirement. For FCA transports is the transport cost zero. We have created a seperate condition in the cost procedure as a condition class A ( discount or surcharge ) in T_06. This has an access sequence assigned which uses a 9xx condition table (T_03) with fields Service agent f.stage ( TDLNR ) and
Incoterms ( INCO1 ). This enables us to maintain condition records in TK12. So FCA is maintained with 100 % deduction and thus no costs. -
In Adobe Bridge, when I try to open my camera raws, I get a pop up stating"Bridges parent application is not active. Bridge requires that a qualifying product has been launced at least once to enable this feature." What the heck? I have a PC and haven't had problems before.. I have adobe cloud and pay my monthly bill...
Have you opened Photoshop or any other Adobe app that Bridge works with? You need to do this if you've upgraded PS or just signed up for CC.
-
I just upgraded computers (PC w/Windows 8 64 bit) and I did a fresh install of my copy of Adobe Photoshop CS5 (along with Bridge and Camera Raw).
The install asked for serial numbers which I provided and the installation was a success - however, I can not view full resolution images, only thumbs
in Bridge and I can not open RAW files from my Canon 5D Mark III (though, I can my files with the older Canon 7D). I WAS able to view and work with
the newer RAW files on the older computer.
Under "Help", "Updates", it says they are available but after appearing to upload to my computers, I get this:
Adobe Bridge CS5 4.0.5 Update
There was an error downloading this update. Please quit and try again later.
Adobe Extension Manager CS5 5.0 Update
There was an error downloading this update. Please quit and try again later.
Photoshop Camera Raw 6.7 Update
There was an error downloading this update. Please quit and try again later.
There is then a link to customer service which brings me to this:
Creative Cloud Help /
Error "This serial number is not for a qualifying product" | CS6, CS5.5, CS5
What gives? It was a qualifying product a few months back. Even if Adobe stopped supporting CS5 (???), I should still have access to past updates
that I had already once received.
I tried 3 times in 1 hour - no luck in getting back to a state I was in only yesterday, and months earlier.
/MitchApparently, Adobe has very little interest in it's past customers unless they shell out more cash.
I have never seen such a move as this - to REMOVE support and older update links off the Web in an effort to force an upgrade.
My tech support stated (after first stating I was simply out of luck) that he was graciously allowed to make an exception and provided me with a link to support that is strangely
hidden and /or removed from public access.
Here is that link:
Adobe Update Support Web Site: 1-28-2015
https://www.adobe.com/support/downloads/product.jsp?product=39&platform=Windows
/Mitch -
Not able to see data in the qualifier table of the main tbl , Data Manager
Hi,
I have an issue of not able to see the data of two qualified table after populating them.
It is in mdm-5.5 ps4.
When populating data first time ,it shows up in those two table slots in the right side of the Data Manager.
However subsequently it does not show up in those slots , only by right click on the table and selecting "View/edit", the window pops up where those data shows up.
However unlike other qualified tables the data does not showup automatically for these two tables.
Appreciate any suggestion or feedback on this.
regards,
-reoYou may have checked the Filter Check Box next to the Qualified Lookup cell in Data Manager, when the current table is the Main Table.
You use the Filter Checkbox to limit the qualified table records by the current search selections.
Secondly, you have see if there are any Qualified Links to the main table record you are viewing.
If not, create the Qualified links in Data manager, for the main table record and the Qualified Table Record.
Once this is done, you will see the Display fields of the Qualified table for which the links exists for the given main table record.
Message was edited by:
Adhappan Thiagarajan -
Get Qualifier value from Qualified table
Hi,
I am trying to get all the qualifier value for a qualified table. What is the best way to do it. Can I use QualifierSearchDimension to search for all the qualifier value.
Re: Lookup [Qualified Flat] type field how to use as a query condition? link gives us a way to do this , but it talk about getting the non - qualifiers only , so How can we get the qualifier values.
The link Search Qualifier Fields : MDM Java APIs gives us a way to this , but it is using old Java API , does anyone know how to do it using MDM API SP06.
Thanks and Regards,
SubhasisHi Subhasis,
The Search API's will only search for a particular value in the qualified tables. In order to read all the qualifier and non qualifier for a record, please follow the below mentioned steps.
Assuming 'rec' is the variable that holds the reference for the current record.
MdmValue lookUpVal = rec.getFieldValuel(<Field Id of the field>);
com.sap.mdm.valuetypes.QualifiedLookupValue val = (com.sap.mdm.valuetypes.QualifiedLookupValue) lookUpVal;
// Get the total number of qualified records present for that field
int size = val.getValuesCount();
// Iterate through each qualified record to fetch the details
for(int i=0;i<size;i++){
MdmValue nqVal = val.getValue(i);
if(nqVal != null){
MdmValue incVal = val.getQualifierFieldValue(i,<Field Id of the qualifier field value>);
Regards,
Ponraj M
Edited by: Ponraj M on Jul 10, 2009 10:12 AM -
It says my apple id is valid- my ipad not qualified for i cloud
when i sign into i cloud it give this msg :my apple id is valid- my ipad not qualified for i cloud
what do i do now ?When you say "deleting app", which app are you talking about? And what, exactly, is the error message you are getting and from which app?
-
Clientgen does not fully qualify superclasses
I have datatypes that extend classes in a different package. When I use
WLS81 ANT task clientgen to generate client-jars from WSDL files obtained
from web services generated by servicegen, the superclasses are not fully
qualified in the generated java code, nor are there import statements for
the superclasses. This causes the generated code to have compile errors.
Other dependencies are fully qualified in the generated code, but the
superclass is not.
There mayThe WSDL is included below. Specifically,
com.starcomsoft.pp.database.BaseHelper does not get a fully qualifed
reference in the generated java code.
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://localhost:7001/webservice/"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12
="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2002/12/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
targetNamespace="http://localhost:7001/webservice/">
<types xmlns:tns="http://localhost:7001/webservice/"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap12
="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2002/12/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.starcomsoft.pp.common" elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.starcomsoft.pp.common">
<xsd:complexType name="AbstractSearchCriteria"
abstract="true">
<xsd:sequence>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.starcomsoft.pp.customer"
elementFormDefault="qualified" attributeFormDefault="qualified"
targetNamespace="java:com.starcomsoft.pp.customer">
<xsd:import namespace="java:com.starcomsoft.pp.database">
</xsd:import>
<xsd:import namespace="java:language_builtins.lang">
</xsd:import>
<xsd:import namespace="java:language_builtins.util">
</xsd:import>
<xsd:import
namespace="http://schemas.xmlsoap.org/soap/encoding/">
</xsd:import>
<xsd:import namespace="java:com.starcomsoft.pp.common">
</xsd:import>
<xsd:complexType name="Address">
<xsd:complexContent>
<xsd:extension base="stns:AddressHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="AddressHelper" abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:string"
name="addressOne" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="addressTwo" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="city" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="stateId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="zipCode" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ArrayOfCustomerGraphData">
<xsd:complexContent>
<xsd:restriction
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
base="soapenc:Array">
<xsd:attribute
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType"
wsdl:arrayType="stns:CustomerGraphData[]">
</xsd:attribute>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ArrayOfProfile">
<xsd:complexContent>
<xsd:restriction
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
base="soapenc:Array">
<xsd:attribute
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType"
wsdl:arrayType="stns:Profile[]">
</xsd:attribute>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="Contact">
<xsd:complexContent>
<xsd:extension base="stns:ContactHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ContactHelper" abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:boolean"
name="active" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="contactPoint" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="customerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="departmentId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="first" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="last" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:boolean"
name="primaryContact" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="title" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="type" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="Customer">
<xsd:complexContent>
<xsd:extension base="stns:CustomerHelper">
<xsd:sequence>
<xsd:element type="stns:Address"
name="billAddressData" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="stns:Address"
name="billToAddress" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="stns:Address"
name="shipAddressData" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="stns:Address"
name="shipToAddress" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CustomerAdjustment">
<xsd:complexContent>
<xsd:extension
base="stns:CustomerAdjustmentHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CustomerAdjustmentHelper"
abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:int"
name="adjustmentId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="amount" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="code" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="customerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="facilityId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="factorId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="methodId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="type" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="value" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CustomerGraphCollection">
<xsd:sequence>
<xsd:element
type="stns:ArrayOfCustomerGraphData" name="customerGraphDataValues"
minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CustomerGraphData">
<xsd:sequence>
<xsd:element type="xsd:string" name="code"
minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int" name="id"
minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string" name="name"
minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int" name="parentId"
minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CustomerHelper" abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:int"
name="accountStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:dateTime"
name="agingDate" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="agingDays" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="allowSplitOrders" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="balanceDue" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="stns:Address"
name="billAddressData" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="stns:Address"
name="billToAddress" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="billToAddressId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="billingAddressSourceCode" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="billingPartnerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="billingPartnerName" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="buyer" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:double"
name="creditAvailable" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="creditLimit" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="currencyId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="customerCode" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="deliveryPoints" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="departmentCode" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="dropSequence" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="facilityId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="financeChargePercent" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="fixedTimeForStop" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="freightAmount" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="freightTypeId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="groupId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="gstTaxApplicable" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="hasHistory" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="importNumber" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isDirectlyBillable" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isGroupVolumeDiscounted" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isRegion" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isShipTo" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="kitCodeId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="leadTime" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="lockoutControl" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="managerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="mediumRangeZone" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="merchandiserId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="packageId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="parentCustomerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="parentName" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="priceListId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="printStatement" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="receivingTimeFrom" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="receivingTimeTo" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="requirePO" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="requireSKU" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="salesRepId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="stns:Address"
name="shipAddressData" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="stns:Address"
name="shipToAddress" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="shipToAddressId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="shipViaId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="shipZoneId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="shortRangeZone" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="specialCodes" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:dateTime"
name="startDate" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="storeNumber" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="summaryPrintCodeId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="taxCodeId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="taxNumber" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="termsCodeId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:double"
name="toBeDue" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="useShippingAddress" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="vendorNumber" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="warningControl" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CustomerProfile">
<xsd:sequence>
<xsd:element type="stns:ArrayOfProfile"
name="profiles" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CustomerSearchCriteria">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.common" base="tp:AbstractSearchCriteria">
<xsd:sequence>
<xsd:element type="xsd:int"
name="billingPartnerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isDirectlyBillable" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isRegion" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:boolean"
name="isShipTo" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="parentCustomerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="searchString" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="searchType" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CustomerTypePct">
<xsd:complexContent>
<xsd:extension
base="stns:CustomerTypePctHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="CustomerTypePctHelper"
abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:int"
name="customerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="customerTypeId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="status" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="typePct" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="MailingListSubscription">
<xsd:complexContent>
<xsd:extension
base="stns:MailingListSubscriptionHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="MailingListSubscriptionHelper"
abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:boolean"
name="checked" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="customerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="mailingListId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="mailingListName" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="NoteVault">
<xsd:complexContent>
<xsd:extension base="stns:NoteVaultHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="NoteVaultHelper" abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="tag" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="text" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="type" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="Notes">
<xsd:complexContent>
<xsd:extension base="stns:NotesHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="NotesHelper" abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:int"
name="customerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:dateTime"
name="date" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="owner" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="reference" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="subtype" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="text" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="type" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="Profile">
<xsd:complexContent>
<xsd:extension base="stns:ProfileHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ProfileHelper" abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:int"
name="customerId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="id" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.util" type="tp:ArrayList"
name="messageList" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="numericInfo" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element
type="stns:ProfileInfo" name="profileInfoData" minOccurs="1" maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="profileInfoId" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:int"
name="recordStatus" minOccurs="1" maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string"
name="textInfo" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element type="xsd:int"
name="version" minOccurs="1" maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ProfileInfo">
<xsd:complexContent>
<xsd:extension base="stns:ProfileInfoHelper">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ProfileInfoHelper"
abstract="true">
<xsd:complexContent>
<xsd:extension
xmlns:tp="java:com.starcomsoft.pp.database" base="tp:BaseHelper">
<xsd:sequence>
<xsd:element type="xsd:string"
name="domainValueName" minOccurs="1" maxOccurs="1" nillable="true">
</xsd:element>
<xsd:element
xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString"
name="errorMessages" minOccurs="1" maxOccurs="1" nillablBruce,
Sorry, I forgot to mention that the WSDL was generated by querying the URL
of the deployed webservice. If there is something missing from the WSDL,
it may be due to servicegen, or a problem with deployement. All of this
used to work in WLS 7.0 sp1.
I submitted this case (459937) to BEA Support on 11/12/03 and have given
them my EJB jar file so they can reproduce the problem using servicegen.
I would appreciate any input you can provide to resolve this problem, but
you can let Support handle it from here if you wish.
Thanks,
Tony
[email protected] (Bruce Stephens) wrote:
Hi Tony,
Could you clarify your starting point; i.e. do you begin with WSDL or
from java?
In looking at your WSDL, on the surface I'm concerned that the imports
should be something like <xsd:import namespace="..."
schemaLocation="myschema.xsd"/> so it may not be including your
definitions.
Thanks,
Bruce
Tony Huang wrote:
I have datatypes that extend classes in a different package. When I
use WLS81 ANT task clientgen to generate client-jars from WSDL files
obtained from web services generated by servicegen, the superclasses
are not fully qualified in the generated java code, nor are there
import statements for the superclasses. This causes the generated
code to have compile errors. Other dependencies are fully qualified in
the generated code, but the superclass is not.
There mayThe WSDL is included below. Specifically,
com.starcomsoft.pp.database.BaseHelper does not get a fully qualifed
reference in the generated java code. -
Hi,Gurus
I have a problem about incoterms in PO.
In my company, there are three kinds of planned delivery costs,freight,insurance charge and customs clearance charge.
They will be calculated as conditions as po creation.
For example,Freight is defined as the following ratio:
|IncoTerms|Freight Ratio
| EXW | 0.958%
| FOB | 1.829%
I firstly entered incoterms FOB while PO creation, the ratio 1.829% was correctly carried out.
and then not to save the PO,but change the incoterms from FOB into EXW right now,
I found the condition item Freight still holds the older value,1.829%, in item detail.
In one words,Changing incoterms will not lead to conditions re-calculation.
Anyone could give me suggestion?Thanks.
As well known,
Incoterms is a head-level field in purchase order.
My purchase order should calculate the planned delivery costs,freights,insurance charges,which are based incoterms.
The calculation logic is Freight = Item's net order value * rate.
ex.
1.PO item net order value = 1000 USD
2.Case1: Incoterms = FOB,Freight rate = 1.829%
3.Case2: Incoterms = EXW,Freight rate = 0.928%
Create PO:
PO incoterm is FOB, so the planned freight = 1000 * 1.829% = 18.29 USD
Change PO incoterms
Changed PO incoterms form FOB into EXW, so the planned freight = 1000 * 0.928% = 9.28 USD
Now, my problem is that the above item's freight can not be automatically calculated again after incoterms was changed in PO head.
By the way,
Incoterms(INCO1) field is in Communication Header for Pricing(KOMK),not in Pricing Communication Item(KOMP).
MOVE I_KOMK TO E_KOMK. was added into User-exit LMEKO001.
Edited by: Mic chen on Aug 19, 2009 3:41 AM -
I have Adobe CS 5.5 with a valid product key (On the original box) but it wont install on my new work computer. This product is owned by my company and has been used in the past on my old computer.
I enter the product key and get the customary Green Check Mark:
[image removed by moderator]
I Click "Next" and it displays the screen below. I do not have any CS 5.5 programs installed on this computer. (It is brand new - opened and set up this morning)
I used this disk to install CS5.5 on my previous computer which has crashed and did not need to Upgrade anything. I do not have any other product keys to use for the second box and I have found nothing on this problem in the forums.
Any help is appreciated, I am at a loss.Never share your serial number in a public forum or other non-private communication.
For the second image you show you need to follow the instructions.
You copy of CS5.5 appears to be an upgrade version. THis means it was made available at a reduced price because you had an earlier version that you upgraded from. The second image you show is asking you to provide the information for that older version as proof that you qualify to activate/use the new one. -
How to stop sales orders from contracts from qualifying for Rebates.
We have set up rebate agreements for customers and they are working as expected.
Now our sales people want to start using contracts for some special deals for certain customers and products. But they DO NOT want these sales orders from these contracts to qualify for rebates.
Does anybody know how we can set this up or if it is at all possible?Hi Zoya,
I got one more idea and so try it out.If it sounds foolish please ignore.Instead of going for userexits its better you go for a different sales order type whenever you refer to a contract.And make sure you assign a different pricing procedure which does not contain the condition type BO03 at all.Ofcourse this new sales document should have a different document pricing procedure.
Regars
Ravi Kiran -
How to Map Idoc-Orders05 Qualifier permitted values to a flat file Str
Hi All,
My scenario is IDoc-xi-flat file. I have a problem in mapping the respective qualifier value in IDoc to the flat file structure. I am using the function fix values in Message Mapping. Suggest how should the target field should look like to map to the qualifier.
Thanks
Gowri K.hi,
can you tell a little bit more on what are you trying to achive?
do you only need one qualifier in file or all or what?
can you use the same structure as in IDOC ?
be a little more precise
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
Header and Item Incoterms different in Sales order
Hello SAP Guru's,
I have an unique issue of Incoterms in Sales order item being different from the Header, when this happens any change to the header Incoterms is not getting copied to sales order Items.
The issue is due the different Division maintained for Sales order item in the Material master, which is fetching the Inco 2 from the Different Sales area for this is customer.
This is fine as per design where Item category is checked for Business data and Sales Document type is checked for different Division in the config.
However the Business would like the Header Incoterms to be copied to all items and any change in Header should also be copied to Line items also.
We had narrowed down on Couple of Alternatives:
Remove the Business data allowed check in the Item category config
But this would allow all Business data to be copied from sales order header to items
2. Make changes to VBKD user Exit during Sales order creation to copy the Incoterms from Sales order header to items
But this is causing multiple lines in VBKD and some issues while adding new items in VA02 ending with an Update termination.
Would like to know whether there is any other Option whether there would be least impact and also would like your advice on the better Option between the above two Options.
Thanks and Regards
Mohammed RoshanHi Lakshimipathi,
Finally we removed the Business Item check in the Item category which is causing the Header incoterms and any changes in Header incoterms to be copied to Sales Order line items as required but we have an issue where Sales Order item Pricing date is being greyed out due these changes, Currently the Sales order Pricing date is being determined through a Z table triggered from a User Exit which was also editable in Sales order item level.
Due to these new changes Sales order pricing date is being determined in the header and getting copied to the Sales order line item thus greying out the Sales order item pricing date field.
Would like to know your thoughts on how removing the Business Item check in Item category in VOV7 is causing the grey out of sales Order item pricing date, where the Business can modify on certain occasions and what would the workaround to restore the functionality of Sales order item pricing date.
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan -
Today I went to the Verizon store to upgrade my girlfriends phone which is on my account b/c I wanted to use the edge plan to buy the iPhone 5c. I had read in several different places that I could upgrade using edge and not loose my unlimited data, turns out I was misinformed, which the guy at the store told me after he had my information pulled up using my cell number. I told the guy I was not willing to give up my unlimited plan AND pay full price for the phone, I thanked him for his time and we left. When we left the store I called the Verizon number that is given on the website and told them I was interested in the edge plan for the 5c and asked for more information, ( I thought the guy at the store was wrong and I was checking). The woman I talked.......long story short, I talked to 8 people including 2 managers and none of them could tell me why I did not qualify for the edge financing (even if switching the plan), SO I was hoping someone on here might could help. I have been a customer since Verizon bought out Alltel, I have automatic payments set up with no late payments for as long as I can remember, and was eligible for an upgrade on 01/03/2013. Any experience or advice in this area would be appreciated.
Thank You!rjg030585 wrote:
I told the guy I was not willing to give up my unlimited plan AND pay full price for the phone, I thanked him for his time and we left.
Here is my advice, at least. Not sure if anyone will agree, but it is my take on the problem.
With the Edge program, there is a "possibility" that someone will pay full price for a phone. This is not always the case, though. IF you do not complete ALL of the 24 months of payments, then you WILL NOT have paid full price for the phone, but simply a portion of the full price. THAT is why it does not make the plan "eligible" to keep your unlimited data. With the Edge plan, technically you only have to pay 50% of the full price before you can trade it in for another phone on the Edge plan. The way the plan is designed, the majority of people WILL NOT ever pay full price for the phone, but only a portion of the full price before they exchange their phone for a new device. That is what Verizon is hoping for, at least.
As Ann154 has pointed out, you can use the Device Payment Plan and keep your unlimited data. At no time during your contract can you trade THAT phone in to get another phone. You would have to continue making the payments on THAT phone along with any other phone you upgraded to. THAT is the difference between the 2 plans. You WILL end up paying full price for the phone on the Device Payment Plan, where you can STOP making payments on a phone with the Edge Plan if you turn it in for another device.
Good luck.
Maybe you are looking for
-
Search help is not triggering second time in interactive form
Hi, I have online interactive form in WDABAP. And I have few search helps in the form, If i click on any search help it is opening and I can select the value and the same is populated to the field. But if i click it again search help is not opening.
-
Add Microsoft Publisher to Office Professional Plus 2013
Hi, I'm trying to do a command-line installation to add Microsoft Publisher 2013 to an existing Office Professional Plus 2013. It was assumed that our staff would not need it, but as we have already received one request to get it installed, and the s
-
Won't go to sleep when I close the lid
When I close the lid of my Macbook Pro (running Lion) it doesn't realy go to sleep. When I open the lid the screen goes black. Does anyone know what the issue is? Thanks
-
Hey everyone. I'm trying to diagnose a remote AP installation using SNMP. The default SNMP traps aren't adequate for what I need to monitor. For instance, with the built-in MIBs I can information like input/output errors, link status, etc. But, what
-
I wans to know what components of EPM do I need to create project which takes data from Oracle Financials, Makes Some Transformations and create reports. It's some kind of migration from Oracle Financials, then new data will be loaded from OLTP syste