Home | Imprint | Contact 
   Overview

  TecCom Home
  CAP-Standard
   What is CAP?
     Management
     History
   News
   Founding Members
   Download
   Message Standards
   Support
   FAQ
   Forum
   Productive Users

 


   Frequently Asked Questions
Don't hesitate to get in contact with the CAP helpdesk at TecCom. They know everything you want to know about the CAP Standard.

The helpdesk can be contacted via email caphelpdesk@teccom.de or for urgent matters during office hours by dialling +49 (0)89-32 12 16-111.


Q: Is it possible to obtain the XSD File concerning the CAP Order message?
 
A: One can download the XSD files for all the CAP messages from the Download page. 


Q: What's the meaning of respAgency "92" for the Supplier and "91" for the Buyer.
Concerning the Buyer, the PartyId is our Customer number to the supplier concerned by the order ?
 
A: Example:

<Supplier>
   <PartyId respAgency="92">11111</PartyId>
</Supplier>
<Buyer>
   <PartyId respAgency="91">22222</PartyId>
</Buyer>

The Supplier is known as code 11111 by the Buyer.
The Buyer is known as code 22222 by the Supplier.
It is not possible for the respAgency to equal 91 within the Supplier element, as this would mean the code with which the supplier is known by itself. The same is true for respAgency code 92 in the Buyer element.  


Q: As a software developer I've been searching through quite a big part of the internet looking for some CAP Availabilityrequest / response example files to test my schema definitions and maps as well as the parser.
I haven't found a single file at all.
Can you perhaps help me out?
 
A: One can download CAP Examples for all the CAP messages from the Download page. 


Q: Please provide clarification on the proper interpretation of the 'action' attribute of a Line item in an OrderResponse. Specifically, what are the circumstances where a supplier should return "3 - changed" and "24 - accepted with amendment"? Both imply that the original request was modified in some way. The question is what was modified and how? Does one type of change take precedence over another? Any clarifying documentation, examples or use cases would be appreciated.
 
A: Regarding the 'action' attribute in the OrderResponse Line element, for all the actions ( 3, 5, 7, 24 ) one uses the QtyDiff element to explain the reason for the action. An action '3 - changed' means that the ordered item has changed and that the ordered item has therefore not been accepted. The item will have to be reordered.
An action '24 - accepted with amendment' means that there are changes and that even though there were changes the ordered item is processed.