The entire document is validated by default. In the Data Structure dialog, click Next. No preprocessing is needed in this scenario. In the Clean Up Data File dialog, click Next. Using the Oracle B2B Document Editor Analyzer, validate the data file against the orders.ecs guideline file, and test the data file against the standard to check for required segments or elements that may be missing.īrowse for D98A_orders.dat and click Next.Įnsure that Show Advanced Options is selected, and click Next. The DAT file opens, as shown in Figure 3-7. Select any data dictionaries you want to use.Īccept the default delimiters and click Next.Ĭlick Output Data file name, enter C:\D98A_ORDERS.dat and click Next. Set the repeat count options, depending on how many messages you want generated. Select Mandatory + Percentage of optional data and move the slider to indicate the percentage. The envelope segments are not incorporated in the guideline file.
Select Use directly from the Standards Database and click Next. Select the Syntax 3 envelope segment and click Next. Select Select Envelope Segments from the Standards Database and click Next. Select From a guideline file, select ORDERS.ecs, and click Next. This step generates new data using the specified data dictionaries. Using the Oracle B2B Document Editor Data Generator, create a test data file based on the guideline. The orders.xsd file is created in Oracle B2B 2.0 format. If you see the message Some characters were replaced in XSD names because No macros are needed for any of the nodes in this scenario. If you want to start Oracle B2B, enter the URL for your B2B interface ( host_name:port/ b2b). The data type of the XSD element is changed from numeric to string to enable the count.Įnsure that the Launch Oracle B2B option is not selected (it is not needed in The SegmentCount macro counts the number of segments. In the Document Conversion Options dialog, accept the default, Allow to use SegmentCount macro, and click Next. Suppressing enumeration reduces the XSD size considerably.Ĭheck the Use this export module instead of default during XData generation option.
#Oracle b2b document editor code
This is recommended because code lists are in the ECS file. Any changes will cause theĬONTRL and 997 generation to fail because B2B relies on the default tags toĬheck the Suppress Enumeration in XSD option. Note:Do not modify any information in this dialog.