ALV + User Exit

Hi all,
One of my friends here is facing a small issue in using ALV(Classic) within a user exit.
In the existing ALV display, he is using a form for setting the PF-Status as follows.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
         I_CALLBACK_PROGRAM          = report_name
         I_CALLBACK_PF_STATUS_SET    = 'F100_PF_STATUS_SET' n so on n so forth ...
But since this is being written within an exit, it does not permit the use of FORMENDFORM for the dynamic call of the subroutine 'F100_PF_STATUS_SET'.
Anybody who has worked on Exits and ALV, your inputs would be of great help.
Hope my question is clear !!
Many Thanks,
Gayathri.

Hi, try my solution.
Create a new report, assume name it ZCALLBACK, and write your F100_PF_STATUS_SET form in it, like following:
report ZCALLBACK.
FORM F100_PF_STATUS_SET.
your logic
ENDFORM.
And in your user-exit, call the ALV function like following:
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
     I_CALLBACK_PROGRAM        = 'ZCALLBACK'
     I_CALLBACK_PF_STATUS_SET = 'F100_PF_STATUS_SET'
Hope it will be useful to your scenario.
And thanks a lot

Similar Messages

MEREQ001 User Exit Problem for ALV Columns.

Hello,
I am using this user exit to make changes to the Purchase requisition enjoy transaction. There is an ALV used for item details and if you use the customer CI_EBANDB include in EBAN table you can see those fields available in the alv and you can add them up using change layout.
To make these fields editable as they remain in display always inspite of the fact that you use ME51n or ME52n.
MM --> Purchasing --> Purchase Req -->Define Scree Layout at document level.
is the configuration required as per a previous mail thread in the forum. However when i go to spro i am not able to see those new fields which i have added for KEY FIELD selection. Am i missing something or has anybody before done this... Could anybody guide me with the step by step process.
Regards,
Shekhar Kulkarni

Hello,
In 46C, I checked and found no user exits / BADIs for your requirement. If you are very keen of this feature, may be that you have to modify the SAP standard. Not a good option.
Regards, Murugesh AS

ME28 user exit - sy-ucomm not available

Hi experts,
I have a requirement to check sy-ucomm in the user exit EXIT_SAPLEBND_002 which is triggered by transaction ME28 - convert a planned order to purchase requisition. Immediately after pressing the release button for the purchase document the SY-UCOMM value is '%_GC 102 2'.
When the program control reaches the user-exit, SY-UCOMM is already cleared. Analysing the flow shows it is cleared by the method,
CL_GUI_CFW=>DISPATCH. This is totally the ALV way of handling things. The ALV control passes on to call the function module BAPI_PO_RELEASE which inturn calls the user exit.
The question is?? How to get the SY_UCOMM in the user exit. Has any one has ever experienced this before. Your answers are much appreciated.

Ok Guys
Sorry for my ignorance.But i think that i don't udesrtand correctly .sorry.
1-you go to ME28 and do your process (click)
2-this process pass by exit .
3-I dont understand the ALV in this case.
Can you send images of screens with process ?
I think maybe you could use assign but i need know more about it.
thanks and sorry again.

Badi & User Exit for ME21N & ME22N

Hi,
        My requirement is when a Purchase order is created using ME21n or when a line is added or changed using ME22n, the system should copy the vendors tax jurisdiction to the purchase order line items jurisdiction code. I tried badi (ME_PROCESS_PO_CUST) but could not suceed. Can any one tell me if any badi or user exit available for the same???
Thanks in Advance.

hi,
Enhancement/ Business Add-in            Description
Enhancement
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
MM06E003                                Number range and document number
MM06E004                                Control import data screens in purchase order
MM06E005                                Customer fields in purchasing document
MM06E007                                Change document for requisitions upon conversion into PO
MM06E008                                Monitoring of contr. target value in case of release orders
MM06E009                                Relevant texts for "Texts exist" indicator
MM06E010                                Field selection for vendor address
MMAL0001                                ALE source list distribution: Outbound processing
MMAL0002                                ALE source list distribution: Inbound processing
MMAL0003                                ALE purcasing info record distribution: Outbound processing
MMAL0004                                ALE purchasing info record distribution: Inbound processing
MMDA0001                                Default delivery addresses
MMFAB001                                User exit for generation of release order
MRFLB001                                Control Items for Contract Release Order
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
AMPL0001                                User subscreen for additional data on AMPL
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
M06B0001                                Role determination for purchase requisition release
M06B0002                                Changes to comm. structure for purchase requisition release
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
No.of Exits:         35
No.of BADis:         55
Arunima

User exit/BADI for Return PO item delivery Address

Hi Guyz,
We have a requirement where in when a PO item is marked as return PO item(In ME21n/ME22n/ME23n We have check box at item level) and click on enter/Check/Save, In delivery address of item details we have to populate Vendor address. By default SAP populates Plant address. If we manually give Vendor number in item details=>Delivery address tab then it populates vendor address. We want to automate this functionality.
Is there any Exit/BADI which serve this purpose.
Note: We need this functionality for few doc types(i.e PO doc type should also be available in the exit).
Any ideas could be really helpfull.
Thanks,
Vinod.

Hi,
there are some user-exit & enhancements....
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
MM06E003                                Number range and document number
MM06E004                                Control import data screens in purchase order
MM06E005                                Customer fields in purchasing document
MM06E007                                Change document for requisitions upon conversion into PO
MM06E008                                Monitoring of contr. target value in case of release orders
MM06E009                                Relevant texts for "Texts exist" indicator
MM06E010                                Field selection for vendor address
MMAL0001                                ALE source list distribution: Outbound processing
MMAL0002                                ALE source list distribution: Inbound processing
MMAL0003                                ALE purcasing info record distribution: Outbound processing
MMAL0004                                ALE purchasing info record distribution: Inbound processing
MMDA0001                                Default delivery addresses
MMFAB001                                User exit for generation of release order
MRFLB001                                Control Items for Contract Release Order
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
AMPL0001                                User subscreen for additional data on AMPL
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
M06B0001                                Role determination for purchase requisition release
M06B0002                                Changes to comm. structure for purchase requisition release
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number
Some BADI s:
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
No.of Exits:         35
No.of BADis:         55
Arunima

User exit/BADI for tracing change of User Status in IW22

Hello,
I am looking for a user exit or BADI that triggers whenever ther's a change made to User status field.
eg. changing user status to APTC(Approved to be executed)
I then need the exit/badi to trigger my workflow to send mails to list of reviewers. I can handle that but I am not able to find the suitable exit.
I have seen BADI IQS0_STATUS_MAINTAIN, but no use.
Can anyone help?

Hi..
Transaction Code - IW22                     Change PM Notification
Enhancement/ Business Add-in            Description
Enhancement
IWO10026                                User check on setting status 'Do not perform'
IWO10027                                User exit: Generate user-defined settlement rule
IWOC0001                                Create PM/SM notification: Determine reference object
IWOC0002                                PM/SM notification: Check whether status change is allowed
IWOC0003                                PM/SM authorization check of ref. object and planner group
IWOC0004                                Change single-level list editing PM/QM/SM ALV settings
Business Add-in
WOC_FL_DETERMINE                        Determine Date for Determining Installation Loc. Equi.
NOTIF_AUTHORITY_01                      Additional Authorization Checks for the Notification
IWOC_OBJECTINFO_CHNG                    Changes to Data of Object Info Screen
IWOC_LIST_TUNING                        Performance Tuning for Lists in PM/CS
IWO1_SUBSCREEN_0170                     Display Additional Data on Object Screen 0170 PhysicalSample
IQS_MASS_CHANGE                         BadI for Mass Changes to Notifications
IQS0_STATUS_MAINTAIN                    Control of Changeability of User Status
No.of Exits:          6
No.of BADis:          7
Arunima

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

User exits to update a Zfield in AUFK table for T-code KO01(Order Creation)

Hi all,
I have a custom field(zZTEST) in aufk and coas struture(zztest) in order to display in the output generated by kok5 for order.
The reason for adding in coas struture is the ALV output in kok5 uses coas structure
I know aufk table gets an entry while creating an order in ko01.
When i save the order (i.e when i succesfully create an order) i have to pass a value to aufk-zztest so that the custom field in aufk for that internal order created has an value.
I was looking at the user exits available for ko01
i found 5 user exits for ko01
Exit Name---Description
COOPA002---Customer function for master data maint. - internal
COOPA003---User-Defined Fields in the Order Master
COOPA004---Customer function: Print order master data
COOPA_01---Customer check modules for internal orders
KKAZ0001---Customer check modules for internal orders
I have written the code break-point in all the includes associated with this USER EXITS.
Out of this only only 2 includes gets triggered when i click General data and investments tab .
I have the code in both of them and the aufk tables gets updated when i save an internal order and i can see the value in kok5 output as well.
To be frank this is what i want.
But my only worry is that when we create a new internal orders we don't have any data to be filled i.e mandatory fields in General data and INvestments tab.
i.e. user can create an internal order without even going to these tabs(General data and INvestments tab) in that case the custom field doesn't get updated and as a result of that i don't see that value in KOK5 ALV output.
Let me know what can be done or is there any other way that this can be achieved or the way i approached is right or wrong or am i am missing any user exits and the system is at 4.6c.
Thanks
Venkat

Hi,
Any suggestions on this post
Thanks

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

ENHANCEMENT QPAP0001 (User Exit 'EXIT_SAPLQPAP_001

HI all,
We are Using Variant Configuration, for this we have linked MIC's to Class character, When The Inspection Lot is created the Lower & Upper Limit in the specification comes as the character Value.it does not takes in to consedration the tolerance key assigned to it. For E.g. Charater Dia has value 20, & in the Tolerance key for 20 +/- 0.10 is maintained, when the Inspection lot is created the Upper & lower Limit comes as 20-20 instead 19.9 - 20.1
I have gone through SAP Note 210658, the sample code provided in note is for "Material Specification" I have tried the same with minor code correction the specifications in the lot comes as desired i.e. specifications in the lot consider the tolerance key.
Our Requirment is of task list, in the same not EXIT for task list is also mentioned but no souce code is provided, when we are using the above program (Used for Material Specification) after doing the desired changes, & when we run in de-bugging mode it shows all the calculations are being done, but finally in the lot specification appear as the charater value ( 20-20) & in the inspection lot One first MIC comes it delete's all other MIC's assigned in the Plan.
Has any body worked on this requirment, please let me know how to do the same, & if any body has used EXIT_SAPLQPAP_001 (Enhancement QPAP0001.)Plese provide me with the soution if any one has worked on it.
Thanks & Regards
Gaurav Behl

Hi,
these are teh enhancements that r available...u need to check each of them.
IWO10026 User check on setting status 'Do not perform'
IWO10027 User exit: Generate user-defined settlement rule
IWOC0001 Create PM/SM notification: Determine reference object
IWOC0002 PM/SM notification: Check whether status change is allo
IWOC0003 PM/SM authorization check of ref. object and planner gr
IWOC0004 Change single-level list editing PM/QM/SM ALV settings
Regards,
nagaraj

User Exit / BADI for Header Text in IW21

Dear All,
I have an requirement to update a header text of IW21 (Creating Notification) with some condition, ie., Header Text should be updated with different text (some information along with entered text) depends on Notification type and Functional Location.
Is there any User Exit / Badi to do this ?
Could any one help on this regard ?
Thanks and Regards,

Hi,
Below are the exits for the Transaction Code - IW21.
Exit Name Description
IWO10026 User check on setting status 'Do not perform'
IWO10027 User exit: Generate user-defined settlement rule
IWOC0002 PM/SM notification: Check whether status change is allowed
IWOC0003 PM/SM authorization check of ref. object and planner group
IWOC0004 Change single-level list editing PM/QM/SM ALV settings
IWOC0001 Create PM/SM notification: Determine reference object
Check each which can server your purpose.
May be EXIT_SAPMIWO0_020 might suit your purpose.
Regards,
Vijay V

Dumb question about E messages generated in user exits called from dialogs

After a user enters goods receipt info in MIGO and hits POST, there is a user exit (EXIT_SAPLIE01_007) which receives a copy of the goods receipt table (xmseg) from MIGO and lets you do whatever you want before the MIGO update task is called. In other words, you're still in the MIGO dialog process.
I have successfully used this exit before to pop an editable ALV that lets the user enter custom data per line item, and then store this data in memory so it can be accessed in MB_DOCUMENT_BADI or in the equivalent XMBC exit (enhancement MB_CF001).
But here's my question.
Suppose I generate an "E" message in EXIT_SAPLIE01_007.
Will this stop the MIGO "POST" so that the update task isn't called?
And will the text of the "E" message be displayed at the bottom of the main MIGO screen (the one you hit "POST" from) ????
Edited by: David Halitsky on Feb 21, 2008 9:03 PM
Edited by: David Halitsky on Feb 21, 2008 9:04 PM

Hi David,
it seems that you will get it:
E in Status bar
+behaviour: +
PAI processing is terminated, and control returns to the current screen. All of the screen fields for which there is a FIELD or CHAIN statement are ready for input. The user must enter a new value. The system then restarts PAI processing for the screen using the new values. Error messages are not possible in POH or POV processing. Instead, a runtime error occurs.
according to help [http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbaabc35c111d1829f0000e829fbfe/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbaabc35c111d1829f0000e829fbfe/frameset.htm]
best regards,
Wojciech

How to find the structure in this user exit

My requirement is add new field to Delivery due list ALV report(VL10G).For enhance this report i will append one field(LIKP-SDABW) in this structure SHP_VL10_ITEM.This structure is not showing in the include LV50R_VIEWG05
USEREXIT_PREPARE_LAYOUT_FILL .Where i have to find this structure,and internal tables?
Please help me.
Thanks & Regards,
sairam

Hi Sairam,
Goto the program for transaction VL10G.In that u make a seach for the user-exit
USEREXIT_PREPARE_LAYOUT_FILL.Then write the logic inside tht.U will need an access key for that.
Reward points if it solves ur query or answer is helpful
Thanks
Chinmay

User Exit for Transaction QM01 & VA01

Hi experts,
I have a requirement such that the newly created QM Notification number(QMNUM) from QM01 will be exported to a memory ID and imported in transaction VA01 such that the Sales order(VBELN) will have the same value of Notification number(QMNUM). QMNUM = VBELN.
QM notification number and the Sales Order number to be created for each claim filed by a customer should be the same. This is being done in QM01. The problem is that when this is done in BDC, we cannot simply "copy" the notification number in QM01 into the sales order number of the linked Sales order that is being created.
Need a User Exit for this. Thanks.

Hi Marc,
User-exit for QM01
IWO10026 User check on setting status 'Do not perform'
IWO10027 User exit: Generate user-defined settlement rule
IWOC0001 Create PM/SM notification: Determine reference object
IWOC0002 PM/SM notification: Check whether status change is allowed
IWOC0003 PM/SM authorization check of ref. object and planner group
IWOC0004 Change single-level list editing PM/QM/SM ALV settings
User-exit for VA01
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
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001 Activating Sourcing Subitem Quantity Propagation
plz reward points if helpful or if it solves ur query.
Thanks
Chinmay

ALV + User Exit

Similar Messages

Maybe you are looking for