GR value field for a/c assigned PO

Dear Gurus,
How to know the GR value for the a/c assigned PO. In other words, Is it possible to know the GR value from any table without any manipulation.Thanks in advance.
Cheers!

Thanks Rajesh for your reply. I forgot to mention in my last thread that i want the amount in document currency. Like EKBE-WRBTR. Thanks in advance,
Cheers!
Kannan

Similar Messages

Define value in value field for CO-PA analysis.

Hello everyone,
I am looking to determine the values of a custom value field I created. This new value field is activated and assigned to an operating concern and I am able to use it in my form.
Now I would like to "link" my field value to an GL account in FI. How can I do this?
Thanks.

Hi Elodie,
Just to add to Pavan's reply you need to use tcode KEI2.
In case of SD to COPA transfer you need to map the SD condition to the value field
regards
Waman

CO-PA : How to define separate value fields for Revenue & Incoming SO

Hello friends,
In CO-PA reports, how can I see separate value fields for Revenue (ERLOS) and "Incoming Sales Order" ? I created a value field for incoming sales order value.
But when I goto customizing for CO-PA, Transfer of Incoming Sales Orders and Transfer of Billing Documents refer to the same tcode KE4I. So its not possible for me to define a condition type to 2 separate value fields.....how can I see both incoming sales order value and revenue (from invoices) together ?
Any advice you can give me would be greatly appreciated.
Cheers
Ken

Hi
In COPA value flow from a condition type thru a value feild.
One condition type can be assinged to only one value feild ratio
Condition    :        Value feild
     1                         1
But where as ratio between
Value feild              :         Condition
      1                                     N
Apart from above check the operating concern check for the values & characteristics and activate.
Thanks
Colin Thomas

Display Assignment Field for Mulitple Account Assignment Screen in MIRO

Hi Members,
I'm hoping someone may have the answer to a question concerning the transaction MIRO-posting an invoice.
The issue occurs in MIRO on the Purchase Order tab. I have a validation rule which requires a value in the assignment field before the document can be posted. When multiple account assignment functionality is used to allocate the charges, there is no assignment field available. How can I configure the assignment field (ZUONR) to be present in this area?
Your responses are appreciated.
KF

Thank you for your response.
What is call point 2? Would this specify that the substitution rule would only apply to the multiple account assignment screen?
If that is the case, this might provide one option.
However, if it applies to the entire MIRO transaction, that will not be possible because we use the text field and the assignment field for other purposes in the transaction.
Do we have any other options?
KF

Populate New Value field in COPA for Previous periods

Hi All,
I have added a new value field to COPA structure and regenerated the Operating Concern. But I dont know how to populate this value field for all the exsiting records. Any help would be appreciated.
Thanks
MKR

I have to manually update all the COPA tables for reporting.

Field name and table name for the value field

hi,
i requred the value field for which the quantity that is not delivered in purchase order, so please tell me which field i have to go for the value field.
thanks and regards.

Hi,
There is no direct field to get the PO Open qty(undelivered Qty).
Take the PO quantity for each Item from EKPO-MENGE.
For each PO Item there will be multiple GR(good's receipts) 's in MSEG table.
So pass EBELN and EBELP for MSEG table and Take all the GR Quantities(ERFMG) field and sum up .(have to take care of the Movement type also, becasue there will be some returns and GI's).
Substract the GR qty from PO qty you will get the UNDELIVERED QTY of A PO.
Regards,
Anji

Impact of Addition of New Value Fields in the existing Op. Concern-COPA

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669
Ohter details are as follows...
VALUE FIELDS : Defines the Structure of your Costs & Revenues. (Op. Concern 120 Value Fields)
1)     The client requires three new value fields to be created. Value fields for :
-     Other Airport Charges - International
-     Cargo Commission Cost
-     Personal Cost (Direct)
2)     What are the Steps involved in creation of new value fields? The steps are :
1)     Before creating new value field we need to check whether we can use already existing UNUSED value fields (There are 62 value fields created for the op concern 1000, in production the value fields TBUL1-L7 i.e. to be used (I assume) screen shot1 provided. My predecessor has used value field VV291, VV292, VV380 original description being TBUL3, TBUL4, and TBUL1. I believe he has changed the description in development client and created a transport request ref screen shot 2)
2)     You can create new value field thru T-Code KEA6 (4-5 characters beginning with VV) u2013 My predecessor has reused the value fields originally created he has not created new one I believe. please provide give your comments)
3)     Specify whether this field is for Currency or Quantity (currency defined in attribute of op concern and quantity defined by its own field u2013 unit of measure) u2013 My predecessor has configured the three value fields as Currency.
4)     Describe how the values in this field are aggregated over characteristics. (SUM, LAS, AVG) u2013 My predecessor has aggregated all the three value fields as SUM and they are in Active status.
5)     After the value field is created you have to add the value field (active status only) to the operating concern by Editing the Data Structure. (I guess this is done in the next step)
6)     Assign newly created Value fields to the Operating Concern u2013 T-Code KEA0 (In development client the value fields are assigned to the op concern 1000 refer screen shot 3. In the production client also those three value fields exist (does it mean they are assigned? your comments please.) As they have the original description TBUL3, TBUL4, and TBUL1 refer screen shot 4.
7)     After the Data Structure is defined you need to activate them. (creates plan vs actual database) u2013 Go to the data structure tab and Choose Activate. The status in dev client is Active with correct description but in the production client it is Active with the OLD description. After addition of the value field you need to regenerate the operating concern. T-Code KEA0 u2013 right?
8)     Condition Types are assigned to Value Fields? Donu2019t know u2013 T-Code KE45 (I think this is NOT required in our case u2013 Please give your comments)
9)     Define and Assign Valuation Strategy u2013 Cost assigned to Value fields u2013 T-Code KE4U (I think this is also NOT required in our case)
10)     Define PA Transfer Structure for Settlement u2013 T-Code KEI1 (This step is crucial u2013 I think I have to to include newly created value fields, but am not aware how to do it and what is the connectivity or what happens after this is done)
Note: My predecessor has created a Transport Request No# KEDK902167 for the value fields created by him.
3)     Whether my predecessor has performed all the steps for value field creation? How to test it and check that?
4)     If yes then, Do I need to perform additional configuration or can I proceed to transport it to Production?
5)     What is COPA Allocation Structure & PA Transfer Structure? Where and Why It is used?
6)     What are the different methods of cost and revenue allocations in SAP?
7)     I have checked the status of the value fields across clients, It is as followsu2026
     Value Field     Value Field For     Description     Development      Quality     Production
1     VV291     Other Airport Charges International     TBUL3     Exists      DNE     DNE
2     VV292     Cargo Commission Cost     TBUL4     Exists      DNE     DNE
3     VV380     Personal Cost u2013 Direct     TBUL1     Exists      DNE     DNE
#DNE : Does Not Exist (assumed since the description given to value field is not the same as in development client.)

HI sree,
ofter creation value field and saving that time reqwest number appeare copy the reqwest number and go through the se01 select that reqwest number select and transport click the truck symbole, and draft a mail to basis guyw.
Thank You!
Best Regards,
pradheep.

How to get the table of value field? and can we expand the technical limits

Dear
I have created value field in COPA with KEA6. And now, I need the table which the value fields are saved. Yet, I have tried a lot to find it and get failure? Can any guy help me? Please tell me how to get the table of a value field.
And another question is that, can we extend the technical limits for the number of value field for ECC6.0?
We have a note for R.4.x Please see below:
OSS note 160892
You can display the length of a data record using Transaction KEA0 ('Maintain Operating Concern'). After you have navigated to the 'Characteristics Screen' or to the 'Value field Screen' choose menu path 'Extras -> Technical Limits'.
The maximum displayed here under 'Length in bytes on the DB' is the maximum length permitted by the Dictionary. The reserve required for the release upgrade must be subtracted from this value.
To increase the allowed number of the value fields, increase the value that is assigned to field ikcge-bas_max_cnt (FORM init_ikcge_ke USING fm_subrc, approx. line 165) in Include FKCGNF20. It specifies the number of the possible value fields. The corresponding part of the source code is attached to the note as a correction.
David Sun
Regards!

how to extend the limit of value numbers? please see the original question.

Value field in cost element

Dear Experts,
I am facing an error after running copa cycle (cost allocation) through keu5.It is showing ''value field is not assigned to cost element this this.How to get the details of warning message showing in red ?
Regards
Partha

Dear,
Identify the PA settlement structure assigned to Assessment cycle using transaction KEU2 and then check this PA settlement structure in transaction KEI2. Here assign the cost element to the value field for valid assignment.
Regards,
Chintan Joshi.

Only on value field in COPA gets values from SD

Hi,
I created two value fields for COPA. I assigned one of them to the condition VPRS (a cost) which works properly. The other condition, assigned, VKP0 doesnt appear in the COPA-document. We are using record type F.
But when I ran an flow analysis I can see that the value from VKP0 has flown to COPA in record type A?
I will assign point directly to a working solution.
Best regards
Carl-Johan

HI,
Billing document value flow is as per KE4I mapping to value fields.
There are some value flow analysis tools under CO-PA to check your settings with respect to value flows. Use transaction KE4ST (Simulate billing document transfer -> Value flow (<Ctrl +F7>) to check where things went wrong.
Hope this helps.

Value Field not fetching the data

Dear COPA Experts,
There has been an addition to the cost component structure for my current client. The cost component has been created and CK11n is showing the correct data for the correct cost component. I had to add value fields to my current COPA report to reflect the figures from the cost component. For that, I had created and activated the Value Fields in KEA6 and assigned it to the Operating concern in KEA0 and activated it. Then, I had assigned the value fields to the cost component structure in KE4R. I had then added the value field in the COPA form through KE95.
When a new cycle is completed, It does not reflect the valuation in KE30 report. I had crossed checked in KE24 which is a standard report. The result in KE24 and KE30 report is same, i.e the valuation is not even reflected in KE24 report.
Please guide me to where am I missing something?
Best Regards...

Hi,
"When a new cycle is completed, It does not reflect the valuation in KE30 report". This statement is not clear. Are you expecting KEU5 cycles to populate this value field ? Normally this value field should be populated during billing (VF01) when the value of the cost component is populated in the value field.
regards
Waman

Add value field to operating concern

Hello,
I have created a new value field VV955 and want to add it to my operating concern in transaction KEA6.
I go into change mode for all value fields for my operating concern and add a new line with my value field. When I hit the save button, it says "Field VV955 exists as Val. fld in field catalog -> choose another name".
Also when I go into change mode in KEA0 where you can drag value fields from left to the right, the value field is blue which means I cannot assign it to my operating concern.
Any suggestions?
Thanks
Anne

Hi,
While creating value field it will only consider long text. Inoperating concern Data structure in KEA0 you can assgin value field it will display in blue first, when you select to data structure you can see value field and save the value field.
Regards,
Sreekanth

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
To delete characteristics or value fields, perform the following activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

To change User defined Value field from Amount to Quantity in COPA

I have created a created a User defined Characteristics VV930 - Number of labor hours. While creating, i wrongly assigned the chategory Amount instead of Quantity.
Now when i am trying to change it is giving me errors.
Also it is not allowing to delete and recreate the new VV930 with category as Quatity.
No data is posted in COPA.

Hi Rupesh
1. Remove it from your COPA data structure in KEA0... Shift it from Left to right in data structure screen... Then try to delete it
2. Else, reserve this Value Field for future use and change the name as of now to XXXXXX...Create a new Qty Field for your use now.
Regards
Ajay M

Stepe involved in Transport Value Fields.

Hi all,
I have created a Value field which i have assigned to operating concern. now i want to transport the changes to quqlity system for testing. I am using TCode Ka3i to created transport request. After creating transport request i get CHOOSE DEPENENT OBJECT CLASSES . which fields should i choose to transport the value fields? should i select the structure ABAP Repository Objects as default?
Please provide me step by step process for transporting the value fields.
Thanks,
Naveen

Dear Naveen,
You must be using transaction KE3I. You can select the Operating concern >Execute >Select Structures: ABAP Repository objects.
However, you need to re-concile the Production system with development and ensure that the only intended changes are overwritten.
Kind Regards
Umapathi G

GR value field for a/c assigned PO

Similar Messages

Maybe you are looking for