User exit trigerred after billing document is generated

The objective is to set the Sales Order Item Level System Status. Using a line item that is created in VA01, I have to create a reference item in VA02. For both the line items created I have to generate billing document in VF01. After the billing document is created (when I give save in VF01), using the billing document number I have to set the Billing and delivery system status to completed.
The functional specification provided me with a user exit USEREXIT_NUMBER_RANGE in RV60AFZZ. But the exit is getting triggered before the billing document number is generated. So I am unable to set the status. Can you suggest me a user exit that would be triggered after the billing document is generated?

if your invoice is relevant for accounting posting - you may use one of SD/FI exits (check RV_ACCOUNTING_DOCUMENT_CREATE and search for call customer-function).
OR you may define new output type for your invoice and put your logic there, nast-objkey will have invoice number.

Similar Messages

BADI or User-Exit while a billing document is generated in CRM

Hi SAP Gurus,
I'm looking for a BADI or a user-exit that gets triggered when a billing document is generaed in CRM.
(My requirement is to transfer Invoice information to Legacy when a billing document is generated.)
Please let me know if you have any idea about it.
Thanks in advance.
Regards,
Sreeraj
Edited by: Sreeraj Pulickal on Apr 21, 2011 1:49 PM

Found the solution.
We used certain 'Events' under the 'Billing Engine' in CRM to achieve the results

User Exit regarding SD billing Document

Hi Experts,
I want several user exits of SD billing document. The one is used to update Item condition when Billing document created, and the second is used to save to my add-on table before document saved. Could you have any suggestions?
Thanks.

[User exits in sales document processing|http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm]

What are the User Exit Available after saving a Billing Documents

Hi,
What are the User Exit Available after saving a Billing Documents
Regrds,
Binayak

Hi
Check the following Exits for VF01 Tcode
V61A0001                                Customer enhancement: Pricing
V60P0001                                Data provision for additional fields for display in lists
V60A0001                                Customer functions in the billing document
V05N0001                                User Exits for Printing Billing Docs. using POR Procedure
V05I0001                                User exits for billing index
SDVFX011                                Userexit for the komkcv- and kompcv-structures
SDVFX010                                User exit item table for the customer lines
SDVFX009                                Billing doc. processing KIDONO (payment reference number)
SDVFX008                                User exit: Processing of transfer structures SD-FI
SDVFX007                                User exit: Billing plan during transfer to Accounting
SDVFX006                                User exit tax line in transfer to accounting
SDVFX005                                User exit reserves in transfer to accounting
SDVFX004                                User exit G/L line in transfer to accounting
SDVFX003                                User exit cash clearing in transfer to accounting
SDVFX002                                User exit for A/R line in transfer to accounting
SDVFX001                                User exit header line in delivery to accounting
Business Add-in
SD_CIN_LV60AU02                         BADI for billing
VOR_WA_FAKTURA                          Billing before Goods Issue
Reward points if useful
Regards
Anji

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.

Billing Document not generated.....

Hi Gurus,
When i am creating a Billing Document VF01....after completion of VL01n...the system shows an error Billing Document not generated...
Please help me
Rewards will be given

To resolve the error, you can analyze account determination in the billing document. Process:
Goto T.Code: VF02 & Enter Invoice number
Next (On the top most strip) goto Environment
Next (Select Environment) go to Account determination
Next (In Account Determination) select Revenue Account Determination (first option)
This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.
Possible errors:
1. VKOA not maintained for required combination
Solution: Maintain the combination in VKOA.
2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).
Solution:
Option 1 (Standard solution):
step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
step 2: Maintain Customer master / Material Master correctly.
step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
Option 2:
Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.
3. Account Key not maintained in Pricing Procedure:
Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.
From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client ot uploaded through LSMW / SCATT / BDC.
In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:
1. G/L account not found
2. Cost Element not maintained for G/L account.
In both the above cases, FI consultant requires to take corrective action.
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

User-Exit for changing Sales Document Number - Urgent

Hi Experts ,
 Please suggest me the User Exit for changing Sales Document Number.
thanks,
Jayesh

hi jayesh,
chech this exit-----EXIT_SAPFV45S_002.
this exit's description says " Change Sales Document Using Configuration".
Other available exits are
SDAPO001 Activating Sourcing Subitem Quantity Propagation
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
Enter these exits name in SMOD transaction and select components. u can find all the user exits available for this exit name.
Reward me if useful..........
Harimanjesh AN

Set sales order status is complete after Billing document created

Hi experts:
Current
Complete rule of item category 'TAN' is space.
The Status will be set complete after Delivery document is created.
I want to change the rule to
the status will be set complete after billing document is created.
Han can I do it ??

Go to VOV7, select the item category and execute. There maintain "B" against the field "Completion Rule"
thanks
G. Lakshmipathi

No billing documents were generated. See log

Hi Expert,
While doing billing trough VF01, i am getting below error message :
No billing documents were generated. See log
Error log is as below :
0025000513 010 Item category ZDOR TAX cannot be invoiced with billing type F2
Could you please tell me how to resolve this error.
Thanks.

Hi,
1> I have gone through transaction VOV7, in that item catagory is assigned with A. If i'll change it to B, will it affect any other billing documents ?
2> Also when i am looking into SD -> Billing -> Billing Documents -> maintains copying controls -> Sales document to billing document in this F2 is in the target anf Zdor is in the source but item category TAX is not present there, so do i need to add item category TAX there ??
Tell me where exactly i need to do changes, in both the above steps or any one of them ?
Thank you.

Is there any user exit in IW54 before document saving?

Dear experts,
Is there any user exit in IW54 before document saving? I want to check some data before saving.
thanks
Lance

Or BADI NOTIF_EVENT_SAVE (Change When Saving Notification)
PeteA

No billing documents were generated

Hi friends i created an sales order and subsequently i did vl01n,lt03 and vlo2n now i want to do billing using VF01 but system is giving error saying that process is incorrect and msg is that No billing documents were generated.
pls help me your help is much appreciated
Thanks
Rag sam

Hi,
There could be no of reasons as per your information.
1)Is PGI done?
2)Are items in order relevant for billing?
3)Please check S.doc type confi- Is there proposed billing type in VOV8?Is it special order type?
4)Please check copy control settings in VTFA.
Thanks,
Vrajesh

VF01 - "No billing documents were generated see log"

Hello Gurus,
I have created the following:
- A sales order
- A delivery
For some strange reasons I cannot create a billing using VF01.
I have selected as follow: F2 for invoice
and I get the following error: "No billing documents were generated see log"
I have checked in VTFL that Billing is related to the Delivery which is the case.
Where can the problem come from?
Please help
Chris

Hi Chris
First of all check weather PGI has been done for the delivery document or not. So Go to VA02 and check the document flow.If PGI has been done in the document flow also then the delivery document might not got updated in the database Table.It might be taking some time to get updated in the database table
Thanks and Regards
Srinath

User exit / BADI for billing block in VL01n

Hello Techies,
Through custom transaction we are creating delivery notes. We run a background job to pick up these delivery notes & create return deliveries using BDC call transaction method calling VL01N (We also create order of type return for same). Though i can not see any place where billing block is filled in custom program but still there are some deliveries with billing block. Could you please let me know if there is any User exit / BADI for billing block or any configuration setting for same?

Just to add more details:
Our program sets memory id field.
We call transaction VL01N.
program clears memory id field value.
all this happens in loop for number of deliveries.
In VL01 user exit overwrites LIKP-FAKSK value to 05. However we have written code here which imports value from memory id. by this we come to know that we have created this delivery using custom transaction & billing block should not be set.
From this we can conclude that only when sy-subrc for import memory id is not equal to 0 then billing block is set.
what could be the reason for sy-subrc for import memory id is not equal to 0 ?
can it be because of number of deliveries created at a time where memory id export / import is causing problem?
we are not able to replicate this issue in Dev/Quality systems.
Thanks & Regards,
Sachin

User exit for Reversing the Document

Hi,
Is there any User exit for reversing the document for FBRA?
Thanks

Hi,
Execute this report you will get the list of user exist for particular transaction,The inpur parameter for this report is transaction code , the output you will be getting is the list of user exists available for this trransaction.
If find my answer suitable pelase reward me suitable points.
REPORT Z_USEREXIT .
TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
TABLES : tstct.
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
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 EQ enlfdir-area.
      MOVE : tadir-devclass TO v_devclass.
    ENDIF.
ENDIF.
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.
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.
Regards,
Irfan Hussain

User exit/BADI AFTER the database commit in va01 va02

Hi All
I need an user exit/BADI AFTER the database tables are updated when save button is pressed on VA01/VA02, both these user exits are fired before that.
Regards
Badari

Check out all these exits
 SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001 Activating Sourcing Subitem Quantity Propagation

User exit trigerred after billing document is generated

Similar Messages

Maybe you are looking for