Description

This article shows how to set up a basic 850 EDI Transaction Set for test data generation in GenRocket. We have configured the necessary Segments (i.e. Elements) to generate output based on the following specification.



Sample Story

To configure an EDI Project to output the specification sheet shown above, an EDI Project will need to be created and configured to match the defined specifications.


The following steps will need to be completed to generate the desired output file: 

  1. Create an EDI Project
  2. Remove Segments/Loops from the EDI Configuration
  3. Configure Generators and Values for Attributes
  4. Download the EDI Config File
  5. Download and Run the Scenario Chain Set


Step 1 - Create an EDI Project

Create a new EDI Project through the EDI Store. If a Project already exists for the 850 EDI Transaction Set, it may need to be renamed to prevent a version of the existing EDI Project from being created. 


Complete the following steps:

  • Click on EDI Store within the EDI Dashboard.


  • Select the 850 Transaction Set.


  • Click on Create Project for the selected transaction set.


Note: It will take approximately 5 to 15 minutes for GenRocket to create the EDI Project. You will receive an email when the EDI Project has been created.


Step 2 - Remove Segments/Loops/Fields from the EDI Configuration

Some EDI Segments, Loops, and Fields will need to be removed from the EDI Configuration to match the specification shown above. 

  • Locate each Segment, Loop, or Field that should not be included. 
  • Remove the checkmark to not include the Segment, Loop, or Field.
  • Expand a Segment by clicking on the Expand Icon to uncheck specific fields or loops.
  • For this example, the following Segments are enabled: 
    • BEG_BeginningSegmentforPurchaseOrder
    • REF_ReferenceIdentification
    • CSH_SalesRequirements
    • DTM_DateTimeReference
    • Loop_N1
    • Loop_PO1
    • Loop_CTT



2a - BEG Segment Checked Fields

  • BEG01_TransactionSetPurposeCode
  • BEG02_PurchaseOrderTypeCode
  • BEG03_PurchaseOrderNumber
  • BEG04_ReleaseNumber
  • BEG05_Date
  • BEG06_ContractNumber


2b - REF_ReferenceIdentification

  • REF01_ReferenceIdentificationQualifier
  • REF02_ReferenceIdentification



2c - CSH_SalesRequirements

  • CSH01_SalesRequirementCode


2d - DTM_DateTimeReference

  • DTM01_DateTimeQualifier
  • DTM02_Date


2e - Loop_N1

  • N1_Name_N1


2f - Loop_PO1

  • PO1_BaselineItemData_PO1


2g - Loop_CTT

  • CTT_TransactionTotals_CTT


Step 3 - Configure Generators and Values for Attributes

GenRocket automatically assigns a default Generator for each EDI Segment Attribute. This section shows what Attribute Generators and values need to be altered within the EDI Configuration.


Note: To learn how to assign a new Generator to a Segment Attribute, please see this article: How to Assign a Different Generator to an EDI Segment Attribute?.


3a - BEG_BeginningSegmentforPurchaseOrder

  • purposeCode01 Attribute


  • typeCode02 Attribute


  • orderNumber03 Attribute


  • releaseNumber04 Attribute


  • date05 Attribute


  • contractNumber06 Attribute


3b - REF_ReferenceIdentification

  • idenficationQualifier01 Attribute


  • REF0202 Attribute


3c - CSH_SalesRequirements

  • requirementCode01 Attribute


3d - DTM_DateTimeReference

  • timeQualifier01 Attribute


  • date02 Attribute


Step 4 - Download the EDI Config File

After the above configuration changes have been made, the next step will be to download the EDI Config file and place it within your config directory.


Note: More information about this step can be found by viewing this article: How Do I Generate My EDI Test Data?


Step 5- Download and Run the Scenario Chain Set

Next, you will need to download and run the Scenario Chain Set for your EDI Project. This will generate your output file based on the configuration set up in the previous steps.


Note: More information about this step can be found by viewing this article: How Do I Generate My EDI Test Data?


Completed Story Test Data Output File

The following is the generated output file after running the Scenario Chain Set set up in this example: