You can find the results of your search below. If you didn't find what you were looking for, you can create or edit the page named after your query with the appropriate button.


Result XML Examples, List No. 1: 93 Hits
</Shipping> </Shippings> <Customers> <Customer CustomerRoleType="1" Editable="1" Visible="0" Req... le="1" Visible="1" Required="0" FieldDisplayName="Customer Id" FieldDisplayType="" FieldDisplaySize="0" Fiel... "4" ActionName="Lookup" /> </Actions> </Customer> <Customer CustomerRoleType="2" Editable="1" ... le="1" Visible="1" Required="0" FieldDisplayName="Customer Id" FieldDisplayType="" FieldDisplaySize="0" Fiel
Entering Customer Information: 46 Hits
====== Entering Customer Information ====== ===== Populate customer roles===== Customer information can be entered through the **Customer Info** tab. Depending on how your company has it set up, there are three roles in which customer information can be entered: **Bill To**, **Ship To**, and **End User**... can be entered the same way for all three roles. Customer information can be entered by adding a new custom
Customer Custom Fields: 38 Hits
====== Customer Custom Fields ====== Each SAP CPQ Customer address fields (Bill To, Ship To, End User) contains some standard fields which hold customer information. First Name, Last Name, Address and Company are some of these standard customer fields. If there is need, administrators can add one or more custom fields to Customer Roles. This is being done from SAP CPQ Admin -> Customers/Customer Roles -
CTX Tags for Quote 2.0: 36 Hits
omField().InUserTimezone.InUSDateFormat * Quote.Customer().CustomerId * Quote.Customer().QuoteId * Quote.Customer().UserId * Quote.Customer().FirstName * Quote.Customer().LastName * Quote.Customer().Company * Quote.Customer().Address1 * Quote.Customer().Address2 * Quote.Customer().City * Quote.Customer().StateAbbrev * Quote.Customer().ZipCode * Quote.Customer().CountryAbbrev * Qu
Complete Tag List: 36 Hits
Value\\ Quote.CustomField().AttrValueCode\\ Quote.Customer().CustomerId\\ Quote.Customer().ShopCartId\\ Quote.Customer().UserId\\ Quote.Customer().CustomerCode\\ Quote.Customer().CRMAccountId\\ Quote.Customer().CRMContactId\\ Quote.Customer().DirtyFlag\\ Quote.Customer().RevisionNumber\\ Quote.Customer().FirstName\\ Quote.Customer().LastName\\ Quote.Customer().Company\\ Quote.Customer().Address1\\ Quote.C
Customer Role Defaults: 23 Hits
====== Customer Role Defaults ====== The **Customer Role Default** administrative section allows users to define whether or not customer role fields are filled with user’s information or a user’s company information. Pre-populating customer role fields with data can be helpful in many instances. For e... channel reps often user themselves in the Bill To customer role and the customer’s name in the Ship To or En
Contract Pricing/Discounting: 23 Hits
ract/special prices for some products for certain customer(s). Use cases include:\\ Use Case 1. Contractual/... ems (Used when discount must be shown on quote to customer)\\ For both use cases, the prices are setup using... ct/special pricing process, first make sure the **customer required** checkbox field is **checked**. When th... o an empty Cart/Quote. From there, they can enter customer information. A product can then be configured whe
Customer Administration Execution Workflow: 21 Hits
====== Customer Administration Execution Workflow ====== - The supplied username and password are check... wed value - 50, the API call will fail. \\ - Customer nodes are one by one deserialized from input XML.... sting customers is performed, or the deserialized customer is being added (saved) in CPQ DB without search. ... or AddOrUpdate the search is performed in CPQ for customer. Search rules are described later. \\ - If s
Global Customer Visibility: 20 Hits
{{indexmenu_n>1005}} ====== Global Customer Visibility ====== Customers in the SAP CPQ are divided into 2... to see global customers are defined in the Global Customer Visibility admin section. This section can be ac... cessed by clicking the link under the **Customers/Customer Roles** admin menu //(Figure 1)//. This displays ... tomersadministration:prvag.png|}} \\ The Global Customer Visibility administration screen shows the parame
User Types: 20 Hits
w Quote**: an empty quote. \\ - **New Quote** – **Customer Tab** – the **Customer Info** tab of an empty quo... page. \\ - **When creating a new quote, require customer to be selected first**: determines whether users will be redirected to fill out customer information first when creating a new quote. \\ - **Show pri... Types**. * **When creating a new quote, require customer to be selected first** - toggle switch in **Users
Customer Field Permissions: 19 Hits
{{indexmenu_n>1001}} ====== Customer Field Permissions ====== The **Customer Field Permissions** administ... section allows users to define how the fields in customer roles will be displayed to the user. Permissions ... The following permissions can be defined for each customer role field: * **Hidden** - This is used for t... are displayed with a red asterisk. If user has a customer role set as required in the **Required Fields by
Local Customer Visibility: 19 Hits
{{indexmenu_n>1004}} ====== Local Customer Visibility ====== Customers in the SAP CPQ are divided into 2 ... ese customers, though. \\ Rules that allow local customer sharing are defined in the Local Customer Visibil... cessed by clicking the link under the **Customers/Customer Roles** admin menu. This displays a list of all ... ustomersadministration:prva.png|}} \\ The Local Customer Visibility administration screen shows the parame
Application Parameters: 17 Hits
de number in the **Bill To Details** table on the Customer Info page in order to save the page. When set to ... ata**: determines whether Users can modify global customer data. When set to **NO**, only administrators can... method.\\ * **When Creating Quotes through API, customer roles are required**: defines whether Users creating Quotes through API have to include customer roles.\\ * **When Creating Quotes through API, do
New Quote Details: 16 Hits
in the node <Name> **\\ ** **<Customers>** * **<Customer CustomerRoleType="1">-:$**Before Customer is adde... lookup is performed in order to find out if such customer already exists in CPQ system. \\ Search is performed first by looking if CPQ customer's ID is present in input XML. (Node "Id"). If there is a customer with supplied ID, that customer will be used. If this id is supplied wrong, API call will fail,
General: 9 Hits
Pricebooks: 8 Hits
Reports: 7 Hits
Scripting: 5 Hits
CTX Tags: 4 Hits
Enablement: 4 Hits
CTX Tags: 4 Hits
CRM Objects: 3 Hits
Quote Tabs: 2 Hits
Companies: 2 Hits
User Page: 2 Hits
sidebar: 1 Hits
Time Zones: 1 Hits
Favorites: 1 Hits
GI Tags: 1 Hits
GI Tags: 1 Hits
sidebar: 1 Hits
Quote Tables: 1 Hits
Integrations: 1 Hits
You are here: CallidusCloud SAP CPQ Online Help