Tuesday Nov 27, 2012

Customisation / overriding of the Envelop ecs files

There are few usecases where the requirement is to customise the envelop information (Interchange/Group ecs file).
Such scenarios might be required to be used for only few of the customers.
Hence, in addition to the default seeded envelop definitions, it also required to upload the customised definitions.

Here is the steps for achieving the same.
1. Create only the Interchange ecs and save
2. Create only the group ecs and save
3. Use the same in B2B

1. Create only the Interchange ecs and save :
      Open the document editor and select the required version and doctype. During creating new ecs, ensure to select the checkbox for insert envelop.
      Once created, delete the group and transactionset nodes and retain only the Interchange ecs nodes, including both header and trailer. Save this file.

2. Create only the group ecs and save
      After creating the ecs file as mentioned in steps of Interchange creation, delete the Interchange and transactionset nodes and retain only the group ecs nodes, including both header and trailer. Save this file.


3. Use the same in B2B
      These newly created ecs can be used in B2B by 2 ways.
             a. By overriding at the trading partner Level:
             This will be very useful when the configuration is complete and then need to incorporate the customisation. In this case, just select the Trading partner -> document -> select the document which need to be customised.
             Upload the newly created Interchange and group ECS files under the Interchange and group tabs respectively and re-deply the associated agreement.
             The advantage of this approach is
             - Flexibility to add customised envelop definitions to the partners
             - Save the re-work of design time effort.

             b. By adding another document definition in Administration -> document screen:
             This scenario can be used if there is no configuration done at the trading partner level. Create the required document revision and overtide the Interchange and group ECS files under the Interchange and group tabs respectively. Add the document in Trading partner -> document. Create and deploy the agreements

Tuesday Oct 02, 2012

Come visit us at OOW 2012 B2B Demo Booth!

You’re invited to visit us at the Oracle B2B Demo POD at Oracle OpenWorld and JavaOne 2012. Please stop by at our booth to see cool demos on EDI X12, EDIFACT and SBRES (used in Airlines industry). We will also be showing integration with OSB, SOA Suite and BAM. Use this opportunity to see the product in action, learn, and get answers to your questions. We will be happy to meet you and hear about your B2B integration usecases and discuss our roadmap. The demo pod will be available at the Fusion Middleware Demo POD area on Monday, October 1 through Wednesday, October 3, 2012. Look forward to seeing you there! Happy OOW 2012!
Ref: https://blogs.oracle.com/SOA/entry/come_visit_us_at_oow
About

To Discover and discuss the capability of B2B in the world of Trading Partner Integration. This blog is primarily intended to share thoughts on Oracle B2B Product and to share best practices in performance, scalability and various topologies.

Search

Archives
« September 2015
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today