Last Price for Sales Order History

Hi Friends,
I have a requirement in LSMW, where i have to upload Sales Orders data into SAP to convert Customer
and Material price points for the past X months.
Is there any SAP standard program or BAPI available for this requirement?
Thanks in advance.
Murthy

Similar Messages

How to mark up the price for sales order entry?

Hi Gurus,
How to Mark up the price for sales order entry?
Example: Item Price: $10, Adding 20% Margin
Selliing price of the item is $12
we are giving many typs discounts like festival Discount, customerwise, Order value wise etc..
After giving above discounts, if discount falls below $10 system should not allow to book the order, Trigger should go to respective person or sales person saying that item price falling below cost, system should not allow to book the sales order.
How to configure this scenarios in Order management Module, appreciate your inputs, advise.
Regards
AK

Thanks for your response,
can you please guide me step to achieve this requirement.
Regards
AK

Table name for sales order history

hi guys,
               I want to know the name of table which contains sales order history.
regards
neelesh

Hi
Use this code it will get all the details
Sales Order Changed History Display
Sales Order Changed History Display
You can execute the report by :
1. Change Date
2. User Name
3. Sales Order Number
Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff
               http://www.sap-img.com
REPORT ZSDCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADING
                 LINE-COUNT 065(001)
                 MESSAGE-ID VR.
TABLES: DD04T,
        CDHDR,
        CDPOS,
        DD03L,
        DD41V,
        T685T,
        VBPA,
        TPART,
        KONVC,
        VBUK.
DATA: BEGIN OF ICDHDR OCCURS 50.
        INCLUDE STRUCTURE CDHDR.
DATA: END OF ICDHDR.
SELECT-OPTIONS: XUDATE FOR ICDHDR-UDATE,
                XNAME FOR ICDHDR-USERNAME,
                XVBELN FOR VBUK-VBELN.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.
PARAMETERS: SUDATE RADIOBUTTON GROUP R1,
            SNAME RADIOBUTTON GROUP R1,
            SOBID RADIOBUTTON GROUP R1.
SELECTION-SCREEN END OF BLOCK BLK1.
DATA: WFLAG,
      WCHANGENR LIKE CDHDR-CHANGENR,
      WUDATE LIKE CDHDR-UDATE,
      WNAME LIKE CDHDR-USERNAME,
      WVBELN LIKE VBUK-VBELN,
      WDEC1 TYPE P DECIMALS 3,
      WDEC2 TYPE P DECIMALS 3,
      WDEC3 TYPE P DECIMALS 3,
      WDEC4 TYPE P DECIMALS 3.
DATA: UTEXT(16) VALUE 'has been changed',
      ITEXT(16) VALUE 'has been created',
      DTEXT(16) VALUE 'has been deleted'.
DATA: BEGIN OF ICDSHW OCCURS 50.
        INCLUDE STRUCTURE CDSHW.
DATA: END OF ICDSHW.
DATA: BEGIN OF ITAB OCCURS 10.
        INCLUDE STRUCTURE CDSHW.
DATA:   UDATE LIKE CDHDR-UDATE,
        USERNAME LIKE CDHDR-USERNAME,
        CHANGENR LIKE CDHDR-CHANGENR,
        VBELN(10),
        POSNR(6),
        ETENR(4),
        INDTEXT(200),
END OF ITAB.
SELECT * FROM VBUK WHERE VBELN IN XVBELN.
CLEAR CDHDR.
CLEAR CDPOS.
CDHDR-OBJECTCLAS = 'VERKBELEG'.
CDHDR-OBJECTID   = VBUK-VBELN.
PERFORM READHEADER.
PERFORM READPOS.
LOOP AT ITAB.
    CASE ITAB-TABNAME.
      WHEN 'VBPA'.
        IF ITAB-FNAME = 'KUNNR' OR
           ITAB-FNAME = 'LIFNR' OR
           ITAB-FNAME = 'PARNR' OR
           ITAB-FNAME = 'PERNR' OR
           ITAB-FNAME IS INITIAL.
         MOVE ITAB-TABKEY TO VBPA.
         SELECT SINGLE * FROM TPART WHERE SPRAS = SY-LANGU
                                   AND   PARVW = VBPA-PARVW.
         IF SY-SUBRC = 0.
           REPLACE '&' WITH TPART-VTEXT INTO ITAB-INDTEXT.
         ENDIF.
       ENDIF.
     WHEN 'VBAP'.
       IF ITAB-FNAME IS INITIAL.
         REPLACE '&' WITH 'Item' INTO ITAB-INDTEXT.
       ENDIF.
     WHEN 'KONVC'.
       MOVE ITAB-TABKEY TO KONVC.
       SELECT SINGLE * FROM T685T WHERE SPRAS = SY-LANGU
                                 AND   KVEWE = 'A'
                                 AND   KAPPL = 'V'
                                 AND   KSCHL = KONVC-KSCHL.
       IF SY-SUBRC = 0.
         REPLACE '&' WITH T685T-VTEXT INTO ITAB-INDTEXT.
       ENDIF.
     ENDCASE.
     IF ITAB-INDTEXT(1) EQ '&'.
       REPLACE '&' WITH ITAB-FTEXT(40) INTO ITAB-INDTEXT.
     ENDIF.
     IF ITAB-CHNGIND = 'I'.
       REPLACE '%' WITH ITEXT INTO ITAB-INDTEXT.
     ELSEIF ITAB-CHNGIND = 'U'.
       REPLACE '%' WITH UTEXT INTO ITAB-INDTEXT.
     ELSE.
       REPLACE '%' WITH DTEXT INTO ITAB-INDTEXT.
     ENDIF.
     CONDENSE ITAB-INDTEXT.
     MODIFY ITAB.
   ENDLOOP.
ENDSELECT.
IF SUDATE = 'X'.
SORT ITAB BY UDATE VBELN POSNR ETENR.
ELSEIF SOBID = 'X'.
SORT ITAB BY VBELN POSNR ETENR UDATE.
ELSE.
SORT ITAB BY USERNAME VBELN POSNR ETENR UDATE.
ENDIF.
LOOP AT ITAB.
CLEAR WFLAG.
IF SUDATE = 'X'.
    IF WUDATE NE ITAB-UDATE.
      SKIP.
      WRITE:/001 ITAB-UDATE,
             023 ITAB-USERNAME,
             037(10) ITAB-VBELN.
      WFLAG = 'X'.
      WUDATE = ITAB-UDATE.
      WCHANGENR = ITAB-CHANGENR.
    ENDIF.
ELSEIF SOBID NE 'X'.
    IF WVBELN NE ITAB-VBELN.
      SKIP.
      WRITE:/001 ITAB-VBELN.
      WVBELN = ITAB-VBELN.
    ENDIF.
ELSE.
    IF WNAME NE ITAB-USERNAME.
      SKIP.
      WRITE:/001 ITAB-USERNAME.
      WNAME = ITAB-USERNAME.
    ENDIF.
ENDIF.
IF WCHANGENR NE ITAB-CHANGENR.
    WRITE:/023 ITAB-USERNAME,
           037(10) ITAB-VBELN.
       WFLAG = 'X'.
       WCHANGENR = ITAB-CHANGENR.
    ENDIF.
    IF WFLAG = 'X'.
      WRITE: 013 ITAB-CHNGIND,
             049 ITAB-POSNR,
             057 ITAB-ETENR,
             065 ITAB-INDTEXT(60).
    ELSE.
      WRITE: /013 ITAB-CHNGIND,
              049 ITAB-POSNR,
              057 ITAB-ETENR,
              065 ITAB-INDTEXT(60).
    ENDIF.
WRITE:/065 ITAB-F_OLD.
WRITE:/065 ITAB-F_NEW.
ENDLOOP.
FORM READHEADER.
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
       EXPORTING
            DATE_OF_CHANGE    = CDHDR-UDATE
            OBJECTCLASS       = CDHDR-OBJECTCLAS
            OBJECTID          = CDHDR-OBJECTID
            TIME_OF_CHANGE    = CDHDR-UTIME
            USERNAME          = CDHDR-USERNAME
       TABLES
            I_CDHDR           = ICDHDR
       EXCEPTIONS
            NO_POSITION_FOUND = 1
            OTHERS            = 2.
CASE SY-SUBRC.
    WHEN '0000'.
    WHEN '0001'.
      MESSAGE S311.
      LEAVE.
    WHEN '0002'.
      MESSAGE S311.
      LEAVE.
ENDCASE.
ENDFORM.
FORM READPOS.
LOOP AT ICDHDR.
    CHECK ICDHDR-UDATE
                        IN XUDATE.
    CHECK ICDHDR-USERNAME
                          IN XNAME.
    CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
         EXPORTING
              CHANGENUMBER      = ICDHDR-CHANGENR
              TABLEKEY          = CDPOS-TABKEY
              TABLENAME         = CDPOS-TABNAME
         IMPORTING
              HEADER            = CDHDR
         TABLES
              EDITPOS           = ICDSHW
         EXCEPTIONS
              NO_POSITION_FOUND = 1
              OTHERS            = 2.
    CASE SY-SUBRC.
      WHEN '0000'.
        LOOP AT ICDSHW.
          CHECK ICDSHW-CHNGIND NE 'E'.
          CLEAR ITAB.
          MOVE-CORRESPONDING ICDHDR TO ITAB.
          MOVE-CORRESPONDING ICDSHW TO ITAB.
          CASE ITAB-TABNAME.
            WHEN 'KONVC'.
              MOVE ICDHDR-OBJECTID TO ITAB-VBELN.
              MOVE ICDSHW-TABKEY(6) TO ITAB-POSNR.
            WHEN OTHERS.
              MOVE ICDSHW-TABKEY+3(10) TO ITAB-VBELN.
              MOVE ICDSHW-TABKEY+13(6) TO ITAB-POSNR.
              MOVE ICDSHW-TABKEY+19(4) TO ITAB-ETENR.
          ENDCASE.
          MOVE '& %' TO ITAB-INDTEXT.
          APPEND ITAB.
          CLEAR ITAB.
        ENDLOOP.
      WHEN OTHERS.
        MESSAGE S311.
        LEAVE.
    ENDCASE.
ENDLOOP.
ENDFORM.
TOP-OF-PAGE.
WRITE:/ SY-DATUM,SY-UZEIT,
       50 'SALES ORDER CHANGE HISTORY',
      120 'Page', SY-PAGNO.
WRITE: / SY-REPID,
         60 'SALES ORDERS STATISTICS'.
SKIP.
ULINE.
IF SUDATE = 'X'.
WRITE:/001 'Change Date',
         013 'Time',
         023 'User Name',
         037 'Sale Order',
         049 'Line',
         057 'Sch No',
         065 'Changes'.
ELSEIF SOBID = 'X'.
WRITE:/001 'Sale Order',
         013 'Line',
         021 'Sch No',
         029 'Change Date',
         041 'Time',
         051 'User Name',
         065 'Comment'.
ELSE.
WRITE:/001 'User Name',
         015 'Time',
         025 'Change Date',
         037 'Sale Order',
         049 'Line',
         057 'Sch No',
         065 'Changes'.
ENDIF.
ULINE.
*--- End of Program
Regards
Shiva

Prices for sales order

hi all
I want to create different prices for different sales order under same contract. The service materials is the same. Does the system allow me to link price to a particular sales order instead of a contract.
Advice me.
cheers
shalsa007........

Hi
You can do this by giving the price manually when you create Order.
If the system does not allow you to enter price manually, then you need to Maintain
'C' Manual entry has priority in the Condition type Under Changes which can be made Tab.
Regards,
Sree

Need different price for sales order and billing document.

Hi,
I'm having a scenario.I have created a sales order for a material,the order value is $100.I have done up to Delivery.Billing part is only remaining in the flow.Unexpectedly the price of the material increases $20 more.Customer is ok with the new price $120.So how the new price comes in billing document.For this what are all the steps i want to configure?
Regards
Raj

I want to know from you is client entering price manual or condition records maintained, if it is manual.you can go billing in the item pricing condition click on update field and select B i.e carry out new pricing.& enter the current price manually.

Minimum Price for Sales Order

Hi Gurus,
We want to implement a price check, so that vbap-netwr cannot be under a certain value.
(Like a kind of PMIN).
But PMIN is not practible as we want to add additional authority-checks.
Which user exit or enhancement can be used to achieve this.
Any sample cadingn would be appreciated.
Thanks
Dieter

Hi
Use VOFM condition value. See the condition 014 'best value' as a simple sample. Perhaps you can set other condition and set it as statistical to do the comparations in the subroutine.
I hope this helps you
Regards
Eduardo

Question about table of Sales Order History?

Dear All,
In SAP B1 SP01, when I click "Tools" --> "Change log", it will display what is the different between previous version.
May I know which table is for sales order history?
From Samson

Table is ADOC, objtype is 17
select * from adoc where objtype = 17 and docentry = XX
where XX is docentry of sales order

Report for Sales Order Change History CDPOS and CDHDR

How to take a report of the data for the Sales Order Change history for a particular period of time. It is required to take a report of all the Sales Orders for which the basic price has been changed. Please let me know the procedure. I could not get the data from the table CDPOS and CDHDR
Helpful answer would be rewarded.
Regards
Praveen

Dear Praveen Kumar
Have you tried with VBAP where sale order details at item level would be stored.
Moreover, to my knowledge, there won't be any changes as for as pricing is concerned at sale order level but there is at billing level. Normally, any price increase / decrease would reflect in billing. So why dont you to table join through SQVI VBAP (for sale order details) and VBRP (for billing details) so that you can compare the selling price in sale order with billing.
Thanks
G. Lakshmipathi

Planned material price in case of production order for sales order (MTO)

Hi,
In case of production orders created for sales order, the planned price for a component (BOM) material gets picked as per following:-
1. If there is no entry in EBEW for the component (that is, there is no previous GR for the component) for that sales order, then plan price is picked up on the basis of planned costing variant.
2. In case there is an entry for the component in EBEW (there has been a previous GR for the component with reference to the sale order) then the plan price for the component is taken from the EBEW table (first GR price) and system ignores the costing variant.
The above is as per my observation. Please validate if this is correct or not.
The requirement is that even if there has been a previous GR for the component (there is an existing entry in EBEW) the system should take the plan price on the basis of costing variant and not from the EBEW table.
How can this be achieved? Is there a user exit that can force the system to read the costing variant before looking into the EBEW table?
BR
Abhi

Hi Ajay,
Yes i had considered it but I'm not sure If it will help.
Because the main problem here is that system is ignoring the costing variant itself and instead picking the price from EBEW table. So changing the costing variant (validation variant) may not help.
Moreover i don't want to valuate with my own strategy. I want the plan price to be equal to standard price of material from material master. Basically MBEW instead of EBEW.
Any clues?
BR
Abhi

Hide Unit price from sales order for sales user without change authorization of document setting

Hi all expert
Hide Unit price from sales user without change authorization of document setting.
I have also refer this note
SAP B1 2005 Purchas Order,Good Reciept PO'S, and Unit Price Block
but sill I had not getting my proper solution.
I want to restrict sales person to see & access unit price. Here I know option of block authorization of document setting but its not good option because , In future ,if sales user wants to changes forms setting in future so Its become problematic for user. so I want do this without restrict user for form setting & only hide unit price table from him/her. also He/her able to access form setting with out unit price.
Please reply
Amol Nikam

Hi Experts,
Please Tell me Is there any option "Hide Unit price from sales order for sales user without change authorization of document setting"
Regards/Thanks
Amol

Need to pull INITIAL(vbap)net price of Sales Order, after changing viaVA02

Hi Experts,
Mine is differetnt requirement..........
I created a my_Sales_order_12345678 with 2 items, as follows,(all following values/entries r for my_Sales_order_12345678)
line item_10---->net_value_netpr = $100
line item_20---->net_value_netpr = $200
Then the VBAP entries as r as follows,
POSNR -
>NETPR
10----
> $100
20----
> $200
I changed first time as via VA02 tx, as
line item_10---->net_value_netpr = $300
line item_20---->net_value_netpr = $400
Then the VBAP entries as r as follows,
POSNR -
>NETPR
10----
> $300
20----
> $400
I changed second time as via VA02 tx, as
line item_10---->net_value_netpr = $500
line item_20---->net_value_netpr = $600
Then the VBAP entries as r as follows,
POSNR -
>NETPR
10----
> $500
20----
> $600
My requirement: for some reason, I need the initial values, I mean
the VBAP entries of,
POSNR -
>NETPR
10----
> $100
20----
> $200
I tried with CDHDR & CDPOS tbls, but no use? So, from Where Can I get/pull them??
thanq
Edited by: Srinivas on Jan 24, 2008 12:22 AM

hi sirnivas..
Thanq you for the points..these are the first i ever recieved..
if you are working on peice of code which can get the price history do me a favour if you have finished the code just explain it to me who did u do that...
i have been working on an object from last two weeks to get the latest price...
the thing is even though the price for condition items has been changed it wont get updated in the Sales orders unless new pricing fot the document is done...
so i have to get all the sales orders who condition items price has been changed and display them in an ALV...so if you can get the exact old values...for the conditions i guess the opposite also can be done.....
Here i have suggestion for you...in condition items there is a process called SCHEMA ( pricing Schema) which you can see using Condition Analysis button at the bottom of the condition item window...
you can see all the price changes to the condition when you parse the tree structure of the procedure..EXAMPLE :- R0000 etc...
so some Sales orders if the Schema has been changed all the existing condition are replaced by New ones from the changed Schema...so i guess that would play an important role in deciding the Price of Sales order...
I know this is bit long but .....if you did finsish your program do let me know how you did it...
Thankyou very much and good luck.

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

User exit for additional data B for sale order item .

Hi., all
my client requirement is
( This business requirement will make the Last Price for a given item be visible during order entry. )
u2022Retrieve & display during order entry, the most recent unit price given to a customer for a specific item, from the Billing data.
. Display the Last Price under Additional Data B Screen
add new field (last extended price) in additional data b screen.
after that 1.     Using the Sales Order Material Number (VBAP-MATNR), Sales Order Sales Organization (VBAK-VKORG), Sales Order Distribution Channel (VBAK-VTWEG), Sales Order Division (VBAK-SPART), Sales Order Sold-to Number (VBPA-KUNNR for VBPA-PARVW=u2019AGu2019) to access the Billing Items By Material Index Table (VRPMA) and specify a billing date (VRPMA-FKDAT) of less than 60 days from current Sales Order requested delivery date (if specified at header VBAK-VDATU or at the schedule line level (VBEP-EDATU). This will result in all the billing documents where the Sold-to bought the item but isnu2019t completely refined as of yet. Retain the billing document (VRPMA-VBELN), item (VBPMA-POSNR), and billing date (VRPMA-FKDAT) in a temporary table to pass to number 2 as the input.
2.     Use the billing document (VRPMA-VBELN) and item (VRPMA-POSNR) to read the Sales Document Partners Table (VBPA) where the partner function (VBPA-PARVW = u201CSHu201D) and the Sales Order Ship-To (VBPA-KUNNR for VBPA-PARVW=u2019WEu2019) to select ONLY billing documents that are for that given ship-to location. This filters out only billing documents relevant for that ship-to location.
3.     From the resulting list of billing documents, select the most recent date (VRPMA-FKDAT) which will refine the search for the last Billing Document (VRPMA-VBELN) and item (VRPMA-POSNR).
4.     Using the most recent Billing Document (VBPA-VBELN), access the Billing Document Item Table (VBRP). To result in the Last Extended Price as VBRP-KZWI1.
5.     This price will be an extended price which needs to be calculated as a u2018unit priceu2019. For this billing item, select the sales unit (VBRP-VRKME) to determine if the sales unit is in cases or eaches.
a.     If the unit of measure is in cases, then simple math is required to divide the Last Extended Price (VBRP-KZWI1) by the billing quantity (VBRP-FKIMG). Standard rounding should apply when .005 results in a .01.
how to achive this ?

Hi Chakravarthy,
use the Exits provided in SAPMV45A -includes MV45*ZZ and screen exits as well 8309 8310 8459, 8460. Just be sure to
use zznnnnnn include in the SAP provided forms instead of coding directly in the forms.
You can check below user exits:
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.
Reddy

Surcharge rate for sales order item condition

Hi,
I have a two condition for sales order item.
First condition is ZP00-Price. It is using for automatically price with customer and material. It linked with account key in pricing procedure.
Second condition is ZI00-Index rate. Calculation type is A-Percentage. This condition value is monthly. It will be used for surcharge with percantage . I have a formule this condition.
It is not linked with account key in pricing procedure.
Formula for ZI00 - Index rate:
(Index Rate to delivery date - 1 / Index Rate to contract start date) x 100
For example;
Index rate conditions is entrying monthly;
Index date          Index%
01.08.2008         1,05
01.09.2008         1,15
01.10.2008         1,17
Contract start date = 03.08.2008
Delivery date = 02.10.2008
ZP00 = 500
ZI00 = Index rate for sales order item = ((1,17-1)/1,05 ) * 100 = 16,19
Last condition value = 500 + (500 * 16,19)/100 = 500 + 80,95 = 580,95
What can I do for this pricing?
Best Regards
Gulay Celik

Hi
I think that perhaps it is too late. The application supports cancellation and re-billing as separate transactions. Maybe this is not a 'development' problem.
Cheers
Dom

How to update the condition price in sales order while creating the invoice

Hi,
How to update the condition price in the sales order to carry out the new price while creating the invoice?
While creating the invoice it should update the condition price in sales order.
Thanks,
Balaram

No, pricing is not there in delivery.
I found an exit for VF01transaction where we can update the price in order.
Can you please tell me how to update the price if I have the order, material numbers and conditions number?
Thanks,
Balaram

Last Price for Sales Order History

Similar Messages

Maybe you are looking for