cancel
Showing results for 
Search instead for 
Did you mean: 

Strange situation with clearings date for delta BW

Former Member
0 Kudos

Dear Guru

We use the standard extractors 0FI_GL_14, 0FI_AR_30, 0FI_AP_30 to account "Accounts receivable" and "Accounts payable". Since that report, we consider only open positions, hence we analyze the date alignment AUGDT. In productive ERP we encountered the same problem: the delta update procedure 0FI_GL_14 AIED. Thus, the information found on forums and help'e had such understanding - if the document is created, the record should get a table BWFI_AEDAT, which are read from the changed document titles, then ship all items from BSEG. Everything would be fine if not for adjustment is not key fields: for example clearing operation or reversal. At this point, the field BKPF-AEDAT transactionally not changed in ERP, therefore changes should not get in BWFI_AEDAT, but the data in BW come.

If we consider a specific example, but I want to note that this problem is not regular, so it is impossible to systematize the problem:

1 creates a document with empty AUGDT, AUGCP, AUGBL.
Delta says it for me and ship in BW.
After a time a document is created 2, which is a reversal of the document 1 and shall AUGDT, AUGCP, AUGBL in both documents, but only brings the delta document 2 and the amended document 1 does not work.

Dear experts, help to understand how to construct a chain of operations since inception to the end-1 document display in reporting document 2. Just wanted to you to share the experience in other companies analyzed open \ closed position papers if SAP'a recommendations to update the field BKPF-AEDAT following:

Calendar day on which the last document change was made using a document change function.
Document changes resulting from other processing, for example, clearing, dunning or payment, are not taken into consideration.

PS: I have presented only a very simple example, the same problems occur operation UnJustify \ reversal in previous periods (reason 03, 04).

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Albert,

Did you get a solution to the problem.

I am having similar issue. When a document status changes from open to closed, the delta is not picking that for extractor 0FI_AR_30.

Thanks,

Shilpa

Former Member
0 Kudos

Sorry, solution in Russian lang, Please repeat yourself

Решение:

1) Init Delta без переноса данных, затем FULL загрузка.

2) Init Delta с переносом данных, затем FULL загрузка.

3) Init Delta с переносом данных, когда в ERP системе никто не работает и нет рисков, что дельта-очередь изменится.

  1. P.S.: Данная не консистенция происходит, из-за того, что во время Init Delta попадают в дельта-очередь документы. Можно проверить очень просто:

время выполнения Job на стороне ERP 0FI_AR_30 (с и по). Идем таблицу BKPF_AEDAT и делаем выборку по значению AEDAT в этих временных рамках.

Former Member
0 Kudos

Albert,

Any update on how you got the reversed documents to be picked by delta. Any OSS message??

Thanks,
Voodi