Topic overview

This documentation describes the procedures for using the Import data application in relation to purchase order confirmations. These procedures include general steps and special features that need to be considered. You will also be informed about possible preconditions and effects.

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

General information

The import of a purchase order confirmation 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 typically based on a technical GUID attribute in the data model. Depending on the use case, either the technical GUID attribute or the business key from the target object (usually code or number) can be used for the import. 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 voucher context. Further information on this can be found in the chapter Overview: Attributes.

Hash code business objects are referenced both in the header and in the line items of a purchase order confirmation. These are technically related attribute groups that are always the same for many vouchers and whose reuse therefore saves storage space in the database and main memory. Using a special conversion, these hash code business objects are displayed as parts for export or import.

Certain data from purchase order confirmations, such as local currency values and internal auxiliary attributes, cannot be imported.

If you are not sure which format is suitable for the import file, proceed as follows: Enter a sample purchase order confirmation via the Purchase order confirmations application and export it using the filter for the 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 generated.

The same rules apply when importing as when editing via the application. For example, an item in a saved line item can no longer be changed. Attribute values are ignored if they cannot be adopted in the current context. The same logic is applied when determining the default value, so that import and application behave identically. The same applies to data validations.

Procedure: Importing purchase order confirmations

1. Open the Import data application.

2. Display the filter for this business object: com.cisag.app.purchasing.obj.SupplierConfirmation

• The filter for importing purchase order confirmations will be displayed

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. Press the [Import data] button on the standard toolbar.

• The Import data dialog window will open

6. You can make settings for the import file in the Import data dialog window. You can find a description of the fields in the Import data article.

7. Press one of the [In background] or [Immediately] buttons.

• The import will be executed

Creating new purchase order confirmations

The minimum required attributes per base object:

Optionally, you can also transfer the number using the import. In this case, the number determined via the number range according to type is ignored. In addition, suitable conventions must be used to ensure that the number assigned via the import does not match a number that has already been assigned or is to be assigned automatically in the future.

A corresponding minimal XML with functional attributes and two line items has the following content, for example:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation" xsi:schemaLocation="com.cisag.app.purchasing.obj.SupplierConfirmation SupplierConfirmation.xsd" created="2007-12-10T12:00:52.090Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" nlsMode="SINGLE_LANGUAGE" dateTimeMode="COMPACT">
   <SupplierConfirmation xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation">
      <supplierConfirmationData>
         <salesConfirmation>1234567</salesConfirmation>
         <date>
            <value>10#12#2007</value>
         </date>
      </supplierConfirmationData>
      <Type>
         <code>100</code>
      </Type>
      <Correspondence>
         <number>POC1375</number>
      </Correspondence>
   </SupplierConfirmation>
</semiramis>

The remaining base attributes are added in this example using the default values according to the header of the purchase order document.

To control the default values for line items, pay particular attention to the functions and settings you select when you generate an order confirmation in the Generate confirmation from purchase order document dialog window. The following attributes are relevant:

• Quantity defaults (quantityDefaults)
  Default: true
• Delivery date for line items (detailDeliveryDateOrigin)
  Suggestion: LAST_CONFIRMATION
  For the option Use specified date (SPECIFIED), the Delivery date attribute (specifiedDeliveryDate) must also be filled in

You can also import further base values and use technical attributes instead of the specialized attributes. You will find a list of the attributes in the chapter: Overview: Attributes.

Selecting line items

As with the [Generate from purchase order document…] action in the Purchase order confirmations application, you can also specify the confirmation status during the import, which is used as a selection characteristic for the line item selection.

The specification during the import is done via a comma-separated list of the technical identifications of the confirmation statuses to be used, which are available with the confirmationStatusSelection attribute. The following values are allowed:

The confirmationStatusSelection attribute suggests the following value: “1, 13” (Not confirmed and Confirmed conditions changed).

If this function has been set in the header, it is adopted into the corresponding header attribute.

By default, the selection made during import has no further effect initially. In addition to the header, only those line items are processed that are directly contained in the import source. Only if you set the virtual base attribute takeSelectedDetails to true will the import process all line items according to the selection in the confirmationStatusSelection attribute before the actual line item processing.

The following example transfers all line items for which the confirmation status of the order document basic line item has one of the values Confirmed, Cancellation confirmed, Change recommendation received, Rejected, or Cancellation rejected before the actual line item processing:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation" xsi:schemaLocation="com.cisag.app.purchasing.obj.SupplierConfirmation SupplierConfirmation.xsd" created="2007-12-10T12:00:52.090Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" nlsMode="SINGLE_LANGUAGE" dateTimeMode="COMPACT">
   <SupplierConfirmation xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation">
      <supplierConfirmationData>
         <salesConfirmation>1234567</salesConfirmation>
         <date>
            <value>10#12#2007</value>
         </date>
      </supplierConfirmationData>
      <takeSelectedDetails>true</takeSelectedDetails> 
<confirmationStatusSelection>5, 6, 9, 12, 14 
</confirmationStatusSelection>
      <Type>
         <code>100</code>
      </Type>
      <Correspondence>
         <number>POC1375</number>
      </Correspondence>
   </SupplierConfirmation>
</semiramis>

Deviating line item data

As in the Purchase order confirmations application, you can specify data that differs from the purchase order document line item data when importing confirmation line items. In the simplest case, only individual values change. You can also apportion an existing purchase order line item or an existing confirmation line item.

When apportionings are carried out, the source is always the purchase order document basic line item with all its sub-items. You can also use an existing confirmation basic line item with all its sub-items as the source by means of the virtual line item attribute creationSourceSequence:

• creationSourceSequence<0 (default):
  The order document basic line item is used as the source for the apportioning.
• creationSourceSequence>=0:
  The confirmation basic line item with the specified sequence is used as the source for the apportioning.

If you want to apportion a line item, then you must either define the virtual line item attribute creationSourceSequence for the new line item (the default is then used for sequence) or define the sequence attribute with a positive value. The advantage of specifying the sequence value is that such an apportioning line item can be easily found again if changes are made at a later date.

In the following example, the delivery of line item 10, which has not been canceled in the purchase order document, is rejected (canceled) by the supplier. On 2 January, the original line item 20, with the quantity of 20 pieces, is apportioned as a change recommendation to two line items with the quantities of 7 pieces for 3 January (sequence: 0 – cannot be changed for the original line item) and 13 pieces for 4 January (sequence: 1):

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation" xsi:schemaLocation="com.cisag.app.purchasing.obj.SupplierConfirmation SupplierConfirmation.xsd" created="2007-12-10T15:19:19.577Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" nlsMode="SINGLE_LANGUAGE" dateTimeMode="COMPACT">
   <SupplierConfirmation xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation">
      <supplierConfirmationData>
         <salesConfirmation>1234567</salesConfirmation>
         <date>
            <value>10#12#2007</value>
         </date>
      </supplierConfirmationData>
      <Type>
         <code>100</code>
      </Type>
      <Correspondence>
         <number>POC1376</number>
      </Correspondence>
      <Details>
         <canceled>true</canceled>
         <CorrespondenceDetail>
            <number>10</number>
         </CorrespondenceDetail>
      </Details>
      <Details>
         <deliveryDate>2008-01-02T23:00:00.000Z</deliveryDate>
         <totalQuantity>
            <amount>7</amount>
            <Uom>
               <code>St.</code>
            </Uom>
         </totalQuantity>
         <CorrespondenceDetail>
            <number>20</number>
         </CorrespondenceDetail>
      </Details>
      <Details>
         <deliveryDate>2008-01-03T23:00:00.000Z</deliveryDate>
         <sequence>1</sequence>
         <totalQuantity>
            <amount>13</amount>
            <Uom>
               <code>St.</code>
            </Uom>
         </totalQuantity>
         <CorrespondenceDetail>
            <number>20</number>
         </CorrespondenceDetail>
      </Details>
   </SupplierConfirmation>
</semiramis>

Processing open confirmations

Only one purchase order confirmation may be in process at the same time for a purchase order. When attempting to generate a second order confirmation for the same purchase order, an error message is generated during import, as in the Purchase order confirmations application.

You can further process an existing open purchase order confirmation if you reference the type (Type or type) and number (number) in the import source, where number is the relevant confirmation number that was assigned during generation according to the number range.

To simplify matters, an open purchase order confirmation can also be further processed without explicitly specifying the number under the following conditions:

• The CREATE mode was not explicitly specified
• The import source contains a reference to the relevant purchase order document header
• The import source does not contain a confirmation number
• The purchase order document for the open confirmation matches the purchase order document specified in the import source
• The external voucher number of the open confirmation matches the external voucher number according to the import source.
• The open purchase order confirmation has the general status In process

Automatic completion after the import

Provided that the import was successful and there are no relevant changes to the associated purchase order document, purchase order change document, or current order, you can automatically complete a processed order confirmation after the import. To do this, you must set the virtual base attribute autoCompletion to the value true for the relevant instance.

If this function is activated and no other errors are detected, an additional information message is issued in the message log, which contains the information whether the purchase order confirmation was completed automatically or whether this was not possible due to deviations.

Overview: Attributes

The attributes of the individual business objects that are available for import are listed below. For foreign key attributes, the corresponding relationship name is also provided. The identification and mandatory fields are subject to change and can be extended by customizations.

For some business objects, an organization (organization) is required to convert the business key to the technical key. This is indicated in the attribute lists by the following notes in the Attribute column:

• Purchasing organization (always according to the purchase order document)
• Firm (always according to the purchase order document)
• Firm country (always according to the purchase order document)

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

Header data

Purchase order confirmation (SupplierConfirmation)

The identification of a purchase order confirmation consists of a purchase order type and a number from the number range defined for the purchase order type.

Supplier data (deliverySupplierData, invoiceSupplierData)

The supplier data in the two partner roles is stored in the database as a hash code business object and is represented as a part for export/import. The same applies to the address data.

The following part names have been assigned in line with the technical attribute names:

• deliverySupplierData – Delivery partner
• invoiceSupplierData  – Invoicing party

The following attributes therefore exist once per role.

Delivery data (deliveryData)

The delivery data is stored in the database as a hash code business object and is represented as a part for export/import.

Invoicing data (invoicingData)

Some invoicing data is stored in the database as a hash code business object and is represented as a part for export/import.

Intrastat data (intrastatData)

The Intrastat data is stored in the database as a hash code business object and is represented as a part for export/import.

Information texts (InfoTexts)

text

The following example contains two base texts. The header text references the text module “TXT1” and the second text contains a free footer for the languages de and en:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation" xsi:schemaLocation="com.cisag.app.purchasing.obj.SupplierConfirmation SupplierConfirmation.xsd" created="2008-08-08T13:53:43.905Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" nlsMode="SINGLE_LANGUAGE" dateTimeMode="COMPACT">
   <SupplierConfirmation xmlns="com.cisag.app.purchasing.obj.SupplierConfirmation">
      <supplierConfirmationData>
         <salesConfirmation>1234567</salesConfirmation>
         <date>
            <value>10#12#2007</value>
         </date>
      </supplierConfirmationData>
      <Type>
         <code>100</code>
      </Type>
      <Correspondence>
         <number>POC1376</number>
      </Correspondence>
      <InfoTexts>
         <language>de</language>
         <text>&lt;html&gt;Infotext der Basis&lt;/html&gt;</text>
         <contentType>text/html</contentType>
      </InfoTexts>
   </SupplierConfirmation>
</semiramis>

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

Line item data (basic line items)

Purchase order confirmation line items (SupplierConfirmationDetail)

Supplier data (deliverySupplierData)

The attributes correspond to those in the header. See the chapter Supplier data (deliverySupplierData, invoiceSupplierData).

Intrastat data (intrastatData)

The attributes correspond to those in the header. See the chapter IntrastatData (intrastatData).

Delivery data (deliveryData)

The attributes correspond to those in the header. See the chapter Delivery data (deliveryData).

Information texts (InfoTexts)

The attributes correspond to those in the header. See the chapter Information texts (InfoTexts).

Line item data (discounts in kind)

Purchase order confirmation line items (SupplierConfirmationDetail)

Supplier data (deliverySupplierData)

The attributes correspond to those in the header. See the chapter Supplier data (deliverySupplierData, invoiceSupplierData).

Intrastat data (intrastatData)

The attributes correspond to those in the header. See the chapter Intrastat data (intrastatData).

Delivery data (deliveryData)

The attributes correspond to those in the header. See the chapter Delivery data (deliveryData).

Information texts (InfoTexts)

The attributes correspond to those in the header. See the chapter Information texts (InfoTexts).

Line item data (components)

Purchase order confirmation line items (SupplierConfirmationDetail)

Intrastat data (intrastatData)

The attributes correspond to those in the header. See the chapter Intrastat data (intrastatData).

Information texts (InfoTexts)

The attributes correspond to those in the header. See the chapter Information texts (InfoTexts).