CURRENCY POSITION

  • namco
  • Topic Author
  • Visitor
  • Visitor
14 years 3 months ago #6844 by namco
CURRENCY POSITION was created by namco
T24 R09
Jbase

Hi Guys

What causes POSITION RECORD DISCREPANCY BETWEEN AMOUNTS AND DATES

Please Log in or Create an account to join the conversation.

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
14 years 3 months ago #6848 by jpb
Replied by jpb on topic Re: CURRENCY POSITION
Can you put a little flesh on the bones?

Please Log in or Create an account to join the conversation.

  • namco
  • Topic Author
  • Visitor
  • Visitor
14 years 3 months ago #6851 by namco
Replied by namco on topic Re: CURRENCY POSITION
This is an eb.eod.error we keep getting. And i want to know what causes them and how to correct

EB.EOD.ERROR.ID... ZW0010001.20110301
1. 1 TIME.DATE...... 21:47:24 01 MAR 2011
2. 1. 1 DESCRIPTION. POSITION RECORD DISCREPANCY BETWEEN AMOUNTS AND DATES
3. 1 APPLICATION.ID. POSITION
4. 1 ROUTINE........ (EOD.FCY.POS)
5. 1. 1 RECORD.KEY.. ZW00100011TR01USDZAR20110228
6. 1. 1 DETAIL.KEY.. 157660002778444.30
8. 1 FIX.REQUIRED... NO
1. 2 TIME.DATE...... 21:47:24 01 MAR 2011

Please Log in or Create an account to join the conversation.

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
14 years 3 months ago #6855 by jpb
Replied by jpb on topic Re: CURRENCY POSITION
I fear the cause can be in any transaction that builds the POSITION.

To correct it I believe it's best to contact CSHD as you have to manipulate the POSITION backdoor (it will cost you a lot of records to be send).

The reported error is a mismatch between AMOUNT-fields and SD.AMOUNT-fields in ZW00100011TR01USDZARyyyymmdd.

Please Log in or Create an account to join the conversation.

More
14 years 3 months ago - 14 years 3 months ago #6909 by DUBLIN
Replied by DUBLIN on topic Re: CURRENCY POSITION

T24 R09
Jbase

Hi Guys

What causes POSITION RECORD DISCREPANCY BETWEEN AMOUNTS AND DATES


It tells you that amounts in fields AMOUNT.1 , AMOUNT.2 & LCY.AMOUNT are not equal to the sum of each correspondig mv fields SD.AMOUNT.1,SD.AMOUNT.2 & SD.LCY.AMOUNT i.e.

AMOUNT.1 = SUM(SD.AMOUNT.1)
AMOUNT.2 = SUM(SD.AMOUNT.2)
LCY.AMOUNT = SUM(SD.LCY.AMOUNT)

If one of above statements is FALSE then it's an error.

NB. Sorry, didn't see jpb's post.

If it just happend you probably could analyse a POS.MVMT.LWORK.DAY otherwice - POS.MVMT.HIST.

May be it will brging some light on ...

Good Luck
Last edit: 14 years 3 months ago by DUBLIN.

Please Log in or Create an account to join the conversation.

Time to create page: 0.040 seconds