Inscripción
Páginas: 2 (377 palabras)
Publicado: 23 de abril de 2011
Summary regarding issues 1, 2 and 3.
1. Exchange rate problem
Description: In some transactions the exchange rate is incorrect and the exchange rate values are out of bounds of the expectedvariation range.
Solution: A trigger and table were created and generated for the purpose of auditing the exchange rate data sent from PS, in case this rarely occurring problem shows up again.2. The PO changes its value.
Description: After saving the PO the rate of change and TotalCost values change.
Solution: As already commented, to solve this problem we went back to the originalproblem (product defect) and implemented a workaround using java classes to obtain the exchange rate directly from the PO under the following circumstances:
The PO10 field from the PO was used as aflag to see if the exchange rate needs to be recalculated.
1. If (Exchange rate is NULL OR value has not been FLAGGED [PO10==0] )
Then
Recalculate the exchange rate using the current date.
SETEXCHANGEDATE to current date.
2. IF(New State of PO is distinct from [WAPPR o synonym ])
THEN
FLAG [PO10->1]
In other words, the change is triggered if the exchange rate is NULL (This canoccur when the PO is generated from a RFQ) also when PO10 has not been flagged. Initially the field PO10 is equal to 0. PO10 is flagged to 1 when a PO changes to a different state other than waitingfor approval, therefore from this state and onwards the exchange rate is not calculated.
3.- Cost error in some returned items.
Description: In some transactions, the cost is not being calculatedproperly
Problem: The bug is reproduced in a special situation in PO returns, where the loaded cost field is not being calculated correctly due to the lack of a minus sign in the tax field of thesame line. (Points 4 and 5)
The solution was to implement a customized java class to correct the issue what it does is the following:
Writes the correct sign for the tax field according the...
1. Exchange rate problem
Description: In some transactions the exchange rate is incorrect and the exchange rate values are out of bounds of the expectedvariation range.
Solution: A trigger and table were created and generated for the purpose of auditing the exchange rate data sent from PS, in case this rarely occurring problem shows up again.2. The PO changes its value.
Description: After saving the PO the rate of change and TotalCost values change.
Solution: As already commented, to solve this problem we went back to the originalproblem (product defect) and implemented a workaround using java classes to obtain the exchange rate directly from the PO under the following circumstances:
The PO10 field from the PO was used as aflag to see if the exchange rate needs to be recalculated.
1. If (Exchange rate is NULL OR value has not been FLAGGED [PO10==0] )
Then
Recalculate the exchange rate using the current date.
SETEXCHANGEDATE to current date.
2. IF(New State of PO is distinct from [WAPPR o synonym ])
THEN
FLAG [PO10->1]
In other words, the change is triggered if the exchange rate is NULL (This canoccur when the PO is generated from a RFQ) also when PO10 has not been flagged. Initially the field PO10 is equal to 0. PO10 is flagged to 1 when a PO changes to a different state other than waitingfor approval, therefore from this state and onwards the exchange rate is not calculated.
3.- Cost error in some returned items.
Description: In some transactions, the cost is not being calculatedproperly
Problem: The bug is reproduced in a special situation in PO returns, where the loaded cost field is not being calculated correctly due to the lack of a minus sign in the tax field of thesame line. (Points 4 and 5)
The solution was to implement a customized java class to correct the issue what it does is the following:
Writes the correct sign for the tax field according the...
Leer documento completo
Regístrate para leer el documento completo.