on ‎2018 May 21 4:49 PM
I have implemented the 0FC_BP_ITEMS in BW and storing open and clear Item in two different DSOs. Now i am facing issue in computing Open Item in BEx.
I have document number in DFKKOP table which is cleared on 25th April, 2018.

The same is not being captured in Open Item DSO as it is already been cleared and loaded to Clear DSO. How would I load the document in Open Item ?
Now, while running the report , we are getting mismatch in data. If I run the report till 22.12.2016, I am not getting this record as it is not present in Open Item Cube.
Ideally it should show in open Item.
Could you please help in this and how can i capture this record in Open Item DSO to get correct results ?
Request clarification before answering.
Hi There,
Consider taking a new approach.
Put both Open and Cleared DSO into a MutiProvider or Composite InfoProvider with a query with "Closed Amount" and "Open Amount".
Place a condition of the query results showing only those records with "Open Amount" > "Closed Amount".
Good luck!
John Hawk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cleared item records have a reconciliation date, the report/query should consider those records as open as long as the reference date is less than this date (or the date initial)
It should not be necessary to duplicate the records.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can find it in online help
I have also implemented the datasource 0FC_BP_ITEMS. Could someone assist me in determining the DSO, Infocube, and standard Multipro to activate from the business content, as well as the standard queries to retrieve the data according to a standard flow? Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 6 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.