Skip to main content

Vote (0) Share
's profile image

on

Comments (0)
's profile image Profile Picture

74596956 467e-ea11-a812-000d3a8faea9 on 14 Sep 2020 16:05:58

RE:

essential fix

's profile image Profile Picture

74596956 467e-ea11-a812-000d3a8faea9 on 14 Sep 2020 16:05:49

RE:

essential fix

's profile image Profile Picture

74596956 467e-ea11-a812-000d3a8faea9 on 14 Sep 2020 16:05:34

RE:

essential fix

's profile image Profile Picture

74596956 467e-ea11-a812-000d3a8faea9 on 14 Sep 2020 16:05:26

RE:

essential fix

's profile image Profile Picture

74596956 467e-ea11-a812-000d3a8faea9 on 14 Sep 2020 16:05:17

RE:

Essential fix

's profile image Profile Picture

348b23ca 6f4e-4f9b-85d8-5560f70497fa on 14 Sep 2020 15:49:09

RE:

I really hope, we will get this eventually. It's already been more than 5 years

's profile image Profile Picture

0d35a2b4 95f6-ea11-a815-000d3a8b3802 on 14 Sep 2020 15:44:23

RE:

That is very good idea. After few months we have many jobs which should not be used now but there is no way how to retire them.

's profile image Profile Picture

0d35a2b4 95f6-ea11-a815-000d3a8b3802 on 14 Sep 2020 15:42:24

RE:

Hi, that cause also problem with integration of inactive position. When you retire a position, activation field in JobPosition in CDS is empty (as HR workers retire positions after the retirement day). Then 1. there are errors "activation field must be field" 2. position is not retired in FO. Thanks a lot.

's profile image Profile Picture

46cb939b 9df6-ea11-a815-000d3a579c38 on 14 Sep 2020 15:20:50

RE:

Many customers complain because the subtotals and totals don't export from a table / matrix. This needs to be addressed.

's profile image Profile Picture

5b540303 8c72-ea11-a811-000d3a579c38 on 14 Sep 2020 14:21:23

RE:

We achieved this with a customization in a customer project. The idea was that Purchase orders created from a Planned purchase order receive the status "Draft". Thereby, it is possible to use the standard Purchase order workflow.

In the further ongoing of the project, we implemented a Purchasing policy that defines which field of a Purchase order need a re-approval if changed.

Thereby, we were confronted with the following issue: the system does not evaluate Purchase orders created from Planned purchase orders as changed. Therefore, Purchase orders created from Planned purchase orders are automatically approved.

We set up the Purchasing policy in a way that if e.g. the total amount of the Purchase order changes, a re-approval is required. When creating a new Purchase order manually, you enter an item with a price and therefore, the total amount is "changed" - PO runs through the workflow.

But if you create the PO from the Planned PO, the system does not evaluate the amount as changed - therefore, the re-approval rule is not triggered and the Purchase order runs through the automatic approval (depends on the setup of the workflow).

So far, we did not solve this issue - but simply giving the status "Draft" to Purchase orders created from Planned Purchase orders does not fulfill the whole requirement.