COPA Derivation based with target field as non-copa field

Hello experts,
There is a requirement to derive the Characteristic maintained in Classification view(AUSP table) in Material master based on material number.The target field into which the characteristic value needs to be populated is not in COPA(it is a non-copa field).
I tried to use table look up with AUSP table, but it is asking for values of certain key fields like
ATZHL(Characteristic value counter) MAFID(Indicator: Object/Class) and
KLART(Class Type), which are not there in COPA.
With the Enhancement in KEDR transaction, EXIT_SAPlKEDRCOPA_001 and Include ZXKKEU11, I created an enhancement step by giving the material as the key in the source fields.With that material number I can do a select on the AUSP table inside the include ZXKKEU11 and get the characteristic value. The problem i am facing is that the target field which stores the internal characteristic value is not there in COPA?And while creating a derivation rule, I can only select the COPA fields as target fields.
It's urgent....any suggestions please? Points will be rewarded for any useful answer.
Thanks,
Anky

Hi,
As far as I know the derivation functionality in COPA is meant for derivation of characteristic values to store them in a characteristic field.
If you splitt up the derivation in two steps it might be possible to use the USERTEMP fields, to store the information needed and to pass it on to an other lookup step as a key-reference.
Regards,
Roy

Similar Messages

Key fields and non-key field of condition table

Hello Gurus,
what is key fields and non-key field of condition table?
thanks very much!

Key field
Each condition table contains keys that can be used for creating dependent condition records.
for example let take condition type PR00.
PR00 uses access sequence PR02 .
Access sequence PR02 has following tables associated with it namely 304, 305 & 306
When you create a conditon record for PR00 with transaction VK11 or VK31, you have a button 'key combination' which is nothing but fields associated with tables 304, 305 & 306.
In brief, Condition records are always created using specific keys. Condition tables are used to define the structure of the keys of a condition record.
Non key field
For example take condition table 144 - sales deal basic data.
Table 144 is associated with access sequence PBUD.
If you check the fields associated with this table (click technical view button), there are three fields at bottom which do not have 'key' check mark -KDATU, PLTYP, KSTAF
So, when you create a condition record for PBUD, system does not propose these 3 fields in 'key combination' and hence are non key fields.
Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

Problems with query on a non-database field

Hi,
Hopefully I am in the correct section...
I have some problems. I wanna query a non-database field but it does not work for one of them. I have tried the following...
declare
vsNewDefaultWhere varchar2(4000);
vbFirstWhere boolean;
cursor curArea is
select a1_area, a1_hbno, a1_seqno
from b1_in, c1_hdr, a1_bl
where b1_sequenceno = a1_seqno
and b1_shipid = a1_hbno
and b1_id = :c1_shipid;
rowArea curArea%ROWTYPE;
procedure mergeStrings (sNewWhereClause varchar2) is
begin
if not vbFirstWhere then
vsNewDefaultWhere := vsNewDefaultWhere || ' and ';
end if;
vsNewDefaultWhere := vsNewDefaultWhere || sNewWhereClause;
vbFirstWhere := false;
end mergeStrings;
begin
navigate.resetselrows('IMP_HDR');
navigate.resetselrows('IMP_DTL');
if not navigate.customwhereclause then
navigate.resetwhereclause('IMP_HDR');
end if;
vsNewDefaultWhere := Get_Block_Property('IMP_HDR', DEFAULT_WHERE);
vbFirstWhere := vsNewDefaultWhere is null;
---- does work!
if :IMP_HDR.c1_usecode is not null then
mergeStrings('c1_shipid in (select b1_id from b1_in where b1_fac = ''' || :global.fac || ''' and b1_comp = ''' || :global.comp || ''' and b1_code like ''' || :c1_usecode || ''')');
end if;
---- does not work!
open curArea;
fetch curArea into rowArea;
if curArea%found then
if :IMP_HDR.c1_area is not null then
mergeStrings('c1_shipid in (select b1_id from b1_in, c1_hdr, a1_bl where b1_fac = ''' || :global.fac || ''' and b1_comp = ''' || :global.comp || ''' and b1_sequenceno = ''' || rowArea.a1_seqno || ''' and b1_shipid = ''' || rowArea.a1_hbno || ''' and rowArea.a1_area like ''' || :c1_area || ''')');
end if;
end if;
end;
Thanks for your help in advance and let me know if you Need more Information.

Hello,
Ask Personalization questions in the dedicated E-Business Suite forum ;-)
Francois

COPA account-based only!

Hi
I intend to implement COPA for my customer, but only COPA account-based.
As my knowledge about COPA, costing based uses value fields instead of account as in account based.
But when i demo in client 800 (IDES), I realized that many diffirences between costing based and account based. It seem to be not only relevant to the value fields and account based.
For example:
when i post an invoice (fb50) in FI, then click profit segment field. I can not find characteristics that i want to post to such as material group. And there is nowhere for choosing all characteristics in client.
How can i find the way to post to characteristics that i want to post to directly from FI to PA?
Another example:
when I create report in PA account-based, there are limited characteristics in compare with PA costing based, so I can not choose profit segments i want?
What's the problem here?
Is it possible? Which problems can I meet if i do not use costing-based?
I am apreciated any help of you!
Thanks

Couple of things:
In Account based CO-PA:
1. You can't get Cost component break down.
2. No break down of variance categories.
3. Create a Characteristic in KEA5 and add to operating conern in KEA0. KEQ3 is to define segment level characteristics. To improve system performance, you can also restrict the characteristics that make up the profitability segment.
4. When you add a characteristic to operating concern, then by default that characteristic is available at the time of document entry. We use characteristic groups to determine what characteristics appear in which order on the screens for assigning profitability segments in different business transactions. If no characteristic groups are defined, the user can enter values for any characteristic in the operating concern.
5. Account based CO-PA uses the same tables (COEP, COEJ, COSP, COSS etc.,) as used by overhead cost management, whereas costing based COPA has it's own tables. The definitions of profitability segments for both CO-PA sub-modules are stored in the same table, the CE4XXXX table (where XXXX = operating concern).
6. Period account approach, unlike costing based which is cost of sales accounting approach.
7. Account-based CO-PA stores all transaction in three currencies: the transaction currency, the local currency, and the controlling area currency.
Also, check SAP note 69384 on account based COPA.
What kind of business is your client in? What reporting is he expecting out of CO-PA?
Edited by: Pradeep kumar Athmakur on Dec 31, 2009 6:32 PM

-- SQL -- GROUP BY clause: non-aggregate fields mandate

Hello,
I was studying Databases, (particularly the retrieval of the data), and found something interesting.
While using an Aggregate Function in the SELECT clause, it is mandatory to have all the non-aggregate fields in the SELECT clause to be there in the GROUP BY clause.
For example,
SELECT dept_no, SUM(salary)
FROM employee
GROUP BY dept_no;
The above SQL works fine.
But, what if the user misses the dept_no in the GROUP BY clause or he/she misses the GROUP BY clause itself?
Certainly, it is an error.
Why is this error not handled by the database. I mean, the database should be smart/intelligent enough to add the GROUP BY clause by itself. So suppose, if I miss out the GROUP BY clause or miss a non-aggregate field from the SELECT clause when I am having at least one aggregate function on a field with at least one non-aggregated field in the SELECT clause, the database should check the GROUP BY clause at time of compilation and add the mandate missed out fields in the GROUP BY clause.
Example,
SQL1:_
SELECT dept_no, SUM(salary)
FROM employee
GROUP BY dept_no;
SQL2:_
SELECT dept_no, SUM(salary)
FROM employee;
Here, the SQL1 and SQL2, both should give me same outputs without an error.
I am unable to understand why is this not handled?

Hi,
998478 wrote:
... If we mix aggregate and non-aggregate values then there must be a GROUP BY clause containing all the non-aggregate values. Why is this not handled by the database/compiler itself? It IS handled by the compiler itself. The compiler handles it by raising an error. The compiler has no way of knowing whether you want to remove something from the SELECT clause, or to add something to the GROUP BY clause, or not to use aggregate functions, or to use more aggregate functions, or some combination of the above. If the compiler re-wrote your code, and did any of these things automatically, it would be wrong more often than it was right, and you would (rightly) be complaining about its behavior.
For example, this is clearly wrong:
SELECT    deptno
,       job
,       SUM (sal)
FROM       scott.emp
GROUP BY deptno
;What is the right way to fix it?
<h3>1. Remove something from the SELECT clause</h3>
SELECT    deptno
,       SUM (sal)
FROM       scott.emp
GROUP BY deptno
;<h3>2. Add something to the GROUP BY clause</h3>
SELECT    deptno
,       job
,       SUM (sal)
FROM       scott.emp
GROUP BY deptno
,         job
;<h3>3. Not use aggregate functions</h3>
SELECT    deptno
,       job
,       sal
FROM       scott.emp
;<h3>4. Use more aggregate functions</h3>
SELECT    deptno
,       MIN (job)
,       SUM (sal)
FROM       scott.emp
GROUP BY deptno
;These aren't all the options, either. For example, the correct fix might be to use analytic functions instead of aggregate functions.
How can anybody say which of these is right? All of them are the right answer for some problem.
By the way, saying that everying in the SELECT clause must be an aggregate or in the GROUP BY clause is a bit over-simplified.
More completely, here are the ABC's of GROUP BY:
When you use a GROUP BY clause and/or an aggregate function, then everything in the SELECT clause must be:
(A) an <b>A</b>ggregate function,
(B) one of the "group <b>B</b>y" expressions,
(C) a <b>C</b>onstant, or
(D) something that <b>D</b>epends entirely on the above. (For example, if you "GROUP BY TRUNC(dt)", you can SELECT "TO_CHAR (TRUNC(dt), 'Mon-DD')").
Edited by: Frank Kulash on Apr 13, 2013 1:44 PM
Added code examples.

How to copy copa derivation rules ( maintain rule value)

Hi All,
Can anyone help how to copy the copa derivation rules with maintain rule value from production to quality.

Hello,
Export and import of copa derivation rule is not possible.
usually Transports are moved from quality to production as per best policy.
Production to quality happens at the time of quality refresh.
in case of high importance please get in touch with Basis team.
Regards
Lavanya

Changing Non key field to Key field in a custom table

Hello Abap gurus:
I have a requirement in which i need to change a non key field in my custom table(Z TABLE) to key field.
For example; i have field sequence as
field 1 key field
field 2 key field
field 3 key field
field 4 non-key field
field 5 non-key field
field 6 non-key field
field 7 non-key field.
i want to change field 7 as key field.
Can i do perform operation??
when i am tryingto perform bove operation it is taking long time to get the table activated.
Could any one please help me in getting this resolved.
regards,
Sravanthi.

Use DB Utility (se14) to perform alter table or conversion. The latter is used when atemps to perform first operation fails. Which one is used, really depends on system and current DB table state (i.e. if has any content and what is being adjusted).
The way Max suggested is similar to [conversion process|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21f1b8446011d189700000e8322d00/content.htm] which system takes care of itself.
Refer [Adjusting Database Structures|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21f1ab446011d189700000e8322d00/content.htm] and already given link to conversion.
Please also consider potential errors while doing conversion . This can lead to data loss, so you should think of some backup to prevent that.
Regards
Marcin

Gr non valuated field in PO

Hi Gurus,
The field "Gr non valuated field" in PO has become non ediatable in delivery tab of PO . I checked in the screen layout in SPRO. It is not there. Where do we do the screen layout changes for this field.
Regards,
Kumar

Please check these answered links:
GR Non valuated field
GR Non-Valuated field in PO
Re: GR non valuated help
Edited by: Afshad Irani on May 28, 2010 4:45 PM

Process data of none bound fields in Adobe Interactive Form (stack 13)

I use a Adobe interactive form (made in Designer 7.0)which is a combination of fields bound to Web Dynpro Context fields and fields which has no binding at all (in Designer: Default binding = Normal). The Adobe Document Services on the J2ee server is of stack 13.
When I save the Adobe Form (off-line scenario)from the Web Dynpro Application, only fields bounded to the Web Dynpro Context are saved in the Form on my local file system(no warning that data isn't saved).
When I open the Form for off-line editing, I can change bounded fields and none bounded fields. But when I save and re-open the form, the data in the none bounded fields is lost.
I used the same scenario in a stack 11 j2ee/portal system, but then all data (bounded or not) in the form was saved!
Could anyone explain the difference, but better tell me how to save both kind of fields in the off-line form (and bounding all fields is <u>not</u> a solution).
Thanks in advance,
Richard

Hi,
Check your ADS settings, I feel it's due to lack of some config in ADS only.
Regards
<i><b>Raja Sekhar</b></i>

Non-display fields in Qualified Table to be displayed in ItemDetail iView

Hello expert,
Is it possible to display a non display field in Qualified Table in ItemDetailed iView?
It seems not possible by standard iView configuration.
Is it possible to achieve by some minor coding? If possible, such code is appreciated.
Thank you.
Dale

Hi Dale,
Yes, it is possible , and no need to do any custome coding. You can configure non-Display field of Qualified table to be displayed in Standard item detail iview.
You have to select Qualified look up field if you are creating Item iview on Main table and complete all steps.
once you complete all steps, open Item iview , select Reletionship and qualified display field option .
now you can see qualiied tables in table , click on Edit , now you can see all fields of qualified table.. you can select any field (dis/non-dis fields).
Hopw this helps you.
Thanks & Regards,
Veera.

COPA derivation rule :more than 6 target fields

Hi ,
As per client's requirement I need to include 10 target fields in a COPA derivation rule . Now after entering 6 , I can see rest of the rows are greyed out ; it looks like SAP does not allow more than 6 as target .
I tried to find out if such limitation is mentioned anywhere in SAP documentation but I could not find ; if anyone has any reference doc on that please let me know .
Secondly , how to meet the requirement ? I can break the same into 2 separate derivation , say 6 target & related rule value in the first and in just next step another 4 targets & rule value ; the source remains same in both the step .
OR any COPA user exit / enhancement will help me accommodate all 10 targets in a single step of derivation ? as far as my knowledge goes SAP provided COPA user exits (1 to 5) will not be helpful here .
Awaiting your help ...
Regards
Indranil Sen

Dear Indranil Sen,
As per my knowledge it is not possible to mention more than 6 source and target fields for a derivation rule.
Because for that program, SAP defines that (1+5) fields for that screen.
That is the reason you are getting the gray color after 6 entries
Yes we can increase that limit but for that we need the access key.
If you have access key authorization, you can increase the limit
Reasons in detail:
Screen filed what you are looking for is:
DYNP5400-SRC-NAME-FIELDNAME
There you can enter (1+5) entries only. enhancement for that field is difficult.
So you can opt for 2nd option as you said.
Let see Mr. Waman Shirwaicar's views on this issue.
Regards,
Pavan Kumar Arvapally

COPA derivation rule for GL fields

we are using Transaction type (BSEG_BEWAR) to store additional information for our Sales reporting. During the GL entry this field is update. I have created Derivation rule in COPA using table look up. The table I am using is BSEG. I have characteristics defined for Transaction type- WWTTY.
when the table lookup is populated I get following fields in source as target :
BSEG -
> BUKRS                                COPA --> BUKRS
BSEG -
> BELNR                               COPA -
> BELNR
BSEG -
> GJAHR                              COPA ---> GJAHR
BSEG -
> BUZEI                               COPA -
> WWDOC ( This is custom defined in COPA)
Assignment of Target Fields:
BSEG ---> BEWAR                                COPA -
WWDOC
Still I am in seeing COPA getting updated with Transaction type value.
Need input to solve this issue.
Thanks in advance

Hi Ajay,
Thank you so much for your reply.Please note that the GL is a cost element but the category in system is 1 and not 12.However I would like understand as to why is this happening.why does the system picks up derviation rule for a Gross sales GL and not for Discount GL(Cost element).
The distribution channel gets updated for sales GL when i check the prof segment of the line item, however this is not the case with doscount GL.
I would like to understnad the implication before changing cost element category from 1 to 12 as it runs across system.
Kindly provide some more explaination.
thanks in advance.

Problem with Non-English Fields Output to PDF by JASPER in JDev10.1.3

I am using jsprx files(designed in i-report) to generate pdf reports out of an oracle database.
The non-English fields are shown correctly when I output the report into an HTML or when I view it with JasperView.
If I try making PDF files (JasperExportManager.exportReportToPdfFile) the static fields containing e.g.Arabic/Chineese characters won't be displayed and dynamic fields from the database with non-English contents will be shown as ??? or null.
I received some suggestions about using PARAMETERS to feed the report instead of FIELDS, which I think can not be helpful in this case and in general.
I think this should be a common problem. These are the components I am using:
itext-1.4.7. jar
commons-digester- 1.7.zip
jasperreports- 1.2.8.jar
Any comment or help is appreciated.
Thanks
Farbod

I am using jsprx files(designed in i-report) to generate pdf reports out of an oracle database.
The non-English fields are shown correctly when I output the report into an HTML or when I view it with JasperView.
If I try making PDF files (JasperExportManager.exportReportToPdfFile) the static fields containing e.g.Arabic/Chineese characters won't be displayed and dynamic fields from the database with non-English contents will be shown as ??? or null.
I received some suggestions about using PARAMETERS to feed the report instead of FIELDS, which I think can not be helpful in this case and in general.
I think this should be a common problem. These are the components I am using:
itext-1.4.7. jar
commons-digester- 1.7.zip
jasperreports- 1.2.8.jar
Any comment or help is appreciated.
Thanks
Farbod

Quotation with target value (field ZWERT)

Hello
the requirement is to create a sd quotation, which is not based on target qty or order qty!! furthermore I need to have a sd quotation which is based on target value. Is there any way to have this? I tried all the standard quotation types (AG, AV, AS, ...)! All of them are qty based not value based! What can I change in customizing to have it value based? could it be solved by change the field "Screen sequence grp." from AG to WK1 without change any logic for standard quotation reports??
please help...
thx
deniz

For me, it does not make sense. Just from practical approach point of view, a seller would decide his selling price to his end customer based on what off-take they are going to lift. Having said this, to decide the final selling price, you need to know what quantity you are going to sell. You cannot fix the selling price for who orders 10 nos. and sell at the same price for those who orders 1000 nos.
G. Lakshmipathi

Derived tables with prompts - based universe

why can't I use derived tables with prompts - based universes on Dashboard Design 4.0? I mean I can add to Dashboard Design data coming from a universe like that but the prompts don't show in the query panel in Dashboard Design. Could it be becuase my universe was created first as an unv and then I transformed it to unx?

Good day Yuvraj,
Thank you for your response.
Basically, I have 2 classes based on physical tables:
Product (P); and
Time/Calendar (T/C).
Two classed based on derived tables:
Stock on Hand (SoH); and
Stock Movements (SM)
The derived tables SQL code selects (Quantity and Selling Price) from the SoH table and joins to the T/C table with conditions and a Where clause to restrict the data output to the last 2 months (the same applies to the SM derived table).
Example code below:
SELECT q.sm_table _no, q.tim_cal_no, q.quantity, q.selling_price
FROM    tim_cal_table p,
              sm_table q
WHERE q.tim_cal_no= p.tim_cal_no
AND        p.day between to_char(sysdate - 60,'DD/MON/YY') and to_char(sysdate - 1,'DD/MON/YY');
Now, the SoH table and the SM table are joined (in the universe schema) to the P table and T/C table using Primary Keys (which are shared by all the tables - physical and derived i.e. foreign keys on the SoH and SM tables used in the derived tables).
Now to answer your questions:
Do you get data in case you take objects only from derived table class?NO
Does the columns used to join physical table and derived table has matching values? YES. I mean to say is the join getting satisfied? YES. Checked Universe Integrity - structure, objects, joins, conditions, loops, context and cardinalities - everything is OK.
Adding to this, is the data type same for both the columns (on which join is set) or is there any typecasting required? YES - checked the data types of the primary/foreign keys that join the tables and they all match, except for one on the SM table - the foreign key has 6 set for precision (instead of 5 as per the other columns), however the data type is Numeric so this shouldn't be an issue.
I hope this helps to clarify the nature of the problem.
Thank you.
Regards,
B

COPA Derivation based with target field as non-copa field

Similar Messages

Maybe you are looking for