User Exit in Credit Managment - Urgent
Dear All,
One of our customers want to use option of Oldest of open Items overdue in the Automatic credit check.
WIth the only difference that he does not want the field " Days oldestItem ( Table Name V_T691F / Field Name OITOL)" within IMG. He wants that field to be available in the customer master.
In order to achieve this we have thought of following solution --
1. Add new field in the customer master using screen exit in " General Data / Company Code" Tab for capturing " Days oldestItem ( Table Name V_T691F / Field Name OITOL)"
2. Use user exit LVKMPFZ1. Build following logic into the same.
Refer table for Open Line Item (Table BSID)
Due date = Document Date (Field BLDAT) + Days 1 (Field ZBD1T)
If, Due date + Field in Customer Master added through screen exit (in no. of days) < Today, Credit Check will be active & depending on the setting in Automatic Credit Check, we can get either warning message or error
Please check if above logic is OK. If you wish to suggest any changes, you are most welcome to do so. Points will be rewarded for any valuable suggestion. But please hurry up. Unfortunately we do not have much time.
Regards
Nikhil
Hi,
TRY THIS PROGRAM MAY BE HELP U,
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& Tables
TABLES : tstc, "SAP Transaction Codes
tadir, "Directory of Repository Objects
modsapt, "SAP Enhancements - Short Texts
modact, "Modifications
trdir, "System table TRDIR
tfdir, "Function Module
enlfdir, "Additional Attributes for Function Modules
tstct. "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir
WHERE pgmid = 'R3TR'
AND object = 'PROG'
AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
SELECT SINGLE * FROM trdir
WHERE name = tstc-pgmna.
IF trdir-subc EQ 'F'.
SELECT SINGLE * FROM tfdir
WHERE pname = tstc-pgmna.
SELECT SINGLE * FROM enlfdir
WHERE funcname = tfdir-funcname.
SELECT SINGLE * FROM tadir
WHERE pgmid = 'R3TR'
AND object = 'FUGR'
AND obj_name = enlfdir-area.
MOVE : tadir-devclass TO v_devclass.
ENDIF.
ENDIF.
Find SAP Modifactions
SELECT * FROM tadir
INTO TABLE jtab
WHERE pgmid = 'R3TR'
AND object = 'SMOD'
AND devclass = v_devclass.
SELECT SINGLE * FROM tstct
WHERE sprsl EQ sy-langu
AND tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
WRITE:/(95) sy-uline.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
WRITE:/(95) sy-uline.
LOOP AT jtab.
SELECT SINGLE * FROM modsapt
WHERE sprsl = sy-langu AND
name = jtab-obj_name.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
WRITE:/1 sy-vline,
2 jtab-obj_name HOTSPOT ON,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
ENDLOOP.
WRITE:/(95) sy-uline.
DESCRIBE TABLE jtab.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No of Exits:' , sy-tfill.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'No User Exit exists'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
Thanksmate,
Reward if helpful,
Phani
Similar Messages
-
Please give me User Exit for Credit Release -Urgent-
Please send the User Exit for Credit release
Mr.Goutam
My request is that dont continue your questions in one thread.
Two options are available for you to post in this forum
a) First list out what are all your requirements and ask this forum in which specific area you have doubts. If all your questions are answered, award points who have given the solution for you.
b) Post question one by one and wherever your questions are answered, close the thread and reward points to the members.
If you take this thread, Initially you raised a question on Credit Limit and many of us have answered your question and the thread should have been closed. But questions are continuing with same subject but with different topics which I feel is WRONG.
Hope you understand now.
Thanks
G. Lakshmipathi -
User Exit for credit management at confirmed quantity in sales order
Dear All ,
kinldy tell how to define a user exit and where i can write for credit check to be done to the confirmed quantity in the sales order .
Also pls tell me that how to define the user exit and attach to customer reserve field in the customising for automatic credit control .
regards
Baranidharan RamarHi
The following is the information from the sap documentation...you can also refer from IMG - SD - System modification - userexit - userexit for credit check
Credit Check
If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3
User exit for availability check
User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
Thanks,
Ravi -
User exit for Credit Management check on SD document
Is it possible to enhance and put in some custom logic during CREDIT check on SD documents?
Can some one tell me which User exit can I used?Hi,
Yes, I think you can do. Here is what SAP help says....
If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3
User exit for availability check
User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
Hope this helps
Thanks
Mukund S -
Hi all,
I am looking out for user exits at credit check t-code VKM3
For customized order type, delivery gets created automatically after we save the order (as Immediate delivery (X) is present in the sales doc type in delivery section)
But this order should not save if there is a credit check or if there is a stock deficit.
How can i check availabilty as well as credit check simultaneously.
If stock is not available then this order should not get saved.
If credit check is active, order should not get saved.
Client wants deliveries to get created the moment we release order from credit check in VKM3
Please advice
SunilHello Sunil,
You do not need a USEREXT for this. For the relevant document type, to to VOV8 and in the shipping tab, there is a filed delivery block, in this you can select credit check. Whenever the user creates a so with this doc type, based on the credit check, system will block the doc for delivery and the same can be released via VKM3.
Let me know if this was useful.
Regards,
Sanjay -
Hi Friends,
I got user exits for credit check but I could not understand how to implement these rather these are not found in system (CMOD & SMOD tcodes) We have ECC6.0. These are the following.
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3
Any help how to implement these is appriciable.
Regards,
Rajesh VasudevaHi Rajesh,
You can make use of the implicit enhancement, where in you can add code to any standard program either at the start or after the last line in a form or function module.
Refer the URL
http://help.sap.com/saphelp_nw04s/helpdata/en/8f/f2e540f8648431e10000000a1550b0/frameset.htm
for more info on Enhancement Framework.
Hope this helps you.
Reg
Praveen Alex Luke. -
Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
SIMPLE CREDIT CHECK : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1,00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options : A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.
A) Credit Checking Groups : Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be u201800012u2019. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etcu2026)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999
American Express Credit Expires in 30 days
340000 349999
370000 379999
Discover Card Credit Expires in 30 days
601100 601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter u201C03u201D in the column labeled u201CPTu201D for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence u201CA001u201D
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu -
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 -
Complete End User transactions of Credit management and Cash Remittance
Hi All
Can any one please Guide me on what are all transactions the end users need to perform in the below areas -
1 - Collections
2 - Credit Management
2 - Cash Remittance
4 - Tax Processing
I have to give the trainings on these areas and these are very much new areas to me
Appreciate your Quick Response
Aadi
Moderator
http://help.sap.com/saphelp_erp60_sp/helpdata/en/d2/9202b646f111d189430000e8323c4f/frameset.htmHi,
You got this message because you set check for "Permitted aging of A/R summary" on OVA8. And you also chose to create AR summary on table T000CM.
You can do one of following:
1. on OVA8, make "permitted days and monthes" blank.
2. delelte entries in table T000CM
3. Make "permitted days and monthes" longer, and delete and re-create AR summary by FCV2 and FCV1.
Hope it helps. -
User Exit in Credit Card Authorization
Is there a user exit that can be invoked whenever a Credit Card Authorization is performed?
hi
refer to the link below.. list of user exits
http://www.easymarketplace.de/userexit.php
http://www.planetsap.com/userexit_main_page.htm
====================
User Exit structural authorizations: http://help.sap.com/erp2005_ehp_02/helpdata/en/17/8b7f409cd50a1ae10000000a155106/frameset.htm
Chk Authorizations: http://help.sap.com/erp2005_ehp_02/helpdata/en/2b/fe26406f2c185de10000000a1550b0/frameset.htm
http://help.sap.com/erp2005_ehp_02/helpdata/en/41/f7c8380ef2c707e10000000a11402f/frameset.htm
http://help.sap.com/erp2005_ehp_02/helpdata/en/fc/75e43a744ebe14e10000000a11402f/frameset.htm
http://help.sap.com/erp2005_ehp_02/helpdata/en/51/778838d4687e0ce10000009b38f8cf/frameset.htm
http://help.sap.com/erp2005_ehp_02/helpdata/en/46/51f0b794b85e40e10000000a11466f/frameset.htm
Reward if Useful
Thanx & regards..
Naren.. -
User Exit for warehouse management - transfer order sorting
Hi,
I want to sort transfer order of warehouse management by user exit, which user exit I can use?
Kindly please advise.
RegardsHi,
I worked on the same object.
For sorting you have to place a button in the standard transaction,
I found some screen exits but they are not working.
Finally I developed the total customized transaction for that standard LM45.
If you have any doubts let me know. -
User Exit related Credit check
HI All,
I have createed one sales oreder, initailly credit check status is NOT APPROVED, i have released SO manually from t-code VKM3 . then the status has changed to APPROVED.
if change the sales order through VA02 on the same day status is not changes(still APPROVED status, this is fine),
is we change next day(from creation date) credit status is NOT approved..
what user exit is triggering the second block to happen.
we are chnaging bulk sales order, which iare comnig frm Legacy system.
Regards,
DSKThank you,
Can u explain some more detail?
How do i check whether VL10C triggers this exit in OVA8?
Actually , it is triggering for VL01N or VL02N but not triggering for VL10c.
And Will there be chances like , it triggers sometimes and not sometimes based on any condition?
Regards
Ramakrishna L -
Hi all,
Can anyone give the user exit name for credit check.Hello,
Following exits are available:
LVKMPFZ1
LVKMPFZ2
LVKMPFZ3
Regards,
John. -
User exit for sales order-Urgent
How Developed a User Exit, which will be triggered when a Sales Order is changed manually. This user exit will check the requested delivery date and update VBKD-BSARK field.
Pls help me how to do it....
Pts will be rewarded.....Hi,
The following exits trigger during VA01 creation:
EXIT_SAPMV45A_002 and
EXIT_SAPMV45A_003
Check this include MV45AFZZ also.
Regards,
Satish -
User Exit in Contract -Very Urgent
Dear Experts,
We are using User Exit "M06E0005 - Role determination for release of purchasing documents" for some enhancement of release strategy for purchasing docs.
It is working fine for PO but in case of contract the exit is not firing. We wrote to SAP Service, They told that this user exit is not currently being supported in case of contract. I really have doubt in their comment as SAP documentation for the user exit is telling different things.
Can anybody used/experienced the same exit or any other exit for enhancement of release strategy for contract?
Please dont send the list of MM user exits, I need a specific answere.
Full points will be awarded for explanatory replies.
Regards,
SantoshHii..
It is better to use these BADIs to enhance MIGO..
MB_MIGO_BADI
MB_MIGO_ITEM_BADI
Check the Documentation of these BADIs in SE18
Implement the BADI in SE19.
<b>reward if Helpful</b>
Maybe you are looking for
-
I have tried downloading on my new iMac and nothing happens. Why?
I went to the page for downloading, pressed the download icon and waited, but nothing happened. I tried this several times and still nothing happened.
-
PSE 10 w OS 10.9.2 Lost photo folder.
I worked on 10-15 photos. imported from iphoto, saved somewhere ??? I believe I know the folder name but it doesn't show anywhere on the computer. am I going nuts? Been using this program for years. must have save them in a very special place. A
-
Reading Podcasts in reverse order
Hello Is there an issue to read Podcasts in reverse oder with iPod nano ? Thank's
-
Any way to increase form entered fonts over 72pt?
I need to create forms where someone can enter a code which will be entered/printed at 125-250 pt. Does this come down to the type of font? I've had no luck with Opentype or Truetypes, but in my research people claimed they could. If I enter a value
-
Won't Let me Set up iCloud Email
I am trying to set up an @me.com account with iCloud, but it won't let me. When I try it on Mac, it won't create, it will go back to the "Choosing your email" page, and when I do it on iOS, it says "There was a problem turning on your email, try agai