Import opportunities

Topic overview

This documentation describes the procedure for using the Import data application in relation to sales prospects.

These procedures contain general instruction steps and which special features need to be taken into account. You will also be informed about possible prerequisites, effects and restrictions.

The description of the Import data application, which also includes field and button descriptions, can be found in the documentation Importing data.

General information

The import of a sales prospect is essentially based on the current data model, which is stored in the repository database. More attributes are available for data export than for data import. It therefore makes sense to define separate filters for export and import.

1:1 relationships are generally based on a technical GUID attribute in the data model. Depending on the use case, either the technical GUID attribute or the GUID attribute or the business key from the target object (usually code or number). For some business objects, an organization is required to convert the business key to the technical key. The relevant organization is usually not directly in the import source, but is specified via the document context. Further information on this can be found in the chapter Overview: Attributes.

Certain sales prospect data such as the status fields and internal auxiliary attributes cannot be imported.

If you are not sure which format is suitable for the import file, proceed as follows: Use the Sales prospects application to create a sample sales prospect and export it using the filter for import in the desired format with the desired attributes. The resulting sample file can be used as a template for the import files to be created.

The same rules apply when importing as when editing via the application. Attribute values are ignored if they cannot be adopted in the current context. The same logic is also used when determining default values, so that import and application behave identically. The same applies to the checks.

Note
Existing sales prospects can be expanded by importing additional data. The existing data is replaced by the import data if possible.

Procedure: Importing sales prospects

  1. Open the Import data application.
  2. Display the or a filter for this business object:
    com.cisag.app.crm.obj.Opportunity
    The filter for importing sales prospects is opened. 3.
  3. Duplicate or create a new filter for this business object if required.
  4. Change the already selected attributes of the filter if required
  5. Select the [Import data] button in the standard toolbar.
    The Import data dialog box opens.
  6. You can make settings for the import file in the Import data dialog box. A description of the fields can be found in the Import data documentation.
  7. Select one of the [In the background] or [Immediately] buttons.
    The import is executed.

Overview: Attributes

The attributes of the individual business objects are listed below. For foreign key attributes, the corresponding relationship name is also included. The identification and mandatory fields are subject to change and can be expanded by making adjustments.

The identification attributes (key attributes) are marked with a (K).

Basic data: Sales prospect (opportunity)

The identification of a fast entry sales document consists of a fast entry sales document type and a number from the number range stored for the type.

 

Attribute Relationship Explanation
acceptProbability Accept probability
Activity Activities, see chapter 4.2 “Basic data: Activity”
classification1 Classification1 Classification 1
classification2 Classification2 Classification 2
classification3 Classification3 Classification 3
classification4 Classification4 Classification 4
classification5 Classification5 Classification 5
closeDate Closing date
committed Binding
date Start date
description Designation
Document Documents, see chapter 4.3 “Basic data: Document”
grossMargin

– grossMargin. amount

– grossMargin. currency

Currency Contribution margin

– amount

– currency

guid (K) Technical identifier for the modification/deletion of already stored data – if known
netSales

– netSales.amount

– netSales.currency

Currency Revenue

– Value

– Currency

number (K) Number (functional identification), optional for new creation – otherwise determined automatically.
Mandatory if the guid was not specified when changing/deleting.
OrderPartnerReference Order partner, see chapter Basic data: Order partner relationship (OrderPartner reference)
partner Partner Partner
probability Probability
responsible ResponsiblePartner Responsible employee
salesOrganization SalesOrganization Organization
stage OpportunityStage Sales stage
status Status
type (K) Type Type Sales prospect type (functional identifier):
Mandatory if the guid was not specified during change/deletion
weightedGrossMargin

– weightedGross Margin.amount

– weightedGross Margin.currency

Weighted coverage contribution

– Weighted value

– Currency

weightedNetSales

– weightedNetSales .amount

– weightedNetSales .currency

Weighted revenue

– Weighted value

– Currency

Basic data: Activity

Together with the sales prospects, you can import one or more assigned activities.

Attribute Relationship Explanation
code Number
description Subject
endTime End time
guid (K) Technical identifier for the change/deletion of already saved data – if known
startTime Start time
type Activity type

Basic data: Document

You can import one or more assigned documents together with the sales prospects.

Attribute Relationship Explanation
description Designation
document Document
guid (K) Technical identifier for the modification/deletion of already saved data – if known
maintainingOrganization MaintainingOrganization Organization
number Number
template Template Document number
type Type Document type

You can also use various formatting options for the documents. If you need examples of specific formatting, it is best to create a sample document with the desired text formatting and export it.

Note
Texts are normally imported from the import file and any default values from the partner master data etc. are ignored. If the server property com.cisag.app.general.order.bi.applyAllwaysTextDefaults has the value true, the default values are always determined and combined with any existing texts in the import file. Please note that the numbers of the text lines must be selected appropriately and that only one text line with an article text is created in the result.

Basic data: Order partner relationship (OrderPartnerReference)

Together with the sales prospects, you can import one or more assigned partner links.

Attribute Relationship Explanation
description Designation
guid (K) Technical identifier for changing/deleting data that has already been saved – if known
partner Partner Partner
type Type Partner link type

Czy ten artykuł był pomocny?