Topic overview
This article describes the procedures for working with the Import data application with regard to sales fast entry vouchers. The procedures describe basic steps and important special features of the application. You will also find information on possible prerequirements and action results.
More information on the Import data application, including the description of its fields and buttons, may be found in the Import data article.
General
The export and import of sales fast entry vouchers is primarily based on the current data model saved in the repository database. More attributes are available for data export than for import. This is why it is recommended to set separate filters for export and import.
1:1 relationships in the data model are usually based on a technical GUID attribute. For data import, depending on the application, you may either use the technical GUID attribute or special keys from the target object (most often, code or number). For some business entities, an organization is required for the conversion of a special key to a technical key. A relevant organization is usually not included directly in the import source but is specified by the voucher context. For more information, refer to chapter Overview: Attributes.
The header of the sales fast entry voucher contains references to hash code business entities. These are technically related attribute groups recurring for many vouchers, which allows you to save some storage space in the database and the main memory. Using a special conversion, the hash code business entities for export or import are represented as parts.
Some data cannot be imported from sales fast entry vouchers, e.g. status fields or internal auxiliary attributes.
If you are unsure of the appropriate format of the import file, complete the following steps: In Import data, add a sample voucher and export it in any format, using the import filter and any attributes. The sample file created in this way can be used as a template for the import files to be generated.
In the case of data import, the same rules apply as when editing data in the application. For instance, an already saved line item cannot be changed anymore. Attribute values are skipped if they cannot be applied in the current context. The same logic is also used for determining default values. Thanks to that, data import and the application work in the same way. It applies to data validation as well.
Procedures: Import sales fast entry vouchers
- Open the Import data application
- Find the filter for the business entity: cisag.app.sales.obj.SalesRapidDocument
Open the filter for the import of sales fast entry vouchers - Duplicate or create a new filter for this business entity
- If you need it, change filter attributes
- Click the [Import data] button in the standard toolbar
The Import data dialog window will be displayed - In the window, you can adjust settings for the import file. See the Import data article for descriptions of separate fields.
- Click the [In background] or [Immediately] button to initiate import
Data will be imported
Overview: Attributes
Below, you will find the overview of attributes of individual business entities that are available for import. In the case of foreign key attributes, the corresponding relationship names are also listed. The header and required fieds can change and be appropriately extended.
Identification attributes (key attributes) are marked with (K).
Header discount
Sales fast entry vouchers (SalesRapidDocument)
The header of the sales fast entry voucher consists of a type and number that is specified for the type in the number range.
Attribute | Relationship | Description |
|---|---|---|
| afterTransfer | After transfer | |
| autoConfirmWarnings | Automatically confirm warnings | |
| customerData | See chapter: Customer data (customerData, deliveryCustomerData, invoiceCustomerData) | |
| customerOrderData.purchaseOrder | External voucher number | |
| customerOrderData.date.value | External voucher date | |
| CustomerProposal.Type.code | Sales quotation type Hint When importing sales fast entry vouchers for sales quotations, save a sales quotation type to be used for this attribute. |
|
| date | Creation date | |
| deliveryCustomerData | See chapter: Customer data (customerData, deliveryCustomerData, invoiceCustomerData) | |
| deliveryData | See chapter: Supplier data (deliveryData) | |
| discountOriginType | Discount origin Hint You can import price data only for vouchers whose type has the Use prices parameter acti-vated. Hint In the case of existing sales fast entry vouch-ers containing line items, this attribute can be changed via im-port only when price determination is de-layed as per the vouch-er type. |
|
discounts[0..3]
| DiscountType | Discounts 1 to 4
Hint You can import price data only for vouchers whose type has the Use prices parameter activated. To import discounts, their origin must be set as Manual. Hint In the case of existing sales fast entry vouchers containing line items, this attribute can be changed via import only when price determination is delayed as per the voucher type. |
| guid (K) | "Technical ID for changing/ deleting saved data – if it is known." |
|
| invoiceCustomerData | See chapter: Customer data (customerData, deliveryCustomerData, invoiceCustomerData) | |
| invoicingData | See chapter: Invoice data (invoicingData) | |
| invoicingPartyData | See chapter: Sales organization data (invoicingPartyData) | |
| number (K) | Number (technical identification) You can select this op-tion when creating new objects – if you do not select it, a number will be assigned automati-cally. Required if no guid has been given upon change/deletion. |
|
| payee | PayeePartner | Payment partner Hint In the case of existing sales fast entry vouchers, this attribute can be changed via import only when there are no voucher line items yet. |
| priceDate | Calculation date Hint You can import price data only for vouchers whose type has the Use prices parameter acti-vated. Hint In the case of existing sales fast entry vouchers containing line items, this attribute can be changed via import only when price determination is delayed as per the voucher type. |
|
| priceListing | Price listing Hint You can import price data only for vouchers whose type has the Use prices parameter activated. Hint In the case of existing sales fast entry vouch-ers, this attribute can be changed via import only when there are no voucher line items yet. |
|
| priceValidityDate | Reference date for price determination Hint You can import price data only for vouchers whose type has the Use prices parameter acti-vated. Hint In the case of existing sales fast entry vouch-ers containing line items, this attribute can be changed via import only when price determination is delayed as per the voucher type. |
|
| pricingPartner Relation | Partner usage Hint You can import price data only for vouchers whose type has the Use prices parameter acti-vated. Hint In the case of existing sales fast entry vouchers containing line items, this attribute can be changed via import only when price determination is delayed as per the voucher type. |
|
| requestDate.value | Preferred date | |
| RequestForProposal. Type.code | Sales RFQ type Hint When importing sales fast entry vouchers for sales RFQs, save a sales RFQ type to be used for this attribute. |
|
| responsible | Employee responsible | |
| SalesOrder.Type. code | Sales order type Hint When importing sales fast entry vouchers for sales orders, save a sales order type to be used for this attribute. |
|
| salesRepresentatives[0:2] | Up to 3 representatives | |
| shippingDate | Shipping date | |
| storageArea.warehouse | Warehouse Hint You can import ware-house data only for vouchers whose type has the Use warehouse parameter activated. |
|
| targetOrderType | Destination voucher type | |
| TextAssignments | File attachments/Texts See chapter: Texts (TextAssignments) |
|
| type (K) | Type | Type (technical identi-fication) Required if no guid has been given upon change/deletion. |
Customer data (customerData, deliveryCustomerData, invoiceCustomerData)
Customer data in these three roles is saved in the database as a hash code object and is available for import/export as parts. It applies to address data as well.
As in the case of attribute names, the following part names are assigned:
-
customerData Customer
-
deliveryCustomerData Delivery recipient
-
invoiceCustomerData Invoice recipient
Therefore, the following attributes occur once for each role.
Attribute | Relationship | Description |
|---|---|---|
| addressData.city | Address – City | |
| addressData.country | addressData.Country | Address - Country |
| addressData.district | Address – District | |
| addressData.poBox | Address – P.O. box | |
| addressData. poBoxCity | Address – P.O. box city | |
| addressData. poBoxPostalCode | Address – P.O. box postal code | |
| addressData. postalCode | Address – Postal code | |
| addressData.region | addressData.Region | Adres – Region |
| addressData.street | Address – Street | |
| customer | CustomerPartner | Customer |
| name | Customer name | |
| careOf | CareOfPartner | Care of |
| careOfName | Care of Name |
Supplier data (deliveryData)
Supplier data is saved in the database as a hash code object and is available for import/export as parts.
Attribute | Relationship | Description |
|---|---|---|
| deliveryTerms | DeliveryTerms | Delivery term |
| deliveryTermsLocation | Delivery term Location |
|
| shippingTerms | ShippingTerms | Shipping term |
Invoice data (invoicingData)
Some invoice data is saved in the database as a hash code object and is available for import/export as parts.
Attribute | Relationship | Description |
|---|---|---|
| currency | Currency | Currency Hint You can import curren-cy data only for vouch-ers whose type has the Use prices parameter activated. Hint In the case of existing sales fast entry vouch-ers, this attribute can be changed via import only when there are no voucher line items yet. |
| paymentMethod (Company) | PaymentMethod | Payment method Hint You can import pay-ment methods only for vouchers whose type has the Use payment terms parameter acti-vated. |
| paymentTerms (Company) | paymentTerms (Company) | Payment term Hint You can import pay-ment methods only for vouchers whose type has the Use payment terms parameter acti-vated. |
Sales organization data (invoicingPartyData)
Some sales organization data is saved in the database as a hash code object and is available for import/export as parts.
Attribute | Relationship | Description |
|---|---|---|
| partner | Partner | Partner Hint In the case of existing sales fast entry vouch-ers, this attribute can-not be changed via im-port. Data in the import file will be skipped dur-ing the import. |
| careOf | CareOfPartner | Care of |
| careOfName | Care of Name |
Texts (TextAssignments)
Attribute | Relationship | Description |
|---|---|---|
| code | Text module (optional) |
|
| document | Document | |
| sequence | Number | |
| text | Texts for each language (Used only when a text module has not been specified. See chapter: Text) |
|
| type | Text type |
Text
Attribute | Relationship | Description |
|---|---|---|
| contentType | Content type | |
| language | Language | |
| text | Text |
You can use different text formats. If you need formatting samples, create a voucher template with the appropriate formatting and export it.
Line items of the sales fast entry voucher (SalesRapidDocument)
Attribute | Relationship | Description |
|---|---|---|
| customerItemNumber | Customer item's number For more information, see the article Import voucher line item by means of an EAN |
|
discounts[0..3]
|
| Discounts 1 to 4
Hint You can import discounts only for vouchers that use prices entered manually (Price origin: Manual). |
| ean | European Article Number (EAN) For more information, see the article Import voucher line item by means of an EAN |
|
grossPrice
| Currency | Gross price Hint You can import gross prices only for vouchers that use prices entered manually (Price origin: Manual). Hint Used only for vouchers that do not refer to retail customers (see retailGrossPrice). |
| guid (K) | Technical identification (line item) for changing/deleting saved date – if it is known. | |
| item | Item | Item |
| netCode | No base discounts Hint You can import the No base discounts attribute only for vouchers that use prices entered manually (Price origin: Manual). |
|
| number (K) | Number (technical iden-tification) You can select this op-tion when creating new objects – if you do not select it, a number will be assigned automati-cally. Required if no guid has been given upon change/deletion. |
|
| noCashDiscount Enabled | No cash discount Hint You can import the No cash discount attribute only for vouchers that use prices entered manually (Price origin: Manual). |
|
| noClassification Discounts | Do not apply multi-item discounts Hint You can import the Do not apply multi-item discounts attribute only for vouchers that use prices entered manually (Price origin: Manual). |
|
| noOrderValue Discounts | Do not apply any order value discounts Hint You can import the Do not apply any order value discounts attribute only for vouchers that use prices entered manually (Price origin: Manual). |
|
| priceDimension | Price dimension Hint You can import price dimensions only for vouchers that use prices entered manually (Price origin: Manual). |
|
| priceOriginType | Price origin Hint You can import a price origin only for vouchers whose type has the Use prices parameter activated. |
|
| priceUom | PriceUom | Price unit Hint You can import a price unit only for vouchers that use prices entered manually (Price origin: Manual). |
| pseudoItemDescription | Pseudo item description Hint It applies to pseudo items only. For other items, this value will be skipped. |
|
retailGrossPrice
| Currency | Gross price incl. taxes Hint You can import gross prices including taxes only for vouchers that use prices entered manually (Price origin: Manual). Hint Used only for vouchers that refer to retail cus-tomers (see gross-Price). |
| TextAssignments | File attachments/Texts See chapter: Texts (TextAssignments) |
|
| totalQuantity.amount | Total quantity amount | |
| totalQuantity.uom | Uom | Total quantity unit |
| uomObligation | Binding unit Hint You can import a binding unit only when the Manage inventory in lo-gistic units function is activated in Customizing for the active OLTP client. |
|
| uomObligationOrigin | Origin of Binding setting of units Hint You can import the origin of Binding setting of units only when the Manage inventory in logistic units function is activated in Customizing for the active OLTP client. |