Use exit in sales order.

I want to change material available date through program when I save sales order. I will write this program in sales order user exit. Which exit shall i Use so that changed material available date will be reflected in all tables.
What impact will be impact if I change material available date using program

Hi,
please see this it my be usefull for u.
Hi, You can try inthe program: MV45AFZZ to use the exit: USEREXIT_SAVE_DOCUMENT_PREPARE I that point does not meet your needs you can check that program for others points of process execution. The system SPRO path to find on line doc is: -Sales and Distribution --System Modifications ---User Exits -
User Exits in Sales User Exits In Sales Document Processing.
Best regards,
venkataswamy.y

Similar Messages

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can 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)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

How can I use the field "Sales Order" on derivation?

Dear All.
This is about PA characteristic derivation.
I want to change the characteristic value "Sales Order (KAUFN)" by derivation.
But I cannot select the characteristic field on target field.
The field "Sales order(KAUFN)" doesn't exist there.
Why? How can I use the field "Sales Order" on derivation?
Y.C.Bae

Hi Bae,
in order to be able to choose fields KAUFN (for sales order) and KDPOS
(for sales order item) as target fields of derivation step 'enhancement'
you have to modify the coding of subroutine EXIT GET_ALLOWED_TARGETS
in program RKEDRCOPA like this:
    NAME-IDENTIFIER = 'CO-PA'.
    NAME-TABNAME = FIELDTAB_ENTRY-TABNAME.
    NAME-FIELDNAME = FIELDTAB_ENTRY-FIELDNAME.
    IF FIELDTAB_ENTRY-USGFL CA 'DUV'
BEGIN OF INSERTION *****
         OR FIELDTAB_ENTRY-FIELDNAME = 'KAUFN'
         OR FIELDTAB_ENTRY-FIELDNAME = 'KDPOS'
END   OF INSERTION *****
         OR FIELDTAB_ENTRY-FIELDNAME = 'KNDNR'
         OR FIELDTAB_ENTRY-FIELDNAME = 'ARTNR'
Actually sales order number and sales order item shouldn't be changed
by derivation (therefore they are no valid target fields in standard)
but if you need to fill them within an enhancement this modification
will help you to define them as valid target fields. But this is just
the technical frame so far; the logic from which table you'd like to
derive the sales order number correctly depends on your implementation
of the enhancement! I just want to ask you to be rather careful with
the implementation of the exit so that the sales order number isn't
changed in cases that shouldn't be concerned.
Regards,
Abhisek

Same serial number + material combo can be used in different sales orders?

Hi,
We have a recurring issue in our system where a Serial Number/Material combination can be used in another sales order once it is already in ECUS status.
Example: We sell and post material 123 with serial number 456, it goes into ECUS status, and we are then able to create a sales order with the exact same numbers.
Is this something that I should escalate to OSS? Why is this happening? Is there an IMG setting where I can turn on this functionality?
I woud be very grateful for any help! Thank you so much!

Hi San,
The org. determination rule is setup correctly, I've followed the link below to determine sales area on item level - to clarify, we are creating online sales orders (B2B scenario)
https://help.sap.com/saphelp_sm40/helpdata/en/61/ac747795b511d3b53e006094b9ea37/content.htm?frameset=/en/63/02b638faa32d…
Check the table in the section "Organizational data at item level" - i have already assigned an org.determination profile with no determination rule on item level and still facing the same problem.

Which t code use before pre sale order

gud morng to all
pls tell me. which t. code use before pre sale order (va21) and why this function use and how
regards,
gaurav pabreja

T.Code: VA11
to create Inquiry
The document flow is
IN > QT > OR > LF > F2
The Inquiry is done in order to get to know the price that the customer is going to get. It can be done over the phone, e-mail or a walk-in.
Regards
AK
reward points if helpful

What is the standard class used to create SALES ORDER in SAP CRM?

Hello Experts,
Can anyone suggest me what is the standard class used for creating sales order.
I have created sales order using the BAPI 'BAPI_SLSTRANSACT_CREATEMULTI' in my report program.
Now, I have to create sales order using standard classes and methods(my assignment).
Please suggest the suitable class.
Regards
DNR Varma

Hi Varma,
You can create crm documents like sales order using BOL interfaces.
You can check one example at the following thread:
Create OrderThro BOL
Check if it helps you a little more.
Kind regards,
Garcia

Using va02 change sales order

dear experts,
i need help from urs, i am using bdc close sale order, when its having delivery. i done this issue
only single line delivery, that is in schdule lines having one schedule line with delivery, i done this using call transaction, but i can't do multiple scdule line with delivery. i know sap standard not allowed with delivery. but i want any other way, like using bapi.
regards
sakthi

Hi,
Not able to understand this.....Can you please a bit more explanatory....

One time Discount Coupon to be used during the Sales Order Creation

I need help to configure a one time coupon to be used during a Sales Order creation. During 2009 our customers that have purchased more than certain amount we are going to give them a discount Coupon with a code that they can use just one time during his next purchase. I need help to configure this request.
Thanks

Hi Gilberto
Go VK11.
After maintaining the material & price, please go to -->Additional data.
You will be displayed with Validity, Assignments, Assignments for retail promotion, Limits for Pricing, Payments.
In the 'Limits for Pricing' you have three options - Max. condition value, Max number of orders & Max condition base value.
In the Max number of Orders - enter 1 to avail this special price only for first order.
Importent Note: to activate the ' Limit of Pricing' -- you need to tick 'Condition update' for the particular contion type, in condition type customising.
FOr eg. condition type - ZR00 - you need to have special price for this condition type & want to limit only for first order order.
In the customising for ZR00 - 'condition update' need to be ticked, then only you can get the above option.
i hope it is clear to you
thank you
Anirudh

User exit for Sales order

hi,
i need to eliminate leading zeros for PO number which comes in SO created trough ALE.i found the enhancement for the FM idoc_input_orders.in that enahancement we have 12 FM's.my Leading zeros are comming for field belnr which comes in e1edk01 segment of idoc orders05.now i had coded my part of coding in FM exit_saplved.._oo1 and i had activated that.but it is not working for me.than i tought of going to other FM exit_sapl..._009.in which i'm not able go into the include either.plz help me out.thank you.

Hi, Krishna!
With IDOC_INPUT_ORDERS during IDoc interpretation PO number is assigned to XVBAK-BSTKD field which is later used for sales order creation with reference to PO.
So all you need is to use some customer exit with changing parameters containing XVBAK after IDoc interpretation is completed. For example you can use EXIT_SAPLVEDA_009 which is called at the end of IDoc check after interpretation.
Regards,
Maxim.

User exit for sales order creation VA01.

Hi friends,
While creating Sales order, before saving the document, I need to check the Customer (Sold to pary?) details in KNEX table. KNEX-KUNNR KNEX-TDOCO KNEX-DHRCO. if condition fails, I need to display an error message V1525,
which should contain
1)customer(sold-to -party?KNEX-KUNNR)
2)partner function PARVW (VBPA-PARVW?)
3)country LNDEX KNEX-LNDEX
Functional spec says, 1)V45A0002
                              2)V45A0003
                              3)V45S0001
                              4)V50EPROP User exits can be levaraged.
1)triggers before we enter customer (sold-to-party) in VA01. so may not be used.
remaining i tried, but I am not able to get the proper PARVW, LNDEX from function module parameters / structures like VBAP/VBPA etc.
Please help me the way.
i) the above user exits can be used?if not, help me with user exit name.
ii)if yes, how to fetch PARVW , LNDEX, KUNNR...as all the primary keys must be used in the selection query.
Please help me ASAP.

Hi,
Use this enhancement V45A0002.
Reward points if it helps,
Satish

User exits for sales order

Dear all SAP experts,
How to find out the user exits for sales document type? Especially the user exits which are called when we save the sales order.
With best regards,
Allabaqsh G. Patil

Hi,
Also there is user exit to refresh data
USEREXIT_REFRESH_DOCUMENT
       It is always necessary to refresh user-specific data before   *
      the next document will be processed.                          *
      This can be done in this userexit.                            *
      This userexit can be used to refresh user-specific data       *
      when the processing of a sales document is finished           *
      - after the document is saved                                 *
      - when you leave the document processing with F3 or F15       *
      It may be necessary to refresh user-specific data before      *
      the next document will be processed.                          *

Reg:User-Exit In Sales Order to Invoice

Hi All,
I have An requirement that to create automatic sales order and invoice in one go, i have used BAPI_SALESORDER_CREATEFROMDAT2 to create sales order and bdc invoice to create invoice its worked fine.
My problem is now i got an requirement as after creating sales order it should not create invoice as such because they will manually check whether the sales order is correct then only i should proceed to invoice also they need the option to create,change,delete sales order and same too invoice how can i acheive this scenario through user exits?
Since am new to user exit can any one tell me how to use user exits and what user exits need like this scenario?

Hi Suresh,
For sales order following user exits can be used. These are available in include MV45AFZZ.
USEREXIT_DELETE_DOCUMENT : At the time of deletion of sales order
USEREXIT_SAVE_DOCUMENT : At the time of updations or creation of sales order.
Following are the user exits available in smod.
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 numbe
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 Procedu
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lis
V61A0001 Customer enhancement: Pricing
Please check this exits which will help you for your requirement.
Thanks,
Naveen Kumar.

User-Exits in sales Order

Hello friends,
In VA02 the customer has a requirement,For particular users it should not allow to enter new line items in the existing orders.but it should be able to modify the exsisting line items.ie if there are 3 line items a 4th item should not be allowed to be created(the below lines should come shaded).Please suggest a user exit and also help in the logic
Thanks in advance

You can use MV45AFZZ Include .
here you can write the code in one of form routine.
form save_document_prepare.
endform.
or
form save_data.
endform.
you can keep break point with in form routine and change the sales order.
Thanks
Seshu

User exit in sales order

Hi All,
I want to know if there is a way (user exit) that could look at the Sales Order Type , particular Item Pricing Condition and Ship-to party State and set the materialu2019s tax classification (VBAP/TAXM1) to u201C0u201D (Exempt) ?
Thanks in Advance!
Sonali.

Hi GSL,
I have put the code in the user exit, and I am able to set the tax classification indicator but I have a problem... Before setting the indicator I need to check for the Usage code of the line item (This code I am using instead of checking the Pricing condition) . I am able to read all the values of line item in VBAP structure in the user exit except for the first time this user exit is hit as soon as a line item is entered it is not picking up the Usage code. That field is blank.
But if add another line item and go into the user exit I can see the previous line item Usage code in XVBPA table.
Do you have any idea why usage code is missing in VBAP structure in the user exit or is there any other table or structure where I can get the usage code?
Please let me know if any one have any ideas.
Thanks in Advance!
Sonali.

User Exit during Sales Order Creation - New Line Item needed

I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
I will definitely reward points for useful answers.
Clark

Hello Mahendra
The requirement is as follows :
PART 1:
Sales Order Enter:
1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check items where VRKME <> EA
2.     If VRKME = EA, go to MARM for MATNR.
3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
6.     Add a new line to VBAP for the same material with the case quantity. If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
PART 2:
Batch Job to run prior to the Delivery Due List:
1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed). Get all of the document numbers (VBELN).
2.     Go to VBEP for those document numbers to get the goods issue date for the order. There will be many records in VBEP for the same sales order. Look at all orders with a goods issue date (WADAT) of next day.
3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
4.     For customers who have more than one order in VBAK, search all line items (for all orders). If there are no duplicate materials across sales orders, do nothing.
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
5.     If there are duplicate materials, go through the same logic as in part 1. If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, Line Item Consolidation. If there is no remainder, update the qty on this item directly.
     Part 2 is relevant for order types ZOR, ZCA, ZSM
     This batch job will have to be run manually for Day Pick orders. The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
Business Justification:
The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking. This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material. In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

Use exit in sales order.

Similar Messages

Maybe you are looking for