By: se80.co.uk

All IDoc data records are exchanged in a fixed format, regardless of the segment type. The segment’s true structure is stored in R/3’s repository as a DDic structure of the same name. The segment info tells the IDoc processor how the current segment data is structured and should be interpreted. The information, which is usually the only interest, is the name of the segment EDID4-SEGNAM.
The segment name corresponds to a data dictionary structure with the same name, which has been created automatically when defining the IDoc segment definition with transaction WE31 .
For most applications, the remaining information in the segment info can be ignored as being redundant. Some older, non-SAP-compliant partners may require it. E.g. the IDoc segment info will also store the unique segment number for systems, which require numeric segment identification.
To have the segment made up for processing in an ABAP, it is usually wise to move the segment data into a structure, which matches the segment definition. For a segment of type e1maram the following coding is commonly used:
TABLES: e1maram.

. . .

MOVE edidd-sdata TO e1maram.
Then you can access the fields of the IDoc segment EDIDD-SDATA as fields of the structure e1maram .
WRITE: e1maram-matnr.
The following coding sample, shows how you may read a MATMAS IDoc and extract the data for the MARA and MARC segments to some internal variables and tables.
DATA: xmara LIKE e1maram.

DATA: tmarc AS STANDARD TABLE OF e1marcm

WITH HEADER LINE.

LOOP AT edidd.

CASE edidd-segnam.

WHEN ‘E1MARAM’.

MOVE edidd-sdata TO xmara.

WHEN ‘E1MARCM’.

MOVE edidd-sdata TO tmarc.

APPEND tmarc.

ENDCASE.

ENDLOOP.

now do something with xmara and tmarc.

By :  Amit Khari

Overview

R/3 provides three “customization spots” that allow you to enhance FI/CO features without modifying the standard code. Although often collectively referred to as “user exits,” two of the three have different names. SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. Enhancements were new in release 3.0. The Open FI Interfaces or Business Transaction Events are also used to expand the standard functionality within SAP. These events are defined in the IMG. Business Transaction Events were new in release 4.0. They are not available for all modules and are not called on all integrated transactions into FI as of release 4.5B. This will change with each release and should be retested. The older User Exits in FI/CO are “Z” programs that are defined in table T80D for client-dependent user exits, and in table T80I for client-independent user exits. These are also used to expand the standard functionality within the FI/CO modules. These User Exits have been available since the early releases of SAP. All of these FI/CO User Exits are listed in this document in the Configuring User Exits (Older). The list is included because these User Exits are not a part of the Enhancements or Business Transaction Events and do not have an Info System for searching.

Benefits

-         Standard SAP functionality can be enhanced without modification to the standard code.

-         Upgrades do not erase the functionality and it does not have to be re-transported or re-entered into the system. The enhancements should be thoroughly tested when upgrading to ensure the system will still work as implemented.

Configuring SAP Enhancements

Basic Steps in Configuring an Enhancement

-         Find the appropriate Enhancement.

-         Enter the ABAP code in the “Z” program within the function module.

-         Create a project.

-         Add the Enhancement to the project.

-         Activate the project.

Example Business Scenario for Enhancements

Company A has a requirement to validate all customer master records created with a U.S. address. The U.S. entity reports on the industry field on the customer master. This is only a U.S. requirement and should not be required for the other countries, so the field status would not work. To accomplish this requirement, Company A will need to set up an Enhancement for the customer master transaction. The necessary steps are detailed below with screenprints. This example was configured in a 4.6C system.

Detailed Steps

1.   Tools ABAP Workbench Utilities Enhancements Definition Utilities List Enhancements

2.    Do not execute this without any parameters! There are too many Enhancements and it will probably time out. You’re searching for a customer master exit. Enter *mast* in the short text. You’ll start there. Searching for an exit can be tricky, so make sure you try several things before giving up.

3.    Execute the search.

4.    Look through the list until you find the Enhancement for User exits: Customer Master Data.

5.    Double-click on the enhancement SAPMF02D. This will take you to the details of the Enhancement and list the function modules included in the Enhancement.

6.    To continue, double-click on the function module EXIT_SAPMF02D_001

7.    This will take you to the source code for the function module. Click on the Import tab to review the tables/fields that are available for the Enhancement

8.      To view the tables/fields that can be changed in the function module, click on the Export and Changing tabs. For this function module, these tabs are empty because you can only validate data. You cannot change any fields in this enhancement.

9.      Return to the Source Code tab.

10.  Scroll down until you see the Include statement in the program. The “Z” program listed after the Include is where your code will be written

11.   Double-click on the Include. You will be prompted to create the include. Click on Yes to create.

12.   At this point you will be prompted to enter a development class and to create a transport request. If you do not know which development class to use, please contact your technical team.

13.  Enter the following ABAP code into the program

*

* User exit to ensure that all US customers have a group key

* entered on the customer master.

*

if i_kna1-land1 = ‘US’ and

i_kna1-brsch = ‘ ‘.

message e001(F2).

endif.

14.   Note that the table name matches the table name in the import tab tables.

15.   In this example you are using the standard message class F2 with message number 001. Normally, you will create your own message within your own message class. All customer message classes must begin with a “Z” and are created in transaction SE91.

16.  Save the program.

17.  The next step is to create the project. Go to transaction code CMOD or follow menu path: Tools  ABAP Workbench  Utilities  Enhancements  Project Management.

18.  Enter the project name; begin the name with a “Z.”

19.  Click on the Create button.

20.   Enter in a description for the project.

21.   Click on the Enhancement Assignments button.

22.   You will be prompted to save the enhancement. Click on Yes.

23.   At this point you will be asked for a development class and to create a transport for the project. You may use the same one created when adding the ABAP code to the function module.

24.  Enter the name of the enhancement SAPMF02D

25.  Save the project.

26.  Back out of the enhancement assignment.

27.  Activate the project by hitting the Activate button.

The SAP Enhancement is ready to be tested! Try creating a customer with U.S. as the country and a blank group key. Be sure to test one with a group key to make sure the message is not displayed in error as well.

Configuring Business Transaction Events

Basic Steps in Configuring an Event

-         Make sure the application is active for Business Transaction Events.

-         Copy the sample interface function module into a “Z” function module.

-         Enter the ABAP code into the source code section of the new “Z” function module. You may choose to create a “Z” program to enter the code into and then insert the “Z” program into your function module source code.

-         Activate the function module.

-         Assign the function module to the event, country and application.

Example Business Scenario for Business Transaction Events

Company A would like to copy the group key field from the vendor master into the allocation field on all the line items within a vendor invoice and payments, including the vendor lines. This requirement assumes only one vendor is posted to in a document. To accomplish this requirement, Company A will use the Business Transaction Event 1130, Post Document: SAP Internal Field Substitution. 1.      IMG Menu Path: Financial Accounting  Financial Accounting Global Settings  Use Business Transaction Events  Environment  Infosystem (Processes).

2.      Find the correct Business Event. You are updating a field, so you select the Processes Info System instead of the Publish and Subscribe Info System.

3.      Execute the search with the defaults.

4.      Find the correct interface for updating a document: Post Document: SAP- Internal Field Substitution

5.      Put your cursor on the event and click on the Sample Function Module button.

6.      You are now in transaction SE37 – Function Builder. This is the function module (sample_process_00001130) you will need to copy into a “Z” name function module for your coding. This Is the Function Module You Need to Copy Your “Z” Name Function Module

7.      Click on the Copy button.

8.      Enter the “Z” function module name in the To Function Module field

9.      Enter a Function Group. If you need to create a “Z” function group, go to transaction code SE37 and follow menu path: Go to  Function Groups  Create Group. A function group is a logical grouping of function modules, and the ABAP code is generated for function groups. You will be prompted for a development class and transport when creating the function group.

10.  In Function Builder (transaction SE37), enter the new “Z” function module. Click on the Change button.

11.  The system will default into the source code screen where you may enter your ABAP code.

12.  Notice the tables available for the code. Additional tables may be declared if necessary.

13.  Enter the following source code

tables: lfa1.

data: z_groupkey like lfa1-konzs.

z_groupkey = ‘ ‘.

loop at t_bseg.

* check for vendor lines. If one is found, read the vendor master and

* retrieve the group key field.

if t_bseg-koart eq ‘K’.

select single konzs from lfa1 into z_groupkey

   where lifnr = t_bseg-lifnr.

endif.

* Move the group key field into all line items allocation field.

loop at t_bsegsub.

t_bsegsub-zuonr = z_groupkey.

modify t_bsegsub index sy-tabix.

endloop. “t_bsegsub

endloop. “t_bseg

14.  Save the function module.

15.  Back out to the main Function Builder screen by clicking on the green arrow button.

16.  Activate the function module by clicking on the Activate button

17.  Assign the function module to the event in the IMG: Financial Accounting Financial Accounting Global Settings Business Transaction Events Settings Process Function Modules of an SAP Appl.

18.  Hit enter past the warning messages that this is SAP data.

19.  Click on the New Entries button.

20.  Enter the process for your interface. In your example it is 00001130.

21.  Enter the country the interface is valid for. If it is valid for all countries, leave this field blank.

22.  Enter the application the interface should be called for. If it should be called for all applications, leave this field blank. Please note that not all integrated transactions are programmed to go through these interfaces! You will need to test to find out!

23.  Enter the new “Z” function module

24.  Save the settings. At this point you will be prompted for a CTS number for the configuration change.

25.  The Business Transaction Event is complete! You are ready for testing.

Configuring User Exits (Older)

Basic Steps in Configuring an User Exit

-       Create a “Z” program for the User Exits and enter the necessary ABAP code.

-       Enter the new program name into table T80D.

-       Configure the application to call the User Exit.

List of User Exits

-       Variable Field Movements

-       Substitutions in FI,CO, PCA

-       Validations in FI,CO, PCA

-       Rollups in SPL

-       Fixed Field Movements in SPL

-       CostCenter Summarization on Detail Screen

-       Sets Formula Variables

Example Business Scenario for User Exits

Company A would like to add a “Z” field in the Special Purpose Ledger to capture a Business Unit field for reporting. They have used all the standard SAP fields such as Business Area and ProfitCenter. The field will only be used for reporting and is only needed in the Special Purpose Ledger. You created a special ledger table (ZZSPL1) with field Z_BUNIT and need to populate this field based on a combination of G/L account, fund and functional area.  To accomplish this requirement, Company A will use the Variable Field Movement User Exit. To make maintenance easier, table ZZBUSUNIT was created with the G/L account, fund and functional area fields as key fields, and the business unit field as a non-key field. You generated the table maintenance so the table could be updated using transaction SM30. SAP users update the business unit determination rules in table ZZBUSUNIT by entering the G/L account, fund and functional area, and then the business unit that combination should be posting to. The User Exit will read table ZZBUSUNIT using the G/L account, fund and functional area from the posting transaction and determine the business unit. The steps for using the user exit are detailed below. This example was created on a 4.6C system. 1.      Copy the delivered template User Exit program RGIVU000_TEMPLATE into a “Z” program. Follow menu path Tools  ABAP Workbench  Development  ABAP Editor (transaction code SE38). In early releases, the delivered program was RGIVU000.

2.      You will be prompted for a development class and a transport. Please check with the technical team for the correct development class.

3.      At the initial ABAP Editor screen, enter your new “Z” program name, select the Source Code button and click on Change

4.      Enter the following code in the User Exit :

FORM E01_MVC USING FROM_FIELD TO_FIELD.to_field = 'CORP'. "Set a default

business unit.* read table zzbusunit to determine the business unit field.

select single z_bunit from zzbusunit into to_field

where hkont = accit_glx-hkont and    geber = accit_glx-geber and

fkber = accit_glx-fkber.ENDFORM.

5.      Activate the program by clicking on the Activate button.

6.      Change the configuration in the User Exit table to point to your new “Z” program.

7.      Follow the IMG menu path: Financial Accounting  Special Purpose Ledger  Basic Settings  User Exits  Maintain Client Specific User Exits.

8.      The entry to maintain is application area GIMV: Variable Field Movement. Enter your “Z” program

9.      Save the changes.

10.  The final configuration step is to assign the User Exit in the variable field movement for your special ledger table. In the IMG: Financial Accounting à Special Purpose Ledger à Basic Settings à Master Data à Maintain Field Movements. Field movements control how the fields in a special ledger table are populated. They can be populated straight from other fields in a posting or through User Exits. After You Assign the Business Unit Field and the G/L Account, the Exit Field Should Contain U01.

11.  Assign the business unit field as a receiver and the G/L account as the sender. The Exit field should contain U01

12.  The User Exit number U01 calls User Exit E01_MVC form in the “Z” program.

13.  Save the field movement.

14.  You are ready to test your User Exit!

By: Suresh Upadhyayula

1. User exits can be found out using a development class or a package.

2. For which transaction you would like know whether user exit is available or not. example 1. Whenever I create a purchase order my vendor is same for a particular purchasing group and a particular purchasing organization .

Procedure to find out the user exit :
3.For which transaction you would like to see the user exits, frrst goto transaction and click system status and find out the technical name i.e is package.

4. By going to the SMOD transaction give package name and find out the real user exits available or not.  Once it is available go to edit attributes and write program by givng the filed name = ’9999′ (some vendor) and save , click, save, activte.
5. Go top CMOD  transaction and give that user exit in the filed area and activate .

6. Go and observe in me21 and see that 9999 vendor by default will come when ever you will create po.

To Develop Enhancements for Purchasing  In this step, you develop enhancements for Purchasing.

1. Either create a new project or use an existing one and then enter the enhancement.

2. Activate the project – Your enhancement will only become effective after activation.

In contrast to modifications, enhancements are basically release-insensitive since they are not implemented in the SAP original but in a name range that is reserved for the customer.  If you want to display the documentation for an enhancement, choose Goto -> Documentation in the enhancement transaction.

The following SAP enhancements are available for the Purchasing area:

AMPL0001 – User subscreen for additional AMPL data (manufacturer part number)

LMELA002 – Adoption of batch number from shipping notification at time of posting of a goods receipt

LMELA010 – Incoming shipping notification: adoption of item data from IDoc

LMEQR001 – User exit for source determination

M06B0001 – Role determination for release of requisitions

M06B0001 – Changes to communication structure for release of requisitions

M06B0003 – Number range and document number

M06B0004 – Number range and document number

M06B0005 – Changes to communication structure for overall release of purchase requisitions

M06E0004 – Changes to communication structure for release of purchasing document

M06E0005 – Role determination for release of purchasing documents

ME590001 – Grouping of requisitions for PO split in transaction ME59

MEETA001 – Determination of schedule line type (backlog, immediate requirement, forecast)

MEFLD004 – Determination of earliest delivery date for checking at time of goods receipt (PO only)
MELAB001 – Generation of forecast delivery schedule: realization via creation profile
MEQUERY1 – Enhancement for document overview ME21N / ME51N

MEVME001 – Calculation of default GR quantity and over/underdelivery tolerances
MM06E001 – User exits for inbound EDI messages and outbound purchasing documents

MM06E003 – Number range and document number

MM06E004 – Control of import data screens in purchase orders

MM06E005 – Customer fields in purchasing documents

MEREQ001 – Customer’s own data in purchase requisitions

MM06E007 – Change document for requisitions when converting into POs

MM06E008 – Monitoring of contract target value in case of release orders

MM06E009 – Relevant texts for “Texts exist” indicator

MM06E010 – Field selection for vendor address

MM06E011 – Activation of requisition block

MM06L001 – Exits for determination of ratings in vendor evaluation

MMAL0001 – ALE source list distribution: outbound processing

MMAL0002 – ALE source list distribution: inbound processing
MMAL0003 – ALE purchasing info record distribution: outbound processing

MMAL0004 – ALE purchasing info record distribution: inbound processing
MMDA0001 – Default values for delivery addresses
MMFAB001 – User exit for generation of releases

MRFLB001 – Control items during release creation

LWBON001 – Enhancement of LIS update through extension of the communication structure

MCKONA (business volumes and rebate income)

LWBON003 – Change settlement data for end-of-period rebate settlement before creation of settlement documents

LWSUS001 – Customer-specific source determination in Retail

LMEXF001 – Conditions in purchasing documents without invoice receipt

LMEKO002 – Enhance communication structure KOMP for price determination   

By: erpgreat             

SAP user exit can be found in number of ways:

1) To find user exit in SD module , goto object navigator(SE80) and select

development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press

enter and you will find all the includes which contain userexits in SD for

different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it

and start coding .

Some examples of userexits in SD(SALES & DISTRIBUTION ) are:

1)ADDING OF NEW FIELDS IN PRICING

In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.

The fields which are not in either of the two tables KOMK and KOMP

cannot be used in pricing .Sometimes a need arises when the pricing

is to be based on some other criteria which is not present in the form of fields in either of the two tables.

This problem can be solved by using USEREXITS which are provided for pricing in SD.

Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is

USEREXIT_PRICING_PREPARE_TKOMP or

USEREXIT_PRICING_PREPARE_TKOMK

Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.

In the case of userexit which will be called when invoicing is done ,these

are provided in the include RY60AFZZ which is in the standard SAP

program SAPMV45A. The name of the userexits are same. i.e

USEREXIT_PRICING_PREPARE_TKOMP or

USEREXIT_PRICING_PREPARE_TKOMK

These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely

created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that

has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.

Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose

includes are provided in each of them .

To create the field in header data(KOMK) the include provided is KOMKAZ

and to create the field in item data(KOMP) the include provided is KOMPAZ.

One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.

2)The other method of finding userexit is to find the word USEREXIT in the

associated program of the transaction for which we want to determine userexit using SE38.

3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.

Some other examples of userexits in SD are:

USEREXIT_NUMBER_RANGE

This userexit is used to assign a different internal document number to the

sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .

USEREXIT_SAVE_DOCUMENT_PREPARE

This userexit is used to insert the ABAP code which will be called when

the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.

Exits & Enhancements

There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.

These are different from USEREXIT in the way that they are implemented

in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .

These start from the word EXIT_ followed by the program name and then followed by a three digit number.

e.g. EXIT_SAPMV45A_002

This exit is found in SD in enhancement V45A0002.

TYPES OF EXITS

1)MENU EXITS

2)FUNCTION EXITS

3)TABLE EXITS

4)SCREEN EXITS

5)KEYWORD EXITS

6)FIELD EXITS

We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD

selecting the enhancement e.g. V45A0002 and selecting the component

(one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.

An exit can be coded only once.

FUNCTION EXITS

These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any tupe of exit including function exits.

The function exits are called from the standard SAP program in the form

of ABAP statement

CALL CUSTOMER-FUNCTION ‘NNN’

This is in contrast to USEREXITs where PERFORM statement is used to call

the required userexit.

To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its compnents the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.

e.g.

ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation

To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located

in enhancement no V45A0002 . Before we can choose the exit we have to

create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the

exit EXIT_SAPMV45A_002 . This exit is used for our purpose.

Double clicking on this exit will takes us to function builder (SE37) . This

function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR

of type KNA1-KUNNR i.e if we move the desired customer name to this

structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order.

This function also contains a customer include ZXVVA04 . This include

will be used to write our custom code .

Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.

e.g. E_KUNNR = 301.

Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined

customer .

FIELD EXITS

The field exits are managed,created,activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.

The format of field exit is :

FIELD_EXIT_dataelement_A-Z or 0-9

If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.

The function module associated with field exit shows two parameters

INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.

Before the field exit can have any effect the system profile parameter

ABAP/FIELDEXIT in all the application servers should be set to YES

ABAP/FIELDEXIT = YES.

As in sap.niraj.tripod.

A SAP User Exit is a user defined FORM routine that is used to calculate and/or replace values within a validation, substitution, or rule.

User exits have the following format:

• U (for a user-defined user exit) or S (for a standard user exit)

• The user exit number (three digits)

For example, U123 is a user-defined user exit.

You can configure the form pool name of the sap user exit and must store it in the table for client-dependent user exits (T80D) in Customizing. Table T80D contains the form pool names for the user exits used in validations, substitutions, and rules. Each validation/substitution form pool is client-dependent. (For more information, refer to the Maintain Client-Dependent User Exits activity in the Implementation Guide (IMG) for Special Purpose Ledger.)

Example form pools RGGBS000 and RGGBR000 for client 000 are delivered with the SAP R/3 System. You must copy these form pools and configure them in T80D. The new form pool name should conform to the customer naming convention (beginning with the letter Z ) so that is not overwritten when the next SAP upgrade is installed (for example, ZGGBR000).

Example FORM routine for substitution exit 001 (U001).

TABLES: COBL.

FORM U001.
COBL-KOSTL = COBL-BUKRS.

ENDFORM.

Tables and structures should not be declared in the FORM routines so that the contents can be used together with the calling transaction.

SAP exits are FORM routines that have been programmed by SAP. The name of the form pool for SAP exits is SAPFGBEB.

If you still store your rules in table T890 (interpreted rules), you cannot use user exits in your rule definition. It is highly recommended that you use report program RGUGBR10 to convert interpreted rules into generated rules so that you can use the Customizing function for maintaining rules. For more information, see Using the Rule Manager Reports .

The following table shows the types of user exits that can be used in validations, substitutions, and rules.

Validations and rules use exit numbers 1 and 3 from the above table.

Substitutions use all of the exit numbers from the above table.

For substitutions, you can also create user exits that accept a field as one parameter and then return the changed value in this parameter. This allows you to create a user exit that can be used independently of the field and table name. This type of user exit cannot be used as an entry in the Exit only field in the list of values to be substituted; you can only use this exit type in conjunction with a field name. An example of this user exit type is in form pool RGGBS000.

If you want to define a parameter for your user exit that is different from the result of a validation (B_RESULT), you must make an entry for your user exit in the FORM routine GET_EXIT_TITLES in the form pool you defined. It is recommended that you copy the SAP example form pool RGGBR000 for validation exits or RGGBS000 for substitution exits. These example

You can implement company-specific enhancements (user exits) that will provide additional functions. Customer-specific user exits may encompass such activities as:

• Specifying the conditions for dispatching      certificates (FORM routines as user exits)

• Defining additional data origins for inspection      specifications, results, and short texts for characteristics in the      certificate profile (self-defined function modules as table entries)

• Defining and evaluating additional limitations      for the selection of inspection lots and partial lots (SAP user exit with      menu function in the certificate profile and function modules)

• The automatic entry of the characteristic detail      data in the certificate profile (SAP user exit)

• Defining the layout (text elements from a      SAPscript® layout set, SAPscript® standard texts, SAPscript® layout sets)

• Defining the layout and the output data for      characteristics (special text elements in the SAPscript® layout set for      the characteristic output format, inspection method and supplementary      text, if the result is outside of the tolerance; SAPscript® standard      texts)

• Adding new objects to which certificate profiles      can be assigned (enhancement of a structure in the dictionary and an SAP      user exit with a function module)

• Using your own program to select the data and      print the certificates (as a table entry)

To obtain information about additional enhancement possibilities, you can create a list as follows:

1. Choose Tools ® ABAP Workbench.

The system displays the initial screen for the ABAP Workbench.

1. Choose Utilities ® Enhancement ® Definition.

The system displays the initial screen for SAP enhancements.

1. Choose the possible entries help for the Enhancement field.

The system displays the selection screen for locating SAP enhancements.

1. Enter QC in the Enhancement field.
2. Choose Execute.

As in SAP.COM

So how do you execute or test a function module in a system/client but wish to get around the authorization issue? Simply use SE38 with program RSFUNCTIONBUILDER.

TIP – You can sometimes use the same technique by using SE93 with the problem transaction and using the program name however do not expect to be able to bypass all authorizations.

By: SAPtricks

FI CO Master Data