Scribd
Upload
47 views2 pages

Notepad

The document discusses fixing an issue with invoices posting incorrect amounts and then addressing historical incorrect invoices. It requests the customer to test the fix by invoicing with different tax and currency scenarios. It also notes there were approximately 15 incorrect invoices in one system and 7 in another and requests the customer open a new incident to allow identifying and correcting the historical invoices.

Uploaded by

arunsuresh.dextrous
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
47 views2 pages

Notepad

The document discusses fixing an issue with invoices posting incorrect amounts and then addressing historical incorrect invoices. It requests the customer to test the fix by invoicing with different tax and currency scenarios. It also notes there were approximately 15 incorrect invoices in one system and 7 in another and requests the customer open a new incident to allow identifying and correcting the historical invoices.

Uploaded by

arunsuresh.dextrous
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

5536

@Feature: 'MM_PUR_OA_CON_HEIR_ITEM'
@ObjectModel: { readOnly: true }
@UI.hidden: true
cast ('X' as boolean) as temp_SrvcProcmtItmHierIsEnbld,

@ObjectModel: { readOnly: true }


@UI.hidden: true
SrvcProcmtItmHierIsEnbld = stemp_SrvcProcmtItmHierIsEnbld

Part 1: Fix the issue so that all future invoices will be correct
>> Inform the customers immediately to test the fix for all the test cases
>> New incident

Part 2: Fix the historical invoices:

Pre-requisite:
Request customer for a new incident in their productive system
with required authorization to view the table + invoices

Options on the table for now:


Option A: Ask Google to speak with their suppliers to cancel and rebook
the invoices once again
Option B: Ask Google to cancel the errorneous invoice and rebook, that
triggers a CC_Invoice
Variants:
Invoices booked and payments NOT made yet
Invoices booked and payments already made

Dear Customer,

Good News! We have deployed the fix in both of your P system and Q system with this
all of the forthcoming
invoices will be posted with the right amount.

We would request you to test the following cases:

1. Invoices with tax jurisdiction active and tax jurisdiction inactive.


2. Invoices with header level tax and Invoices with item level taxes (eg: item1 10%
and item2 20%).
3. For currencies TWD which has 0 decimals, EUR/USD which has 2 decimals and BHD
which has 3 decimals.

With the above, we will ensure that the solution covers all corner cases.

Next step:

We have observed that approximately 15 invoices from your P system and 7 invoices
from your Q system are posted
with currencies that have decimals that are not equal to 2.

Note: We are only able to see the count but not any of your data.

Therefore, Inorder to get an summary/further details of these errorneous invoices


we would like you to create
a new incident for your P system, with which we will be able to detect the
errorneous ones.

after detection, we would come up with the plan to do a cleanup, the whats and
hows, we would discuss
in the new incident which you will create.

Thank you for your understand and patients.

We will close this incident and continue with the new incident for the cleanup.

Best Regards,
Arun Suresh

CCCCCCCCCCCCCCCCCCCCgues,

You might also like