Conversion in BP transaction

i have set of data in flat file,like bp number,date,time and the text,i need to add these text in the long text tab of BP transaction, how do i do that?

Hi Gerad,
Try this Function module for adding text to Business partner BUPA_EXECUTE_LONGTEXT or use function module SAVE_TEXT if you are sure about the TDNAME, TDID, TDOBJECT.
Regards,
Karthik.

Similar Messages

Re:Currency Conversion In Intercompany Transactions Currency Rate

Hi FI Experts ,
We have a Scenario of Intercompany transactions .
Kenya - KES
Uganda - UGX
1 KES = 25 UGX
When posting is done in the UGX, amount in Local Currency is getting multiplied with 25 instead of dividing it by 25 to convert into Local Currency ie KES
Please Help how to go about ....
Regards,
Sriram

Srirama,
You need to make sure that you have a translation ration as 1:1 for KES to UGX and UGX to KES. Then you need to maintain the FX rates in OB08 transaction as follows:
1 KES = 25 UGX and
1UGX = 0.04 KES
You have to specify this otherwise the system won't give you the proper results.
Best regards,
Vishal Thakur

User exit/BADI for updating custom table in MB1B transaction-

Dear All,
When performing a material to material conversion in MB1B transaction for batch managed materials,system is creating a new batch by copying the characteristics of issuing material/batch.The details of the new batch created are updated in standard batch tables(MCH1,MCHA,MCHA).
The requirement is when the new batch is created,the batch details and characteristics has to be stamped in a custom table.
Kindly suggest a user exit/BAIi available for updating the same in the custom table.
Regards,
Deepak

Deepak, Exits for MB1B are
MBCF0002            Customer function exit: Segment text in material doc. item
MBCF0005            Material document item for goods receipt/issue slip
MBCF0006            Customer function for WBS element
MBCF0007            Customer function exit: Updating a reservation
MBCF0009            Filling the storage location field
MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011            Read from RESB and RKPF for print list in MB26
MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.

Unit Conversion in BI 7.0

Hi i want to display the units in US standards in initial view of report and allow users to convert in local units if they want.
A. I find that data is comingfor "factory area" field in cube in various units such as FT(Feet), MT (Meters), ST, IN. as entered in ECC
Please get me some help to write the ABAP code to convert the units in US standard units or tell me some functionality at report level to convert the units so that report display all data for "factory area" in one unit
Thanks
Regards
Poonam Roy

Just a Correction here..
with NW2004s the HOW-TO GUIDE for qty conversion is obsolete.
As of SAP NetWeaver 2004s you can create quantity conversion types using transaction RSUOM.
The business transaction rules of the conversion are established in the quantity conversion type. The conversion type is a combination of different parameters (conversion factors, source and target units of measure) that determine how the conversion is performed.
In terms of functionality, quantity conversion is structured similarly to currency translation.
Quantity conversion allows you to convert key figures with units that have different units of measure in the source system into a uniform unit of measure in the BI system when you update them into InfoCubes
http://help.sap.com/saphelp_nw2004s/helpdata/en/27/b65c42b4e05542e10000000a1550b0/content.htm
Hope it Helps
Chetan
@CP..

Function modules for unit conversion

hai gurus.
what is the function module to make one qty to the same unit as other qty.
if one is in kg and other in pounds
i want to make both in pounds.
pls help me with this

Hi
chk UNIT_CONVERSION_SAMPLE
also chk this
CF_UT_UNIT_CONVERSION
Some Insights-
Unit conversions
with NW2004s the HOW-TO GUIDE for qty conversion is obsolete.
http://help.sap.com/saphelp_nw2004s/helpdata/en/27/b65c42b4e05542e10000000a1550b0/content.htm
As of SAP NetWeaver 2004s you can create quantity conversion types using transaction RSUOM.
The business transaction rules of the conversion are established in the quantity conversion type. The conversion type is a combination of different parameters (conversion factors, source and target units of measure) that determine how the
conversion is performed.
In terms of functionality, quantity conversion is structured similarly to currency translation.
Quantity conversion allows you to convert key figures with units that have different units of measure in the source system into a uniform unit of measure in the BI system when you update them into InfoCubes
http://help.sap.com/saphelp_nw04s/helpdata/en/27/b38c4284a8c353e10000000a1550b0/content.htm
It is entered in ODS table linked to info object (0material)
What you need to do basically is-
1 ) Goto your infoobject for eg- 0material
2 ) In Info object Maintenance- Tab page- Bex Explorer
3 ) Enter 0BASE_UOM in Base unit of measure
4 ) Generate UOM ODS (System generates it with prefix UOM)
It is made of 4 fields (1 more in case of compounding) with SID for them. This is the place where you enter numerator and
denominator to calculate conversion factor
5 ) Load the UOM ODS with conversion from 0MAT_UNIT_ATTR or flat file
6 ) Define conversion type
7 ) In the conversion type, then you can select 0Material in the dynamic determination of conversion factor
8 ) Select source unit and target unit
For more help refer SAP help file on NW2004s. It is comprehensive and even explain - How to do unit conversion in
transformation rule?
http://help.sap.com/saphelp_nw04s/helpdata/en/4f/707242df019c60e10000000a1550b0/content.htm
Check this sample code,
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
 EXPORTING
* CLIENT = SY-MANDT
 DATE = pdate
 FOREIGN_AMOUNT = p_amt1
 FOREIGN_CURRENCY = p_curr1
 LOCAL_CURRENCY = p_curr2
* RATE = 0
* TYPE_OF_RATE = 'M'
* READ_TCURR = 'X'
 IMPORTING
 EXCHANGE_RATE = w_rate
 FOREIGN_FACTOR = w_fact1
 LOCAL_AMOUNT = w_amt
 LOCAL_FACTOR = w_fact2
* EXCHANGE_RATEX =
* FIXED_RATE =
* DERIVED_RATE_TYPE =
 EXCEPTIONS
 NO_RATE_FOUND = 1
 OVERFLOW = 2
 NO_FACTORS_FOUND = 3
 NO_SPREAD_FOUND = 4
 DERIVED_2_TIMES = 5
 OTHERS = 6.
IF SY-SUBRC <> 0.
 write: / 'Conversion to loc.curr. failed:',
 p_curr1, '->', p_curr2, 'err.code=', sy-subrc.
ELSE.
 write: / 'to Loc.curr:', p_amt1 currency p_curr1, p_curr1, '->',
 w_amt currency p_curr2, p_curr2,
 '(', w_rate, ')', w_fact1, w_fact2.
ENDIF.
http://www.geocities.com/victorav15/sapr3/examples/currconv.txt
Check this
CONVERSION_FACTOR_GET
Measurement unit conversion: Get measurement unit conversion factor Not for Dimensionless Units of Measure
UNIT_CONVERSION_SIMPLE Measurement unit conversion by table T006, with rounding
UNIT_OF_MEASURE_SAP_TO_ISO
UNIT_OF_MEASURE_ISO_TO_SAP
MATERIAL_UNIT_CONVERSION Material quantity conversion from Base Unit of Measure to Alternative Unit of Measure and vice versa. For Dimensionless Units of Measure (Each, Piece, Box etc.) conversion depends on the given Material (see table MARM). For other Units of Measure (Length, Weigth etc.) conversion can be calculated from the T006 table or via CONVERSION_FACTOR_GET.
CONVERSION_EXIT_CUNIT_INPUT Conversion exit for commercial (3-char) measurement unit INPUT
CONVERSION_EXIT_CUNIT_OUTPUT Conversion exit for commercial (3-char) measurement unit OUTPUT
CONVERSION_EXIT_LUNIT_INPUT Conversion exit for technical (6-char) measurement unit INPUT
CONVERSION_EXIT_LUNIT_OUTPUT Conversion exit for technical (6-char) measurement unit OUTPUT
UNIT_OF_MEASUREMENT_HELP Input help for measurement units of a predefined dimension
http://www.geocities.com/victorav15/sapr3/abapfun.html
Reward all helpfull answers
Regards
Pavan

Currency conversion with query selection mask and InfoObject 0Curtype

Hi,
question to following scenario:
in the data source is an column with the currency type. This currency type column contains values like
10 = company code currency
20 = account area currency
So for each data set in the table is an assignment of currency types.
In the cube is an InfoObject called 0Curtype (for currency types 10,20,30 ...).
In the BEx Query should a filter or selection be possible before the whole data is displayed.
The user can select in which currency he wants to display the data. When he selects the 10 the whole data is displayed in different currencies which are available because its local currency (Euro, Dollar etc.). By selecting 20 the whole data is displayed in Euro.
Does anybody knows how to achieve that? Is there any function module availabe which is provided by SAP and it is available for use?
Thank you in advance!!!

Hi There:
You have two options available.
One you can define currency conversion variable in transaction RSCUR. Then use this currency conversion variable at query run time using a formula Key figure and go to Conversions tab and select this variable. Then at query run time the query will convert your key figure from source currency type to target currency type. But this can significantly impact your query run time because the query will calculate this at query run time.
The second option is to use a standard SAP function module CONVERT_TO_LOCAL_CURR in the back end and store this key figure in the back end during data load. This way the query will run faster for you. The difference is significant in my case.
Good luck.
Let me know if you need more information.
MP.

Currency Conversion type not in Query

Hi,
I have created a Currency Conversion Type using transaction RSCUR.
In the query i want to convert a particular column to target currency by using this curr conversion type.
But in the column properties under the conversions tab, the conversion type does not appear in the drop down.
Kindly suggest.
regards,
Vedaas

If you have followed the links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/462fe790-0201-0010-3ca4-adfd89e4f9f2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/287bab90-0201-0010-f48e-cc55b0cd13d0
Then log on and off the Query as it may be due to a refresh issue you can't see it.

Currency conversion Type

Hi experts,
I created a currency conversion type in transaction RSCUR. My problem is I don't see this in BEx query designer. I used an existing one as template and experienced the same. Did I miss something or is it a system bug?
For your info we are running BI7 SP6
Regards
Aban
Edited by: Abolfazl Hassanzadeh on Feb 18, 2011 2:47 PM

Hello Vikas,
Please don't post the same question multiple times. You have alread posted the same question 3 times here.
Please see the other thread that you have posted for answers.
Thanks
Chandran

BW Upgrade from 3.5 to version 7 - RSRV check fails in conversion exists

Hi All,
We are in the process of doing preupgrade checks for version 3.5 and for infoobject 0MATL_GROUP (material group) RSRV checks fails and throughing conversion exit issue for some SID's ,
Error Message:
Check values of characteristic 0MATL_GROUP for conversion exit
There are 41 values with the wrong internal format in the SID table
The first 10 errors are:
Value in SID table 4350/ correct value 000004350/ SID in SID table 2732
Value in SID table 10000000/ correct value 010000000/ SID in SID table 2716
Value in SID table 12000000/ correct value 012000000/ SID in SID table 2717
etc...
I just want to check do we need to fix this error before doing the actual basis upgrade 7.0 tasks orelse is it OK to do upgrade without fixing this error .
Pls advice is there is any way to fix this issue in system without deleting the above SID's in the system.
Is this error will create major issues afterupgrade to 7 without fixing this SID issues in 3.5 - Pls adivce us.
With regards,
Hari

Hi Hari,
From the error message it seems that you had data loaded to 0MATL_GROUP before the EXIT (I guess it is an ALPHA exit)
was switched on. Now the system find values that are not ALPHA converted with the RSRV check. You should correct this
problem before doing the upgrade. It should be possible to do the ALPHA conversion using the transaction RSMDCNVEXIT.
The reason for doing the ALPHA conversion before the upgrade is that transaction RSMDCNVEXIT is no longer available in BI
7.0, Since some objects of the new data flow in BI 7.0 ( for example BIA) are not covered by RSMDCNVEXIT it has been set to obsolete.
Customers cannot use transaction RSMDCNVEXIT anymore in release BI 7.0.
Best Regards,
Des.

Error in Quantity Conversion type.

Hi all,
I have created quantity conversion types in transaction RSUOM."ZCRFNSC"
In the Conversion Factor Tab,Dynamic Determination of Conversion factor i chosen as Using Refrence Info Object------0MATERIAL.
In the UOM Tab.
Source Unit TAB-- I have defined as UOM from data Records
And in the Target UOM i have set as Fixed Unit --"SC".
Now when i am executing the report where i have apllied this conversion type it throws error
"Inconsistent i/p parameter(I_TUOM, value SC)"
Kindly help me tounderstand & get the solution for this error
Points will be assigned....

Dear Experts ,
P101 condition type is not picking the MAP value in PO . It sometimes takes 0.00 or some other value other than MAP . Please tell me what could be wrong ?
Regards
Anis

Alfa conversion

Hi,
what is alfa conversion and what its usage.
thaks for ur answers
regards
ram

hi,
https://websmp102.sap-ag.de/~sapidb/011000358700000167472003
Frequently Asked Questions - ALPHA Conversion
Questions
What is the "ALPHA conversion" about?
Why is the "ALPHA conversion" necessary?
Where do I find detailed information?
What are the prerequisites for the "ALPHA conversion"?
What effects does the "ALPHA conversion" have on my SAP NetWeaver BI system?
How long does the conversion take?
What is the interrelation between a SAP NetWeaver BI upgrade and the "ALPHA conversion"?
Answers
What is the "ALPHA conversion" about?
A characteristic in SAP NetWeaver BI can use a conversion routine like the conversion routine called ALPHA. A conversion routine converts data that a user enters (in so called external format) to an internal format before it is stored on the data base.
The most important conversion routine - due to its common use - is the ALPHA routine that converts purely numeric user input like '4711' into '004711' (assuming that the characteristic value is 6 characters long). If a value is not purely numeric like '4711A' it is left unchanged.
We have found out that in customers systems there are quite often characteristics using a conversion routine like ALPHA that have values on the data base which are not in internal format, e.g. one might find '4711' instead of '004711' on the data base.
It could even happen that there is also a value '04711', or ' 4711' (leading space).
This possibly results in data inconsistencies, also for query selection; i.e. if you select '4711', this is converted into '004711', so '04711' won't be selected.
Why is the "ALPHA conversion" necessary?
In such a case, a number of problems can arise in reporting like wrong values of key figures, no data found for certain filter values...
The "conversion of internal characteristic values", in short term: "ALPHA conversion", is a transaction (transaction code RSMDCNVEXIT) that checks the format of all values of characteristics that use one of the conversion routines ALPHA, GJAHR and NUMCV.
If values are found that do not have the correct internal format it can replace them by correct value and update all dependant SAP NetWeaver BI objects (like InfoCubes, Hierarchies, master data of other characteristics...).
This transaction potentially has to touch a very significant part of all the data in SAP NetWeaver BI. While running the check or conversion phase of RSMDCNVEXIT no data loads of any kind are possible; the conversion part of it cannot be interrupted. Therefore you should never start the conversion part without having thoroughly read the documentation.
We recommend to run the conversion as soon as possible.
Where do I find detailed information?
The "ALPHA conversion" transaction RSMDCNVEXIT has online documentation which you reach via its "Help" button.
OSS note 447341 is about the ALPHA conversion in general and has attached to it a number of other OSS notes describing solutions to known problems.
What are the prerequisites for the "ALPHA conversion"?
Before running ALPHA conversion, apply SP 26 (SAP BW 2.0B) resp. SP 18 (SAP BW 2.1C) resp. SP 11 (SAP BW 3.0A).
If you have large ODS Objects (> 50 mio records in all) we recommend to apply Support Package 27 (SAP BW 2.0B) resp. 19 (SAP BW 2.1C) or the coding correction of OSS note 548122.
If you are unsure if the conversion has already been executed in your system (in a SAP BW 3.0A system it probably has already been done during the upgrade to SAP BW 3.0A) start transaction RSMDCNVEXIT and look at the system status: if it says "All characteristic only have correct internal values" you do not need to run it.
We recommend a database backup before you run the transaction.
If you have strong reasons not to apply the named support packages, please note that you can run the ALPHA conversion starting from SP 22 (SAP BW 2.0B) resp. SP 14 (SAP BW 2.1C). If your support package level is strictly smaller than 25 (SAP BW 2.0B) resp. 17 (SAP BW 2.1C) you have to apply the coding correction of OSS note 528381. If you have SID tables with more than several millions of records you have to be on SP 25 (SAP BW 2.0B) resp. 17 (SAP BW 2.1C) and also apply a correction described in OSS note 543482.
What effects does the "ALPHA conversion" have on my SAP NetWeaver BI system?
No data loads are possible while the transaction is checking or converting.
Once the conversion part has been started the conversion has to be completed. The system is in an inconsistent state in the mean time!
How long does the conversion take?
Usually, the alpha conversion requires between 3 and 20 hours for production systems. For very big systems (>1TB) , it could also take up several days.
From our experience, the most decisive factor for the duration is the size of the ODS objects. As a rough rule of thumb, approximately 2.5 mio. Records per hour can be converted within ODS objects (status SAP BW 2.0B SP 27 resp. SAP BW 2.1C SP 19). To improve the conversion for ODS objects, keep the change log small (i.e. delete old entries) because all change log records will be converted, too. Furthermore, the size of the master data tables (which include characters with one of the ALPHA, NUMCV or GJAHR conversions) has impact on the runtime of the upgrade.
As of SAP BW 2.0B SP 29 resp. SAP BW 2.1C SP 21, ODS objects can be converted in parallel. Please see note 559524 for details how to set up this parallelism.
As of SAP BW 2.0B SP 29 resp. SAP BW 2.1C SP 21, transaction RSMDCNVEXIT is enhanced by a workload estimate. This preliminary check lists all characteristics, database tables and the size of the tables that will be converted during the alpha conversion. Furthermore, possible meta data inconsistencies are found and the possibility of aborts during the conversion is reduced.
During the conversion process, you can check the state of the conversion in the log.
This estimate can be executed without locking the system. We recommend to run it before starting the conversion.
Please see the enhanced online help in transaction RSMDCNVEXIT for more details.
What is the interrelation between a SAP NetWeaver BI upgrade and the "ALPHA conversion"?
During the prepare phase of an upgrade to SAP BW 3.0B it is checked that the "conversion of internal characteristic values", also called "ALPHA conversion", has been successfully completed. This "ALPHA conversion" is time-consuming. Therefore we strongly recommend to separate this conversion from the actual upgrade process.

We are getting faxes with 812 error - "Document conversion failed" in SOST

Hi
We are getting faxes with an 812 error - "Document conversion failed" in transaction SOST. The user is sometimes able to fax the number successfully, but other times fails - it is not consistent.
The conversion rules seem to be set up correctly, indeed, on a resubmit this often (but not always) works, so I don't think this is down to the conversion rules.
Is it a problem at the SAP side or the receiving system?
We enabled a trace but on analysis the only step that appears to be different in the failing ones is:
Status "Fehler" am Sendeauftrag gesetzt
Which I believe roughly translates that it failed to send - but why, and where can I find more detail?
Thanks
Ross

I also noticed in the trace that the faxes that work have the following lines:
Determined device type: POST2. OTF Device Type POST2
Format conversion from OTF to PS With Device Type POST2
Converting OTF to PS
Whereas the ones that have failed say:
Determined device type: PDF1. OTF Device Type PDF1
Format conversion from OTF to PDF
Conversion rules for this country PL (Poland) and 'blanks' in order of prioroty are:
PDF                   S POST2
PDF PL Polish S ID2PDF
PS                          POST2
PS PL Polish   S I2SPOST
Is that correct?
Cheers
Ross

Uom conversions

hi gurus
How DP UOM conversion from CS to 9 Liters cases

Hi dallyanusha,
You can create user defined UOM conversion in CUNI transaction in APO or in R/3 and transfer to APO during the material transfer. Can you please brief about your actual issue.
Regards,
Saravanan V

Delayed Payment charges and Arrears in the Invoice output

Hi,
can we show Delayed Payment charges and Arrears in the Invoice output in case of SD invoice. From where can i take those. suggest.

Hi,
Please check whether the SMARTFORM/SAP SCRIPT was created in the DE login langage, if so then you have to maintain the Language conversion using SE63 transaction
Goto SE63 and in that transaction you have option to convert the TEXT to different langage.
Use transaction SE63 (translations). From the menu select:
Translation - Logntexts - Sapscript - Forms
From this point on you can translate both the descriptions and the
window texts. This transaction also checks if you don't forget to
translate a part of the script.
Hope it is clear
cheers,
santosh

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

Conversion in BP transaction

Similar Messages

Maybe you are looking for