Help with BD79 - IDOC conversion rules

Hi, I'm looking for a "How to" guide to help me with this transaction.
I need to do a very simple rule for segment E1MTXHM, in ABAP it can be done like this:
IF EMTXHM-TDID = 'IVER'.
E1MTXHM-TDSRPAS = 'Z'
ELSE.
* Source field
ENDIF.
But I expect that it's not necessary to write code to do that simple conversion in BD79, so can anyone help me?
Thank you.

Thanks Pawan,
It's a very interesting blog, I already know how to do the first part of the blog but maybe someday I didn't know how to use a user exit.
In my scenario I need to create a more simple rule, but I don't know how to use transaction BD79. But I think with "Try and Error" I will get my expected result.

Similar Messages

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

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.

Errors with the global conversion rule for the field 0SOURSYSTEM.

Hello Gurus,
We are implementing CRM Activities. I enhanced the data source and when I add new info objects to 0SAL_DS01 DSO and trying to activate I'm getting there errors. Can some one please help me out in this problem?
Error in global conversion rule for InfoObject 0SOURSYSTEM
Message no. RSAR263
Diagnosis
Errors with the global conversion rule for the field 0SOURSYSTEM.
System Response
The function module delivers the following error message:
Field "" is unknown. It is neither in one of t
Procedure
Check the definition of the global conversion rule for an InfoObject
What does this error mean? We are using BI 7.
Thanks
RKR

I have around 9 source systems, do I have to maintain data for all of them for 0SOURCESYSTEM?
I set data for CRM system and then tried to activate.. but still I'm getting same error.
I;m getting this warning too...
InfoObject 0FISCVARNT needs to be in key for DataStore object C_0SAL_D
Message no. RSDODSO123
Diagnosis
Characteristic 0FISCVARNT is included in the data part of ODS object C_0SAL_D.
System Response
The fiscal year variant cannot be used in the update rules for calculating business hour characteristics.
Does this matter???
Thanks
RKR
Message was edited by:
RKR M

Errors with the global conversion rule

Hi Guys,
When I activate the DSO,I get an error "Errors with the global conversion rule".I applied OSS note 1387854.But the problem still persists.I did not find any replies on SDN for this error,so posting it again.
If anyone knows how to proceed,please help! <REMOVED_BY_MODERATOR>
Thanks,
Sri
Edited by: Pravender on Dec 9, 2010 4:51 PM

the error might show due to which infoobject this error is happening.
that particular infoobject might conatin a transfer routine. Open the transfer routine in the infoobject, do a dummy change, save the routine and activate the infoobject, then try activating the DSO.
this might do the trick . Hope this helps.
rgds, Ghuru

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 Rules

Hi all,
Good Morning Friends. I am looking for proper documentation which can help me to understand the concept of <b>Idoc conversion rules</b>. I search a lot in help.sap.com and also google resources, but couldn't figure out any. I am very much interested in comprehending this concept from quite a long time. Can anyone help me to find out good doc's on this concept. If you have any documents you can plz forward them to <b>[email protected]</b>.
Any kind of help will be appreciated and will be awarded points without failing.
Have a nice day !!
Thanks and Regards,
Varun.

HI Ferry LIanto,
Thanks for your immediate reply. I have gone through this. I also want to learn the theoritical aspects behind this concept. Is there any documentation available in help.sap.com regarding this or are there any other resources available to learn this very much in detail ? I have tried rigorously, but couldnt trace any. If possible can you please help me in this regard ?
Thanks and Regards,
Varun.
Message was edited by: varun sonu

Need Help with data type conversion

Hello People,
I am new to java, i need some help with data type conversion:
I have variable(string) storing IP Address
IPAddr="10.10.103.10"
I have to call a library function which passes IP Address and does something and returns me a value.
The problem I have is that external function call in this library excepts IP Address in form of a byte array.
Here is the syntax for the function I am calling through my program
int createDevice (byte[] ipAddress).
now my problem is I don't know how to convert the string IPAddr variable into a byte[] ipAddress to pass it through method.

Class InetAddress has a method
byte[] getAddress() You can create an instance using the static method getByName() providing the IP address string as argument.

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

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

Help with Creating a Business Rule...

Hi All,
I am using Planning 11.1.1.1.0.
I have created a classic planning application and now have to incorporate a way to copy data from one slice of the essbase db to other.
I am trying to copy data from the following slice
Entity : EasternZone
Version:Working (Bottom Up)
Scenario: Actuals
Currency:USD
Period:YearTotal
Year: 2007
to
Entity : EasternZone
Version:Working (Bottom Up)
Scenario: Actuals
Currency:USD
Period:YearTotal
Year: 2008 and increase by a certain percentage which is not fixed..
How should i go about achieving this using business rules? (Calc manager is used with only EPMA applications so where do i create the business rule?) Can somebody share some ideas please?
Any help would be greatly appreciated.
Kind Regards.
Alicia

Hi!
Are you transferring data in same application from db to another? If yes, then possibly you could use @xref function.
for example :
fix ("EasternZone", "Working","Actuals","USD","YearTotal")
"2008" = @xref("_name of source db location alias_","2007")*[RunTimePrompt for percentage];
endfix
The name of the location alias you can find from destination db --> edit --> location aliases. There you can see the location alias name of the source db.
if you want to be sure about block creation then you could also add the following rows at the beginning
/*fix ("EasternZone", "Working","Actuals","USD","YearTotal","any account")*/
/* "2008" = 0;*/
/*endfix*/
kind regards,
user637777

Help with INVOICE01 iDoc

Hello,
I'm trying to do a MIRO from an INVOICE01 iDoc using TEST tool WE19 and function module "IDOC_INPUT_INVOIC_MRM".
I can get it to post the MIRO properly for a non taxable item but as soon as I try to post to a PO line that is taxable I get error "Balance not zero: 17.37 debits: 133.65 credits: 151.02"
This line has total invoice amount of $151.02, total amount excluding tax of $133.65, and tax amount of $17.27.
I cannot figure out where on the idoc these values need to be. I've tried every variaton I can think of and I'm stumped.
Any help would be appreciated. I need to know which records and segments I need to use. And I'm under considerable pressure to figure this out "yesterday". Thank you.
Dan

Hello;
I got the same error message. I was able to solve it by following oss note 398414.
I put below an extract of what need to be change in the customizing.
Note 398414 - EDI: processing of tax code / tax amount
Symptom
You want to edit an invoice via EDI. The invoice Idoc, however, runs into status "51" (incorrect). The system generates error message M8534:
"Balance not zero: & debits: & credits: &"
With the amount displayed as a balance, it is the tax amount.
Additional key words
idoc, idoc_input_invoic_mrm, idoc_input_invoic_mm, M8534, tax
Cause and prerequisites
Consulting
Solution
On the item level (segment E1EDP04) only the tax codes are read when the invoice Idocs are processed; the tax amounts are not read from these segments.
For each tax code, a segment E1EDK04 must exist with the total tax amount for this control indicator on the header level. Thus, the tax amounts are read from these segments (E1EDK04).
You must set the Customizing for the creation of the invoice Idoc so that the corresponding E1EDK04 segments are generated. Change this setting by using Transaction V/08. To do this you must setthe tax condition as follows: "S: Printing at totals level".
Hope it is helping.
Regards
Arnaud

Help with ID3 tag conversion

hi - I use a product called Squeezecenter as a music server to drive a couple music devices, and in order for it to read tags and artwork properly it needs to used v 2.3. iTunes has always given me the option to select all tracks and convert to v2.3, no problem. Recently I re-ripped my entire CD collection (to AIFF) and also buy high resolution tracks online and transcode from WAV to AIFF. AIFF has tagging capability, but now that my entire library is AIFF and some Apple Lossless, iTunes is no longer giving me the option to convert tags to v2.3 (which I used to do after I added new tracks to ensure compatibility). So, anyone know what version iTunes uses by default with the AIFF format now that I don't have the convert option? (I have a 2nd library with my lossy collection and it still has the option to convert tags, so I'm guessing it's the presence of MP3 or AAC that allows for this?).
So anyone know how to access the tag conversion feature when just AIFF/Apple Lossless files or which version of tags it might be using? Thank you!

Hello Odetojoy,
Thank you for your post.
It will be helpful in your next post, to include your method
of PDF creation, and also your page-setup settings prior to
printing. It is possible that those got mixed up accidentally.
Other than that suggestion:
You should know that these forums are specific to the
Acrobat.com website and its set of hosted services, and do
not cover the Acrobat family of desktop products.
Please visit the following Acrobat forums for any questions
related to the Acrobat family of desktop products:
http://www.adobeforums.com/cgi-bin/webx/.3bbeda8b/
Cheers,
Pete

Need Help with simple date conversion

Hi all,
I have been creating integrations from custom Oracle tables to my Hyperion Planning application. I have most of them working, but am having issues loading dates to the application.
The dates in the source are formatted as M/DD/YY.
Hyperion can only recieve the dates if they are in MM-DD-YYY format. (atleast that is the error I receive when I load the interface)
Could someone please help me build an ODI expression that will convert/format the date? My SQL is pretty weak.
Thanks,
Nick

Thanks for the reply. I guess one of my issues is I am trying to do this conversion in my Sunopsis Memory Staging Area. So I guess I should be using SQL to convert the date, but I am still having issues.
Here is the error from my log file when I attempt a straight mapping of the date...
B9708547A,Plan1,2001-08-27,OrganizationNone,Project Type None,BegBalance,FY11,RateNone,Working,Final,Cannot load dimension member, error message is: com.hyperion.planning.HspRuntimeException: Date is incorrectly formatted, expecting "MM-DD-YYYY" format.
Here is the SQL statement from the operator when I attempt (poor attempt) at converting the date....
sql= """select C2_MT_PROJECTID "Project",'Plan1' "Data Load Cube Name",CONVERT(C1_MT_PROJ_START_DT,Date('MM-DD-YYYY')) "StartDate",'OrganizationNone' + ',' + 'Project Type None' + ',' + 'BegBalance' + ',' + 'FY11' + ',' + 'RateNone' + ',' + 'Working' + ',' + 'Final' "Point-of-View" from "C$_0Project" where      (1=1) """
Here is the error from the operator get...
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 20, in ?
java.sql.SQLException: Unexpected token in statement [select   C2_MT_PROJECTID    "Project",'Plan1'    "Data Load Cube Name",CONVERT(C1_MT_PROJ_START_DT,Date(]
     at org.hsqldb.jdbc.jdbcUtil.sqlException(jdbcUtil.java:67)
     at org.hsqldb.jdbc.jdbcStatement.fetchResult(jdbcStatement.java:1598)
     at org.hsqldb.jdbc.jdbcStatement.executeQuery(jdbcStatement.java:194)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
     at org.python.core.PyMethod.__call__(PyMethod.java)
     at org.python.core.PyObject.__call__(PyObject.java)
     at org.python.core.PyInstance.invoke(PyInstance.java)
     at org.python.pycode._pyx14.f$0(<string>:20)
     at org.python.pycode._pyx14.call_function(<string>)
     at org.python.core.PyTableCode.call(PyTableCode.java)
     at org.python.core.PyCode.call(PyCode.java)
     at org.python.core.Py.runCode(Py.java)
     at org.python.core.Py.exec(Py.java)
     at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
java.sql.SQLException: java.sql.SQLException: Unexpected token in statement [select   C2_MT_PROJECTID    "Project",'Plan1'    "Data Load Cube Name",CONVERT(C1_MT_PROJ_START_DT,Date(]
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)

Help with BD79 - IDOC conversion rules

Similar Messages

Maybe you are looking for