Key date problem

Hi Friends,
I want to create the routing for material.but i have one problem. when i create the routing for material on the intial screen of the routing one option is there . ie KEY DATE. the system shows automatically 02.02.2006. but iwant to create 02.04.2010. but system not allowed tom at that date. please give me a help how can i change the KEY date from 2006 to 2010.
Thanks
Venkat

Dear,
Are you using the change number to create routing? Then system will pick up date from change master.
key date of the routing to be read and the change number else by default it will take today date.
The field 'Key date' (RC271-STTAG) is predefined with the date entered last. If you call the transaction with different key dates you must ensure that the key date is always entered correctly.
Also check SY-DATUM system date. Or any transaction variant create for CA01 with default value.
Regards,
R.Brahmankar

Similar Messages

Bw time dependent hierarchy authorization in Hr - Key date problem - 0orgunit

Hello Gurus,
I'm facing a problem with the 0Orgunit hierarchy authorization.
In the Rsecadmin screen we set the hierarchy authorization for 0orgunit characteristic, before selecting the hierarchy node, we enter the key date.
I tried many cases, but neither of the key dates gives the correct results in the report. (Todays date, 01.01.1900, 31.12.9999 etc..)
In the report the key date variable is generated by RSTHJTMAINT transaction. I guess, this is creating a problem with the authorization key date.
A similar problem is told in the following link as well:
http://scn.sap.com/thread/1437951
I spend some hours, and tried many possibilities (validity period etc.), but I could'nt get it worked.
I'm not sure if I had this error before 7.31 update.
With this opportunity, I want to thank you every one in the Sdn community. It helps a lot for resolving our issues and sharing the knowledge.
Thanks a lot.
Regards.

Hi Norbert,
Can you check that the SAP note 1301644 has been applied in your system.
Best Regards,
Des Gallagher

Key Date variable; Interval in query properties for Time Dep. Masterdata

Hi,
I've been searching on the forum, and I think I know the answer already, but still I'd like
to ask you all whether it's possible to create a Key Date Interval variable to be used in the query properties.
As far as I can see you can only report by a single key date used in the query properties field for time dependant masterdata, but my customer has asked me to investigate the possibility to enter a date range.
As all masterdata is time dependant I don't see how this would work, but if someone can shine a light on this maybe there is a solution available?
Thanks for your help.
M.

Hi marc
I understand your problem.
I had an idea for a workaround.
If you can create master data compounded with Valid from and Valid to both of these characteristics , how the query is computing
the keyfigures.
Every change in valid from or valid to is unique for the system in this case.
Thanks
N.Ganesh

Key date for a query

Dear All,
I have created a customer exit variable on key date of a query.
With this input variable i am first asking user to input one particular date say he enters 31.12.2010 then i am trying to add 1 more day to it and making it 01.01.2011.
I have put a break point in the code but it does not stop the processing there.. report executes directly taking the first user input.
I want to add 1 more day to the user entered date and this modifiied date should be the input date for key date field.
Below is my code.
WHEN 'ZCAL_DAY_EXT'.
    IF I_STEP = 2. "after the popup
      LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
      WHERE VNAM = 'ZCAL_DAY_EXT'.
        CLEAR L_S_RANGE.
      ENDLOOP.
      DATA: v_temp like sy-datum.
      v_temp = loc_var_range-low.
      v_temp = v_temp + 1.
      L_S_RANGE-LOW = v_temp.
      L_S_RANGE-SIGN = 'I'.
      L_S_RANGE-OPT = 'EQ'.
      APPEND L_S_RANGE TO E_T_RANGE.
    ENDIF.
Do let me know where am i going wrong? Or is it we cannot use customer exit with Key date.
Thanks & Regards,
Anup
Edited by: Anup Chaudhari on Aug 2, 2011 7:16 AM

Hi Anup,
Basically I_STEP = 1 is used for populating the default value which will be shown on selection screen and I_STEP = 2 is the step in which you does the processing on variable values which are entered on selection screen.
I am surprised that your internal table is empty, actually it is supposed to contain all the variable values which are entered in I_STEP = 1.
Can you try to add some more variables along with the current variable and check whether their value is coming in the internal table or not?
Finally what you can try is get the user input date in one variable and then create another customer exit variable in which you will calculate the new value and use this variable in Key date, the problem might be that we are trying to modify the same variable, actually it should not be the problem but I have no clue what is happening and you can just try this alternative.
Regards,
Durgesh.

Passing of Key Date in RRI

Hi Folks,
This problem is related to passing of Key Date value in RRI. We have the Basic(Source) Report in one server & Detail(Target) Report in another server. Now my requirement is to pass Key Date (Query --> Properties) to Target query. I think only variable values & selection will be passed to the target query, So I had a variable in Source report which takes input from user (or default value goes). Now how can this be received by the Key date of the Target query. Iam getting "#" in the Key date of Target query. Mind you once again both queries are on different servers.
Thanks & regards,
Manoj.

Found the answer, thanks to another thread:
Function RRS_VAR_VALUE_FROM_MEMORY_GET with I_VNAM equal to the key date variable returns the value of the key date.
DP

Mapping error at deployment with foreign key data rule

I have created data rules for enabling foreign key constraints. There are 4 foreign key constraints on the fact table.
For the 1st foreign key ... its a single key match key1 on table 1
For the others, its a composite key .. key1 and key2 on table 2
key1 and key3 on table 3
key1 and key4 on table 4
When I implement with the single key foreign key constraint the mapping works fine. But when I apply the other foreign key data rules for composite keys, I get the following message while deploying ....
M_CNT Create Warning ORA-06550: line 209, column 3:
PL/SQL: ORA-00909: invalid number of arguments
M_CNT Create Warning ORA-06550: line 520, column 65530:
PL/SQL: SQL Statement ignored
M_CNT Create Warning ORA-06550: line 56, column 65530:
PL/SQL: SQL Statement ignored
M_CNT Create Warning ORA-06550: line 673, column 3:
PL/SQL: ORA-00909: invalid number of arguments
The data rule setup done is type Referential
Specify the number of attributes in row relationship - 2
Specify the referencing cardinality of row relationship
Minimum Count 1 Maximum Count n
Specify the referenced cardinality of row relationship
Minimum Count 1 Maximum Count n
What is it that I am doing wrong ?
Any suggestions. Help !!!!
Regards,
AW

Hi AW,
How can I overcome this situation ?The best solution as suggested by Jörg is use of surrogate keys.
For every production key (composite or single) generate a corresponding surrogate key using sequence operator in staging area.
This will not just solve your problem but it will be faster also (the joins will be faster with system-generated sequence numbers),
In a data warehouse use of production keys as primary key for linking with (foreign key) is not recommended, keep the production keys as additional attributes.
Regards,

Exception CX_SY_MOVE_CAST_ERROR when Process Reassignments for Key Date Results

Hi Experts,
I got an exception error when process reassignments for key date results(transaction code /BA1/FG_PR_KR_REASS) in BANK ANALYZER, did anyone get the same problem before? any solutions?
the process sequences is listed below:
1,,Set SDL Timestamp,,              /BA1/B0_CLOSE_SDL
2,,Generate Positions,,              /BA1/F2_PB_PR
3,,Aggregate Financial Transactions,,,,          /BA1/FG_PR_FT
4,,Prepare Business Transactions for Aggregation,,    /BA1/FG_PR_BT_PRE
5,,Process Reassignments for Business Transactions,,    /BA1/FG_PR_RABT
6,,Aggregate Business Transactions,,/BA1/FG_PR_BT
7,,Process Reassignments for Key Date Results,,    /BA1/FG_PR_KR_REASS
7.a),,Subcomponent view,,subcomponent=S_SVAC01 ,,OK
7.b),,Subcomponent view,,subcomponent=S_SVFT01 ,,Exception
I nenver changed subcomponent settings, they are all SAP delivered.
Exception CX_SY_NO_HANDLER: An exception with the type
CX_SY_MOVE_CAST_ERROR occurred, but was neither handled locally, nor
declared in a RAISING clause
Message no. /BA1/AL_X0_M_H000
Exception CX_SY_MOVE_CAST_ERROR: Source type
\CLASS-POOL=/BA1/CL_AL_FG_MD_SUB_CMP_VIEW\CLASS=LCL_SCV_FT2AGGRO is not
compatible, forthe purposes of assignment, with target type \INTE
Message no. /BA1/AL_X0_M_H000
Thanks!

Hi Abhi,
in do_prepare_output you are getting mixed entity which is combination of bol entity and value node.
you can get the bol entity from mixed node by calling a method get_model_node similarly to get value node entity get_value mode method is available check the class CL_BSP_WD_MIXED_NODE methos, you will get an idea.
Cheers,
Sumit Mittal

Cannot change variable for key date in aggregate

Hello,
when I drag time-dependant attributes into an aggregates definition I am prompted to enter a key date or choose a variable for that. I then activate and fill that aggregate. Afterwards I deactivate it and remove the time-dependant attributes so there are no time-dependant attributes in the definition any longer. I then want to also remove the variable for the key date but I can't do so. This property is greyed out and there is no context menu for the entry "Variable for key date".
The SAP Help says this should be possible by changing the key date variable through the context menu (see http://help.sap.com/saphelp_nw04/helpdata/en/7d/eb683cc5e8ca68e10000000a114084/frameset.htm).
Has anyone faced this problem, too? I do not want to redefine my aggregate as this is not an elegant solution to the problem.
Thanks to any answers in advance.
Regards,
Philipp

Hey Karim,
Because you have time dependent attributes in the aggregate you need to specify key date:
check this
http://help.sap.com/saphelp_nw70/helpdata/en/44/70f4bb1ffb591ae10000000a1553f7/frameset.htm

SAP BW Hiearchy Key Date Variables - Web Intelligence

Hi,
I have couple of issues / scenarios which are not working as expected. First, as I understand that hiearchy variables are supported by WebI.
Scenario 1
I have created a hiearchy key date variable within the report and made it optional. I run the report an no key date appears. It should appear. If I then make the hiearchy key date to mandatory I get a database error. Looks like there is a problem with hierarchy key date variables?
Scenario 2.
I change the hierarchy key date so it uses the key date of the query (so no longer a variable).
As an example,I have employee "Employee X" assigned to "team A." This team moves from the Desktop team to the IT team on the 01.04.2011.
IT
   A - 01.04.2011 -> 31.12.9999
Desktop
   A - 01.01.2011 -> 31.03.2011
I have a hiearchy variable so I can select a team as requied (using the object 0ORGUNIT) If I run the report using the key date 01.04.2011 the WebI report displays the current hierarchy nodes i.e.
IT
   A
and the data shows correctly,
If I now re-run the report using the key date 01.03.2011 in the selection screen in the WebI report the following is still shown
IT
   A
If I select team A - no data is displayed. So it looks like via the use of the "Use query key date" for the hierarchy key date works but not in selection screen which is a problem.
Is this a bug or am I doing something wrong?
Thanks

Hi,
I have now got scenario 2 working - well I didnt do anything apart from run it InfoView and it is fine. But for some reason does not work in WebI Rich client - I will have a look into this furrher but am happy that it works in infoview. Sceanrio 1 is no working still I have run it in InfoView and get the error "A database error occured. The database error text is: Failed to execute MDX query. Reason: Specify a value for variable Hierarchy Key Date. (WIS 10901)" This hiearchy key date is th variable which I have created and assigend to the hiearchy so that a "hierarchy date" can be selected.
+Scenario 1+
+I have created a hiearchy key date variable within the report and made it optional. I run the report an no key date appears. It should appear. If I then make the hiearchy key date to mandatory I get a database error. Looks like there is a problem with hierarchy key date variables?+
Any help is appreciated.
Thanks.
Edited by: Leo on Apr 25, 2011 4:20 PM

Using a range of dates for Key Date

In a HR Bi data warehouse, we have a position-to-position hierarchy, where each of the nodes are time dependent. So, it shows for each node, valid from and valid to dates, and all the employees who are reporting to that position. This hierarchy is built on the infoobject 0HRPOSITION, which is maintained in R/3 and extracted to BI.
Let us take an example: Position 1000 is valid from 1-1-2006 to 6-30-2006 Employees reporting to this position are A,B,C,D
Position 1000 is valid from 7-1-2006 to 12-31-9999 Employees reporting to this position are A,E,F,G
When a user chooses the position 1000, and date range 1-1-2006 to 12-31-2006, it show the complete list of employees as
A,B,C,D,E,F,G.
Because the Keydate can only be a single value, and it is automatically taking today's date, and pulling the nodes based on that.
I have created a hierarchy node variable on the 0HRPOSITION infoObject, and entered the value 1000, with no value for the keydate.
The system is simply showing employees, A,E,F and G. That is my problem
My requirement is this: I like to be able to give a date range, (for the hierarchy) say from 1-1-2006 to 12/31/2006 and get the complete list of Employees, which is A,B,C,D,E,F,G.
Is this possible? Can I change the way this hierarchy is defined so that I can pull the possible values for a range?

Thank you Ajay.
After some thinking, I have realized that these options will not work.
We have a position-to-position hierarchy that shows who reports to who in the organization. This hierarchy is built on the Infoobject 0HRPOSITION. Each node in this hierarchy has is time-dependent. Note that, the entire hierarchy is not timedependent. Only the individual position nodes are time-dependent.
This 0HRPOSITION infoobject exists in the Heacount cube as one of the characteristics. Here is my requirement.
1. I want to show in a report, all the employees (directly or indirectly) reporting to a manager for a period of say, 1 year?
I know that I can specify a key date for the hierarchy 0HRPOSITION, then the report will show all the employees (direct and indirect) reporting to a position say 6/30/2008. I don't want this for a specific date, I want to get ALL the employees (direct and indirect) reporting to a position in a range of dates( say 1 year)
Does that make sense? How do we achieve this goal?

Primary key, unique key impdp problem

Hi, during my impdp I came across problems with constraints being violated. So I disabled all constraints in a proper order. It didn't help. There are still the same errors. I checked some individual constraints that were problematic and it turned out that they were all disabled as I expected. I don't understand why datapump still shows these errors despite constraints are DISABLED.

But if the unique index exists on the target table it does not matter if the PK is disabled or not. You would need to drop the index; however, this shows you have a data problem.
Why do you have duplicate keys? If you import duplicates then rebuilding the unique index would result in an error.
Do you need to truncate or drop some of the target tables before importing?
These are points I raised in my first response and which you have not addressed in your answer.
HTH -- Mark D Powell --

WAD 3.5 - Pass a date to Hierarchical Filter Selection Key Date

I'm working in WAD 3.5, with 3.5 queries. I currently have a Hierarchical Filter Selection on Org Unit using a query with no Key Date set, so as to pull the most current version of the hierarchy. This filter selection is then applied to several charts and tables below.
I need the web app to initially display this current version, but also allow the user to select a date, which triggers a requery of the Hierarchical Filter Selection data provider, passing the date selection to the key date of the data provider query. 1) how do I pass the date (currently from a drop down) to the key date of the other query, and 2) how do I force a requery of the Hierarchical Filter Selection?
The problem we are attempting to address is that if Org Unit A contained Org Units 1, 2, and 3 at the end of 2007, but only 1 and 2 today, the Hierarchical Filter Selection will not show #3, thus not allowing the user to drill down to it. If they can choose the version/point in time of the hierarchy, they will then have the ability to drill down on the older Org Units.
Thanks!
Anna
Edited by: Anna Kamrath on Feb 6, 2009 8:52 AM

Our solution was to modify the user exit variables and store the values in a MEMORY ID and restore from there.

How to get PNP Org Structure to reflect the org structure as of key date?

I created a custom program using the PNP logical database. I defined a custom report category indicating the selection period = employee selection period and allowing org.structure. Im also using the standard SAP PNP_DEFAULT selection view.
Inside my ABAP I initialize the pnpbegda and pnpbegps to reflect 20060930. Upon Execution the key date reflects 09/30/2006. I click on the org.structure button. The org.structure displayed reflects the one as of today rather than as of Sept-30.
During run debug I see that the RP_PNP_ORGSTRUCTURE program, LRPPNU11, calls function 'RH_TYPE_STRUC_HELP' to get the org.structure. The call to this function passes 09/30/2006 for the begda and endda, but it still returns the latest org.structure. I did some playing with this function and found that if I also pass the ACT_SEARCH_WEGID as ORGEH it works.
Any idea on how I can get the LRPPNU11 program to pass the ACT_SEARCH_WEGID or the subsequent called functions to process for ORGEH?

thanks. but maybe I don't describe my problem well.
I use javascript to get some information such as position, sytle of each elements and then pass these to javafx. So the besides the dom tree, I can get more information about elements.
I need to pass them back to javafx.
if node support setUserData, I can associate them to each Node/Element. But webkit don't support this feature.
BTW, If javascript pass a object to javafx. it can only deal with primary types such as string, numeric. But I need pass back a complicated javascript object like:
{name:"parent", children:[{name:"child1"},{name:"child2"}]
I can use (String)JSObject.getMember("name"); and JSObject children=JSObject.getMember("children");
but I can't cast children to Object[] or JSObject[].
so I have to use some tricky to convert Javascript Object to json string and then in javafx convert it back to Object tree.
Edited by: user12956197 on 2013-3-11 上午4:27

Key date description - is it possible?

Dear all,
we are looking for means to enable users to see/check key date descriptions when entering/choosing key date as parameter. Further problem is that second parameter is hierarchy variable for chosing node(s) from time-dependent hierarchy, i.e. appropriate hierarchy is derived from key date (on the same parameter screen). It worked fine until this key date description feature was requested.
Basically we just want dates (0DATE based!?) to have text (description). Until now, we found no solution.
Any workarounds?
Kind regrads, Josko.
Edited by: Josko Poljak on Dec 15, 2009 5:21 PM

Dear all,
we solved it. Here is the solution. We created IO Z_ITER with key (char 60) that acts as description and two nav. attributes 0DATEFROM and 0DATETO. We do have two query variables Z_ITER_UI (based on IO Z_ITER) which is user input, it serves for user to choose from descriptions (Z_ITER key). Second var. Z_ITER_RP acts as key date . It is replacement path variable based on 0DATE and it inherits 0DATEFROM attribute from var. Z_ITER_UI. Define Z_ITER key format or/and hierarchy for easier sorting and thats it.
Kind regards, Josko.

Program RFKORD10 - Print program: Account Statement -- Changing Key dates

Hi Experts,
Greetings, I need help in program <b>RFKORD10 - Print program: Account Statement.</b> I have a requirement to copy in zprogram. The main purpose is the key dates in acct statement should be based on BSEG-ZFBDT. Is there any option on how to change this in functional side. Because I read the program documentation like this
You can extend this list of selectable fields in order to meet your
requirements. To do so, you can use a repair correction to import fields
from tables BKPF and BSEG, that are not yet in table RF140W, into table
RF140WZZ. When doing so, you must take care to use the field names and
data elements from the standard tables, as the fields in table RF140WZZ
are supplied using the names from the documents.
Is there anyone know how to use this "Repair Correction"
Thanks
Please help...

Hi Sridhar
thanks for the reply, I am a developer and i figure it out on how solve this problem. I wanna know if there is anyway to solve this in functional side, without copying the standard program. Like what i've said it is indicated in the documentation that it can be change. anyway thanks again....

Key date problem

Similar Messages

Maybe you are looking for