1. Curtis Can Protocol Document Converter
2. Curtis Can Protocol Documents
3. Curtis Can Protocol Document Search

8.1 Using the Custom Document ProtocolOracle B2B supports custom document protocols to create documents needed for proprietary transactions. With XML messages, you have the advantage of schema enforcement (XSDs).With non-XML messages, you can create trading partner agreements for specific message types.When creating a Custom document, you specify rules to identify the incoming document. For XML documents, specify an XPath expression and a value, which is the expected result of the expression.For non-XML documents such as a flat file, you can specify start and end positions or a document routing ID.Document Version ParametersNo parameters need to be set when you create the document version for a Custom document.Document Type ParametersWhen you create a Custom document type, you can set ebXML messaging service (ebMS) parameters to identify the ebXML document.

Shows the document type parameters for a Custom document. Table 8-1 Document Type Parameters for a Custom Document ParameterDescriptionebMS Tab-Action nameThe action name for the ebXML header, which is also an identification criteria for inbound and outbound messages. EbMS documents require an action name to avoid run-time errors.Service nameThe service name for the ebXML header, which is also an identification criteria for inbound messages. EbMS documents require a service name to avoid run-time errors.Service typeThe service type for the ebXML header, which is also an identification criteria for inbound messages. EbMS documents require a service type to avoid run-time errors.From RoleThe trading partner that sends the message. A value provided here overrides the Identifiers values supplied on the Profile tab.To RoleThe trading partner that receives the message. A value provided here overrides the Identifiers values supplied on the Profile tab.Vaildate ebMS HeaderWhen selected, validates inbound ebMS header from role, to role.CPA FileCPA fileDocument Definition ParametersWhen you create a Custom document definition, select the file type—XML or Flat—and set parameters in the tabbed areas.

Shows the document definition parameters for an XML-type Custom document. Table 8-2 Document Definition Parameters for a Custom Document ParameterDescriptionXML Tab(Available if XML is selected from Identification Type)Identification Expression (XPath)Locates a node in the XML payloadIdentification ValueProvides the value to match in the node identified by the Identification Expression. If the values match, then the document is successfully identified. Example 8-1 Specify the XPath and the Matching Value34561-0-0String. Example 8-2 Check for the Existence of a Node791:1EB3CDC749A1F2BABE03014906CC4605AoraclesupXSD974050142.

Curtis Can Protocol Document Converter

8.2 Using the EDI EDIFACT Document ProtocolOracle B2B supports message exchanges using UN/EDIFACT, the United Nations Electronic Data Interchange for Administration, Commerce and Transport. These standards prescribe the formats, character sets, and data elements used in purchase orders and invoices.Oracle B2B supports all versions and document types of EDI EDIFACT, although for some of the newer versions you may need to add the interchange and group guidelines while creating the document version. Lists a few of the transaction sets supported in Oracle B2B. Table 8-4 Document Version Parameters for an EDI EDIFACT Document ParameterDescriptionInterchange Tab-Create UNASelect from always, never, or delimiter-based. If delimiter-based is selected, then UNA is created if the specified delimiters are different from the EDIFACT default value.

The Never option does not generate UNA for outbound EDIFACT documents, even if nondefault delimiters are used. The Never option for inbound messages cannot work for B2B if an EDIFACT document is received without UNA and with nondefault delimiters.Syntax IdentifierCoded identification of the agency controlling syntax and syntax level used in an interchange. EDI position UNB 010 010 S001 0001. The value UNOB is supplied.Syntax Version NumberVersion number of the syntax identified in the syntax identifier (0001).

EDI position UNB 010 020 S001 0002. The value 1 is supplied.Service Code List Directory Version NumberVersion number of the service code list directory. EDI position UNB 010 030 S001 0030.Character EncodingCoded identification of the character encoding used in the interchange. To be used as specified in the partners' interchange agreement, for the purpose of identifying the character repertoire encoding technique used in the interchange (when the default encoding defined by the character repertoire's associated character set specification is not used). EDI position UNB 010 040 S001 0133.Interchange DateLocal date when an interchange or a group was prepared.

EDI position UNB 030 010 S004 0017. The value #SystemDate(YYMMDD)# is supplied.Interchange TimeLocal time of day when an interchange or a group was prepared. EDI position UNB 030 020 S004 0019. The value #SystemTime(HHMM)# is supplied.Recipient's Reference/PasswordReference or password to the recipient's system or to a third-party network as specified in the partners' interchange agreement.

To be used as specified in the partners' interchange agreement. It may be qualified by data element 0025. EDI position UNB 060 010 S005 0022.Recipient's Reference/Password QualifierQualifier for the recipient's reference or password. To be used as specified in the partners' interchange agreement.

EDI position UNB 060 020 S005 0025.Application ReferenceIdentification of the application area assigned by the sender, to which the messages in the interchange relate; for example, the message type, if all the messages in the interchange are of the same type. Identification of the application area (for example, accounting, purchasing) or of the message type, as applicable. EDI position UNB 070.Processing Priority CodeCode determined by the sender requesting processing priority for the interchange. To be used as specified in the partners' interchange agreement. EDI position UNB 080.Interchange Agreement IdentifierIdentification by name or code of the type of agreement under which the interchange takes place. Name or code to be specified in the partners' interchange agreement. EDI position UNB 100.Test IndicatorIndication that the structural level containing the test indicator is a test.

EDI position UNB 110.Interchange ecs FileUse the Browse button to find an ecs file to override the standard file. If not provided, the B2B-provided default file (interchange ecs file of the syntax version number, UNB 010 020) is used.Group Tab-Create Functional GroupIndication of function group (UNG) creation. The value TRUE is supplied.Date of Group PreparationLocal date when an interchange or a group was prepared.

EDI position UNG 040 010. The system date stamp is supplied.Time of Group PreparationLocal time of day when an interchange or a group was prepared. EDI position UNG 040 020. The system time stamp is supplied.Controlling AgencyCode identifying a controlling agency. EDI position UNG 070 010. The value UN is supplied.Group Association Assigned CodeCode assigned by the association responsible for the design and maintenance of the message type concerned that further identifies the message.

EDI position UNG 070 030.Application PasswordPassword to the recipient's division, department or sectional application system/process. EDI position UNG 080.Group ecs FileUse the Browse button to find an ecs file to override the standard file. If not provided, the B2B-provided default file is used.Delimiters TabA delimiter is characterized by two levels of separators and a terminator assigned by the sender.

Delimiters are also called service characters, data delimiters, or message delimiters. They are specified in the interchange header and cannot be used in a data element value elsewhere in the interchange. In an EDI file, the segment delimiter, the element delimiter, and the subelement delimiter are used.Note: Click Select Hexadecimal Characters next to any of the delimiter fields to provide values.Segment DelimiterEDIFACT segment delimiter. The value 0x27 is supplied.Element DelimiterEDIFACT element delimiter. The value 0x2b is supplied.Subelement DelimiterEDIFACT subelement delimiter. The value 0x3a is supplied.Decimal SeparatorEDIFACT decimal separator. The value 0x2e is supplied.Release CharacterEDIFACT release character.

The value 0x3f is supplied.Replacement CharacterEDIFACT replacement character. The value 0x7c is supplied.Repeating SeparatorEDIFACT repeating separator. The value 0x2a is supplied.Miscellaneous Tab-Check Duplicate Control NumberWhen this property is selected (set to true), messages with duplicate interchange control numbers are rejected, meaning that the state of the incoming message is set to ERROR.Ignore Envelope ParametersUse this option to provide a list of envelope elements, separated by commas, to be ignored during look-up validation. The possible values depend on the identifiers used in the agreement.

Possible values include InterchangeSenderID, InterchangeReceiverID, GroupReceiverID, GroupSenderID, TransactionAssociationAssignedCode, InterchangeReceiverQual, InterchangeSenderQual, and InterchangeControlVersion.Document Type ParametersWhen you create an EDI EDIFACT document type, you can set various parameters. Shows the document type parameters for an EDI EDIFACT document. Table 8-5 Document Type Parameters for an EDI EDIFACT Document ParameterDescriptionTransaction Tab-.Functional Group Identifier CodeCode identifying one type of message in a functional group. EDI position UNG 010 0038. Required.Controlling AgencyCode identifying the agency controlling the specification, maintenance and publication of the message type. EDI position UNH 020 040 S009 0051.Transaction Association Assigned CodeCode, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message. EDI position UNH 020 050 S009 0057.Common Access ReferenceReference serving as a key to relate all subsequent transfers of data to the same business case or file.

EDI position UNH 030 0068.Document Definition ParametersWhen you create an EDI EDIFACT document definition, you can set various parameters. Shows document definition parameters for an EDI EDIFACT document. 8.3 Using the EDI X12 Document ProtocolOracle B2B supports message exchanges using American National Standards Institute (ANSI) X12. These standards prescribe the formats, character sets, and data elements used in documents such as purchase orders and invoices.Oracle B2B supports all versions and document types of EDI X12, although for some of the newer versions you may need to add the interchange and group guidelines while creating the document version. Lists a few of the transaction sets supported in Oracle B2B. Table 8-8 Document Version Parameters for an EDI X12 Document ParameterDescriptionInterchange Tab-Authorization Information QualifierCode to identify the type of information in the authorization information. EDI position ISA 01.

The value 00 is supplied.Authorization InformationInformation used for additional identification or authorization of the sender or the data in the interchange. The authorization information qualifier sets the type of information. EDI position ISA 02.Security Information QualifierCode to identify the type of information in the security information. EDI position ISA 03. The value 00 is supplied.Security InformationInformation used to identify the security information about the interchange sender or the data in the interchange. The security information qualifier sets the type of information.

EDI position ISA 04.Interchange DateDate of the interchange. EDI position ISA 09.

The system date stamp is supplied ( #SystemDate(YYMMDD)#).Interchange TimeTime of the interchange. EDI position ISA 10.The system time stamp is supplied ( #SystemTime(HHMM)#).Interchange Control Standard/Repetition SeparatorCode to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer. EDI position is ISA 11. The value U is supplied.Interchange Control Version NumberCode specifying the version number of the interchange control segments. EDI position ISA 12. The value 00401 is supplied.Usage IndicatorCode to indicate whether data enclosed by this interchange envelope is in test or production.

EDI position ISA 15. The value P, for production, is supplied.Interchange ecs FileUse the Browse button to find an ecs file to override the standard file. If not provided, the B2B-provided default file (interchange ecs file of the interchange control version, ISA 12) is used.Group Tab-Functional Group DateDate sender generated a functional group of transaction sets. EDI position GS 04.

The system date stamp is supplied ( #SystemDate(CCYYMMDD)#).Functional Group TimeTime when the sender generated a functional group of transaction sets (local time at sender's location). EDI position GS 05.The system time stamp is supplied ( #SystemTime(HHMM)#).Responsible Agency CodeCode used in conjunction with data element 480 to identify the issuer of the standard. EDI position GS 06. Table 8-9 Document Type Parameters for an EDI X12 Document ParameterDescriptionTransaction Tab-.Functional Group Identifier CodeUniquely identifies a transaction set GS 01. Required.Implementation Convention ReferenceReference assigned to identify Implementation Convention. EDI position ST 03.Transaction Purpose CodeCode identifying the purpose of the transaction set. EDI position BEG/BGN 01.Duplicate Transaction TabThis feature enables you to detect the duplicate transactions by considering specific content in the payload (such as Purchase Order number and invoice number).This is achieved by providing the XPath for the specific tag of the payload.

The three XPath fields provide the flexibility to arrive at the uniqueness criteria with multiple values of the payload.For inbound, this adds an additional check during the Oracle B2B inbound message processing to check duplicate control numbers. The XPath-based duplicate check is done after the control number check.Note: You cannot specify the second/third XPath without specifying the first XPathDocument Definition ParametersWhen you create an EDI X12 document definition, you can set various parameters. Shows document definition parameters for an EDI X12 document.

Table 8-11 Document Version Parameters for an HL7 Document ParameterDescriptionMessage Header Tab-SecurityIn some applications of HL7, this field is used to implement security features.Processing IDMSH.11 - This field is used to decide whether to process the message as defined in HL7 Application (level 7) processing rules. The first component defines whether the message is part of a production, training, or debugging system (refer to HL7 table 0103 - Processing ID for valid values). The second component defines whether the message is part of an archival process or an initial load (refer to HL7 table 0207 - Processing mode for valid values). This allows different priorities to be given to different processing modes.Accept Acknowledgement TypeSets the conditions under which application acknowledgments are required to be returned in response to the message. The value AL (always) is supplied.B2B checks the payload (MSH.15) of an incoming message to see if an ACK has to be generated.

In some HL7 Systems, MSH.15 is not sent in the payload at all and it is expected that an ACK is still sent.Application Acknowledgment TypeMSH.16. The value AL (always) is supplied.Country CodeSets the country of origin for the message. The value US is supplied.Character SetSets the character set for the entire message.

Table 8-12 Document Type Parameters for an HL7 Document ParameterDescriptionTransaction Tab-HL7 Generic ACKIf selected, Oracle B2B sends a generic ACK immediately upon receiving an HL7 message.Map ACK Control IDSelect to enable mapping the MSH.10 of the business message to the MSH.10 of the acknowledgment.Note: This Map ACK Control ID parameter is for the functional ACK.Accept AcknowledgementA functional acknowledgment is generated when MSH.15 has no value. Select None to take no action.

Acknowledgment generation is dependent on the value in MSH.15 of the business message. Select AL (always) to generate the acknowledgment under any conditions. Select ER (error/reject) to generate the acknowledgment when the message errors or is rejected. Select SU (successful completion) to generate the acknowledgment when the message is successfully processed.Document Definition ParametersWhen you create an HL7 document definition, you can set various parameters. Shows document definition parameters for an HL7 document.

Curtis Can Protocol Documents

8.5 Using the OAG Document ProtocolOracle B2B implements Open Applications Group (OAG) standards, a robust XML standard used across many industries. This standard defines messages as business object documents (BODs).For information about the organization that created and maintains the OAG standards, go toDocument Version ParametersNo parameters need to be set when you create the document version for an OAG document.Document Type ParametersWhen you create an OAG document type, you can set various parameters. Shows the document type parameters for an OAG document. Table 8-14 Document Type Parameters for an OAG Document ParameterDescriptionControl Area Tab-Logical IdentifierLogical IdentifierComponentComponentTaskTaskFA on ErrorWhen enabled, CONFIRMATION flag is set to 1.LanguageLanguageCode PageCode PageAuthorization IdentifierAuthorization IdentifierDate Time QualifierDate Time Qualifier attributeDocument Definition ParametersWhen you create an OAG document definition, you can set various parameters. Shows document definition parameters for an OAG document. Table 8-15 Document Definition Parameters for an OAG Document ParameterDescriptionXML Tab-Identification Expression (XPath)Locates a node in the XML payloadIdentification ValueProvides the value to match in the node identified by the identification expression. If the values match, then the document is successfully identified.

Note:Positional flat files must be manually upgraded from 10 g to 11 g.Document Version ParametersNo parameters need to be set when you create the document version for a positional flat file.Document Type ParametersNo parameters need to be set when you create the document type for a positional flat file.Document Definition ParametersWhen you create a document definition for a positional flat file, you can set various parameters. Shows document definition parameters for a positional flat file. 8.7 Using the RosettaNet Document ProtocolOracle B2B implements the nonproprietary, XML-based RosettaNet standards to exchange documents over the Internet. RosettaNet standards prescribe when information should be exchanged, acknowledged, or confirmed, and how messages in an exchange should be packaged and physically exchanged between trading partners. In addition to using the RosettaNet document guideline files in Oracle B2B Document Editor, you can also download standard DTD files from the RosettaNet Web site.A RosettaNet DTD, when used with Oracle B2B in a SOA composite application, must be converted to an XSD.

Curtis Can Protocol Document Search

An AQ Adapter added to the composite application can convert the inbound DTD to an XSD and manipulate the data as needed. Likewise, the AQ Adapter can convert the outbound XSD to a DTD for Oracle B2B to send the message out.RosettaNet standards are specified by using of the RosettaNet Partner Interface Process (PIP), RosettaNet Dictionaries, and RNIF. Oracle B2B supports all PIPs. (The RosettaNet Technical Dictionary is not supported in Oracle B2B.)For information about the RosettaNet consortium and its history, and for a complete list of PIP clusters and segments, go to. Table 8-18 Document Type Parameters for a RosettaNet Document ParameterDescriptionService Header Tab-.From RoleThe trading partner that sends the message (in Partner Role Description of the PIP).To RoleThe trading partner that receives the message (the role the trading partner receiving the message plays in the PIP).From ServiceThe service that sends the message.To ServiceThe service to which the message is sent.Business Transaction NameThe name of the business transaction is required.Business ActionThe name of the business action is required. The value must be consistent with the Global Business Action Code.Time to Perform for CollaborationThe time to perform the business action is required.Collaboration NameThe RosettaNet collaboration name signifies the business transaction between trading partners (the roles as buyer and seller) depending on a common transaction. Required.Collaboration CodeThe textual form of the abbreviated collaboration name.

Required.Document Definition ParametersWhen you create a RosettaNet document definition, you can set various parameters. Shows the document definition parameters for a RosettaNet document. Table 8-19 Document Definition Parameters for a RosettaNet Document ParameterDescriptionParameters Tab-Document Routing IDSets the consumer name to the back-end applicationDTD/XSD Namespace ConversionA converted document can optionally replace the original RosettaNet document. Select Both to replace the RosettaNet document with the converted document for both the inbound and outbound messages. Select Inbound to replace the RosettaNet document with the converted document for the inbound message. Select Outbound to replace the RosettaNet document with the converted document for the outbound message. Select None for no replacement.

None passes the DTD instance as-is. Inbound converts the instance DTD to XSD. Outbound converts the instance XSD to DTD. 8.7.2 RosettaNet ValidationRosettaNet validation compares the elements in RosettaNet XML-format business documents to the requirements specified in the RosettaNet Message Guideline specification to determine their validity. This specification defines requirements for details such as element datatypes, element lengths, element value lists, and element cardinality.

PIPs that require RosettaNet dictionary validation are also validated when a dictionary is present.The minimum validation-level requirements on the sections of a RosettaNet XML-format business document are as follows. These requirements cover the preamble, delivery header, service header, and service content sections of a document.

Table 8-21 Document Definition Parameters for a UCCnet Document ParameterDescriptionXML Tab-Identification Expression (XPath)Locates a node in the XML payloadIdentification ValueProvides the value to match in the node identified by the Identification Expression. If the values match, then the document is successfully identified. 8.9 Changing Document DetailsDocument details—document protocol versions and document type parameters—can be changed for a remote trading partner from the Partners Documents tab. Host administrators can change any remote trading partner's document details here (host administrators must change their own data on the Administration Document tab), and remote administrators can change document details for their own data, if the remote administrator has been granted access to those document types. See for more information.shows the Version tab in the Document Details section, where parameters for the document protocol version can be changed. Figure 8-25 Changing Document DetailsUse the Override Version Param and Override DocType Param parameters to indicate that override values are provided.

Document type parameter values set for a remote trading partner take precedence over the default document type parameter values set for the document definition when the document was created on the Administration Document tab.To override document details:.Click the Partners tab.Click the Documents tab.Select a remote trading partner.Select a document definition.Select the override types that apply:.Override Version Param.Override DocType Param.Provide values to override values on the Version tabs or the Document Type tabs, or both.Click Save. 8.10 Using Document Routing IDsA document routing ID is useful in two circumstances: when enqueuing to an AQ queue and when using B2B documents in a SOA composite application. If you set a document routing ID for messages enqueued to an AQ queue (inbound only), then the AQ consumer name is set to the document routing ID.

Within a SOA composite application, if you use a document routing ID in your B2B binding component instead of the document definition, then all messages with the same document routing ID are routed to the same SOA composite.This is useful if you have many different document definitions, but you want them to be handled the same way. The WSDL uses the document routing ID instead of the document definitions. In a SOA composite application, the B2B Configuration Wizard provides an option to use the document routing ID instead of selecting a document definition, as shown in.