# Unexpected warning define 2.1 (SEND 3.1.1)

**URL:** <https://forum.certara.com/t/unexpected-warning-define-2-1-send-3-1-1/4427>\
**Category:** Define.xml\
**Created:** [September 18, 2026, 2:01pm UTC](https://forum.certara.com/t/unexpected-warning-define-2-1-send-3-1-1/4427 "2026-09-18T14:01:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sergio.garofalo](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@sergio.garofalo](https://forum.certara.com/u/sergio.garofalo)\
**Post date:** [September 18, 2026, 2:01pm UTC](https://forum.certara.com/t/unexpected-warning-define-2-1-send-3-1-1/4427/1 "2026-09-18T14:01:00Z")

</div>

Hi all,

While validating a Define-XML file, I encountered some unexpected warnings related to **Origin Type** :

| BW, BWNOMLBL, Other | DD0073 | Invalid Origin Type value |
| --- | --- | --- |
| BW, BWREASEX, Not Available | DD0073 | Invalid Origin Type value |

According to the rule definition, **“Other”** and **“Not Available”** are valid Origin Type values for **SEND** Define-XML v2.1.  
Has anyone experienced this issue before? Do you think this could be a bug in Pinnacle 21?

For reference, I am using:

- **Pinnacle 21 CLI:** v1.0.9
- **Validation engine:** FDA 2508.1

I’ve also included the rule description below:

_For Define-XML v2.0, the Origin Type attribute must have a value of ‘CRF’, ‘Derived’, ‘Assigned’, ‘Protocol’, ‘eDT’, or ‘Predecessor’ for SDTM and ADaM data and ‘COLLECTED’, ‘DERIVED’, ‘OTHER’, or ‘NOT AVAILABLE’ for SEND data. For Define-XML v2.1, the Origin Type attribute must have a value of ‘Collected’, ‘Derived’, ‘Assigned’, ‘Protocol’, or ‘Predecessor’ for SDTM, ‘Collected’, ‘Derived’, ‘Assigned’, ‘Protocol’, ‘Other’, ‘Predecessor’, or ‘Not Available’ for SEND, and ‘Derived’, ‘Assigned’, or ‘Predecessor’ for ADaM._

Thanks,  
Sergio

---

<div class="post-metadata">

**Author:** ![Trevor\_Mankus](https://sea1.discourse-cdn.com/certara/user_avatar/forum.certara.com/trevor_mankus/32/2650_2.png) [@Trevor\_Mankus](https://forum.certara.com/u/Trevor_Mankus)\
**Post date:** [September 22, 2026, 1:45pm UTC](https://forum.certara.com/t/unexpected-warning-define-2-1-send-3-1-1/4427/2 "2026-09-22T13:45:11Z")

</div>

Hi @sergio.garofalo

This is a known bug that we have already made a bug fix for. It just hasn’t made it through to P21C yet.

Thanks,

Trevor