Output type in user exit USEREXIT_SAVE_DOCUMENT in VL02N

Hello all, i am using the user exit USEREXIT_SAVE_DOCUMENT in include MV50AFZ1 to process some information when delivery is saved in VL02N. The problem is i have to limit this to a certain output type. There are 3 different ones that the user can choose from and i have to be able to know which one they did.
Does anyone know what table is used to store this information that i can read in the user exit? Or is there a FM to get that information?
Thanks in advance for your help.
-- David

Hi
Check This table T685B and this view VN_T685B for output ..
Regards.

Similar Messages

Purchase order output determination thru User exit

Hi,
We are trying to find a way to determine the output for PO while creation (me21n) or modification (me22n).
We do not want to maintain output condition records for each fax/print/email etc..cases.
Can we do below thru a user exit or any other method ?
While creating PO, an OA partner will be chosen, so instead of maintaining the output condition records,
- user exit can access to OA's vendor master record and read Standard Comm.Method in Address section.
- according to comm.method, the PO message should be determined..
i.e: if comm.method is Fax, then message should be sent to OA thru Fax.
can this be done thru an exit ?
Thanks and Regards,
Ocal

Hi Stefan,
The steps are as follows:
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
*4. Message Determination Schemas*
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Reward me if it helpful
ASHOK

Client Copy Error - ERROR: Type 'F' user exit with SYS_ERROR:

Hello,
We want to create a client copy from client 001 to clien 715.
The client copy test runs successfully.
The following error occurs in normal mode of client copy.
1 ETA028XClient copy from "03.11.2010" "17:12:43"
1 ETA029 System ID............................ "IS3"
1 ETA043 Target client........................ "715"
1 ETA030 R/3 Release.......................... "701"
1 ETA354   Basis Support Package..............."SAPKB70107"
1 ETA031 Host................................. "xxx"
1 ETA000 Start in background............. ....." "
1 ETA032 User................................. "SAP*"
1 ETA033 Parameter
1 ETA034 Source client........................ "001"
1 ETA188 Source client user masters............"001"
1 ETA185 Copier profile:......................."SAP_ALL"
1 ETA036 Table selection
1 ETA177 Customizing data ....................."X"
1 ETA037 With application data................ "X"
1 ETA155 Initialize and recreate......... "X"
1 ETA294 Change documents are not copied
2 ETA367XStart analysis of system "17:12:43"
3 ETA108 "/GC1/CC_EXIT_CLIENT_DELETION" executed "        0"("        0") entries copied
4 ETA114 Runtime "             0" seconds
3 ETA072 Exit program "/GC1/CC_EXIT_CLIENT_DELETION" successfully executed "17:12:53"
A2EE/SAPAPO/OM 012 "Mandant 715:" "Verbindung nicht oder fehlerhaft gepflegt:" "IS3CLNT001" " "
2 ETA102 ERROR: Type 'F' user exit with SYS_ERROR: "/SAPAPO/OM_CLNT_COPY_DOWNLOAD"
2 ETA534 "RCOD:" " 8" "SY-SUBRC:" " 0"
2 ETA191 Program ended abnormally
Can you help me?
thx
Torsten

Torsten,
Are you doing a local client copy in a SCM System. I can see it fails & is looking for SCM specific fn modules & user exits.
If yes, has a look at this notes there are some steps that needs to be done for the transactional date:
894490 - Client copy: Transactional data
And re-post it in the SCM forum: SAP Advanced Planning & Optimization (SAP APO)
- Regards, Dibya

Types of USER EXITS user for enhancement

Can any one please let me know the types of USER EXITS user for enhancement normslly used in SD module.
Thanks

Hi,
here you can find what's enhancement (overview), the steps, and exits in bw ...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
and later abap in bw may useful
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4493c4a6-0301-0010-62a2-efd6ded61e04
for general understanding of enhancement, take a look this 'Changes to the SAP Standard ' doc
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975a043b111d1896f0000e8322d00/frameset.htm
... Enhancements represent potential customer requirements that have not been developed in the standard software. Instead, the standard provides for further development of such exits at the customer site, using logic specific to the customer ...
some threads on data extraction enhancement
Enhancement
Re: User exit
Hareesh

Badi/user exit for tx vl02n

Hi,
I need to find a badi or a user exit thats triggered after pressing "save" in transaction vl02n.
Help me please.
Best regards,
Roberto.

hey
.Code SE18 is used to Identify the BADI available.
Look for the string 'CL_EXITHANDLER' in the standard program. This is a class which has a method 'GET_INSTANCE' which is used to trigger BADI's from the Standard Program. The interface parameter for this static method 'EXIT_NAME' is used to pass the BADI to the method.
Open Standard Program and do a global search 'CL_EXITHANDLER'.
SE18 > give the BADI name found through above search.
CUSTOMER_ADD_DATA > which has a method SAVE_DATA.
T.Code SE19 is used to Implement BADI.
SE19 > give the implementation name > Give the Definition name as CUSTOMER_ADD_DATA and the Short Text.
Intro.....
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
Check these links for info about badi..
BADI's
http://support.sas.com/rnd/papers/sugi30/SAP.ppt
BADI's
http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm
http://support.sas.com/rnd/papers/sugi30/SAP.ppt
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://members.aol.com/_ht_a/skarkada/sap/
http://www.ct-software.com/reportpool_frame.htm
http://www.saphelp.com/SAP_Technical.htm
http://www.kabai.com/abaps/q.htm
http://www.guidancetech.com/people/holland/sap/abap/
http://www.planetsap.com/download_abap_programs.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
http://www.esnips.com/web/BAdI
http://www.allsaplinks.com/badi.html
New to Badi
check any fo the below links. this will def help u.
http://www.allsaplinks.com/badi.html
And also download this file....
http://www.savefile.com/files.php?fid=8913854
There are other tutorials on this site...
http://sapbrain.com/Tutorials/tuto_download.html
What are BAdIs?
-> is an anticipated point of extension these points act like sockets and exist in the original source code
-> based on ABAP Objects. BAdI defines an interface that can be implemented by BAdI-implementations that are transport objects of their own
->Important! There are 2 roles: Enhancement Option-provider & Implementer.
-> In the above context, Enhancement Implementation can be done only if option (hook) is provided by the Option-provider. In simple words there are no implicit BAdIs.
Note: In the following slides, Definitions are created so as to understand the method of BAdI definition & for example purpose. As stated above this is the role of Enhancement Option-Provider.
Classic BAdIs already exist since SAP Release 4.6
BAdIs have been Re-implemented in ECC7.0 under the new Enhancement Framework & Switch Framework
Classic BAdIs
To understand what a powerful pattern a BAdI is, we will now define & then implement a BAdI
BADI Class is created automatically.
The various options are described below in detail:
1. Enhanceable: Enhanceability of filter types can only be specified for filter-dependent BADI definitions under very special conditions. For example, the domain belonging to the filter type must be linked with a value table that is of the type E or G. A BADI implementation can then be created in one step by creating a new filter value that is automatically entered into the value table at save and also copied into the transport order of the BADI implementation. In addition, it is also possible to create a new filter value and, at the same time, a BADI implementation with the same name. Naturally, you can also specify existing filter values.
You should select this feature if there is a prerequisite that a new filter value is created together with a new BADI implementation - that is, that BADI implementations are not created solely with existing filter values, although this, too, is possible.
2. Multiple-Use
3. Filter-Dependent
Instance Methods can access all of the attributes of a class and can trigger all events of a class. Static Methods can only access static attributes and static events.
Exceptions:
Events:
Events can be defined in classes or in interfaces. Corresponding methods can trigger these events with the RAISE EVENT statement. Each class (or interface) that is going to handle the corresponding event must implement a relevant handler method, and register it using the SET HANDLER statement. When an event occurs, the system calls all of the handler methods registered for that event.
Like method definitions, events have a parameter interface. The only difference is that events may only have EXPORTING parameters.
BADI : Businees Add IN's
Business Add-Ins are SAP enhancement technique based on ABAP Objects.
Where the SAP standard program is not going to fullfill the client requirement , we are going to add our own program to SAP standard program, without changing the standard prog.
Each Business Add-In has
at least one Business Add-In definition
a Business Add-In interface
a Business Add-In class that implements the interface
Each BADI has two different Views.
1.Definition view
2.Implementation view
T.C for BADI Definition is SE18.
T.C for BADI Implementation is SE19.
There are multiple ways of searching for BADI.
Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE
Finding BADI Using SQL Trace (TCODE-ST05).
Finding BADI Using Repository Information System (TCODE- SE84).
1. Go to the Transaction, for which we want to find the BADI, take the example of Transaction VD02. Click on System->Status. Double click on the program name. Once inside the program search for CL_EXITHANDLER=>GET_INSTANCE.
Make sure the radio button In main program is checked. A list of all the programs with call to the BADIs will be listed.
The export parameter EXIT_NAME for the method GET_INSTANCE of class CL_EXITHANDLER will have the user exit assigned to it. The changing parameter INSTANCE will have the interface assigned to it. Double click on the method to enter the source code.Definition of Instance would give you the Interface name.
2. Start transaction ST05 (Performance Analysis).
Set flag field "Buffer trace"
Remark: We need to trace also the buffer calls, because BADI database tables are buffered. (Especially view V_EXT_IMP and V_EXT_ACT)
Push the button "Activate Trace". Start transaction VA02 in a new GUI session. Go back to the Performance trace session.
Push the button "Deactivate Trace".
Push the button "Display Trace".
The popup screen "Set Restrictions for Displaying Trace" appears.
Now, filter the trace on Objects:
V_EXT_IMP
V_EXT_ACT
Push button "Multiple selections" button behind field Objects
Fill: V_EXT_IMP and V_EXT_ACT
All the interface class names of view V_EXT_IMP start with IF_EX_. This is the standard SAP prefix for BADI class interfaces. The BADI name is after the IF_EX_.
So the BADI name of IF_EX_CUSTOMER_ADD_DATA is CUSTOMER_ADD_DATA
3. Go to Maintain Transaction (TCODE- SE93).
Enter the Transaction VD02 for which you want to find BADI.
Click on the Display push buttons.
Get the Package Name. (Package VS in this case)
Go to TCode: SE84->Enhancements->Business Add-inns->Definition
Enter the Package Name and Execute.
Here you get a list of all the Enhancement BADIs for the given package MB.
Have a look at http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm
http://support.sas.com/rnd/papers/sugi30/SAP.ppt
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://members.aol.com/_ht_a/skarkada/sap/
http://www.ct-software.com/reportpool_frame.htm
http://www.saphelp.com/SAP_Technical.htm
http://www.kabai.com/abaps/q.htm
http://www.guidancetech.com/people/holland/sap/abap/
http://www.planetsap.com/download_abap_programs.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
How to develop BADI
Rewards if useful.

PO document types and user exit

Hi freinds
There is a typical issue I have. The Document types required by my client is huge. I want to bring them down. Is there any way it can be done using user exits. If yes how to do the same.
Regards
Eldee

Hi Dev,
To reduce the document types you have to delete those entries from customizing tables you need not have to use user exit for that
Which document types you want to reduce?
BR
Diwakar

Message type in user exit

Hi,All,
In Tcode AS01,I use user exit AISA0001 to check the value of ANLA-SERNR,if the value did not fit the rule,raised an error through "message ... type 'E' or message exxx with ...", now the problem occured, although I enter new value for the field SERNR,in the user exit, I got the old value,It seemed that the PAI did not trigged again.
Does anybody can help?
Thanks very much!
Pole
Message was edited by: gw gw

Hi there,
Not sure if this will help as im not sure at what point the user exit is called, but there is a method to access field values available in the main SAP program from within the user exit using field symbols. The code for this is as follows:
field symbol declaration
FIELD-SYMBOLS: <status>.
Assign value of variable from calling prog to field
symbol
ASSIGN ('(SAPMM06E)RM06E-BSART') TO <status>.
The value will now be contained in the field symbol
<status> which can be used as usual i.e.
message exxx with <status>.
Hope this helps
regards
Mart

How to write include in user exit userexit_save_document

when i am trying to insert a inlcude in the exit userexit_save_document. i am getting error.
i ahve written a statement 'include 'Zabcd' inside the user exit.
doubl clicked on the include->system asked to create a new include-> opted for yes-> an editor came inc hange mode-> i ahve witten the statements form test. endform.
when i am trying to activate my include 'Zabcd' ,, ia m getting an error. "the corresponding form should have an edform"
i cant proceed , it is beyond my imagination
can some help me out of this situation.
Best Regards
Amarender Reddy B

So you have
FORM userexit_save_document.
INCLUDE zabcd.
ENDFORM.
And your include contains
FORM myform.
ENDFORM.
Include just inserts source code at the INCLUDE point, so effectively you've written:
FORM userexit_save_document.
FORM myform.
ENDFORM.
ENDFORM.
Now do you see the problem?
matt

Output type doens't exits

When I create a goods issue in shipment supposedly there should be an output type ZZZ1 defined in the delivery document. But it doesn't exist.
Output type is properly assigned to Delivery type. Anything else that I missed?
Points will be given . THank you!

Hi,
Please check whether the output type is linked to the output procedure which is linked to the delivery type. This may be missing.
Check the delivery type for the output procedure say V10000
Now go to this procedure in NACE ina pplication V2 and then check if your output type is available or not.
If not please include this.
Now after maintaining your condition records, check the transaction. It should work fine.
Hope this helps.
Pls reward if this helps.

Some Quries on User Exit For VL02N

Hi All,
Does anyone knows how to obtain what Output Type the user has selected for a particular Outbound Delivery document before that document is saved/post goods issue?? I've tried using the user exit 'MV50AFZ1' but i couldnt seem to get any data on NAST.
Thanks in advance and Best Regards.

try to get output type based on the delivery Type not based on the delivery Number ?
comming to ur probs : SAP will update NAST with delivery numner + output type ,but u are going to create delivery ? So u may not get from NAST table.
Regards
Prabhu

User Exit for "Serial Number" in VL02N before "Post Goods Issue".

Hi Friends,
Current Scenario:
End User has to scan "Serial Number" for Main Unit (Item CAtegory - TAN) while doing "Outbound Delivery". But, sometimes he forget to do this activity of scanning "Serial Number". And do "Post Goods Issue" without "Serial Number".
Requirement:
When End user will click "Post Goods Issue", system should first check "Serial Number" for Main Unit (Item Category - TAN). If he will not find "Serial Number" then system should give warning message for "Serial Number".
Please suggest the suitable "User Exit" that can be used for above purpose.
Or if there is any other way then let us know.
Regards
Siva

hi
check is there any standard User Exit available for VL02N. apply your logic and activate

User exit for four quaters of a year

Hi All,
I need to write an user exit to fetch the Quater1(3 months) to Quater4 from a Calyear.
If the user enters 2008 then i want to get the sales for the 4 quaters for an year in separate columns. I think of creating 4 restrcited KFs with the sales KF and restrict it with the four user exit variables which we fetch three months for each quaters.
Please help me to write an user exit.
Thanks,
Pallavi

Hi,
Do you have Fiscal year in cube. If you have year then you can go with the below code.
In that case create a variable for calmonth with select option and type as user exit. Then use the below code.
LOOP AT lt_var_range INTO ls_var_range WHERE vnam = 'YEARVARIABLE'.
Concatenate ls_var_range-low '01' INTO ls_range-low.
Concatenate ls_var_range-low '03' INTO ls_range-high.
ls_range-sign = 'I'.
ls_range-opt = 'BT'.
APPEND ls_range TO et_range.
CLEAR ls_range.
ENDLOOP.
If you have only calmonth in cube get the input any one of the calmonth and using below code.
LOOP AT lt_var_range INTO ls_var_range WHERE vnam = 'CALMONTHUSER ENTRY VARIABLE'.
Concatenate ls_var_range-low+0(4) '01' INTO ls_range-low.
Concatenate ls_var_range-low+0(4) '03' INTO ls_range-high.
ls_range-sign = 'I'.
ls_range-opt = 'BT'.
APPEND ls_range TO et_range.
CLEAR ls_range.
ENDLOOP.
Use this to restrict the calmonth in first key figure. In 2nd,3rd and 4th key figures use offset for low and high value and you can get the output as you expected.
Hope this helps
Regards
Akhan
Edited by: Akhan_BI on Sep 5, 2009 12:30 AM

IDOC triggerred by which Output type?

Hi Gurus,
My requirement is to add a new segment in ORDERS05 and populate the values int he Zsegment based on the output type selected.
I am using same user-exit to populate but i am not sure how to find the output type which user selected.
How to find the Output type in FM IDOC_OUTPUT_ORDERS?
Thanks GIRI

Hi Giri,
There is no direct provision to Read the Output type from the function module. But you can do this with the following Options.
1) Find user Exit in PO Transaction while issuing the output. Export the output type from there and import it in your IDOC function module and then do you logic.
2) Since you are going to Specify the Basic type and Extension in the partner profile you no need to worry about other partners. This extension will not trigger to the other partner and other output types.
Let me know if you need any further details.
Thanks,
Venkat

User Exits for Inbound Process

hi all
can any one please give some example user exits in inbound process and explain the omportance of user exits
Thank you,
Swapna

hi
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
Types of User exits
1. Menu Exits
2.Function exits
3.Table exits
4.Screen exits
5.Keyword exits
6.Field exits.
also refer to the links below.. can get more info on user exits
list of user exits
http://www.planetsap.com/userexit_main_page.htm
can also get the list of user exits thru..
Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
User Exits Notes:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
below are some of the useful invound and outbound userexits
IDoc Inbound User Exits
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
 ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
 ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
 ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
 ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
 ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
 ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
 ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
 MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
 MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
 MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
 MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
 VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
 VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
 VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
 VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
 VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
 VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
 VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
 VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
 LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
 MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
 V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
 V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
 V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
 V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
 V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
 V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
 CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
 CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
 VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
 VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
 VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
 VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
 F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
 F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
 F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
 F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
 F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
 F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
 F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
 FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
 FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
 VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
 VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
 VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
 RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
 RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
 RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
 MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
 MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
 FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
 FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
 FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
 FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
 FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
 FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
 FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
 FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
 FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
 FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
 MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
 MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
 MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
 MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
 MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
 WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
 MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
 SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
 MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
 MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
 VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
 VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
 VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
 VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
 VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
 VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
 VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
 VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
 VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
 VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
 VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
 MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
 MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
 MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
 MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
 VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
 VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
 VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
 VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
 VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
 VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
 VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
 VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
 VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
 VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
 VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
 WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
 MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
 MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
 MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
 WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
 SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
 SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
 WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
 FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
 FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
 VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
 VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
 VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
 VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
 VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
 VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
 VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
 VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
 VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
 VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
 VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
 VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
 VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
 VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
 VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
 VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
 VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
 VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
 VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
 VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
 V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
 V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
 V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
 V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
 V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
 V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
 V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
 V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
 V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
 V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
 V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
 V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
 V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
 MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
 MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
 BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
 BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
 V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
 V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
 V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
 V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
 V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
 V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
 V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
 V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
 V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
 MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
 MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
 MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
 MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
 MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
 MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
 MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
 WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
 WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
 WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
 WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
 WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
 WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
 WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
 WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
 WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
 WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
 WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
 WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
 WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
 WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
IDoc Outbound User Exits
72. ACCONF
Confirmation of IDoc processing from the application
 ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73. ACLPAY
Accounting: Inbound invoice
 ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
 ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
 ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
 ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74. ACPJMM
Posting in accounting from materials management
 ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
 ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75. ARTMAS
Create and change of material master (Retail)
 MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76. BLAORD
Purchasing contracts
 MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
 MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77. BLAREL
Purchasing contracts
 MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78. COND_A
Conditions: master data for price determination
 VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
 VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79. CREMAS
Distribute vendor master
 VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80. DEBMAS
Customer master
 VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81. DELPKB
KANBAN call
 MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
 MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82. DIRDEB
Preauthorized withdrawal
 FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83. DOCMAS
Master document
 CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
 CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84. DOLMAS
Document-object links
 CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
 CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85. FIDCC1
Send entire FI documents (user exit 003/4)
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
 F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
 F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86. FIDCC2
Send entire FI documents (user exit 005/6)
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
 F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
 F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87. FIDCMT
Sending single items for FI-GL
 F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88. FIPAYM
Payment data
 FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
 FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
 FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
 FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
 FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90. GSVERF
Cred. memo procedure
 MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91. HRMD_A
HR: Master data and organizational data (appl. system)
 RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
 RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
 RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92. INFREC
Purchasing info record
 MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93. INVOIC
Invoice / Billing document
 LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
 LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
 LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
 LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94. KANBAN
KANBAN call
 MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
 MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95. LIKOND
Listing conditions
 WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96. MATMAS
Material Master
 MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97. ORDCHG
Purchase order/order change
 MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98. ORDERS
Purchase order / order
 MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99. ORDRSP
Purchase order / order confirmation
 MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
 MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
 MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
 SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
 SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
 SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
 SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
 SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
 SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
 SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
 SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
 WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
 WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100. PAYEXT
Extended payment order
 FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
 FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
 FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
 FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101. PICKSD
Picking data confirmation to customer delivery
 VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102. PRDCAT
Product Catalog
 WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103. PRDPOS
Product catalog item
 WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104. PRICAT
Price list / catalog
 VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
 VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
 VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105. PROACT
Stock and sales data
 WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106. REMADV
Payment advice
 FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107. REQOTE
Inquiry
 VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
 VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
 VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
 VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
 VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
 VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
 VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
 VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108. SRCLST
Source List
 MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109. SRVMAS
Master data service master
 BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
 BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110. SYPART
Partner profiles
 SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
 SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
 SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
 SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
 SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
 SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
 SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111. TPSDLS
Shipping planning system: Transfer delivery
 V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
 V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
 V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
 V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
 V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
 V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
 V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112. WBBDLD
Assortment list: Material data
 WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113. WMCATO
Reversal/Reversal request for transfer order
 MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114. WMINVE
Inventory count input
 MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115. WMRREF
Release reference number
 MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116. WMTORD
Transfer order
 MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117. WP_EAN
POS interface: Upload / Download EAN assignments
 WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118. WP_PER
POS interface: Upload / Download person data
 WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
 WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119. WP_PLU
POS interface: Upload / Download material master
 WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
 WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120. WPDCUR
POS interface: Download exchange rates
 WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121. WPDNAC
POS interface: Download products
 WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
 WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122. WPDSET
POS interface: Download set assignments
 WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123. WPDSET
POS interface: Download set assignments
 WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124. WPDTAX
POS interface: Download tax rates
 WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125. WPDWGR
POS interface: Download material group master
 WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
 WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126. WPUBON
POS interface: Upload sales documents (compressed)
 WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127. WTADDI
Additionals
 WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128. WTADDI_CVB1
Additionals w/o 06
 WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
General IDoc User Exits
 ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
 ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
 BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
 KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
 KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
===
User exits for Pricing.
1.USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
2.USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
3.USEREXIT_FIELD_MODIFICATION
4.USEREXIT_FIELD_MODIFIC_KZWI
5.USEREXIT_FIELD_MODIFIC_KOPF
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
====
Reward if USeful
Thanx & regards
Naren..

User Exit During Goods Issue

T Code is :VL02N
program :SAPMV50A
Package VL.
The goods issue of a consignment fill up order (ZOCF), should the material have been issued from a plant other than the customers preferred plant (held on the Shipping Tab of the Sales Area Data on the customer master record) we then perform a follow on goods movement (plant to plant transfer posting) that will post the stock to the correct plant and stock type.
witch Function module i have to use kindly help me out.
Thanks & Regards
Kavitha

Hi,
try this BADI
it will tigger when u do PGI only.

LE_SHP_GOODSMOVEMENT
Please check this user exits avalaible for VL02N
V50PSTAT - Delivery: Item Status Calculation
V50Q0001 - Delivery Monitor: User Exits for Filling Display Fields
V50R0001 - Collective processing for delivery creation
V50R0002 - Collective processing for delivery creation
V50R0004 - Calculation of Stock for POs for Shipping Due Date List
V50S0001 - User Exits for Delivery Processing
V53C0001 - Rough workload calculation in time per item
V53C0002 - W&S: RWE enhancement - shipping material type/time slot
V53W0001 - User exits for creating picking waves
VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)
V02V0001 - Sales area determination for stock transport order
V02V0002 - User exit for storage location determination
V02V0003 - User exit for gate + matl staging area determination (headr)
V02V0004 - User Exit for Staging Area Determination (Item)
rEGARDS

Output type in user exit USEREXIT_SAVE_DOCUMENT in VL02N

Similar Messages

Maybe you are looking for