Inspoke data logic

Hi all,
I have created an Ispoke which is getting the data from an infocube and feeding the data to a flat file.
The number of records transferred from infocube to Ispoke are not same. For example, infocube is getting 16 records and Ispoke is getting only 14 records. Where the balance records can be missed.. There is no problem with selection conditions in Ispoke, it is set to get full data from the infocube
Please suggest.

Hello BW,
In InfoSpoke monitor you can understand where the number of records become lesser than in Cube. So 1st check in InfoSpoke Monitor.
the better solution is:
In BI7.0, InfoSpoke execution can happen with DTP. In the DTP do the Temporary Storage settings and check the transformation values.
http://help.sap.com/saphelp_nw04s/helpdata/en/43/58e1cdbed430d9e10000000a11466f/content.htm
Regards,

Similar Messages

MDX calculation based on date logic for the Jan 1 of current year through the 15th of the previous month

Hello,
We need some help with an SSAS MDX query based on date logic. One of the problems is that I don't have access to the Cube but have been given a query example with the logic needed for the calculation. Here's the scenario;
The ETL process will run on the first Tuesday after the 15th of a given month. The Analysis Cube data queried should include the current year up to the end of the previous month. For example, on May 19th
(the first Tuesday on or after the 15th) the query should include data from January 1st through April 30th.
The 15th of the month is not part of the query, it is a factor in when the query is run. The query will always be in terms of complete months.
SELECT
 NON EMPTY { [Measures].[Revenue Amount],
 [Measures].[Utilization],
 [Measures].[AVG Revenue Rate],
 [Measures].[Actual Hours] }
ON
 COLUMNS,
 NON EMPTY { ([dimConsultant].[User Id TT].[User Id TT].ALLMEMBERS * [dimConsultant].[Full Name].[Full Name].ALLMEMBERS * [dimConsultant].[Employee
Type].[Employee Type].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION,
 MEMBER_UNIQUE_NAME
ON
 ROWS
FROM
 ( SELECT
( { [dimDate].[Week Date].[1/4/2015], [dimDate].[Week Date].[1/11/2015], [dimDate].[Week Date].[1/18/2015], [dimDate].[Week Date].[1/25/2015], [dimDate].[Week Date].[2/1/2015] } )
 ON
 COLUMNS
 FROM
 ( SELECT
( { [dimIsBillable].[Is Billable].&[True] } )
 ON
COLUMNS
 FROM
[SSASRBA]
WHERE
 ( [dimIsBillable].[Is Billable].&[True], [dimDate].[Week Date].CurrentMember ) CELL PROPERTIES VALUE,
 BACK_COLOR,
 FORE_COLOR,
 FORMATTED_VALUE,
 FORMAT_STRING,
 FONT_NAME,
 FONT_SIZE,
 FONT_FLAGS

Hi Hans,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Simon Hou
TechNet Community Support

Last Consumption & Last receipt date logic

Hi
I am facing some issue while developing BI Stock report where user wants last consumption date & last receipt date in the report.
But issue is that when i am going to develop BI query how can i differentiate date for both consumption & receipt because consumption & receipt has differentiate with movement type (suppose Mov type : 101 is for receipt & 261 is for consumption then if i use exceptional aggregation and put last value & reference char as Mov type then all 101 & 261 mov type data will come.
Please guide for developing last consuption & last receipt date logic
Regards,
Gaurav

Hi Anshu
Thanks for your helpful reply.
This is my last option as you suggested. But i will share you my concern that i have developed report on 0IC_C03 & in our business scenario, If i change ETL Structure then we need to delete target data, & we have millions of records if i reconstruct the data then it will take 4-5 days times. Also, some times our marker is interrupted then we need to again the same activity so i want to avoid the same activity in Workbench side and do all required changes in BI Query side.
Can we use customer variable for time characteristics for the same issue.
If there is any other idea in your mind, Please share.

Difference between data logic operation and business operation

hiii, DI core, main component of DI API, performs all data logic operaton where as OBServer.dll perform bussiness logic operation at database level...
what is the difference between these operations????

Hi Nirdesh,
The DI API offers a number of objects/methods that allow you to access the information stored in the database (tables) by using objects.
The DI API is represented by the SboBobCOM.dll, in your code you only add a reference to this COM dll. This dll offerst the objects/methods you can access.
The SbobobCOM.dll is using the OBServer.dll, this dll contains all the business logic rules (like for example: you cannot delete a BusinessPartern if it has already some documents created) that will control all actions you are trying to do with the DI API methods/objects.
You have a schema representing both dlls in the DI API help file -> Introduction -> DI API components section.
Regards
Trinidad.

Why doesn't Aperture use iPhoto's date logic?

This is how image date logic works in iPhoto. This image date value is used in queries and sorts.
1. Image date is stored in database.
2. Initial value taken from image metadata if available.
3. If image metadata not available, use file date.
4. User can edit database date (does not change file header).
This is how it seems to work in Aperture 1.5
1. Image date is stored in database.
2. Initial value taken from iPhoto database if import from iPhoto.
3. If not import from iPhoto, initial value taken from image metadata if available.
4. If image metadata not available, use file date.
5. User CANNOT edit database date.
I was shocked (really, I'm still stunned) that Aperture 1.5 still does not equal iPhoto's date management capabilities. Since Aperture is a Pro application it's reasonable to have several date fields, but one of them should behave like iPhoto. That metadata field should be useable in queries/filters, sorts, display, book printing, etc. It should be the default date metadata element for all date related operations.
Please note, it's fine that Aperture does not muck with image file (exif) metadata -- that's dangerous. EXIF is a quasi-standard badly implemented.
So now, my question. Why?
Aperture 1.5 was a huge update. They fixed much more than I thought was possible. It could have been labeled Aperture 3.0. Offering it free to users was a genuine apology, gratefully accepted I'm sure. It took all my strength of will not to order it immediately, waiting instead for the initial reviews to come in.
So there had to be a reason Aperture's Product Manager, Joe Schorr, had not to implement iPhoto's image date behavior. Something he'd thought carefully about.
What was it?

Perhaps it's just that they don't have infinite resources ?
The big deal (for me) was that they can "import" files but leave them on the filesystem. In true Apple fashion though, they took the extra steps of allowing management of the images within the application (consolidate and relocate). Perhaps the knock-on effects of all the things they did implement prevented them from doing other things...
We see Apple as a corporate entity, master of its domain, all-seeing, all-knowing, all-powerful within the confines of an Infinite Loop. In reality it's a bunch of people who only have a fixed number of hours in the day to work. Someone takes the decision that X is more important than Y and Y is dropped for this release - it's that simple IMHO.
In any event, I'd like to know how many people worked on Aperture 1.5 - the difference between the Aperture update and the Lightroom update was huge! Do they have lots more engineers/QA, or did they just get more done in the same time-frame ?
-=C=-
Mac Pro Mac OS X (10.4.7)

Help Needed in Date Logic

Hi I am working in sqlserver 2008 R2 and below is my sample research query
i am trying to get previous 6 months data.
WITH CutomMonths
AS (
SELECT UPPER(convert(VARCHAR(3), datename(month, DATEADD(MM, DATEDIFF(MM, 0, GETDATE()) - N, 0)))) Month
,DATEADD(MM, DATEDIFF(MM, 0, GETDATE()) - N, 0) startdate
,DATEADD(MM, DATEDIFF(MM, 0, GETDATE()) - N + 1, 0) enddate
FROM (
VALUES (1)
,(2)
,(3)
,(4)
,(5)
,(6)
) x(N)
WHERE N <= 6
SELECT month
,SUM(isnull(perks.amount,0)) AS PerkAmount
FROM CutomMonths
LEFT JOIN (
select 10.00 as amount,'2014-04-03' as StartDate,'2015-04-03' as EndDate union all
select 10.00 as amount,'2014-04-03' as StartDate,'2015-04-03' as EndDate
) perks ON
CutomMonths.startdate >= perks.StartDate
AND CutomMonths.startdate < perks.EndDate
GROUP BY CutomMonths.Month
,CutomMonths.startdate
ORDER BY CutomMonths.startdate ASC
current output what i am getting:
Expected Output:
I found why the April month i din't get the $20 because the startdate of my perks CTE '2014-04-03'. If it is '2014-04-01' then i will get the expected output.
But i should not change the the date on perks. How to neglect this date issue and consider the month instead to get the expected output. please help me on this as i am struggling on my logic
loving dotnet

I'm just going to focus on the JOIN criteria in this reply since my answer above and your 2nd response are essentially the same except for the JOIN.
What your are describing and what you are doing in code is conflicting.
You are saying this:
"I just need to check whether the perks start date falls in between month start date and month end date"
..., which translated directly to code would be this:
ON perks.StartDate >= CustomMonths.StartDate
AND perks.StartDate <= CustomMonths.EndDate
What I believe you are getting after is this:
"I just need to check whether the dates within the perks start and end date range fall in between month start date and month end date"
..., which translated directly to code would be this, which is also my answer proposed above:
ON CustomMonths.StartDate >= DATEADD(DAY, -(DAY(perks.StartDate) - 1), perks.StartDate)
AND CustomMonths.StartDate <= perks.EndDate
However, if you really want to use the code solution you proposed, then you would actually be saying this:
"I just need to check whether the dates within the perks start and end date range fall in between month start date and month end date, but if perk end date happens to be the first day of the month, then ignore it and use the previous day."
..., in which case then your code, as follows, would be the solution:
ON CutomMonths.startdate >= DATEADD(mm, DATEDIFF(mm, 0, perks.StartDate), 0)AND CutomMonths.startdate < DATE
ADD(mm, DATEDIFF(mm, 0, perks.EndDate), 0)
NOTE: The alternate JOIN I had commented out in my proposed answer above will do the exact same thing as your latest proposed solution
ON CustomMonths.StartDate >= DATEADD(DAY, -(DAY(perks.StartDate) - 1), perks.StartDate)
AND CustomMonths.StartDate < perks.EndDate
BTW, I see how you are getting to the first day of the month by subtracting all the months from the given date to 01/01/1901, and then turning around and adding them all back to 01/01/1901. While that is one way to get to the first day of the month, it
seems excessive from a calculation stand point, although I haven't performed any performance tests to know for certain.
SELECT DATEADD(mm, DATEDIFF(mm, 0, '2014-04-03'), 0)
I prefer simply subtracting one less than the current day number from the given date to get to the same first day of the month value.
SELECT DATEADD(DAY, -(DAY('2014-04-03') - 1), '2014-04-03')

In which package would I find the recalculate payment due date logic

In R12 Invoice Workbench screen when you change certain fields the payment due date is recalculated. I want to look at the logic behind that functionality. I am looking at the code for the form but struggling as I haven't looked at Oracle forms in years and never anything this complex. Can someone point me to the pl/sql package that contains the logic? Thanks!

The information comes from multiple tables.
But you can get most of the information from mtl_material_transactions. It will give you transaction date, type, subinventory, quantity, uom , transaction value
You will have to join the record with po tables to get PO#
Hope this answers your question,
Sandeep Gandhi

Help in implementing date logic calculation

Hello,
We need to implement below logic in our Webi report:
Report Logic: Any Purchase_Order whose delivery (Promised Date) is pending next in 15 days and also any pending deliveries which has not happened beyond 15 days.
Please suggest how the above logic can be implimented at the report level or at the Universe level.
I have tried with below object at the universe level but it is not giving correct results.
case when (sysdate - DWH_SSS_PO_LINE_LOC_DETAILS.PROMISED_DATE>=15) or (DWH_SSS_PO_LINE_LOC_DETAILS.PROMISED_DATE-sysdate<15 ) and DWH_SSS_PO_LINE_LOC_DETAILS.QUANTITY_RECEIVED=0 then 'Y' else 'N' end
It is BOXI3.1 SP7 on Oracle 11g db.
Thank you.
Regards,
Kaustubh Ghate

Hi Kaustubh,
You could use DaysBetween function in WebI.
So the formula would be like the following:-
If (DaysBetween(Currdate;Promise date)<=15) then Purchase Order
And for the second one:-
Pending Deliveries Where (DaysBetween(Promise date;Currdate)<15)
Let me know if the above works.
Regards,
Manpreet

Date logic of OM infotypes

hi all.
i need to change the start date of object from SY_DATUM to 1st jan of currennt year on following condition.
if the object is create before 1st jan of 2008 the logic sholud be applicable else the creation date of object should be default date for start date of that object while entering values through PP01.
please help me by giving details.
and in which table this BEGDA and ENDDA values of OM infotypes will be stored.??
Advance Thanks,
kranthi
09739567165

you can check the Tables
HRP1000 to HRP1999 for OM Related tables.

How to get back deleted data logically

Hi
Friends
Once again need your guidance to solve my this problem.
If I have deleted data and commited.Now I want to bring that data back.
How m I to do this.I want to do it logically.
Pls help me.Is there any thirdparty software to do it logically if yes thwn what its name
Hope to hear soon
Regrds,
Chandrima Roy

There are number of ways to recover from such user erros:
1). RMAN incomplete recovery, if you have proper backups and redo logs to recover until the time just before the user error happened.
http://www.kods.net/use-rman-based-incomplete-recovery-time/
2). Flash back query, if UNDO is being managed properly.
http://www.orafaq.com/node/50
3). Flashback database if set to ON and flashback logs are being written.
http://www.oracle-base.com/articles/10g/Flashback10g.php#flashback_database
4). Last but not the least, Oracle LogMiner, required minimal setup i.e. db should be in Archive Log Mode.
For Oracle 10g:
http://www.oracleflash.com/25/Using-Oracle-LogMiner-to-undo-incorrectly-committed-changes.html
For Oracle 11g:
http://www.oracleflash.com/31/Oracle-11g-DBMS_FLASHBACK-TRANSACTION_BACKOUT.html
http://www.oracleflash.com/30/Oracle-11g-Flashback-Transaction-in-OEM-LogMiner-Interface.html

Master Data-Logic of dates in Master data

Dear Sapients,
In Master data what should be the Logic for BEGDA, for diff. Infotypes and the objects.
In my present project I have taken the earliest hiring date i.e, 01011985 as BEGDA. Is this logic is okie. Else what should be d logic for BEGDA-ENDDA.
In one of my master data position is assigned to cost centres, FI guy has maintained d BEGDA of cost centers from 01012007 but my position's BEGDA is 01011985, I believe it ll be a mismatch n throw error. What should be d solution for this?
Regards,
Kaushal

hai
the begda of the records always depends upon accepted date s per the requirement of the client
more precisely from which date u r going to maintain the data for the employee in sap system.
generally it is acccepted upon earlier by the client and you.
because it always difficult to maintain all the data of the employee since the icepton of the company.
so a cut off date has to be accepted upon and from that date the data will be maintained and the records will have that BEGDA
regards
nalla

Date logic required urgently

hI all,
i need logic for the following
Basically, 15.06.2007 is the Required delivery date for the plant. This means that the stock should be there in the plant by 15.06.2007.
We need to change the formula for the delivery date.
Formula: Delivery date = (15.06.2007 LEAD TIME of the material)
Say, for example the lead time for the product is 8 (this varies for different materials). Then the delivery date should be:
Delivery date = (15.06.2007 8)
                            = 07.06.2007
So we need to create a PO for this material on 07.06.2007
Thanks
sanjeev

use this Fm
RP_CALC_DATE_IN_INTERVAL
pass i/p as date and sign as minus .
make use of this code .
pass ur lead days
data: date like sy-datum,
      date1 like sy-datum.
date = sy-datum.
CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL'
EXPORTING
    date            = date
    days            = 08 "take this as leadtime in days
    months          = 00
   SIGNUM           = '-'
    years           = 00
IMPORTING
   CALC_DATE       = date1. " new date
write:/ 'new date', date1.
regards,
Vijay

Interactive Reort with DATE logic

Hi,
I have a Interactive Report having the following criteria.
Let's suppose report is based on EMP table and it has a date field called EMP_DATE
My week start from Monday to Sunday.
*1. Current Week*
Feb 01 - Monday
Feb 05 - Friday
Feb 07 - Sunday
when I run the report any day from Monday (Feb 01) to Sunday (Feb 07), it should fetch all the employees whose EMP_DATE falls between the current week Monday (Feb 01) & Friday (Feb 05).
*2. Next Week*
Feb 08 - Monday
Feb 12 - Friday
Feb 14 - Sunday
when I run the report any day from Monday (Feb 01) to Sunday (Feb 07), it should fetch all the employees whose EMP_DATE falls between the next week Monday (Feb 08) & Friday (Feb 12).
*3. Previous 3rd Week*
Jan 11 - Monday
Jan 15 - Friday
Jan 17 - Sunday
when I run the report any day from Monday (Feb 01) to Sunday (Feb 07), it should fetch all the employees whose EMP_DATE falls between the previous 3rd week Monday (Jan 11) & Friday (Jan 15).
if anyone has implemented this kind of logic??, appreciate your feedback..
Thanks,
Deepak

Hi
After a slight amendment, here you go...
1.
WITH my_dates AS (SELECT TRUNC(SYSDATE)+LEVEL-20 dt
 FROM dual
 CONNECT BY LEVEL <= 20)
SELECT dt
FROM my_dates
WHERE dt BETWEEN NEXT_DAY(TO_DATE(:d)-7,'Monday')
 AND NEXT_DAY(TO_DATE(:d)-3,'Friday');2.
WITH my_dates AS (SELECT TRUNC(SYSDATE)+LEVEL-7 dt
 FROM dual
 CONNECT BY LEVEL <= 20)
SELECT dt
FROM my_dates
WHERE dt BETWEEN NEXT_DAY(TO_DATE(:d),'Monday')
 AND NEXT_DAY(TO_DATE(:d)+4,'Friday'); 3.
WITH my_dates AS (SELECT TRUNC(SYSDATE)+LEVEL-50 dt
 FROM dual
 CONNECT BY LEVEL <= 50)
SELECT dt
FROM my_dates
WHERE dt BETWEEN NEXT_DAY(TO_DATE(:d)-28,'Monday')
 AND NEXT_DAY(TO_DATE(:d)-24,'Friday'); To fit this into your reports, replace the :d variable with TRUNC(SYSDATE) and dt with emp_date. Remove the WITH clause and you should be sorted.
Cheers
Ben
Edited by: Munky on Feb 5, 2010 4:17 PM

Date logic implementation in store proc

Monthly – 5th day of each month including on holidays or weekends

Hmm..do you mean excluding holidays and weekends? Otherwise 5th day of month is always having date as 5 :-)
If you meant excluding you can use this logic based on calendartable
SELECT MAX(Date) AS [5thDay]
FROM
SELECT TOP 5 [Date]
FROM CalendarTable
WHERE WeekDay = 1
ORDER BY [Date]
)t
If holiday info is in seperate table then use this
SELECT MAX(Date) AS [5thDay]
FROM
SELECT TOP 5 [Date]
FROM CalendarTable c
WHERE WeekDay = 1
AND NOT EXISTS (
SELECT 1
FROM HolidayTable
WHERE [Date] = c.[Date]
ORDER BY [Date]
)t
if you want this to be returned for every month use this
SELECT [Date] AS [5thDay]
FROM
SELECT ROW_NUMBER() OVER (PARTITION BY DATEDIFF(mm,0,[Date]) ORDER BY [Date]) AS Rn,
[Date]
FROM CalendarTable
AND NOT EXISTS (
SELECT 1
FROM HolidayTable
WHERE [Date] = c.[Date]
WHERE WeekDay = 1
ORDER BY [Date]
)t
WHERE Rn = 5
If you dont have a calendartable already you can use this UDF instead
http://visakhm.blogspot.in/2010/02/generating-calendar-table.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Date logic in PCS tags

I've seen old postings, with no solutions posted, and wanted to rehash the discussion.
Is it possible to do any date processing in a presentation template? I want to filter out content items older than X number of days, etc.
Any ideas are appreciated.

outer loop would be pcs foreach
inner loop would have pt-tag based check
<pcs:for each...>
<pt:logic.variable pt:key="date1" pt:value="<pcs:value date1"/>
<pt:logic.variable pt:key="date2" pt:value="<pcs:value date2"/>
<pt:logic.intexpr pt:expr="($date1) > ($date2) + 7" pt:key="boolvalue"/>
<pt:logic.if pt:expr="$boolvalue">
<pt:logic.iftrue>
<pcs:insert my content item>
</pt:logic.iftrue>
<pt:logic.iffalse>

</pt:logic.iffalse>
</pt:logic.if>
</pcs:foreach>
I would see if you could use the date output format to print the date in a way that would be easily comparable...I haven't looked into that too much. Otherwise you would have to account for day/week/month etc..could be a real hassle.
Oh bt1 these tags are only available in MP1. You could always write your own tags.

Inspoke data logic

Similar Messages

Maybe you are looking for