Value field from Manual Invoice FI

Hi experts,
Is it possible to create a value field to record the quantity of the materials sold through manual invoice of FI?
Well, there are some materials which won't be sold via SO in our system, and hence when it is sold, it will be recorded through fb70 of FI. Well, I think there is no problem for the revenue and cogs.
Thank you very much for your inputs
Best Regards,
Erwin

Hi,
I am so glad that both of you know each other, =)
About that user exit, do u mean that i have to write an ABAP code to populate the qty from fb70 into valued field xxxx?
Is there any way around this? as i am kind of new to user exits, but i am willing to learn
However, if there is any standard way, i would try that first
And Ajay, I have to thank you too, you have supported me since i was very new.
If you remember the first time i post here, that was the very first time i started.
Once again, thank you
Best Regards,
Erwin Hartono

Similar Messages

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

Powerpivot pivottable - I can't add or drag a "value field" from the pivottable field list into the "values" section.

I built a pivottable using Powerpivot.
Initially, I can add or drag any data field I want to columns, Rows or the Values area inside the field list (those 4 squares). However, as times goes by...suddenly... I just no longer can add or drag a "value field" from the pivottable field list into the
"values" section.
Does anybody know how to fix this problem ?

Hi Bin Long,
I tried what you suggested.
I believe that there is a glitch in the Powerpivot field list (where you find the 4 squares for columns, rows, values, filter)
When I initially create a pivottable with powerpivot, everything works fine when I am adding field list items to the the columns, rows, values sections, filters.
However.....IF I close the powerpivot field list or if I save and close the excel file...then I cannot add more items to the "values" section.
I can comment about one thing that seems different in my powerpivot field list. When I can no longer add items to the "values" section, I realized that in the TOP section of the field list I see in bold letters a summary of the items that are SUM ∑ in the "values"
section.
Does anybody know how to fix this ?
Thanks.

MIGO_GR fill delivery note field from manual entry in bill of lading

I have to fill header field delivery note from manual entry in bill of lading in tcode MIGO_GR for mopvement type 101.
I searched for the exits and BADI's but header fields are not in changing parameters.
Has anybody worked on automatically filling the delivery note field in MIGO_GR transaction from bill of lading field or a value from database?

Hi You can use MB_MIGO_BADI Badi.
Thanks,
Anmol.

Costing component allocation to CO-PA value field via SD invoicing

Hi experts,
Somewhere a setting must be made that allocates costing component amount to CO-PA value fields.
I.e. this takes place when the CO-PA document is created belonging to the order/invoice created in SD.
Will appreciate to learn a transaction code where this setting is made.
BR,
Niclas

Hi,
costing-based CO-PA:
all values from billing documents flow to CO-PA based on KE4I T-code, quantities based on KE4M. If its necessary to reset some of the transferred values this can be done depending on the billing type using KE4W.
All other values that are posted with a PAOBJNR as cost object (=direct postings) are processed by mapping the cost element number to a value field in T-code KEI2.
Other values are settled to CO-PA by different settlement transactions (KEU5, KO88,...)
Best regards, Christian

CO-PA Value Field from Sales Document: Item Data

Hi,
I need to see a field from sales document.
This field is "volume" and it is in table VBAP, field VOLUM.
Can any body give a hint how should I configure the system to get data on a value field if I want to run a report?
Thanks
G

Try creating a characteristic from VBAP. KEA5 is the tcode. Create a new characteristics from table VBAP and pick VOLUM. Then it will be availble for u in COPA.

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

GR unit value coming from the Invoice

I have the following situation:
PO 100 units price 3,14 u20AC/unit
IR: 1 unit at a price of 314 u20AC/unit
GR: Post GR for 100 units and the system is generating the accounting doc. for a value of 624,86 u20AC, that comes from
- 1 unit at the price of the Invoice 314 = 314 u20AC
- 99 units at the price of the PO 3,14 u20AC/unit = 310,86 u20AC
The total GR amount is bigger that the PO amount.
Is this the standard SAP behavior?
Is there a way to get only the price from the PO, not from the Invoice
Best regards

Yes this is standard SAP design. This situation will raise if you post Invoice before doing GR. also depends on price control in material master.
To fetch the price from PO u must follow GR followed by posting an Invoice.
Edited by: Sachin D C on Nov 10, 2010 3:47 PM
Edited by: Sachin D C on Nov 10, 2010 3:48 PM

How can we delete value fields from the Table T237A?

Dear All,
We need to delete some value fields in CO-PA. We got a message that these value fileds are being used in the Table T237A.
This table is related to key figure scheme.
We have deleted in t.c. sm31 in the table/view V_RS_T237A elements which were assigned to value fields to be deleted.
But we still have a message value fields are being used. And after some searches we found out they are still being used in the table T237A.
COuld you please, help us?
Thank you in advance!
Best regards,
Kamila.

Change the Table Control attributes such that user can only select a single record(row).
<u>Tip to delete a selected record</u>
1) write a module 'Mark' in the PAI as below
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
LOOP WITH CONTROL table_view.
MODULE read_table_control.
FIELD flag MODULE mark ON INPUT.
ENDLOOP.
MODULE user_command_0100.
2) Module Mark is below.
MODULE mark INPUT.
CHECK flag = 'X'.
x = table_view-top_line + sy-stepl - 1.
Delete itab INDEX x.
ENDMODULE. " mark INPUT
Table_view is the TableControl Name.
'flag' is of type char(1) available in the Internal table which was assigned to the select option in the table control.
<u>award if uesful</u>
Regards,
Sudheer

Automatically populating Assignment Field from Customer Invoice Reference

Dear All
I have a situation. I want when a customer invoice is posted the invoice reference mentioned in the Reference field of the document Header should automatically be populated into assignment field
Can any one tell me how to get this situation condigured
Bilal

Hi,
You can use substitution function. T.Code GGB2.
Create substitution under Financial Accounting> Line Item
Click Create Substitution : System will ask How would you like to substitute
field BSEG-ZUONR : Choose Field - Field Assignment : Choose the Field Assignment
Create Click Step : Prerequisities : Double Click ABAP System Fields > Double Click System Transaction Code > Click = > Click Constant tab > Give T.Code F-43 (for eg) save
Double Click Substitute Enter BKPF-DBBLG in the blank field and save.
Now Use T.Code : OBBH
Enter Company Code; Call Point 0002 Line Item fill substitution and activation level 1 save.
If you are an End User kindly advise your FICO Consultant to do that.
Best Regards,
Sadashivan
Edited by: Sadashivan Natarajan on Feb 12, 2009 3:17 PM
Edited by: Sadashivan Natarajan on Feb 12, 2009 3:19 PM

Info about a new value field in a live operating concern

Hi Team,
I'm working on 4.7 system.
I have a live Operating Concern with 120 value fields in "Active" Status.
Some of them never have been posted until now. I need a new "Quantity type" value field, but I can't create another one because I already have 120.
In addition, the value fields that have not been used until now are "Amount type" ones.
Is it possible to delete or modify one of these value files and create another "Quantity type" one, considering that Operating Concern is productive? And how can I do it? What kind of problems could I have?
Best Regards,
Gio

Hi Gio,
Good evening and greetings,
Please go through the SAP Note No.21207 on Deleting a Characteristic / Value Field from an active Operating Concern. This should clarify your questions.
Please reward points if the note is of some use to you.
Thanking you,
With kindest regards
Ramesh Padmanabhan

Having problems when adding new Curency value field + currency field.

I need to add a new Currency field (CURR, length 15, 2 decimal places) plus the Currency field itself to a view.
I'm really struggerling. I have looked at the existing SAP fields in the Component workbench and I have to admit I can not see how a field is linked/related to the currency itself. Is this link established purlely at the disctionary level?.
Has anyone added their own Z field value and Z currency field before. I can create both fields and display them, but what I can not work out is how I related them within the component workbench, or is this done from the dictionary?.
Any help would be greatly appreciated.
I should have been able to look at an existing SAP example and work out how it's done, but so far I can not see/determine how this is achieved, even though someone has mentioned that it's controlled via the GET_I_field method. Looking at this method I was expecting to see some mention of both the Currency value field and the Currency field. But as I don't see these confusion reigns.
Jason

That's correct, but am I right in thinking that you can't actually create the currency key field itself?.
I am aware that currency value fields can be created which reference a currency key field, but can see nothing that allows me to create a currency key field to be referenced.
I hope that makes sense.
Also, I have amended the structure, changing my value fields from Decimal 15,2 to Currency 15,2 and have created a new currency key field in the structure and referenced this from the Currency value field.
Witin the Component/view/context node I can see this new currency key field, but it appears as STRUCT.fieldlabel whereas my currency value field appears in the context node as EXT.fieldlabel, because it was created in the AET.
My problem is that when attempting to add the currency key field onto the screen I don't have it to select from within the list of structures/attributes. All the others attributes in the context node seem to be there, except the new currency key field/attribute.
The attribute has a SET_fieldlabel, GET_fieldlabel, GET_M_Fieldlabel and a GET_I_Fieldlabel, which I believe is all that should be required.
Does anyone know what my problem could be?.
Jason

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should 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
(TA KECM).
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.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

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

CO-PA: Value fields - where to find? Function Module?

Hi there,
I want to select all the available value fields (VV010, ...) that can be included in tables CE1xxxx and CE2xxxx. Is there any Function module or table where I can get the (value) fields from? I don't want to create static coding that includes the fields that are included in this structures in this moment. My report should be as flexibel as it could be and so I'm looking for a possibility to get the VV-fields in the named tables.
Will thanh you so much
Kind regards
Max

Hi,
There are two tables you may need to refer to.
The table TKEF is the field catalog table and contains all fields and their attributes in the system, from where you can identify the value fields. Table TKEFE lists the fields assigned to the operating concern.
You may also look at the program RKEREOFC to identify a FM or method for your use.
Cheers.

Value field from Manual Invoice FI

Similar Messages

Maybe you are looking for