Billing output user exit

Hi,
My requirement is to have checking on material price during billing process.
When billing document posted -> the output determination is set automatically. But when user try to print the billing doc, I want to have some checking on material pricing group and be able to show error message if pricing not maintained.
Is there any user exit can be used ?
Thanks,
Melissa

Hi Melissa,
You need to get a routine written through VOFM and need to assign this routine in Billing Output Rocedure with the output Type in the requirements column.
You need to identify the Material Pricing group which particular groups/ else identify the Pricing Condition type which is responsible for this Material Pricing group based discount/surcharge and look for the values from KONV table the PK-FK relationship between VBRK/VBRP table and KONV table id done through KNUMV field in the billing tables ,take that number and then go to KONV look for that particular Condition Type KSCHL Files and its value in KWERT/KBETR check if the vlaue is not null.
Hope it helps.

Similar Messages

Cancel Billing document User Exit

Hi,
The requirement at our client is as follows:
In transaction VF02, if the user selects to cancel the billing document "Menu: Billing document->Cancel", then we need an user exit to check that, for a particular pricing condition if an accounting document exists. If so, then put out a message and stop the cancel from happening.
Are there any user exits that get triggered specifically when cancelling a billing document so that I will have access to VBRK, VBRP and KONV data to read table BSET?
Any suggestions will be appreciated.
TIA.
Cheers,
-Ramesh

Hi Ramesh,
In configuration of the billing document type, there is a section for 'cancellation'. In this section, you can enter a copying requirement. In that requirement(probably your custom one), you can write the logic for your purpose. You can see this configuration by following the path
IMG--> Sales and Distribution
       -->Billing
          -->Billing Documents
             -->Define Billing Types
                -->Define Billing Types
Once you select your billing type and do the display, you will see this section in there.
Srinivas

Copy header text from DO to billing via user-exit

Dear Experts,
We have a requirement to copy one text field in the DO header to Billing header text field. I've searched the forum before posting this one but none seems to fit my requirement. I am using RV60AFZC form USEREXIT_FILL_VBRK_VBRP for this. From VF01, I see the header text was populated but after saving, it is being cleared out. I suspect the copy control from sales order to billing header text is doing this, nothing is saved in the SO.
Any idea how to do this by configuration or by user-exit/enhancement spot?
Looking forward for your responses.
Thanks in advance.
nEnE

Can you please check VOFM>Copying Requirements>Texts, Routine 1. The documentation states:
"This requirement checks if the reference document header has a text entry. If so, it is automatically transferred. This requirement is assigned in the detail of the access sequence for header text determination."
You can copy this in a 9XX routine number and write your specific code there.
Hope this helps!

Change PO Output, user exits

Hello Champions,
Will anyone share me, is there any user exit which triggers while changing Purchase Order Output Medium in ME22N transaction. How to know list of user exits which are applicable for ME22N transaction?. will anyone guide me.
Reward with Full points

Hi,
Here are the list of User Exits for ME22N
Enhancement
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
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
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
MRFLB001                                Control Items for Contract Release Order
AMPL0001                                User subscreen for additional data on AMPL
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
M06B0001                                Role determination for purchase requisition release
M06B0002                                Changes to comm. structure for purchase requisition release
M06B0003                                Number range and document number
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
Business Add-in
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
SMOD_MRFLB001                           Control Items for Contract Release Order
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
Edited by: Raj on May 12, 2008 10:05 PM

How to Suppress billing using user exit EDMSUBI

Dear ALL,
Could anyone let me know how to use this user exit EDMSUPBI. Basically my requirements is to suppress billing for certain meter readings during upload of reading using meter reading upload BAPI.
This user exit gets triggered during the above mentioned meter reading upload event. But I would like to know how to pass the parameters to enable the suppress billing order functionality.
There are no export or import parameters in this user exit. Whereas the user exit has the following tables
XT_EABL
XT_EABLG
XT_ETRG
YT_SUPPR_ETRG
YT_DEACT_EABL
Let me know how to pass the paramets such that the suppress billing order functionality is enabled
WIth Regards
Balaji.J

If you still care:
You will have to access the mtr_obj in memory to get informations.
DATA:
       ls_obj TYPE ISU17_METERREAD.
   import xy_obj TO ls_obj
       FROM memory id 'ISU_MR_EXIT_SAPLEL01_015'.
Cheers.

Billing Document User Exit

Is there a user exit that I can use when a Billing Document (in SD) is being created to change the NAST record ( specifically field VSZTP ) based on certain conditions.
Thanks
Amit

Try EXIT_SAPLV60A_002 in enhancement V60A0001.
Or here are userexits triggered by VF01 and VF04:
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference number)
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lists
V61A0001 Customer enhancement: Pricing
Points are always welcome!

USER EXITS IN BILLING

HI ALL,
Scenario. Billing document created and the user wants to cancel the billing document after the closing period . but the system should not allow to do that what is the user exit to be used ?
Please provide the user exit
Regards
Anil Mairpady

Dear Anil,
Instead, what i would suggest to discuss with FI-Personnels and resolve the same.
Best Regards,
Amit.
Note: As far as, your exact requirement is concerned, Lemme check and If, I come-up with some alternate solution, I'll definitely update. meanwhile, you may check with BAPI_BILLINGDOC_CANCEL1 (haven't much knowledge about it as never encountered such requirement at my end).
Also, you may look in to following threads, if you get some helpful information:
[Thread1|Fixing Billing Date in vf11 (cancel billing Document)]
[Thread2|User-Exit to cancel a Billing Document]
[Thread3|Cancel Billing document User Exit]
Edited by: Amit Yadav on Dec 8, 2008 7:08 AM

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

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

Query on Billig Save User-exit

Hello Folks,
This question is related to SD (Billing Area).
We have a requirment, In the Billing Save User-exit 'RV60AFZZ', we need check for the VAT Reg No of the Sales Org in a Z-table, if its not configured in it then we need to stop the Billing creation.
i.e, when sy-subrc ne 0, stop the Billing generation.
We tried with the commands 'check' and 'Exit', these did not work. The control exits from RV60AFZZ but the billing is still created. Then we tried command 'STOP'. This works good in online mode (VF01), however in batch mode there is an issue. The billing for the particular document (when sy-subrc ne 0) is stopped, however the job skips all the docs for billing generation. But the Job does not abort.
I know that the copy control routines are the perfect choices for implementing this kind of logic. However due to the other requirements we had to put the logic in the Billing save User-exit,
Can someone help me here.
I need to stop the billing generation( in batch mode )for a particular doc based a check (if sy-subrc ne 0) and the batch job should invoice the rest of the docs which it picks from the Billing due list.
Regards,
Mohan Krishna

Hi
U can use fm READ_TEXT:
DATA: THEAD LIKE THEAD,
 TLINES LIKE STANDARD TABLE OF TLINE WITH HEADER LINE.
THEAD-TDID = <text id>.
THEAD-TDSPRAD = <language>.
THEAD-TDOBJECT = 'VBBK'.
THEAD-TDNAME = VBAK-VBELN.
CALL FUNCTION 'READ_TEXT'
EXPORTING
 ID = THEAD-TDID
 LANGUAGE = THEAD-TDSPRAD
 NAME = THEAD-TDNAME
 OBJECT = THEAD-TDOBJECT
TABLES
 LINES = TLINES
EXCEPTIONS
 ID = 1
 LANGUAGE = 2
 NAME = 3
 NOT_FOUND = 4
 OBJECT = 5
 REFERENCE_CHECK = 6
 WRONG_ACCESS_TO_ARCHIVE = 7
 OTHERS = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
U can use it in all situations ( inserting and updating) because that fm returns the buffered text.
Max

User exit in order related IC billing

Hello,
we implemented note 63549 and all related notes to make order related IC billing run through output RDIV and program RVIVAUFT.
We have a problem to find a clever way to realize the user exit KOMKBV3_FILL, which should perform a check on cross company transaction and fill consequently field CROSS_COMP, to be used in the output requirement 018. At the moment when the system runs this userexit the customer invoice has not been posted yet and only header fields are available, so it is not possible to go back through doc flow and check for instance plant company code vs sales rog company code. Any suggestion?
Thanks

Hi,
Another way is to make a validation (OB28) and do your checks there.
Regards,
Eli

User exit for output in VF02

Does anyone know of a user exit for the Sales Billing (VF02) that would allow me to manipulate the email address for email outputs. Currently the email address comes from the communciation tab on the customer master, and I want to be able to change it to come from the contacts tab in the cusomer master. I think the program used for the output is RSNAST00

Maybe in one of these Enhancements
VN000001                                Customer exits in output determination
VCOM0004                                Fill Output Communication Areas - Application V7
VCOM0003                                Fill Output Communication Areas - Application M1
VCOM0002                                Fill Output Communication Areas - Application E1
VCOM0001                                Fill Output Communication Areas - Application V6
Sorry, don't remenber which one is for printer, for fax or for mail.
Regards,
Raymond

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.

User exit in VF01 for plant validation while taking the output smartform

Hi Gurus,
I am in a typical situation..
We ahve a scenario where for one specific plant we need to trigger a different output type(smartform) where the billing type is being common for all plants...
example: billing type : A00 ( same for all plants)
              outout type (billing) : B00 ( one smartform)
                                             C00 (another smartform)
For all the plants, Boo triggers as the layout is same for all Except for One specific plant where it should trigger C00 i.e., different smartform i.e., layout...
Any user exit for validating Plant at the time of saving the billing document to trigger a different outout type as above for the same billing type ???
Please help me..
regards
Ravikumar

Dear Ravikumar,
          You can do like this with out using User exit.
-->Take field Plant in to the output condition table
-->Put that condition table in to access sequence
-->Define two condition type as you mentioned B00 and C00
-->Assign access sequence to that condition types.
-->Put those output condition types in the output determination procedure.
-->Assign that output determination procedure to the billing type.
-->Main the condition records for that conditon types with one of the key combination PLANT
I hope it will help you
Regards,
Murali.

User exit at item level for billing block field default for VA41 or VA42

Hi All,
I want user exit at item level for contract (VA41or VA42) for the field Billing Block in the Billing document tab
which has to populate with some default value.
Which user exit i need to check.
Regards
Jai

Hi,
Use subroutine USEREXIT_FIELD_MODIFICATION in Include MV45AFZZ.
Make sure this is for only tcodes VA41 and VA42 because this wil trigger for sales order also.
Regards,
Ashok.

Billing output user exit

Similar Messages

Maybe you are looking for