abap

[Former Member]

1.whar are the interface/conversion pgm in sap?

2what are the userexit /what is involed in writting them?what precautions are needd?

3.what is the diff workbench request/custominsgrequest?

[Former Member]

1.whar are the interface/conversion pgm in sap?

2what are the userexit /what is involed in writting them?what precautions are needd?

3.what is the diff workbench request/custominsgrequest?

[Former Member]

Hi,

-

---

Conversion takes place when converting the contents of a screen field from display format to SAP-internal format and vice versa and when outputting with the ABAP statement WRITE, depending on the data type of the field.

If standard conversion is not suitable, it can be overridden by specifying a conversion routine in the underlying domain.

A conversion routine is identified by its five-place name and is stored as a group of two function modules.

The function modules have a fixed naming convention.

The following function modules are assigned to conversion routine xxxxx:

CONVERSION_EXIT_xxxxx_INPUT

CONVERSION_EXIT_xxxxx_OUTPUT

The INPUT module performs the conversion from display format to internal format. The OUTPUT module performs

the conversion from internal format to display format.

If a screen field refers to a domain with a conversion routine, this conversion routine is executed automatically each time an entry is made in this screen field or when values are displayed with this screen field.

eg . refer to the vbak table.

Go to SE11 -> VBAK -> Display mode -> double click on the data element VBELN_VA

Double click on the domain VBELN

You can find the conversion routine in the Output characteristics.

-

---

1)User exits

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.

The naming standard of function modules for functionmodule exits is:

EXIT_<program name><3 digit suffix>

The call to a functionmodule exit is implemented as:

CALL CUSTOMER.-FUNCTION ❤️ digit suffix>

Example:

The program for transaction VA01 Create salesorder is SAPMV45A

If you search for CALL CUSTOMER-FUNCTION i program

SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'

exporting

xvbak = vbak

xvbuk = vbuk

xkomk = tkomk

importing

lvf_subrc = lvf_subrc

tables

xvbfa = xvbfa

xvbap = xvbap

xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

2. How to find user exits?

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD.

Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

3. Using Project management of SAP Enhancements, we want to create a project to enahance trasnaction VA01 .

- Go to transaction CMOD

- Create a project called ZVA01

- Choose the Enhancement assign radio button and press the Change button

In the first column enter V45A0002 Predefine sold-to party in sales document.

Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed

Press Save

Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

Now the function module is displayed. Double click on include ZXVVAU04 in the function module

Insert the following code into the include: E_KUNNR = '2155'.

Activate the include program. Go back to CMOD and activate the project.

Goto transaction VA01 and craete a salesorder.

Note that Sold-to-party now automatically is "2155".

-

---

request:

you can create 2 type s of requests

Workbench Request & - Used for Objects like programs ,domains etc

Customizing Request - used for data

But you can also create Transport of Copies to transfer data.

Change Requests

Change requests are managed by the Transport Organizer. Changes to Repository and Customizing objects are recorded in change requests.

So that you can differentiate between global changes to the system and client-specific Customizing settings, the CTS records your changes in either a Workbench request or a Customizing request:

Workbench Requests

When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.

Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.

Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.

Customizing requests

Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).

Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.

Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.

See also:

Configuring Transport Routes

Request Types and Task Types

http://help.sap.com/saphelp_erp2005vp/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm

**********please reward points if the infromation is helpful to you***********

[Former Member]

hi,

1.whar are the interface/conversion pgm in sap?

Conversion, converting legacy system data into SAP data. Meaning that it is mainly a one shot deal, for example bringing your customer master to SAP from the legacy system, converting the fields used in legacy to the fields and values used in SAP.

Interface, a program or group of programs that handle the passing of data from one system to another. These programs work together to export the data from one system and import into a target system, maybe these programs run once a day, maybe twice, may every hour throughout the day. It is a good way to keep the data in two or more systems in sync with each other.

A conversion means data that is converted from one format to another format and from one system to another. So when you first implement SAP, you are actually replacing some of your legacy systems, but you are not completely trashing the data. You still need some of that data from the systems that are being replaced. So you pull the data out of your legacy systems and put them on some files. You then want to load that data into your new SAP system. That is when you write some programs which will read that data and load it into SAP. Imagine you had a home grown purchasing system. You are now replacing all that with SAP. But until SAP goes live, you want to keep using your home grown purchasing system. So during go live, you want to transfer the POs from your legacy system to SAP. Now a PO in your legacy system may not have the same fields as a PO in SAP. So you convert the data.

Interfacing is connecting two or more different entities. In our case, it is connecting one or more systems with SAP. Now extending our previous example, you are replacing some legacy applications but there are some applications that you don't want to replace yet. You need to somehow pass data back and forth between SAP and these remaining systems. Data may be going one way or the other way or both ways. You will still need to do some data transformations/translations etc to make the data understandable to the receiving system. This will continue as long as you want to keep the systems running alongside SAP.

In short, conversions are written to load data into SAP onetime. These are typically file based.

Interfaces are written to exchange/update/send/receive data between SAP and other systems on an ongoing basis. These can be in many forms, file based, idoc based, real time(business connector, XI etc are useful in this), xml, and the list goes on.

Interface and Conversion program with BDC are same.

Only the difference in the mode of execution.

Conversions Program - mainly used for master data

migration. Mostly will be executed standalone and

once .

Interface Programs - These program will be executed

periodically for Transaction data upload(may be

for some periodic report). So these programs are

scheduled.

Conversions - One time upload of data

Interfaces - Communication between two systems to transfer the data. It can be in a scheduled way also. Example SAP to external system and External system to SAP.

2what are the userexit /what is involed in writting them?what precautions are needd?

User-Exits

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sap-img.com/ab038.htm

http://www.planetsap.com/userexit_main_page.htm

http://www.sap-basis-abap.com/sapab013.htm

http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283

These links will help you to learn more on user exits.

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

http://www.planetsap.com/userexit_main_page.htm

http://www.allsaplinks.com/user_exit.html

www.sap-img.com/abap/what-is-user-exits.htm

Also please check these threads for more details about user exits.

1. Document on UserExits in FI/CO

http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc

2. Finding User Exits...

http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits

3. List of all User Exits...

http://www.planetsap.com/userexit_main_page.htm

3.what is the diff workbench request/custominsgrequest?

Workbench Requests :

Workbench Request is used for Objects like programs ,domains etc

When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.

Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.

Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.

Customizing requests:

Customizing Request is used for data

Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).

Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.

Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.

[uwe_schieferstein]

Hello Reddy

I like to add a few comments on conversion exits.

Conversion exits are automatically active when we are working with the SAPGUI. For example, lets us assume we have a material with MATNR = '123'. Actually, this material is stored as MATNR = '000000000000000123' (18-digits, 15 leading zeros).

When you call function module BAPI_MATERIAL_GET_DETAIL via SAPGUI (transaction SE37) and enter MATERIAL = '123' then the system converts this value within the function module automatically to MATERIAL = '000000000000000123' and the material details will be found on the DB and displayed.

However, if you have a flat file in which the material number is given as '123' and upload this file into an ABAP program the conversion exit is not "triggered". Thus, if you call the same BAPI as abovie within your program with MATERIAL = '123' then you will get the following error message:

<i>"The material 23 does not exist or is not activated".</i>

Conclusion: Within your sample program (e.g. a data migration report) you have to call all required conversion exits yourself. In case of MATNR this is <b>CONVERSION_EXIT_MATN1_INPUT</b> (MARA-MATNR -> data element MATNR -> domain MATNR -> conversion routine MATN1).

Regards

Uwe