USER EXIT for Validation

Dear All,
We have two user group for creating the Sales Order.They are
1. Sales order creation (Real ) and 2. Sales Order creation (Virtual ).
Our requirement is that a user(s) belonging to Real must be able to create Virtual SALES ORDER and vice versa.
We have identified the table and the field as mentioned below.
Table is VBAK ( Transaction Code : VA01 & VA02), & Field is ZZSO_SORT.
As we are planning to write a Validation in FI as per the below logic.
Validation 1.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( REAL group),then check ZZSO_SORT = REAL (hard code value)
Validation 2.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( VIRTUAL group),then check ZZSO_SORT = VIRTUAL (hard code value)
But we don't have the table VBAK( and also the feild ZZSO_SORT) in FI validation (OB28),so we have to write an user exit.
As we have fever knowledge about writing a code for user exit( as per above logic) and assigning the same to the respective Validation,it will great,if some one can assist us to achieve our target.
Thanks for your time and patience.
Regards,

Hi
I don't know where the information for that field is from
Validation 1.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( REAL group),then check ZZSO_SORT = REAL (hard code value)
Validation 2.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( VIRTUAL group),then check ZZSO_SORT = VIRTUAL (hard code value)
The field VBAK-ZZSO_SORT can be filled programatically by the user-exit USEREXIT_MOVE_FIELD_TO_VBAK (include MV45AFZZ):
FORM USEREXIT_MOVE_FIELD_TO_VBAK.
IF T180-AKTYP = 'H' OR "---->VA01
 T180-AKTYP = 'V'. "---->VA02
 IF SY-UNAME = <......>.
 VBAK-ZZSO_SORT = 'REAL'.
 ENDIF.
 IF SY-UNAME = <......>.
 VBAK-ZZSO_SORT = 'VIRTUAL'.
 ENDIF.
ENDIF.
ENDFORM. "USEREXIT_MOVE_FIELD_TO_VBAK
Otherwise it needs to know who/what inserts the value of VBAK-ZZSO_SORT in order to decide where the control has to be placed.
Max

Similar Messages

BADI/User Exit for validation in WAK1

Hi,
I need to put validations in transaction WAK1.
for the Site Groups under the site groups TAB.
Please suggest if any BADI or User Exit is available to do this.
I checked there are BADI's "WAKT_BADI_001" to "WAKT_BADI_008" but they are for SAP Internal Use only.
Regards
Ankur

Hi
Below are some of BADIs available for WAK1. Please check.
Exit
WCOUP001 User exit for coupon processing in POS inbound
BADIs
RDM_BAPI_PROMO_CREATE - Enhancement Spot (RDM_OPT_PROMO_IN)
RDM_PROMO_POST - Enhancement Spot
RDM_PROMOTION_WAK1 - Enhancement Spot
WAKT_BADI_001 -
~~~Ganesh Kumar K.

User Exit for Validity Date for VA41 Tcode

Hi,
I am giving order type in VA41 Tcode and then Clicking on 'Create with Reference' .Then a Pop Up is getting generated. In this i am giving Contract created with validity date lessthan today's date(in Contract Tab).For Example i created a Contract xxxxxx with 'valid to' 9.12.2008. When I am giving this contract and clicking on 'Copy' button a Warning message is getting generated 'The sales document is only valid until 09.12.2008'. Now i have to change this into Error message instead of Warning Message.
i used User Exits mv45afzz,MV45AFZA,MV45AFZB. But the debugger is getting started only after Warning message got generated.Is there any User Exit for which debugger gets started when i give the Contract and then Click on 'Copy' button. Please Suggest.
Thanks and Regards
K Srinivas

Hi,
One idea. Go to VTAA (copy between sales docs) and create a new VOFM where you manage the copy control. Set a warning/error message in the new VOFM (in your range number), and try it.
Regards,
Eduardo
Edited by: Eduardo Hinojosa on Dec 10, 2008 3:58 PM

User exit for validation of field NEWKO in f-48 tcode in finance

hi,
Previously we validated the Field XBLNR (Reference) in the document header from the table EKKO, for the PO Number. now we want to validate the vendor number(LIFNR) in the field NEWKO from the table EKKO with reference to the PO number entered in the field XBLNR.
we want to find out the correct user exits or any enhancement for the above validation.
pls help me in this regard ,matter most urgent.
Thanks & regards
veera

hi,
for f-48 you could use FI-validation with tcode OB28
use an exit (UK...) for your check in Program ZGGBR000
A.

User Exit for validating overall limit field and expected limit field-ME2xN

Dear Gurus,
Can you please suggest me any user exit or BAdi to validate the overall limit field and expected limit field in transaction ME2xN.
Or any other way to to achieve this functionality in ME2xN.
Our Requirement is while raising a service PO in the Limits tab the 'Overall limit' should be same as 'Expected Value', at present the user can enter overall limit greater than 'Expected Value'.
Regards,
Priyank Joshi

this will not work. you cannot add another structure (AUFK) on top of CEBAN. all characteristics have to be of one structure and since you want to release a PR it has to be CEBAN. before attempting to program something around that why do you not go to tx. OLME -> PR -> Release Strategy -> With Classfication -> Release Strategie and run it in a simulation mode. you will then see how it reacts.
there's a white-paper on service.sap.com explaning in detail release-strategies. it's a good one and a good read too!

User Exit for VA41 Validity Date

Hi,
I am giving order type in VA41 Tcode and then Clicking on 'Create with Reference' .Then a Pop Up is getting generated. In this i am giving Contract created with validity date lessthan today's date(in Contract Tab).For Example i created a Contract xxxxxx with 'valid to' 9.12.2008. When I am giving this contract and clicking on 'Copy' button a Warning message is getting generated 'The sales document is only valid until 09.12.2008'. Now i have to change this into Error message instead of Warning Message.
i used User Exits mv45afzz,MV45AFZA,MV45AFZB. But the debugger is getting started only after Warning message got generated.Is there any User Exit for which debugger gets started when i give the Contract and then Click on 'Copy' button. Please Suggest.
Thanks
K Srinivas

Hi,
Create a file say breakpoint.txt file as follows:-
[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand
Once you come to the screen of 'Create with reference' where you are giving the contract, from second session drag the above mentiuoned file to the session where you are running VA41, & drop it here. Now debugger has been activated. Proceed with debugging. This method you can use for any of the 'POP UPs'.
I hope this helps,
Regards
Raju Chitale

User exit for transaction VA01 for screen validations

Hi All,
I would like to know a user exit where I can validate the entry for "sold to party" on second screen of VA01 transaction against the sales area entered in the first screen.
Also please let me know how to code in "MV45AIZZ" to capture the same if it can be done.
Regards,
Usha.

Hi Usha,
Following are the User Exits for VA01.
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document 
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
Have a look at V45A0002.
Reward points if it helps.

User Exits for Purchase order Header Text Validation

Hi Experts,
I need user exit for validate a Long text in Purchase order header data for a Particular Doc type.
We are using 4.6 B so badi is not available .
So pls tell me user exit for the same or any other method as i was unable to find user exit for this scenario.
Note : This valiadation should trigger whhile creating PO.
Warm Regards
Santosh Kumar
Edited by: Santosh L on Mar 19, 2010 9:58 AM

i have used concept of global memory through call stack

How to find the exact user exit for our requirement?

Dear Mr. keerthi,
can you please explain me how to find the exact user exit for our requirement?

Hi sandip
There is more than one method in which you can check for user-exits.The following method is used very often.
How to find the exact user-exit for your requirement.
1. You can check the user exists using transaction SE85.
2. Repository Information System -> Enhancements -> Customer exits
3. You can search the user-exits by package name.
4. Double click on each exit name to check the function module exits.
The procedure to find the package name.
Execute transaction SE93
Enter the tcode of the transaction for which you want to check the user exit.
Example: if you want to find the user-exit for purchase orders while changing, enter ME22n and press display.
You will get to see the package name
But you need to confirm that the user exit will get triggered at the appropriate event.
( example: you might want some validations to be done ON SAVE of a purchase order)
Checking if the user-exit is getting triggered or not.
1. Open the user exit function module (that you have got in step 4) in Tcode SE37.
2. Click on where used button. In the pop up that immediately appears choose only programs .
3. You will get a list of programs. Double click on the program name.
4. You will get the list of location where this function module user exit is used.
5. Place session break points at each of these location ( at each CALL FUNCTION statement)
6. Now go to your transaction ( say change purchase order tcode:Me22n) and check if the user exit is getting triggered on appropriate event.
regards,
Prasad

Logic and User Exit for Availabilty Check in Sales Orders,

Hi All,
I have a requirement of creating a Sales order from an Inbound IDOC. Before saving i need to do all the validations for the sales order including the availabilty check for the sales orders. If it is not fulfilled i need to reject the sales order creation.
I am trying to search for the logic for the availabilty check of the sales order but i am not able to find one. Please help me out with that and also i need the user exit for the availabilty check for the sales orders. Please help me out with that one too.
Regards,
Sharadendu

See this function Module for message type ORDERS
IDOC_INPUT_ORDERS all validations are there in this Function Module .
Please reward if useful.

User Exit for Company Code verification

Helo All.
I have to add a validation that Company code of the sales organisation should be same as company code of the plant from where the product is sourced.
Is there any User Exit for this?
Thanks in advance.

hi,
please tell me what the T-code for this one
Regards,
Vijay

FBCJ BADI/User Exit or Validation Rule Implementation

Inspite of my maintaining validation as under, i am not able to achieve what i desire, i.e., System is still posting Cash transactions thru FBCJ t code for amount exceeding INR 50,000
1. Created a validation name
2. Assigned it to Application Area - FI
3. Callup Point - 2 Line item
4. In validation step 0001, created pre-requisite as
Transaction code = 'FBCJ' AND Account Type = 'D' AND
Posting key = '15'
5. Under check, Amount <= '50000.00'
6. Entered E in message type with corresponding message class ZKM_MSG_CLASS for message number 018
7. Assigned the above validation in OB28 t code for activation level 1 (i.e., Active)
System display a message; but also post it as well, despite of 'E' error message type.
How to tackle with the above problem.
Is there any other badi/user exit for FBCJ. I have only find CJ_DOCUMENT, but it's not working for me.
Thanks and Regards,
Sohail

Hi
Below are some of BADIs available for WAK1. Please check.
Exit
WCOUP001 User exit for coupon processing in POS inbound
BADIs
RDM_BAPI_PROMO_CREATE - Enhancement Spot (RDM_OPT_PROMO_IN)
RDM_PROMO_POST - Enhancement Spot
RDM_PROMOTION_WAK1 - Enhancement Spot
WAKT_BADI_001 -
~~~Ganesh Kumar K.

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

User Exit For PR Create and Change

Hi,
Please help me for finding User Exit while creating Purchase Requisiton(Me51/Me51n) and aslo changing Purchase Requisiton(Me52/Me52n).
Mainly i want to exit for validating Plant and material code while creating and changing PR.
Thanks,
Sunil sahoo

Hi,
Use the exists
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
Regards,
Nandha

User Exit for Inbound Process - Changing IDOC control record

Hi,
I want to utilize the identification field (under details tab) of the IDOC Control Record. What is the suitable user exit for inbound process that i can use to change the IDOC control record?

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

USER EXIT for Validation

Similar Messages

Maybe you are looking for