4 Replies Latest reply: May 15, 2014 9:57 AM by Grant Perkins RSS

    Append line below detail

    Baldwin _

      I am using version 6.01 of Monarch. I have an EDI file that I want to capture information from and I reviewed the advice in a previous post (Dec 2003) involving that same type of EDI document. The info I want to capture always starts with a line beginning with the characters “IT1” and I have a one line trap for this line. There is other information in this file that I have been able to capture but I am having a little difficulty with the data that follows the “IT1” detail line.

       

      Here is a simplified sample. As a general rule the IT1 detail is followed by one PID line but not always.

       

      IT1   partnumber1

      PIDpart1description

      IT1   partnumber2  

      PIDpart2description

      IT1   partnumber3    

      IT1   partnumber4

      PIDpart4description

       

      In order to capture the PID data I created a 2-line append trap using “IT1” as the trap on the first line, painting the data on the 2nd line following PID as the field to be captured and defining the field to be active only if the preceding string equals “PID”.

       

      This technique works in every case except where an IT1 line is not followed by a PID line.  In that case, shown above, the data “part4description” was not only assigned to the immediately preceding IT1 line but also to the next IT1 line above that so that the “partnumber3” was assigned “part4description” when no description should have been assigned.

       

      I have gotten a lot out of reading other posts regarding capturing data with an append template for data below the detail line.  However no one seemed to have my problem and I am wondering if version 6.01 was ever capable of doing this.

       

      Monarch user since 2004

        • Append line below detail
          Data Kruncher

          Hi Baldwin.

           

          I've come up with a solution that worked in v5 Standard.

           

          I created a one line detail template, trapping the IT in column 1. I set the End Field On: Minimum action only. I defined the field as "IT Field".

           

          I then created a two line append template, again with IT in position 1 of the trap line. Once again I set the End Field On: Minimum action only option. I defined the field as "Pre PID Field".

           

          What you wind up with in the table is a PID Field for partnumber3 which includes partnumber4 and the PID description for partnumber4.

           

          Knowing that you only want the PID description when it starts the field, not part-way into it, we can take advantage of this.

           

          Build a calculated field named "PID Field" with this formula:

          [font="courier"]If(Instr("PID",[Pre PID Field])>1,"",[Pre PID Field])  /font[/quote]This will return a blank field if the PID tag isn't in the beginning of the field; meaning that it doesn't really belong to this partnumber, so you want to ignore it.

           

          If however it does start the field properly, then great, use it as extracted.

           

          While there may be more elegant way (I've certainly had better template success with v8 and v9), this worked fairly quickly. Sorry, I don't have more time at the moment to find that "perfect" solution.

           

          HTH,

          Kruncher

          • Append line below detail
            Grant Perkins

            Hi,

             

            Further to Kruncher's solution your requirement is a little similar in concept to this recent problem.

             

            [url="http://mails.datawatch.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=1;t=001712"]http://mails.datawatch.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=1;t=001712[/url]

             

            I think the concept of overlapping an append on to a detail trap, using the preceding string concept to determine whether the variably present line exists, should work for you. As far as I remember it should be possible in V6.

             

            The append detail should then appear when it appears or give you an empty field if it does not exist. But the append should always be reset by the next record and therefore not carry over to records to which it should not apply.

             

            Worth a try at least.

             

             

            HTH.

             

             

            Grant

            • Append line below detail
              Baldwin _

              Thanks for your help Kruncher and Grant. I did not follow you exactly but I saw the approach and made it work. If this is easier with a newer version however, I will upgrade just so it will be easier to teach others.

              • Append line below detail
                Grant Perkins

                Originally posted by Baldwin:

                If this is easier with a newer version however, I will upgrade just so it will be easier to teach others. /b[/quote]Glad you found a solution. There are many ways, usually, to derive what you need to derive, often all equally as good as the others.

                 

                I would always recommend the upgrades since Monarch has added functionality with every new version.

                 

                That said I don't think there is anything much to add to the basic concept of the solutions suggested. You can have more appends and footers these days but you don't seem to need them much!

                 

                However, if you are teaching others, from which I infer you will be mentoring a few more Monarch users, then V9 may offer something more useful than simplified teaching.

                 

                The V9 concept of Linked Objects might (it depends on your interoperational requirements) prove interesting for sharing operational functionality and being better able to manage models for consistency and the timeliness of any changes that may be required.

                 

                A further extension of that idea which may be valuable could be the Used Defined Functions functionality which would allow you to create a 'central' repository of 'functions' that all could share. The implication is that other users may not need to know the 'mechanics' of Monarch, rather just what operational tool they need  for their model's analysis and where to get it.

                 

                I would predict faster and more consistent model development using V9. How much faster and how much benefit is difficult to suggest without knowing your needs and likely model development volumes.

                 

                Certainly worth spending a little time investigating though.

                 

                HTH.

                 

                 

                Grant