Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support forum-datenaustausch.ch XML dunning #4703

Closed
metas-ts opened this issue Oct 26, 2018 · 1 comment
Closed

Support forum-datenaustausch.ch XML dunning #4703

metas-ts opened this issue Oct 26, 2018 · 1 comment

Comments

@metas-ts
Copy link
Member

Is this a bug or feature request?

FR
follow-up of #4621

What is the expected or desired behavior?

If we have a dunning document and the dunned invoices were exported to XML forum-datenaustausch.ch XML invoices, then create respective XML dunnings and attach them to the C_DunningDoc

@metas-ts metas-ts self-assigned this Oct 26, 2018
metas-ts added a commit that referenced this issue Oct 26, 2018
* add API and SPI analog to invoice exporting

#4703
metas-ts added a commit that referenced this issue Oct 30, 2018
* fixes during dev-tests
* different AD_Tweaks

#4703
metas-ts added a commit that referenced this issue Oct 30, 2018
@metas-ts
Copy link
Member Author

metas-ts commented Oct 30, 2018

A bit of doku:

Config

Same as in #4621; nothing changed, no new config-fields were added;
Therefore, the XML-dunnings are for now failed in the same location as the XML-invoices

Workflow

Actually, the "What is the expected or desired behavior?" text already describes it:

  • If you have an invoice with an forum-datenaustausch.ch exported XML-invoice (not the one that was attached to the C_OLCand, but the one created by metasfresh)

    • and you create a dunning doc for that invioice
    • then the system creates an async-WP to create an exported XML-dunning for the exported XML-invoice and attaches that dunning-XML to the dunning document (C_Dunning_Doc)
  • Now if you have "dunning" activated in "Ausgehende Belege" (C_Doc_OutBound_Config), metasfresh will create a C_Doc_OutBoundLog (not related to this issue) and the exported XML-dunning will be forwarded to that C_Doc_OutBoundLog. From there, you can store it, just like the exported XML-invoice in issue Support forum-datenaustausch.ch XML invoice #4621.

Note

to IT: i'm now showing the payment term in the (sales)invoice adv-edit overlay.
Can be handy if you want an invoice to be dunned now

metas-ts added a commit that referenced this issue Oct 30, 2018
#4703-app - Support forum-datenaustausch.ch XML dunning
metas-ts added a commit that referenced this issue Nov 1, 2018
make sure the dunning C_Doc_OutBound_Config is active
metas-ts added a commit that referenced this issue Nov 5, 2018
[#4690](#4690) Picking Terminal v2: filtering options
[#4691](#4691) Picking Terminal v2: if there is not enough Qty in storage create a new Products To Pick line
[#4703](#4703) Support forum-datenaustausch.ch XML dunning
[#4705](#4705) Avoid SQL N+1 in HU source queries
[#4708](#4708) webui: Change my password does not work
[#4719](#4719) Allow AD_Val_Rule to be auto-applied on new record
[#1094](metasfresh/metasfresh-webui-api-legacy#1094) Login: Show a user friendly error when user or password is empty
[#4732](#4732) Can not create a new order line using 'Add new'
[#1082](metasfresh/metasfresh-webui-api-legacy#1082) Picking from source HU not working
[#1083](metasfresh/metasfresh-webui-api-legacy#1083) QtyPicked in first window picking terminal not correct
[#2018](metasfresh/metasfresh-webui-frontend-legacy#2018) Included view: clicking on it's right side space shall not close the included view
[#2034](metasfresh/metasfresh-webui-frontend-legacy#2034) Uncaught TypeError: selected.indexOf is not a function
[#2036](metasfresh/metasfresh-webui-frontend-legacy#2036) Uncaught TypeError: Cannot read property 'length' of null at windowHandler (windowHandler.js:395)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant