General Ledger Interface Question

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf General Ledger Interface Question

  • Creator
    Topic
  • #51038
    Shaun Beckman
    Participant

    We are currently working on a General Ledger interface for Maestro. We will be reading the following file from a directory.

    0120090702GL TRANSACTIONSHH_200906PE

    05MONTHLY BATCH HH 06/2009      2009063020090630BILLING_AR

    1012345678                                        6168.12

    1013456789                     24430.37    

    1014567890                      1850.00    

    :

    :

    1015678901                                        11394.66

    99

    (Colons represent repeating lines, 99 indicates end of file)

    We need to convert it to the following format.

    FHS|^~&|MM||GL|RMC

    BHS|^~|MM||GL|RMC|||||Wed Apr 01 07:15:07

    MSH|^~&|MM||GL|RMC|||GLI^G01|1234567800000000|P|2.5

    ZJR||MM12345678900000|Issues from MAESTRO|FN|20090331|200903

    ZTX||16114600|DR|223.5580

    ZTX||11160162|CR|-363733.20

    ZTX||16113500|DR|1132.36

    ZTX||16113600|DR|1923.16

    ZTX||16775250|DR|31476.70

    ZTX||16113800|DR|132.2170

    ZTX||16513600|DR|2566.310

    :

    :

    ZTX||17376300|DR|7.0000

    ZTX||17373500|DR|8.6304

    BTS|0|GL Batch Trailer

    FTS|1|GL Issues from MAESTRO

    (Colons represent repeating segments0

    I was just looking for suggestions on how others are handling this type of issue before I start spinning my wheels.

    We are on v5.5 Rev1, RedHat es4

    Any assistance will be greatly appreciated.

Viewing 2 reply threads
  • Author
    Replies
    • #68522
      Jim Kosloskey
      Participant

      Shaun,

      I am not doing anything like this but my suggestion would be to define your inbound file as an HRL.

      Without the inbound system’s specification I am only guessing but it looks like each record is an FRL (it also looks like the first 2 characters are a record code). So at first glance your HRL would be a definition of at least 3 FRL specifications one for each of the record types. The ’10’ record type record would need to be defined as repeating. Then you can ITERATE over the repeating FRL in an Xlate

      Using the HRL concept gives you a chance to treat everything from the ’01’ record type record through the 99 record type record as  one message which you might want to do to convert it to the appropriate HL/7 message.

      email: jim.kosloskey@jim-kosloskey.com

    • #68523
      Shaun Beckman
      Participant

      Thanks Jim. I’ll give that a try.

    • #68524
      Shaun Beckman
      Participant

      I have defined the inbound variant as an HRL which includes 3 FRLs, but when I attempt to compile the xlate, I receive the following error message:


      FAILED


      [0:TEST] Unrecognized field name ‘Partial path resolution not yet implemented for HRL formats header.gl_header.[0]’

      [0:TEST] Unable to compile IN list ‘{header.gl_header.[0]}’

      [0:TEST] Unable to compile statement ‘

      { OP PATHCOPY }

         { ERR 0 }

         { IN {{header.gl_header.[0]}} }

         { OUT 0(0).FHS }

      Can someone provide some insite into the error message, or possibly post an HRL -> HL7 or FRL -> HL7 xlate that I can take a look at?

      Any assistance will be greatly appreciated.

Viewing 2 reply threads
  • The forum ‘Cloverleaf’ is closed to new topics and replies.

Forum Statistics

Registered Users
5,053
Forums
28
Topics
9,235
Replies
34,153
Topic Tags
273