0FI_AR_4 & SPECIFICALLY BWFI_AEDAT

Hi All,
I have read so much about 0Fi_ar_4,but 1 doubt still prevails.
A few information:
1.0Fi_ar_4 extractor in my project is still not minute based.
2.The extraction takes place after 2 GMT.Loading is always once a day.
Confusion:
I have understood that,when the I run the load suppose at 3GMT (6.12.2007),the function module of the datasource 0fi_ar_4,gets data from the table BWFI_AEDAT & sends it to BW.
But when I check the table BWFI_AEDAT with selection (after the load is completed):
changed on : 5.12.2007....
I get the number of records = 80000
& the number of records extracted in the corresponding ODS = 99000.
Can any one explain me why do I get this difference.
I want to thank chetan Patel,as I am following his answers regularly & that has clarified a lot of doubts.

Hi Guys,
Can anyone please clarify me.....Or atleast tell me if my understanding is wrong....
Regards
Kishore

Similar Messages

0FI_AR_4 delta problem

We have recently implemented the 0FI_AR_4 extract of AR customer items into BW in conjunction with some of the Collections Management targets. This appeared to be working well and was giving the data we expected. However, after we started loading in Production, we realized that items that were being cleared after the initialization were still being reflected as Open in the BW datastore/cube. In looking at the delta updates, we see the clearing document itself but no records affecting marking the old Open items with a Cleared status/date/etc.
After reinitializing the targets, the affected data looks correct again and the items are marked as Cleared. We get Delta updates nightly but it just doesn't appear to be everything we expect. I have looked at some old notes in this area discussing 0FI_GL_4 and possible dependencies or need to decouple them. We are on SAP ECC 6.0 - 7.0SP14 and BW 7.0 SP21. Could anyone elaborate on if there would still be any need to also load 0FI_GL_4 to get 0FI_AR_4 deltas to work? Or if there is anything I should specifically look for in this area before opening up a message with OSS? For now, I was just going to have reinitialize it periodically to be safe.
Thanks in advance for any assistance you can provide on this...

Abby, we did some more research on exactly how the deltas worked with this extract in our environment. Ultimately we didn't change anything -- I think it was more in just figuring out what timeframes were being pulled so we could understand differences in balances between R3 and BW at a given point. There are other tables involved beyond just BSID and BSAD. Such as BWFI_AEDAT that holds pointers to changed records in BSID/BSAD, since those tables don't have a 'change' date in all instances to work from with deltas. There was also a table called BWOM2_TIMEST that holds delta upper limit timestamp info for each 0FI_AR_4 load and it behaves based on settings in BWOM_SETTINGS. It controlled the time periods involved in each daily load (i.e. in our case, it went from 10 pm to 10 pm), so that was also part of the reason we were 'missing' records. We didn't realize that a load running at 5 am one morning was only pulling records up to 10 pm the preceding night. Once we felt better about the completeness of the records coming into BW, we no longer pursued it.
This extract is by design a daily load. But there are some notes out there about doing additional configuration to set up 'minute based' extraction and be able to run it multiple times in a day. Fortunately we didn't have to look further into it. Also, the 'coupling' between 0FI_GL_4 and 0FI_AR_4 were no longer a requirement in our version, so apparently that was never part of the issue either.
Hope that helps you. Good luck...

0FI_AR_4 Datasource, Delta

Hi Experts,
we are using 0FI_AR_4 datasource, this is delta enable, but the problem is we can run delta just once a day.
Can any one please let me know how to change this so that i can run the delta more than once a day.
Any document or a link would be of great help.
Thanks in advance.
Ananth

hi Ananth,
take a look Note 991429 - Minute Based extraction enhancement for 0FI_*_4 extractors
https://websmp203.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=991429&_NLANG=E
Symptom
You would like to implement a 'minute based' extraction logic for the data sources 0FI_GL_4, 0FI_AR_4 and 0FI_AP_4.
Currently the extraction logic allows only for an extraction once per day without overlap.
Other terms
general ledger 0FI_GL_4 0FI_AP_4 0FI_AR_4 extraction performance
Reason and Prerequisites
1. There is huge volume of data to be extracted on a daily basis from FI to BW and this requires lot of time.
2. You would like to extract the data at a more frequent intervals in a day like 3-4 times in a day - without extracting all the data that you have already extracted on that day.
In situations where there is a huge volume of data to be extracted, a lot of time is taken up when extracting on a daily basis. Minute based extraction would enable the extraction to be split into convenient intervals and can be run multiple times during a day. By doing so, the amount of data in each extraction would be reduced and hence the extraction can be done more effectively. This should also reduce the risk of extractor failures caused because of huge data in the system.
Solution
Implement the relevant source code changes and follow the instructions in order to enable minute based extraction logic for the extraction of GL data. The applicable data sources are:
                        0FI_GL_4
                        0FI_AR_4
                        0FI_AP_4
All changes below have to be implemented first in a standard test system. The new extractor logic must be tested very carefully before it can be used in a production environment. Test cases must include all relevant processes that would be used/carried in the normal course of extraction.
Manual changes are to be carried out before the source code changes in the correction instructions of this note.
1. Manual changes
a) Add the following parameters to the table BWOM_SETTINGS
                         MANDT OLTPSOURCE    PARAM_NAME          PARAM_VALUE
                         XXX                  BWFINEXT
                         XXX                  BWFINSAF            3600
              Note: XXX refers to the specific client(like 300) under use/test.
              This can be achieved using using transaction 'SE16' for table
                         'BWOM_SETTINGS'
                          Menue --> Table Entry --> Create
                          --> Add the above two parameters one after another
b) To the views BKPF_BSAD, BKPF_BSAK, BKPF_BSID, BKPF_BSIK
                       under the view fields add the below field,
                       View Field Table    Field      Data Element DType Length
                       CPUTM       BKPF    CPUTM          CPUTM      TIMS   6
                       This can be achieved using transaction 'SE11' for views
                       BKPF_BSAD, BKPF_BSAK , BKPF_BSID , BKPF_BSIK (one after another)
                           --> Change --> View Fields
                           --> Add the above mentioned field with exact details
c) For the table BWFI_AEDAT index-1 for extractors
                       add the field AETIM (apart from the existing MANDT, BUKRS, and AEDAT)
                       and activate this Non Unique index on all database systems (or at least on the database under use).
                       This can achived using transaction 'SE11' for table 'BWFI_AEDAT'
                           --> Display --> Indexes --> Index-1 For extractors
                           --> Change
                           --> Add the field AETIM to the last position (after AEDAT field )
                           --> Activate the index on database
2. Implement the source code changes as in the note correction instructions.
3. After implementing the source code changes using SNOTE instruction ,add the following parameters to respective function modules and activate.
a) Function Module: BWFIT_GET_TIMESTAMPS
                    1. Export Parameter
                    a. Parameter Name : E_TIME_LOW
                    b. Type Spec       : LIKE
                    c. Associated Type : BKPF-CPUTM
                    d. Pass Value      : Ticked/checked (yes)
                    2. Export Parameter
                    a. Parameter Name : E_TIME_HIGH
                    b. Type Spec       : LIKE
                    c. Associated Type : BKPF-CPUTM
                    d. Pass Value      : Ticked/checked (yes)
b) Function Module: BWFIT_UPDATE_TIMESTAMPS
                    1. Import Parameter (add after I_DATE_HIGH)
                    a. Parameter Name : I_TIME_LOW
                    b. Type Spec       : LIKE
                    c. Associated Type : BKPF-CPUTM
                    d. Optional        : Ticked/checked (yes)
                    e. Pass Value      : Ticked/checked (yes)
                    2. Import Parameter (add after I_TIME_LOW)
                    a. Parameter Name : I_TIME_HIGH
                    b. Type Spec       : LIKE
                    c. Associated Type : BKPF-CPUTM
                    d. Optional        : Ticked/checked (yes)
                    e. Pass Value      : Ticked/checked (yes)
4. Working of minute based extraction logic:
              The minute based extraction works considering the time to select the data (apart from date of the document either changed or new as in the earlier logic).The modification to the code is made such that it will consider the new flags in the BWOM_SETTINGS table ( BWFINEXT and BWFINSAF ) and the code for the earlier extraction logic will remain as it was without these flags being set as per the instructions for new logic to be used(but are modified to include new logic).
Safety interval will now depend on the flag BWFINSAF (in seconds ; default 3600) and has a default value of 3600 (1 hour), which would try to ensure that the documents which are delayed in posting due to delay in update modules for any reason. Also there is a specific coding to post an entry to BWFI_AEDAT with the details of the document which have failed to post within the safety limit of 1 hour and hence those would be extracted as a changed documents at least if they were missed to be extracted as new documents. If the documents which fail to ensure to post within safety limit is a huge number then the volume of BWFI_AEDAT would increase correspondingly.
The flag BWFINSAF could be set to particular value depending on specific requirements (in seconds , but at least 3600 = 1 hour) like 24 hours / 1 day = 24 * 3600 => 86400.With the new logic switched ON with flag BWFINEXT = X the other flags BWFIOVERLA , BWFISAFETY , BWFITIMBOR are ignored and BWFILOWLIM , DELTIMEST will work as before.
As per the instructions above the index-1 for the extraction in table BWFI_AEDAT would include the field AETIM which would enable the new logic to extract faster as AETIM is also considered as per the new logic. This could be removed if the standard logic is restored back.
With the new extractor logic implemented you can change back to the standard logic any day by switching off the flag BWFINEXT to ' ' from 'X' and extract as it was before. But ensure that there is no extraction running (for any of the extractors 0FI_*_4 extractors/datasources) while switching.
As with the earlier logic to restore back to the previous timestamp in BWOM2_TIMEST table to get the data from previous extraction LAST_TS could be set to the previous extraction timestamp when there are no current extractions running for that particular extractor or datasouce.
With the frequency of the extraction increased (say 3 times a day) the volume of the data being extracted with each extraction would decrease and hence extractor would take lesser time.
You should optimize the interval of time for the extractor runs by testing the best suitable intervals for optimal performance. We would not be able to give a definite suggestion on this, as it would vary from system to system and would depend on the data volume in the system, number of postings done everyday and other variable factors.
To turn on the New Logic BWFINEXT has to be set to 'X' and reset back to ' ' when reverting back. This change has to be done only when there no extractions are running considering all the points above.
              With the new minute based extraction logic switched ON,
a) Ensure BWFI_AEDAT index-1 is enhanced with addition of AETIM and is active on the database.
b) Ensure BWFINSAF is atleast 3600 ( 1 hour) in BWOM_SETTINGS
c) Optimum value of DELTIMEST is maintained as needed (recommended/default value is 60 )
d) A proper testing (functional, performance) is performed in standard test system and the results are all positive before moving the changes to the production system with the test system being an identical with the production system with settings and data.
http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm

Decoupling of AR, AP, GL Datasources (i.e. 0FI_AR_4)

I've checked out several posts regarding the topic of Decoupling 0fi_ar_4 0fi_ap_4 from 0fi_gl_4, but unfortunatly still don't see my specific issue.
We have PI 2004_1_46c, BW 3.0b. I found an OSS note 826023 that says it decouples the extractors. Now, i thought this would remove the dependency, but we applied this and the dependency is still there.
In R/3, using RSA3, if I try to view 0FI_AR_4 data, I cannot unless 0FL_GL_4 has been loaded into BW. I have no use for GL at this time, so I really do want to remove this dependency.
ALSO, I used CMOD to add logic in the customer exit to populate zz* fields I added to the structure append. I read in another thread that I could do it this way instead of using the SAP suggested function module (from SAP documentation). However, now that I have done that, when I try to run the delta init, it just sits there. When I look at the job log (R/3), it is empty, save for some comments. Any idea why?
Any help would be appreciated!!
Lisa

Hi Guys!,
I'm having the same problem, does anybody know if it possible to decoupling the FI extractors??
Thanks!!.
Mauricio.

0FI_AR_4 not updating item status

Hi !
I am facing a problem with extractor 0FI_AR_4. When loading a delta load with clearing docs the status of the document cleared by this delta is still O.
I can find the clearing doc in the ODS, but the cleared one is still the same, with blank clearing doc and clearing date.
Is this correct ? Shouldn't the cleared doc appear as cleared with its corresponding cleareing doc and clearing date ?
edit: I have just found an OSS Note 1051099 - BUC: Change to clearing information not reported to BW, but I know for certain that the clearing process is made through SAP standard transactions and not the program mentioned in the note. But the problem is the same. The chage of status that should update the record in the ODS is not beign generated, so I have only two records in PSA, one for the original document and another for the clearing doc, but there should be a third one for the update of original doc with status changed to C. Am I right ? Has this happened to anyone else out there ?
Please tell me where to start looking for answers !!
Regards,
Santiago
Edited by: Santiago Reig on Mar 11, 2008 7:32 PM

Hi..
For FI datasources you will not be able to see any data in the delta queue..
Data will get populated in the delta queue during extraction..
After init...it writes the entries into the time stamp table BWOM2_TIMEST in the SAP R/3 System with a new upper limit for the time stamp selection...
Depending on that data will get fetched from the table BKPF based on creation date (CPUDT)...
For 0FI_AR_4 (AR- line items )Selections are made from tables BSID/BSAD (Accounts Receivable)
This is for new entries.......
For changed records data will get fetched from the table BWFI_AEDAT , depending on the time stamp table BWOM2_TIMEST....
Check the following blog :
/people/swapna.gollakota/blog/2008/01/14/one-stage-stop-to-know-all-about-bw-extractors-part1
Regards,
Debjani.........

0FI_AR_4 not fetching delta

hi experts,
i am having problem with 0fi_ar_4, i have run the init with data transfer for this datasource and it went successfully, But delta values are not able to fetch, delta infopackage brings 0 records with green status.
In rsa7 there are no records for this datasource. I have checked in smq1 also no luws are stuck there
I have 0fi_gl_4 data source which is working fine with full and as well as delta.
I have checked in bwom2_timest which has last updated information for 0fi_ar_4 and delta also. But the values in delta run are not fetching.
The same data source is working fine in development system. I can able to see delta records in rsa7 against this 0fi_ar_4 DS.
please suggest me ..

Hi..
For FI datasources you will not be able to see any data in the delta queue..
Data will get populated in the delta queue during extraction..
After init...it writes the entries into the time stamp table BWOM2_TIMEST in the SAP R/3 System with a new upper limit for the time stamp selection...
Depending on that data will get fetched from the table BKPF based on creation date (CPUDT)...
For 0FI_AR_4 (AR- line items )Selections are made from tables BSID/BSAD (Accounts Receivable)
This is for new entries.......
For changed records data will get fetched from the table BWFI_AEDAT , depending on the time stamp table BWOM2_TIMEST....
Check the following blog :
/people/swapna.gollakota/blog/2008/01/14/one-stage-stop-to-know-all-about-bw-extractors-part1
Regards,
Debjani.........

0FI_AR_4 Arithmetic overflow while extracting delta

Hi All,
While extracting 0FI_AR_4 delta from R/3 only data packages 2-4 were recieved in BW. Data package 1 is missing and the load was terminated with an error: "Arithmetic overflow error converting numeric to data type numeric.#3621 The statement has been terminated."
Looking in RSA7 (in R/3 side) I can see all delta data waiting for Delta Repetition but can not locate any erroneous record (although I get "overflow" error when trying to sum one of the fields there. Sorting this field's values reveals nothing odd).
Any idea as how to locate the bad record(s) , and as how to fix the problem?
Thanks,
OM

Thank you Srinivas,
I've checked ST22 log but besides listing the cause of the dump (Arithmetic overflow...) it gives no details as to the specific record / value / string.
OM

Table BWFI_AEDAT empty?

Hi Guru's,
I am loading DS 0FI_AP_4 into our BI7 system. However, I notice that even after running an init load and then a delta the next day, that the BWFI_AEDAT table is empty.
I perhaps do not understand the purpose of entries in this table? I thought it was to store all rows already transferred via the delta load (for use in a repeat delta if required) if the corresponding date was still available in the BWOM2_TIMEST table for this DS? And also for failed rows requested on a prior delta request?
If not, is there any config I need to do to enable entries to get written into this table? Our BI system is fairly new and perhaps not fully set up, so maybe we still need to do some config settings?...
Thanks!
Darryl

Hi there,
Both 0FI_AP_4 and 0FI_AR_4 need to be run only after running 0FI_GL_4.
Did you run 0FI_GL_4 first?
Check in here:
[http://help.sap.com/saphelp_bw33/helpdata/en/3f/fbf83a0dfa5102e10000000a114084/content.htm]
In particular it says this:
Features of the Extractor
As the strict connectoin of DataSources has been abolished as of PlugIn2002.2, you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 in any order you like. You can also use DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another (see note 551044).
Note
As soon as DataSource 0FI_GL_4 has been loaded, it is the leading DataSource with regard to accruals, such as the time and date (CPU date) by which extraction should be carried out.
From the transition of the data requirements in Delta-Init-Modus to Delta operation therefore, the data requirement in Delta mode 0FI_GL_4 should take place first.
Connecting the DataSources in delta operation helps to ensure consistent extraction of FI data. Consistency must be ensured using the Init selection criteria.
Diogo.
Edited by: Diogo Ferreira on May 27, 2009 4:05 PM

Extraction from 0FI_AR_4

Hi,
I ran the initial load for the datasource 0FI_AR_4 and it was successful. Before the load the activated the chage pointers using BD61. Now in RSA7 I see the delta queue for 0FI_AR_4. The problem is I don't see any records in the delta queue even though there are new and changed records after I ran my initial load.
Do I need to schedule the Delta collection as we do in LBWE. Please help where I can schedule a job which collects all the changes and puts in delta queue.
Please help!
Thanks,
Vish

Hi Vish,
You do not need to schedule any job for FI datasources. The job you mentioned are specific to LO Cockpit.
>>Before the load the activated the chage pointers using >>BD61
Please elaborate the above statement? THat might be the reason for the delta not being picked up. Hope this helps.
Thanks and Regards
Subray Hegde

How can I setup a mail-specific passcode/restriction on iPad used by multiple family members?

How can I setup a mail-specific passcode/restriction on iPad used by multiple family members?
Have an Exchange mail account setup and accessible in my mail on iPad... however my kids use it and i would like to restrict them from accessing this specific portion of the device. I tried viewing restriction options and do not see that i can apply a restriction specifically to Mail. Thanks for your help.

Not a feature of iOS. Check the AppStore to see if there are other
mail apps that allow passcode protection.
Or use Safari to log onto your email via a web-based interface and
enter your credentials each time. A bit slower, but the kids will
not know the details to login.

Cannot send email from Verizon to a specific domain using the web UI

I'm trying to send an email to a specific address on a domain I own from a Verizon account using the web UI. Whenever I click send, a popup appears saying "Your e-mail contains the following invalid e-mail addresses:" followed by the email address. I can send email to this address from a GMail account as well as my work email.
In Chrome, I can see that a "code":1002 error is being produced.
Does anyone know why this would happen? Does Verizon check destination domains for reputation? Is there any way to debug this further?

rhodeislandred wrote:
I'm trying to send an email to a specific address on a domain I own from a Verizon account using the web UI. Whenever I click send, a popup appears saying "Your e-mail contains the following invalid e-mail addresses:" followed by the email address. I can send email to this address from a GMail account as well as my work email.
In Chrome, I can see that a "code":1002 error is being produced.
Does anyone know why this would happen? Does Verizon check destination domains for reputation? Is there any way to debug this further?
What is the domain that is giving you the error?

How to pop up a system message for a specific user when She/He log on SAP

Hi Friends,
As we know SM02 setting will pop up a system message to all users in specific client in a specific period when the user log on SAP system; and we can do the same thing via using function module SM02_ADD_MESSAGE.
But now we want to pop up a message to a specific user ID when somebody log on SAP via this ID, instead of all user IDs in the client. Please do we have any similar traction / function module / class method to to do this job??
Thanks in advance.
Joe

Below code can be used to send a pop up message to all users who are logged on to the
system.
DATA: MESSAGE(128) VALUE 'Test message'.
DATA: OPCODE TYPE X VALUE 2.
DATA: BEGIN OF USR_TABL OCCURS 10.
INCLUDE STRUCTURE UINFO.
DATA: END OF USR_TABL.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD OPCODE
ID 'TAB' FIELD USR_TABL-SYS.
LOOP AT USR_TABL.
CALL FUNCTION 'TH_POPUP'
EXPORTING
CLIENT = SY-MANDT
USER = USR_TABL-BNAME
MESSAGE = MESSAGE
EXCEPTIONS
USER_NOT_FOUND = 1.
ENDLOOP.
In the above code just pass the desired user ID instead of All user ID's
Edited by: harsh bhalla on Mar 26, 2009 2:14 PM

IIS 7.5 URL Rewrite: Hit specific page of a web application but should be redirected to another application's page

I have deployed 2 different web application on IIS 7.5 running on Windows Server 2008 R2 but on different port numbers i.e. one application deployed on port no. 1776 and another on 8091. I want to rewrite URL in such a way that if i hit any page of first
application such as default.aspx then it will be redirected to particular page of another application along with some changes in url.
Example: if i access any page from first application like:
http://g2wv126rbsc:1776/sites/main/commercial/commercial-solutions/financing/default1.aspx
then it should redirect to specific page of another application along with some changes in url:
http://g2wv126rbsc:8091/main/commercial/commercial-solutions/financing/default2.aspx
Note: In above mentioned url, also removed "sites".
I tried to create a inbound rule through URL Rewrite module (installed on IIS 7.5) by selecting Action as "Rewrite" but didn't find any success.
I need some examples if anyone has come across same kind of issue.
Thanks in advance.

Please post ASP.NET questions in the ASP.NET forums (http://forums.asp.net ).

How to blick tree view few specific nodes

here i got a code which show how to blink tree view node but i am confuse that how to blink few node.
Answered by:
Avatar of Tamer Oz
20,185
Points
Top 0.5
Tamer Oz
Partner Joined Sep 2009
2
8
17
Tamer Oz's threads
Show activity
Treeview control - How to make a node blink?
Visual Studio Languages
.NET Framework
>
Visual C#
Question
Alert me
Question
Vote as helpful
0
Vote
Hi,
Is there a "elegant" way to make blink a treeview node?
I am thinking to use a timer with the collection of nodes that I want to make the blink effect, and update the icon ...
Friday, November 06, 2009 6:19 PM
Reply
|
Quote
|
Report as abuse
Avatar of Kikeman
Kikeman
R. BOSCH
105 Points
All replies
Question
Vote as helpful
0
Vote
Hi,
You can develop your custom control for this purpose. The logic you mentioned was correct. Here is a sample control that I developed by the logic you mentioned.
public class BlinkingTreeView : TreeView
private Timer t = new Timer();
private List<TreeNode> blinkingNodes = new List<TreeNode>();
public BlinkingTreeView()
t.Interval = 1000;
t.Tick += new EventHandler(t_Tick);
bool isNodeBlinked = false;
void t_Tick(object sender, EventArgs e)
foreach (TreeNode tn in blinkingNodes)
if (isNodeBlinked)
//update Icon
tn.Text = tn.Text.Substring(0, tn.Text.Length - 1);//to test
isNodeBlinked = false;
else
//update Icon
tn.Text = tn.Text + "*";//to test
isNodeBlinked = true;
public void AddBlinkNode(TreeNode n)
blinkingNodes.Add(n);
public void RemoveBlinkNode(TreeNode n)
blinkingNodes.Remove(n);
public void ClearBlinkNodes()
blinkingNodes.Clear();
public List<TreeNode> BlinkingNodes
get { return blinkingNodes; }
public int BlinkInterval
get { return t.Interval; }
set { t.Interval = value; }
public void StartBlinking()
isNodeBlinked = false;
t.Enabled = true;
public void StopBlinking()
t.Enabled = false;
just show me how to use BlinkingTreeView class. i will have tree view which will have few node and few nodes may have few child nodes. now how to achieve by this class BlinkingTreeView and show me how to blink few specific node not all. thanks

better to come with code. first populate tree view with some dummy node this way
Root
       Child1
                Child1-sub1
                Child1-sub2
       Child2
                Child2-sub1
                Child2-sub2
now blink Child1-sub2 & Child2-sub1. please come with code. thanks

FBL3N to BW report for specific GL's

Dear BW Experts,
I want to create report in BW for FBL3N for specific GL's, for open items.
I am done with development.
Report on standard DSO 0FIGL_O02 (0FI_GL_4)...
Simply GL in rows, with filter for open status.
Issue: Balance is not matching from ECC for one GL, because of one document,
which is closed in ECC but in DSO its still open (data is upto date in BW).
Thanks
Arun Purohit

I did re-load but without luck.....
that docment is there in BSAS(closed docs table) table not in BSIS (open docs table)...still ds 0FI_GL_4 shows that item still open....

0FI_AR_4 & SPECIFICALLY BWFI_AEDAT

Similar Messages

Maybe you are looking for