Creating Custom Identifier Types

10-4 Oracle Fusion Middleware Users Guide for Oracle B2B

10.2 Creating Custom Contact Information Types

Oracle B2B provides a centralized location for trading partner contact information. After you create a type, you can add it to a trading partners profile and change its value. You can create any type of contact information. You may want to create types for contact names, e-mail addresses, telephone and fax numbers, and so on. You can deleted unused types to further customize your B2B environment. A type that is used by a trading partner cannot be deleted. To create a contact information type: 1. Click the Administration link. HL7 File Application Universal ID Identifies the trading partner based on the HL7 file application universal ID. HL7 File Application Universal ID Type Identifies the trading partner based on the HL7 file application universal ID type. HL7 File Facility ID Identifies the trading partner based on the HL7 file facility ID. This field further describes the sendingreceiving application. The facility ID can have an organizational entity, unit, product or vendors identifier. HL7 File Facility Universal ID Identifies the trading partner based on the HL7 file facility universal ID. HL7 File Facility Universal ID Type Identifies the trading partner based on the HL7 file facility universal ID type. HL7 Message Application ID Identifies the sendingreceiving application. HL7 Message Application Universal ID For outbound messages, this field is used to override the Message Application Universal ID, which is MSH.3 for the sender and MSH.5 for the receiver. For inbound messages, this field is used for lookup. HL7 Message Application Universal ID Type For outbound messages, this field is used to override the Message Application Universal ID Type, which is MSH.3 for the sender and MSH.5 for the receiver. For inbound messages, this field is used for lookup. HL7 Message Facility ID Identifies the trading partner based on the HL7 message facility ID. HL7 Message Facility Universal ID For outbound messages, this field is used to override the Message Facility Universal ID, which is MSH.4 for the sender and MSH.6 for the receiver. For inbound messages, this field is used for lookup. HL7 Message Facility Universal ID Type For outbound messages, this field is used to override Message Facility Universal ID, which is MSH.4 for the sender and MSH.6 for the receiver. For inbound messages, this field is used for lookup. MLLP ID The TCPIP Minimum Lower Layer Protocol MLLP is the standard for HL7. The MLLP ID and the Name identifier are required for MLLP exchanges. Name Identifies the trading partner by its name. The value for this type is automatically supplied when you create or edit the trading partner name, for example, Acme or GlobalChips. The Name identifier is required for Generic File, Generic FTP, Generic SFTP, Generic AQ, and Generic JMS exchanges. ebMS Identifier This type, OASIS ebXML Messaging Services ebXML, specifies a secure and reliable way to exchange messages using HTTP, HTTPS, SOAP, XMLDsig, and XMLEncrypt. The ebMS Identifier and the Name identifier are required for ebMS exchanges. Table 10–1 Cont. Identifier Types Defined in Oracle B2B Name Description Creating Types 10-5

2. Click the Types tab.

3. In the Contact Information area, click Add.

4. Provide a name for the contact information type, an optional description, and click Save . The string that you provide in the Name field is displayed in a list under the Type field on the Partners Profile page. See Task 4, Add Contact Information on page 5-6 for how to add the new type and a value to a trading partners profile.

10.3 Creating Custom Trading Partner Parameter Types

Trading partner parameter types are string types. After you create a type, you can add it to a trading partners profile and change its value. To create a trading partner parameter type and default value: 1. Click the Administration link. 2. Click the Types tab. 3. In the Trading Partner Parameters area, click Add. 4. Provide the following information and click Save. ■ Name required ■ Default Value optional ■ Group Name optional ■ Display Name optional; however, the value of Display Name, not Name, appears when you add this type to a trading partner profile ■ Description optional See Task 5, Add a Trading Partner Parameter and Value on page 5-6 for how to add the new type and a value to a trading partners profile. There are no predefined trading partner parameter types. You may want to create a type named Country, for example. Then the value—a specific country code—can be configured for each trading partner. You can deleted unused types to further customize your B2B environment. A type that is used by a trading partner cannot be deleted. 10-6 Oracle Fusion Middleware Users Guide for Oracle B2B 11 Batching EDI Messages 11-1 11 Batching EDI Messages For outbound messages, use the Oracle B2B interface to batch, schedule, and send outbound EDI X12 and EDI EDIFACT messages. Inbound messages to Oracle B2B are automatically debatched. This chapter contains the following topics: ■ Section 11.1, Setting Up a Batch ■ Section 11.2, Managing Batched Messages See the following for more information about EDI: ■ Section 8.2, Using the EDI EDIFACT Document Protocol ■ Section 8.3, Using the EDI X12 Document Protocol

11.1 Setting Up a Batch

Batching is often used to group messages by document type; for example, you may want to send out a batch of purchase orders or a batch of invoices, to one or more trading partners. You can also batch multiple document types, sent to one or more trading partners. When batching more than 1000 documents, where the payload size is greater than 30 KB, specific settings are required. See Settings for Batching a Large Number of Documents in Oracle Fusion Middleware Performance Guide. Figure 11–1 shows where you set up a batch transmission of EDI messages.