Oracle Business Network - Punchouts

Punchouts let you integrate account-based stores with your procurement system.

This integration allows a buyer who is logged into a procurement system to access a Commerce storefront, view items from the assigned catalog, add items to the cart, and return to the procurement system.

Once the procurement system approves the purchase, it sends supplier a purchase order, which becomes a sales order on their end.

Traditionally, punch-outs can be configured in the Oracle iProcurement portal but this functionality can also be achieved via Oracle Business Network (OBN).


Traditional Punchouts EBS:

Traditional Setup Challenges:

- Individual certificate management for each vendor

- Connectivity handshake/errors, errors in returning carts

- Catalog Administration maintenance

Punch-out Process through OBN:

- The buyer logs on to iProcurement. 

- Buyer clicks a link to the supplier site from iProcurement. 

- OBN authenticates the requester and sends a punchout request to the supplier.

- The supplier site responds to OBN.

- OBN forwards the supplier site response to iProcurement.

- iProcurement redirects the requester’s browser to the supplier site for shopping.

- Once buyer finishes shopping, the supplier site returns the shopping cart items to iProcurement via the requester’s browser. 

- Buyer completes the checkout process, and iProcurement processes the order.

OBN Configurations:

- Navigate to PunchOut section

- Click on Add Punchout button

- This should show a pop-up containing all the available Punchouts from various vendors who have registered on OBN

- Select the desired Punchout from the list and click Add Access. Once added, it will appear in Buyer Access section

- Now, navigate to EBS and create a new Punchout Content Zone as below

Punchout URL: https://osn-prod.oracle.com/punchout/punchoutloginserver

User Name: Your OBN User
Password: Password for above user

- Save and navigate to above Content Zone entry and click below button

- This will present below page from where you need to click Download button

- This will download a file containing the Punchout definition for the configured vendors and they will be available in your catalog for use.

Oracle Business Network – Supported Transactions:

Common Transactions Types:

- Purchase Order - OAG PROCESS PO 007 and cXMLOrderRequest

- Change Purchase Order - OAG CHANGE PO 006 and cXMLOrderRequest Update

- Advance Ship Notice (ASN) - OAG SHOW SHIPMENT 005 and cXMLShipNoticeRequest

- Invoice - OAG PROCESS INVOICE 002 and cXMLInvoiceDetailRequest

Available Document Types:

Oracle Business Network – PO Transmission Setups (EBS)

Lets look at all the EBS configurations needed for PO transmission via OBN


- Certificate Management

Navigate to osn-prod URL and download the certificate as shown below:

- Download and Import above certificate into $INST_TOP/certs/Apache/cwallet.sso


- EBS XML Gateway Hub Definition:

- Trading Partner Setup:

Configure new a new entry for a given supplier using Map 'itg_process_po_007_out' as shown below.

Oracle Business Network – AP Invoice Import Setups (EBS)

- Trading Partner Setup:

Configure new a new entry for a given supplier using Map 'AP_INVOICE_INBOUND' as shown below.

With all above steps completed, you would have Supplier Punchouts, PO Transmission Outbound and AP Invoice Inbound processes configured using Oracle Business Network.

Read More

Oracle Business Network - Deep Dive

In my previous post, I shed light on basics of Oracle Business Network and it's capabilities.

Let's take a deep dive into OBN configurations as well as corresponding EBS setups and it's uses.


OBN Home Page

Once you login to OBN, here's what you see on Home Page. You'll see various tabs such as Profile, Messaging, Partners, Monitor etc.

Company Profile

Profile page let's you maintain your company's profile details. This is mainly for information purpose only.

Messaging Setup

This is one of the crucial setup pages. We can define various Communication Parameters as well as Transaction configurations here.

In below example, we are configuring two transactions:

1. Send POs from EBS to Trading Partner

2. Receives Invoices from Trading Partner to EBS

Now, let's take a look at Delivery Method configuration

We have defined two Delivery Methods:

1. Oracle XML Transport Agent - Used to specify EBS server details. This is how OBN connects to our EBS instance.
2. HTTPS URL Connection - Used to specify OBN server details. This is to make connection to our OBN account through which the messages/documents are exchanged with Trading partners.

Oracle XML Transport Agent:
As shown below, we need to specify Transport Agent URL here, one pertaining to Test Environment and another pertaining to Production Environment; along with the EBS user credentials.
Usually, the best practice is to create a dedicated user in EBS for such purposes so that we can track all incoming and outgoing transactions to and from OBN.

HTTPS URL Connection:

As shown below, we need to specify OBN specific URLs here, one pertaining to Test Environment and another pertaining to Production Environment; along with our OBN user credentials.

The URLs are usually fixed for Test and Production Hubs:

OBN Test Hub HTTPS URL: https://osn.oracle.com:443/HTTPService/Receiver OR https://osn.oracle.com/HTTPService/Receiver

OBN Production Hub HTTPS URL: https://osn-prod.oracle.com:443/HTTPService/Receiver OR https://osn-prod.oracle.com/HTTPService/Receiver

Let's take a look at Transaction Management configuration

For Invoice transaction, we use below parameters:

Document Format: OAG
Format Version: 002

Document Type: PROCESS_INVOICE_002
Action: Receive

And, we choose Oracle XML Transport Agent for both Test and Prod instances:

For, Purchase Order transaction, we use below parameters:

Document Format: OAG
Format Version: 007

Document Type: PROCESS_PO_007
Action: Send

And, we choose Oracle XML Transport Agent for both Test and Prod instances:

We can test our configuration by sending a dummy/test document by accessing Send Document tab as shown below.

Here, we can use Test Hub and Document Type from above steps (PROCESS_PO_007) and upload the test payload/file to test out configuration.

Trading Partner Setup

Now, let's take a look at how we can add new Trading Partners and maintain the current ones.

Under Partners tab, we can see Add Trading Partners option. This lets you Search the desired Trading partner from the list and add them to our OBN account.

Note: The trading partner must have registered on OBN for you to search and add them; or else you won't see them in the list of registered OBN partners.

Under Pending Approval tab, we will be able to see all the trading partners we added to our account but are still pending approval from their end.

Once we add a trading partner in our OBN account, the corresponding partner admin gets a notification asking to approve this request. Only once they approve your request, they will appear as Approved under your trading partners list.

All the Trading Partners that you added in your OBN account will appear under Your Trading Partners tab. This includes the ones that are Approved as well as the ones that are Pending Approval.

Monitoring the inbound and Outbound Transactions

Navigate to Monitor tab and we'll see two options: Sent Messages and Received Messages

Sent Messages:
If we click on download button against any Sent Message, it will let us download Pre-Transform or Post-Transform document. I've explained about these in my previous post.

If we wish to Resend any message, then we can click on Resend button and click OK. This will Resend that particular message to Trading Partner.
This is useful especially when there's a transmission failure which may happen for a number of reasons one of which could be that Trading partner server was down or was under maintenance and now you need to resend all pending/failed messages; this feature comes handy in such cases.
You can also use Resend All option to Resend all the desired messages to Trading Partner.

Received Messages:
Similarly, we can monitor all Incoming messages under Received Messaged tab. Here also, we have similar options either to download the Pre and Post transform documents and also to Resend the message to EBS server.

Supported Transaction Types

Below are some of the Common Transactions Types supported by OBN:

Purchase Order - OAG PROCESS PO 007 and cXMLOrderRequest

Change Purchase Order - OAG CHANGE PO 006 and cXMLOrderRequest Update

Advance Ship Notice (ASN) - OAG SHOW SHIPMENT 005 and cXMLShipNoticeRequest

Invoice - OAG PROCESS INVOICE 002 and cXMLInvoiceDetailRequest

Available Document Types:





EBS Configurations for OBN

Now, let's see what all configurations we need to do in EBS in order to connect to OBN and exchange the messages.


Certificate Management

Navigate to OBN Test or Prod URLs and download the certificate for the same.



Import the certificate into $INST_TOP/certs/Apache/cwallet.sso


Hub Definition in EBS

We need to define a new Hub in EBS using either Test or Prod URL of OBN as shown below:





PO Transmission (Outbound) Setup

Navigate to Trading Partner Setup and create a new entry using itg_process_po_007_out Map as shown below:







AP Invoice (Inbound) Setup

Navigate to Trading Partner Setup and create a new entry using AP_INVOICE_INBOUND Map as shown below:






Voila ! We have finished all the setups in OBN as well as EBS. With this in place, all the Outbound POs and Inbound Invoices for this Trading Partner will be exchanged via Oracle Business Network.

Read More

Oracle Business Network - A Primer

Are you still utilizing the traditional B2B cXML model to transmit POs from your EBS system to vendor systems? Are you looking for an end-to-end automated solution for inbound invoices?
Are you trapped in an endless cycle of transmission errors?

Oracle Business Network (OBN) is here to help you.

OBN (formerly known as Oracle Supplier Network a.k.a. OSN/OSuN) is a cloud-based supplier registration and messaging service provided to Oracle customers and their trading partners. It is free and works seamlessly with Oracle Fusion, E-Business Suite, and PeopleSoft applications. It lets customers exchange business documents with their trading partners.


Let's see what are the Traditional B2B approach and challenges:

• Configure each vendor for outbound transactions like PO transmission
  
  
• Import certificates for each vendor
  
  
• IP whitelisting may be needed
  
  
• Transmission/Handshake errors
  
  
• No monitoring tool except Workflow monitor in EBS
  
  
• No option of performing self tests
  
  
• No easy administration features
  
  
• High maintenance

Oracle Business Network Benefits over these challenges:

• One configuration for all vendors
  
  
• OBN certificates and OBN IP address only
  
  
• Transmission/handshake errors eliminated
  
  
• Excellent monitoring features for inbound as well as outbound transactions
  
  
• Option to perform self-tests for inbound as well as outbound transactions
  
  
• Easy administration
  
  
• Very low maintenance
  
  
• Free to use for all customers and trading partners
  
  
• Hosted by Oracle Outsourcing to provide a high availability connection for trading partner collaboration
  
  
• Simplifies the administrative burden of creating and managing a complex multi-point integration infrastructure

Oracle Business Network Structure / Process

• Oracle customers (EBS) communicate with OBN via OAG XML standard for inbound and outbound messages
  
  
• OAG XML = Oracle Applications Group XML standard
  
  
• This facilitates messaging without any customizations or custom maps
  
  
• Trading partners can choose from one of the common standards supported by OBN such as cXML
  
  
• Real time message transformer in OBN converts messages from OAG XML to destination XML standard
  
  
• This eliminates additional cost and effort of multiple standards and configurations on either sides

Pre-Transform Document (OAG XML)

When a document is sent from EBS to OBN, it appears under Pre-Transform Document section.
Below is a sample for the same:

Post-Transform Document (cXML)

OBN transform the Pre-document into Post-document and it appears under Post-Transform Document section.
Below is a sample for the same:

This way, we don't have to configure various cXML documents on EBS side in order to send them to various trading partners. Instead, we maintain a uniform configuration for all the vendors and send the documents in OAG XML format to OBN and OBN takes care of transforming them to cXML and send to the corresponding trading partners.

This uniform approach eliminates transmission/handshake errors and gives us more control over monitoring and resubmission of error transactions.

In Oracle EBS, the XML Gateway is used to integrate with OBN and exchange the messages/documents.

In Oracle Fusion Cloud, the Collaboration Messaging Framework (CMK) is used to integrate with OBN and exchange the messages/documents.

Read More

Extend EBS workflows using Oracle Business Event System

So, we all are aware of Workflows in EBS but do you know we can extend the workflow functionality using Business Events ? Let's see how.


Oracle Business Event System .. what's that ?

• Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events between systems
• Mainly consists of the event manager and process event activities
• Event Manager –
    - Contains a registry of business events, systems, communication agents within those systems, and subscriptions for a given event
    - Events can be raised/received from an external system or the local system through AQ. When an event occurs, the subscribing code is executed in the same transaction as the code that raised the     event, unless the subscriptions are deferred
• Each business event represents a ready to use integration or extension point
• Oracle E-Business Suite currently ships preconfigured with over 900 business events

What's Oracle Advanced Queuing ?

• It's a Message-oriented middleware (MOM) infrastructure that supports sending and receiving messages between distributed systems

• AQ uses database structures as a repository for asynchronous queuing which acts as the main element in various Oracle related as well as heterogeneous operations

• Oracle Advance Queuing does not support synchronous messaging

• Oracle AQ supports PL/SQL, Oracle Cloud Infrastructure, Java Message Service and SOAP APIs

Messaging using Oracle Advanced Queuing

Messaging is the ability to send a message containing data from one application/process to another application/process and is widely used in distributed systems, particularly high volume OLTP systems

Client server applications are typically synchronous whereas messaging is asynchronous

In an asynchronous model, the sender, usually referred to as the producer, is not blocked waiting for a reply from the recipient(s), referred to as consumer(s)

Messages are placed into queues by Producer systems 

– This is called enqueuing

Messages are read & removed from the queue by Consumer systems 

– This is called dequeuing

The data section of the message is referred to as the payload

Now, let's see what's the difference between Workflow Engine vs Business Event System

What are Business Events ?

• Business Event is an occurrence of a business activity which is significant to other objects or processes in a system or to external agents.
  
  
• For example, the activity of creating a Purchase Order is a business event, similarly approving PO, receiving goods against a PO or matching a PO with invoice is a Business Event.
  
  
• Business Event is a ready to use integration or extension point.
  
  
• Business Events are integrated to specific business flows for additional processing or validations.
  
  
• Examples of preconfigured Business Events –

oracle.apps.po.autocreate.pocreated

oracle.apps.po.autocreate.rfqcreated

oracle.apps.per.api.employee.create_employee

oracle.apps.wsh.delivery.gen.shipconfirmed

Navigation to access Business Events:

Uses of Business Events

System Integration Messaging hubs - 

Business Event System can serve as a messaging hub for complex system integration scenarios. The Event Manager can be used to "hard–wire" routing between systems based on event and originator.

Distributed Applications Messaging – 

Applications can supply Generate and Receive event message handlers for their business entities.

Message-based System Integration – 

You can set up subscriptions, which cause messages to be sent from one system to another when business events occur. In this way, you can use the Event Manager to implement point–to–point messaging integration.

Business event-based workflow processes – 

You can develop sophisticated workflow processes that include advanced routing or processing based on the content of Business Events.

Non-invasive customization of packaged applications - 

Create subscriptions to various Business Events to trigger custom code or workflow processes.

What are Event Subscriptions ?

• An activity to be performed on occurrence of a Business Event.

• For example, in order to send an email notification to users when a PO receipt is created, you can create a Subscription to PO Receipt related Business Event and trigger a workflow notification from the subscription to send email.

• Whenever an Event is raised locally or received from an external source, the Event Manager searches for and executes any active Subscriptions for that event.

• If multiple subscriptions are defined to the same Business Event, you can control the order in which the Event Manager executes those subscriptions by specifying a phase number for each subscription. Subscriptions are executed in ascending phase order.

• Subscriptions can be executed immediately or be deferred

• Immediate Subscriptions are Synchronous

• Deferred Subscriptions are Asynchronous

• The Event Manager determines the execution method based on Phase Number of a Subscription

• Immediate (Synchronous) Subscriptions have Phase <= 99

• Deferred (Asynchronous) Subscriptions have phase > 100

• Deferred subscription events are enqueued to WF_DEFERRED AQ and Workflow Agent Listener dequeues/executes them in the background

• All events with Synchronous subscriptions are executed in the same thread they are raised in and not enqueued to any AQs

Navigation to access Event Subscriptions:

Sample Subscription Definition:

Let's auto-create a PO for testing:

We'll be able to see below entries in WF_DEFERRED table for above PO:

One entry for Auto-create and one for Notification

And now, if we head back to Application, we'll be able see the custom notification 

Below are some Possible Use Cases using Business Event System:

Subscriptions can include the following types of processing –

• Executing custom code on the event information

• Sending event information to a workflow process

• Sending event information to other queues or systems

• Sending a notification based on the event information

• Sending or receiving an Oracle XML Gateway message

• Invoking a business process execution language (BPEL) process or other Web services

This topic was presented in one of my OATUG webinars. Please find the details below for full presentation and demo:

Webinar

Presentation and Demo

Read More