As group folio styles are defined separately, a different bucket configuration is possible for group folios. Group codes are available for folios generated for group accounts. If you respond Yes, the folio will be printed with expenses grouped according to the codes set up here. When these codes are configured and the Cashiering>Prompt for Expense Folio Upon Checkout application parameter is set to Y, the message Do you want to print the expense folio? Yes/No will be displayed upon guest check out. When the guest folio is printed in arrangement code style, the individual postings for food and beverage are consolidated and printed as a single posting – Breakfast Charge the detail of the food and beverage component is hidden.Įxpense codes are used to generate expense folios that can summarize transactions for up to 12 expense buckets. For example, if you have configured transaction codes for breakfast food and breakfast beverage separately, you can define an arrangement code Breakfast Charge that links these together. Package Arrangement Codes ( Cashiering>Package Arrangement Codes)Īrrangement codes are a way in which to group similar transactions together and print the folio using this summarized configuration.Expense Code ( Cashiering>Prompt for Expense Folio Upon Checkout).Arrangement Code ( Cashiering>Folio Arrangements).Application parameters control availability of specific Folio Groupings options: Started with Sinopia, but there are other aspects to this.Select the Configuration>Cashiering>Folio Groupings option to define codes that will aggregate charges when printing a folio. Jakub Skoczen to add some context to this page providing insight into the motivation behind doing this.Marc Johnson to touch base with Steve Osguthorpe who might have investigated this not too long ago.The team behind Sinopia (Entity editor to become part of FOLIO)expressed a need for the minimal version of the FOLIO platform to allow their existing users to continue running Sinopia during the transition to the FOLIO platform.The activity to define "platform-minimal' is seen by some members of the TL as an activity that could kick-start this process by analysing and reorganising dependencies for the so-callled "core" set of modules It's been discussed that un undertaking to analyse and potential limit or reorganize dependencies in FOLIO should be started in FOLIO but no specific details or next steps have been agreed on. This complexity creates operational, architectural and scalability challenge for developing, shipping and running FOLIO. Both the Technical Council and various interest groups (TL, SysOps SIG, etc) discussed the complexity stemming from the fact that FOLIO consists of large and an ever-growing number of distributed but highly inter-connected modules. Ideally we can address these situations and define a "platform-minimal" that makes sense, and would allow the FOLIO platform to be used for non-LSP application development. The expectation is that we'll likely find modules which are currently required, but shouldn't be (e.g. There's interest in determining the minimal set of modules to run a bare-bones FOLIO instance. See: DR-000028 - FOLIO should define a minimal platform This decision has been migrated to the Technical Council's Decision Log as part of a consolidation effort.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |