Spool request creation user exit
Hi Experts,
I need to do some action every time, when spool request is created. Is there any standard user exit or badi, or do I need to modify standard program?
Best regards,
Jirka F.
For checking user exit - SMOD, you need to activate this exit via CMOD
For Badi - SE18 to check & SE19 to implement
Take the help of your abaper, give him / her your logic.
Hope the above answers your query.
Regards,
Vivek
Similar Messages
-
Sales Order Creation User Exit
Hi,
during the creation of Sales Order via VA01, I need to perform some checks and update certain customized table if the Sales Order is blocked based on the Risk Category that was setup.
Does anyone know how to tell that a SO is going to be blocked in the user exit? Or is there any function module that i can used in the user exit to check whether the SO is going to be blocked?
Thanks and regards,
NormanHi,
Finding the risk category will give you the correct status of sales order being created, i.e. if it will be blocked or not. The risk category you define through customer and sales area. So check these values and you will get the correct status. This is what you can do before creating a sales order. Check for the required values in the back ground and later work as per your logic.
Hope this clarifies your doubt. Let me know if you need more information.
Thanks,
P. Anurag -
[Request] Special user-exit we need during creating purchase order
Hi, Gurus!
We need to make specific User-Exit during creating Purchase order.
When user creates/change a PO document (ME21N/22N), SAP has to check the u2018CUSTOMERu2019 filed whether it is BLANK or NOT in Delivery Address tab at ITEM LEVEL.
If there is no value in that field, system will automatically input right value with useru2019s business logic.
Thatu2019s what we want to implement in the future.
If you have any solution or recommendation for this, Please help us.
I really appreciate your help in advance.
Best Rgds;
IanFor checking user exit - SMOD, you need to activate this exit via CMOD
For Badi - SE18 to check & SE19 to implement
Take the help of your abaper, give him / her your logic.
Hope the above answers your query.
Regards,
Vivek -
Request for User Exit or BADIs for outgoing posting block in F-53
Dear Gurus,
Can somebody advice me which user exit or BADIs to use for the below scenario:
My users is using more than one alternative payee for their invoices, therefore when they use F-53 to clear open item, they always accidentally do multiple payment for document no. with different alternative payee. Worst case is that the posting go through! But when they print out the form, its too late and they had to do reversal.
I like to enforce a block so that if the alternative payee is different across the document no. selected, they cannot post.
Desperately,
Belinda
Edited by: Belinda Lee on Jun 3, 2008 5:34 PMHello,
You can use Business Transaction Event (BTE) . You should use 00001120 events.
You must do some customizing in FIBF.
Regards,
Burak -
Maximum number of spool requests per user
Hello,
I realise this question is a bit off-topic....
We are experiencing problems with users that are creating 5000+ output requests in one time. As you can imagine, this is causing a lot of problems. Is there a possibility to limit the number of output requests per user?
Pascal Ottenssend them an email with a CC to their superiors
-
How may spool request can I create in the backend?...
Hi Experts,
How may spool request can I create in the backend? If yes, is there anywhere in the system can I set this value to increase number of spool request per user.
Is there any condition which can prevent me create a new spool request?
Yes all of the answer above is answered, so is there any offfical document from SAP states them.
Thanks!
- Anthony-Thx for the feedback. But, in fact, what was the real issue, originally?
I forgot to inform you of that:
1) [Note 193638 - Calculating spool number from file names as of 4.0A|http://service.sap.com/sap/support/notes/193638] (indicates the algorithm of UNIX file names). This note also indicates "For Release 4.0A, the maximum spool number has been increased from 99000 to 2000000000. The maximum number of output requests per spool request has been increased to 32767 as well."
2) I think I forgot one of your initial questions:
> Is there any condition which can prevent me create a new spool request?
By default, SAP tries to append pages to existing spools with same characteristics. If they are always different, a new spool request is always created. So, you may change some characteristics so that they are identical and SAP will reuse existing spools. See rules in [Note 85318 appending documents to existing spool requests|http://service.sap.com/sap/support/notes/85318]. -
Hello experts,
I want to get the spool request date corresponding to the spool request number from a table. Can you please tell me from where i can get the spool request date??? After search i got that table TSP01 contains the spool request number/id. But how and where to use it exactly i dont know.
Thanks!!Hi,
TSP01-RQCRETIME field is having concatenation of Date and Time.
TSP01-RQCRETIME(8) specifies the spool request creation datae and
TSP01-RQCRETIME+8(8) will give the spool request created time.
Thanks,
Renuka S. -
User-exit EXIT_SAPLSPOR_001 not executed (filter spool requests)
Hi,
The default SAP functionality provided to control the output controller functions via auth. objects S_SPO_DEV, S_SPO_ACT & S_ADMI_FCD does not do what we would like to do.
There's a user-exit available to implement some additional code: SPOOAUTH / EXIT_SAPLSPOR_001.
I've activated SPOOAUTH via CMOD and added a record in table TSPOPTIONS (AUTHORITY, value CUSTOM) which was mentioned in the documentation of the function module.
No other changes were made.
However, this user-exit is not called when I start trx. SP01.In the selection screen I choose to show all spool request from all users for a specific time period. According to the documentation this should trigger the user-exit.
Now the funpart begins:
I've debugged SP01 and found that FM RSPO_CHECK_JOB_PERMISSION contains:
IF INIT IS INITIAL.
data: v like tspoptions-value.
call function 'RSPO_OPTION_GET'
exporting
name = SPOPT_AUTH
IMPORTING
VALUE = v.
if not v is initial.
return value of v should be CUSTOM. However it is empty -> skips the user-exit.
The check in FM RSPO_OPTION_GET contains:
ALL 'RSPO_CACHE_CONTROL' ID 'AREA' FIELD 'OPTION' ID 'OP'
FIELD 'GET'
ID 'NAME'
FIELD NAME
ID 'VALUE'
FIELD V.
if sy-subrc ne 0.
perform write_trace1 using 'RSPO_OPTION_GET %s failed\n' name. "#EC NOTEXT
select single value from tspoptions into v where spoption = name.
Field NAME = AUTHORITY
Field V = empty
Return = 0 -> skips user-exit.
Have I overlooked something?
Any help would be welcome.
Kind regards,
MarkHi Mark,
Could be that the option value is being picked from cache/buffer (old value). You can restart the system and verify.
Also, after putting a break-point in FM RSPO_OPTION_GET, you can edit the value of 'v' in debugger and set it to CUSTOM, just to check whether the user-exit gets executed in this case. -
Need of User-Exit in the creation of Sales Order(VA01)
Hi,
In the creation of Sales Order, I need to Compare the Ordered Quantity and Confirmed Quantity. If the CQ is less than OQ I need to create one more line item with the same material for the rest of the quantity and send the request to Production order for the remaining quantity. For this I am unable to get the exact exit. Please help me in this regard ASAP.
Thank you.the following program are the user exit for billing.
we often use RV60AFZC and RV60AFZZ.
RV60AFZA
RV60AFZB
RV60AFZC
RV60AFZD
RV60AFZZ
RV60BFZA
For Sales order
Pricing, item addtion deletion
MV45AFZZ
First, I did not find documentation for the BADI either. But at the first glance the process of implementing it looks quite straightforward. I assume you run R/3 Enterprise (4.7). So, you should implement BADI 'BADI_SD_SALES' - this must be done in transaction SE19. In particular for the purpose of adding some additional items into sales document I would implement method SAVE_DOCUMENT_PREPARE. This method has changing table parameter FXVBAP of type VA_VBAPVB_T - it holds all the sales document items. Just add items of yours to it. Certainly, you have to fill all the appropriate fields carefully.
Hope this helps somehow.
In that case you should use USEREXIT_DOCUMENT_SAVE_PREPARE subroutine (form). As far as I remember it has no parameters. To add items to the sales document you should modify internal table XVBAP.
regards
vinod -
Hi All,
System is not creating the spool request for the background job. Two days before the job was running correctly generating the spool request. When I checked today..system is not creating the spool request..
There is no changes in the authorization profile of the user-id. Also no changes in the program were made. So what may be the possible reason for system not creating the spool. There are entries which suits the condition for the creation of spool.
Thanks in Advance....Hi,
It could be a number ranges issue, please check trx. SNRO and see if the number ranges are specified as correctly, otherwise please extend, And also check if the batch Job 'SAP_REORG_SPOOL' is running to clear the spool requests which are already being processed, Job 'SAP_REORG_SPOOL' has to run on daily basis. Hope this will solve the issue. -
User-Exits stop working in automated purchase order creation
Dear all,
we used to create sales orders with transaction VA01 and then separately call ME21N to create a purchase order.
In saving the purchase order we activated user-exit EXIT_SAPMM06E_012 to process some extra logic we need here.
Now we changed to process for SAP to automatically create the purchase order (to eventually be able to automate the entire process, including sales order creation). Ever since we did that, the user exit is not called any more!
Does anyone know why? If I manually open ME22N and save the PO, it works! We have to find a way to run the logic in the user-exit during automated PO creation just for the volume of orders.
Besides that, we're still looking for a convenient way to update PO confirmations using a BAPI or other function module.
Thanks for your help!
regards,
Johannes.Good question
User-exit may not work as the function modules [ and not ME21N ] called in the Sales Order --> Purchase Req --> Purchase Order process may not call the enjoy user-exits.
Further, this process of automated PO works on Business Obejct event trigger.
So a event is triggered [ ALECREATED ] on Sales Order Business at the time of Sales Order Creation.
This event is linked with a function module called PUR_ORDER_CREATE_VIA_SD_EVENT.
similarly for change it is PUR_ORDER_CHANGE_VIA_SD_EVENT.
If you go through the FM code, you can make out how to utilize this FM as user-exit.
However you need to make the change in this FM after copying the related function group to a Z one. And then change the event linkage accordinlgy to call the new FM.
See Business Workflow --> Events section..
If you are not sure about how to do the event linkage then ask it in BPM section...[ They will request you to get lost ...no no ..they didn't do it to me ..just kidding ]
Cheers,
Ram -
User exit for Credit Memo creation
I want to create an IDOC when the credit memo will be created.
What is the name of the user exit where I can write the IDOC generation code ?
Edited by: Alvaro Tejada Galindo on Feb 18, 2008 9:47 AMIDoc 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 -
User exit / badi in spool list display
Hi, I have a little "problem" with spool lists: I'm looking at a spool list, generated by a Z-report in a Job. This is in maintenance planning: The job executes a first step to generate with ristra20 maintenance orders. In a second step my Z-report updates the orders generated in the first step. The next morning my maintenance planners can look into the spool generated by the job... but there is no easy, modification-free way to allow my maintenance planners to just double-click on of the order numbers and to sump into the order. For that I would need a user exit / badi in the spool list display. Now, I got some questions: Is there somebody else who would be supporting a user exit / badi in spool list display? How are development requests to be send to SAP nowadays with maximum probability to get implemented? Thanks for your time, Holger
Hi Holger,
If you go to class CL_EXITHANDLER, Method GET_INSTANCE, then put a breakpoint after 'call method cl_exithandler=>get_class_name_by_interface' i.e. at line 28 'case sy-subrc'; then run your transaction again and you will get many of the user exits and badis available. It will not show you the enhancement points, but all badis etc. will be there.
Hope this helps.
Glen -
User Exit/ Badi for Changing Quant parameters during TO Creation
Hi Gurus,
Could you please guide me to advice the User Exit/Badi which can be used for changing Quant Data during TO Creation.
User Requirement: Using "Recepient Field" in MIGO as a Key Value for FIFO in WM during goods issue. Receipient is copied into TR and TO (Standard SAP Functionality). For the purpose of Stock Removal based on Receipient Value, we need to copy this value into Quant Data field named Certificate Number ("LQUA-ZEUGN").
I will highly appreciate reply from Gurus.
Regards,
Gupta MHi manish,
Use the Exit MWMTO001 for this purpose and modify the table accordingly. This will solve your problem.
Thanks,
Shibashis -
User Exit for Requested Delivery Date in Sales Order
Hi
Which user exit can be used to change Requested Delivery Date in Sales Order.
Scenario: Sales Document Type: OR has Lead Time: 7 days. System always proposes delivery date after 7 days. We need to change this Lead Time based on plant.
Thanks in advance for your support.
Regards
UmaHello,
try with USEREXIT_MOVE_FIELD_TO_VBEP or USEREXIT_SAVE_DOCUMENT_PREPARE, of program MV45AFZZ.
Hope to be useful.
Best regards,
Andrea
Maybe you are looking for
-
In Mail can I change my "To" field to From or sender
In Mail my inbox shows 3 fields "To, Subject, Date Recieved" Can I change the "to" field to from or sender. I know who the mail is to, it's always to me after all it's my mail I'm checking. I would like to know the sender so I can better decide which
-
When I tried to sync my iPod the other day, iTunes suddenly decided my computer was no longer authorized to play my purchases. Then when I authorized it, it said it was already authorized. After clicking "okay" it took me back to the original messa
-
adobe photoshop elements 4 cd is not working on my new computer can not install the programm what to do? Message was edited by: Pat Willener - removed serial number.
-
Credit Memo DFF does not contain information from the original invoice line
Hi Customer is facing issue mentioned in Note: 364999.1 Issue: Created a credit memo against the invoice and noticed that the resulting credit memo lines do not contain the DFF information from the original invoice lines. I found through Metalink tha
-
Unable to start Oracle Soa suite 10g on Windows 7
I am able install oracle soa suite 10g on Windows7 platform. But I am unable to start Oracle Soa Suite 10g. Wenever I am starting the SOA suite a new window is popping up the default color scheme of windows 7 is getting changed, but after that this w