Import

Optional or depending values in the examples beneath, which can be missing, are indicated by square brackets. Alternative entries are separated by a pipe "|".

Success protocol file structure

<entry>

  <pid>[unique process identifier]</pid>

  <date>[date and time of process completion]</date>

  <command>ArchiveDocuments|ArchiveSapDocuments</command>

  <filePath>[path to meta.xml]</filePath>

  [<sapDocId>[an SAP document ID only in case of ArchiveSapDocuments]</sapDocId>]

  <state>OK</state>

  <batchId>[batch ID or “NaN” if none available]</batchId>

  <documentId>[document ID]</documentId>

  <revisionId>[revision ID]</revisionId>

</entry>

Error protocol file structure

<entry>

  <pid>[unique process identifier]</pid>

  <date>[date and time of process completion]</date>

  <command>ArchiveDocuments|ArchiveSapDocuments</command>

  <filePath>[path to meta.xml]</filePath>

  [<sapDocId>[an SAP document ID only in case of ArchiveSapDocuments]</sapDocId>]

  <state>NOK</state>

  <error>

    <code>[some code]</code>

    <message>[some message]</message>

    <id>[some id]</id>

    <property name="messagePos0">...</property>

    <property name="messagePos1">...</property>

  </error>

  <attributes>

    <attribute name="any_name">[value]</attribute>

    ...

  </attributes>

</entry>

State protocol file entries

<entry>

  <pid>[unique process identifier]</pid>

  <date>[date and time of process completion]</date>

  <command>ArchiveDocuments|ArchiveSapDocuments</command>

  <directory>[the batch directory]<directory>

  <state>STARTED|FINISHED|ABORTED</state>

</entry>

 

<entry>

  <pid>[unique process identifier]</pid>

  <date>[date and time of process completion]</date>

  <command>ArchiveDocuments|ArchiveSapDocuments</command>

  <operation>

    archiveDocument

  </operation>

[

  <filePath>[path to meta.xml]</filePath>

  <requestId>[request ID if available]</requestId>

]

  <state>RUNNING|OK|NOK</state>

</entry>