BD79 - conversion rule issue

Hi,
I am trying to send vendor master data between 2 client (on change
pointers) whenever there is change in vendor.
I have done full ale config and i can see the idoc coming in the
receiver system.
Now when i try using conversion as my requirement is to modify some
data, then i cant see the idoc data in sending or receiving system,idoc
gets created but there is no data in there.
I have attached the screenshot of my conversion steps. I am using
CREMAS with segment E1LFA1M
in BD79 i have used create proposal for rule just for testing purpose

Hi Ajay,
Try to 'Set constant' in BD79 under the section 'What happens with the non-assigned/non-converted field values?' too.
Regards,
Soumya.

Similar Messages

Can we write code using BD79(ALE IDoc Conversion Rule)

Hi -
I had created a conversion rule that specifies for the field account group (KTOKD) on KNA1: I need to include the following logic :
if the customer number (KNA1-KUNNR) is in the range 0010000000-0019999999 or 0140000000 to 0149999999, then change the account group value to u201CSKIPu201D.
So I had created a conversion rule using BD62.
In BD79, I had set the constant to SKIP.
But where to include the following logic :
if the customer number (KNA1-KUNNR) is in the range 0010000000-0019999999 or 0140000000 to 0149999999, then change the account group value to u201CSKIPu201D.
Thanks,
Gyanaraj

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

About conversion rule in 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

Hi sudeep
Could you let me know the exact steps you did to create the conversion rule for idocs.
Thanks in Advance

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 ?

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

Send custom error message using IDoc conversion rule?

Hello,
I am using an Idoc conversion rule in BD79 to load cost centers. In my conversion rule I use a conversion exit function module to concatenate 2 specific characters and sending cost center value together and then this output value placed in the receiving cost center field. This works fine, but now I want to send a custom error message to the idoc and fail the idoc if the sending cost center value is greater than 8 digits.
Does anyone know how to send an error message or update an idoc with an error message using a conversion rule (bd79)?
Thank you,
Rhonda

Hi Rhonda,
Any luck on the below.. i have a similar issue...
Sorry to hijack your thread...

Data records in an IDoc getting erased, when conversion rules are defined

Hello ,
We are sending IDocs of message type GLMAST & COELEM from a system(version 4.7) to another system (version 4.6B).
The segment data in the IDocs are changed using the user exit enhancement KKCD0001. The function exits used are EXIT_SAPFKCIM_001 and EXIT_SAPFKCIM_002.
If there is no conversion rule defined in the receiver system, for the segments, the IDocs are posted correctly in the receiving system. But if we define conversion rules , then the data records for all the segments for which conversion rule is defined are getting erased, and an error occurs during processing of IDocs
Please let me know what can be the the reason behind this issue..And how to solve this..
Thanks in advance,
Afsar

Issue solved

Conversion rule executed in sender and receiver system?

Hello experts,
I want to send an Idoc from one SAP system to another.
Both systems are in the same transport line.
In the sender system I want to execute a field conversion. There
Therefore I maintained BD62 (Define Conversion Rule), BD55 (activate Conversion Rule for Sender/Receiver combination) and BD79 (Specifie Conversion).
The mapping works perfectly.
The creation of the IDoc and the field conversion work perfectly.
But I get an error in the receiver system.
It seems that this system also tries to execute the fieldmapping, because it has the same BD55 (sender/receiver) settings.
The conversion rule itself does not exist in the receiver system, as these settings are not contained in a transport request.
What is the correct way? Can I customize BD55 not to generate a transport request and maintain this setting only in the relevant system?
Or do I need to maintain BD79 and BD62 also manually in the receiver system?
any hints
Barbara

Hi Barbara,
you have to maintain BD79 and BD62 manually in all receiver Systems.
Kind regards
Werner

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>

ALE Conversion rules not processed

Hi all,
I defined some conversion rules for an inbound IDoc with trascation BD79 in my backend system.
If I send an IDoc from XI to the backend system the rules are ignored:
Status 64
No filters , No conversion , No version change .
If I try the SAME Idoc with WE19 using the standard inbound, it works:
Status 64
No filters , Fields converted , No version change.
Any idea? I guess it's a bug.
Thank you.
Stefano

FYI
http://help.sap.com/saphelp_erp2005/helpdata/en/80/411a73382b44d0a1667816716f5b37/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/f9/c3075cac7d11d39460005004580996/content.htm
Hope thisll give you idea!!
Pl... award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

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

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

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

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.

ALE conversion rules - Using a Mapping table

Hi, I need to use ALE conversion rules to modify Objects IDs using a custom mapping table. I´m looking BD79 transaction but I didn't find a place to use a mapping table..does anyone know how to do it?
Thanks!

FYI
http://help.sap.com/saphelp_erp2005/helpdata/en/80/411a73382b44d0a1667816716f5b37/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/f9/c3075cac7d11d39460005004580996/content.htm
Hope thisll give you idea!!
Pl... award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

BD79 - conversion rule issue

Similar Messages

Maybe you are looking for