SNP Planned order start and end dates are not calculated correctly

Hello SNP Guru's
The SNP planned orders generated after the Heuristics run, have a start and end date based on the Activity Duration (Fixed), while the resource consumption is based on the Bucket Consumption (Variable), which is correct.
The Activity Duration (Fixed) is based on the BOM Base Quantity. So if the Activity Duration = 1 day, and if the order quantity is more than a day, the start and end dates, still shows as 1 day. So no matter what is the order quantity, the start and end dates is always = 1 day.
Does anyone have any experience in implementing any code to change the start and end dates on SNP Planned Order?
Seems like it should work as standard.
Am i missing something?
Thanks,
Mangesh

Dear Mangesh,
SNP is a infinite planning tool. If you have defined fixed duration to be 1 DAY in the activity, no matter how many quantity you input for your planned order, the order will last for one day. If the resourced is overloaded, you then run capacity levelling to
banlance the capacity. What your expected beahavior happens in PPDS planning.
Claire

Similar Messages

How the prodution order start and finis dates are changeing...?

Dear friends,
It was observed that one of my client's production order start and finish dates are changing frequently.
No user is claiming the responsibility, I feel very dificult to to find out who did the changes.
When I observed, it is happening for orders if we Revert the Teco, and that to for those orders which doesn't have the sale order assignment.
and some times it is not happenign for even for the orders which does not have the sale order assignment also.
Here it is having Forward type Sheduling.
Please help me how and when , the prodcuction orders start and finish dates will get changed.

Dear RS,
Plz check in AUT10, by giving t-code CO02 for order changes
in AUT10, u can track user id also
this may help you to some extent
Regards
kumar
Edited by: kumar kumar on Sep 17, 2009 8:32 AM

Product View - Start and End dates

Hi,
I have a material that is externally procured from a vendor to a location. In product view, I have few purchase requisitions. When i double click on it, it takes me to the details of PR. I am trying to understand what start and end dates of the PR are.
For some PRs, the start and end dates are same but for some there are is some times a day or two and even 3 in some cases.
I am wondering what makes the end date differ from start date.
There is a safety day's supply of 2.5 days
We have a transportation lane with transportation duration 23hrs.
Any of these play any role in the end date delay?

Hi,
Thanks for the reply. The vendor and the receiving location have a transportation lane defined.
What do you mean by the time duration that shows up in the T Lane corresponding to the inforecord?
Here are the times I see in transportation Lane;
Product Specific Transportation lane:
GR processing times (checked) : (No value defined) days
Planning Horizon: 0 days
Partner Horizon: 0 days
Horizon for Expctd receipts: 0 days
Horiz. Fut. Aval. Whse Stck: 0 days
Planned Delivery time: (No value Defined)
Means of Transport
Tsp. duration: 23 hrs
Bucket offset: 0.5
Period factor: 0.5
and no other times defined.
Are any of these effect the delay?
My ECC is EST and the timestream is EST. Should I change the product view (also my own data) to EST or UTC??
I have a product that has no delay between the start and end dates. The difference I see between the one that I am having problem (the start and end dates are apart ( I'm calling it bad one) by atleast a day) with and the one that has no delay(I'm calling this good one) between the start and end dates is the "Planned Delivery time.
The good one has 1 day and the bad one has nothing defined.
Does this make any difference?
Thanks.
Edited by: Raj G on Jul 17, 2008 3:36 PM

Start and End Dates check

Hi,
I have a requirement to find the list of persons who have overlapping dates.
Each person can have many start and End Dates, but only one row that has a NULL end date, the active record. If the start and end dates are overlapped, like in the example below, the second row should have a start date of 24-DEC-2006 and not 22-DEC-2006. Is it possible to list those persons who have overlapping dates/gap in the dates.
Empl_ID Start Date End Date
12345 01-JAN-2006 23-DEC-2006
12345 22-DEC-2006 13-JAN-2007
12345 14-JAN-2007 NULL
Any help is greatly appreciated.
Thanks!

Hi Patrick
I like where you are coming from. I hope you don't mind but I have extended your idea slightly to add in a PARTITION BY clause to make sure we look at records for the same person. Also, if we LAG to get a previous record shouldn't we LAG the END_DATE and compare it with the current START_DATE?
LAG(END_DATE,1) OVER (PARTITION BY EMPL_ID ORDER BY START_DATE)
Doing this, then the results would look like this:
Empl_ID Start Date End Date Lag Date
12345 01-JAN-2006 23-DEC-2006 NULL
12345 22-DEC-2006 13-JAN-2007 23-DEC-2006
12345 14-JAN-2007 NULL 13-JAN-2007
This would give the SIGN an issue because in the first record the LAG would be NULL and in the last record the END_DATE would be NULL. So it looks like some manipulation of NULLs has to take place as well which I will deal with later.
SIGN((LAG(END_DATE,1) OVER (PARTITION BY EMPL_ID ORDER BY START_DATE)) - START_DATE)
Anytime the difference between the Lag Date and the Start Date is positive this means this is an overlap which means we do need to look for any variance where the SIGN is 1.
Using the other function, we could use LEAD like this:
LEAD(START_DATE,1) OVER (PARTITION BY EMPL_ID ORDER BY START_DATE)
Doing this, then the results would look like this:
Empl_ID Start Date End Date Lead Date
12345 01-JAN-2006 23-DEC-2006 22-DEC-2006
12345 22-DEC-2006 13-JAN-2007 14-JAN-2007
12345 14-JAN-2007 NULL NULL
which when combined with SIGN becomes: SIGN((LEAD(START_DATE,1) OVER (PARTITION BY EMPL_ID ORDER BY START_DATE)) - END_DATE)
This time you would be looking for the SIGN to be -1
Personally, I think I would prefer the LEAD function because a) there would always be a START_DATE, and b) we could replace all of the possible NULLs with the SYSDATE to get a final calculation like this:
SIGN(NVL(LEAD(START_DATE,1) OVER (PARTITION BY EMPL_ID ORDER BY START_DATE),TRUNC(SYSDATE)) - NVL(END_DATE, TRUNC(SYSDATE)))
Based on the current date being 17-NOV-2009, you would now get this result:
Empl_ID Start Date End Date Lead Date
12345 01-JAN-2006 23-DEC-2006 22-DEC-2006
12345 22-DEC-2006 13-JAN-2007 14-JAN-2007
12345 14-JAN-2007 17-NOV-2009 17-NOV-2009
Best wishes
Michael

Update Contract Start and End dates via BAPI_SALESORDER_CREATEFROMDAT2

Hi Experts.
We are successfully using BAPI_SALESORDER_CREATEFROMDAT2 to create sales order.
Only problem is that the contract start and end date do not get updated.
We are passing that in ORDER_HEADER_in-CT_VALID_F and ORDER_HEADER_IN-CT_VALID_T.
After debugging, I found that there is one more table SALES_CONTRACT_IN in SD_SALESDOCUMENT_CREATE. Updating the values in that table works.
But the problem is this table is not available in BAPI_SALESORDER_CREATEFROMDAT2. How to update Contract start and end dates from this FM ?
I could not find anything in the search of this forums. So I guess this is not an issue and I am doing something wrong. Can someone suggest to me please?
Thanks in adv.
Aishi

Are you creating a contract or a sales order?

How to determine current period start and end dates

Hi All,
If given previous period start date and end date, how to determine current period start date and end date?
Suppose if given previous period start and end dates are 12/28/08 - 01/30/09, then current period start date and end date will be 01/30/09 - 02/27/09. (where 12 is the previous period, 28 is the day, 08 is the year......)
Can you please suggest an FM to determine the current period dates?
Thanks & Regards
Gowthami

>
gowthami karunya wrote:
> If given previous period start date and end date, how to determine current period start date and end date?
> Suppose if given previous period start and end dates are 12/28/08 - 01/30/09, then current period start date and end date will be 01/30/09 - 02/27/09. (where 12 is the previous period, 28 is the day, 08 is the year......)
Hello,
I am assuming you have the Company Code with you & proposing this solution.
TABLES: bkpf.
PARAMETERS:
p_bukrs TYPE bukrs.
SELECT-OPTIONS:
s_date FOR bkpf-budat.
DATA :
l_perio LIKE bkpf-monat,
l_poper TYPE poper,
l_year LIKE bkpf-gjahr,
l_spmon TYPE spmon,
l_periv TYPE periv,
l_date1 TYPE datum,
l_date2 TYPE datum.
CALL FUNCTION 'BAPI_COMPANYCODE_GET_PERIOD'
EXPORTING
    companycodeid = p_bukrs
    posting_date = s_date-high
IMPORTING
    fiscal_year   = l_year
    fiscal_period = l_perio.
CONCATENATE l_year l_perio INTO l_spmon.
* Get the next period
IF l_perio < 12.
l_perio = l_perio + 1.
ELSE.
l_perio = '01'.
l_year = l_year + 1.
ENDIF.
MOVE l_perio TO l_poper.
SELECT SINGLE periv INTO l_periv
FROM t001
WHERE bukrs = p_bukrs.
IF sy-subrc = 0.
CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
    EXPORTING
      i_gjahr        = l_year
      i_periv        = l_periv
      i_poper        = l_poper
    IMPORTING
      e_date         = l_date1
    EXCEPTIONS
      input_false    = 1
      t009_notfound = 2
      t009b_notfound = 3
      OTHERS         = 4.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'LAST_DAY_IN_PERIOD_GET'
    EXPORTING
      i_gjahr        = l_year
      i_periv        = l_periv
      i_poper        = l_poper
    IMPORTING
      e_date         = l_date2
    EXCEPTIONS
      input_false    = 1
      t009_notfound = 2
      t009b_notfound = 3
      OTHERS         = 4.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
WRITE: / l_date1, l_date2.
ENDIF.

How to input my own Validity Start and End Dates in ME21N

Hi All,
I have to change the Validity Start and Validity End date in Addiitional Data Tab of ME21 transaction( PO Create ) using default Customer Values.How Can i accomplish it?
I have used the BAdI ME_PROCESS_PO_CUST and implemented it, I have coded in the method PROCESS_HEADER.First I retrieved the data using get_data( ) method, changed the values with Customer Values and called the method set_data( ).
However my validity start and End Dates and not changing.
Even in ME21N if I create the PO with my own Validity Start and End dates, and go to ME23N to display the created PO, still in the additional data tab, the start and End dates are current date and Next date respectively.why its happening?
Thanks in advance

Hi,
Can you please let us know in which business scenario this is required.
SAP has provided separate functionality of Outline Agreement for considering validity period.
If you let us know the business scenarion some solution/workaround can be suggested.
Regards

What parameters determine Planned order production start and end dates?

Greetings
We are using the graphical planning table @ MF50 to firm Planned Orders (Basically checking off "Firm Order" field within the Planned Order). We are on ECC 6.0
Whenever I backflush, the production start and end dates get overwritten (The Basic dates do not change).
I would like to prevent this. Can someone advise me on what parameter controls how the production start and end dates getting changed?
Thank you
Hanarin

Hi,
Calculating production dates ( Lead time scheduling) are explained in detail in the SAP help URL as below:
If "Automatci Scheduling indicator" is set in the customizing for scheduling parameters then after every change relevant to scheduling, the production order is also automatically rescheduled before saving.
You need to check these settings.
regards
Datta

Contract Start and End Dates in Sales Order

Hi
I have a situation where a service item is bundled with a deliverable item. The order is as follows
Line Item    Mat                                                                 Qty            Higher Level Item
10              Item No.1 (Physical Item)                                  1
20              Item No.2 (Service Item)                                    1               10
For the deliverable item 10 , Revenue is recognized immediately. For the Service item no.20 , revenue needs to be recognized over a period of 1 Year (It is a 1 year service contract).
The whole order is created via BAPI from an external 3rd party order capture system.
In order to do revenue recognition properly for service items , SAP I believe has 2 options
1. Based on Billing plan dates
2. Based on contract start dates
Since order with both the line items need to produce 1 invoice, I cannot use billing plan . The only other option is to use contract start and end dates. I have enabled contract data at the sales order level. So when I enter the contract start and end dates manually at the line item level and set the item category to recognize revenue based on contract start and end dates based on time-based revenue recognition it is working fine.
But I need a way to automate the population of contract start and end dates at the line item level. My ABAP guy is not able to find a user exit that can change the XVEDA or any VEDA structure in any of the user exits.
I guess the SAP SD gurus out there would have definitely dealt with a situation of product bundling (Service and non-service items in the same sales order with one billing document , but seperate revenue recognition for service and non-service items)
Please help.
Thnx
Siva

Hi Siva,
Kindly let me know what criteria you want to give for automatic population of start date of contract...
Standard SAP comes with a few baseline dates for contract start date and we can control this from customization itself.
01     Today's date
02     Contract start date
04     Acceptance date
05     Installation date
06     Date contract signed
07     Billing date/Invoice date
08     CntrctStDate+contract duration
09     Contract end date
If you have some criteria which is not covered here, then let me know and i will try to provide some help then.
Thanks
Kapil Sharma

Effective start and end dates for a compensation workbench plan

Hi all,
We are having a requirement where we want to get the data respective to current plan for reporting purposes. What i have noticed is there is no such thing as effective_start_date and effective_end_date directly in all the cwb tables.
The different dates we are looking at to capture the data are
enrt_perd_start_dt and enrt_perd_end_dt
upd_strt_dt and upd_end_dt
within_yr_strt_dt and within_yr_end_dt
But we have same plan with different enrollment period and start dates. We are planning to use max(data_freeze_date or lf_evt_occrd_dt) to get
the records.
select max(nvl(bcpdx.data_freeze_date, bcpdx.lf_evt_ocrd_dt))
from ben_cwb_pl_dsgn bcpdx
where bcpdx.pl_id = p_pl_id)
Catch with this is, We have 62 business groups off which only 50 might run the plan next year and ohters might not. in that case it will also return data for all the BG's including the 12 BG's where plan has not been run for that year.
Any suggestions or help will greatly be appreciated.
Thanks
Hari

Hi Ankush,
I am also of the same opinion. Start and end dates can probably be enforced by a policy condition in AM but would lead to proliferation of policies as we would end up creating policies per role entitlement duration for a user.
Any thoughts on whether the sunrise/sunset concept of Identity Manager can be used for this requirement.
Thanks,
Srinivas

Hyperion Planning dynamic forms based on start and end date across years

Hi All,
I have a requirement where i need to be able to view a form showing periods across years that are dynamically built depending on the start and end dates. If i have a start date of 01/11/2009 and an end date of 31/7/2013 i want to be able to view a form that shows all of the periods (Jan,Feb etc) in a form that is driven by these dates, in addition it will need to show the actual scenario up to the current month and the forecast from the current month to the end date. So basically if a user inputs the start and end dates the form will display the relevant periods driven by these dates.
Any tips very much appreciated!

Hello,
This is difficult to realize, but you can get quite far with a workaround. The first question is, where do you want to input your selection of time periods? Assuming you have a webform with the complete timeline in months and years and you type in the start period and end period.
Webforms have the option to suppress rows and columns.
This can be extended with option of empty cells or not empty cells.
You will need to apply your creativity on this.
Put every month-year combination in a column and add the suppression.
Calculate the timeline between start period and end period with a dummy member, so data exists for these and columns will show.
Maybe you will need to copy the required timeline into a separate version for this, to avoid having periods which were outside the selection and still have data.
I hope these hints help a bit in this challenge.
Regards,
Philip Hulsebosch
www.trexco.nl

Start and end date in purchase order

hi everybody
I have to activate start and end date on the purchase order screen in the customer tab
can anybody tell me how to do this?

First Go to SPRO-MM-Purchasing-Purchase Order-Define document types and Identify the Field Selection Screen assigned to Doc Type
then Using the same Path Go to Define Screen Layout at Document level and select the Field Selection screen for eg: NBF and Select Administrative Data, Header Tab and Set the Fields Start & End Dates as Required and Save.
If you do not Put Tick mark against three options called Required, Optional & Display then these Fields can not Seen in Po (Ie Hide)
Generally these Fields can be Seen in Purchase Order header Tab Additional Data tab.
Regards,
Ashok

SAP CRM Tables and Fields for Contract start and End dates

Hi Experts,
Please Provide me SAP CRM Tables and Field names for the below.
SAP CRM Contracts start date and End date
SAP CRM Conditions(PROO, K007 etc....) records start and End Date.
Thanks and Regards,
Teja

correction
10 Replies Latest reply: 24 May, 2013 8:38 AM by nishant Vasudev
Tweet
SAP CRM Tables and Fields for Contract start and End dates
This question has been Answered.
Teja Dhar 12 Oct, 2009 8:03 PM
Currently Being Moderated
Hi Experts,
Please Provide me SAP CRM Tables and Field names for the below.
SAP CRM Contracts start date and End date
SAP CRM Conditions(PROO, K007 etc....) records start and End Date.
Thanks and Regards,
Teja
Correct Answer by Sreekantha Gorla on Oct 22, 2009 8:22 PM
Hi,
dates will be stores in the table 'SCAPPTSEG'.
I double checked it. This table stores all the date types of one order transactions...
The relationship is as follows..
CRMD_ORDERADM_H- guid = crmd_link-guid_hi
crmd_link-guid_set = SCAPPTSEG-APPL_GUID.
Thanks and regards,
Sreekanth
<:footer>See the answer in context
6281 Views
Topics: Customer Relationship Management
Reply
Average User Rating
0
(0 ratings)
My Rating:
Rating Saved!
Comment on your rating
Re: SAP CRM Tables and Fields for Contract start and End dates
Robert Jesionowski 14 Oct, 2009 2:23 PM (in response to Teja Dhar)
Currently Being Moderated
    Hi,
you should try with FM: CRM_DATES_READ_SINGLE_OB or CRM_DATES_READ_DB.
There is something in table SCAPPT and SCGENAPPT.
Regards, R
Report Abuse
Like (0)
Reply
Re: SAP CRM Tables and Fields for Contract start and End dates
Teja Dhar 22 Oct, 2009 5:30 PM (in response to Robert Jesionowski)
Currently Being Moderated
    Hi Robert,
I am not able to find contract start date and End dates in the tables SCAPPT and SCGENAPPT.
Can you suggest some relevant tables.
Best Regards,
Teja
Report Abuse
Like (0)
Reply
Re: SAP CRM Tables and Fields for Contract start and End dates
Sreekantha Gorla 22 Oct, 2009 2:35 PM (in response to Teja Dhar)
Currently Being Moderated
    Hi,
Table SCAPPTSEG stores the contract start and end dates.
Thanks,
Sreekanth
Report Abuse
Like (0)
Reply
Re: SAP CRM Tables and Fields for Contract start and End dates
Teja Dhar 22 Oct, 2009 5:32 PM (in response to Sreekantha Gorla)
Currently Being Moderated
    Hi Sreekanth,
I am not able to find contract start date and End dates in the table SCAPPTSEG.This is for appointments.
Can you suggest some relevant tables.
Best Regards,
Teja
Report Abuse
Like (0)
Reply
Correct AnswerRe: SAP CRM Tables and Fields for Contract start and End dates
Sreekantha Gorla 22 Oct, 2009 8:22 PM (in response to Teja Dhar)
Currently Being Moderated
    Hi,
dates will be stores in the table 'SCAPPTSEG'.
I double checked it. This table stores all the date types of one order transactions...
The relationship is as follows..
CRMD_ORDERADM_H- guid = crmd_link-guid_hi
crmd_link-guid_set = SCAPPTSEG-APPL_GUID.
Thanks and regards,
Sreekanth
Report Abuse
Like (0)
Reply
Re: SAP CRM Tables and Fields for Contract start and End dates
Wim Olieman 23 Oct, 2009 9:12 AM (in response to Sreekantha Gorla)
Currently Being Moderated
    Hi,
I can tell you where the pricing records are saved, replicated from ECC.
The data from ECC table Axxx (e.g. A304) is replicated to CRM table
CNCCRMPRSAPxxx (e.g. CNCCRMPRSAP304).
Here you can find fields TIMESTAMP_TO and TIMESTAMP_FROM.
About the dates: what Sreekantha Gorla stated, about table 'SCAPPTSEG' is correct.
What might help is to execute program "CRM_ORDER_READ". Here you can find
the relevant entries also.
regards,
Wim
Report Abuse
Like (0)
Reply
Re: SAP CRM Tables and Fields for Contract start and End dates
Teja Dhar 23 Oct, 2009 4:59 PM (in response to Teja Dhar)
Currently Being Moderated
    Hi Experts,
Thanks a lot for your support.My problem got resolved.
Best Regards,
Teja
Report Abuse
Like (0)
Reply
Re: SAP CRM Tables and Fields for Contract start and End dates
rajesh gadamsetty 27 Nov, 2009 12:29 PM (in response to Teja Dhar)
Currently Being Moderated
    Hi Teja
Please let me know how you got the dates. i got the same requirement
Report Abuse
Like (0)
Reply
Correction on above mail.
Hi Sanjay,
Can you please help me to find the contract st art date and end date fetching from the table as below
ITEM DATES:
Select guid_set from table CRMD_LINK where guid_hi              = CRMD_ORDER_I-GUID AND
                                                                          OBJTYPE_HI     = '06'
                                                                          OBJTYPE_SET = '30'.
Select * from SCAPPTSEG where APPL_GUID = guid_set.
as from the table scapptseg has some unusal fields which fields to select to get the start date and end date and on what condition and isuppose we need to convert als the same
pls suggest further on same
regards
Arora

Report for Validity Start and End Date in PO

Dear All
Is there any report where I can get PO validity start and end date which user input in addtional data header tab of PO?
Regards
Satish Kumar

Hi,
Yes, It is available standard report using T-code ME2N - Purchasing Document (PO) Per Document Number, enter the T-code and provide the following input data's are as follows.
Scope of List                 : ALV ( for Ms-Excel format report)
Plant                               :   __________ to __________ (if required)
Document Date              : ____________ to ___________ (if Required)
Execute the report shown by default in excel format and if required PO validity start and end data, you have to select Change Layout button and open new window options screen right side field option as Validity Per.Start, Validity Period End, Commutative number field data's are selected and click <--- arrow button and then click bottom tick marked button. Now, the report shown your requirement.
Hope, it is useful for you,
Regards,
K.Rajendran

Calculate Start and End date in Connect By -- When Hirerchy Changes

/* Formatted on 5/20/2013 9:53:00 AM (QP5 v5.115.810.9015) */
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Hello , Can some one Please help me or Guide me in calculating Start and End dates for the below logic
I want to calculate the Manager Hirerchy for the given Agent.
Then Below Query is working fine and its giving me the desired results
But when there is a change in the Manager Hirerchy or Manager gets Promoted
Then i need to calculate the start date and end date.
CREATE TABLE PERSON_DTL
SID                 VARCHAR2(10 BYTE),
EMP_MGRS_ID         VARCHAR2(10 BYTE),
START_EFFECTIVE_DT DATE,
END_EFFECTIVE_DT    DATE
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M100', 'M107', TO_DATE('05/20/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M101', 'M102', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('05/18/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('A100', 'M100', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M100', 'M101', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('05/18/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M107', 'M102', TO_DATE('05/20/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M102', 'M103', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M103', 'M104', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('A101', 'M105', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
Insert into PERSON_DTL
   (SID, EMP_MGRS_ID, START_EFFECTIVE_DT, END_EFFECTIVE_DT)
Values
   ('M105', 'M106', TO_DATE('01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), TO_DATE('12/31/9999 00:00:00', 'MM/DD/YYYY HH24:MI:SS'));
COMMIT;
SELECT   CONNECT_BY_ROOT (b.sid) agent_sid,
             TRIM (
                LEADING ',' FROM    SYS_CONNECT_BY_PATH (b.sid, ',')
                                 || ','
                                 || b.emp_mgrs_id
                PATH,
             START_EFFECTIVE_DT Start_dt,
             END_EFFECTIVE_DT End_dt
      FROM   PERSON_DTL b
     WHERE   CONNECT_BY_ISLEAF = 1
START WITH   sid IN ('A101', 'A100')
CONNECT BY   PRIOR b.emp_mgrs_id = b.sid
This is the results that i am getting now.
AGENT_SID    PATH                       START_DT    END_DT
A100    A100,M100,M101,M102,M103,M104    1/1/2010    12/31/9999
A100    A100,M100,M107,M102,M103,M104    1/1/2010    12/31/9999
A101    A101,M105,M106                   1/1/2010    12/31/9999
Results Required
A100    A100,M100,M101,M102,M103,M104    1/1/2010    5/18/2013
A100    A100,M100,M107,M102,M103,M104    5/20/2013   12/31/9999
A101    A101,M105,M106                   1/1/2010    12/31/9999

May be this..
SQL> select agent_sid,max(path) path,max(start_dt) start_dt,
2         min(end_dt) end_dt
3 from
4 (
5    select agent_sid,path,start_dt,end_dt,
6           sum(flg) over(order by rn) sm
7    from
8    (
9      select agent_sid,
10             path,
11             start_dt,
12             end_dt,rn,
13             case when path like lag(path) over(order by rn)||'%' then 0 else 1 end flg
14      from
15      (
16        SELECT   CONNECT_BY_ROOT (b.sid) agent_sid,
17                 TRIM (
18                    LEADING ',' FROM    SYS_CONNECT_BY_PATH (b.sid, ',')
19                                     || ','
20                                     || b.emp_mgrs_id
21                 )
22                  PATH,
23                 START_EFFECTIVE_DT Start_dt,
24                 END_EFFECTIVE_DT End_dt,rownum rn
25        FROM   PERSON_DTL b
26        START WITH   sid IN ('A101', 'A100')
27        CONNECT BY   PRIOR b.emp_mgrs_id = b.sid
28      )
29    )
30 )
31 group by agent_sid,sm
32 order by agent_sid;
AGENT_SID PATH                                     START_DT END_DT
A100       A100,M100,M101,M102,M103,M104            01-JAN-10 18-MAY-13
A100       A100,M100,M107,M102,M103,M104            20-MAY-13 31-DEC-99
A101       A101,M105,M106                           01-JAN-10 31-DEC-99Edited by: jeneesh on May 20, 2013 7:54 PM
Not thoroughly tested.And not sure whether an easy way exists..

SNP Planned order start and end dates are not calculated correctly

Similar Messages

Maybe you are looking for