Set Credit control status in user Exit LVKMPFZ1

Dear all
we like to set the credit control status in the above mentioned user exit. Is there a better way than
*VBUK-CMGST = 'B'.
MODIFY *VBUK.
Is there a FM, Bapi or something that can be used?
Thank you
Herbert

User Exits For Credit Checks And Risk Management
   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:
     o   LVKMPTZZ
     o   LVKMPFZ1: USER_CREDIT_CHECK1
     o   LVKMPFZ2: USER_CREDIT_CHECK2
     o   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.
   Risk Management for Receivables
Regards
Prabhu

Similar Messages

Customer Credit Balance with user exit: LVKMPFZ1

Hi SD Gurus,
Is it possible to use exit:LVKMPFZ1 with USER 1 in transaction OVA8 to be able not to check credit limit when the customer has credit balance....If possible, please advise.
Thanks
Themba

Hi,
Good evening and greetings,
In the dunning procedure, FBMP transaction code click on the Dunning Levels and inside the dunning levels there is an option under the print parameter tab to print all items...Check that box and the system would include even the credit line items lying in the customer account and that can be printed out.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

CREDIT MANAGEMENT - EXPOSURE CALCULATION USER EXIT

Hello Folks
I am looking for a solution to a peculiar problem we have in credit management.
In case of Drop Ship sales order life cycle, the system automatically creates two line items per sales order - one each for Freight and Handling Fees. these are NOT relevant to schedule line delivery, nor are they billed to the customer along with the material billing. The default update rule for credit control area concerned is 12. The system, on finding line items not relevant to schedule line delivery automatically switches from rule 12 to 18. This leads to Open Deliveries field (S067-OLIWW) being updated instead of Open Orders (S066-OEIKW) on saving the sales order.
Once the sales order is billed for the material, the system should logically display net value as zero for the open order (as the 2 lines of fees and freight are not yet billed, the order is still open). But the system considers this figure at SALES DOCUMENT HEADER level and considers the net value as the total value of the sales document (including the material that is already billed).
What I am looking for is if there is an exit available whereby the system considers only those line items whose billing status indicator is "not complete". As such, the net value should be updated to the S067-OLIKW field net of the billed items.
Please advise if there is any such user exit available. Also, is there a way to customize this? We are exploring this at our end, but would appreciate an expert advise. Right advise will be awarded with brownie points
Regards
Mandar Barve

Hi,
Actually I have got some User exits for credit checks...
LVKMPTZZ
LVKMPFZ1: USER_CREDIT_CHECK1
LVKMPFZ2: USER_CREDIT_CHECK2
LVKMPFZ3: USER_CREDIT_CHECK3
And trying with that also but looking for any other solution if it is available..
And using another Sales Document Type is not possible in this case..
Any inputs...?? anybody???
Thanks..
HP

User status or user exit

Dear Gurus,
My client requirement is
If my production order status is MSPT(Material shortage),CNF and PCNF should not be possible.Please suggest If any body come accross this situation with user exit or user status please forward the solution to [email protected] help since its very urgent in client side.
Thanks in advance
Regards,
Guna

You can select to terminate confirmation of goods movements in OPK4. Pls go to the General Individual Entry tab in OPK4 and select Termination for incorrect goods movts.
So if someone tries to confirm an order with missing parts, it will terminate the confirmation.
I hope I understood you right.
Thanks
Jagadish

Credit control procedure/user exit

Hi,
Is it possible to set credit control block for the customer who has not configured credit limit in FD32?
I looked in VOFM and in the include LVKMPFZ1 but as far as I can see these programs are started only if there are records in FD32 (table KNKK).
many thanks
Piotrek

Hello Piotrek,
Unfortnately it is not possible in the standard. You need to mainatin the credit management master data in FD32 if you want to use the credit control block functionality.
Best regards,
Lela

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

How to implement user-exit based changes for incompletion status?

Hi,
I have to implement changes to incompletion procedure using user exit. I have found the following user exit for controlling header status.
User exit in Program RV45PFZA
In this user exit you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
Please help, how to implement changes to incompletion procedure using user exit?
Regards,
Chamandeep

Dear,
Go to CMOD and enter the enhacement number there. U can find the enhancement number through table MODSAP. here u can enter the enhancement object which is in ur case is Program name. Then you can use the enchacement number in CMOD and create a project and export it.
RG,
VM

User Exits on Updating and Integrating

I was reading an old Forte v3.0 presentation on whats new in Forte v3.0.
One of the proposed features was a set of primitives for defining user exits
on updates and integrations.
I haven't seen any facility for this in Forte v3.0g though. Has this in fact been
done ? Does anyone have any information on this.
Thanks,
-Carl
Carl Schei
Technical Forte Consultant
South Africa
+27 31 3641765 (w)
email : [email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

You can use the BADI:MB_MIGO_BADI. In this badi you could check the header by using the method status and header.
Hope this solves your problem.
Regards,
Narayani

Brief about enhancements and user exits

hai,
can any one tell me what are enhancements and user exits in sap sd,
their signifcance & configuration
regards
sriram

hi,
an example of user exit
In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the Target *** Qty required and the Target *** Date for a specific customer who was not sending *** Qty Received by him.
So for that specific customer we used the search term and added the same in the Data 4 field of the IDOC under segment E1EDK09.
There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating *** Issued and then find out the difference from Target *** Qty and get *** Qty Received for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
User exits in SD
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Pl reward if helpful.
Thanks
Sadhu Kishore

Error Message in user-exit EXIT_SAPLRRS0_001 in Query

Hi,
ABAP BW Guru's
I got an ABAP type problem with RANGE numeric variables in EXIT_SAPLRRS0_001.
With character or dates iuser-exits worke fine.
My characteristic is CONNID Type NUMC 4
My user-exit variable is named CONNID_EXIT_STEP_2.
My ABAP processing in the exit for the user-exit varibale is quite simple (testcase):
DATA: l_e_t_range TYPE rsr_s_rangesid.
l_e_t_range-low = '17'.
l_e_t_range-opt = 'EQ'.
l_e_t_range-sign = 'I'.
APPEND l_e_t_range      TO   e_t_range.
My Error message in the BEX Analyser is:
Value "17" for user-exit variable CONNID_EXIT_STEP_2 is inavlid.
What's wrong with the ABAP processing in the exit (testcase) ?
The debugger clearly shows l_e_t_range-low with value 17.
l_e_t_range-low seems is a character.
Anyone can give a tip ?
Thank You !
Martin
ThanXs

Dear Karthik,
You are right. First time my user exit execute, after that report automatically call message located Function Module LCOPDU13 504th row
     IF NOT SY-MSGID IS INITIAL.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
Message number is 806 message id is RU.
Can you help me for fix this situation? I just want to add a data control in ZXCOFU05 user exit. For user fill data (werks based)
Thanks your helpful answer

ME28 user exit - sy-ucomm not available

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

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

F110 transction, user exit

Hi all,
I have a situation.
There is a substitution rule defined, in one of the steps, there is a prerequisite which says
G/L = 'M163004002', i have attached a user exit for this step. So, this user exit will get triggered whenever a line item containg the above GL account is encountered.
Supposing i have vendor line items like shown below,
Itm CoCd Acct no. Description Amount in MXN001 4127 5000026 José Luís Gárcia Méñ 120,00
002 4127 M260512000 OTHER LIABILITIES 11,57-
003 4127 M260505000 OTHER LIABILITIES 1,16-
004 4127 M163004002 ABA Seguros 107,27-
Here, the line item 004 is the line item which satisfy the prerequisite, so the user exit will get triggered when line item 004 is encountered. At the point to trigger, when the control is in user exit, i hav access only to line item 004, my problen will be solved if I somehow get the access to all the remaining (i.e., 001, 002 and 003) line items. Remember, this data is still not available at Database.
Could somebody help me on this.
Thanks and regards
Deep.

Hi Andreas,
Could you tell me more about this, please....
Thats right, i have made substition with TA OBBH.
Here is the snapshot of OBBH Tranaction,
CoCd CallPnt Substitution Description Activtn Level
4001 2 XXXXX Substitution Rules 1
Thanks and Regards
Deep

User exit code does not execute

I'm having a problem with User exit code that does not execute yet seems to be set up correctly.
The User exit is implemented as FM "EXIT_SAPLIPW1_001" in function group XQSM.
I've tried everything I know of with the CMOD and SMOD transactions, and I suspect some sort of transport error.
The only clue I can find in comparing the development system (which works) with the test system (which does not work) is that running "Extended Check" in SE80 on function group XQSM fails with the following error:
"The namespace of program SAPLXQSM has the setting "C" and cannot be tested."
Has anyone any idea what could have happened?

Let us try to retrace the steps.
1. You created a Z project in CMOD and assigned the enhancement IQSM0001 and the component EXIT_SAPLIPW1_001 and activated the same. This is there in the transport.
2. You double clicked on the include in the user exit and created it. You activated the code and included it in the same transport.
If you did the above steps, then your user exit should be active in your test system.
Can you please go to SE10, and list out the objects in your transport? You should see entries in there like below(not necessarily a complete list)
R3TR CMOD <your project name>
R3TR PROG ZXQSMU01
See if you created any of the objects as local objects.
Srinivas

Enhancements, User Exits

Hi all,
where can u find all the userits & enhancements available in Materials Management.
thanks

Dear Sridhar,
ME590001 |Grouping of requsitions for PO split in ME59 |
MEAG0001
Distribution of Contract/Scheduling Agreement from CRM
MEETA001
Define schedule line type (backlog, immed. req., preview)
MEFLD004
Determine earliest delivery date f. check w. GR (only PO)
MELAB001
Gen. forecast delivery schedules: Transfer schedule implem.
MENUCRQ0
QM: Enhancement in CRQ0 Menu (Work Center)
MENUQA00
QM: Enhancement in QA00 Area Menu (Quality Inspection)
MENUQB00
QM: Enhancements in QB00 Area Menu (QM in Procurement)
MENUQD00
QM: Enhancement in QD00 Menu (Archiving)
MENUQM00
QM: Enhancements in QM00 Area Menu (Quality Notification)
MENUQMM0
QM: Enhancements in QMM0 Menu (Material-Related Q. Planning)
MENUQP00
QM: Enhancements in QP00 Area Menu (Inspection Planning)
MENUQS00
QM: Enhancements in QS00 Area Menu (Basic Data)
MENUQT00
QM: Enhancement in QT00 Area Menu (Test Equipment)
MENUQV00
QM: Enhancements in QV00 Area Menu (QM in SD)
MENUQZ00
QM: Enhancements in QZ00 Area Menu (Quality Certificate)
MEQUERY1
Enhancement to Document Overview ME21N/ME51N
MEREQ001
Customers' Own Data in Purchase Requisition
MEVME001
WE default quantity calc. and over/ underdelivery tolerance
MGA00001
Material Master (Industry): Checks and Enhancements
MGA00002
Material Master (Industry): Number Assignment
MGA00003
Material Master (Industry and Retail): Number Display
MGV00001
Material Master (Industry): ALE Distribution
MGV00002
Material Master (Industry): Read Values for Filter Objects
MGV00003
Material master (retail): ALE distribution
MGW00001
Material Master (Retail): Additional Data
MGW00002
Material Master (Retail): Number Assignment
MKKS0001
Variances: Automatic Job Scheduling in Subsequent Period
MM06E001
User exits for EDI inbound and outbound purchasing documents
MM06E002
IDOC processing for contracts in inbox
MM06E003
Number range and document number
MM06E004
Control import data screens in purchase order
MM06E005
Customer fields in purchasing document
MM06E007
Change document for requisitions upon conversion into PO
MM06E008
Monitoring of contr. target value in case of release orders
MM06E009
Relevant texts for "Texts exist" indicator
MM06E010
Field selection for vendor address
MM06E011
Activate PReq Block
MM06L001
Exits to determine ratings in vendor evaluation
MM08R001
User exits for ERS
MM08R002
User exit for tolerance checks
MM61W001
User exits in function module FORECAST environment
MMAL0001
ALE source list distribution: Outbound processing
MMAL0002
ALE source list distribution: Inbound processing
MMAL0003
ALE purcasing info record distribution: Outbound processing
MMAL0004
ALE purchasing info record distribution: Inbound processing
MMDA0001
Default delivery addresses
MMFAB001
User exit for generation of release order
MPKB0001
User's own functions in the Kanban processing
MPKB0002
Customer defined display in kanban board
MPKC0001
User exit for kanban calculation
MPKD0001
Kanban output as EDI
MPKP0001
Customer Defined Display in Kanban Board
MPKR0001
Customer fields in kanban control cycle
MPR10001
User Exits in TA MPR1 (External Forecast Transfer)
MPRO0004
Postprocessing of forecast errors and exception messages
MRMH0001
Logistics Invoice Verification: ERS procedure
MRMH0002
Logistics Invoice Verification: EDI inbound
MRMH0003
Logistics Invoice Verification: Revaluation/RAP
MRMN0001
Message output and creation: Logistics Invoice Verification
MSSTV001
Customer Exit 'Team Viewer': Exclude Manager
MV56AINI
Initialization of transaction control for transportation
MVEIPREF
User exits - Preference determination
MWM2S001
Exit to Determine 2-Step Picking Characteristic
MWMBAP01
Enhancement for BAPI WarehouseTransOrder.GetDetail
MWMBAP02
Enhancement for BAPI WarehouseStock.GetDetail
MWMD0001
Transfer order print via RLVSDR40
MWMD0002
Transfer order print as multiple process with RLKOMM40
MWMIDI01
Enhancement for error handling with IDOC inbox
MWMIDI02
Enhancement for mssge WMTOCO (Confirm transfer order) Inbox
MWMIDI03
Enhancement for mssge WMCATO (Cancel transfer order) Inbox
MWMIDI04
Enhancement for mssge WMBBIN (Lock storage bin) Inbox
MWMIDI05
Enhancement for mssge WMTREQ (Create transfer req.) Inbox
MWMIDI06
Enhancement for mssge WMSUMO (Move storage unit) Inbox
MWMIDI07
Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO01
Enhancement of IDOCs WMTOID01 (Transport request) Outbox
MWMIDO02
Enhancement of IDOCs WMCAID01 (Cancel transfer req.) Outbox
MWMIDO03
Enhancement of IDOCs WMRRID01 (release ref. no.) Outbox
MWMIDO04
Enhancement of IDOCs WMIVID01 (system inventory rec.) Outbox
MWMIDO07
Enhancement for error handling for IDOC inbox: PDC
MWMIDO08
Enhancement for message WMMBXY (goods movement) Inbox
MWMIDO09
Enhancement for msg. WMINVE (count data, phys. invnt.) Inbox
MWMIDO10
Enhancement for msg. WMTORD (Generate transfer order) Inbox
MWMIDO11
Enhancement for message WMTORD: TO with several items
MWMIDO12
Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13
Extension for WMMBXY (subsequent tasks after goods movement)
MWMK0001
Warehouse management: Customer exit for storage unit number
MWMMOB01
Enhancement for Verification Field in the Warehouse Master
MWMMOB02
Extension for Barcode Translation
MWMPP001
Enhancement WM/PP Interface (automatic TR generation)
MWMRF001
RF: Influence Display of material description
MWMRF100
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0100)
MWMRF101
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0101)
MWMRF102
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0102)
MWMRF104
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0104)
MWMRF105
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0105)
MWMRF106
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0106)
MWMRF107
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0107)
MWMRF108
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
MWMRF151
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
MWMRF152
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
MWMRF153
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
MWMRF170
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0170)
MWMRF202
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF203
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
MWMRF204
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
MWMRF205
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
MWMRF212
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
MWMRF213
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
MWMRF221
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
MWMRF302
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
MWMRF303
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)
MWMRF304
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0304)
MWMRF305
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0305)
MWMRF312
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0312)
MWMRF313
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0313)
MWMRF321
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0321)
MWMRF400
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0400)
MWMRF402
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0402)
MWMRF403
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0403)
MWMRF404
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0404)
MWMRF405
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0405)
MWMRF406
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0406)
MWMRF410
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0410)
MWMRF411
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0411
MWMRF412
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
MWMRF502
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0502)
MWMRF503
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0503)
MWMRF504
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0504)
MWMRF505
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0505)
MWMRF600
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0600)
MWMRF601
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0601)
MWMRF630
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
MWMRF631
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
MWMRF632
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
MWMRF633
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0633)
MWMRF634
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0634)
MWMRF650
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
MWMRF651
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0651)
MWMRF700
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF701
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0701)
MWMRF702
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF703
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0703)
MWMRF704
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0704)
MWMRF705
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0705)
MWMRF760
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0760)
MWMRF761
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0761)
MWMRF762
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0762)
MWMRF763
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0763)
MWMRF764
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0764)
MWMRF765
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0765)
MWMRF766
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0766)
MWMRF767
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0767)
MWMRF768
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0768)
MWMRF769
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0769)
MWMRF777
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0777)
MWMRF800
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0800)
MWMRF801
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0801)
MWMRF802
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0802)
MWMRF803
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0803)
MWMRF804
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0804)
MWMRF805
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0805)
MWMRF806
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0806)
MWMRF807
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0807)
MWMRF888
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0888)
MWMRF889
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF998
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0998)
MWMRF999
ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0999)
MWMRFCOD
Enhancement for function codedisabling
MWMRFDLV
select delivery by user criteria
MWMRFPRT
Enhancement for printing
MWMRFSRT
ENHANCEMENT FOR TO SORTING
MWMRFSSG
user exit for sorting TOs in RF system-guided transaction
MWMRFUP
Customer defined general purpose pushbutton called from scr.
MWMRP001
Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002
Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003
Customer Exit for Replenishment using RLLNACH1
MWMRP004
User Exit for Replenishment using RLLNACH4
MWMTO001
Enhancements for end of transfer order generation
MWMTO002
Enhancements at end of transfer order confirmation
MWMTO003
Own stock placement strategy
MWMTO004
Own stock removal strategy
MWMTO005
Underdelivery
MWMTO006
Overdelivery and with restriction, also underdelivery
MWMTO007
Palletization and storage type search for stock placement
MWMTO008
Storage type search for stock removal
MWMTO009
Prevent the TA items being deleted
MWMTO010
Exit: Calculation of Total Planned TO Processing Time
MWMTO011
Correction of Planned Processing Time for TO Item
MWMTO012
Correction of Sorting and Split Transfer Order
MWMTO013
Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU1
Own sel. of transfer reqs. for auto. transfer order creation
MWMTOAU2
Own selection for auto. transfer order creation via ref. no.
MWMTOAU3
Separate selection of posting changes for autom.TO creation
MWMTR001
Exits at the end of transfer rqmnt creation (IM,PP interf.)
MYCATS01
Enhancement of Picklists for CATS notebook
MYCATS02
Send Customer Table or Standard Texts to CATS notebook
MYCATS03
Supplement Offline Time Data
MYCATS04
CATS notebook: Influence Synchronization Messages
Hope this will help.
Regards,
Naveen.

Re: User Exits on Updating and Integrating

Carl,
I sent this out to the list some time ago. But in case
you missed it here it is again.
Below is a zip file (UUencoded) containing instructions
on integrating Forte with Microsoft SourceSafe. It may
contain enough information for you to figure out how to
tap the repository callouts that happen on integrations.
-Fred
[email protected]
>
I was reading an old Forte v3.0 presentation on whats new in Forte v3.0.
One of the proposed features was a set of primitives for defining user exits
on updates and integrations.
I haven't seen any facility for this in Forte v3.0g though. Has this in fact been
done ? Does anyone have any information on this.
Thanks,
-Carl
Carl Schei
Technical Forte Consultant
South Africa
+27 31 3641765 (w)
email : [email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>------------------------------------------------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Ltd.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Although not a direct answer to your question, this blog series will help you to understand the difference better :
/people/thomas.weiss/blog/2006/01/24/what-the-new-enhancement-framework-is-for-150-its-basic-structure-and-elements-for-beginners
/people/thomas.weiss/blog/2006/03/15/the-new-enhancement-framework-part-2--what-else-you-need-to-know-before-building-an-enhancement
/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
/people/thomas.weiss/blog/2006/05/03/source-code-enhancements--part-5-of-the-series-on-the-new-enhancement-framework

Set Credit control status in user Exit LVKMPFZ1

Similar Messages

Maybe you are looking for