As previously explained, with the rapid growth of the Internet, organizations are increasingly using the Web to conduct business with greater speed, reach, and efficiency. This transformation is especially prevalent in business-to-business (B2B) commerce and trade. Many of the Fortune 500 companies have adopted e-procurement systems such as Ariba (see sidebar, “Ariba”), Commerce One, and mySAP. Many others participate as buyers in e-marketplaces, such as Commerce One MarketSet, Ariba Hosted Market Place, and IBM’s WebSphere Commerce Suite, Marketplace Edition (WCS MPE, or MPE for short), among others.
B2B buyers have diverse procurement systems, such as those offered by Ariba, Commerce One, and SAP, among others. Each of these procurement systems uses different B2B protocols for interaction with seller systems. Many of these protocols are proprietary and specific to the procurement system. Check attached example:
Ariba uses the punchout process between the Ariba Order Request Management System (ORMS) and seller systems using their Commerce XML (cXML, or Commerce Extensible Markup Language) specification for the messages. Commerce One uses XML Common Business Library (xCBL) as the format of messages, and mySAP uses the Open Catalog Interface (OCI; for a process similar to punchout) between buyer and seller systems.
Many other protocols for B2B processes, many proprietary to procurement and other systems, and others customized for specific partners are being defined and implemented. In addition to the procurement systems, which typically reside within the firewall of the buying organizations, marketplaces are being set up on the Internet through which buyers can access a large number of suppliers, typically for specific industry segments. Many of these marketplaces use the same or similar technology to connect to procurement and supplier systems and offer buyers at small and medium-sized businesses access to suppliers.
Meanwhile, standards bodies are defining protocols and message formats for B2B processes. One of the early processes was that defined by the Open Buying on the Internet (OBI) consortium, a precursor of the punchout process. The RosettaNet consortium used OBI as a starting point and defined Partner Interchange Processes (PIPs), including both flows and XML-based message formats for interactions between partners. The electronic business XML (ebXML) framework (sponsored by the United Nations Center for the Facilitation of Procedures and Practices for Administration Commerce and Transport [UN/CEFACT] and the Organization for the Advancement of Structured Information Standards [OASIS]) includes a messaging service, a Collaborative-Protocol Agreement (CPA) specification, and a Business Processes Specification Schema. These are all used for enabling the interaction between business processes.
The Web services approach defines both a messaging and a remote procedure call mechanism using Simple Object Access Protocol (SOAP). On top of SOAP, the Web Services Description Language (WSDL) defines a Common Object Request Broker Architecture (CORBA) interface definition language (IDL)-like interface for Web-based B2B remote procedure calls. And, the Universal Description, Discovery, and Integration (UDDI) consortium has defined a directory mechanism for registering and locating businesses on the Web, with an optional WSDL interface specification. The Open Application Group (OAG) has defined Business Object Documents (BODs) for the content of B2B messages.
Some of these originally disparate efforts are now coming together. For example, the RosettaNet consortium has announced that they will move to the ebXML messaging protocol, and OAG has announced that they will support ebXML. In spite of these efforts, however, the number of B2B protocols continues to grow.
Friday, July 15, 2011
The Internet Environment
As previously explained, with the rapid growth of the Internet, organizations are increasingly using the Web to conduct business with greater speed, reach, and efficiency. This transformation is especially prevalent in business-to-business (B2B) commerce and trade. Many of the Fortune 500 companies have adopted e-procurement systems such as Ariba (see sidebar, “Ariba”), Commerce One, and mySAP. Many others participate as buyers in e-marketplaces, such as Commerce One MarketSet, Ariba Hosted Market Place, and IBM’s WebSphere Commerce Suite, Marketplace Edition (WCS MPE, or MPE for short), among others.
B2B buyers have diverse procurement systems, such as those offered by Ariba, Commerce One, and SAP, among others. Each of these procurement systems uses different B2B protocols for interaction with seller systems. Many of these protocols are proprietary and specific to the procurement system. Check attached example:
Ariba uses the punchout process between the Ariba Order Request Management System (ORMS) and seller systems using their Commerce XML (cXML, or Commerce Extensible Markup Language) specification for the messages. Commerce One uses XML Common Business Library (xCBL) as the format of messages, and mySAP uses the Open Catalog Interface (OCI; for a process similar to punchout) between buyer and seller systems.
Many other protocols for B2B processes, many proprietary to procurement and other systems, and others customized for specific partners are being defined and implemented. In addition to the procurement systems, which typically reside within the firewall of the buying organizations, marketplaces are being set up on the Internet through which buyers can access a large number of suppliers, typically for specific industry segments. Many of these marketplaces use the same or similar technology to connect to procurement and supplier systems and offer buyers at small and medium-sized businesses access to suppliers.
Meanwhile, standards bodies are defining protocols and message formats for B2B processes. One of the early processes was that defined by the Open Buying on the Internet (OBI) consortium, a precursor of the punchout process. The RosettaNet consortium used OBI as a starting point and defined Partner Interchange Processes (PIPs), including both flows and XML-based message formats for interactions between partners. The electronic business XML (ebXML) framework (sponsored by the United Nations Center for the Facilitation of Procedures and Practices for Administration Commerce and Transport [UN/CEFACT] and the Organization for the Advancement of Structured Information Standards [OASIS]) includes a messaging service, a Collaborative-Protocol Agreement (CPA) specification, and a Business Processes Specification Schema. These are all used for enabling the interaction between business processes.
The Web services approach defines both a messaging and a remote procedure call mechanism using Simple Object Access Protocol (SOAP). On top of SOAP, the Web Services Description Language (WSDL) defines a Common Object Request Broker Architecture (CORBA) interface definition language (IDL)-like interface for Web-based B2B remote procedure calls. And, the Universal Description, Discovery, and Integration (UDDI) consortium has defined a directory mechanism for registering and locating businesses on the Web, with an optional WSDL interface specification. The Open Application Group (OAG) has defined Business Object Documents (BODs) for the content of B2B messages.
Some of these originally disparate efforts are now coming together. For example, the RosettaNet consortium has announced that they will move to the ebXML messaging protocol, and OAG has announced that they will support ebXML. In spite of these efforts, however, the number of B2B protocols continues to grow.
B2B buyers have diverse procurement systems, such as those offered by Ariba, Commerce One, and SAP, among others. Each of these procurement systems uses different B2B protocols for interaction with seller systems. Many of these protocols are proprietary and specific to the procurement system. Check attached example:
Ariba uses the punchout process between the Ariba Order Request Management System (ORMS) and seller systems using their Commerce XML (cXML, or Commerce Extensible Markup Language) specification for the messages. Commerce One uses XML Common Business Library (xCBL) as the format of messages, and mySAP uses the Open Catalog Interface (OCI; for a process similar to punchout) between buyer and seller systems.
Many other protocols for B2B processes, many proprietary to procurement and other systems, and others customized for specific partners are being defined and implemented. In addition to the procurement systems, which typically reside within the firewall of the buying organizations, marketplaces are being set up on the Internet through which buyers can access a large number of suppliers, typically for specific industry segments. Many of these marketplaces use the same or similar technology to connect to procurement and supplier systems and offer buyers at small and medium-sized businesses access to suppliers.
Meanwhile, standards bodies are defining protocols and message formats for B2B processes. One of the early processes was that defined by the Open Buying on the Internet (OBI) consortium, a precursor of the punchout process. The RosettaNet consortium used OBI as a starting point and defined Partner Interchange Processes (PIPs), including both flows and XML-based message formats for interactions between partners. The electronic business XML (ebXML) framework (sponsored by the United Nations Center for the Facilitation of Procedures and Practices for Administration Commerce and Transport [UN/CEFACT] and the Organization for the Advancement of Structured Information Standards [OASIS]) includes a messaging service, a Collaborative-Protocol Agreement (CPA) specification, and a Business Processes Specification Schema. These are all used for enabling the interaction between business processes.
The Web services approach defines both a messaging and a remote procedure call mechanism using Simple Object Access Protocol (SOAP). On top of SOAP, the Web Services Description Language (WSDL) defines a Common Object Request Broker Architecture (CORBA) interface definition language (IDL)-like interface for Web-based B2B remote procedure calls. And, the Universal Description, Discovery, and Integration (UDDI) consortium has defined a directory mechanism for registering and locating businesses on the Web, with an optional WSDL interface specification. The Open Application Group (OAG) has defined Business Object Documents (BODs) for the content of B2B messages.
Some of these originally disparate efforts are now coming together. For example, the RosettaNet consortium has announced that they will move to the ebXML messaging protocol, and OAG has announced that they will support ebXML. In spite of these efforts, however, the number of B2B protocols continues to grow.
Subscribe to:
Post Comments (Atom)
Nice blog about punchout XML, it's being great to read this.
ReplyDeleteCXML Punchout
ReplyDeleteGood to read article about open catalog interface Punchout.
OCI Punchout
cXML Ariba Protocol - Vurbis Interactive used cxml ariba protocol created by ariba in 1999. It is based on XML and provides formal XML schemas for business transactions.
ReplyDeletecXML Ariba
Nice Blog..XML and provides formal XML schemas for business transactions.
ReplyDeletecXML Ariba