Numeric control to hex(in numeric control) conversion ?

hi
I have n.o (numeric control ) which appears as hex display , I want to convert it to decimal number and reverse
can any please show with help of example please

Since you want to convert the number:
There is a very elegant way to do it in the control:
# Place a numeric control on the FP
# Change the representation to a 'binary' I/U 8/16/32/64 (my example is with I32
# In the display properties enable the advanced mode and enter all the formats you want to use
(Hint: new line is shift-enter)
You can also add some indication like
dec:%d
hex:%x
bin:%b
The nice thing is that all conversion is made by the FP on the fly whatever numerical format you change. Hey mom, look without any wire
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Similar Messages

ME22N Show Numerator for Conversion of Order Price Unit into Order Unit

I hide Price in Me22n, when we do this, system hide the "Numerator for Conversion of Order Price Unit into Order Unit", but i want show this field on screen.
This field is : in Me22n -> view "Quantites/Weights "->"Order Unit <-> Ord. Price Unit".
How do i for this?

Hi Paul,
The field for Denominator for Conv. of Order Price Unit into Order Unit is MEPO1311-BPUMN and for Numerator it is MEPO1311-BPUMZ. Try hiding only the Denominator field using Loop at Screen. <CODE> ENDLOOP and see.
Hope that it helps. Reward if useful.
Thanks and Regards,
Maddineni Bharath.

Unicode (numerical) character conversion

What is the problem?
Some characters written in unicode format do not get transformed to their appropriate font-character.
Example
Numerical version: ≥ is printed as ≥
String version: ≥ is printed correctly
Both have the same unicode, yet LiveCycle DS will only convert the "string"-version and not the numerical version.
Question
Is there a way to make LiveCycle convert the numerical unicode representation of special characters aswell? If so how do I do this using LiveCycle Designer. I am working with textFields
Workaround
I have written the following workaround in my java project, obviously I'd appreciate it if I LC did this work for me as I'm not willing to implement a full-scale unicode table while LC has it by itself already (≥ works ...):
private String getNodeText(NodeList nl)
if (nl == null){
return null;
if (nl.getLength() == 0){
return null;
String unescapedString = StringEscapeUtils.unescapeXml(nl.item(0).getTextContent());
return (unescapedString.equals("null") ? null : replaceUnicodeNumbers(unescapedString));
private String replaceUnicodeNumbers(String unescapedString) {
return unescapedString.replace("≥", "≥"); // I changed this code to something more usable

You want the LPAD function
select LPAD( col1 , 9, ' ') from my_table;
Hi everybody !
Can someone solve this for me. I have a varchar2(9) variable, var, with the value '1234'.
Now I want to convert this to having leading blanks, ie. ' 1234'.
How to do this?
If I use the to_char(var,'fmt') function I get some error message that says there's too many declarations of to_char. I guess because tha variable already is a varchar2.
Thanx in advance
Vrjan

Numeric type conversion

Hi, it may be asked by someone before.
But,
public static void main(String[] args){
int i , j = 100;
double temp = i * 0.1;
i = (int) temp; //works
j = (int) j * 0.1; //fails, why?
System.out.println(i);
System.out.println(j);
error: loss of pecision
Any helps appreciate! ^^

Check out this page. When an int and a double are the operands of an arithmetical operation, the result is a double.
http://java.sun.com/docs/books/tutorial/java/nutsandbolts/arithmetic.html
Hmmm, note that "j = (int) j * 0.1; " is equal to "j = ((int) j) * 0.1;" It should work if you change the statement to "j = (int)( j * 0.1); "

Conversion error in Table control for Negative values

hello all,
Iam using table control with 6 columns and in that columns values are coming from Ztable. and out of that one column is of value which is input/output field and having negative value's also.type of that column is DEC.
Now when i run the report dump occurs showing error message as COnversion Error.
I think its because of negative value even the in attributes of that column i had selected With Sign checkbox.
Now when i run the report then if in Ztable negative value is there then i want to display negative value in table control also.
Please suggest me...
<removed_by_moderator>
Thanking you.
Regards.
Edited by: Hemant Baviskar on Sep 10, 2008 3:07 PM
Edited by: Julius Bussche on Sep 10, 2008 1:13 PM

Hemant
Refer to following link:
Table Control : Conversion error
Thanks
Amol Lohade

Parental controls sign-in

I recently re-loaded window XP SP2. My wireless linksys router is WRT54GS. Ever since, I constantly have to re-sign in to parental controls even though I check off "NEVER". I have had numerous email conversations with Linksys & they've been no help! I'm listed as a "family manager" & i have unlimited access but this is ridiculous! This is the only computer in my household that has this problem. Does anyone have a solution?

I had the same issue several years ago. It has to do with the update Netopia plug-in. Every time your computer goes to sleep and your screen saver with password protection kicks in, the plug-in determines that it cannot guarantee that you are the last person who was logged in (I say who cares, I got in using a password....and its the same user as the last time). So for safety sakes, it logs you out of parental controls. To get around this, I went into the parental controls website and listed my main computer as always connect as me so it never has to authenticate. It does this by MAC address. For the other PCs, I copied the older Netopia software and keep it handy. Any time someone updates the software I put the old back and then they can remain connected even after screen saving with lock. Jerry.

ORA-06502 : PL/SQL: numeric or value error in Report formattrigger

Hi guys,
I have a Format Trigger code to not display any amount less than 1.00 at a group frame level and outside of the group frame is the Grand Total in my report but I am getting
" REP-1401: ' r_headerformattrigger ' : Fatal PL/SQL error occurred.
"ORA-06502 : PL/SQL: numeric or value error"
every time I try to run it.
function R_headerFormatTrigger return boolean is
begin
if :c_header_amount_accrual1_disp > 0.99 then
return (TRUE);
else
return (FALSE);
end if;
end;
Does any one have any idea as why?

read this code
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 88 to a variable declared NUMBER(2).
Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints
Rizwan

QoQ unsupported numeric type??

Hi,
Has anyone successfully used CF_Select from Masrizal? I
bought the code only
to find that it's not working with dynamic options.
Would appreciate suggestions on how to get this to work. TIA
THis error is coming from this code in the Tag.
<cfquery dbtype="query" name="qryTemp">
select * from qryTemp
order by parent
</cfquery>
Error Executing Database Query.
Query Of Queries runtime error.
Query Of Queries runtime error.
Unsupported Numeric type conversion in Query of Queries.
My Code:
<cfquery name="getPA" datasource="bibs2">
select PraticeArea, PraticeAreaID from bibs_tblPraticeArea
where DeleteFlag = 0 order by PraticeArea
</cfquery>
<cfquery name="getBibs" datasource="bibs2">
Select *
from bibs_tblBibliographies
where DeleteFlag = 0
Order by DateModified Desc
</cfquery>
<table border="0">
<form name="test" action="example.cfm" method="post">
<tr><td>Pratice Area</td>
<td>
<cf_select name="PraticeArea" formname="test"
passthrough="style='background-color:##000000;
color:##ffffff;'">
<cf_option value="">Select Pratice
Area</cf_option>
<cfoutput query="getpa">
<cf_option
value="#PraticeAreaID#">#PraticeArea#</cf_option>
</cfoutput>
</cf_select>
</td>
</tr>
<tr><td>Bibs</td>
<td>
<cf_select name="BiBs" parent="PraticeArea"
formname="test"
passthrough="style='background-color:##000000;
color:##ffffff;'">
<cf_option value="" parent="">Select
Bib</cf_option>
<cfoutput query="getBibs">
<cf_option value="#BIBSID#"
parent="#PraticeArea#">#Title#</cf_option>
</cfoutput>
</cf_select>
</td>
</tr>
<tr>
<td>
<br>
<input name="Submit" type="Submit">
</td>
</tr>
</form>

<cfif isdefined("form.Submit")>
<tr>
<td >
<hr>
<cfoutput>
You have selected this:<br>
<cfloop collection="#form#" item="key">
<cfif key neq "fieldnames" and key neq "submit">
#Key#: #evaluate("form.#key#")#<br>
</cfif>
</cfloop>
</cfoutput>
</td>
</tr>
</cfif>
</table>

Solution: #jsstringformat()#
Example:
<cf_select name="PraticeArea" formname="test"
passthrough="style='background-color:##000000;
color:##ffffff;'">
<cf_option value="">Select Pratice
Area</cf_option>
<cfoutput query="getpa">
<cf_option
value="#jsstringformati(PraticeAreaID)#">#PraticeArea#</cf_option>
</cfoutput>
</cf_select>
<cf_select name="BiBs" parent="PraticeArea"
formname="test"
passthrough="style='background-color:##000000;
color:##ffffff;'">
<cf_option value="" parent="">Select
Bib</cf_option>
<cfoutput query="getBibs">
<cf_option value="#jsstringformat(BIBSID)#"
parent="#jsstringformat(PraticeArea)#">#Title#</cf_option>
</cfoutput>
</cf_select>
thanks for all the respond!
"is" <[email protected]> wrote in message
news:[email protected]...
> Hi,
>
> Has anyone successfully used CF_Select from Masrizal? I
bought the code
only
> to find that it's not working with dynamic options.
> Would appreciate suggestions on how to get this to work.
TIA
>
> THis error is coming from this code in the Tag.
>
> <cfquery dbtype="query" name="qryTemp">
> select * from qryTemp
> order by parent
> </cfquery>
> Error Executing Database Query.
>
> Query Of Queries runtime error.
> Query Of Queries runtime error.
> Unsupported Numeric type conversion in Query of Queries.
>
>
>
>
>
>
>
> My Code:
> <cfquery name="getPA" datasource="bibs2">
> select PraticeArea, PraticeAreaID from
bibs_tblPraticeArea
> where DeleteFlag = 0 order by PraticeArea
> </cfquery>
>
> <cfquery name="getBibs" datasource="bibs2">
> Select *
> from bibs_tblBibliographies
> where DeleteFlag = 0
> Order by DateModified Desc
> </cfquery>
>
>
> <table border="0">
> <form name="test" action="example.cfm"
method="post">
> <tr><td>Pratice Area</td>
> <td>
> <cf_select name="PraticeArea" formname="test"
> passthrough="style='background-color:##000000;
color:##ffffff;'">
> <cf_option value="">Select Pratice
Area</cf_option>
> <cfoutput query="getpa">
> <cf_option
value="#PraticeAreaID#">#PraticeArea#</cf_option>
> </cfoutput>
> </cf_select>
> </td>
> </tr>
>
> <tr><td>Bibs</td>
> <td>
> <cf_select name="BiBs" parent="PraticeArea"
formname="test"
> passthrough="style='background-color:##000000;
color:##ffffff;'">
> <cf_option value="" parent="">Select
Bib</cf_option>
> <cfoutput query="getBibs">
> <cf_option value="#BIBSID#"
> parent="#PraticeArea#">#Title#</cf_option>
> </cfoutput>
> </cf_select>
> </td>
> </tr>
>
> <tr>
> <td>
> <br>
> <input name="Submit" type="Submit">
> </td>
> </tr>
> </form>
>
> 
> <cfif isdefined("form.Submit")>
> <tr>
> <td >
> <hr>
> <cfoutput>
> You have selected this:<br>
> <cfloop collection="#form#" item="key">
> <cfif key neq "fieldnames" and key neq "submit">
> #Key#: #evaluate("form.#key#")#<br>
> </cfif>
> </cfloop>
> </cfoutput>
> </td>
> </tr>
> </cfif>
> </table>
>
>
>
>
>
>

FPGA Read/Write Control Issues

Hello all! Rather new to using FPGA, but I have an interesting issue that's popping up.
Currently pulling in RAW voltage data from a set of sensors (Pressure Transducers, Load Cells, etc) through a cRIO DAQ. Have the FPGA file setup to pull in that data already and have the main VI and all the sub-VIs working just fine.
What I'm trying to do is save the raw voltage data (TDMS files) on the lower level and the convert and display on the upper level so that I don't have to convert and save (speed up saving data). So that leaves 3 distinct levels/sections:
On FPGA that pulls in the raw data
On FPGA that saves the raw data
Main VI that does all the controls/conversions/displays etc.
Number two is where I'm having an issue. I want to save all the data in parallel so I'm creating a save FPGA for each I/O device (8 Relays to command solenoid valves, 3 Pressure Transducers, 1 Load Cell, 4 Thermocouples). To do this I want to create a separate VI for each device (not sure if that's a smart thing to do).
The issue I'm having is when I use the FPGA Read/Write control to read in from the Target and save to the TDMS. When I only use a single FPGA target reference the lines are broken, but as soon as I switch to two targets, it now works.
Any reason why it might be doing this? Any ideas/suggestions at all on how to go about setting this up in general?
Thanks!

Hi,
HySoR wrote:
The issue I'm having is when I use the FPGA Read/Write control to read in from the Target and save to the TDMS. When I only use a single FPGA target reference the lines are broken, but as soon as I switch to two targets, it now works.
Could you take a screenshot and post this part of your code? I'm having trouble understanding what you are describing.
Craig H. | CLA | Systems Engineer | National Instruments

Ora-06502 numeric or value error --urgent

Hai ALL,
In our Application some fields are blank and gives an error 'ora-06502 numeric or value error'. The blanked Fields are taken from another server. Before the error some os booting problem arises and reboot the server. no oracle maintanace and software maintanace done this place. the network connectivity is ok. How the oracle error comes? how to rectify ..please help.. Oracle version is 7..and an urgent matter.
Shiju

Hi Orashiju,
ORA-06502:     PL/SQL: numeric or value error string
Cause:     An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2).
Action:     Change the data, how it is manipulated, or how it is declared so that values do not violate constraints.
For more use this link. I am certain you will get an solution.
http://ora-06502.ora-code.com/
Thanks
Shivank

FPGA Read/Write Control Function Issues

Hello all! Rather new to using FPGA, but I have an interesting issue that's popping up.
Currently pulling in RAW voltage data from a set of sensors (Pressure Transducers, Load Cells, etc) through a cRIO DAQ. Have the FPGA file setup to pull in that data already and have the main VI and all the sub-VIs working just fine.
What I'm trying to do is save the raw voltage data (TDMS files) on the lower level and the convert and display on the upper level so that I don't have to convert and save (speed up saving data). So that leaves 3 distinct "levels/sections":
On FPGA that pulls in the raw data
On FPGA that saves the raw data
Main VI that does all the controls/conversions/displays etc.
Number two is where I'm having an issue. I want to save all the data in parallel so I'm creating a save FPGA for the I/O devices (8 Relays to command solenoid valves, 3 Pressure Transducers, 1 Load Cell, 4 Thermocouples).
The issue I'm having is when I use the FPGA Read/Write control to read in from the Target and save to the TDMS. When I only use a single FPGA target reference the lines are broken, but as soon as I switch to two targets, it now works.
I've attached a screen cap of the current problem. The set-up on the bottom (with only one target) doesn't work. But the second I add more than one target, it works.
Any reason why it might be doing this? Any ideas/suggestions at all on how to go about setting this up in general?
Thanks!
Attachments:
FPGAError.jpg ‏35 KB

HySoR,
You might check the documentation for "data" terminal of "TDMS Write" (http://zone.ni.com/reference/en-XX/help/371361H-01/glang/tdms_file_write/). One DBL element is not accepted, but 1D DBL array is accepted.
data is the data to write to the.tdmsfile. This input accepts the following data types:
Analog waveform or a 1D array of analog waveforms
Digital waveform
Digital table
Dynamic data
1D or 2D array of:
Signed or unsigned integers
Floating-point numbers
Timestamps
Booleans
Alphanumeric strings that do not contain null characters

Regarding Conversion of the Charecter field Into Lowercase in an ALV REPORT

HI ALL,
I have created an editable alv Report. In which i have a coloumn with charecter field where i can enter 64 charecters. when ever i have enter and moved to another Tab its converting into Capital Letters. I need to stop it conversion. Can any one suggest me Regarding It. I am Using the Docking Container and method set_table_for_first_display for displaying the Grid.
Please give some suggestion in order to control conversion of charecters.
Thanks in Advance.
Naresh

What Kind of Dataelement/Domain you are using? CHAR60? Then try TEXT60 f.e.
Maybe you check this out
http://help.sap.com/saphelp_erp2005/helpdata/DE/bf/3bd1369f2d280ee10000009b38f889/frameset.htm
and there the FC option lowercase..
Edited by: Mathias Maerker on Apr 23, 2009 2:14 PM

Uniqueness of conversation IDs(?)

In WebLogic81sp5/WLI8.5 I use a service control to call a conversational Web service from a JPD process. The service control exposes two methods, clientRequest (conversation state: start) and a callback method, clientResponse (conversation state: finish).
When I call the clientRequest method (in a Control send node), the service control generates a unique conversation id of the form:
[<processInstanceID>]myserviceControl:<AUniquePart>
Now, the web service may not reply, so I put a Timeout path on my Control send/Control receive structure, configured to retry once. In case the response does not arrive within, say, 1 minute, the request is resent, generating a new conversation ID for the service control:
[<processInstanceID>]myserviceControl:<AnotherUniquePart>
So far, so good. But now the fun starts: Assume that the first response was only delayed, not lost. After 1.5 minutes it arrives, bearing the original conversation ID in a <CallbackHeader> element in the SOAP header. Because the service control is now tied to the new conversation ID, I would expect the Workshop framework to ignore the incoming (delayed) response and just return a SOAPFault saying that the conversation ID is unknown.
However, the process happily accepts the old message, even if the conversation ID is outdated?
In fact, when the second response arrives, IT triggers a SOAPFault stating that the conversation is unknown.
Workshops seems to discard the unique part of the service control conversation ID, given that the error message reads: "An attempt was made to send a request to conversation id <processInstanceID>. This is not a valid conversation id." So for conversation control, Workshop only uses the process instance ID?
I tested this theory by having the web service return with a modified conversation ID in the header, like:
[<processInstanceID>]myserviceControl:BLAHBLAHBLAH
Indeed, the process happily accepts this response and continues?!
Is this how the Workshop framework is supposed to work, or is there some switch that I am not aware of? In other words, how can I make sure that Workshop does not loose the uniqueness of a service control ID and just accepts any incoming message to the process instance in question?
(This becomes a serious issue if the control is used more than once in a process. Assume requestA will generate responseA ('SUCCESS'), and requestB will generate responseB ('FAILURE'). If the Control receive node waiting for responseA times out, it causes requestA to be resent. Now, if the first responseA is received, it will appear to the process as belonging to the second requestA. This is not critical; however, when the process now sends off requestB, it receives (and accepts) the second responseA as belonging to requestB! Since responseA and responseB differ (SUCCESS/FAILURE), the process now thinks that requestB went fine even though it actually failed.)
If you are still with me so far, I thank you for reading and apologize for the lengthy post...
/ Anders

Hi Anders
Hi
I tested your scenario and it seems to work as designed.
It is true that the process Instance Id is what JPD considers and not the whole of conversationId.
So which ever response "comes first" will be consumed and other will get dropped.This is what we see now.
Here are the convId and the results for 2 concurrent requests.
JPD ---> Service control ---> JWS
Req 1:
<conversationID>[1152668451563]ws:192.168.1.100-1be3a66.10c6056ed9d.-7f8d</conversationID>
Retry1:
<conversationID>[1152668451563]ws:192.168.1.100-1be3a66.10c6056ed9d.-7f87</conversationID>
Response1:
Actual response with convId [1152668451563]ws:192.168.1.100-1be3a66.10c6056ed9d.-7f8d
Retry1 Response:
Failure with conv Id [1152668451563]ws:192.168.1.100-1be3a66.10c6056ed9d.-7f87
com.bea.wlw.runtime.core.bean.ConversationNotFoundException: An attempt was made to send a request to conversation id 1152668451563. This is not a valid conversation id. The most common cause of this exception is an attempt to send a request to a conversation that has already been
Request2:
<conversationID>[1152668454958]ws:192.168.1.100-1be3a66.10c6056ed9d.-7f8a</conversationID>
Retry of request2:
<conversationID>[1152667953547]ws:192.168.1.100-1be3a66.10c6056ed9d.-7fa5</conversationID>
Response1:
Actual response with convId [1152668454958]ws:192.168.1.100-1be3a66.10c6056ed9d.-7f8a
Retry1 Response:
Failure with conv Id [1152667953547]ws:192.168.1.100-1be3a66.10c6056ed9d.-7fa5
com.bea.wlw.runtime.core.bean.ConversationNotFoundException: An attempt was made to send a request to conversation id 1152668451563. This is not a valid conversation id. The most common cause of this exception is an attempt to send a request to a conversation that has already been
MULTIPLE CONTROL INSTANCES:
In this case I believe we can use control factory to create multiple control instances and so they get unique control instance id also and so the responses are consumed correctly not across the requests as you mentioned here.
You can define a factory like
* @common:control
private test.WsControlFactory wsFac;
and then create the instances by
public void wsSayHello1() throws Exception
WsControl ws1 = wsFac.create();
WsControl ws2 = wsFac.create();
ws1.sayHello(timeout);
ws2.sayHello(timeout);
I have tested this scenario also.
the conv id looks like
control instance1 (ws1)
<conversationID>[1152668886228]wsFac:0:192.168.1.100-1be3a66.10c6056ed9d.-7f79</conversationID>
control instance2 (ws2)
<conversationID>[1152668886228]wsFac:1:192.168.1.100-1be3a66.10c6056ed9d.-7f77</conversationID>
control instance1 retry
<conversationID>[1152668886228]wsFac:2:192.168.1.100-1be3a66.10c6056ed9d.-7f6f</conversationID>
control instance2 retry
<conversationID>[1152668886228]wsFac:3:192.168.1.100-1be3a66.10c6056ed9d.-7f6d</conversationID>
Please let me know if you have any questions or you see a different behavior.
Thanks
Vimala

What are forms, interfaces, conversions and enhancements?

Hello Experts,
Please enlighten me on what are those terms. Any examples would be highly appreciated. Thanks guys and take care!

hi ,
Forms :
1. They r Client Independent.
2. It contains more than one main window.
3. Multiple layout is possible in smart form.
4. Colors can be given in script form.
5. Function modules can be generated automatically.
6. background is possible.
coming up to an Interface:
Interface is a system or a device that is used to connect two unrelated or non-understanding entities.
This definition to an interface could be the key to your answer.
As you might already know, Interface does not provide any implementation but just defines a set of protocols that can be implemented by any class.
Let us consider a few examples...
You and the bicycle. Both of you are not related in anyway. But you want to ride the bicycle. How do you interact with the bicycle? You do it via the pedal which is an interface between you and the bicycle.
You could extend this concept to 'You' and the 'Television' where the interface is a remote control.
conversions :
SAP provides a conversion for SAPscript documents to SMARTforms.
This is basically a function module, called FB_MIGRATE_FORM. You can start this function module by hand (via SE37), or create a small ABAP which migrates all SAPscript forms automatically.
You can also do this one-by-one in transaction SMARTFORMS, under
Utilities -> Migrate SAPscript form.
You could also write a small batch program calling transaction SMARTFORMS and running the migration tool.
Enhancements :
CMOD is the Project Management of SAP Enhancements (i.e., SMOD Enhancements). SMOD contains the actual enhancements and CMOD is the grouping of those SMOD enhancements.
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for function module exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
For Example:
The program for transaction VA01 Create salesorder is SAPMV45A
1. If you search for CALL CUSTOMER-FUNCTION program SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
    xvbak   = vbak
    xvbuk   = vbuk
    xkomk   = tkomk
importing
    lvf_subrc = lvf_subrc
tables
    xvbfa = xvbfa
    xvbap = xvbap
    xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
2. How to find user exits
Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.
Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.
or use this ABAP program to search for user exits :-
Finding the user-exits of a SAP transaction code
3. Using Project management of SAP Enhancements
You want to create a project to enhance transaction VA01
- Go to transaction CMOD
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used for 1 project. If the enhancement is allready in use, and error message will be displayed
- Press Save
- Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002.
- Double Click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and create a salesorder. Note that Sold-to-party now automatically is "2155"
if u find tht its an helpful answer dont forget to reward points for it.
with regards,
madhuri

What are the conversion rules

what are the conversion rules?can anybody give information on that?points wil be rewarded?

hI..
From sap help....
<b>Conversion Rules for Elementary Data Types</b>
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character
<b>
Conversion table for source type C</b>
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
<b>Source Type Date</b>
<b>Conversion table for source type D</b>
<b>Target
Conversion</b>
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
<b>Source Type Floating Point Number
Conversion table for source type F
Target
Conversion</b>
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
<b>Source Type Integer</b>
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
<b>Source Type Numeric Text
Conversion table for source type N</b>
<b>Target
Conversion</b>
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
<b>Source Type Packed Number</b>
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
<b>Conversion table for source type P
Target
Conversion
</b>
C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
<b>Source Type String
Conversion table for source type STRING
Target
Conversion</b>
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.
<b>
Source Type Time
Conversion table for source type T
Target
Conversion</b>
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
<b>Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion</b>
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.
Conversion Rules for Internal Tables
Internal tables can only be converted into other internal tables. You cannot convert them into structures or elementary fields.
Internal tables are convertible if their line types are convertible. The convertibility of internal tables does not depend on the number of lines.
<b>Conversion rules for internal tables:</b>
Internal tables which have internal tables as their line type are convertible if the internal tables which define the line types are convertible.
Internal tables which have line types that are structures with internal tables as components are convertible according to the conversion rules for structures if the structures are compatible.
<b>Conversion Rules for Structures</b>
ABAP has one rule for converting structures that do not contain internal tables as components. There are no conversion rules for structures that contain internal tables. You can only make assignments between structures that are compatible.
You can combine convertible structures in the following combinations:
Converting a structure into a non-compatible structure
Converting elementary fields into structures
Converting structures into elementary fields
In each case, the system first converts all the structures concerned to type C fields and then performs the conversion between the two resulting elementary fields. The length of the type C fields is the sum of the lengths of the structure components. This rule applies to all operations using structures that do not contain internal tables.
If a structure is aligned, the filler fields are also added to the length of the type C field.
A non-aligned structure without filler fields:
If you convert a structure into a shorter structure, the original structure is truncated. If you convert a structure into a longer one, the parts at the end are not initialized according to their type, but filled with blanks.
It can make sense to assign a structure to another, incompatible, structure if, for example, the target structure is shorter than the source, and both structures have the same construction over the length of the shorter structure. However, numeric components of structures that are filled in incompatible assignments may contain nonsensical or invalid values that may cause runtime errors.
DATA: BEGIN OF FS1,
INT TYPE I VALUE 5,
PACK TYPE P DECIMALS 2 VALUE 2.26,
TEXT(10) TYPE C VALUE Fine text,
FLOAT TYPE F VALUE 1.234e+05,
DATA TYPE D VALUE 19950916,
END OF FS1.
DATA: BEGIN OF FS2,
INT TYPE I VALUE 3,
PACK TYPE P DECIMALS 2 VALUE 72.34,
TEXT(5) TYPE C VALUE Hello,
END OF FS2.
WRITE: / FS1-INT, FS1-PACK; FS1-TEXT, FS1-FLOAT, FS1-DATE.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
MOVE FS1 TO FS2.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
Message was edited by:
Rammohan Nagam

Numeric control to hex(in numeric control) conversion ?

Similar Messages

Maybe you are looking for