ALE conversion rules

Hi All,
We are downloading HR master data into CRM through ALE.
I have a requirement where in the telephone numbers for employees should not come into CRM from HR.
I am trying to do this with the help of conversion rules where I am specifying that the particular field in the segment be overwritten by a constant. However, I cannot have a blank value as a constant, hence am having to put some character like a '.'
Can anyone please let me know if there is an option by which any particular field can be just blanked out?
Regards,
-Sweta

Hi;
n the ALE implementation guide (IMG) choose:
Transaction SALE ® IDoc Interface/Application Link Enabling (ALE) ® Model and Implement Business Processes ® Set-Up Conversion between Sender and Recipient
Proceed as follows:
       1.      Create rule: The rules are defined per segment.
       2.      Maintain rule: Rule maintenance specifies conversion rules at field level.
       3.      Assign rule to a message type: The assignment specifies when the rule is to be applied. This is sender/recipient and message type specific.
Regards
Shashi

Similar Messages

Query about ALE conversion rule

Hi,
   I am trying to copy an ALE conversion rule from one system to another.
   In the rule, for one of the variables, the option 'Set Variable' is selected and a variable '&PRTMVxxxx' (Name changed)
   is set under 'Rule Type'.
   I was not aware of how this variable gets filled or what additional setting is required.
   Could someone help me out with this option under the conversion rules?
Regards,
Sudeep

Hi Gaurav,
I have exactly the same problem that you had back in late 2006, with the Conversion Rules somehow not passing the data to the IDOC segment.
The IDOC segment is cleared of all values with the Conversion Rule active.
I have managed to determine that the exit is working properly, at least to the point where it is finished in EXIT_SAPFKCIM_001, and SENDER_SET_NEW is filled correctly.
Did you manage to figure out what was wrong?
Does anyone else know how to get this working?
Thanks,
Bruno

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"

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 Conversion Rules: Make recv'r dependant on different sender segment?

Hi Everyone,
I am putting in a conversion rule for MBEW-LIFO. I need this field to be checked on the receiving end ONLY for certain Material Types.
I know I can create a conversion rule to place in 'X' in MBEW-LIFO, but can I make that dependant upon Material Type, which is not in the E1MBEWM segment? I believe material type is in E1MARCM....
thanks!
Jen

hi Sudeep.
kindly look at this thread as reference ,inorder to get rid of your problem
aler&idocs
Regards
Saurabh Goel

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

Conversion rule in ALE/IDocs

Hi,
   I have a requirement to make use of conversion rules in ALE/IDocs.
   For a particular field, I need to concatenate the values of two other fields in the IDOC segment
   and populate the value. The other direct options like setting a constant or changing a field's value
   work fine.
   But I was not able to figure out how to implement this option. Does anyone have an idea?
Regards,
Sudeep

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

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

IDOC reprocessing with new conversion rules

Hi All,
we've created IDOCs and after the creation the conversion rules are changed. Now we want to reprocess the IDOC's and in the reprocessing we want to use the new conversion rules.
I've tried just reprocessing, I also tried WE19, but with these 2 the conversion rules seem to left untouched.
Has anyone a solution were I can reprocess making use of the new rules?
kind regards,
Pieter

Hi,
I've debugged the reprocessing of the idoc and it seems indeed I had to change the status, however not all statusses result in reprocessing of the rules. Status '29' Error in ALE Service works. So my problem is solved.
Thank you.
kind regards,
Pieter

Idoc Conversion rule, Change pointers and Filters

Hi Experts,
Please any one can help me out, i need material or clear picture about Idoc Conversion rule, Change pointers and Filters where we can use these concepts what is the befit for these concepts.
Thanks in advance,
Ramesh.

Hi,
Check this link. It has got some of the tutorials you are looking for.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Cheers
VJ

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.

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

Error in global conversion rule for InfoObject 0PERSLANGU when activating

Dear Experts
We are working on HR in BI7.0 with Ehp1.
I am trying to Activate the Transfer Rules of 0HR_PA_PA_1 DataSource which has the BID (BW Development) as the Source System to itself in order to load 0PAPA_C02 (Headcount) InfoCube.
When trying to Activate, it gives the following error message:
Error in global conversion rule for InfoObject 0PERSLANGU
Message no. RSAR263
Diagnosis
Errors with the global conversion rule for the field 0PERSLANGU.
System Response
The function module delivers the following error message:
Incorrect statament: Expression missing Operand mi
Procedure
Check the definition of the global conversion rule for an InfoObject.
In fact, we are Re-implementing 3.0b BW System in new BI7.0 Ehp1 System. I have checked the Config of InfoObject 0PERSLANGU to the one available in existing BWP (3.0b Production) system and it's all the same.
Has anyone come across similar error message and how did you resolve. Any help is very much appreciated.
Many Thanks,
Chandu

HI Chandu ,
It is a bug in the system , can you take a look at the SAP note
Note 1070702 - RSAR 263: Error in global conversion rule for InfoObject
Hope it helps ,
Regards,'
Sathya

Error in global conversion rule for InfoObject 0INCOTERMS2

When I activate BI content 2LIS_12_VCITM with transfer rule, The transfer rule was error with the message " Error in global conversion rule for InfoObject 0INCOTERMS2" and Mgs No. 263.
The transfer rule cannot be activated.
I checked the 0INCOTERMS2 infoObject . The global conversion rule is no error.
The global conversion is in below.
============================================================
PROGRAM CONVERSION_ROUTINE.
Type pools used by conversion program
TYPE-POOLS: RSD, RSARC, RSARR.
TYPES: DE_0INCOTERMS2(000028) TYPE C.
Conversion rule for InfoObject 0INCOTERMS2
    Data type       = CHAR
    ABAP type       = C
    ABAP length     = 000028
FORM CONVERT_0INCOTERMS2
USING    RECORD_NO LIKE SY-TABIX
           SOURCE_SYSTEM TYPE RSA_LOGSYS
           IOBJ_NAME TYPE RSIOBJNM
CHANGING RESULT TYPE DE_0INCOTERMS2 " InfoObject value
           RETURNCODE LIKE SY-SUBRC.
$$ begin of routine - insert your code only below this line        -
TRANSLATE RESULT TO UPPER CASE.
$$ end of routine - insert your code only before this line         -
ENDFORM.
=================================================================
If you have any idea or face the similar problem, please suggest solution.
Thank you.

Good afternoon,
If you have not done so already can you apply the SAP note 1387854 in your system and it should prevent the problem from happening again. If you also reactivate the infoobject 0INCOTERMS2 in RSD1 then it should be possible to manually activate the transfer rule.
Best Regards,
Des

ALE conversion rules

Similar Messages

Maybe you are looking for