Configurator events during order line copy

When an Order lines is copied to the same order, no events are fired within CZ, and it appears to be a straight copy of standard data.
We write to custom tables from CZ through events and must determine a way to include this functionality during a copy line (Coping an order does utilize the cz object and events are fired).
Is there a way to utilize CZ events during copy line or recommended handle for performing custom updates?
I would think there would be some cz event fired because the config header id uniquely assigned.

Best way is to add the * number to the price list when it first comes over.

Similar Messages

Material Variant configuration in sales order line item from Ztable

Hello Experts,
we have configurable material and and creating sales order. from sales order line item if we goto configuration we can maintain variant configurations. My requirement is that when i click on configuration after selecting a line item i need to check ztable where i have material no and and relable text. if an entry exists i have to populate this relable text in one of the configuration filed. Can any one help how can i read and update configuration in sales order level and where to do this coding so that when i click on configuration the value from ztable populated in a field.
Many thanks in advance.

Hi Senthil,
It is simple.
When you create a characteristic which should have the value maintained in the Z table, go to the tab values. Here you have a push button called "Other Value check". Here you click this button and select the function module option. Now, in the window, you will have a place where you can mention the name of teh function module.
You create a function module with the help of your developer to find out the text maintained in the Z table using teh rules you have in your mind and update that logic in the characteristic. In the earlier screen, you just have to mention the name of the function module, thats all, your work is done.
Now when you configure, for this characteristic, the value will be automatically determined using teh function module. You have to create such characteristics as "Not ready for input" ones in additional data for which you cannot enter values manually.
Hope this helps.

Order Management Implementation - Configurator and Move Orders

We are in the process of implementing Order Management (11i) version. We have been facing the following issues:
a. Configurator button on order lines form does not open for PTO models - we are not using the Oracle configurator, but are interested in manually choosing the options during Order entry - the form does not open, despite the fact that we have set up the profile,BOM:Configurator URL of UI Manager, as per the suggestions of Oracle.
b. Issues around using Workflow for Move orders - basically, suggested set ups in Organization parameters have been done, but do not see specifically that the workflow process has been started, when saving a move order.
Does any one been successful in getting through either of the issues - any input is highly appreciated.
null

we did face the same problem whes the configurator button was pressed nothing opened up. We applied patch set B and that took care of the problem.We are going to use Oracle Configurator and not BOM bit do have configurator developer installed yet, so are creatinf bills in BOM and selecting the model to order through the sales order screen and choosing the options etc by clicking on the configurator button.The order gets saved but does not gets over to receivables as the workflow process that needs to be run(as per oracle) does not seem to be doing anything at all. There are so many bugs especially in OM that it would take sometime for it to stablize.
Let me know if you need to the specific things that we did to make the configurator screen to appear.

Entry of Configured Star item in sales order line

Hi All,
We have a requirement to enter a Configured item(STAR Item) into a sales order line and facing pricing issues.
The Configured item will be imported from a legacy system(client's equivalent of i-store) along with all the option class and options into Order Management.During this import, we will update the unit selling price of the star item and complete the sales order.
Now, when another order comes in for the same star item(same set of options), client wants to just enter the item manually in OM without having to do configuration(as the options classes are close to 30 which would be in-efficient from a timing perspective).In this case if they were to enter the star item right into the sales order line, then we are unable to price it as this item does not exist in any price list.
So, can anyone suggest if there is a standard way to add the star item into a price list (via profile options/advanced pricing attributes. etc.,) or would it make sense just to add the star item into the price list when it first came from the leagacy system using some customisation.
To add: we are using Oracle OM and a legacy system for configuring products. We are not using Oracle Configurator.
Please help resolve this paramount issue.
Regards.
Sarav

Best way is to add the * number to the price list when it first comes over.

Copying Variant Configuration across sales order items

Hi,
We are working with SAP 4.7.
I have a requirement to default the variant configuration values entered within line 1 of the sales order entry process on to subsequent lines. i.e. defaulting initial values for the configuration.
Our users have to enter many variant line items on a sales order and within an individual order the variant characteristics will be very similar, therefore by defaulting these values to be the same as the previously entered line would be a considerable overhead saving.
However I am having difficulty accessing the variant values which have been entered in the first line item. I have looked at userexit_move_workarea_to_sdwa and userexit_get_field_from_sdcom, however I don't know if I am heading in the right direction. Any advice appreciated.
Thanks for your time.

We are doing this with main-positions and subpositions. The sales clerk enters the main Position with all the characteristics, switches to the tab "Fast data entry" types in the main position, he wants to copy from and the material. There is a dependency which calls a function module which does the real work.
This works with 4.6B in 4.7 there is a psotion type global position which acts similiar.
Ok, now the code:
Dependency
pfunction Z_SD_WERTE_CHARACTERICS
(SD_VBAP_UEPOS         = SD_VBAP_UEPOS,
   STAERKE           = $self.STAERKE,
   BREITE              = $self.BREITE)
/code
CALL FUNCTION 'Z_SD_INHERITANCE'
     EXPORTING
          GLOBALS        = globals
     TABLES
          QUERY          = query
          MATCH          = match
     EXCEPTIONS
          FAIL           = 1
          INTERNAL_ERROR = 2
          OTHERS         = 3
/code
Z_SD_INHERITANCE
DATA: h_uepos LIKE vbap-uepos.
DATA: x_values TYPE ibco2_value_rec OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS:
-values.
    ENDLOOP.
ENDIF.
*-- Ausgabeverarbeitung
LOOP AT match WHERE atcio = 'O'.
*-- Konvertierung ATINN auf ATNAM
    SELECT SINGLE * FROM cabn WHERE atnam = match-varnam.
    CHECK sy-subrc EQ '0'.
    READ TABLE x_values WITH KEY atinn = cabn-atinn.
    IF     sy-subrc IS INITIAL AND
       NOT x_values-atwrt IS INITIAL.
      match-atwrt = x_values-atwrt.
    ELSEIF sy-subrc IS INITIAL AND
       NOT x_values-atflv IS INITIAL.
      match-atflv = x_values-atflv.
    ENDIF.
    match-atfor = cabn-atfor.
    MODIFY match.
ENDLOOP.
ENDFUNCTION.
/code
Kind regards
Matthias Kabel

Third Party GRN Posting Date to be Copied to Sales Order Line item Billing Date

Hello Experts
I have a client requirement where in they want to bill line items in the sales order ( third party process ) to the end customer in sync with the GRN posting dates happened in the PO
For EG if GRN happened on 1st July 2014 then Billing Date should come in as 31st July 2014 so when they execute VF04 giving from and to dates as 1st july to 31st corresponding sales order can be invoiced
Actual problem is for suppose if i create a sales order in the month of june say 26th basing on the factory calendar setting and invoicing list maintained in the customer master system defaults the billing date to 30th June 2014 , and the same when user runs VF04 from 1st June to 30th June this sales order shows as due and mistakenly end user invoices the customer ( whereas logical GR would have only received in July 1st )
My requirement is similar to below threads but i am unable to find answer how to copy GR Posting date to Billing Date of the sales order line item
use GR Doc date as billing date
3rd party sales process (w/o ship notif) - Billing

Hi Lakshmipathi ji,
As my requirement is to update the billing date at the sales order line item level , As a process user goes in executes VF04
For Ex
Sales Order Created Date is 1st June 2014 then System Defaults Billing Date at line item to 30th June 2014
Now when i do GRN suppose on 1st July 2014 for that line item , system should trigger a code where in check the posting date of the GRN and override the same in the Biiling Date field of the sales order line item
So when VF04 is run for a month All the GRN which are recieved in the month of July are invoiced in July
Please share me your thoughts do we need to check any userexits from MM side which reads the posting date of GRN and then copies in to my third party sales order
Regards
Hiba

Unable to copy the Price Modifiers associated with a Sales Order Line

Dear All,
I am copying Sales Order Line using the process_order API. I was not able to copy the Price Modifiers associated with the Lines. How can I accomplish this..?
Is there any API available for copying the Price Modifier info associated with the Sales Order Line..?
Environment is 11i and OS is SUN Solaris
Please update...
Many thanks in advance..

Hello All,
Please let me know is this possible to have the list of Invoices for an associated Sales Order.
Thanks,
Abdul

Add new line item in VA02 by copying same Order line details

Hi All,
I've a requirement where i need to add new line items in the Sales Order (T Code VA02) with reference to the same Order lines . For e.g an Order 80000100 which has 2 line items and the requirement is to create a new line i.e. line item 0030 by copying the details from the existing line item 0010 of the same order .
I've checked the BAPI - BAPI_SALESDOCUMENT_COPY which is for Order Creation T Code VA01 . I'm looking out for Sales Order Change BAPI where i can give the reference as Order no and Order line item which will create a new line item in the same Order with the same details of the reference Order line item .
Do let me know your thoughts !!!!
Thanks,
Bintu

Hi -
Please check these two FM's BAPI_SALESORDER_GETDETAILBOS & BAPI_SALESORDER_CHANGE.
Regards,
Atul Mohanty

Copying text from CMIR (KNMT) to the Sales Order Line Item

We need to copy text from the CMIR (KNMT) to the Sales Order Line Item with two steps in the access sequence. First to look up by the Ship to Partner Function. If doesn't exist, then look up by Sold to Partner Function. Have setup a new text id (ZPRN), a new access seq (9011). The access seq has one seq =5 for KNMT, ZPRN, all languages and that saves fine. When I set the Partner Function to be SH. I get the following error msg:
"The Language does not come from the partner function AG for MVKE".
Any ideas? This access seq does not reference MVKE. It only references KNMT.
Thanks!

Hi Lisa,
Just stumbled on this post, as I am searching for something similar.
What you are attempting to do isn't possible in config.
This is because as standard Customer Material Info Records are not even considered for ship-to party in the sales order.
They work for sold-to only.
Therefore, this funny error message is SAP's way of saying, "Why are you trying to enter a partner here, because the data is determined for sold to only?"
You can change this with development for other fields (ie, to determine delivery plant, tolerances etc at ship-to) by using
the exit MV45AFZB with the USEREXIT_CUST_MATERIAL_READ form.
However, even if you do this, Text Determination is still sold-to only and still doesn't behave.
I am currently looking myself for a solution for this problem and I will let you know what I find.
Cheers
Chris

Report on Orders that have Order Lines modified during the period

hi,
I am a Beginner, PLEASE I NEED A HELP
Report on Orders that have Order Lines modified during the period

I don't know a standard report (SE95 does not seem to include selection by date), maybe you can tweak SE16 display of table SMODILOG for your purpose.
Thomas

ATP after Sales Order Line Item Configuration

Hello experts,
I have a question regarding the ATP at the time of Sales Order entry. I am in the process of creating a technical spec for creation of program that looks at the lowest level of BOM explosion. Here are the details:
1) It is a MTO environment using VC BOMs and Routings.
2) At the time of Sales Order entry, and after the line item is configured, the user must have the visibility of the raw material resulted from BOM explosion before Sales Order is saved.
3) What my issue is how to retrieve the lowest level of BOM explosin as a result of SO line item configuration.
I appreciate any lead that can be provided.
Newoxford

Sorry for a partial post. Some button !
Hello Newoxford
Did not quite get your issue.
How the sales order item is exploded depends on the Config Profile (VA42) for that material. In the tab ' Confign Initial screen' and subtab " Confign Parameters' , you have the ability to specify multilevel BOM explosion. Also in the item cat , you need to specify the structure scope as B-Explode multi-level bill of material.
If you do this, after the item is configured in the order, it will be exploded as needed.
With respect to ATP, do you want to check the lowest level for availability? if so, that item should be relevant for delivery and should have appropriate Sched Line and all the requisite config.
And my question to you is all this is through config, master data etc, then what are you trying to accomplish with your program?

How to Trap Order Line cancle event?

Hello,
I need to design a interface which will send the sales order line information whenever a order line get cancelled.
Now question is where should I add this interface program to achive real time processing.
Thank You.

Vipin,
The Oracle White Paper 'Business Events in Oracle Order Management' (May 2009, Srecko Bartl, Sarath Nimmagada, Vaibhav Kapoor - see MySupport Note 113492.1) will give you chapter and verse on this.
Regards,
Jon

How to configure third party order ?

how to configure third party order ? and how the business know that the customer has received the goods so that invoice to be raised?

hi shoban,
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1) After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always followwing a third party process for a material then you have to create the material using item category group BANS.
The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).
step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination
ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat
OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevnat for billing indicator as F
step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.
Hope it helps
Mastan

User exit for changing Sales order lines.

Hello experts ,
I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE" but it does not seems to do the job.
What is the name of user exit that i have to use for this task and which structure should be used, is it xvbap ? is it vbap ?
Thanks for the help.
Avi.

Hi,
find the user exit u required.
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
Best regards,
venkatawamy.y

Need to Split Sales Order Line Item in VA01

Hi,
I have a requirement in which i have to split an order line item for KMAT materail number. system popup configurable screen, here all the required characteristic values have to be selected as per the customer requirement.
After entering all the required customer specific characteristic values, system determines batch automatically. If characteristic values of the Batch matches with the characteristic values of configurable screen selected in the sales order
Here also we have to check the sales Order Quantity (VBAP u2013 KWMENG) and order Confirmed quantity (VBEP u2013 BMENG), if the both the quantities are not same, consider order has partially confirmed.
If Order quantity is partially confirmed, check for the batches with the same characteristic values of the quotation configurable screen and if batch found, system has to create a one more line item and new batch has to be assigned to create line item.
Reduce the order quantity equal to the confirmation quantity in the first line item.
Create a new line item in the quotation, copy all the remaining unconfirmed quantity from the first line item and also copy all the characteristics and properties (item category, schedule line category, business data, item data, and requirement type) and assign the batch to the new line item. System does the availability check automatically and confirms.
In another scenario system doesnu2019t find batch, in this case capable to promise has to trigger directly.
Here we have to check the Order confirmed quantity, if confirmed quantity is equal to zero.
Change the item category of the line item, due to which system determines different Requirement type and schedule line category.
Based on the Requirement type system triggers the capable to promise.
I would lke to know which is the suitable user eixt or BADI to split the line items and what all the tables or structures i need to populate in order to create a new line item successfully.
I have seen many post in sdn but no body gives the right user exit name where i can add new line item.
Regards,

Hi Amit,
Thanks for your reply. In this scenario configurable material is involved. And first Make to Stock scenario is executed to check any material with customer entered characteristics are avialable. If its so it will determine its batch and assigned the quantity.
If zero quantity is assigned or no quantity is assigned then I have to trigger the Make to Order scenario for rest of unconfirmed quantities in order.
I have check it in USEREXIT_MOVE_FIELD_TO_VBAP but it was of no use. I even tried in USEREXIT_CHECK_VBAP but still no result. I am not sure what all the tables and structures i need to populate there.
Regards,

Configurator events during order line copy

Similar Messages

Maybe you are looking for