Home

Oracle B2B EDI Cookbook

image

Contents

1. EE Data Editor s Data Dictionary Editor i Data Dictionary Generator ar Standards Reference Sie z Additional Offerings Click New document to create the new ecs file Select guideline as EDI X12 Documents Page 21 of 53 E New Document Wizard B New document creation Please select a guideline g SIMPL EDI Fa E TRADACOMS Fla UCS Fl VICS EDI EQ WINS Hg 12 X12F H a X12N Health EQ X12N Life amp Annuity Gy X12N Property amp Casualty F 2 Documents Back gt Cancel Help 2 Click on to select the desired Document Protocol Version V4010 New Document Wizard Hew document creation Please select a guideline PS 4030 By V4022 fy 4021 FE 4020 Fy V4012 ES 14011 ETE Bes 001 Control Segments m 100 Insurance Plan Description m 101 Mame and Address Lists Lo ir Shinment Infarmatinn Back gt Cancel Help 2 Select the Document Type 850 Purchase Order Page 22 of 53 New Wizard New document creation Please select a quideline Specifications T echnical Inform Nonconformance Report md Delimited Flat File ZEE Response to Request for Quotat e EDI Pod Product Transfer Account Adjus POR Price Authorization amp cknowledgr m HL POR Inventory Inquiry Advice ru i i Mat
2. 47 Reverse engineering specifications using existing data 48 PV DICGUISDE ELIOT S ECT 49 See 50 Reference 52 Page 2 of 53 Introduction EDI Electronic Data Interchange is a structured Document standard and is one of the most widely used standard in Business to Business communication The various modes of exchanging an EDI data are using the well known exchange protocols such as AS1 AS2 and VAN Purpose The main purpose of this book is to get basic understanding of the EDI standards learn Oracle Fusion Middleware B2B EDI support User experience while configuring EDI protocol using Oracle B2B Various Error Exception scenario and also to model the various EDI messages using Oracle B2B Document Editor After reading this book users should be able to independently model Various EDI use cases such as batching debatching and end to end scenario using various EDI message types and revisions Audience EDI Cookbook is intended for B2B users who want to exchange EDI messages such as EDIFACT X12 using Oracle B2B as an Integration Gateway product and would like to understand various use cases and implementation Prerequisite Basic Knowledge of EDI Standard i e both X12 or EDIFACT is a must Assumptions This document is based on Oracle Fusion Middleware B2B 11g H1 Page 3 of 53 What is EDI Electronic Data Interchange is a Structured Busin
3. InterchangeSenderID Interchange Sen lt Lookup gt Date Time References Lookup Name InterchangeSenderQual gt 01 lt Lookup gt Lead Time Lookup Name InterchangeUsageIndicator I Lookup Item Identification c Lookup Name Standard gt X12 lt Lookup gt Service Characteristic Ident Property Name ElementDelimiter gt 0x7e lt Property gt Product Item Description Property Name InterchangeAckRequested gt 0 lt Property gt Measurements Property Name InterchangeAuthorizationInfo Authorizat lt Property gt Paperwork Property Name InterchangeAuthorizationInfoQual gt 00 lt Property gt Marking Packaging Loadir Property Name InterchangeChildCount 1 lt Property gt Carrier Details Quantity anc Property Name InterchangeComponentElementSep gt 0x5c lt Property gt Carrier Details Routing Seq Property Name InterchangeControlNumber 000000001 Property Carrier Details E quipment Property Spec Name InterchangeControlStandard RepeatingSeparator U lt Property gt al Property Name InterchangeControlVersion gt 00401 lt Property gt n nanana SES A Properties User Notes Children Analyzer Data Pricing Information CreatedBy XEngine 2045 GUID F13BB277 5528 4331 BAE7 6922DBA5D127 gt EE E E EE EE E E ff 22227 91 9 2A AE E R8 it 9 1 EmorlD EmorMessage _ Error Data
4. Page 15 of 53 Control Numbers Control Numbers are included in all header and trailer segments as an additional means of tracking and confirming EDI transmissions Control numbers issued in the header segments must match control numbers assigned in the trailer segments An ISA control number must match the IEA control number the GS control number must match the GE control number and the ST control number must match the SE control number in each EDI transmission or there could possibly be errors Control numbers can be assigned in the following two ways Control Number along with the sender ID provides a unique identifier to identify incoming EDI data from a sender Following are various control numbers e Interchange Control Number Originated by the sender and is typically a sequence number This together with the sender ID uniquely identifies the Interchange e Functional Group Control Number This Uniquely identifies Group e Transaction Set Control Number This Unigely Identifies Transaction Set Control Numbers are used for correlation at various stages it may be correlation in the Back End application or correlation in the B2B application between the business document such as 850 and Functional Acknowledgement 997 Control Number Generated by Back end Application This is the most likely case as back end application uses the Interchange Group and Transaction Set Control Number for correlation at various levels and also for correla
5. based on criteria that you specify The following example shows how to batch the document type 850 revision 4010 to the trading partner named GlobalChips The examples follow the scenario described in the EDI X12 tutorial gt Go to Administration gt Select Schedule Batch Document gt Deploy Manage Deployments Types Import Export Manage Batch Callout Purge Listening Channel Configuration Schedule Batch Create Batch Batching is often used to group messages by document type Use Oracle B2B to batch schedule and send outbound EDI X12 and EDI EDIFACT messages For example you may want to send out a batch of purchase orders or a batch of invoices Batch Name Selected Range Initiate event at February 20 2009 6 30 AM Launch Scheduler ElSearch Advanced Saved Search Default Match Any Responding Partner Contains v Document Protocol Version Equals v Agreement Contains v Document Type Equals v Document Protocol Name Equals Document Definition Equals Search Reset Save Initiating Partner Responding Partner Agreement Document Protocol Document version _ Document Type Document Definition gt Provide the batch name L h Schedul gt Click on Launch Scheduler button to schedule the batch time Page 17 of 53 Scheduler Selected Range Initiate event at February 20 2009 6 30 AM OK Cancel gt Provide the time ra
6. by Back end Application eene eene nenne 16 Control Number Generated by B2B cies eee ene en eese enn nh ese rn ness enne nnne 16 EDI Bathin uc D T TTE 17 B tehins FIDE Transaction SCs ooo tectis nre cn aera ando tots boe tuition 17 De baichine EDL Transachon onore Eo ene alesis eee eee 18 Additional features Tips and Tricks cccscssssssssssssssssssssssssscsssscssssccssscessssssees 19 Custom Code Dist BDDE E UE our ERE re dE De BUE RU 19 Handlias Posr onal Flat Pile tese iuda 19 P rtormiatnce Best 20 Larse Payload Con Me Gao conned bebe re tout Eo De ccs iene 20 Oracle B2B Document Editor dete bia 21 CREATION of ECS files USING SPEC BUILDER 6 6 1 21 CREATION of XML Schema Definition xsd for the ECS file eee 24 DATA GENERATION USING ECS 2 9232922329 na hu E E EEn 29 ANALYSE THE DATA VALIDATE THE GUIDE LINE 37 Print and Publish Specifications Wane 43 Write and Test Business Rules Using Java 45 Compare customized specification to the standard specification
7. document protocol parameter Is it possible to identify the incoming document only based on ecs file Yes it is possible to disable the validation of incoming document against Document protocol parameters by setting the value for Ignore Validation on Envelop elements E Miscellaneous Default Trading Log Payload 9 Partner Ignore Validation on Reconnect on Error Envelope HTTP Header elements Delimiter Ignore Treat Reply To Correlation Message as Additional Request MIME Types Is it mandatory to have Functional Acknowledgement in EDI No it is optional Page 50 of 53 10 What happens when the Document related parameter are modified in the admin page when it is already being used in the trading partner level Can the updated information propagate to all the trading partners NO Page 51 of 53 Reference Information Links Oracle B2B http www oracle com technology products integration b2b index html Oracle B2B Forum Forum http forums oracle com forums forum jspa forumID 242 Fusion Middleware http www oracle com technology products middleware index html Service Oriented Architecture http www oracle com technologies soa index html Page 52 of 53 This cookbook has been assembled using excerpts from e Oracle B2B User Manual e Oracle B2B Partner Training Curriculum e Oracle B2B Technical Notes e Oracle B2B Tutorials Chief Editor Ramesh Anantharamaiah Contributors Jeffrey Hutchi
8. for inbound messages Oracle B2B validates the document and then translates it into xml depending on the settings The below mentioned parameters are validated against the configured parameters to make sure that the data is from the right partner Document Protocol Parameters Header e Interchange Receiver ID Interchange Receiver ID Qualifier Interchange Sender ID Interchange Sender ID Qualifier Page 13 of 53 e Application Receiver s Code e Application Sender s Code e Interchange Control Version Number Functional Acknowledgement Support in Oracle B2B Functional Acknowledgment is a confirmation sent by the recipient Application about e Receipt of the message e Status of Validation of the message against the configured ecs file Functional Acknowledgement can be configured to be sent by either B2B or by the Back end application e Functional acknowledgement required Functional Ack required or not This option is available while creating the agreement as shown below Agreement 428 Acme_GlobalChips_X12_4010_850_File Save Validate Deploy Export Acme 850def GlobalChips Details Agreement Id Acme GlobalChips X12 4010 850 Start Date Name Acme GlobalChips X12 4010 850 End Date Description Callout Callout Details Agreement Parameters Validate Translate e Functional Ack handled by B2B Generates FA in B2B or by the Back end Application To enable this gt Goto Administration gt Click Configu
9. the database y A 00502 with optional segments i i _ 850 Purchase Order 00501 5 Interchange Control Header 00406 00406 with optional segments with optional segments with optional segments 00402 with optional segments AU 4 1 with antinnal seaments IN I PE SUED MINES LC DCN NEA DE CEA EE Page 31 of 53 8 Data Generator Wizard Envelope Segments Please specify how to use the selected Envelope segments Data Generator options Please select data generation options gt Click Next Page 32 of 53 Data Generator Wizard Element Size Please select Data Generator Element Size option gt Click Next Ry Index Reset Please set Data Generator Index Reset option gt Click Next Page 33 of 53 Data Generator Wizard Repeat Count Please set Data Generator Repeat Count option gt Click Next Data Wizard v Data Dictionaries Please select Data Dictionaries to use by Data Generator I Selected Dictionaries n ji R gt Click Next Page 34 of 53 gt Provide the desired delimiters or select the segment separator as shown below Delimiters Please set delimiters to use by Data Generator when generating data file Edit delimiters gt Click next gt Select the output data file name Data Generator Wizard Test Case Save Please save the Test Case v Dutput Data file nam
10. the desired Document Protocol Version V4010 Select the Document Type 850 Purchase Order Envelope Segments Select default Click Finish 1 Write rule that accumulates the line item quantities If the total quantity does not match the count in the control segment then report an error 2 Create and initialize quantity accumulate variable e Select the root Transaction node in the guideline tree Click on the Rules tab on the detail pane Click on the icon to add a new Rule Select User Global Declaration Script Add java script variable declaration abc totQuantity 0 Guideline T XPE x12 Guideline User Global Declaration ag V4O10 850 Purchase 01 E User Global Declaration Script User global declaration area is uw Ej 3 isa Intercha f 1 To reference JavaScript functi m 3 Gs Functior 2 To declare variables which wil m 3 ST Transa 3 To declare common user functio Beginnir Currenc abc totQuantity 0 Referen Administ Tax Ref F 0 B F Pricing Period Sales Ai w ie _ 4 x 99 E Guideline 9 Dictionary 4 4 P PLIN Properties Rules A ChidView Analyzer Data E E Oum m C rm zt FOB CTP 8 Fe 1 b Ln amp Col 11 3 Write code to accumulate quantity for each line item loop In the guideline tree Expand Loop Baseline Item Data Select segment PO1 Baseline Item Data Select element PO102 Quantity Orders Cli
11. will be created for BT Oracle B2B Document Editor Oracle B2B Document Editor Powered by Edifecs is an integrated guideline creation and implementation application for business to business B2B electronic commerce e commerce Use the Document Editor to simplify developing migrating testing distributing and printing your electronic business e business guideline documents You can create new guideline documents or use the Document Editor s comprehensive library of Standards as templates Using an existing standard as a template you can create new transaction sets by changing the attributes of underlying segments elements and codes as well as create implementation guidelines from data files Oracle B2B Document Editor is also integrated with Edifecs CommerceDesk the most complete solution available for data generation and guideline compliance testing In order to use the EDIFACT X 2 and HL7 protocol in ORACLE integration B2B it is mandatory to know below mentioned basic steps Creation of ECS files using SPEC BUILDER 6 6 1 xsd generation using ecs file Data generation using ecs file Analyse the data CREATION of ECS files USING SPEC BUILDER 6 6 1 Prerequisite Install the spec builder 6 6 1 gt Open the spec Builder 6 6 1 Oracle B2B ORACLE B2B Document Editor Poser tl EDIFECS New Document SpecBuilder aZ r2 M 7 Dpen Document a EX Analyzer A Migtator Data Generator
12. 072771941 700172007C H REF 01 Reference Identification Description 01 Reference Identification O1 Reference Identification 01 Reference Identific E PER 14A Name AA Communication Number amp A Communication Number Communication Number Contact Inquiry Refe TAX Tax Identification N A Location Identifier amp Location Identifier A Location Identifier A Location Identifier Location I FOB 11 A Description 01 CAF A Description BY Description amp amp 15054794109701 15272875232431 198 01 2545589771 213982 01 505115 5 23881515 01 15987 1 01 H amp PAM 01 2 014145528401 41 195064934905431 87401 3 309 01 39731 6402634341 431 6401 M111 76280854307341699 1 17E H CSH B 17149 Account Number 20070727 10 AC A 1 921729571 amp TC2 2 Commodity Code Loop SAC HH SAC A AN10 10 Agency Ser7259052064717264831787017497201182185925424701 Reference Identification Option CUR O1 CUR 43899 01 CUR IMF O01 20070727 1 941 3700 001 20070727 1 941 001 20070727 1941 001 200 gl amp TD0 0171 2935 20070727 119 20070727 1 3770101 20070727 297159 Description 1971 1687130136 H DIS AMT CA 80667DAT 1572027129 FE 01701 45172 13 1 37 1 01 2934 17132 57 01 311527 234 01 141951585 4474172891371944414721837265 amp DTM 0017200707277194137701 7CC Date Time Period E LDT7AA7210243106652467AA 20070727 iz LIN Assigned IdentificatA1 Product S
13. B2B runtime software 2 0 5 TH P A Properties User Notes A Rules A Children A Analyzer Data a gt Click Next gt Select the option of saving the guideline before exporting gt Select the location for saving the exported file Page 24 of 53 Le 850 ecs Oracle B2B X12 V4010 Bie Edit Tools Window Help amp amp emos Transaction Properties Category Reset Changes Apply Guideline Transaction Set Header Beginning Segment for Purc Ei General ae ID so Reference Identification Administrative Communicati Name Purchase Order Tax Reference Export Wizard F 0 B Related Instructioi Pricing Information Export Period amp mount Export destination Sales Requirements Commodity Service Promotion Allo Tems of Sale D efered Gave exported Fle as Discount Detail Installment Information CA850 xsd Date Time Reference Lead Time Item Identification Service Characteristic Ide Product Item Descriptio Measurements Paperwork Marking Packaging Loa Carrier Details Quantity Carrier Details Routing S Carrier Details Equipme Carrier Details Special Es 99 Dict i Guideline 14 4 gt P Properties A User Notes A Rules Children Analyzer Data E IV Save guideline before exporting EB E E EE EE EH A EE
14. Ee gt Select the option for namespace generation as Custom namespace gt Provide the custom namespace as urn oracle integration b2b X12 4010 850 50 ecs Oracle B28 X12 4010 Edt yew Tools Window lt Rese Transaction Set Header A RBESESEES umcoracke integration 2631 2 4010 850 Add unique sutiy Namespace previews oes DR cmn om 141 4 gt Properties A User Notes A Rides Chisren Amlyzer Camer Detais Routing S Detads E quip Carmer Details Special H gt Click Next Page 25 of 53 r Options Export Select name templates configuration Templates Node Transaction Loop lt Node ID Segment Made ID Composite Mode ID Element Mode ID Abbreviated element name prefix Preview element name Transaction lt Node ID type Transaction lt Node ID 3 Templates are loaded from the registry Back Cancel Hep gt Click Next Export Please select common conversion options Please select common convesion options Replacement character Underscore _ Internal node name separator Dash ut Suppress Enumeration in X5D Add offset and size to leaf XML elements Suppress use of optional attributes in XSD Use this export module instead of default during XD ata generation Templ
15. Header with optional segments gg GE Functional Group Trailer gg IEA Interchange Control Trailer with optional segments with optional segments with optional segments with optional segments ANANI with nntinnal senments VIGO ESL US Let ee 5 t H ITE CMA see Envelope Segments E rer er rr a Please specify how to use the selected Envelope segments Click Next Page 40 of 53 Analyzer Mode and Outputs Please select analyzer modes and outputs to generate Generate short report gt Select the option to generate Xdata as Always or No Errors in order to generate XML Data gt Click Next Oracle 878 RE EET EN Data 1850 dal Transaction Set Header Interchange Beginning Segment tor Pure 5 i ISA 00Aushorizat00 Securty 1 01 interchange Sen 701 laterchange Rec 07072771 507 U 00401 000000001 70717 Group H GS PO Applicalion Sen Appleation Riec 20070727 1350090 1 71 004010 Transaction Gy ST 85070001 BEG 0074B Purchase Order Number Release Number 20070727 Contract Number AC IBM 01 7AE 700701 8 SI CUR 017CUR 71329331701 CUR IMF 00120070727 19500970017 20070727 1350030 001720070727 19507 001 20 S REF O17Relerence Identification Description 01 Reference Identification 01 Reterence Idertification 01 Relerence Iderlific 8 PER 1A Name AA Communication Number AA Communication Number AA Communication Number Contact Inqu
16. ORACLE An EDI Cookbook for Oracle B2B Page 1 of 53 Contents FHIFOUHUION dna divo dace o aeo n a Riot 3 What 1S EDEs i ov un Tuna eds 4 EDI Document SU UFUCUIER eei ee snot ee nakana a eeina andana anie aaaea oa aa aa ataia 4 EDI Support in Oracle BIB 5 User Experience while configuring EDI protocol in Oracle B2B 5 Create a Document Protocol VerstOB iiec orte os Du ede eu pao eem a nop re x pb vaL e ETE e Pere a Sara rae Rer ra ER 6 Greate a DOCUIBEDUT VIE odit ou radio aso diti bod us iade 6 Create a Document Ct Co E HOLD ENSE CAU VOLO PISIS UN 7 Add Documents definitions for responder 9 Outbound EDIL Processie 11 Thbound EDT Process eoo pct pea ert Fe mad 12 ASreement TCSII 12 Partner Td ntibloatiofi susce orato eoo ub tes ere ane 12 Functional Acknowledgement Support in Oracle B2B esses 14 Overriding the Document Protocol Parameter for FA sene 15 SUPO easa epe fiat toe en b bellua dunno al ni Dac ee 15 Control NUDIDGES 5o tisse eo ise qelu pis nie Aeon een eeu e esa eae Rue Ix LOE exa v aeq RES enda GO 16 Control Number Generated
17. Protocol Parameters mapped to Internal Properties Agreement Identification B2B uses 4 parameters for identifying the agreement From Party To Party document type and document protocol version Trading Partner Identification Trading partner Identification can be done in three different ways and order of identification Exchange this is the default way of identifying the trading partner by using the Exchange headers E g In AS2 protocol it is by using AS2 From and AS2 To headers and comparing with the AS2 identifiers of the Trading Partners Interchange EDI has unique values in the interchange headers that can be used to identify the Trading Partner Optional Group EDI has unique values in the group headers that can be used to identify the Trading Partner Optional in EDIFACT Interchange Sender ID Applcation s Sender Code Exchange identifier M Note In order to identify the trading partner based on the Interchange it is important to forcefully fail the exchange identification Similarly In order to identify the trading partner based on the group it is important to forcefully fail the exchange and interchange identification This can be achieved by adding Page 12 of 53 Identity From Identification Criterion Interchange Sender ID X12 SHZISRTEDIFAGTUNE SUE EDIFACT UNB S002 Application s Sender Code X12 GS 02 EDIFACT UNG Protocol Identification from default party s exchange id
18. RACLE B2B Administration Partners Reports Metrics Help Logout 9 Logged as weblogic Deploy Manage Deployments Types Import Export Schedule Batch Manage Batch Callout Purge Listening Channel Configuration Documents 1 Egi Document Definition Document Protocols ES Custom sd EDI_EDIFACT 8j EDI x12 EDI X12 4010 850 NewDefinition gd 4010 Enter the document definition name and and select the required definition File amp sso TR m NewDefinition Document Definition Name 8504 85 997 Description sd HL7 s CAG 83 PositionalFlatFile Definition 850 xsd Update RosettaNet Root 50 Name sd UCCNet Reset Parameter N Routing XPath Correlation Transaction Set ecs File CAB2B materials VT 1g R1 Samples You have the option of providing an xsd corresponding to the transaction set ecs which can be used in the back end application such as BPEL for required transformation to edifecs xml gt Provide the Transaction set ecs file under Transaction tab This is mandatory It is best practice to create the ecs file using the document editor 6 6 1 However both B2B and document is backward compatible Refer to the section Document Editor Enter the following information Field Value Document Definition Name 850def a name os user choice Definition 850 xsd The xsd file ca
19. S Ee e X Properties A User Notes A Rides A Chien j eri Dot gt Analyser will provide the analysis results with error messages if any the bottom pane of the above screen In case of error edit the data save and execute analyzer gt Click on the button in the top right corner to view the XML Format of the data Page 41 of 53 Guideline c em ms Transaction Set Header ViewasXML C View as HTML Data node Interchange Report Template XSLT 412 Data Beginning Segment for Currency j lt xml version 1 0 encoding UTF 16 Reference Identification _ lt Transaction 850 xmins urn oracle integration b2b X12 4010 850 Administrative Communicati xmins xsi http www w3 org 2001 XMLSchema instance Tax Reference xsi schemaLocation urn oracle integration b2b X12 4010 850 guideline xsd F D B Related Instructions XDataVersion 2 0 Standard X12 Version V4010 CreatedDate 2007 07 27T19 55 20 22000 0220 SRIAS L Period Amount Sales Requirements Commodity Service Promotion Allowar Terms of Sale Deferred Ter Discount Detail c0 w e lt Internal Properties gt Data Structure Name Interchange gt Lookup Name InterchangeControlVersion 200401 lt Lookup gt Lookup Name InterchangeReceiverID Interchange Rec lt Lookup gt Lookup Name InterchangeReceiverQual gt 01 Lookup V sstaliment Information Lookup Name
20. _SNIP Type Severity Analyzer with the Run Linker and Validator option finished successful 14 4 gt Toy Find amp Replace A Cross References Data Errors A Data Dictionaries Data Generator Log Page 42 of 53 Print and Publish Specifications The objective of this section is to create customize and publish an implementation companion guideline Click New document to create the new ecs file Select guideline as EDI X12 Documents gt Click on to select the desired Document Protocol Version V4010 gt Select the Document Type 850 Purchase Order Envelope Segments Select default Click Finish Note either you can create a new guide line or use the existing one 1 Include Exclude Node In the Guideline tree e Expand segment BEG Beginning segment fro Purchase Order e Exclude element BEGO6 Contact Number 2 Adding user note for ISA segment ISA08 element e Expand Segment ISA Interchange Control Header e Select element ISA08 e Select User Notes tab and then o User Note 1 Add Note Value in this element must equal RealProcess for real time purchase orders BatchProcess for batch purchase orders o User Note 2 Add Note Ensure that values match either REALProcess When value is RealProcess only 1 purchase order is in the data file 3 Modify User Note Labels e Select File gt Document Options Select Notes Tab Scroll down on th
21. aScript code in this section is executed Baseline Transac if abc totQuantity ec DataLink m sData 010 var ErrMsg Calculated total quantity totQuantity does not match the reported quanity ec DataLink m sData ec ErrorContainer ddErrorz ec CaseID 9999 ec DescriptionTemplate ErrMsg b Ln10 Col 11 4 99 TG Guideline id STE TE Properties A Rules A Chidview J Analyzer Data Compare customized specification to the standard specification The objective of this section is to compare and migrate customized specification to a newer version of the transaction 1 Launch Migrator e Launch B2B Document Editor e Open the main toolbar to the left and click on the icon for Migrator 2 Executing the comparison and migration wizard e Migrator wizard is started e Source guideline from the database or standard o Select Standard EDI X12 Version 4010 850 Purchase Order a Click Next e Select Destination Guideline or Standard File Les7 Migrate X12 401 850 ecs Click Next e Comparison options o Allow customization of which guideline attributes should be compared and which should be skipped By default user notes are skipped since they will most likely always be different Use the default settings and click Next e Migration options o Allow customization of which guideline attributes should be migrated from source to target Use the default settings and
22. aso 850def 8 997 Description g 997def 53 HL7 OAG Definition 997 xsd Update PositionalFlatFile Root XSD Name RosettaNet UCCNet Document Definition Name 997def Reset Parameter Routing XPath Correlation Transaction Set ecs File 997 ecs Update e As part of document definition use ecs file and xsd files obtained from previous step B2B uses only the ecs file for validation and translation xsd can be used by BPEL process for payload validation and can be accessed by composite while configuring the communication between BPEL and B2B Please refer to the EDI Tutorial for the detailed steps e Define Document Protocol Parameters Document Protocol Parameters are defined while creating the document protocol version however it is possible to override it for a specific Trading partner For e g the list of delimiters option to create the UNA segment etc while defining the Document Protocol Revision Page 8 of 53 Group Delimiters Create UNA always v Interchange Time x SystemTime HHMM s Interchange Agreement Syntax Identifier UNOB Recipient s Reference Password Test Syntax Version Number 1 Recipient s Reference Password Qualifier Interchanc Service Code List Directory Yersion Number Application Reference Character Encoding Processing Priority Code Interchange Date stSystemDate YYMMDD amp e Docu
23. ates will be saved to the guideline file and will be re used next time lt Back Cancel Help gt Click Next Page 26 of 53 Export SpecBuilder ECS Document to XML Schema Options Select proper options Please select EDI specific convesion options JE Don t use xsd choice for keyed segments loops gt Click Next Export Please select server lt Back Cancel Help gt Click Next Page 27 of 53 Options Export Please specify macto nodes Name UPath lt Back Cancel Help Click Next p Export Wizard Export Exporting the document Converting to Oracle B2B 2 0 Finished M Page 28 of 53 DATA GENERATION USING ECS FILE This step is used to create the test data Click on Data generator in the left pane of the below screen MA vA Oracle B2B File Tools Window Help Oracle B2B ORACLE B2B Document Editor Powered by 5 EDIFECS SpecBuilder New Document U Dpen Document D A Analyzer Migrator Data Generalor Data E ditor m Data Dictionary Editor i Data Dictionary Generator rar fd 5 Standards Reference z Additional Offerings Help Data Generator Wizard Welcome to the Data Generator Wizard Test Case is a collection of settings used to generate test data based on a guideline A saved Test Case can be reused later to generate additional t
24. ck on the Rules tab on the detail pane Click on the icon to add new script Page 45 of 53 e Select OnUserNode Script e Add code abc totQuantity abc totQuantity parseFloat ec DataLink m sData Guideline cy Rules 010 Basal Pe HiUser Global Declaration 01 2 OnUserNode Script OnUsexrNode 03 User JavaScript code in this secti 04 05 totQuantity abc totQuantity 06 parseFloat ec DataLink m sData 07 08 234 039 235 10 234 11 235 12 234 13 X 4 4 b 4 in4Ca 99 dic Mi Guideline 20 Dictionary 14 TP TRIN Properies Rules A ChildView Analyzer Data n3 639 CO ro d m E ro al e n3 to a iti 4 Write code to report error Total quantity lt gt total quantity calculated In the guideline tree e Select segment CTT Transaction Total Select element CTTO2 Hash Total Click on the Rules tab on the detail pane Click on the icon to add new script Select OnUserNode Script Add following code and save the ecs file if btotQuantity Je e0 sData var ErrMsg Calculated total Oty 4 abc totQuantity does not matoh the reported Qty Datablink m SData ec ErrorconteiHer AddEFTPOr 2 e0 OaselD 8909 ec DescripLionTemplate ErrMsSg Page 46 of 53 Guideline Rule User Global Declaration Code Sc Z nUserNode Script Specific Ontlse rNode Advertis User Jav
25. click Next e Match options o Allow customization of how the two guidelines should be linked to each other By default node ID is used for linking but additional attributes such as Name and Position can also be used for linking Use the default settings and click Next Click Finish to start the wizard 3 Viewing and navigating differences e Use the scrollbars and the toolbar icons to navigate to next previous differences Tt Page 47 of 53 4 Printing comparison reports Using File gt Print Preview view the o Change summary report o Companion reports Reverse engineering specifications using existing data files The objective of this section is to demonstrate how to create specifications from existing data files 5 Launch SpecGenerator Launch B2B Document Editor Open the main toolbar to the left and click on the icon for SpecGenerator 6 Executing the SpecGenerator wizard SpecGenerator wizard is started Select the data file o File Les7 850 2 dat o Click Next Clean up data flies Click next Data Structure Click next Guideline Selection Verify that the proper guideline from the database is automatically selected and click Next Envelope Segment o gt Please select Envelop Segments Click next o gt Please select Envelop Segments from database Click next o Please select how to use the selected Envelop Segments SpecGenerator Mode Click next Order specification based on the content Toggle the view to onl
26. e e850 dat 3 Page 35 of 53 gt The data gets generated BR B50 ecs Oracle B2B X12 V4010 Ele Tools Window keen Rannan Data c 850 dat Ra E Transaction Set Header A Beginning Segment for Pure Currency Reference Identification Administrative Communicati Tax Reference F 0 B Related Instructions Pricing Information Period Amount Sales Requirements Commodity Service Promotion Allowar Terms of Sale Deferred Ter Discount Detail Installment Information Date Time Reference Lead Time Item Identification Service Characteristic Ident Product ltem Description Measurements Paperwork Marking Packaging Loadir Carrier Details Quantity anc Carrier Details Routing Seq Carrier Details Equipment Carrier Details Special Han 1 Guideline fel Eel EH EH 0000000000000002000000000060 2 e pel pel or mx zl E vaD 2 NIZ gt e 8 z6 E e EH FH o Sa EE CS Ee Fe Fe RR E 2 x uet m RE EH ed OOOOZA Save the data file E Group 1 i 81 GS PO Application Sen Application Rec720070727719413671 T 004010 i ag Transaction 1 ESQ ST 850 0001 amp BEG 00 AB Purchase Order Number Release Number 20070727 Contract Number AC IBM 01 AE 00 01 amp CUR 017CUR 223481701 CUR IMF 001720070727719417001720070727719413500700172007
27. e Edit View Tools Window Help EIE amp megBansemug Transaction Properties Guideline 010 020 040 050 060 070 080 090 095 110 115 120 130 140 145 150 160 180 185 190 200 210 220 230 240 250 260 2 OOOOZ Baath Transaction Set Header Beginning Segment for Currency Reference Identification Administrative Communica Tax Reference F 0 B Related Instructio Pricing Information Period Amount Sales Requirements Commodity Service Promotion Allo Terms of Sale Deferred Discount Detail Installment Information Date Time Reference Lead Time Item Identification Service Characteristic Ide Product Item Descriptio Measurements Paperwork Marking Packaging Loa Carrier Details Quantity 4 Carrier Details Routing S Carrier Details Equipme Carrier Details Special H General ID Name Export Wizard Category ResetChanges Apply Purchase Order Welcome to Export Wizard This wizard helps you convert a SpecBuilder guideline into external formats for use with other applications Choose an export to perform HTML with Branching Diagram Mendelson Transformation Engine Format Oracle B2B Pervasive XML Standard Exchange Format SEF TIE Mapping Manager Format EMM Description This export routine will convert the guideline from the internal format to one that can be used with the Oracle
28. e tree to find the entry for Element Notes Change label for User Note 1 TP Note Change label for User Note2 to Dev Note Click Apply Select Composite Element Tab Scroll down to section Print composite element user notes Enable printing of TP Note and Dev Note Click Ok A Note Label on the screen has also changed to TP Note and Dev Note 4 Modify Cover Page e Select File Properties Change Title to ABC 850 Purchase Order Change Author to ABC Click OK Select File Document Options Select check box to Print Cover Page Click OK Page 43 of 53 5 Save Guideline e File Save e File Les7 X12 4010 850 Notes ecs 6 Print Preview e Select File Properties Verify Cover Page Exclusion of BEGO6 ISA08 notes 7 Publish to HTML PDF RTF Word XML Excel XML optional e Select File Publish To e Select HTML o File Les7 X12 4010 850 Notes e Using Windows Explorer navigate to the location provided for the HTML page Double click to open the HTML page And verify edits e Exit Specification Page 44 of 53 Write and Test Business Rules Using Java Script The objective of this section is to write rule using java script for additional business rule validation Note JAVA Code is available in the attached sample zip file under 2 Class Document Editor java code txt gt Click New document to create the new ecs file gt Select guideline as EDI X12 Documents gt Click on to select
29. entifier To support this configuration e Create a Trading Identification Type EDI Interchange ID EDI Group ID Profile amp GlobalChips The trading partner profile uniquely identifies each partner Set up identifers contact information and customized parameters For each partner E Confirmation GlobalChips has been saved Identifiers Identifier types uniquely identify a trading partner and define how to exchange documents Type Mame GlobalChips EDI Interchange ID GlobalChips EDI Interchange ID Qualifier 22 EDI Group ID GlobalChips Contact Information Important contact information For each trading partner should be entered e Create a new Trading Identification for the target trading partner with the corresponding EDI sender value for Interchange or Group envelope Document Identification Oracle B2B extracts the Document Type and revision from the transaction Set of the incoming EDI Document i e from UNH Segment It is required that the document to be well formed for the successful extraction of Document Type and Revision X12 identification based on Group and Transaction set o EDIFACT identification based on Transaction set Validation and Translation It is required to get the necessary ecs for translation and validation Document protocol parameters of the Document is compared against the one defined during Document definition to extract the ecs file Typically
30. erial Claim Material Safety Data Sheet e NCPDP Response to Product Transfer LN 950 Purchase Order und ParserSchema fi Assat a Purchase Order Cancel e DTD Z gt Unselect the Envelop Oracle integration B2B is pre seeded with all versions of the envelope and group ecs files Hence no need to generate the envelope and group ecs files Unless there is a deviation from the standard New Document Wizard New document creation Please select Envelope Segments Nesi Envelope Segments From Envelope Database C From Guideline x12 V4010 850 Purchase Order Envelopes Preview 950 Purchase Order with optional seg nnl ISA Interchange Control Header Ui GS Functional Group Header with optional seg Jui Objects f GE Functional Group Trailer d IEA Interchange Control Trailer Back Cancel Hep gt Click finish Page 23 of 53 L 5 Ble gdt window Heb OS gt see anaga Oracle 828 3 OTM 01 3 UN si g 3 3 101 g 05 Ga 704 28 X12 4010 Transaction Set Header Bearring Seomert for Curency Reference Identiicaton Administiahwe Communia Tax Referenca F O B Reteted Instructians Pricing Ir ormation Penod Amount Sales Requremerts Commodity Serv
31. ervice ID amp 1 Product Service ID741 Product Service ID A1 Product Service ID A LIN 7Assigned Identificat A1 Product Service ID7A1 Product Service ID A1 Product Service ID A1 Product Service ID amp LIN Assigned Identificat amp 1 Product Service ID A1 Product Service ID A1 Product Service ID A1 Product Service ID A 5 SI7107Se Product Service ID Se Product Service ID Se Product Service ID Se Product Service ID Se Product Service Page 36 of 53 ANALYSE THE DATA VALIDATE THE GUIDE LINE This step is to analyze the test data gt Click on Analyzer in the left pane of the below screen Oracle B2B ORACLE B2B Document Editor L y E Mew Document P he x U Powered by EDIFECS SpecBuilder Open Document g EM Analyzer Migtator 5 Data Generalor seed Data Editor an Data Dictionary Editor Data Dictionary Generator rur B Standards Reference a M Additional Offerings gt Select the file to analyse Analyzer Wizard Welcome to the Analyzer Wizard This wizard helps you to validate a data file Select data file to analyze Specify data file type EDI Show Advanced Options gt Click Next Page 37 of 53 i Analyzer Wizard Clean Up Data File Please select how to use Preprocessor Some data files may require preprocessing Please check this option to prepare the data for parsing Specify either the Block Size or the Termi
32. ess to Business Document standard which can be Electronically exchanged between and with in the Enterprise EDI standard define the structure of the Business document for e g Purchase Order Invoice etc Even though it is a flat file standard unlike the popular XML standard it is difficult to replace EDI due to its wider adoption and customer base Advantages of EDI e Well defined structure for handling various Business processes e Matured standard as it addresses every complex use case in various Business domains e Wider adoption and increased customer base e Matured well defined EDDIINT standard such as AS1 AS2 for data exchange EDI Document structure The below picture explains the EDI document structure by taking X12 and EDIFACT document Interchange Control Header ISA UHE Functional Group Header GS UNG Transaction Header ST U HH Transaction Envelope Transaction Header SE UHT Interchange Group Envelope Em elope Transaction Header ST UNH Transaction Envelope Transaction Header SE Functional Group Trailer GE UHE Interchange Control Trailer IEA UH Z Please refer to any Basic EDI tutorial for Document organization EDI documents can be grouped based on some unique criterion and contain Group sender Group recipient etc Which is unique to the group Multiple Group can be enclosed in an envelope called Interchange Group is not mandatory in EDI
33. est data files 4 Generation T ask is a collection of Test Cases It enables automated generation of multiple data files Please select one of the following Mew Test Case C Existing Test Case Select the Generation T ask file Run Analyzer after Data Generator Show Advanced Options lt Back Cancel gt Click next Page 29 of 53 Data Generator Wizard Create or update data file Please select a Data Generator Test Case Action fe Please specify the data file that should be used as the base file Guring data generation This fle will be first parsed and analyzed O specity data Te type ph 700 d gt Click next gt Since the data is generated for user defined guideline select the option as From a guideline file Data Generator Wizard Guideline selection Please select a guideline 9 RniiOrder ecs Specl ecs Spec2 ecs 5 ADAOL ecs Spec3 ecs H Adt2 4 ecs TestHL ecs Is J ADT AO1 xsd ecs 5 AMERIPATHQquideline xsd ecs 5 EnvelopFile HL7 2 5 ecs 3 FilewithBatch ecs 3 Final1 ecs 51 Final ecs 3l Generic ecs 5 guideline xsd ecs SpecBuilder files ec Rm gt Select the newly created ecs file gt Click Next Page 30 of 53 Data Generator Wizard Envelope Segments Please specify Envelope Segments gt Click Next Fa Data Generator Wizard Envelope Segments Please select Envelope Segments from
34. ice Promotion Allowar of Sale Delenad Ter Discount Detal Installment Information Date Time Reterence Lead Time Item iderfificaton Service Charactenstic ident Product Item Description Measurements Paperwork Maiking Packaging Loadr Canes Detais Quantity anc Casier Detade Routing Seq Cames Dotais Equipment Cartier Details Special Han ID Name Functional Group Standard E Notes Set w paz Version v his Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set 850 for use within the context of an Electronic Data Interchange EDI environment The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information Edit the segment level details as per your requirement Save the generated ecs file CREATION of XML Schema Definition xsd for the ECS file This step is used to create the XML Schema definition Open the newly created ecs file gt Click on File Export Select Oracle B2B 2 0 as export format This export routine will convert the guideline from the internal format to one that can be used with the Oracle B2B runtime software 2 0 J 850 ecs Oracle B2B X12 V4010 Fil
35. iry Rele 5 TAXT ax Identification N A Locaton Identher A Location Iderlifisr A Location Idenliker A Locale Identifier Localion amp GJ FOB TI A Descnplion U1 CAF A Descrptien BY Description H CTP AACACT 3234212812318081 4701422784129431 9230197014277721 91 1137763401422391 111419506277901 24 253423218162451 15510907855491 01 15 1280753 01 3022919 1483 01 55 2522716 01 253 2 01 101 8 162371 2394114304238 0111217 153172751014151889041131206692101 4611197861461101613 101 302 RI 22552473432 3129263832 01425617 01 95 21783184591011938622191177677 271401 247872107611 5 8 Gey CTP7AA ACT 3737147701V32491262601127493268471V156332306313 59420118 0130217601 2563758 amp 17 C5D dg CTP AAW ACT 7795204773726116144701N299709086016V12315V01V33113985507128012656214175V5N0113375290472 i CTPA ACT 1 7009915081 22 430531 05391 0232 01 11 41 1159701 3068421 8S0200H 24539901 I5 01 207298472 321T H Gi 01 32 01 27841257773 2 1 29195212 153432 1252 01 1481871529 539 01 883425325252 8 219 2 1 S SL CSH B71767Account Number 20070727 7107AC7A73571 SL CSH B717167162602327 Account Number 20070727 107AC7A7204124502171 Gey CSH B71735747Accourk Number 200707277107AC7A72471 i Gy CSH B 71732455667 Accourt Number 20070727107 AC7A7171 8 ME CSH E717111831136521468 Account Number 20070727 1074C7A75847832271 E TC2 2 Commodity Code s Il LE
36. ma is used by the application where as ecs file is used in B2B M Note While exporting select the option to export in Oracle B2B 2 0 format e Define Document Revision Document Type and Document Definition for configuring specific EDI Document Page 5 of 53 Create a Document Protocol Version gt Click icon in Document Protocol pane to Add Document Protocol Version ORACLE B2B Administration Partners Reports Metrics Help Logout O Logged in as weblogic Deploy Manage Deployments Types Import Export Schedule Batch Manage Batch Callout Purge Listening Channel Configuration El Documents z Document Protocol Version Save Mew Type 08 Document Protocols Custom 83 EDI_EDIFACT xi2 EDI X12 NewVersion Specify the version For the document protocol After the new version is saved you can create a new document type 53 HL7 a OAG version Name 4010 8 PositionalFlatFile Description 83 RosettaNet UCCNet Reset Parameter Interchange croup Delimiters Authorization Information Qualifier 00 Interchange Control Standard Repetition Separator u Authorization Information Interchange Control Version Number 00401 Security Information Qualifier 00 Usage Indicator Security Information Interchange ecs File Browse Interchange Date SystemDate YYMMDD amp Interchange Time 4 SystemTime HHMM gt Provide the Version na
37. me 4010 Field Value Version Name 4010 gt Save the newly created Document Protocol version gt Observe the confirmation message after save activity Create a Document Type ORACLE B2B Administration Partners Reports Metrics Help Logout Logged in as weblogic Deploy Manage Deployments Types Import Export Schedule Batch Manage Batch Callout Purge Listening Channel Configuration El Documents Document Type Save New Definition E Document Protocols Custom EDI EDIFACT E EDI X12 EDI X12 4010 NewDocumentType Specify the document type for this version After the new type is saved you can create a new document definition Document Type Name 850 Description PositionalFlatFile RosettaNet UCCNet Reset Parameter Mm Functional Group Identifier Code po Implementation Convention Reference Transaction Purpose Code Select newly created Document Protocol Version 4010 in Document Protocol pane gt Click icon to Add Document Type gt Provide the Document Type Name 850 gt Provide the Functional Group Identifier Code PO Page 6 of 53 Field Value Document Type Name 850 Functional Group Identifier Code PO gt Save the newly created document Type Create a Document Definition Select newly created Document Type 850 in Document Protocol pane gt Click icon to Add Document Definition 2 Provide the Document Definition Name O
38. ment Type Parameters while defining the Document Type i e Transaction set e Standard Interchange and group ecs files are seeded in the product Unless there is any change in the ecs file due to customization of any of the envelope segments B2B will always refer to the seeded ecs files For any change in the Interchange or group segments it is required to redesign the respective ecs using the Document Editor use it in B2B as group Interchange ecs file M Note t is required to validate and redeploy the agreement for any change in Document parameters e Add these documents to the trading partner with the respective role initiator responder All the documents that are defined are available for Host by default Just need to assign the proper role for the host Add Documents definitions for responder gt Click Documents tab to add the document definition gt Click icon in Document pane to add Document definition to the trading Partner Profile Users ocuments Wer na RS p d aU cA GlobalChips Add the documents that are specific to this trading partner All documents that the host creates are available to add to the trading partner s profile Docum Select Document Definition Definit Custom rm F EDI EDIFACT E ad EDI X12 El z 4010 gs 850 9 997 ug 997def ad HL7 ad OAG PositionalFlatFile ad RosettaNet a3 UCCNet Docu Add Cancel Page 9 of 53 gt Add the documen
39. n be created using the Spec Builder 6 6 1 by exporting the ecs file in Oracle B2B 2 0 format Transaction set ecs file 850 ecs gt Click Save gt Observe the confirmation message after save activity If it is required to process a functional acknowledge create another document definition for the document Type 997 with the following information Page 7 of 53 Field Value Document Definition Name 997def a name of user choice Observe the xsd and ecs files are already being uploaded As this is a common document type it has been made part of default configuration However it is also possible to upload the ecs Update and xsd files for 997 by clicking Update button with below mentioned Field Value Definition 997 xsd The xsd file can be created using the Spec Builder 6 6 1 by exporting the ecs file in Oracle B2B 2 0 format Transaction set ecs file 997 ecs gt Save the newly created Document Definition Administration Partners Reports Metrics Help Logout O Logged in as weblogic Document Deploy Manage Deployments Types gt Import Export Schedule Batch Manage Batch Callout Purge Listening Channel Configuration Documents di gi Document Definition Document Protocols ET Confirmation 33 Custom 997def has been saved EDIFACT EDI xi2 EDI X12 4010 997 997def 3 gi 4010 Enter the document definition name and and select the required definition File
40. nator from which to start the character removal process and then specify the characters which should be removed Parameters Save Block Size excluding terminator sevens C Terminator String Hex re Remove Chars gt Click Next i Analyzer Wizard Data Structure Please select node to link validate Data node name 9 Interchange EntireDocument Group Data node properties 8 Transaction FileName C 850 dat TasklD C 850 dat Data node links Node start position 0 0 0 Node size 19540 0 4 54 Node end position 19540 0 4c54 gt Click Next Page 38 of 53 gt Select the guideline ecs file to check the correctness of data against the newly generated ecs file Guideline selection Please select a quideline A ae 4 as emet EE Mein uc m Files of type SpecBuilder fles lt gt Click Next Since the ecs file does not contains the envelope segments choose the below mentioned options Envelope Segments Please specify Envelope Segments gt Click Next Page 39 of 53 Analyzer Wizard Envelope Segments Please select Envelope Segments from the database 00502 00501 xj 00501 00406 00406 00405 00405 00404 i 00404 00403 00403 00402 00402 with optional s guonte fg ISA Interchange Control Header with optional segments gg GS Functional Group
41. nge depending on Non Repeating Event or Repeating Event gt Click on Search button to get the deployed agreements ElSearch Advanced Saved Search Default Match AI 9 Any Responding Partner Contains Document Protocol Version Equals Agreement Contains v Document Type Equals Document Protocol Name Equals Document Definition Equals Search Reset Save Initiating Partner Responding Partner Agreement Document Protocol Document Version Document Type Document Definition Acme GlobalChips Acme GlobalChips x12 4010 SEDI X12 14010 85 deF gt Click on Create Batch to create the batch De batching EDI Transaction Sets For inbound message oracle B2B Splits the interchange into individual Transaction Set and depending on the Translation flag translate it to Edifecs XML this is a default behaviour and does not require any configuration Page 18 of 53 Additional features Tips and Tricks This section explains few of the advanced topics as well as few of the tips and tricks to handle the some of the complex EDI scenarios Custom Code List EDI In EDI world Interchange receiver Id and Interchange sender Id has set of codelist which is used to validate the EDI Message However it is possible to use the qualifier which is not there in the standard code list e g ZZ as part of the Document Protocol Parameter configuration This is achieved by foll
42. ns Cliff Wright Sundararaman Shenbagam Ted Hong Eng Khor Krishnaprem Bhatia Sankar Mani JK Nair Prasanna Chandrashekhara Dheeraj Kumar Madai Lasted Updated June 7 2012 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 www oracle com Oracle Corporation provides the software that powers the Internet Oracle is a registered trademark of Oracle Corporation Various product and service names referenced herein may be trademarks of Oracle Corporation All other product and service names mentioned may be trademarks of their respective owners Copyright 2008 Oracle Corporation All rights reserved ORACLE Page 53 of 53
43. operty Name ElementDelimiter gt 0x7e lt Property gt lt Property Name InterchangeAckRequested gt 0 lt Property gt Property Name InterchangeAuthorization Info gt Authorizat lt Property gt Property Name InterchangeAuthorization InfoQual gt 00 lt Property gt Property Name InterchangeChildCount gt 1 lt Property gt lt Property Name InterchangeComponentElementSep gt 0x5c lt Property gt Property Name InterchangeControlNumber gt 691 244239 lt Property gt lt Property Name InterchangeControlStandard_RepeatingSeparator gt U lt Property gt Property Name InterchangeControlVersion gt 00401 lt Property gt Property Name InterchangeSenderQual gt 01 lt Property gt Property Name Interchange Time gt 1525 lt Property gt Property Name Interchange TrailerControINumber gt 691 244239 lt Property gt Property Name InterchangeUsagelndicator gt lt Property gt Property Name SegmentDelimiter gt 0x0d0x0a lt Property gt Property Name Standard gt X12 lt Property gt Property Name SubelementDelimiter gt 0x5c lt Property gt lt Data Structure gt lt Internal Properties gt Please refer to EDI Batching section for handling multiple Transaction Set in an Envelope Page 11 of 53 Inbound EDI Processing Depending on the translation flag B2B translate the inbound native EDI documents to Edifecs XML to be consumed by the back end application The Edifecs XML generated also has all the Document
44. owing the below steps 1 Modify the interchange ecs file to add the YZ in the standard code list 1005 2 This can be done by editing the Interchange ecs file in the spec builder and adding YZ in the ISAI05 Interchange ID Qualifier Standard Code List 1005 Use the updated ecs while configuring the X12 document protocol parameter as interchange ECS 3 Re deploy the agreement after validation 4 Ensure Interchange ecs do not have any group transaction set information This could be tested by exhanging an EDI document whose Interchange Receiver ID as ZZ This also applicable to all the codelists Handling Positional Flat File Apart from the capability of Handling XML file and Traditional EDI file based on various XML and EDI Standard Oracle AS B2B also provides an option to Handle positional Flat File 1 Design the ecs file in spec builder depending on the Positional Flat file 2 Provide the newly created Ecs file as part of the Document definition Parameter along with start position and End position while creating the new document for PositionalFlatFile Page 19 of 53 Performance Best Practices Following are the few of the Best practices for Oracle AS B2B Performance and can be tuned based on the system resources Outbound processing b2b outboundThreadCount no of threads to be spawned for outbound flow b2b outboundSleepTime 1000 Sleep time in msec for thread when there is no message Inbound process b2b inboundTh
45. ration tab E Acknowledgment Functional 4ck Handled by B2B true Functional 4ck internal False properties Notify Inbound Receipt Acks False Notify Inbound Functional Acks False Page 14 of 53 Overriding the Document Protocol Parameter for FA Consider a use case which requires overriding the Interchange Sender ID in the Document Protocol Parameters using the Internal Properties in the Outbound Edifecs Document or using the value present in inbound Business message such as 850 To enable the internal properties to be used in outbound processing set the Functional Ack Internal properties to true in the below picture This screen is available at gt Goto Administration gt Click Configuration tab l Acknowledgment Functional Ack Handled by B2B true Functional 4ck internal Fale properties Notify Inbound Receipt Acks Notify Inbound Functional Acks Fais This will override the Document protocol parameter value of Functional Acknowledgement with Internal Property in the generated Functional Acknowledgement EDIEL Support Oracle B2B also supports another variant of EDIFACT which is EDIEL used in Electrical industry In this case in addition to all the features of EDIFACT it is also possible to e Customise the FA Message Version Number and FA Message Release Number The default value for this is D3 e Provide the reference to the MAP APPLICATION REF of the incoming message to be referred as part of FA
46. readCount no of threads to be spawned for inbound flow b2b inboundSleepTime 1000 Default threads for process all the events b2b defaultThreadCount no of threds to be spawned for all events such as delivery channel creation updating system parameter updation etc including the message flow in both the direction gt b2b defaultSleepTime 1000 Large Payload Configurations Following steps need to be configured in case of large payload above 100Mb 1 Asa pre requisite the following properties need to be set in B2B In Admin gt Configuration e Use JMS Queue as default property as true e Logpayload property to be false e Large Payload Size property as lt payload size gt e Large Payload Directory eg tmp 2 jvm memory args e Increase max heap size according to machine available RAM E g for 2GB Xmx2048m and also change min heap size needy basis 3 Database Configuration changes e DBA can tune the db appropriately based on the message flow 4 Transaction Timeout settings In Weblogic console e Increase JTA transaction timeout from weblogic console Services gt JTA Timeout Seconds 120 seconds e Increase SOADataSource XA timeout setting to 120 180seconds weblogic console Services gt JDBC gt DataSources gt SOADataSource 5 Fabric settings For fabric based testing use streaming option incase of file adaptor listener Page 20 of 53 Comment 01 also we can point to the performance tuning guide which
47. rocessing This approach requires disabling the translation flag while creating the agreement as B2B acts as a gateway forwarding the document to the TP In this mode no correlation will be done with respect to functional acknowledgment e XML It is required by the back end application to get the data from downstream application and transform it to xml as defined by the schema Back end application is required to send only one transaction set at a time to B2B as B2B generates the envelope using the pre seeded envelop details If the Back end application has an envelope with multiple Transaction Sets it is required to split the same into multiple transaction and enqueue it to be processed by B2B Alternatively it is also possible to override the Document Protocol Parameter defined in B2B for a specific Document Type and Revision by specifying the Internal Property in the Edifecs XML For e g the elements with lt Lookup tag will be used for validation Internal Properties xmIns http www edifecs com xdata 100 gt lt Data Structure Name Interchange gt Lookup Name InterchangeControlVersion gt 00401 lt Lookup gt lt Lookup Name InterchangeReceiverlD gt Interchange Rec lt Lookup gt lt Lookup Name InterchangeReceiverQual gt 01 lt Lookup gt Lookup Name InterchangeSender D gt Interchange Sen lt Lookup gt Lookup Name InterchangeSenderQual gt 01 lt Lookup gt lt Lookup Name Standard gt X12 lt Lookup gt lt Pr
48. t to the trading partner Select appropriate role for 850def sender receiver depending on the business usecase gt Click Save Similarly gt Select appropriate role for 997def sender receiver depending on the business usecase gt Click Save Profile Users Documents Channels amp GlobalChips Add the documents that are specific to this trading partner All documents that the host creates are available to add to the trading partner s profile Confirmation EDI_X12 4010 997 997def has been saved Documents o lBMtos 1 1 1 11 o Sede Reeer EDI X12 4010 850 850def EDI X12 4010 997 997def _ Ss Document Details Reset Parameter Version Document Type Definitions Interchange Group Delimiters Authorization Information Qualifier 00 Interchange Control Standard Repetition Separator J Authorization Information Interchange Control Version Number 90401 Usage Indicator Security Information Qualifier 00 Page 10 of 53 Outbound EDI Processing B2B can receive 2 types of EDI documents from Back end Application e Native EDI B2B acts as a gateway doing the validation of the document and forwards it to the respective trading partner using designated exchange protocol This approach does not provide typical of the EDI features such as Batching and generation of the Interchange and group as appropriate Hence it is required to send the complete envelope for B2B p
49. ting the control Ack and business messages However if the translation is enabled B2B can correlate the business message and functional acknowledgement E g To correlate 850 EDI message with 997 Control Number Generated by B2B In case of Outbound Messages B2B Generates the control number only in case the Back end application send the EDI message with the macro controlNumber for e g lt Element 329 gt ControlNumber lt Element 329 gt Oracle B2B fills in the unique number for Interchange and Transaction set Control Number and uses it for correlating the incoming Control messages Note this is not a preferred approach as most of the correlation has to happen in the back end application Page 16 of 53 EDI Batching Batching of EDI messages allows the users to send all messages of particular criteria at a specified time This can include a set of messages with 1 Same document type can be sent to one or more trading partners 2 Multiple document type can be sent to one or more trading partners Batching concept is widely used in Retail industry as the number of messages processed is high in number As the Retail traders widely use EDI as the means of communication the Batching suits well to EDI domain Batching EDI Transaction Sets Individual transactions are sent to the internal delivery channel one transaction at a time For outbound messages received on the internal delivery channel transaction sets can be batched
50. with optional validation e Oracle B2B would not provide features such as Batching etc with this configuration e ltis required to send the complete envelope as Oracle B2B will not generate the envelope using Document Protocol Parameters like in case of Edifecs XML processing What if have a native EDI file in the back end application can I process in B2B Refer to Q1 What if have a EDI document with multiple transactions how do I handle in B2B Oracle B2B Processing is based on Transaction set hence it is required to split the envelope into multiple transactions and send it to B2B B2B translates the transaction set into native EDI and generates the envelope using the Document Protocol Parameters Can receive EDI document with multiple transactions from a trading partner Yes Oracle B2B provides a feature of debatching for inbound messages Refer to section EDI Debatching for more details Can I outbound batch a native EDI documents to be sent to B2B from Back end application No Refer Q1 Can I customize the group and Interchange ecs files How Yes it is possible to customize Group and Interchange ecs file using Oracle B2B Document editor and upload the same at the trading partner level What is the preferred Exchange protocol for EDI EDI won t mandate any Exchange protocol as such However AS1 AS2 are the most popular exchange protocol which go well with EDI Can I disable the validation of incoming data against the
51. world and is possible to enclose the documents directly under Interchange Page 4 of 53 Sample X12 file ISA 00 Authorizat 00 Security I 01l Interchange Sen Ol Interchange Rec 071105 2249 U 00401 849818414 0 I 4 GS PO Ap Ap 20071105 2249 83 T 004010 ST 850 2604 BEG 00 AB P 20071105 PO1 123 SE 4 2604 GE 1 83 IEA 1 849818414 EDI Support in Oracle B2B Oracle B2B supports both the EDIFACT and X12 flavor of EDI Oracle Integration B2B has teamed up with EDIFECS to provide their robust translation and validation engine as an integral part of Oracle Integration B2B This solution provides A library of ALL EDIFACT X12 HL7 HIPAA EANCOM NCPDP Script transaction sets Data file validation Data Migration Tests data generation De ldentification Dictionary generation Batching Guideline migration User Experience while configuring EDI protocol in Oracle B2B The following are the steps to configure an EDI document in Oracle B2B e Identify the Document to be exchanged with the Trading Partner it includes EDI Standard Document Type and Document Revision e g Standard X12 Document Type 850 Document Revision 4010 gt Goto Administration gt Select Document gt Select Document Protocols gt Select EDI X12 e Create the ecs file based on the document to be exchanged using Oracle B2B Document Editor Please refer to the Document Editor Section e Export the ecs file to get an XML schema file Sche
52. y view included items by clicking on the toolbar icon View the N101 code list to verify the code values are limited to those present in the data file Save the specification document as Lab7 850 ecs and close the guideline Page 48 of 53 Typical EDI Errors 1 Unable to identify the Document Make sure the document EDI document is well formed by using B2B document editor 2 Agreement Identification which involves Document Identification and TP Identification Agreement not found for trading partners FromTP GlobalChips ToTP Acme with document type 850 4010 INBOUND Check Make sure to verify Trading Partner Name Trading Partner Parameters Optional Document Type Name Document Type Revision Trading Partner Id Delivery Channel 3 Document Validation Error Check 1 Make sure Document Protocol Parameters and matching values Proper ECS file is used for Validation 4 Connection Issues Transport error IPT HttpSendConnectionRefused HTTP connection is refused Connection refused connect Check Make sure the information about delivery channel is correct and also the end point is active Pinging the end points can do this Page 49 of 53 Is it always mandatory to send the Edifecs XML to B2B for EDI processing It is possible to process Native EDI Edifecs XML and any other flat file using Oracle B2B Following are some of the features with native EDI Flat File Processing e Translation should be switched off

Download Pdf Manuals

image

Related Search

Related Contents

Wireless Presentation System Système de Présentation  EK Water Blocks 3830046990709  Jonsered CS 2156 Operator's Manual  PICO® xMOD™-VENtIl Bedienungsanleitung  Fujitsu Pocket LOOX Bundle Pocket LOOX N520 ENG + MobileNavigator 6  User manual to install QB64 on Precise Pangolin Ubuntu  SpartyJet User`s Manual  Holga 120S User Guide  MANUEL D`UTILISATION POMPE AGRIDOSE PRO  N°81 - Efsra  

Copyright © All rights reserved.
Failed to retrieve file