Import Requirement via EXCEL - "Package Information&quo

Hi people,

I'm trying to import a text into the field "Package Information" of a requirement, but I can't do it.

My configuration file is: (cfg)

requirement.XLSStartRow=2
requirement.XLSArtifactID=A
requirement.dc:title=A
requirement.dc:description=C
requirement.jzalm:owner="admin"
requirement.priority=L

The xml file about requirement in RQM is:

<xs:element name="requirement">
<xs:annotation>
<xs:documentation xml:lang="en">
** Depricated ** A feature or desired piece of functionality.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element ref="dc:identifier">
<xs:annotation>
<xs:documentation xml:lang="en">
An unambiguous reference to the requirement within a given context.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="dc:title">
<xs:annotation>
<xs:documentation xml:lang="en">
A name given to the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="dc:description">
<xs:annotation>
<xs:documentation xml:lang="en">
Summary of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:updated">
<xs:annotation>
<xs:documentation xml:lang="en">
XML dateTime of the last update of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:state">
<xs:annotation>
<xs:documentation xml:lang="en">
An ID or name of the current state of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="dc:creator">
<xs:annotation>
<xs:documentation xml:lang="en">
An entity primarily responsible for making the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:owner">
<xs:annotation>
<xs:documentation xml:lang="en">
The contributor who owns the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="resolver" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
The contributor who resolved the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="priority" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
The importance of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="reviewStatus" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
String representing the status of the review.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:suspectStatus">
<xs:annotation>
<xs:documentation xml:lang="en">
The trace status of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="creationtime" type="xs:dateTime">
<xs:annotation>
<xs:documentation xml:lang="en">
XML dateTime of the creation of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="resolutionTime" type="xs:dateTime">
<xs:annotation>
<xs:documentation xml:lang="en">
XML dateTime of the resolution of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="externalTag" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
Since 2.0.0.1. A tag which identifies the source of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" ref="approvals">
<xs:annotation>
<xs:documentation xml:lang="en">
The approvals associated with the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" ref="customAttributes">
<xs:annotation>
<xs:documentation xml:lang="en">
A list of user generated name/value pairs.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" ref="risk">
<xs:annotation>
<xs:documentation xml:lang="en">
The risk associated with the requirement. The possible values could be 'Unassigned', 'Very Low', 'Low', 'Medium', 'High', 'Very High'.
The corresponding internal representation is number 0-5.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="tags" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
Since 2.0.0.1. Search strings associated with the requirement workitem.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

So, is it possible?

Thanks in advance!!

BR,
Javi