Convert Windows Trading Partner Data

You can convert trading partner data to import into Sterling B2B Integrator.

About this task

To convert trading partner data:

Procedure

On the host computer where Sterling B2B Integrator is installed, navigate to the \install_dir\install\tp_import directory.

Review the following command line options to define how you want to convert trading partner data (.par files) to an .xml file. You can specify these command line options in any order:

Option	Description	Example
-dir	Directory where the .par files (trading partner data) are saved. Enables the script to convert all the .par files in this directory into an .xml file. Required when converting a batch of .par files and not using the -singleparfile option (see `-singleparfile`). Directory can contain only like partners (for example, all XML). When converting a batch of .par files, each file must maintain the same EDI code (you can repeat the conversion procedure for each directory of .par files having a different EDI code)	winconvert.cmd -dir <.par files directory path> `-sysedicode ABC` where `ABC` is the system EDI code.
-sysedicode	Sterling Gentran:Server for Windows EDI code for the partner profile. This code will be used as the ReceiverID for the inbound envelope definitions (ISA, GS and ST). Required. If you do not supply the sysedicode, the utility continues executing. For example, if you run winconvert.cmd -singleparfile PETZONE.PAR, the utility reports that sysedicode is missing, prints the usage menu, and continues to create the .xml and report file. Note: The conversion defaults the receiver ID value. If you do not want to use the default Receiver ID value, you must edit the envelopes in Sterling B2B Integrator after conversion.	winconvert.cmd -dir <.par files directory path> `-sysedicode ABC` where `ABC` is the system EDI code.
-output	Filename path of the .xml file created by the utility. This .xml file contains the output of all of the converted trading partner data. Optional. Consider specifying a meaningful name for the .xml file. To specify a name, type -output and the new file name—for example, to specify `partner` as the name, type the following command: `-output partner.xml` The default name is final.xml.	winconvert.cmd -output partner.xml -dir <.par files directory path> `-sysedicode ABC` where `ABC` is the system EDI code.
-singleparfile	Name of a single .par file. Enables the script to convert the .par file to XML. Required if not using -dir option.	winconvert.cmd -singleparfile petzone.par `-sysedicode ABC` where `ABC` is the system EDI code.
-report	Filename path of the report file created by the utility. This report contains information about the conversion. Review this report using a text editor to determine if any errors or warnings occurred during the conversion. Optional. Consider specifying a meaningful name for the report file. To specify a name, type -report and the new file name—for example, to specify `partner` as the name, type the following command: `-report partner.rpt` The default name is `winconversion.rpt`.	winconvert.cmd -report partner.rpt -dir <.par files directory path> `-sysedicode ABC` where `ABC` is the system EDI code.
-encoding	Character encoding type. Enables the script to convert.par files to the character encoding type specified. The default is the UTF-8 character encoding type. Optional.	winconvert.cmd -singleparfile CII.par -encoding SJIS `-sysedicode ABC` where `CII.par` is the partner file name and `ABC` is the system EDI code.

Option

Description

Example

-dir

Directory where the .par files (trading partner data) are saved. Enables the script to convert all the .par files in this directory into an .xml file. Required when converting a batch of .par files and not using the -singleparfile option (see -singleparfile). Directory can contain only like partners (for example, all XML).

When converting a batch of .par files, each file must maintain the same EDI code (you can repeat the conversion procedure for each directory of .par files having a different EDI code)

winconvert.cmd -dir <.par files directory path> -sysedicode ABC

where ABC is the system EDI code.

-sysedicode

Sterling Gentran:Server for Windows EDI code for the partner profile. This code will be used as the ReceiverID for the inbound envelope definitions (ISA, GS and ST). Required.

If you do not supply the sysedicode, the utility continues executing. For example, if you run winconvert.cmd -singleparfile PETZONE.PAR, the utility reports that sysedicode is missing, prints the usage menu, and continues to create the .xml and report file.

Note: The conversion defaults the receiver ID value. If you do not want to use the default Receiver ID value, you must edit the envelopes in Sterling B2B Integrator after conversion.

winconvert.cmd -dir <.par files directory path> -sysedicode ABC

where ABC is the system EDI code.

-output

Filename path of the .xml file created by the utility. This .xml file contains the output of all of the converted trading partner data. Optional.

Consider specifying a meaningful name for the .xml file. To specify a name, type -output and the new file name—for example, to specify partner as the name, type the following command:

-output partner.xml

The default name is final.xml.

winconvert.cmd -output partner.xml -dir <.par files directory path> -sysedicode ABC

where ABC is the system EDI code.

-singleparfile

Name of a single .par file. Enables the script to convert the .par file to XML. Required if not using -dir option.

winconvert.cmd -singleparfile petzone.par -sysedicode ABC

where ABC is the system EDI code.

-report

Filename path of the report file created by the utility. This report contains information about the conversion. Review this report using a text editor to determine if any errors or warnings occurred during the conversion. Optional.

Consider specifying a meaningful name for the report file. To specify a name, type -report and the new file name—for example, to specify partner as the name, type the following command:

-report partner.rpt

The default name is winconversion.rpt.

winconvert.cmd -report partner.rpt -dir <.par files directory path> -sysedicode ABC

where ABC is the system EDI code.

-encoding

Character encoding type. Enables the script to convert.par files to the character encoding type specified.

The default is the UTF-8 character encoding type. Optional.

winconvert.cmd -singleparfile CII.par -encoding SJIS -sysedicode ABC

where CII.par is the partner file name and ABC is the system EDI code.

Convert the trading partner data using the appropriate command.
- For UNIX, enter: ./winconvert.sh
- For Windows, enter: winconvert.cmd
Note: Append the appropriate parameters to further qualify how the data gets converted.

Determine if you are a CII user using the winconvert.cmd utility:

If...	Then...
No	Skip this step.
Yes	Add the CII Syntax ID to the .xml result file after you convert a Sterling Gentran:Server for Windows trading profile file. The CII Syntax ID is required in Sterling B2B Integrator.

Verify that each value in the XML data is correct.

Results

You can now import the converted data into Sterling B2B Integrator.