Repeating or regular transations?
Forum topic: Submitted by Anonymous on Fri, 2011-05-20 16:59.
Please forgive a newbie question, but I can't find the answer.
I am looking to implement a system where suppliers commit to regularly providing data to their customers. Is it possible to set up CPPs and a CPA to include the requirement for repeating information? Everything I have seen has shown a single transaction within the protocols.
The sort of thing I would like to do is:
Client:
-
- Request information x,y & z every 12 months, information a & b every quarter
Supplier:
-
- Accepts the requests for x,y & z but offers a & b every 6 months
Is this within the scope of ebXML?
Search
Recent Content
- TelCOMM – tool designed for B2B exchange of documents using AS4
3 years ago - Drummond Certifies AS4 and ebMS-based Software Applications in 2021’s 1st Quarter Interoperability Event
3 years ago - ISO Approves OASIS ebMS3 and AS4 as International Standards for Messaging
3 years ago - Use Python and Domibus for eDelivery Message Exchange
3 years ago - ebXML Messaging Protocol Binding for RegRep v1.0 approved as a Committee Specification
3 years ago - Collaboration Protocol Profile and Agreement v3.0 from ebCore TC approved as a Committee Specification
3 years ago
Subscribe
Navigation
Currently online: 2 guests and 0 users:
In CPP and CPA the scope is
In CPP and CPA the scope is really a message exchange in business transaction. A CPP/CPA may be linked to a business process definition, where you can define scenario, e.g. that an order is to be followed within some interval by an order response, and where you can relate a transaction (like ordering) to other transactions (like order cancellations). I think your use case is better handled at another (e.g. BAM) layer.
Pim