How to implement a conversion rule in KC7R (External Data transfer-Tool)

Hi,
I am familiar with programming conversion rules in ABAP in the LSMW and IS-U Migration workbench.
Unfortunately we have to work with EDT (transaction KCLJ).
I need to implement a simple conversion rule: migration file has the external BP number BPEXT and I must retrieve the internalone (PARTNER) for the migration program.
So I must implement a short ABAP code (select single * from BUT000 ...).
Now I see that in KC7R you can use constants and conversion rules. There are also "General Ruels" and "conversion routines".
Can someone explain how to implement this simple ABAP conversion rule in KC7R giving a short example?
This would be great.
EDT is the workst of all SAP Standard Migration Tools I have seen.....
Kind regards,
Thomas

Thomas,
Coud you please share your findings as I am now in a similar to your original post.
ie I too would like to know how to code convesions for use within the transfer rules used by KCLJ.
Kind Regards,
Hiten Mistry.

Similar Messages

How to implement simple CEV rules?

Hi,
I have some doubts how to implement very simple CEV rules (ex: When enddate is filled then determinationdate is sysdate)
When i follow the CDM Guidelines then I have to create a custom routine and make a derivation expression for the column.
When i use commom sense I do a update in the BR implementation. Saves a lot of work.
What is the opinion of the Headstart team?
Regards, Jan-Derk

Hi Kathyaini,
For using a XML connection as data source then you have to follow the below:
Configure the following elements as described below:
u2022 <JavaDir>
u2022 <Classpath>
u2022 <JDBCURL>
u2022 <JDBCUserName>
u2022 <JDBCClassName>
It will prompt you for the class name and path of the URL using, that also depends upon the data base you use.
It is different for each database like oracle, sql and DB2.
For configuring the connection you should follow the process for each database.
JDBCURL - The JDBCURL parameter value is the default JDBC connection URL that will be displayed in Crystal Reports when you create a new JDBC data connection. The exact format of the connection URL is specific to the database driver and is provided by the database driver vendor.
For example, the connection URL for the Oracle JDBC driver is:
jdbc:oracle:thin:@<hostname>:<port>:<sid>
Sample for SQL Server:
jdbc:microsoft:sqlserver://SERVERNAME:1433
Sample for DB2:
jdbc:db2:XTREME
JDBCUserName - Default username for the Database
JDBCDriverName - The JDBCDriverName is the default full classname of the JDBC driver that will be displayed in Crystal Reports when creating a new JDBC data connection..
Oracle: oracle.jdbc.driver.OracleDriver
Let me know if any.
Regards,
Naveen.

How to Implement Dynamic Modification Rule for Material & multiple vendor Combination

Hi Team,
In dynamic modification rule for Material & vendor combination, i have maintained material & vendor in Inspection plan at Material Assignments
1.If i purchase same material from different vendors then how to implement ?

Hi Balaji,
I am not sure if i have followed your requirement.
What do you want to do with Vendor Z? Do you want to inspect each lot from Z?
If yes:
Then Create 2 Inspection plans with same Operations and Same MICs, In Material Assignment, mention Vendor as Z so that 1st inspection plan will only be for Vendor Z. Do not enter DMR in Header.
In 2nd inspection plan Enter DMR and do not mention any vendor so this plan will be applicable for all vendors except Z.
If No:
Then create Qm info record for vendor Z with "No inspection" set in QI06.
Amol.

How to install Data Transfer Tool (DTT) on ECC 6.0

Hello SAP Guru's,
I am trying to get DTT installed on ECC 6.0 system. It used to be part of Best Practices for HCM in ECC 5.0 system. However the Best practices for HCM in ECC 6.0 does not have DTT included in it. Is there any way, I can get just the DTT part of it on ECC 6.0?
Any help you can privide, is greatly appreciated.
Warm Regards,
Balkrishna Kute

Balkrishna,
I've got the same issue as you.
Did you get an answer to this elsewhere or is your issue still unresolved since September last year?

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

How to add conversion rule in SCOT email attachment.

Hello All,
How to add conversion rule in SCOT email attachment.
I try to csv conversion rule in scot through spro. I add this rule through SPRO successfully but this rule not added in SCOT internet tab.

Hi,
Please find below link. May be these are helpful to you.
http://scn.sap.com/thread/717106
http://help.sap.com/saphelp_nw70/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/4d3d3d9ba00645e10000000a114084/content.htm
Regards,
Saket S. Ghanekar

How to implement business rules by using drolls in OSB

Hi
I am new to Drools,can any body tell how to implement drools concept in OSB11,provide any useful links or blogs.
Thanks in Advance
Mani

Mani,
I have implemented Drools by exposing them over web service call through Business Service of OSB.
As you are using Java Callout, try to set proper return type for the java method called, better to use XMLObjects as the return type.
http://www.xenta.nl/blog/2011/08/29/oracle-service-bus-java-callouts-with-xmlobjects/
http://mazanatti.info/index.php?/archives/63-Oracle-Service-Bus-generating-XML-Objects-from-Java-Callouts.html
http://blog.xebia.com/2009/10/11/java-callout-on-the-alsb/
http://itnewscast.com/middleware/oracle-service-bus-java-callouts-xmlobjects
How to retrieve the java object in a proxy service in osb -- Plz help
Hope it helps !!
Abhinav
Edited by: Abhinav on Dec 12, 2012 4:21 PM

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

IDOC inbound conversion Rules

Hi to all,
I'm Implementing an Inbound Interface for Cost Centers using idoc message COSMAS and IDOC type COSMAS01.
I want to modify IDOC data changing the cost center code by another one stored locally in a param table (Z*).
I think the best way to do this is by creating a conversion rule in BD72 than maintain and assign to Message type. The problem is that i have to select data from the Z* Table i need two parameters from the IDOC(LogicalSystem and cost center). How can I create a custom conversion routine or something to get this data from the Z table into the IDOC field (KOSTL).
The conversion exits only have one import parameter and one export parameter.
Do anyone had one problem like this?
Thanks in advance to all.

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

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

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

GRC 10: How to upload Org Level Rules in GRC 10?

Hello Friends,
we have implemented GRC 10 recently but missed to move org level rules from GRC 5.3 to 10. I don't see an option to load org rules in SPRO. Can you please let me know how can i load org rules from 5.3 to 10 with out disturbing the existing risks / functions? or is there an option to update tables directly for org rules?

Hi Colleen Lee,
Thank you for your response. Yes i see Master Data > Exception Access Rules > Organizational Rules and i am able to create org rules but i am trying to find an option to upload all at a time as we have around 50 org rules and have 2600 lines in it. creating manually will take so long and looking for alternate.
Thanks & Regards
Pradeepthi

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

How to implement a conversion rule in KC7R (External Data transfer-Tool)

Similar Messages

Maybe you are looking for