Problem on Deactivation of a User exit

Hi all,
SAP Gurus, I would like to seek for your help regarding an error I encounter upon transporting the deactivation of a user exit to Q00. We activated a user exit EXIT_SAPLMLSR_001 (user exit of ML81N) and transported the changes up to Production. However, we encounter a problem that leads us to deactivating the said user exit again. In the development landscape, we had successfully done this by first deactivating the project in CMOD, deleting the user exit in there then activating the project again. We tried and ML81N works fine. Service entry sheet are editable in D00. But when we transported it to Q00, the entry sheets are non-editable. We check table TFDIR in D00, the status of the said user exit is Client = blank, while in Q00, Client = 'C' of the said user exit. Can you help us on how to solve this issue and what cause the problem? Thanks and regards.

Hi Madhurao,
I cannot delete the entire project because there are othe user exits that are in there. This problem has been solved by a workaround. Here's what we did, create a dummy project, put the user exit in there, activate it, deactivate then delete the project. The user exit status in TFDIR became Client = blank already. But I still don't know why the problem happens. We want to know the root cause so next time, we would not encounter this again.
Edited by: baguado on Jun 1, 2011 7:34 AM

Similar Messages

Problem with step 2 in user exit.

Hello collegues,
I have a problem with the variables user exit in the bex analyzer. I have created a variable user exit and this is used as user authorization, and this variables is optional and enabled to entry . When i debugg the user exit, i put the break point in the step 1, in the step 0 and in the step 2, i can check the step1 and 0 but in the step 2 don´t stop.
Why does this happen?
Thanks for your collaboration.

Variable enabled to entry are not are not candidate to step 2. This step is only called once per exit variable not enabled to entry.
Regards,
Fred

Problem in MRP planning with user exit key

Hi All,
I have a requirement like this..
we have 1000 FG in our plant.. out of which they want to plan only 250 FG's through MRP run collectively...when they do MRP run system should plan only these 250 FG's and also down level materials ( components ) of these 250 FG's ..
So I proposed to use user exit key in MD01 screen by activating user exit M61X0001 and these 250 FG 's are identified with a separate MRP group in material master and developed enhancement..
But when I do MRP run in MD01 with this user exit key, system only planning those 250 FG's but not planning down level materials or components of these 250 FG's.. is this standard behavior.. can somebody guide me how solve this issue..
Thanks
Kumar

Hi Kumar,
You can use either MRP Type, MRP Controller, MRP Group in this user exit to control the MRP run. For these set of Materials you have to assign any of same value or at least differentiate these material from other material. Then only you can control the MRP by using this user exit even though if you use different MRP Group and MRP Controller. In User Exit, you may have to add your dependent material's MRP Group/MRP Controller. Make sure that these set of materials are different than all other materials.
If you don't have any plan to run MRP for other materials then as per Ajit suggestion you make that material's MRP type as "ND". But, in your business case they may want to activate the MRP for all the material not now but may be latter.
Thanks

Problem with information message in User exit

Hi All,
Iam using the below code in MV45FZZ to check the customer(sold to party) entered in VA31 with a Ztable and popup a message if it exist in the Ztable.
select single * from zcust into zcust where kunnr = kuagv-kunnr.
if sy-subrc = 0.
call function 'POPUP_TO_INFORM'
 exporting
titel = 'INFORMATION'
txt1 = 'Calender day orders for this customer have been blocked'
txt2 = 'Please contact [someone] if this block should be removed'
 TXT3 = ' '
 TXT4 = ' '
 exceptions
 others = 1.
if sy-subrc = 0.
leave to screen 101.
endif.
endif.
The problem is, the message needs to be in logon language based.
I tried to give it in a text element, however it is asking me a access key to enter it in a text element. Also I tried to give just a information message box like this message I088(z2). But this is comming like a success message . Letme know how to overcome this.
Regards,
Senthil

Hello,
I have gave similar kind of info message in the same exit like this
 message i082(Z48SD) with l_r_xvbap-posnr
 l_r_xvbap-matnr
 text-302.
Text-302 is created for the same program SAPMV45A
U could try like this.
If useful reeward.
Vasanth

User Exit in VF01 for Tax Conditions

Hello,
Please inform if any user exit is available for processing Conditions (Tax) in a Sales Order.
I'm facing a problem that while Invoicing, a certain Tax condition is not being executed.
Thanks,
Shalabh Jain

HI Colleague,
I will list the available user-exit to be used for Billing Document:
User Exits For Billing
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
EXIT_SAPLV60B_001: Change the header data in the structure acchd
You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
EXIT_SAPLV60B_003: Change the customer line in costing
The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan
parameters in the GL account item.
EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD
After the accounting document is filled in with data, you can use exit 008 to change the document once again.
EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines before they are created.
EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
You can use this exit to change inbound parameters in order to influence account determination.
I hope that one of them could be helpful.
Regards
Ruy Castro

User Exit/BADI/Enhancement Point in VF01 before new document no assignment

Hi Expert,
I am looking for a user exit/BADI/Enhancement point which will trigger in VF01 before the new document no (Billing document no assign).
I need to cross check few things in Billing via VF01 at billing document save and give error message accordingly. The problem is if new number assign and there is error due to my code then when user save the document next he get a new no. its mean a no skip.
Example: The invoice no is 1000. User start creating a billing document with Vf01 and he get an error message due to my code at exit , at this point of time the next number assign to billing which is 1001 but document not save due to my error message. Now after applying correction user save data and billing document created with no 1002. So there is no skip.
I tried BADI BADI_SD_ACCOUNTING but this will trigger after no assignment. Can someone provide me a user exit/BADI/Enhancement point in VF01 which trigger before no range assignment and contain at least Billing header data to use in my code?
Regards
Swati
Edited by: Swati Namdev on Nov 16, 2010 9:55 PM

HI Brad and team,
BRED is right. I check few user exit normally all of us have that list or easily available on net.
BRED: my question is: I need to check the billing date VBRK-FKDAT of document should not be less than the sales order plan billing date VBAP-Oldate.
If this check fail then won't allow the user to create billing document. The problem is I used one user exit SDVFX001 already define previously that's work fine but issue is that user exit trigger after the billing no assignment. That's why when user get that error message he correct the document and create billing this time he get a new number which is skip of one no.
That why I need a User Exit/BADI/Enhancement Point which trigger at save but before document no assignment.
Please update more about your comment "Why not use a header level copy requirement routine to perform the checks and log the messages? This is the standard process." .
Suggest user exit USEREXIT_FILL_VBRK_VBRP trigger before save. I need at save the reason is VBRK-FKDAT this can be change.
Feel free to contact me back if you need more clarification.
Regards
Swati
Edited by: Swati Namdev on Nov 17, 2010 6:22 PM
Edited by: Swati Namdev on Nov 17, 2010 6:25 PM
Edited by: Swati Namdev on Nov 17, 2010 6:32 PM
Edited by: Swati Namdev on Nov 17, 2010 6:47 PM

User Exit on the save of Billing document (VF01)

Hello All,
I have a requirement where in during the creation of a billing document of a particular type i need to put in a block to prevent the creation of a accounting document and call a workflow to remove the block in the Invoice.
My requirement is that I require a user exit which is triggered on the save of the invoice document so that a call to the workflow can be done where in the runtime information of the document would be available in the workflow for further processing .
Helpful answers would be rewarded.
Thanks in Advance,
Sowmya.

Hi,
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
Refer the help
http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm
Regards
Kiran Sure

Workitem User Exit: User determination

Hi There
I got stuck with the following problem:
I implemented a workitem user exit and managed to determine the actual agent of a workitem at the "after_execution" event from the workitem container.
How can I read the users that are assigned in the workflow definition (e.g. via orgunit, position, multiline container element) to a workitem (or more correctly step)? This should of course be done after or just before creation of the workitem.
Any idea is highly appreciated!
Cheers, Michael

Hi Michael,
Welcome to the ABAP forum!!
If your intention is to get all the selected agents of the Workitem, you can use the SAP_WAPI_WORKITEM_RECIPIENTS function module if it is available in your release. This FM does not work for completed WIs. Since WI id is the required parameter, you should call it after WI creation.
Cheers,
Ramki Maley.
Please reward points if the answer is helpful.
For info on awarding points click on this link: https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm

User Exit to Block Invoicing

Hello,
A sales order needs to be created & its invoicing needs to be blocked if the user(creating a sales order) exceeds a certain value (net) in the sales order. Does anyone has an idea of what user exit we need to code for this.
Regards,
Alam.

User Exits For Billing
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
EXIT_SAPLV60B_001: Change the header data in the structure acchd
You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
EXIT_SAPLV60B_003: Change the customer line in costing
The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan
parameters in the GL account item.
EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD
After the accounting document is filled in with data, you can use exit 008 to change the document once again.
EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines before they are created.
EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
You can use this exit to change inbound parameters in order to influence account determination.
regards
vinod

Code Review of User Exits with Code Inspector

Hi,
We are using Code Inspector(Tcode - SCI) for checking the quality of ABAP Codes. It is working fine for all custom programs. But when we are checking the code of User Exits i: e MV50AFZ1 or ZXM06U22 then it checks the std SAP program (SAPMV50A) or (SAPLXM06) for these exits in place of checking that particular Exit only . How the customer/User Exits can be checked using Code Inspector. Pls advice.

Hi there!
Today, I stumbled over the same problem: Defining an Include for user exits leads to a check of the surrounding function group from SAP which I don't want to correct at all.
Is there a nice an elegant way of filtering out the SAP modules from checking? If not, the only way to get around this seems to be building an own implementation of the Code Inspector integration into CTS.
Thanks, Markus

User exit CIFMAT01

Dear All,
We are facing problems while using the CIF user exit CIFMAT01.
We have written a code to select the materials based on certain criteria. However when we acttivate the integration model the CIF user exit is not getting called.
Is there any global setting through which user exits need to be enabled for CIF?
regards,
Kedar

Hello Kedar,
I suppose the comments I have added to this user-exit in our connected R/3 systems might help you:
OSS 828026: This user-exit is called up to three times during
            data transfer to a SCM system.
            Parameter IV_MAP_STATUS shows for which functionality
            the current call is made.
'1': New material master data is mapped to analyze SCM-relevant changes into the SCM format
'2': Old material master data is mapped to analyze SCM-relevant changes into the SCM format
'3': New material master data is mapped for the CIF transfer
'4': Location products for MRP areas are transferred
'5': Material master data is mapped for the CIF comparison and reconciliation report.
Remarks:
- the target destination is not maintained in status '1' or '2'
- the call with status '3' is done in an update task if immediate transfer
    is executed when changing a product. In this case it is not
    possible to debug this call. If necessary CFM2, CFP1 or RIMODINI
    have to be used for debugging.
Regards.
Hubert

How to make Forms 9i User Exits run on DB server.

We have a memory resident C programs developed in Oracle EE 7.3.4 and Dev2K (charecter based) on HP OpenVMS. Since the application is character based forms/reports - all the components are configured in one single server. There was no problem for us to write user exits and run C programs on the DB server.
Now we want to migrate to Oracle 9i and 9iAS.
My big question is How can we call memory resident C programs running in database server from 9iAS node. 9iAS node is separate Windows 2003 server in the 9i implementation.
Any suggestions on how we can implement this. We understand that WebUtil runs userexits on the client PC. We need similar functionality to run on the DB server. Any ideas would be appreciated.
Thanks in advance.

Whoops, meant to include this:
OS: All clients on WinXPPro. Forms are hosted in an simple open-access folder on a server running SqlServer 05 (no SharePoint yet). I'm designing the new form in Adobe Acrobat 9.2 Pro based on a Word 2007 document.
Thanks again!

Billing user exit for partner determination/substitution

Hi ,
For my SAP ERP , I need a Billing user exit for partner determination/substitution .
If somebody has the info .
Thank's

Hi,
User Exits For Billing:
- USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified
in the billing type table and can be changed in this user exit. This
user exit is only called when the billing documents is created.
- USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that
are not provided in the standard system are copied into
communication structure KOMKCV (header fields).
- USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that
are not provided in the standard system are copied into
communication structure KOMPCV (item fields).
- USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the
billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user
exit is being applied.
- USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created.
It is used to provide the header and the item of the new billing
document with deviating or additional data.
- USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
- USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
- User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
- USEREXIT_RELI_XVBPAK_AVBPAK
- USEREXIT_NEWROLE_XVBPAK_AVBPAK
- USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
- EXIT_SAPLV60B_001: Change the header data in the structure acchd
You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
- EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
- EXIT_SAPLV60B_003: Change the customer line in costing
The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
- EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
- EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
- EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
- EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan parameters in the GL account item.
- EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD After the accounting document is filled in with data, you can use exit 008 to change the document once again.
- EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines before they are created.
- EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
You can use this exit to change inbound parameters in order to influence account determination.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

SAPMV60S user exit

Hi,
I am trying to find out if the user exit USEREXIT_PRICING_PREPARE_TKOMP in include RV60AFZZ is called from SAPMV60S. I do not believe that it is, from my searching SAPMV60S for the user exit and the include, but an ex-employee (ABAPer) is telling me that it is. We have a problem in the user exit but I think that the problem could be that the user exit isn't being called. I put a break-point on the user exit and executed the batch job (which runs SAPMV60S) and it didn't stop at the break-point.
Regards,
Davis

Ferry, thanks. I couldn't find the call to the user exit, or the include, but then again the "where used" list is usually incomplete. How would I have found out this information on my own?
Davis
Message was edited by:
Davis

VF02 user exit just after saving

Hi,
Please tell the user exit or BADI which will work in VF02 alone. Requirement is, whatever changes have been made for quantity in the document, has to be reflected in the Z table in the background.
Please clarify.
Regards,
Tom Jerry.

Hi,
Below are the list of user exit available for billing:-
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
EXIT_SAPLV60B_001: Change the header data in the structure acchd
You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
EXIT_SAPLV60B_003: Change the customer line in costing
The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan
parameters in the GL account item.
EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD
After the accounting document is filled in with data, you can use exit 008 to change the document once again.
EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines before they are created.
EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
You can use this exit to change inbound parameters in order to influence account determination.
with regards
Vivek.

Problem on Deactivation of a User exit

Similar Messages

Maybe you are looking for