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"

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 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

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: 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

Currency conversion rule not executing for manual journal entries.

Hi,
We have currency conversion business rule set in our project. THis business rule is not converting LC to other currencies for manual journal posting entries. i.e, it is audit id with DATASRC_TYPE="M".
Can any one let me know if any specific settings are to be done for this to work?
Regards,
Swetha

Hi,
Is the currency conversion working on the other datasources?
If yes, then try to post some record through input schedule in the M datasource, run the currency conversion, and see if the currency conversion is working fine or not.

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

GR/IR expenses not affected with the settlement rule run process in the GL

Please neglect by previous post with the same title
There is a problem I face while running the settlement rule process related to internal orders on the GR/IR expenses.
According to the internal order settlement rule every expense associated to an Internal order no. whether its an account payable or manual journal accounts it should be settled (distributed) on the cost centers specified in each internal order after the monthly settlement run process is done through T.Code "KO8G", and this actually happens on the entries that are booked manually through T.Code "FB50", but the GR/IR entries is the biggest problem, it didn't reflect the settlement rule distributions in the GL it just gives me the original transaction once its was automatically created through T.Code "MIGO" they are only allocated to a one profit center with no cost center and without being distributed to a multiple cost centers according to the distribution strategy.
After a long search I found that the cost center distribution occurred only on a secondary none GL account named A&P Settlement (720010), all GR/IR expenses was settled correctly only on this account not through the ordinary GL accounts (e.g. Gifts, printed materials) and of course the correct distribution didn't appear in the GL,
So is there a transaction or any way to allocate the GR/IR expenses to there correct cost centers with the correct cost element in the GL?
Is there anything to do with the GR/IR calculation that depends on quantity base not value base?
The Process as follows:
(1) Creating Internal order with a settlement rule (E.g. Cost center 1 (50%) Cost center 2 (50%)
2) Creating a purchase order associated to an internal order
3) The Goods received and creating the GR transaction T.Code "MIGO"
Acc/DR Expenses accounts
Acc/CR GI/IR Account 400301
Profit enter ###### (eg. 111177)
Cost Center <blank>
Internal order no. ####### (e.g. 9810512)

4) Closing the GR/IR accounts when receiving the invoice T.Code "MIRO"
When we receive vendor invoice:
Acc/Dr GI/IR Account 400301
Acc/Cr Vendor Account
Profit enter ###### (eg. 111177)
Cost Center <blank>
Internal order no. ####### (e.g. 9810512)
5) Performing the Internal order settlement rule run process
(N.B. By entering the report of the cost center (Actual/Plan/ Variance) T.Code S_ALR_87013611
I found that GR/IR expenses was not charged on the concerned cost centers as shown in the GL )
Your Reply is highly appreciated

Thanks for your kind reply,
But is there a way solve this problem?
And what is the use of leaving a field in the account assignment tab for an internal order while creating a PO and it will not take advantage of the settlement rule????????
And as you know the internal order settlement is a way to create a multiple account assignment
Can we solve the problem by making an automatic fake transaction that reverse the value of the GR/IR and creating another transaction can apply on it the settlement rule??
You know that settlement rule process is one of the best features in the SAP system it save time and effort to make distributions manually

Lync 2013 client not processing history spooler folder (conversation history)

We have been using Lync 2013 fully patched up to latest & greatest, along with Exchange 2013 for about 6 months now & everything is working
great. (I did a AD migration from our old parent company in the UK as well as migrated exchange from 2010 to 2013, all that without a hitch for the most part.)
the issue that seems to be popping up intermittently is conversation history. I manged to work around some of them for the most part & getting
them to process; with the exception of 1 user.
If he logs into another PC his conversation history works fine.
However on his PC it does not seem to want to process the history spooler folder in "C:\Users\User\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]m",
there are 737 files in there (all of his convo history)
Now what i did & it seems to sort of work is,Signed out of Lync, I deleted the users Sip folder after backing up the history spooler folder, logged
back into Lync which recreated the sip_user folder; logged back out of Lync , copied the History Spooler folder back to the SIP folder, & signed into Lync.
This took 10 files out of the history spooler folder, & then appeared in the convo history; both on Lync client & Outlook; but did not bring
all of them in. I did some testing and if you log out, then back in, it processes a few more. but not all.
EWS & MAPI settings & all other Lync configuration information settings match a users with no convo history issues.
So now the questions.
1)What could possibly cause what ever mechanism that processes the History spooler folder to stop/only process a few items during sign in? Also what
is the mechanism?
2)Is there any way through powershell to force the synchronization of the history spooler folder?
Thank you

so in some more testing i had check the history spooler folder, & there were about 700+ files.
as a note* (Upon deleting the users sip folder & logging back in thus re-creating the folder new convo's where saving. So i did "fix" the issue with no new convo's during my initial work prior to opening this thread.)
I then removed a good chunk of the *.hist files & only left convo's from this month. signed out then back in, 10 files processed. then did it again, another 10. did it again, & it did 4 then stopped. I noticed there were some files over 1 mb. &
remember coming across this post (Lync
not processing files over 1mb) so i removed the 1mb files & then logged out then back in. processed 10 more.
i then added all the files to the history spooler file with the exception of the files over 1 mb, & logged in & out about 70 times to process the whole folder. Now all of the convos are in Lync & outlook as well as new convo's being saved. However
i have a folder now with 130 files that are over 1mb that will not process at all..
so now i am trying to find some validity on the statement in the link above
"We did open a case with Microsoft and they confirmed it is a bug in the Exchange EWS HTTP stack. It
is supposedly under review by the Dev team, but my guess is that it won't be fix soon. The magic size is exactly 1MB or 1048576 bytes."
If that is actually true it sucks & is some B.S as it is nearly 2 months later & this is obviously
a major problem & not even a CU or PU has been released to address the issue.

Rules in Outlook are not processed in the order listed

I have created a new rule today to filter out all email that is not directly sent to me to a folder called "process later" hanging off "Inbox"
Problem is, even thou it is the last rule created, and appears to be at the bottom of the list, this seems to be the first rule that is executed.
In order to fix, I need to go into "process later" folder and run all rules on it.
Is there a way to fix this, w/o trying to re-create all the rules (I have like 40-50).

I have same issue where rules are not processed in the order they are written. All rules are "Client Only". I sort email based on the information contained in the subject line. Some should get filed into sub folders, some in the
parent. So, I have a folder called QA and a sub-folder called QA-Project 1.
#1 rule -- processes subject line looking for QA-Project 1 and puts it in QA-Project 1 folder
#2 rule -- processes subject line looking only QA and puts it in QA folder
Problem is when I run both these rules, the email with subject "QA-Project 1" ends up in the QA folder and not the QA-Project 1 Folder. So the rules are not processing sequentially. Please help.

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

Rule XVAL not processing basic pay data.

Hello experts,
While checking the log of payroll run, I find that basic pay data (IT0008 wage-types) are not processed (IT0008 wage-types are not there in the output table IT of schema function - PIT   XVAL P10            Valuate pay elements).
I am using partial period factor 2 in processing class 10. Please advice.
Thanks in advance.
Regards
Peeyoosh

Display Log
Factoring and storage
4 GEN/8 6                   Create wage types /801 to /810 in IT
4 PIT   INP1      NOAB      Determine monthly factors
4 PIT   XCM0 P31            Monthly lump sums for cost accounting
5 PIT   XVAL P10            Valuate pay elements
5 Input
0 IT
5 Processing
0 /806 Partial period factor 6
          0 1000 Basic
          0 1010 Canteen Subsidy
          0 1020 City Comp Allowance
          0 1040 Production Incentive
          0 1070 House Rent Allowance
5 Output
0 IT
4 PIT   INNP                Notice Pay Addition / Subtraction
4 PIT   X023 P20 NOAB      Gross input and storage
Input- IT
Table IT
A Wage Type       APC1C2C3aBKoReBTAwvTvNOne Amount/One Number       Amount
2 /806 Partial per01                       100000.00
2 1000 Basic      01                                                   4,500.00
2 1010 Canteen Sub01                                                     250.00
2 1020 City Comp A01                                                   3,230.00
2 1040 Production 01                                                   1,500.00
2 1070 House Rent 01                                                   2,500.00
Output - IT
                                                                                Table IT
A Wage Type       APC1C2C3aBKoReBTAwvTvNOne Amount/One Number       Amount
2 /806 Partial per01                       100000.00

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.

ALE Conversion rules not processed

Similar Messages

Maybe you are looking for