Creating HL Segments

[jackharris]

From a flat file, I'm attempting to create an X12 856. The flat file is a 945 without HL segments and the X12 is an 856 with HL segments and I don't know much of anything about how the 856 functions.

I looked up the construction of the segment and found that the HL01 increments through out the file and the HL02 refers to previous HL01s as a Parent.

Based on the sample 856 I'm looking at, the HL02 refers to the previous parent anytime there's a new item which leads me to believe that each item is considered to be a package in this 856.

My question is how to map the HL02 segment? Is it a series of containers that refer back to previous elements? If so, how do I reference them?

I did find the following discussion on the topic, but it was never resolved.

[jackharris]

I've been thinking through this and I think what needs to happen is a transformation that will create the HL segments. I'm working through that and will give my feedback unless someone else is able to provide a possible solution.

Thanks for any and all assistance.

[tylerlamparter]

@jackharris it looks like you will need to calculate this in a script (preMap on import or preSavePage on export) prior to getting to the EDI building translation. I haven't dealt with these 856s before, but the structure is weird since everything is put into HL and not some other segment for the packs. Since it's not in it's own sub segment, it forces you to create this parent level reference.

[jackharris]

You wouldn't happen to be able to help me find a starting point or seed code that I could build from, would you?

[tylerlamparter]

@jackharris what does your sample output look like?

[jackharris]

[ {
    "data": {
      "CODE CLIENT": "MAR08",
      "Transaction Set": "945",
      "wHSE": "W1",
      "ST": [
        {
          "ReportingCode": "F",
          "DepositorOrderNumber": "263738",
          "Date": "20240117",
          "ShipmentID": "2090416",
          "PurchaseOrderNumber": "VEGGA00000",
          "AlternateReference1": "27864",
          "LoadNumber": "",
          "SpecialHandlingCode": "",
          "ReasonCode": "",
          "TransactionTypeCode": "",
          "ActionCode": "",
          "AlternateReference2": "",
          "Reference1": "",
          "Reference2": "945Q/DOM",
          "Reference3": "INO",
          "N1": [
            {
              "OrganizationIDCode": "WH",
              "name": "Distribution Technology"
            },
            {
              "OrganizationIDCode": "DE",
              "name": "MARIO CAMACHO FOODS"
            },
            {
              "OrganizationIDCode": "ST",
              "name": "PROGRESSIVE FOOD SOLUTIONS LLC",
              "IDType": "91",
              "EntityCode": "PRO8603006",
              "Address1": "REDIRECT CENTER",
              "Address2": "860 PICKENS INDUSTRIAL DRIVE",
              "City": "MARIETTA",
              "State": "GA",
              "Zip": "30062"
            }
          ],
          "G62": [
            {
              "Date Qualifier": "02",
              "Date": "20240118"
            },
            {
              "Date Qualifier": "10",
              "Date": "20240117"
            },
            {
              "Date Qualifier": "52",
              "Date": "20231211"
            }
          ],
          "TransportationMethod": "H",
          "SCAC": "CPU",
          "Routing": "CUSTOMER PICK-UP",
          "MethodofPayment": "CC",
          "LX": [
            {
              "Assigned Number": "000001",
              "SSCC18": "00007291482000252297",
              "Description": "RIPE SLICED REDUCED BRINE",
              "OrderStatusCode": "CC",
              "OrderedQuantity": "40",
              "ShippedQuantity": "40",
              "QuantityDifference": "0",
              "UOM": "CA",
              "UPC": "",
              "VN": "VN",
              "Item": "7365171058-CT",
              "Lot": "SEP062026",
              "ReferenceQualifier": "ZZ",
              "ReferenceID": "1",
              "ExpiryQualifer": "36",
              "ExpirationDate": "20260906"
            }
          ]
        }
      ],
      "Authorization Information Qualifier": "00",
      "Authorization Information": "",
      "Security Information Qualifier": "00",
      "Security Information": "",
      "Interchange ID Qualifier(ISA05)": "12",
      "Interchange Sender ID": "7045875587",
      "Interchange ID Qualifier(ISA07)": "12",
      "Interchange Receiver ID": "8133054539",
      "Repetition Separator": "^",
      "Interchange Control Version Number": "00501",
      "Acknowledgment Requested": "0",
      "Usage Indicator": "P",
      "Component Element Separator": ":",
      "Functional Identifier Code": "SH",
      "Application Sender's Code": "PPSF",
      "Responsible Agency Code": "X",
      "Version / Release / Industry Identifier Code": "005010",
      "cache": {
        "interchangeControlNumber": "000000019",
        "groupControlNumber": "000000019"
      }
    }
  }
]

[tylerlamparter]

@jackharris you should try and give Celigo AI a go. It gave me this with the first prompt. I'm assuming each ST object you have goes to a HL and then LX to sub of HL (not completely sure what you need, but you can adjust).

Prompt:

Can you go through each ST object and each LX object and add a sequential counter called "Hierarchical ID Number". Then for each LX object, can you add a field called "Hierarchical Shipment Parent ID Number" and the value of it will be the value of the "Hierarchical ID Number" within the ST object outside of itself

Script:

/*
* preMapFunction stub:
*
* The name of the function can be changed to anything you like.
*
* The function will be passed one ‘options’ argument that has the following fields:
*   ‘data’ - an array of records representing the page of data before it has been mapped.  A record can be an object {} or array [] depending on the data source.
*   '_importId' - the _importId currently running.
*   '_connectionId' - the _connectionId currently running.
*   '_flowId' - the _flowId currently running.
*   '_integrationId' - the _integrationId currently running.
*   'settings' - all custom settings in scope for the import currently running.
*   'testMode' - Boolean flag that executes script only on test mode and preview/send actions.
*
* The function needs to return an array, and the length MUST match the options.data array length.
* Each element in the array represents the actions that should be taken on the record at that index.
* Each element in the array should have the following fields:
*   'data' - the modified/unmodified record that should be passed along for processing.
*   'errors' -  used to report one or more errors for the specific record.  Each error must have the following structure: {code: '', message: '', source: ‘’ }
* Returning an empty object {} for a specific record will indicate that the record should be ignored.
* Returning both 'data' and 'errors' for a specific record will indicate that the record should be processed but errors should also be logged.
* Throwing an exception will fail the entire page of records.
*/ 
function preMap(options) {
  return options.data.map((d) => {
    let counter = 1;
    d.ST.forEach((st) => {
      st['Hierarchical ID Number'] = counter;
      counter++;
      st.LX.forEach((lx) => {
        lx['Hierarchical ID Number'] = counter;
        lx['Hierarchical Shipment Parent ID Number'] = st['Hierarchical ID Number'];
        counter++;
      });
    });
    return {
      data: d
    };
  });
}

[jackharris]

Where are you putting this?

[jackharris]

Also, I get errors every time I attempt to use Celigo AI. The handlebar code especially errors out every time.

[tylerlamparter]

@jackharris it's a preMap script on the import, but you could rework it to put it on a preSavePage script on export as well.

[jackharris]

so to break your code down into pseudo-code

set a counter
if each ST segment in the record:
    set the HL ID # to the counter
    increase the counter
    for each lx segment, 
        HLID = counter
        HL Parent = the current HL ID
        increase counter    

In effect, the HL ID will continue to increase and the LX's parent will equal the previous counter. So for the sub loops, I'd just add another st.*.forEach loop?

[tylerlamparter]

@jackharris yeah if you have even deeper loops after LX you can keep nesting forEach loops and referencing parent counts.

[jackharris]

I restructured it so that I could get the right HL loops and used the AI to get code for it but I'm getting a prompt when I use the code.

Here's what I put into the AI:

Can you go through each HLS object and each HLO object and add a sequential counter called "Hierarchical ID Number". Then for each HLO object, can you add a field called "Hierarchical Shipment Parent ID Number" and the value of it will be the value of the "Hierarchical ID Number" within the ST object outside of itself

Here's the restructured sample data:

{
  "data": [
   {
  "Authorization Information Qualifier": "00",
  "Authorization Information": "",
  "Security Information Qualifier": "00",
  "Security Information": "",
  "Interchange ID Qualifier(ISA05)": "12",
  "Interchange Sender ID": "7045875587",
  "Interchange ID Qualifier(ISA07)": "12",
  "Interchange Receiver ID": "8133054539",
  "Repetition Separator": "^",
  "Interchange Control Version Number": "00501",
  "Acknowledgment Requested": "0",
  "Usage Indicator": "P",
  "Component Element Separator": ":",
  "Functional Identifier Code": "SH",
  "Application Sender's Code": "PPSF",
  "Responsible Agency Code": "X",
  "Version / Release / Industry Identifier Code": "005010",
  "BSN": {
    "Transaction Set Purpose Code": "00",
    "Shipment Identification": "2090416",
    "Date": "20240117",
    "Time": "0000",
    "Hierarchical Structure Code": "0002"
  },
  "HLS": {
    "TD5": {
      "Routing Sequence Code": "B",
      "Identification Code Qualifier": "2",
      "Identification Code": "CPU",
      "Transportation Method/Type Code": "H",
      "Routing": "CUSTOMER PICK-UP"
    },
    "REF": {
      "Reference Identification Qualifier": "",
      "Reference Identification": "263738"
    },
    "N1": [
      {
        "Entity Identifier Code": "WH",
        "Name": "Distribution Technology",
        "Identification Code Qualifier": ""
      },
      {
        "Entity Identifier Code": "DE",
        "Name": "MARIO CAMACHO FOODS",
        "Identification Code Qualifier": ""
      },
      {
        "Entity Identifier Code": "ST",
        "Name": "PROGRESSIVE FOOD SOLUTIONS LLC",
        "Identification Code Qualifier": "91",
        "Identification Code": "PRO8603006"
      }
    ],
    "HLO": {
      "PRF": {
        "Purchase Order Number": "VEGGA00000",
        "HLP": [
          {
            "REF": [
              {
                "Reference Identification Qualifier": "LT"
              }
            ],
            "MAN": {
              "Marks and Numbers Qualifier": "GM",
              "Marks and Numbers": "00007291482000252297"
            },
            "HLI": {}
          }
        ]
      }
    }
  }
}
  ],
  "files": [
    {
      "fileMeta": {
        "fileName": "sampleFileName",
        "fileSize": 1234
      }
    }
  ],
  "errors": [],
  "_exportId": "65ba560b026210086eb4e443",
  "_connectionId": "65b93733ca96162a2573ab35",
  "_flowId": "65ba560c0c45e0500aa1bfb2",
  "_integrationId": "65a6991cc89f91203021cb02",
  "pageIndex": 0,
  "settings": {
    "integration": {},
    "flowGrouping": {},
    "flow": {},
    "export": {},
    "connection": {}
  },
  "testMode": true
}

[tylerlamparter]

@jackharris your HLS segment is not an array, it's just an object. So you don't have anything to loop through there.

[jackharris]

When I turn them into [object]'s the previewed data goes away.

[tylerlamparter]

@jackharris HLO is also not an array in your sample data. I made it an array and used the prompt you gave for Celigo AI and the output looks right.

function preMap(options) {
  return options.data.map((d) => {
    let counter = 1;
    d.HLS.forEach((hls) => {
      hls['Hierarchical ID Number'] = counter;
      counter++;
      hls.HLO.forEach((hlo) => {
        hlo['Hierarchical ID Number'] = counter;
        hlo['Hierarchical Shipment Parent ID Number'] = hls['Hierarchical ID Number'];
        counter++;
      });
    });
    return {
      data: d
    };
  });
}

[jackharris]

So, if I want to add levels, I'd do it like this, yes?

Code:

function preMap(options) {
  return options.data.map((d) => {
    let counter = 1;
    d.HLS.forEach((hls) => {
      hls['Hierarchical ID Number'] = counter;
      counter++;
      hls.HLO.forEach((hlo) => {
        hlo['Hierarchical ID Number'] = counter;
        hlo['Hierarchical Shipment Parent ID Number'] = hls['Hierarchical ID Number'];
        counter++;
        hls.hlo.hlp.forEach((hlp) =>{
          hlp['Hierarchical ID Number'] = counter;
          hlp['Hierarchical Shipment Parent ID Number'] = hlo['Hierarchical ID Number'];
          couter++;
        })
      });
    });
    return {
      data: d
    };
  });
}

Test data

{
  "data": [
    {
      "Authorization Information Qualifier": "00",
      "Authorization Information": "",
      "Security Information Qualifier": "00",
      "Security Information": "",
      "Interchange ID Qualifier(ISA05)": "12",
      "Interchange Sender ID": "7045875587",
      "Interchange ID Qualifier(ISA07)": "12",
      "Interchange Receiver ID": "8133054539",
      "Repetition Separator": "^",
      "Interchange Control Version Number": "00501",
      "Acknowledgment Requested": "0",
      "Usage Indicator": "P",
      "Component Element Separator": ":",
      "Functional Identifier Code": "SH",
      "Application Sender's Code": "PPSF",
      "Responsible Agency Code": "X",
      "Version / Release / Industry Identifier Code": "005010",
      "BSN": [
        {
          "Transaction Set Purpose Code": "00",
          "Time": "0000",
          "Hierarchical Structure Code": "0002"
        }
      ],
      "HLS": [
        {
          "TD5": {
            "Routing Sequence Code": "B",
            "Identification Code Qualifier": "2"
          },
          "REF": {
            "Reference Identification Qualifier": ""
          },
          "HLO": [
            {
              "PRF": {
                "HLP": [
                  {
                    "REF": {
                      "Reference Identification Qualifier": "LT",
                      "Reference Identification": "SEP062026"
                    },
                    "MAN": {
                      "Marks and Numbers Qualifier": "GM",
                      "Marks and Numbers": "00007291482000252297"
                    },
                    "HLI": [
                      {
                        "LIN": {
                          "Assigned Identification": "000001",
                          "Product/Service ID Qualifier": "IN",
                          "Product/Service ID": "7365171058-CT"
                        },
                        "SN1": {
                          "Unit or Basis for Measurement Code": "CA"
                        }
                      }
                    ]
                  }
                ]
              }
            }
          ]
        }
      ]
    }
  ],
  "files": [
    {
      "fileMeta": {
        "fileName": "sampleFileName",
        "fileSize": 1234
      }
    }
  ],
  "errors": [],
  "_exportId": "65ba560b026210086eb4e443",
  "_connectionId": "65b93733ca96162a2573ab35",
  "_flowId": "65ba560c0c45e0500aa1bfb2",
  "_integrationId": "65a6991cc89f91203021cb02",
  "pageIndex": 0,
  "settings": {
    "integration": {},
    "flowGrouping": {},
    "flow": {},
    "export": {},
    "connection": {}
  },
  "testMode": true
}

[tylerlamparter]

@jackharris yeah it would be something like that. With each level, you may need a different counter. Like if your third level needs a reference to the second level, then you would need a second level counter as opposed to just your first level counter. Not sure if that's the case, but just calling it out.

[tylerlamparter]

@jackharris I would try to reprompt the AI with your new data structure. "d.HLS" is not a valid path because d.HLS does not exist in your data structure, but it did exist in a prior structure you shared. Your correct path for this structure would be d.ISA.GS.ST.HLS.

[jackharris]

That got it working to preview correctly, but when I try to run the test nothing goes through.