metasfresh/metasfresh-dist-orgs

metasfresh-dist-orgs's Issues

Tidy C_BPartner, delete city, address1, Postal, eMail

Belongs to metasfresh/metasfresh#2483
The columns C_BPartner.city, C_BPartner.address1, C_BPartner.postal, C_BPartner.eMail are now in metasfresh-app and shall be taken out of metasfresh-dist-orgs.

Dist Org Script Problems with metasfresh 5.28

psql:/opt/metasfresh/dist/sql/src/main/sql/postgresql/system/90-de.metas.vertical.orgs/5456790_cli_gh987_flatrate_condition_product_partner.sql:4: ERROR: column "isnewtermcreatesorder" of relation "c_flatrate_conditions" does not exist LINE 1: ...ng,IsCreateNoInvoice,IsFreeOfCharge,IsManualPrice,IsNewTermC...

role Verband does not show seminar window

Setup PDF Druck

Invoice Medium ESR and other Adjustments

set default value for field businesspartner group to "member"

Use dedicated template-DB to check SQL migration scripts

we have a problem applying migration scripts from 90-de.metas.vertical.orgs to the standard template DB.
That's because there are old scripts doing insert c_flatrate_conditions etc and we recently removed a bunch of legacy columns.
So as of now the template DB does not have those columns anymore..therefore those older dist-org scripts can't be applied to the template DB anymore.

I'm fixing the SQL to work with our current single template DB.
Rolling dist-org out production to "old" DBs won't be a problem either because on a normal rollout the insert c_flatrate_conditions etc is done before the legacy columns are dropped (either that or they were already applied long time ago).

buut:

1. do we want to go through the pain of manually fixing the 90-de.metas.vertical.orgs migration SQLs whenever a thing like this happens? e.g. we might in future remove some legacy shit from AD_Column, and then inserts into AD_Column might fail..
2. or do we want to maintain one template-DB for dist and another one for dist-orgs
3. or do we want to include the dist-orgs stuff in our "normal" dist..and switch it off, for e.g. spavetti.

my two cents:

• forget 1... apart from such a one-timer, fiddling with old sqls that are live on some DBs out there is a nightmare
• is doable (by @julian.bischof ) imho the best way to go
• three (feature-toggles etc) is the most interesting and future-proof approach, but today we imho don't have the time or pressure to give it sufficiently high prio
  wdyt?

Add flatrate condition name to invoice orgs medium jasper

1. add field printname to c_flatrate_condition
2. show printname together with product here:

caution:

1. support line breaks
2. play with the field size

add dunning and payment to dist org menu tree

activate role webui

activate role to have full access to all metasfresh windows
update ad_role set isactive ='Y' where ad_role_id = 540024;

Terminierte Adressänderung kann nicht erfasst werden

Die terminierte Adressänderung kann nicht erfasst werden, da die Felder zum eintragen des gültig bis und der neuen Adresse fehlen.

Testfall:

1. Öffnen Fenster Geschäftspartner Dist-Orgs
2. Partner auswählen und mit Doppelkick öffnen
3. Tab Adresse auswählen
4. Butteon Neu hinzufügen klicken
5. Neue Adresse erfassen
6. NOK Gültig bis und neue Adresse eintragen

Erwartung:
Felder für Gültig bis und neue Adresse können über das Advanced Edit in der alten Adresse eingetragen werden.

add email address of default contact to partner window

use product printing format for different cases for selecting invoice document

cases:

1. invoice line without flatrate term (e.g. selling a book) shall have doctype A and jasper report 1
2. invoice line with flatrate term but price > 0 (e.g. paid membership) shall have doctype B and jasper report 2
   • price > 0 can be determined by flatrate_condition.isfree = N
3. invoice line with flatrate term but price = 0 (e.g. free membership) shall have doctype C and jasper report 3
   • price = 0 can be determined by flatrate_condition.isfree = Y

• general - never mix cases in an invoice
• general - combinations can occur. e.g. case 2 + 3 shall have the same doctype or e.g. the same report

one way is to disable consolidated invoicing plus putting lots of logic into the jasper BUT
it would be better to do it generically so we can configure it by system and org somehow

questions:

1. do we have ways to set the target doctype somehow by invoicecandidate ?
2. can invoice aggregation header help use with this as its already calculating the case in a way?
3. what other criterias might exist to determine the case? e.g. product, contract condition, etc.

Invoice Medium Address Layout Changes

make the address field match the window layout

Have a direct relation between order and invoice candidate

Sammlung ToDos

hide fields document no and doctype from order window

Invoice Medium Preview working in Jasper but not on server

address fields are gone from grid tab in partner window

create different doctypes for different invoice variations

Create default import format for flatrate terms

based on metasfresh/metasfresh#2224

create newspaper export based on shipments

create dist orgs Invoice Document

add contract duration to invoice document

idea:

1. copy invoice from metasfresh into dist-orgs
2. add flatrate term start and enddate

Postal Lookup for Switzerland CH

How to activate postal lookup for Switzerland?

1. import postal and region data
2. create postal records from migration data
3. link existing addresses by postal and city to postal list
4. activate postal lookup
5. do a server cache reset

create prototype for address termination

add fields next address and validto

Extend default search fields in businesspartner window

Activate ESR on default config

Adapt KPI Dashboard

Add Import Format for standard Partnerimport

Fix Jasper Version of Invoice Medium

1. report looks fine in jasper studio but not when used on system:

2. use the subreport report_esr.jrxml for esr part

Refactor Migration Scripts for dist orgs

remove scrips for:

1. functional data e.g. products
2. partner window as we do have partner dist-orgs window now
3. multi org because its not needed by default

add Berichts-Präfix to org_info

Add Berichts-Präfix file:////opt/metasfresh/reports to orgs Sektion 1 and Sektion 2

create letter report

change default languages

disable en_US, NL
enable fr_CH, it_CH

Move import Format to client

import formats are on system by default
moving them to client makes them editable

add function for dist-orgs subreports

Switch to separate business partner window

instead of changing business partner window we should either use B2C Cockpit or create a separate window just for dist-orgs to be independent from further window changes

add trainings management

Show product logo on invoice report jasper

add request to orgs menu tree

move flatratecondition to client level so all orgs can access it

Have an integrated way to see and maintain subscriptions

Currently subscriptions are displayed in the dist-orgs bp window as subtab.
as we show flatrate terms we need to think about:

1. how do we make sure to only show the current flatrate terms ?
2. As flatrate terms are just one period of a contract how does the user know when the contract started in general?
3. How can the user manipulate the contract without the need to change each line?

Ideas:
Have a tree in subtab subscription in partner window showing flatrate term data on top node which contains additional info like startdate, enddate, contractstatus of the contract in general.
Below we show the either all flatrate terms sorted descending to have the latest on top and grouped by term (e.g. year) or alternatively only the current flatrate terms
User can then apply actions on nodes like terminate entire contract, change the qty of a line, change the member for all lines or just for one, etc.

Add medium_lettertype invoice report

Add medium invoice report