User Exit for ML81N at the time of save -- urgent

hello all,
I need to fill the field reference field in ML81N transaction with some value for this i need to find user exit i was able to find so many user exits for this transaction but i couldn't find the perfect user exit at the tiem of save,
Any pointers wouls be of great help..............

Hi,
check these 2 threads.
User exit in ML81N
Urgent. Badi or user exit for ML81N transaction
Regards,
Maha

Similar Messages

User Exits for FI transaction at time of 'Save'

Hi All,
I'm looking User Exits for the FI transaction - FBD1.
I used CMOD to identify the user Exits available for the 'FBAS' package:
F050S001 - FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
F050S002 - FIDCC1: Change IDoc/do not send
F050S003 - FIDCC2: Change IDoc/do not send
F050S004 - FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
F050S005 - FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
F050S006 - FI Outgoing IDoc: Reset Clearing in FI Document
F050S007 - FIDCCH Outbound: Influence on IDoc for Document Change
F180A001 - Balance Sheet Adjustment
FARC0002 - Additional Checks for Archiving MM Vendor Master Data
RFAVIS01 - Customer Exit for Changing Payment Advice Segment Text
RFEPOS00 - Line item display: Checking of selection conditions
RFKORIEX - Automatic correspondence
SAPLF051 - Workflow for FI (pre-capture, release for payment)
However I'm looking for an user exit that is called at the time of 'Save'. I'm looking to make some changes
so that no entry can be posted in the above transactions until a document has been attached. None of the User exits above seem to be available at the time of 'Save'.
Is there any OSS note for a User Exit/BADI that can be used at the time of 'Save' for these transactions?
Thanks in advance..
Deepika.

Hi Deepika,
for your requirement you can use FI substitutions (entire document). Check transaction GGB1. They allow to change fields from FI tables (BKPF,BSEG,BSIK,BSAK, etc...)
Please remember to reward points if the answer is useful and eventually to close the post if it solves your problem.
Regards, Manuel

User exit for ML81N

Hi all,
I am looking for user exits for T code ML81N, where in I want to validate 2 fileds i.e. net value inclusive of tax ESSR-NETWR and
PRsp. Intern ESSR-SBNAMAG.
I have tried all the exists available in SMOD for the develoment class.
can any one tell me how to solve this.
Best Regards
Sree

Hi,
Try to check any BADI's Available.
to find the user exits & Badi's for the T-code..
go to table TSTC>enter T-code and execute> get the Program for the t-code..
and go to-se38-->get the package attached to the t-code..
next go to t-code Se15>expand the enhacement tab>enter package under userexit and
                                                     execute you will get the list of exits
                                                     available...
                                                  -->enter package under Badi's tab and
                                                     execute you will get the list of Badi's
                                                     available...
All the User exits are stored in Table MODSAP..
Prabhudas

User Exit for ML81N (Service Entry)

Hi All,
I need user exit for Service Entry Sheet(ML81N). So which user exit is fired when run the transaction after save(ML81N). Please help me urjent.
Thanks & Regards
Ravi Kumar

Hi All,
I am having similar problem with ML81n. I need to add tab (along with few fields) on ML81N and need to pass the data in ESSR table.
I am using enhancement - SRVEUSCR, thru which i am able to display tab on screen.
But i am not able to capture value enter on screen in function modules:
exit_saplmlsr_020 AND exit_saplmlsr_021.
I have added fields in structure - CI_ESSRDB and using the same fields in new customer screen in SE51(Screen fields named as ESSR-Field1 (field1 is added in CI_ESSRDB )).
Please assist and let me know where i am going wrong.
Thanks
Rajesh

User exit for ML81N after SAVE

I need a User exit for Service Entry Sheet change after the user has Saved the release. I need to update a customized "Z" table when a Service Entry is released from ML81N. I need to ensure the Service Entry is saved with release status. The user-exits such as SRVESSR are triggered during creation of the Service Entry but not after Save. For e.g. if I used that exit to update my Z table, the Service Entry release may not have actually saved (say due to some error), but my Z table would have been updated. Is there a solution for such a requirement?? I saw some previous threads similar in request, asking for a User exit after SAVE, but it seemed to relate to WorkFlow.

hi ...
try to use MB_CF001 exit ....
The enhancement MB_CF001 includes a function module that is called up
immediately before the COMMIT WORK when a goods movement is posted.
All the material document data is passed on to this function module from
the following tables:
o   MKPF    (Material document header)
o   MSEG    (Material document items)
o   VM07M   (Update data)
This data can be passed on to other programs.
Note
The enhancement does not write any data to the material document, that
is, it is not possible to change material document data before the
update posting takes place.

Badi or user exit for allocation run (Tcode-J3AT) on save button

hi friends,
i m searching for the BADI or user exit for the Tcode J3AT on the save button press. if u know any badi or user exit for same pls let me know.
thanks and regards,
vicky.

solved with the help of SAP note.

Enhancement/Badi/Enhancement Spot required for BP at the time of SAVE

Dear Friends,
I have a requirement to update the custom field(Created by using EEWB) in BP transaction at the time of Save, based on the condition Risk Class Category, Could any one help me in finding the solution such as BAdi/Enhancement Spot/User exit where I can find the values of Risk Class category, Credit segment category and the custom field I can change at the time of save.
Appreciate Ur help Thanks alot in advance.
Br,
Naveen

Hello Selva,
I tried both the options.
The SDVFX008 is getting triggered.
*if cvbrp-netwr is INITIAL and cvbrp-fkimg is NOT INITIAL.
* MESSAGE 'Not Valid' TYPE 'S' DISPLAY LIKE 'E'.
* ENDIF .
this is my logic but the values are initials.
Is there nay other method which I can use?

User exit for copying planned delivery time

Hi
My requirement is to copy the value in field Planned delivery time from contract to planned delivery time field in MRP2 view in material master. Please let me know which user exit or enhancement may be used for the purpose.
TIA.

Hi
Check BADI_MATERIAL_CHECK
Regards
Sanil

User Exit for ML81N - Goods Receipt

Hello,
I need to populate BSEG-XREF1 and BSEG-XREF2 with custom values from ML81N - Can't find a BADI or User exit - is there one?
Many Thanks

Should able to do it with FI substitution:
Transaction Code: OBBH
1. Create a substitution
2. Create a Step and Define the pre-requisites eg: document type
3. Create the substitution rule. You can create an exit and use it
For more information on creating and maintaining substitutions, see Financial Accounting -> Special Purpose Ledger -> Validations and Substitutions -> Substitutions in the SAP Library.

Need User Exit for ML81N SAVE

Scenario: Track employee id wise payments using SES ORDER field
A.     To track employee Id in Service Entry Sheet (SES)
Payments such as Mobile bill, OYC allowance is made against Service Purchase Order.
1)      In SES, user will enter employee Id in field AUFNR i.e. Order.
2)     Create z-table to maintain Expense GL A/c
3)     While Save, get Service POu2019s GL A/c, validate in Z-table. If exists, then validate entered employee id.
Is there any user exit which we can use while SAVING ML81N.

Hi,
I would advice you to use the user defined fields in table ESLL instead, like
ESLL-USERF1_NUM   User-Defined Field
ESLL-USERF2_NUM   User-Defined Field
ESLL-USERF1_TXT   User-Defined Field
ESLL-USERF2_TXT   User-Defined Field
and develop a custom solution with the help of customer enhancement
SRVDET.
Regards,
Edit

Urgent. Badi or user exit for ML81N transaction

Hi!
   Currently I am working on the transaction LM81N. I am looking for a user exit or BADI before save (commit work). I need to modify the XIMSEG table where this table is updated in the code:
FORM SET_XIMSEG_ACC using p_rcode.
*&      Form SET_XIMSEG_ACC
      ximseg fuellen - Buchung auf Ebene Kontierung
p_rcode = 0.
CLEAR XIMSEG.
XIMSEG-BWART = T156N-BWART_NEXT.
XIMSEG-EBELN = XESSR-EBELN.
XIMSEG-EBELP = XESSR-EBELP.
XIMSEG-KZBEW = 'B'.
XIMSEG-LFBJA = XESSR-ERDAT.
XIMSEG-LFBNR = XESSR-LBLNI.
XIMSEG-ELIKZ = XESSR-FINAL.                 "set ELIKZ
IF XESSR-KZABN EQ KZABN_S.                  "Storno
XIMSEG-XSTOB = 'X'.
XIMSEG-ELIKZ = SPACE.                     "reset ELIKZ
ENDIF.
XIMSEG-ERFMG = 1.
XIMSEG-ERFME = XEKPO-MEINS.
XIMSEG-BPMNG = 1.
XIMSEG-BPRME = XEKPO-MEINS.
<b>XIMSEG-SGTXT = XESSR-TXZ01.</b>
LOOP AT XESKN WHERE PACKNO EQ XESSR-LBLNI
              AND LOEKZ IS INITIAL
              AND NETWR > 0.
XIMSEG-LFPOS = XESKN-ZEKKN.
APPEND XIMSEG.
ENDLOOP.
IF SY-SUBRC > 0.
p_rcode = 8.
REFRESH: XIMSEG, XEMSEG.
exit.
ENDIF.
ENDFORM.                    " SET_XIMSEG_ACC
I need to modify
XIMSEG-SGTXT = XESSR-TXZ01 with ESSL-KTEXT1
I found that use ATP_PUBLISH_RESULTS BADI after the call SET_XIMSEG_ACC . But I didn't found it.
Thanks in advance.

Hi Diana,
these are the available exits for this t.code:
Enhancement/ Business Add-in            Description
Enhancement
SRV_FRM                                 SRV: Formula calculation (obsolete since 4.0A!)
SRVSEL                                  Service selection from non-SAP systems
SRVREL                                  Changes to comm. structure for release of entry sheet
SRVQUOT                                 Service export/import for inquiry/quotations
SRVPOWEB                                Purchase order for service entry in Web
SRVMSTLV                                Conversion of data during importing of standard service cat.
SRVMAIL1                                Processing of mail before generation of sheet
SRVLIMIT                                Limit check
SRVKNTTP                                Setting the account assgnmt category when reading in, if "U"
SRVEUSCR                                User screen on entry sheet tabstrip
SRVESSR                                 Set entry sheet header data
SRVESLL                                 Service line checks
SRVESKN                                 Set account assignment in service line
SRVESI                                  Data conversion entry sheet interface
SRVENTRY                                Unplanned part of entry sheet (obsolete since Rel. 3.1G)
SRVEDIT                                 Service list control (maintenance/display)
SRVDET                                  User screen on tab strip of service detail screen
INTERFAC                                Interface for data transfer
o.of Exits:         18
o.of BADis:          0
Try to found the correct exits and provide the and activate the exits.
If u wan to where the exits is working put the breakpoint.
***********Rewords some points if it is useful.
Rgds,
P.Naganjana Reddy

User exit for MIGO after the material document is created?

hi guys ,
I have requirement like after the material document was creted in migo i need to call my new transcation. can any one please let me know how i have to solve this ?
Moderator Message: Unfortunately, this is not a training forum and we can teach all about Exits and Badi's. I suggest you take a classroom course..... or do some R&D first
Edited by: kishan P on Nov 30, 2010 11:57 AM

Hi
U need to create a FM with UPDATE MODULE attribute checked: so you fm can be run in UPDATE TASK
This fm has to have the same interface of the method of the BAID (or user-exit) or a parte of it, if you don't need to use all parameters of the interface.
All code to schedule the job has to be placed in this fm: you can use the fm JOB_OPEN and JOB_CLOSE in order to scheule a job programmatically.
Call this fm in the BADI, the call has to be in UPDATE TASK, in this way your porgram can start as soon as all updating processes are over
Max

User exit for Tot. repl. lead time

Dear all
My client got around 30 plants and Tot. repl. lead time they maintain for each material like 2 days to 20 days this is what is considered for delivery correct me if i am wrong . now they want to fix the delivery days like 7 days or 10 days for each plant irrespective of the what is maintained in material master.
i have planned to have a z table to maintined which user can select the plant and no of days they required .
but will it affect the planned order and production order ?
Regards

Hi,
If you need this specific to Sales order, then idea of creating new Table specific to Plant and call it some exit while processing sales order
As you will have separate Item Category to create Planned Order from Sales order, you can restrict it with specific to Item category
In this way you can mitigate the impact
regards,
santosh

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 VA02

Hi All,
My requirement to automatically change the schedule line dates (ETDAT) in a sales order when the requested delivery date (KETDAT) of the document is changed.
The schedule line dates should automatically change to the date that is changed in the requested delivery date.
Is there any user exit or enhancement point to achieve this.
Thanks in advance.
Regards,
Darpana.A

>
Darpana Ahire wrote:
> HI,
>
> In Include FV45KF0V_VBAK-VDATU_PRUEFEN I have implemented an enhancement point, just before the data declaration of the include
>
> *---This logic does not display the warning that Date is not copied to the schedule line items
> data: v_vdatu like vbak-vdatu,
>         v_vprgr like vbak-vprgr.
>
> if sy-tcode = 'VA02'.
>   call function 'PERIOD_AND_DATE_CONVERT_INPUT'
>     exporting
>       dialog_date_is_in_the_past = space
>       external_date              = us_ketdat
>       external_period            = us_kprgbz
>     importing
>       internal_date              = v_vdatu
>       internal_period            = v_vprgr.
>
> if *vbak-vdatu <> v_vdatu.
>   *vbak-vdatu = v_vdatu.   "Initialising the Changed date
> endif.
> endif.
>
>
>
> In Include FV45EFEP_VBEP_UNTERLEGEN I have implemented an enhancement point, just before the data declaration of the include
>
>
> DATA: v_vdatu TYPE EDATU_VBAK.
>
> if sy-tcode = 'VA02'.
>
> *---Selecting the required delivery date
> SELECT single vdatu
>        from vbak
>        into v_vdatu
>        where vbeln = vbak-vbeln.
>
> *---Checks if the Required delivery date is changed then changes the schedule line items first date
> if vbak-vdatu <> v_vdatu.
>   loop at xvbep.
>      xvbep-edatu = vbak-vdatu.
>      modify xvbep TRANSPORTING edatu.
>   endloop.
> endif.
>
>
> *---Checks on click of Save button
> if sy-ucomm = 'SICH'.
> *---Checks if the Required delivery date is changed or not
>    if vbak-vdatu <> v_vdatu.
>      loop at xvbep.
>        xvbep-edatu = vbak-vdatu.
>        modify xvbep TRANSPORTING edatu.
>      endloop.
> *---Modifys the database table VBEP accordingly
>        modify vbep from table xvbep.
>    endif.
> endif.
>
> endif.
>
>
> Hope your problem gets solved by this logic.
>
> Regards,
> Darpana.Ahire
Hi Darpana,
I have a requirement to automate the requested delivery date while creating the sales order through VA01.
I have to add some lead time to the defaultly proposed requested delivery date.
I am able to change the requested delivery date VBAK-VDATU and schedule line date VBEP-EDATU.
I have done it through form 'SAVE_DOCUMENT_PREPARE' in SAPMAV45A.
Now my client requires this date date has to be reflected in all places like in goods issue date, loading date, material availability date, invoice date etc.,
As my user exit triggers only at the time of saving the document, changing the requested deliery date is not affecting all these dates.
Any solution for this.
Highly appreciate your help.
Thanks
Sreenivasa Reddy Vallem

User Exit for ML81N at the time of save -- urgent

Similar Messages

Maybe you are looking for