Selection on User Exit Field in InfoPackage

Hi Experts,
Is it possible to have a selection in InfoPackage on a field which is being populated via user exit? If yes, how to achieve it?
Regards,
Yogesh

Hi.......
Yes u can do...........I will tell u what we r doing........
Look........we hav created one IP Steering Table.........say .....YIP_STEER
Now here we hav maintained all the Infopackage related information........like...
InfoSource
Logical InfoPackage variant (ID)
InfoObject
Key for multiple Selection Entries
Selection from
Selection to
Name of Function Module
Single-Character Flag
New Data type
Here ........the Following 4 r the Key fields......
InfoSource
Logical InfoPackage variant (ID)
InfoObject
Key for multiple Selection Entries
Now suppose ....we want that Sales Organization will be filled by some ABAP Code.........now to access the Sales Organization related data we create a Function Module...........
Now go INfopackage Scheduler >> Data Selection Tab >> Click on the Type field and select ABAP Routine (6).........Click on Details of Type(beside Type field ) >> Give a name of the Routine and Click on Editor...........there write down the code..........and access the Steering table...........and in turn that Function module..........
U can take help of some ABAP people.........
Hope this helps.......
Regards,
Debjani........

Similar Messages

User Exit/Field Exit for Field Selection in MM01 & MM02

Dear All,
Please Tell if I want to make Field Purchasing group Mandatory in MM01 & MM02 in Purchasing view only.I dont want the data to be updated in MRP1 view. Please tell me is there any exit for the same.
Regards,
Sandeep

You can customize
via
SPRO>Logistics - General>Material Master>Field Selection>
first from
Assign Fields to Field Selection Groups
you must assign MARC-EKGRP (Purchasing Group)
to a selection Group which will be mandatory.
Then from Maintain Field Selection for Data Screens
you must choose the Material Types which you want to make
Purchasing Group mandatory.
You must check Reqd Entry for the material types you want
Best Regards
Hope will help

User Exit, Field Exit

Hi Folks.
I have a question about user exit, or field exit. The question is that if is possible to fill a field with a value, depending on a value entered by the user within the same transaction.
Thanks for your help.
Regards,
Gilberto Li

The field Exit have only INPUT and OUTPUT, but u can validate using another values.
U can:
1- Use the values in that Screen ( Using function GET_DYNP_VALUE)
example:
DATA: l_vkorg TYPE STRING.
CALL FUNCTION 'GET_DYNP_VALUE'
EXPORTING
 I_FIELD = 'RMMG1-VKORG'
 I_REPID = 'SAPLMGD1'
 I_DYNNR = '1004'
CHANGING
 O_VALUE = l_vkorg.
2- Use Parametes ID:
example:
DATAL l_matnr TYPE MARA-Matnr.
GET PARAMETER ID 'MAT' FIELD l_matnr
3- Get Data from tables using SELECT with any of the values that u can get in options 1 or 2.
Example:
DATA:
 l_matnr TYPE MARA-matnr,
 l_mtart TYPE MARA-mtart.
IF INPUT is INITIAL.
GET PARAMETER ID 'MAT' FIELD l_matnr.
SELECT SINGLE MTART
 INTO l_mtart
 FROM MARA
 WHERE MATNR = l_matnr.
Now I have the value l_mtart to validate.
IF l_mtart = 'Z001'
ENDIF.
Greetings

A user exit field in CJ20n to display in CAT2.

Hi;
Let me define my problem. I have a field in CJ20n which is created by user exit in the activity level. The name of the field is "Effort to complete ".
I want to show the value of this field in the CAT2 transaction in the "TOTAL" field or in a better way in an additional field (column) in the upper pane.
Is it technically possible ?
Kind Regards.
Erkan.

Activate Enhancement CATS0005 (SMOD) in a customer project (CMOD)
- Add your field to CI_CATSDB, add field to customer screen disabling input and perform minimum development required in EXIT_SAPLCATS_005, EXIT_SAPLCATS_008 and global data include ZXCATTOP (as you wont actually manage this field here)
Activate Enhancement CATS0002 in the same project or another
- In exit EXIT_SAPLCATS_002 fill your field
Regards,
Raymond

Brief about enhancements and user exits

hai,
can any one tell me what are enhancements and user exits in sap sd,
their signifcance & configuration
regards
sriram

hi,
an example of user exit
In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the Target *** Qty required and the Target *** Date for a specific customer who was not sending *** Qty Received by him.
So for that specific customer we used the search term and added the same in the Data 4 field of the IDOC under segment E1EDK09.
There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating *** Issued and then find out the difference from Target *** Qty and get *** Qty Received for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
User exits in SD
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Pl reward if helpful.
Thanks
Sadhu Kishore

What is the Difference 'VOFM' and 'User-Exit' ?

What is the Difference 'VOFM' and 'User-Exit' ?

If you need to implement any of these User exits, you first create a project for the user exit, then assign the user exit(s) to your project. Then you write the coding for the user exit, and finally activate the project.
For general information about user exits, in the R/3 Library, go to Basis components and look at the Enhancements section. In addition there is detailed information about each user exit that you can access when you assign it to your project (see below).
Activities
Start by creating your project.
1. Enter a name for your project.
2. Select Modification -> Create.
3. Enter a short text for your project and select save.
Next assign the user exit to your project.
4. Select Components.
5. Enter the name(s) of the user exits you want to implement.
6. Select SAP documentation, if you want detailed information on this user exit.
7. Select save.
8. Select back.
Next make your coding modifications.
9. Select enhancement components.
10. Select change.
11. Select the user exit you want to write code for.
12. Select the include zxpbco01.
The system will then prompt you to create this include, and you can continue to write your coding in it.
Next activate your project.
13. Return to the initial screen and select activate project.
Routines
Routines are short sub-programs that carry out various checks during document processing. In the SD module, you can create and process routines for copying requirements, data transfer, requirements and formulas using transaction VOFM. Besides the routines delivered to you with the system, you can create your own individual routines.
Transaction VOFM allows you to follow a standardized procedure for creating routines. The name ranges are predefined for routines delivered to you with the system and for routines created by the customer. This name convention guarantees that your own routines are not overwritten during a Release upgrade.
Copying requirements and data transfer
The routines for coying requirements and data transfer are defined for the document types sales orders, deliveries, billing documents, sales activities, as well as for texts. You specify copying requirements and the data transfers when defining the document flow for each document type. You enter the routines for texts in the access sequences for texts.
o Copying requirements determine which data is copied during the copying of documents. A copying requirement could define, for example, that the same customer must appear in the document header when you copy an inquiry to a quotation.
o Routines for data transfer make a detailed control of the copying of fields possible. A data transfer could define, for example, that particular item fields can only be copied in combination with other particular fields and can only be copied into contracts or credit and debit memos.
Requirements and formulas
Routines for requirements and formulas are used for functions using the condition technique. You enter these routines in the pricing procedure or the condition types. Requirements are also used for statistics.
o A requirement in pricing can determine that an access is dependent on a particular precondition. It can carry out a check of the document currency, for example, and, depending on whether it is a foreign or the local currency, allow or deny the access.
o Formulas are used in pricing to define various factors for pricing. Formulas are defined for scale base value, condition base value, condition amount, group key, and rounding rules. The formula for a rounding rule could define, for example, that all calculated amounts are rounded to two places behind the decimal point during a price change of the condition record. The formula for a condition base value could define, that the header discount is distributed among the order items according to volume an not value of the item, as is the case in the standard SAP R/3 System.
Creating routines
There are two methods to create a routine
1. Creating by overwriting
When using this method, a note appears as a commentary in the routine to be newly created.
2. Creating
When creating a new routine, an ABAP with internal number assignment is created.
You always have to activate a new routine before using it. Each routine for requirements and formulas, copying requirements and data transfers is stored in a separate program. For each new routine an entry is added in table TFRM and TFRMT. For each routine, a long text can be stored as a text module.
Most routines must be changed in client 000. Transaction VOFM can be transported as XPRAs, which means that after the import all routines can be activated.
Name ranges for routines
The standard routines are to be within the number range 001-599 (for 2 digit formula numbers, 01-49)
The user routines are to be within the number range 600-999 (for 2 digit formula numbers, 50-99).

How to find the appropriate user exit for invoic02 idoc in idoc_output_invo

Hi all,
I am new to this community p
i have issue regarding the How to find the appropriate user exit for invoic02 idoc in idoc_output_invoic function module.........
thanks,

Hi ,
welcome to SDN.
You can select the appropriate Customer exit accrding to the available parameters .
The list of exits available are
EXIT_SAPLVEDF_001
EXIT_SAPLVEDF_002
EXIT_SAPLVEDF_003
EXIT_SAPLVEDF_004
For Example , if you want to modify the Idoc data(EDIDD) you have to use the EXIT_SAPLVEDF_002. accodingly you can select the user exit according to the avaialable parametres.Use Table MODSAP fto get the Enhancement name.
Hope this Helps
Rgds
Sree
Edited by: Sree on Jul 23, 2010 12:11 PM

Additional user mapping fields

Hi,
I am trying to add some additioanl fields of a system to user mapping screen.
so, i created a system based on com.sap.portal.howtos.webapp.par that i downloaded from SDN
2. added a property "department" to that par file and defined in usermapping fields tag of par file.
3. now i created an iview for system based on this par file and under "user management" cateogry, I selected "additional user mapping fields" and specified " {mech,chem,comp,elec}Department "
4. everything is fine and this dropdown box appears in user mapping iview
but my concern is that i want to send 0 for mech, 1 for chem, 2-comp etc... to an url iview. i just want to know.. how to store name-value pairs in that dropdown listbox of user mapping iview?
any clues?
thanks

Hi Daniel,
Thank you for your reply..it was helpful for me for other issues, but didnt help me for the question of this thread. may be i was not clear in explaining my question. In simple.
1. I create a system par file with one additional field dept.
2. i create an alias
3. now the user wants to do usermapping..so he goes to user administration --> user mapping and select a user
4. then he selects the alias of a sytem in the dropdown list box, so two fields appear, i.e. username and pwd, but i want an extra field named dept with a list box of values (computers, mechanical, electronics)
5. i was able to achieve this, by setting {computers,mechanical,electronics}dept" in the property, "Additional User Mapping Fields" of the System object created from the par.
6. now when the user selects that system alias in the user mapping screen.. he will be able to see three fields.. username, pwd and dept(with a listbox) and he can map the user to the respective department.
7. the listbox that is created has value and title the same like,<otpion value = "computers">computers</option> but i want it as <option value="1">computers</option>.
Could you please help me in achieving this. please let me know if you need any further information.
Thank you.
P.S: eventhough, i specify the field dept in portalapp.xml like you mentioned, it will appear as a list box in the system object created from the par, but in the user mapping screen it appears as a text box. so we must specify the "dept" in the property "Additional UserMapping fields" of the system object created from par.

Doubt in Idoc user exit..............

Hi All,
 i have written the user exit for Sales Order subscreen tab called additional data2 , this tab is provided by sap for developer can write their own user exit coding.
 my doubt is whenever PO comes as an Inbound IDOC i need to pass the value from segment to my user exit fields.
 where can i find the inbound idoc user exit for SO .
 Thanks in advance,
Regards,
Saravanan.

Look at enhancement VEDA0001. It has got quite a few user exits you can use. You will also need to enhance the IDOC for the additional fields you have added on your screen.
Cheers,
Sanjeev

Stock placement strategy via user exit

Hello,
I'm tring to change putaway strategy by using a user exit.
In customizing i enter:
Logistics Execution u2013 Warehouse Management u2013 Strategies u2013 Putaway Strategies u2013 Define strategy for fixed bins.
Table V_T301S.
When i enter one of the movements i can put V next to User exit act.
How can I make the connection between the strategy and the user exit?
Thank you,
Lilah.

Hi,
In the ST masterdata (config: WM - Masterdata - Define ST) you must activate the User Exit field for putaway and/or removal for the specified ST you want to use with a user exit. See view: V_T3010-USEIN or Table T331-USEIN. When this indicator is set and you go through the TO creation log, you will see that at some stage there will be an entry where is states that you are using an user exit to place/pick stock.
Cheers,
Hein

User exit for VT01n (Creation of shipment)

Hii All
We have a requirement where we have to automatically enter the planned shipment scheduled time & end time and date for each stage while saving the shipment.
Can anyone let me know user exit which can be used to do the same.
Thanks & Regards
Gaurav

Hi,
You can use V56FSTAT this user exit for your purpose..
If you want more selection of user exits you goto transaction SMOD and input V56* and then press F4,so that you can see all the user exits can be used for shipment or transportation purpose...
Regards,
Chandra

Populating custom idoc thro user exit.

Hi friends,
How can i populate an custom idoc thro user exit?.I haven't done user exit earlier.So Pls let me know in detail.
Thanks and regards.
tharun

Which standard Idoc did you extend? Is it outbound or inbound? Find out what the processing function module is. WEDI is the area menu transaction for all the IDoc related activities.
Once you know the function module, you can then find out what the user exit that is there in it. Then you can go to CMOD and in the menu, click on SAP Enhancements and then click on more options in the selection screen. Enter your function module name in the component there and execute the report. See which enhancement it is included in. You can then create a project in CMOD, assign this enhacement and select the user exit and activate the project.
Next within the function module, in the user exit function module, there will be an include. Double click on it and create upon prompt. After that, it is just your code to fill in the new segment and add it to EDIDD internal table of your function module.
Srinivas

COPA Valuation User Exit

When posting a document to COPA, I want to swap the value of one of the value field with another value field.
1. Is it possible?
2. Do we have a user exit for the same?
I tried COPA0002 but somehow when I create my billing document, control is not coming to that user exit at all.

COPA0002 need to be activated from transaction KE4U, setting the user exit field to U01

Any user exit for MIRO

Hi All,
   Is there any user exit / field exit which gets activated when invoice party value ( in the detail tab of transaction MIRO ) gets filled (either manually or from PO ). The requirement is to display a warning message, once the invoice party is filled, if its a particular supplier.
Thanks in Advance.
Regards,
Kiran

Hi,
Check the following user exits available for MIRO transaction,
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006            Logistics Invoice Verification: Process XML Invoice
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification
Rgds,

User exit/BADI required for coding for the selection custom fields in RSA3

Hi,
I have a requirement in the Datasource extractor. I need to add custom Z fields in the Data souce of the 2LIS_02_SCL and need to include in the selection part. So I have added the custom filed in the append structure and include the check in the selection checkbox in the transaction LBWE under the datasource specified above. For the corresponding custom fields, to be populated in the ALV list, I have written the code in corresponding user exit ZXRSAU01.
Now I can view my custom Z fields in the list as well as on the selection fileds while executing the transaction RSA3. But I need to write code for the selection criteria part. On entering value in the selection criteria of my custom z field, no values are selected to the corresponding query. Please let me know where should i write the coding part for the selection criteria of the Z fields for the Datasource.
On debugging, to my understanding only the standard fields are alone getting filtered by providnig the values in the selection part of the RSA3 tcode. It is called in Macros : Sel < Datasorce> .... and the fetch cursor is included inside the macros.
Please let me know any user exits or Badi;s available for it.
Thanks in advance

Hi shivu,
you might try the BAdI RSU5_SAPI_BADI. A good introduction can be found in the following document:
[Enhancing DataSources with BAdI RSU5_SAPI_BADI|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/3001894b-b1fb-2910-77ba-e80b6f2053b7]
The BAdI is called at the time of extraction, so this would be the right place to populate your additional fields.
Best,
Chris

Selection on User Exit Field in InfoPackage

Similar Messages

Maybe you are looking for