Using conversion rule to convert quantity fields

Hi!
I am trying to find a way to use a conversion rule to convert a quantity specified in one unit of measure to the corresponding quantity specified in a different unit of measure. I was trying to use 'Copy sender field' along with a custom 'Special conversion rule'. However, the code to convert quantities requires both the quantity and material number to do the UoM conversion. 'Copy sender field' only allows the transfer of one sender field. Is there a way to transfer two sender field into a 'Special conversion rule'. Any help much appreciated and rewarded. Thanks, Duncan

Hi Duncan,
Try FM UNIT_CONVERSION_SIMPLE.
Regards,
Atish

Similar Messages

Convert quantity field

Hi All,
How would I convert quantity field thats coming into XI as 6.000 to 6?? On the receiving side quantity is of integer data type.

use the standard function 'formatNum' to achieve this...
the parameter of 'formatNum' should be set to '#'....
Thanks,
Renjith
Message was edited by:
Renjith Andrews

Convert quantity field to char field

Hi folks ,
i have a requirement where i need to convert quantity field value to char field value so as to send in idoc.
plz help me .its urgent
regards,
chandra

data: f1(17).
f1 = qauntity_field.
lenth of the field f1 is the same or gr8 than quan_field also add one more place for decimal .
ex-
ur quan_filed like 13 and 3 decimal place than ur char field must be
13 + 3 + 1(for decimal) = 17

Using a rule to auto-populate fields

I'm using InfoPath/SharePoint 2010.
I work for a law firm and I am designing an InfoPath form for a SharePoint portal. We have a database will a list of matter numbers and names. One of the fields is called, Matter number and the other, Matter name. I want users to be able to type
in the matter number, and have that number validated against the database to auto-populate the matter name in the matter name field. Does anyone know how I would be able to do that?

This would be done in InfoPath.
Click on your Matter Name field and then select properties. For default value, select the data source as your other data source and then highlight the Matter name field. Click filter data and use the form field for Matter number.
Check out this article:
http://blogs.msdn.com/b/bharatgupta/archive/2013/03/07/create-cascading-dropdown-in-browser-enabled-infopath-form-using-infopath-2010.aspx
Andy Wessendorf SharePoint Developer II | Rackspace [email protected]

Different values within "conversion rule" possible?

Hi,
in context of the HR-CRM-integration we are using a conversion rule for converting the private address (IT 0006) to a constant value by using trx bd62 -> bd79 -> bd55. This conversion rule works quite fine, but the disadvantage is that we can only define one address for all.
Is there a way using conversion rules for converting to several addresses? E.g. we have some employees in the USA, and others in Germany. Depending on the country maintained in the IT0006 we would like to convert the addresse for the colleagues in the USA to address1, for german employees to address2. At last we need something like a condition-express: "if... then". Is there anything possible achiving it, please?
Thank you
Maik

Found it by my own. In the transaction bd79 is it possible to use different rule types. With using "Convert/copy" we could define different search criteria for "sender fields". By setting some conditions we could filter, and set then the "Value receiver field" with proper fields.

Lsmw..........Step 5: Maintain Field Mapping and Conversion Rules

Hi All,
After maintaining all the four steps in LSMW, when I goto Step 5, I cannot see any fields which I have created in recording to map the fields to source fields. If i remember correctly there is a button to click to see all the fields under "Fields" after TCODE. Can anyone explain how to see all the fields which I have created using the recording session.
Any inputs will be highly appreciated. I can explain the issue if some one didnt get this?
Regards
Shane.

Hi All,
My question is, In step 5, when I go to map fields, under the "Fields" I can only see four sub nodes. and they are
Fields
          __BEGIN_OF_RECORD__ Before Using Conversion Rules
                    Rule :   Default Settings
                    Code:    MATMAS = INIT_MATMAS.
          TABNAME                      Table Name
                    Rule :   Default Settings
                    Code:    MATMAS-TABNAME = 'MATMAS'.
          TCODE                        Transaction Code
                    Rule :   Default Settings
                    Code:    MATMAS-TCODE = 'MM01'.
        __END_OF_RECORD__   After Using Conversion Rules
                    Rule :   Default Settings
                    Code:    transfer_record.
My question is after TCODE, i should see all my fields to assign the source structre fields. I can also send the screenshot if anyof you can reply to my sapshane27 at gmail
Shane
Edited by: shane shane on Jan 18, 2009 7:14 PM

ALE IDoc Conversion Rule or BADI

Hi,
I'm new to ALE IDoc. I have a requirement to hide some sensitive data field for the HR information when outbound the Idoc.
Example, I need to outbound the IT8 Basic Pay with payscale area etc but not with the basic pay amount. I can convert the basic pay amount to zero when the idoc is being created.
I've searched through some information and found out that there are several ways to achieve it. However, I'm not sure which one is a better way.
Is it using the Conversion Rule (BD62) or using Badi or Idoc Reduction method is better?
Kindly give me some hints as I'm very confuse of which one is the better solution.
Many thanks in advance.

No user exit is needed for conversion rule.
However, you should remember that conversion rules are applied segment fields for a particular message type. So wherever the IDoc message type is used the rule will be applied. If you want to associate the rule for any other condition in addition to message type better to go with a BADI
These are steps to create and apply a conversion rule to a message type:
1. Transaction BD62 - Create conversion rule and assign it to a IDoc segment
2. Transaction BD79 - Define the conversion rule by selecting your field and clicking display button. Once inside you can use various options like set constant to map 0 to the basic pay
3. Finally assign the conversion rule to your message type using BD55
As for BADIs, IDOC_DATA_MAPPER is also suited for your requirement, the method PROCESS, allows you to manipulate your IDoc fields whichever way you want. You get the control record, data records, using which you can restrict your manipulation to specific message type or other conditions
To above post, BADI IDOC_CREATION_CHECK should not be used for mappings/conversions as its specific purpose is to stop creation of an IDoc under required conditions

Idoc conversion rule

Hi,
What is idoc conversion rule? Why we need this?
While upgrading from 4.7 to ECC 6.0 what all precautions need to be taken for the existing standard idocs and custom idocs in the system.
Thanks & Regards,
Soumya.

Hi,
ALE allows the user to perform an SAP transaction in the sending system, after-which the following steps occur:
1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent
These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer
This layer performs an RFC call, using the port definition and an RFC destination determined through the customer model
The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems
If the receiving system is an SAP system then:
In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs
In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. Eg. A PO is loaded on the sending side, yet a SO is created on the receiving system
Master data has another difference:
It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object
If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system
In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.
The Detail as described by SAP
In the output processing one of the function modules of the application creates an IDoc, the so-called master IDoc. This IDoc is sent to the ALE layer where the following processing steps are applied:
Outbound processing
Receiver determination
An IDoc is similar to a normal letter in that it has a sender and a receiver. If the receiver has not been explicitly identified by the application, then the ALE layer uses the customer distribution model to help determine the receivers for the message.
The ALE layer can find out from the model whether any distributed systems should receive the message and, if so, then how many. The result may be that one, several or no receivers at all are found.
For each of the distributed systems that have been ascertained to be receiver systems, the data that is specified by the filter objects in the customer distribution model is selected from the master IDoc. This data is then used to fill an IDoc, and the appropriate system is entered as receiver.
Data selection
Segment filtering
Individual segments can be deleted from the IDoc before dispatch by selecting Functions for the IDoc processing -> Settings for filtering in ALE Customizing. The appropriate setting depends on the sending and receiving logical R/3 System.
Field conversion
Receiver-specific field conversions are defined under Functions for the IDoc processing -> Conversions.
General rules can be specified for field conversions; these are important for converting data fields to exchange information between R/2 and R/3 Systems. For example, the field "plant" can be converted from a 2-character field to a 4-character field.
The conversion is done using general EIS conversion tools (Executive Information System).
Version change
SAP ensures that ALE functions between different R/3 System releases. By changing the IDoc format you can convert message types of different R/3 releases. SAP Development use the following rules when converting existing message types:
Fields may be appended to a segment type;
Segments can be added;
ALE Customizing keeps a record of which version of each message type is in use for each receiver. The correct version of the communication IDoc is created in the ALE output.
The resulting IDocs (it is possible that several IDocs could be created in the receiver determination) are referred to as communication IDocs and are stored in the database. The dispatch control then decides which of these IDocs should be sent immediately. These are passed to the communications layer and are sent either using the transactional Remote Function Call (RFC) or via file interfaces (e.g. for EDI).
If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created. The ALE administrator can use this workflow to process the error.
Inbound processing
After an IDoc has been successfully transmitted to another system, inbound processing is carried out in the receiver system, involving the following steps in the ALE layer:
Segment filtering
Segment filtering functions the same way in inbound processing as in outbound processing.
Field conversion
Specific field conversions are defined in ALE Customizing.
The conversion itself is performed using general conversion tools from the EIS area (Executive Information System).
Generalized rules can be defined. The ALE implementation guide describes how the conversion rules can be specified.
One set of rules is created for each IDoc segment and rules are defined for each segment field.
The rules for converting data fields from an R/2-specific format to an R/3 format can be defined in this way. An example of this R/2 - R/3 conversion is the conversion of the plant field from a 2 character field to a 4 character field.
Data transfer to the application
Input control
When the IDocs have been written to the database, they can be imported by the receiver application.
IDocs can be passed to the application either immediately on arrival or can follow in batch.
You can post an inbound IDoc in three ways:
by calling a function module directly: A function is called that imports the IDoc directly. An error workflow will be started only if an error occurs.
by starting a SAP Business Workflow. A workflow is the sequence of steps to post an IDoc.
by starting a work item A single step performs the IDoc posting.
The standard inbound processing setting is that ALE calls a function module directly. For information about SAP Business Workflow alternatives refer to the online help for ALE programming.

Problem with quantity field in BDC

hi experts,
               i am trying to upload data from internal table to SAP using BDC, but while uploading quantity fields it is giving error as "Input fields is longer than screen field", Is there any method to upload quantity fields to SAP.
                 thanks in adancae,

Hi,
Before passing the value to perform bdc_field, convert that value to char type
For eg.
DATA :        v_val(10)               TYPE c,
v_val = wa_operation-std_value_01. CONDENSE v_val.
CONCATENATE 'PLPOD-VGW01(' n_linecount1 ')' INTO v_para.
PERFORM f_bdc_field       USING v_para           v_val.
FORM f_bdc_field USING fnam fval.
CLEAR wa_bdctab.
wa_bdctab-fnam = fnam.
wa_bdctab-fval = fval.
APPEND wa_bdctab TO it_bdctab.
ENDFORM.                    " f_bdc_field
check this it would be useful.

BD79 Idoc Conversion Rule

Hi,
I have a requirement where I have a Inbound Idoc which has two segments say E1EDP03 and E1EDP20. Both are date fields.
now I want to map date from E1EDP03 if Qualif is Z01 to E1EDP20 using conversion rule.
E1EDP03 (Qualif. Z01) - DATUM -
>>> E1EDP20-EDATU
Is it possible to do this using conversion rule?
Thanks,

Hi Shital ,
Thank U very much for replying to my question.
But when I m trying to create the same , by clicking Use general rule & specifying special conversion routine ZBLNK , it is throwing the following error "Conversion exit ZBLNK does not exist".
Please can u help me out.
Thanks,
Gyanaraj

P_ORGIN object - converting VDSK1 field to Organizational Level field

Hi there,
SAP ECC 6.0 SAP_BASIS 701 0007 SAPKB70107 SAP Basis Component
Looking for input on changind the VDSK1 field in P_ORGIN object to Organizational Level field to use Role Master and subroles(derived) concept. We currently maintain a separate role for each set of Cost Centers and infotypes. On occasion the infotypes
change but means a great deal of manual changes for each P_ORGIN defined role. Our approach is all within the P_ORGIN object - no structural auth in place. Any input or experience appreciated. We separate the functional part of the HR acess in one role tcodes/other objects and separate the master data access p_orgin in another role - which is different for each user.
Thanks !

Dan,
I hope you already heard about PFCG_ORGFIELD_CREATE, using this we can convert auth field into a org field.
There are snotes aswell on this. Please do a search in SMP.
Thanks,
Brahmeshwar.

Validation of a quantity Field gives a run time dump

I have an upload file which provide me with a quantity input field which i needs to validate for non characters and special characters.
I have used a code which does a validation for the character or special character entry in the field but i am not able to check for '.' in the entry.
the problem is if the user by mistake enters two decimal point which should only be one; the program goes for a dump.
the below given code is what i have used for validation of the quantity field.
IF NOT wa_final-actual_quan IS INITIAL.
    MOVE wa_final-actual_quan TO l_fld_quantity.
    TRANSLATE l_fld_quantity TO UPPER CASE.
    IF l_fld_quantity CA sy-abcde OR
                      l_fld_quantity CA '!~@#$%^&*"?><`|}{[]()+-='.
     *giving an error message
      v_flag1 = c_x.
    ELSE.
      CLEAR: l_fld_quantity1,l_fld_quantity2.
      SPLIT l_fld_quantity AT '.' INTO
                                  l_fld_quantity1 l_fld_quantity2.
      CONDENSE l_fld_quantity1.
      l_len = strlen( l_fld_quantity1 ) .
      IF l_len LE 10.
        IF NOT l_fld_quantity2 IS INITIAL.
          l_len1 = strlen( l_fld_quantity2 ).
          IF l_len1 LT 2.
          CONCATENATE l_fld_quantity2 '0' INTO l_fld_quantity2.
          ENDIF.
          CONCATENATE l_fld_quantity1 '.' l_fld_quantity2(2)
                                      INTO l_fld_quantity3.
          CONDENSE l_fld_quantity3.
        ELSE.
          CONCATENATE l_fld_quantity1 '.' '00'
                                      INTO l_fld_quantity3.
        ENDIF.
        wa_zphyin-acqty = l_fld_quantity3.
the requirement is that if the user enters the input for quantity it should only accept one decimal place in the field and if by mistake he enters 2 decimal points it should give an error stating :- invalid input for quantity.
experts please guide as to how i can overcome the problem.
helpfull amswers will be rewarded.

Use try..catch..endtry block to handle the error.
REPORT Z_TEST2.
data: l_num type p decimals 2.
parameter: p_value type char10.
start-of-selection.
try.
l_num = p_value.
catch cx_root.
write: 'Not numeric'.
exit.
endtry.
write: 'Numeric'.
Regards,
Joy

ALE : conversion rule for field value to become null

Dear experts,
I need to pass a material from one system to another with ALE. The problem is that the field marc-prctr (profit center) of this material is populated in the first system, but it does not exist in the second, so I assume transaction bd79 should be used to convert somehow the value of prctr to initial.
How can I do that??? I have already tried defining a conversion rule and assigning it to message type MATMAS, segment E1MARCM, but it did not work.
Please help.

Did you check this?<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d3/06f6679aaf0e44b67ca6d6b58d91df/content.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/d3/06f6679aaf0e44b67ca6d6b58d91df/content.htm</a>

Maintain Field Mapping and Conversion Rules//LSMW

Hello Friends,
I want to add new fields in the step.no.5(Maintain Field Mapping and Conversion Rules).
Indetail i'm going to upload the GL balances, for DR and CR line item fields are same so system is not accepting the same field value, so i have added 1 for the CR line item fields like in the below example.
BSEG-WRBTR(Dr line item)
BSEG-WRBTR1(Cr line item)
but BSEG-WRBTR1(Cr line item) field not displaying in the step.no.5 to mapping to source field.
please let me know the solution for this.
thanks
swapna.

Hi,
I would like to ask few questions.
1. Are you using batch input recording or using any program for uploading. (through LSMW)
2. Whether all your debit or credit line items are same every transactions. I believe they should be same, because you are uploading the balances.
You should not have two similar fields for example, if it is WMBTR, then again WMBTR should not be there, it should WMBTR1 and WMBTR2. Make sure you have done the field mapping properly. When you have done the field mapping all the fileds must have been mapped. If any one of the fields are not mapped, then it will not be uploaded.
Please see the following LSMW sample guide:
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
Maintain Object Attributes Do the recording - Make sure that you do not have two fields with the similar name. If you have two fields with the same name double click on the field name and add1 or 2 to differentiate between field names. Just Copy those fields and descriptions in excel sheet, delete the blank lines, then in excel data => text to columns, your field names and descriptions will be now in two columns. Copy them, then put your cursor on the next sheet, then edit => Paste Special => Transpose, all the columns will become your rows. Now your file structure is ready. Maintain Source Structures Give some unique structure name and description Maintain Source Fields Here you add the fields that are being used in EXCEL first sheet, just copy them and make all the fields as C (Constant) and then give length of 60 for all fields. Maintain Structure Relations Though structure relations are already created just go to this step, click on edit, then click on create structure relation, just accept the message stating that the structure relation has already been created. Maintain Field Mapping and Conversion Rules Do the field mapping for all the fields, all the fields willl be stretched and you will see five rows against each row. In case if there is any row that has NOT stretched means, there is something wrong in the mapping. Maintain Fixed Values, Translations, User-Defined Routines There is nothing to be done at this step. You can simply ignore this. Specify Files Make you must have saved your excel file as .txt (before saving make sure you have copied data from sheet2 to sheet 3 and then sheet 3 is saved at tab delimited file. Text (Tab delimited) Select your file, make SURE that you have select "TABULATOR" radio button and say OK. Assign Files Go to this step and click on Create assignment button and accept the message and say ok. Read Data Remove two check boxes and just click on execute button. See the log. Make sure you have number of entries (lines) in your excel file are matching with this. Display Read Data Display data give 1 to 999 lines and double click on one of the line and see whether fields are mapped correctly are not. Convert Data Execute and see the log match the number of entries. Display Converted Data Display converted data, give 1 to 999 and double click on one of the line and see whether fields are mapped correctly or not. Create Batch Input Session Check on Keep Batch Input sessions check box, then execute. If you select that check box, even after execution it will be there and you can analyze what happened. Run Batch Input Session (Takes you to SM35) Go to SM35 select the batch and click on process button (execute), make sure you have checked right hand side first three check boxes and FOREGROUND (because you want to save what it is creating) Say OK Keep on press ENTER on your key board in order to move the session further. If you follow these steps along with the guide, surely you should be successful. There may be small difference between the file and what I have explained but ultimately the purpose is same. Hope this is useful and let me know in case if you have any issues.
Regards, Ravi

About conversion rule using BD79

Dear experts,
I would like to fall back on your help on the conversion rule in BD79.
In our system, there is a HTTP connection used for sending IDoc to the website. The Unit of measurement need be converted when sending out to the receiver side. The problem is when I converted using BD79 with rule type 'Conver Sender fields', set conditon to convert unit '%' to 'wt%', but the value in recerive field always display in Upper letters('WT%').
Can anyone help me on this problem? if it can not be realized in this way, please show me another possible solution.
Besides, is it possbile to convert '%' to 'wt%' with some condition to make it just apply to some spectial characteristics?
Many thanks in advance.
Regards,
Benny

Are the two GSS devices clustered ? Set one up as the Master GSSM and the other as the Standby GSSM adding the source-lists you've specified. Either of the GSS devices can reply to DNS queries and these will provide an answer depending on where the request was sourced from. It also depends on your DNS Heirarchy and where the request are coming from. Is there a DNS server sitting above your GSS devices ? How are the clients configured ? Do they point directly to you GSS devices or some other DNS device ?

Using conversion rule to convert quantity fields

Similar Messages

Maybe you are looking for