Description

When an EDI 850 Project is created in GenRocket, the entire Transaction Set is enabled. Of course, when you are testing a Transaction Set, not every Segment, Loop, and Element will be needed to complete each test or to achieve a specific Business Case Scenario.


This is where Test Data Cases can be extremely beneficial because they make it possible to fully customize what Transaction Set Segments, Loops, and Elements will be used to generate data. Additionally, you can add Segments (i.e. Domains), add Attributes, and make Generator Configuration changes that are specific to the Test Data Case, but do not effect the Project as a whole. 


When should Test Data Cases be used for EDI 850 Projects?

Test Data Cases can be used to perform specific types of testing (Negative, Integration, Beta, etc.) and for testing Business Case Scenarios., such as: 

  1. Stand Alone-Original Domestic Order
  2. Stand Alone-Original - Ship Direct to Stores
  3. Blanket Order (#00899) and then Release of Order (Pack by Store)
  4. Release Order Transmission with Store Location Numbers Provided
  5. Release Order with DC Allocations - Multiple Prepack (One assortment per Carton)
  6. Release Order with DC Allocations - Inner Prepack (More than one of the same Assortment per Carton)
  7. Release Order with DC Allocations - Compound Multiple Prepack (One Assortment per Carton)
  8. Domestic Private Brand / Exclusive Brand Release Order - Bulk
  9. Import Blanket Order - Multiple Prepack (Prepack order containing one or more of the same UPC / EAN)
  10. Import Letter of Credit Order - Bulk


We have provided samples of the above Business Case Scenarios within the G-Case Dashboard, which you can copy and customize to meet more specific needs. 



How to use Test Data Cases for Business Case Scenarios

To set up a Test Data Case to generate data matching a specific Business Case Scenario, complete the following steps: 


Step 1: Copy a Provided Business Scenario Test Data Case

Note: It is recommended to copy a provided Business Case Scenario and to modify the created copy rather than the original Test Data Case. 

Complete the following steps to do so:

  • Within the G-Case Dashboard, click on the Copy icon within the Actions column.


  • Enter a new Name and Description for the copied Test Data Case.

  • Click Save once finished.


Step 2: Disable/Enable EDI Segments, Loops, and Elements within the Test Data Case

Segments, Loops, and Elements have already been disabled to create each provided Business Case Scenario sample. Once the Test Data Case has been copied, you can enable or disable these items to meet more specific needs. 


To enable or disable specific items within the Transaction Set, complete the following steps: 

  • Choose the EDI View from the drop-down menu.


  • Click on the EDI Tree icon on the G-Case Editor tab.


  • Use each checkbox to enable or disable a Segment, Loop, or Element. A checkmark means the item is currently enabled.


  • Expand Segments and Loops within the EDI Tree View to make additional changes. In this example, BGN_BeginningSegmentforPurchaseOrder has been expanded. 

     
  • Click OK once finished.
     
  • EDI 850 Segments will appear as part of the Test Data Case, as shown below. What Segments are enabled and disabled will depend on what was disabled in the steps above. You can enable and disable Segments within the Test Data Case as needed. 


Step 3: Add Segments or Remove Segments from the Test Data Case (Optional)

Segments can be added to or removed from the Test Data Case after completing Step 2. If a Segment is added and enabled, then test data will be generated for that Segment when the Test Data Case is run.


To add a Segment to a Test Data Case, complete these steps: 

  • Use the Filter to locate each needed Segment. For this example "CTP" has been entered to find all available CTP Segments and Loops.


  • Next, click the Plus (+) icon located to the right of the Segment within the G-Case Editor tab.



  • Added Segments and Loops will appear within the table located on the right of the G-Case Editor tab.


  • To remove a Segment from the Test Data Case, click on the Remove (-) icon within the Actions column.


Step 4: Disable/Enable Segments within a Test Data Case (Optional)

Segments added to a Test Data Case can be enabled or disabled as needed to alter what test data is generated when the Test Data Case is run. 


To disable or enable a Segment, click on the toggle slider to the right of its name.

  • Blue - Enabled
  • White - Disabled



Step 5: Alter Loop Counts for Segments

The Loop Count for each Test Data Case Segment can be changed to a Constant, Random, Increasing, or Decreasing value. 



For example, Loop_PO1 may need to have a constant Loop Count of 5 because there are 5 items in the Purchase Order. Complete these steps to update the Loop Count for a Segment: 

  • Click on the Update Loop Count for Domain icon within the Actions column.


  • Choose a Loop Type and then complete the required parameters for your selection. 

  • For this example, the Loop Type has been left as Constant and the Loop Count has been set to 5

  • Click the Save button when finished.


  • The Domain will now have a constant Loop Count 5, as shown below:


Step 6: Add Attributes to Test Data Case Domain for the Segment

In some instances, you may need to make changes to the generated data for a specific Test Data Case to match the Business Case Scenario. This can be done by adding an Attribute to the Test Data Case Domain.

  • Click the Edit Test Data Case Domain icon in the Actions column for the Test Data Case Domain.
     

  • For this example, the BGN_BeginningSegmentforPurchaseOrder will be modified.



  • Click the Plus (+) button to add one or more Attributes to the Test Data Case Domain.


  • In the dialog window, tick the checkbox for each Attribute that needs to be added.


  • Click the Save button once finished.


  • Each Attribute will be added to the Test Data Case Domain.
     

  • You can now replace the Generator or make changes to the Generator's Parameter configuration for each added Attribute to generate the appropriate test data for your Business Case Scenario.



Step 7: Alter Generator Configurations for Added Attributes

The Generator configuration for each added Test Data Case Domain Attribute can be modified to meet a defined Business Case Scenario need. Below are 2 examples that show how to: 

  • Alter the Generator Parameters
  • Replace the Current Generator


Example 1: Remove Values from a Test Data Case Domain Attribute

For example, let's say that only one Purpose Code is needed in the BGN_BeginningSegmentforPurchaseOrder Segment. Remember, a purposeCode01 Attribute was created for the Test Data Case Domain in Step 6 above.


The purposeCode by default has 5 codes: 00, 01, 03, 04, and 07. For this sample, only 00 is needed. You will need to modify the Generator Parameter configuration so that only 00 is generated. Complete the steps below: 

  • Click on the purposecode01 Attribute.


  • Click on a value within the list to select it and then click the Remove button. 

  • This will need to be done four times to remove each value from the Attribute.


  • The configuration will appear as shown below. Click the Save Generator button.



Example 2: Replace a Generator for a Test Data Case Domain Attribute

In some Business Case Scenarios, an Attribute will need to be set to "Empty" to ensure no data is generated for that Attribute and that it is still part of the generated test data. At other times, a constant text value may need to be used during test data generation.


The following example shows how to set the typeCode02 Attribute for the BGN_BeginningSegmentforPurchaseOrder Segment to a constant value of "SA":

  • Click on the typeCode02 Attribute to select it.


  • If the Attribute has several list values, the easiest method will be to change the Generator to the ConstantGen Generator.


  • This can be done by selecting the ConstantGen Generator in the Quick Generator Replacement Menu.

  • Once selected, click the Replace button to replace the current Generator.


  • For the value Parameter, you can enter one of the following: 
    • #{EMPTY} - The Attribute will have no value for each record.
    • Specific Value - The Attribute will have the entered value for each record.

  • Click the Save Generator button.


Generating EDI Test Data

Once the EDI 850 Test Data Case has been configured for your specific Business Case Scenario, you will be able to download and run the Test Data Case using the command line provided at the bottom of the Test Data Case Dashboard.



EDI Projects have a Scenario Chain Set and a Config File that must also be downloaded in order to generate test data for a Test Data Case. 

You can download these items from the EDI Dashboard, which is accessed by expanding the Management drop-down menu and selecting EDI Management.



Select the EDI-850 Project. Then click on the EDI Config and Scenarios buttons to download these items. 

Please note that it takes a little time to download the Scenario Chain Set. For detailed steps, click here.


The name of the set will replace <ScenarioName.grs> within the command line above. For an EDI 850 Project, the name would look similar to this: EDI850ScenarioChainSet. Please note that this name could be different based on the Project. 


Conclusion

EDI Test Data Cases can be used to customize what Segments, Loops, and Elements are included in generated Test Data.


Domains, Attributes, and Generator configurations can be modified to test specific Business Case Scenarios within a Test Data Case without impacting the original EDI Project Configuration.