• Login
    • Stedi.com

    Amazon dropship 850 relies on order of MSG segments to determine variant

    General
    2
    5
    178
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dkanter last edited by

      In looking at the Amazon Dropship 850 EDI spec, there are two MSG segments listed in the PO1 loop (position 289). The first MSG is Item Description
      CleanShot 2023-03-20 at 11.41.20@2x.png

      And the second MSG is Gift Message

      CleanShot 2023-03-20 at 11.41.29@2x.png

      When building a guide, we cannot create a variant because there is no qualifier present. To my knowledge, sequence of repeating segments cannot/should not be relied on to interpret an X12 EDI file.

      Does anyone recommend a different approach in Stedi Guides other than a single MSG segment with usage notes indicating how this is used?

      R 1 Reply Last reply Reply Quote 0
      • R
        ross @dkanter last edited by

        @dkanter use the advanced section of the segment indicator to change the position of the segments so that one segment is read/written first.

        D 1 Reply Last reply Reply Quote 0
        • D
          dkanter @ross last edited by

          @ross The issue here is that you cannot duplicate the MSG segment since we only use the MSG-01. The MSG-02 is technically a ID type, but you cannot use them to create a variant and then delete them without seeing an error in the guide UI.

          CleanShot 2023-03-20 at 12.05.29@2x.png

          R 1 Reply Last reply Reply Quote 0
          • R
            ross @dkanter last edited by ross

            @dkanter Here are the specific steps

            1. Mark the MSG segment as required
            2. For MSG-01, Set an "Allowed code" to any value (this is temporary). This turns MSG-01 into an ID type that can be used as a discriminator to create a variant.
            3. You can now duplicate MSG
            4. Create any new value for the Duplicated MSG-01 Code
            5. Modify one of the MSG segment's sequence number in the segment advanced second.
            6. The two MSG segments are no longer considered variants.
            7. You can now remove the allowed values for each MSG-01 element.
            D 1 Reply Last reply Reply Quote 1
            • D
              dkanter @ross last edited by

              @ross - this was super helpful. One thing I noticed that you need to do as well is mark the first variant to not be repeated, as otherwise the parser will make only pick up the first key and have multiple objects inside of it.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Powered by NodeBB | Contributors