Change of VAT rate on contracts before activation

For this purpose, a bulk task is added to the system Convert VAT Rate in Contracts before Activation (API Change VAT Group Bef. Act. (78000)). This task ensures the exchange of VAT posting groups on contracts/calculations in the state before activation. This modification takes place without the use of change copies directly on the originals of these contracts/calculations.

Button Convert Contracts before Activation The job run is added to the page VAT Rate Change Setup (550).This new task builds on the logic of the task API Serv. Changes Bef. Activ. (4026639).

Request Form

When the task starts, a dialog box opens Convert VAT Rate in Contracts before Activation To specify the performed task or contracts:

In the section "Options" are the fields:

• Contract Change Type

  • The user selects the contract change type code, which will then be written to the Contract Change History (Change Code field)

  • mandatory, see Checks after the job has started

  • lookup to API Contract Change Type (4046856)/API Contract Change Types (4046856, List) filter-tipped:

    • Object ID wizard (15)=empty (i.e. we do not allow to select a change that is triggered by the wizard)

• Contract Change Reason

  • the user selects the reason code for the contract change, which will then be written to the Contract Change History (Reason Code field)

  • lookup to API Contract Change Reason (4046857)/API Contract Change Reasons (4046857, List)

• Comment

  • empty by default

  • the user adds a text note, which is then written by the task into the Contract Change History (Comment field).

In the section "Filter: Financing Contract Header" are the filters:

User filters are all empty by default

• Financing Product Type Code

• Financing Product No.

• Customer No.

• No. (Contract No.)

• Migrated Contract

• additional filters can be added by the user via the + button (e.g. Fin. Template No., Status, Detailed Contract Status, etc.). If the user wants to filter to Status, he must also take into account the fixed filter for Status.

The fixed filter is:

• Status<Active

Job Process

After starting the task with the "OK" or "Schedule" button, the system executes:

• Check if the Contract Change Type is filled in

  • If it is not filled in, it displays an error message and does not continue:

    • Contract Change Type must be entered. EN: Contract change type must be entered.

  • If they are filled in, it continues

• Filters contracts according to user filters in the Options section (if they are empty, it is not filtered) and to the Status<Active fixed filter

   

• The task will convert VAT posting groups rates according to the settings in the table VAT Rate Change Conversion (551)in the following areas, but only if the relevant posting group is in the target fields are not empty.

• Subsequently, the task writes a new VAT product posting group according to the observed value in the fieldTo Code (3, Code[20])from the conversion table to these fields by making the change only in those fields in the that matches the value in the conversion table in the From Code (2, Code[20], PK. The task works in a cycle and in this way it checks all the set rows.

• Then it proceeds to recalculate the contract according to the contract flag

  • if Complete Calculation (4047060)="NO":

    • the recalculation executes the formula, i.e. calls the functions under the Payment Calculation button

  • if Complete Calculation (4047060)="YES":

    • recalculate and deploy the contract payment calendar with the launch of the financial calculator (so-called calculation or recalculation - if something has already been posted in the GAC of the contract).

• If the task is run without a scheduler, the user will see an information window at the end of the processing with the number of processed contracts and the option to open the Contract Change Log.

Write to the history of changes

• Creates an entry in the contract change history API Contract Change History (4046858) without creating a change copy, but some values are added to the record from the request page:

  • Contract Change Process = Change Copy (must be filled in, cannot remain empty)

  • Change Type Code = Contract Change Type z request form

  • Approved By = ID of the user who runs the task

  • Approval Date = System Work Date

  • Change Reason Code = Contract Change Reason z request form

  • Change Valid From = system work date

  • Change Date = Expected Handover Date

  • Comment = Comment from request form

  • Closed(15)=Y

• Creates an entry in the Contract Change Log with the result Result= "Success".

• Continues to the next contract.

Displayed messages

If the task was started manually by pressing the "OK" button:

• Displays a message during contract processing Working on it... Contract ....

• When finished, it will display a message "The change has been made to X contract(s). There was an error in the Y contract(s)."

If the task was started via "Schedule", these messages are suppressed.

Starting a task via the job queue, the Schedule... button, the Contract Change Queue and the Contract Change Log are described in PD https://iao.atlassian.net/wiki/x/jADVAQhttps://iao.atlassian.net/wiki/x/nADVAQ https://iao.atlassian.net/wiki/x/wADWAQ.