Control file for SAP import

The control file meta.xml for importing an SAP document contains

  • system attributes:

    • _alis_access.sapdocId (SAP document ID)

    • _alis_access.contRep (content repository name)

    • _alis_access.linkDocType (linked document type)

  • properties as required for access by SAP ArchiveLink for each content object with the keys:

    • compId (component ID)

      These component IDs must be unique within one document, so they must be different for each content object. You can use a pattern like illustrated below, starting with “data” for the first content object, and then proceeding with “data1”, “data2” etc., increasing the number for each additional content object.

    • mimetype

Be aware: Copy and paste from an example in this PDF into a text file that shall be processed by FIS can result in errors due to the encoding of special characters that can get broken!

<?xml version="1.0" encoding="UTF-8"?>

<tns:operation xmlns:tns="http://imafis.imaes.ecm.tsystems.com/" name="sapArchive">

  <sapRevision>

    <metadata>

      <attribute name="documentTypeOrders.name">Hugo</attribute>

      <attribute name="documentTypeOrders.lastname">Ratke</attribute>

      <attribute name="documentTypeOrders.number">1</attribute>

    </metadata>

    <systemAttributes>

      <attribute name="_alis_access.sapdocId">IMA-8757785675758</attribute>

      <attribute name="_alis_access.contRep">Q1</attribute>

      <attribute name="_alis_access.linkDocType">documentTypeOrders</attribute>

      <!-- if there are more system attributes, they are ignored for import. The listed system attributes are mandatory -->

    </systemAttributes>

    <content key="contentKey_1">

       <properties>

          <property key="compId">data</property>

           <property key="mimetype">application/pdf</property>

       </properties>

       <data>

          <binaryObject batchFileName="0000000001" originalFileName="dummyPDF150KB_blub.pdf" mimeType="application/pdf" />

       </data>

    </content>

    <content key="contentKey_2">

       <properties>

          <property key="compId">data1</property>

           <property key="mimetype">application/pdf</property>

       </properties>

       <data>

         <binaryObject batchFileName="0000000002" originalFileName="dummyPDF150KB.pdf" mimeType="application/pdf" />

       </data>

    </content>

  </sapRevision>

</tns:operation>

The protocol files are structured in the same way as for the normal import except that there is an sapDocId tag in the protocols in addition to the directory / filePath tag.