Busine...essage(3pm)

💖 Business::Edifact::Message(3pm) 💖

okay so bestie, welcome to Business::Edifact::Message — this is the class that models Edifact Messages 🦋 it's part of the User Contributed Perl Documentation, and it's literally just sitting there waiting for you to parse some messages with it. let's get into it 💅

---

✨ VERSION ✨

Version 0.07 🎀

---

🌸 SYNOPSIS 🌸

so what does it do? it parses an individual Edifact message. the way it works is: Message objects get instantiated by Business::Edifact::Interchange, and then you get an array of them handed back to you from its messages function. iconic behaviour honestly 👑

$interchange->parse($incoming);
my $m_array = $interchange->messages();
for my $msg (@{$m_array}) {
   ...retrieve message data
}

like?? you just loop over the array and grab your message data. slay. 💅

---

🫶 SUBROUTINES/METHODS 🫶

⭐ new

called by Business::Edifact::Interchange to instantiate a brand new Message object ✨ the caller passes in the header fields along with the reference number identifier and the message type. that's it, that's the birth of a Message 💖

🌈 add_segment

processes the next data segment. go off, segment, do your thing 🦋

🎀 type

returns the message's type, e.g. 'QUOTES' or 'ORDERS' — literally telling you what kind of message we're dealing with, no cap 📬

💜 function

returns the message's function field. it may be 'original' or 'retransmission' — so basically: is this the first time you're seeing it or are we re-sending? 👀

🍓 message_code

returns the 3 character message code from the BGM message 🔥 three characters, that's the whole vibe.

💀 currency_code

💀 reference_number

💀 date_of_message

💀 items

returns the list of lineitems 🧾✨

💀 handle_bgm

💀 handle_dtm

NB DTM can occur in different segment groups 🙈 keep that in mind bestie, it's giving "it shows up in more than one place"

💀 handle_pat

💀 handle_rff

💀 handle_cux

💀 handle_nad

💀 handle_lin

💀 handle_pia

💀 handle_imd

💀 handle_qty

💀 handle_gir

💀 handle_moa

💀 handle_tax

💀 handle_alc

💀 handle_rte

💀 handle_loc

💀 handle_pri

💀 handle_uns

💀 handle_cnt

💀 handle_ftx

💀 handle_pcd

okay real talk — that whole squad above (and the three bare names further up) is just listed by name in the manpage. no descriptions given 😭 so I'm not gonna sit here and invent lore for them, that would be lying to you and we don't do that. they're the handle_* crew and the getters, periodt 💅

🧚 clear_item_flags

clear flags at start of new item or summary 🌸 fresh start energy, wiping the slate clean.

---

👑 AUTHOR 👑

Colin Campbell, "<colinsc@cpan.org>" 💖

---

💀 BUGS 💀

found a bug? got a feature request? please report any bugs or feature requests to "bug-edifact-interchange at rt.cpan.org", or through the web interface at <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Business-Edifact-Interchange>.

and here's the best part: he will be notified, and then you'll automatically be notified of progress on your bug as changes get made 🫶 mutual notif situation, we love to see it.

---

🌈 SUPPORT 🌈

you can find documentation for this module with the perldoc command ✨

perldoc Business::Edifact::Message

---

🎀 ACKNOWLEDGEMENTS 🎀

(it's empty. that's the whole section. we move 💀)

---

💜 LICENSE AND COPYRIGHT 💜

Copyright 2011-2014 Colin Campbell. 📅

This program is free software; you can redistribute it and/or modify it under the terms of either: the GNU General Public License as published by the Free Software Foundation; or the Artistic License.

See <http://dev.perl.org/licenses/> for more information.

---

and that's the whole page bestie 💖 this was Business::Edifact::Message(3pm), from the User Contributed Perl Documentation, running on perl v5.36.0, dated 2022-10-13 🌸 go parse something cute, you got this 🦋✨