SOA
>
COMPLY-SYNCH Message
COMPLY-SYNCH Message
This processcompliance.xml message is sent when a user checks compliance without processing a shipment. For example, a user sends a query from an ERP system when processing an order. This check is usually synchronous. The check types are based on what you configure in the message to be checked instead of on the workflow type. The following COMPLY_SYNCH message snippet runs denied party and embargoed country checks.
<ComplianceChecks>
<PartyCheckType>
<Type>DeniedPartyList</Type>
<Type>Keyword</Type>
<Source>*ALL</Source>
</PartyCheckType>
<CountryCheckType>
<Type>EmbargoedCountry</Type>
</CountryCheckType>
</ComplianceChecks>
The following COMPLY_SYNCH message snippet runs license checks on item lines.
<ComplianceChecks>
<ECCNCheckType>
<Type>EccnExportLicense</Type>
</ECCNCheckType>
<LicenseCheckType>
<Type>ExportLicense</Type>
</LicenseCheckType>
</ComplianceChecks>
The following COMPLY_SYNCH snippet runs all six data integrity checks. In addition to these checks, this section also processes a questionnaire.
<ComplianceChecks>
<DataIntegrityCheckType>
<Type>PartnerValidIso</Type>
<Type>ProductValidCoo</Type>
<Type>ProductValidEccnExp</Type>
<Type>ProductValidEccnUs</Type>
<Type>ProductValidHts</Type>
<Type>ProductValidHtsGroup</Type>
</DataIntegrityCheckType>
<QuestionCheckType>
<Level>TRANS</Level>
<Type>TFSQ1</Type>
<Type>QUE_1</Type>
</QuestionCheckType>
</ComplianceChecks>
The following line in the message enables you to specify the type of compliance results returned. You can choose from brief, intermediate, and complete.
<ResultType>Complete</ResultType>
Note: For the processcompliance.xml message, it is not mandatory to specify a shipment type. When no shipment type is specified, there is a default check on the bill to, consignee, and any associated override addresses.