FI改变日志表:bwfi_aedat
the bwom timseatmp table keeps the histroy of the timestamps - this gets updated when the load is successful and the last timsetamp used is marked in the last timsetamp field with an X- thus allowing reruns if drastic problems occue (ie by sm31 the table and moving the X to a load you wish to rerun)
时戳转换函数:RKE_TIMESTAMP_CONVERT_OUTPUT Finance documents get created - cpudt updated
But then during the course of their life they can be changed (ie cleared, paid etc..) - hence BWFI_AEDAT gets updated
So the extractor delivers new records and changed records - hence the need for a DSO to resolve the changed duplicates (FI extractors deliver after images unfortunately)
The reason for this table is that the AEDAT in BKPF cant be trusted for this purpose
The BWFI_AEDAT gets flushed based on a parameter in BWOM_SETTINGS - of the top of my head i cant rememebr which one - but the default is 60 days
So at the end of the extractor it goes and deletes from the BWFI_AEDAT table based on this parameter
But as always best explained by an example..
cpudat 12/1/2008 document 101 created Document no value Text 101 £1000 Simon
That night the extractor will extract document 101 based on the cpudate if the transaction falling between the timestamps of low and high (ie with the low and high dependant on when it was taken last and the safetys etc...) Nothign exists on BWFI_AEDAT
The record goes to the DSO
Document no value Text 101 £1000 Simon
And then into the cube
Document no value Text 101 £1000 Simon
Then two days later we change the document text to \"Dave\"
A record ends up on BWFI_AEDAT
Change date Document no 14/1/2008 101
and this record comes down the line
Document no value Text 101 £1000 Dave
This record goes and overwrites the DSO record after activation the changelog logs like
Document no value Text 101 ( £1000) Simon 101 £1000 Dave
And thus in the cube you see after loading
Document no value Text 101 ( £1000) Simon 101 £1000 Simon 101 £1000 Dave
And after zero elmination and compression you get
Document no value Text 101 £1000 Dave
全局设置:BWOM_SETTINGS
参考代码:
loop per package size
read from bkpf for cpudt between timestamps read from bseg for those records
read from bwfi_aedat for changed date between timestamps read from bkpf/bseg for those records call BTE 00050201 for any user exit mods send package to rfc scheduler endloop package
Definition: in-period
Payroll (PY)
The payroll period (start and end date of a period) in which a payroll result is created. Return ->
Definition: in-period
Definition: for-period
Payroll (PY)
The Payroll period (start and end date of a period) for which a payroll result is created. Return ->
Definition: for-period
因篇幅问题不能全部显示,请点此查看更多更全内容