Conversion Rule in ALE/IDOC Scenario (R/3 To R/3)

By Jitendra Nath Sethi, HCL AXON

Scenario: R/3 To R/3 ALE Communication ->when multiple systems involved in sending the
messages to each other for their business transactions through IDOC.

If both the systems have different configurations then we need to convert the entity like Unit of
measure/Text id/delivery block etc. For example the system ‘A’ has the Unit of measure (BT –Bottle)
but in the system ‘B’ it is (BO-Bottle). So while sending an IDOC (Outbound) we need to convert the
field value from BT to BO.

Solution: This can be achieving through User Exit or conversion Rule.

Conversion Rule: This is the standard functionality provided by the SAP & it is easy to deal with the
conversion of the field value in the segment of the IDOC.

There are three steps to achieve these conversions.

Step 1 -> Maintain Conversion Rules

a) Go to transaction code BD62

b) Click on the change button

c) Enter the name of conversion rule, description and IDOC segment name.

Steps 2 -> Create Conversion Rule

a) Go to Transaction code BD55

b) Click on the New Entries

c) Enter type/Sender/Receiver/Conversion Rule etc.

d) Save
 Steps 3 ->ALE/IDOC Segment

a) Go to Transaction code BD79

b) Enter the conversion rule which we have created in the transaction code BD62

c) Click on the change mode

d) Copy & paste the receiver field to the sender field.

e) Double click on the field whose value need to be converted in this case it is : MENEE & PMENE
f) Select Convert Sender field & Copy Sender field radio button as shown in the screenshots.
g) Click on the conditions button & input the value in the table as shown in the below screen shots.
Click here to continue...

Segment Filtering:

 Transaction code for Segment filtering is BD56

 Segment filtering concept is used to filter out the unwanted segments from IDOC.
 When a Master IDOC is created, it consults the segment filters and removes any
unwanted segments to create the communication IDOC for a receiver.
 Segment Filtering is done at run time.
Note: You cannot filter out mandatory segments. IF you want to filter a parent segment, you
must ensure that all of its child segments are also filtered.

Reduced IDOC type:

 Transaction code to reduce the IDOC type is BD53

 Create the new reduced message type, internally linked with the IDOC type.
 The system Copies the latest version of the IDOC associated with the message type.
 By default only the mandatory fields are activated. So you must activate the
remaining segments and internally fields also.
  Save your changes and activate the Reduced message type.

Steps After activation:

o Change the partner profile to use new message type. You have to add a new
entry in the partner profile with the message type created for the reduced
IDOC.
o Distribution model is also needs to be modified to use the message type
assigned to the reduced IDOC type.
o

In SE03 transaction - select Search for objects in request and execute.

give R3TR SSFO and Your smartform name and select both modifiable and
released at bottom and execute.

You will get all requests available for the smartform.

Using SE03, it will list all the requests generated for the smart form. To view the changes done at
Smartform level, proceed as follows:

Go to tcode:Smartforms.

Specify an existing form name, for e.g., zsmartform , execute the smartform(F8).

Now the generated function module for the smartform is displayed as follows:

Press ‘display’ button, then the following screen appears:

Double click on the program name, then the screen appears as follows:

Here copy the include name from ‘user-defined’ files as follows:

Do the same above process from other server also which need to be compared.

Now go to tcode: SE39, the following screen appears:

Click here to continue...

Here click on ‘Compare different systems’ button.

Now specify different server names under ‘system’ along with include names which were copied from
above screens, then the screen appears as follows:
In the above screen ‘CON’&’QAS’ are different servers.

But include name is same in both the servers.

Now opt display button, then the following screen appears:

Here specify the logon details for to be compared server then the following screen appears:

Here click on ‘compare’ button, then the following screen appears:

Here in the above screen its showing that the code is not similar in two servers.so as to find the same,
click on the ‘next difference from cursor’ button which is next to ‘compare’ button. Then the screen
appears as follows:

In which its displaying the difference…likewise click on the same button until end is reached.

Note: Here the only drawback is the changes in text elements cannot be captured as they are called
from routine ‘%WRITE_TEXT’.
In SAP ABAP version Management is very useful to keep track of the changes that you make to your
program. Version Management helps in keeping a record of the changes that you make and in case
you want to revert back to the older version you can do so by activating the appropriate version.
Version management is a better way of trying out some change in the code and if this leads to
undesirable results then you can go back to the earlier version. In case you want to revert back to
the earlier version you need to re-activate it. Version management is also useful to an auditor to
review the complete history of a program. The system administrator can view the version
management to track changes in a specific time interval.

To create a version of a program please follow the path given below.

From the ABAP Editor

Utilities >>>>>>>>>>>>>>>> Version >>>>>>>>>>>>>>> Create Version

To activate the the previous version navigate to

Utilities >>>>>>>>>>>>>>>> Version >>>>>>>>>>>>>>> Version Management

Select the appropriate version and activate it.

 This document details the procedure in using Microsoft Word as editor in SAP Script / Smart
Forms.
In normal case, when you try opening the editor in Smart Forms, the following editor would
appear:

Click on the editor button. The following editor appears:

Now to change the above editor to MS Word, do the following:

Go to transaction I18N (Internationalization).
 Click on I18N Menu ->
I18N Customizing ->
I18N System Configuration (as shown in the screenshot below)

The following screen appears:

If you would like to use MS Word Editor in both Script and Smartforms, then check the both
checkboxes as shown below:

Click on Activate.
The following popup appears (related to SAPScript Editor):

Click on Yes. Now the following popup appears (related to Smartforms Editor):

Click on Yes to proceed.

Now the MS Word editor is available for both SAP Script and Smartforms.
Result: In the SmartForms:

In SAP Script:
 You can anytime revert to old editor by deactivation MS Word editor option using the
transaction I18N.

LINEAR SEARCH AND BINARY SEARCH :

shouldin case of linear search system will search from begining.

that means Example : z table contains single field with
values
1 2 3 4 5 6 7 8 9
if u r searching for a value then system will starts
from first position. if required value is founded then
execution will comes out from z table.
in case of binary search system will starts from mid
point.if value is not founded then it will search for
upper half.in that upper half it will check mid
point.like that searchwill takes place.

 Binary search requires the input data to be sorted; linear search doesn't
 Binary search requires an ordering comparison; linear search only requires equality
comparisons
 Binary search has complexity O(log n); linear search has complexity O(n) as
discussed earlier
 Binary search requires random access to the data; linear search only requires
sequential access (this can be very important - it means a linear search can stream
data of arbitrary size)
 FROM tab
