Fields missing in Characteristic Relationship

Hi Experts,
I want to derive Currency Key from Company code using Characteristic Relationship. I am using 'With Derivation' and master data attributes. But in the source fields I see only two fields Cost Center and Controlling Area. Not sure why I am missing rest of the fields from the Cube. Does this mean, I have to have Aggregation levels maintained before I look at Characteristic Relationships??
Thanks,
DV

Hi,
derivation is used to fill characteristic values from other characteristics in the InfoCube. So to derive 'Currency Key' from 'Company Code' means that both characteristics have to be inculded in your InfoCube. I think, Currency Key is an attribute of Company code, so you can create a derivation relation based on characteristic Company Code.
If you don't need 'Currency Key' in the InfoCube, you also may use Currency Key as a navigation attribute. Then you need not characteristic relationship for this, the system automatically know about the link between Company Code and Currency Key.
Regards,
Gregor

Similar Messages

Characteristic Relationship BI-IP

Hi,
I am trying to create the following characteristic relationship on real time planning cube.
Within the realtime cube I have 0fiscper and 0fiscvarnt being populated.
I also want to calculate 0calquarter and 0halfyear1.
For this I have created a DSO which has 0fiscper and 0fiscvarnt as the key and 0calquarter and 0halfyear1 as the data fields. I am populating 0fiscper and 0fiscvarnt during the upload and calculating 0calquarter and 0halfyear1 via a routine.
I am now trying to create the characteristic relationship, but when I enter the DSO technical name, I get the following error message:
DataStore object '....' does not have a data field from the InfoProvider; this object is invalid here.
Any ideas why this happening, all the fields in the DSO exist in the realtime cube.
Thanks
DJL

Hi
For time characteristics, there are standard characteristic relationships.. dont see why need to create them.
if it is for fiscvarnt-fiscper combination: guess no need for other things.
Also if u r specifying DSO name in planning modeler, I guess u can look up the DSO thru F4 help.
rgds
Deepak

IP - Characteristic Relationship with exit class URGENT

Hi experts,
I need to derive two infoobjects from other one. I know that I have to use a exit class and there implement the ABAP code for especify the derivation.
I have copied the exit class CL_RSPLS_CR_EXIT_BASE. I suppose that the code of the derivation has to be implemented in the IF_RSPLS_CR_METHODS~DERIVE method. But, does anybody know the structure witch contain the source and target fields where is/are defined?
Thanks in advanced.

Hi,
set a break-point in the factory method get_instance to check whether the class is called. In the planning modeler make sure that you use an external break-point.
Or use rsrt an change a cell value: Derivation is called in the delta buffer to derive from the fields contained in the aggregation level. So check also that the source fields are contained in the aggregation level or can be derived via a a chain of derivations.
Also make sure that all source fields have to be non-initial. The system will not call derivation for initial source fields since in this case there is not unique target, cf. http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
Remark: The attached document of note 994853 is about the disaggregation feature but it also contains a section about the characteristic relationships. Observe also that the template exit classes are documented in SE24.
Regards,
Gregor

Characteristic Relationship - Derive week from 0CALWEEK

I need an exit for characteristic relationship, deriving week (to a custom characteristic ZWEEK) from 0CALWEEK. I.e. I should be filling ZWEEK with the week number 1-52 based on 0CALWEEK's YYYYWW. Anyone have something like this already in place and would perhaps be so generous as to share the code or experiences?
Regards,
Thomas

Hi Thomas,
here you are:
FUNCTION Z_DERIVE_ZWEEK.
*"*"Local interface:
*"       IMPORTING
*"             VALUE(I_AREA) TYPE UPC_Y_AREA
*"             REFERENCE(ITO_CHA) TYPE UPC_YTO_CHA
*"             REFERENCE(ITO_SOURCE) TYPE UPC_YTO_CHA
*"             REFERENCE(ITO_TARGET) TYPE UPC_YTO_CHA
*"       CHANGING
*"             REFERENCE(XS_CHAS) TYPE ANY
*"       EXCEPTIONS
*"              FAILED
FIELD-SYMBOLS: <calweek> TYPE ANY, <zweek> TYPE ANY.
READ TABLE ito_source TRANSPORTING NO FIELDS WITH
    KEY CHANM = '0CALWEEK'.
if sy-subrc = 0.
    ASSIGN COMPONENT '0CALWEEK' OF STRUCTURE xs_chas TO <calweek>.
    READ TABLE ito_target TRANSPORTING NO FIELDS WITH
      KEY CHANM = 'ZWEEK'.
    if sy-subrc = 0.
      ASSIGN COMPONENT 'ZWEEK' OF STRUCTURE xs_chas TO <zweek>.
      <zweek> = <calweek>+4(2).
    endif.
endif.
ENDFUNCTION.
Regards,
Marc
SAP NetWeaver RIG

Characteristic Relationship

I am using a characteristic relationship (without derivation) on Employee for Cost Center.
I have a cube that contains Key figures for each period for each planned cost center (with employee = #). I am wanting to copy these key figures to the employees within each cost center.
ex:
CC   Plan Hrs
1238 155
2345 200
3425 175
I have employee 10134 (CC = 1238)
I am wanting to use ONE copy function to copy all key figures changing Employee:
Employee = # to Employee = 10134
I was hoping setting the Characteristic relationship would only copy the plan hours according to Master Cost Center (155 hours to 10134, etc). Instead, it will fail stating
"Combination '10134,DEL/2345' is invalid; Valid is '10134,DEL/1238': Characteristic 0EMPLOYEE'".
How can I set this characteristic relationship to only allow the copy to employees within the cost center without having it fail? I do not want to allow this function to copy the KF for CC 3425 to employees within another cost center.
Thanks!

Hi,
it seems that you have combinations employee = #, CC = DEL/2345 in your copy source, the system then tries to copy such combinations to '10134,DEL/2345' and this combination is not valid. This will only happen in the special case that you have employee = # as copy source and 10134 as target and employee is the only field to be changed, i.e. source and target have only single value selections.
You can work around this effect as follows: allow more more values in the target for employee or by adding CC to the fields to be changed (if this characteristic is not restricted to a single value in the filter used in the planning function).
Another option is to decomment the following lines in class CL_RSPLFC_COPY, method IF_RSPLFA_SRVTYPE_IMP_EXEC_REF~EXECUTE
        ELSE.
        .... restriction to single values => check the combination (much faster)
          MOVE-CORRESPONDING <s_block_line> TO <s_chas>.
          LOOP AT l_s_rule-t_to_sel INTO l_s_sel.
            ASSIGN COMPONENT l_s_sel-chanm OF STRUCTURE <s_chas> TO <cha>.
          precondition: l_s_sel-t_rng contains just one line with sign = 'I' and opt = 'Eq'
            LOOP AT l_s_sel-t_rng INTO l_s_rng.
              <cha> = l_s_rng-low.
              EXIT.
            ENDLOOP.
          ENDLOOP.
          cl_rsplfr_controller=>p_r_cr_controller->check( EXPORTING i_s_chas = <s_chas>
                                    IMPORTING e_t_mesg = l_t_contr_msg
                                              e_is_valid = l_is_valid ).
          IF l_is_valid = abap_false.
            continue.                                                                                "<== insert
          create context without real message
           me->msg_with_context( EXPORTING i_r_msg_src = l_r_msg         "<== begin of change
                                           i_s_rule = l_s_rule
                                 CHANGING c_r_msg_trgt = l_r_i_msg ).
           LOOP AT l_t_contr_msg INTO l_s_contr_msg.
             MESSAGE ID l_s_contr_msg-msgid TYPE 'E' NUMBER l_s_contr_msg-msgno
                   WITH l_s_contr_msg-msgv1 l_s_contr_msg-msgv2
                        l_s_contr_msg-msgv3 l_s_contr_msg-msgv4
                   INTO l_dummy.
             l_r_i_msg->add_msg( ).
           ENDLOOP.
           RETURN. " all messages are error. => planning function stops.     "<== end of change
          ENDIF.
Regards,
Gregor

Characteristic relationship with Exit class is not applied correctly

We are using a characteristic relationship (with derivation) type Exit class. For that we have created class ZCL_RSPLS_ARTICLE_FROM_PLMOD as a copy of the standard class CL_RSPLS_CR_EXIT_BASE.
Target and source characteristics are members of the aggregation level.
We want to generate a list of valid combinations of characteristics planning models and articles which should be planned in the planning query.
For that we are using the method IF_RSPLS_CR_METHODS~CREATE:
Source is characteristic Model ZMATMOD and we determine in the exit class all active articles ZMATART.
We get a list of active (planning relevant) models and articles in our exit class (table e_th_chas).
--> For instance 6 combinations
Until here everything works fine.
The problem is that in the query 8 combinations are displayed.
We have no idea why more than the generated combinations are displayed.
One reason could be that the characteristic article ZMATART is an attribute from characteristic model ZMATMOD.
So from a master data point of view 8 combinations would be relevant.
But we use the exit class in order to reduce the number of combinations to planning relevant items.
If we use the method IF_RSPLS_CR_METHODS~CHECK we could flag the 2 combinations which are not planning relevant to not valid.
But these are then displayed in the query. 6 combinations in change mode; 2 combinations in display mode. This would not help us.
We would like to see only the planning relevant combinations  6 combinations
Can anyone please help me urgently?
Best regards
Martin

Hi,
set a break-point in the factory method get_instance to check whether the class is called. In the planning modeler make sure that you use an external break-point.
Or use rsrt an change a cell value: Derivation is called in the delta buffer to derive from the fields contained in the aggregation level. So check also that the source fields are contained in the aggregation level or can be derived via a a chain of derivations.
Also make sure that all source fields have to be non-initial. The system will not call derivation for initial source fields since in this case there is not unique target, cf. http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3d0f31b70701e10000000a422035/frameset.htm
Remark: The attached document of note 994853 is about the disaggregation feature but it also contains a section about the characteristic relationships. Observe also that the template exit classes are documented in SE24.
Regards,
Gregor

Characteristic relationships with derivation. I don't quite understand...

Hi, experts!
I'm trying to figure out all about using derivation in characteristic relationships and even though I seem to generally understand what it's for, some moments are still unclear.
Let me describe the task: I have, for example, 10 item categories, all of them are in the real time info-cube. I have unique combinations for them, which are loaded into the DSO and I'm trying to create char. rel-ps based on that DSO.
In the first aggregation level I'm using only the first 3 levels of item categories. The other 7 are not included.
Let's assume I've planned my key figures for those 3 levels, and saved the plan. I need the system to distribute (disaggregate) the values among the remaining 7 category levels, so when I open another plan, based on an aggregation level that includes all 10 item categories, I would see all the data correctly and all the necessary combinations.
As I understand, in that case I need to have characteristic relationships with derivation.
But SAP demands that all the "target" characteristics should be held in the "Data Fields" section of DSO. And therefore they won't be key fields.
I don't really get it - why should they be "data fields"? If I use them as "Data Fields" in the DSO, I won't be able to load all the possible combinations, because in some cases these 3 item categories that are the keys of the DSO, will match, only the remaining 7 will be different...
How do I solve the described task?
Thanks.
Best regards,
Andrey

Hi Andrey,
derivation is a function, given the source fields the derive functions fills the target fields. In other words, given a relation with two characteristics A, B with A source and B target the derive function F modeled in the relation 'calculates' F(a) = b with a, b members of A,B, respecitvely. Since F is a function for a given a there are not two differen b1, b2 with F(a) = b1 and F(a) = b2.
Using a derivation relation modeled in a data store the function F is defined by the active table of the data store. So A has to be the key and B has to be a an attribute (non-key). If this is not the case and A, B are key fields you can have the combinations
A    B
a    b1
a    b2
and this is by defintion not a derivation relation, but an n:m relation.
On other words derivation fills redundant fields.
It seems that you want to do just the opposite. It is a common problem to plan on a 'higher level' and to disaggregate from the higher level to lower levels, but of course only valid combinations should get values. You can use planning functions or the disaggregation feature in the query. Characteristic relationships are used to model the valid combinations.
An example is as follows: We have Product -> Product Group -> Product line, the arrows indicate a derivation relation. The query uses all three characteristics in the aggregation level but has only Product Line and Product Group in the rows. Using disaggregation in the query changed key figure values will be disaggregated to Product (and maybe other characteristics used in the aggregation level). The system uses characteristic relationships that can be applied for the aggregation level to check the consistency of the records. Observe that a derivation relations can also be used to check the consistency of a combinations if both source and target fields are filled. Observe that for disaggregation of the above mentiond fields are filled and thus can and have to be checked using the derivation relations (and maybe other modeled relations).If 'access mode for result values' based on characteristic relationships is used in the query the relations can also be used to create all valid combinations needed for disaggregation.
So you have to check whether the constraints you need are really of type n:m, then all fields have to be key in the data store or whether you have a derivation relation. By the way, derivations can be combined as in the Product -> Product Group (first relation) and Product Group -> Product Line (secdond relation) example.
Regards,
Gregor

CMR-Field missing

None of my container managed relationships get added to the descriptors in
the ejb-jar.xml file just wondering if anyone has a solution.
thanks
Glenn

Hi Shankar,
You may check the following points to know cause.
01. Get the message text by using message category and message number.
Message text would be "%1 field missing"
SQL> select message_text from ci_msg_l where message_nbr='253' and message_cat_nbr='25';
MESSAGE_TEXT
+%1 field missing+
why the framework not populating the field name? might be bug?
02. Compare the user group between these users.
03. Do the same steps in debug mode for these users, and check the log entry. You will get some points.

Creation of new fields for business partner relationship

Hi experts,
We are currently on SAP CRM 7.0 EHP1.
We have a requirement to maintain a custom checkbox (Relevant for business) on each business partner relationship.
Can you please let us know on how we can achive this requirement.
Thanks in advance,
Vamsi.
Moderation: Duplicated. I lock this one and continue here: [Create a new field in Business Partner Relationships|Create a new field in Business Partner Relationships#10795912]
Edited by: Joaquin Fornas on Nov 8, 2011 12:17 PM

Please, anyone can help?
Thanks!!

Fields missing in Infoset.

I have an infoset that contains 3 master data objects. Some of the attribute fields do not show up in the infoset. Does anyone know why some fields show up and other do not?
Thank you
Aaron

Hi Oscar,
The field missing is not set to attribute only. I checked other fields that do show up in the infoset and they are not marked as attribute only. Any other ideas?
Thanks
Aaron

FIELDS MISSING

Hi,
When i replicated CO-PA data into BI. It created two DS's:
0COPA_RCTY AND 1_CO_PA_XXXXXXX
I created an Infosource and transfer rules for 1_CO_PA_XXXXXXX but there are a few fields missing that i do see in the operating concern such as:
ARTNR=0MATERIAL
KNDNR=0CUSTOMER
BZIRK=0SALES_DIST
Why are these fields not in the Infosource since they are in the operating concern?
Where would they be?
Thanks

Delete the data source and then need to re-create using KEB2 transaction. While re-creating the data source use the same old name so that there won't be any changes in the BW side when you need to assign the data source to info-source. Just replicate the new data source in BW side and map the new field in info-source.
(you can also try, goto KE24 and edit the dataaource and add your fields not 100% sure of it works)
how to select fields refer doc:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6

Fields missing on FB60

Hi,
I have a couple of questions.
1. I see there are a few fields missing on the line item level on FB60. It's not the case for development or testing environment. But in Production it's happening. Does anyone know how to get these fields back?
2. Is there a transaction where I can clear multiple documents at once instead of one like FBRA?
Thanks

Hi!
Field is missing in FB60 screen, please brief which field you are missing and whether its comes earlier, if so please check is there any variant create, u can see this variant at end of the line item screen in top position. when u put your cursor there it will show u the configuration, click there and see if any variant is used, if so remove that and put tick on use as standard setting and try.
FBRA is not for clearing the document, but it reset or reset and reverse the clear document.
for clearing of vendor tcode is f-44
for clearing of g/l tcode is f-03
for clearing of customer tcode is f-32
Rakesh

Fields Missing in datasource

Hi friends,
Please help, I have some fields missing in my data source , but they are available in the extract structure of that data source..what do I do now, to see the same fields in my data source also?? should I ahve to append the data source??
thanks alot in advance,

Hi
I think you didn't appended the fields to the append structure.
Try to append the fields in the append structure and save ands activate it. and again activate the extract structure.
then you can see in RSA6
Hope this helps
shiva

Characteristic Relationship Error

Hi
I am deriving 0fiscper by concatenating 0fiscper3 and 0fiscyear. This works perfrectly in BPS. However, when I define the characteristic relationship in IP I get hte following error when checking:
Characteristic relationships for InfoProvider ZSEM_C20 are inconsistent
Relationship 01 is inconsistent
Contains generic time derivation 0FISCYEAR,0FISCPER3 -> 0FISCPER
Not permitted
The code for this is exacthly the same as for another derivation I did in BPS. How do I do this in IP?
L.

Hi,
In IP, their are default characteristic relationships for time characteristics which are always active. This wont show in the properties of the real time infoprovider (char. rel. tab) but this will be active and cannot be overridden; this is different from BPS where no such automatic chal. rel.s were present.
Therefore, you need not code them in an IP implementation.
Hope this clears your issue.
Edited by: Mayank Gupta on Feb 1, 2008 2:52 PM

Characteristic Relationship Challenges in IP

All,
I'm having a bit of a problem with characteristic relationships in IP.
We have a simple planning cube with no data. It has the characteristics 0CALMONTH, 0MATERIAL, 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, and 0PAYER. We want to build a query which allows us to plan on specifically designated valid combinations of 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, and 0PAYER. However, instead of displaying only the valid combinations we desire, things seem to be showing up as the Cartesian Product of the characteristics.
We thought we could accomplish this through a characteristic relationship and we tried establishing one (first by creating a DSO and then by creating a hierarchy). But all combinations seem to yield only one of the following results:
*Only the first level of the hierarchy
*The Cartesian product
*The 2nd level of the hierarchy (and only the 2nd level) but unfortunately containing ALL options in master data
Has anyone here ever managed to do in IP what I'm trying to do (display only certain valid combinations of characteristics)? If so can you give me a step by step outline of how you did it?
According to SAP hosting we have all of the latest Service Packs.

All, the issue is partially corrected. Instead of fighting with hierarchies, I stepped back and re-attacked this problem by creating a characteristic relationship based on a DSO. (I had tried this initially but it failed for a reason I will explain below.)
We do top-down planning and so I need these valid combinations at each level of granularity. I created a DSO with the key 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, 0PAYER, and populated it with the valid combinations. However, when I tried to create the characteristic relationship it does not allow me to select 0PAYER as a "Source Characteristic". This results the relationship being inconsistent.
So then I created a DSO with the key 0SALESORG, 0SALES_GRP, 0SALES_OFFICE, and populated the valid combinations. It worked perfectly for my query at that level of granularity but not for the higher level of simply 0SALESORG and 0SALES_GRP and so I found myself creating another DSO and characteristic relationship to handle that level.
Now I have the valid combinations down to a certain level of granularity displaying properly, but not all the way to the 0PAYER level. I'm not sure why it has a problem aside from perhaps the fact that 0PAYER is a reference char based on 0CUSTOMER. Does anyone know why it has this problem with 0PAYER?
Additionally I have found that I can no longer execute a simple copy function on my cube because it "cannot find reference data for characteristic combination" in an insistance when I planned on a characteristic with a blank value.

Fields missing in Characteristic Relationship

Similar Messages

Maybe you are looking for