Warning message display for Price check-Sale order creation

Hi,
While creating sales order at line item level a warning message is required to pop-up after validating if the sale order line item's Net Price = Gross Price.
1.Is there any IMG customization that can be done to acheive this? If Yes, how??
2.If it can be done only by adding a required message to message class, could you pls tell me the form which may require modification??
Thanks

Hi,
Develope the logic in any of the following userexits avaialble in the program-
MV45AFZB
MV45AFZB
The requirement cannot be processed through Standard SAP behaviour.
Regards
Goutham

Similar Messages

Get condition prices before sales order creation

Hi Experts,
I have a non-SAP system which needs price information from SAP.
As we know, in SAP after Sales order creation, the prices can be found in item condition tabs. All condition records and prices can be found.
Now, before the non-SAP system sends data to SAP for sales order creation, non-SAP needs the condition record and prices same as after sales order creation.
seems i have to write code in SAP for the logic of price determination. i assume that will be a big work.
so i'm supposing whether we can get the condition from the bapi for sales order creation. i can mask testrun = 'X', then get the conditions. but i tried creating sales order in code and found the condition - ORDER_CONDITIONS_IN is not populated.
anyone got a idea to solve this?
Thanks a lot.
Legend Lee.

Hi,
If you run the BAPI under the same conditions but without the text flag checked do you get anything returned? Are there any messages in the RETURN table?
There are a number of OSS notes on this BAPI e.g. 93091 if you search on service.sap.com. The answer may lie in the pricing configuration; that the BAPI is not designed to work how you want it to work or a parameter has not been specified correctly. You could look at FM SD_SALESDOCUMENT_CREATE and try and use that however it is not released. Unfortunately I canu2019t give you a definitive answer or solution.
Regards, David

Capture the purchase price during sales order creation

Hi,
User wanted to capture the item purchase price when a sales order is raised.
Currently, the sales order capture the VPRS whcih is coming from the material valuation (MAP) price.
Is there a standard condition type that will captured the purchase price in the PIR record or the PP condition?
Thanks

Hi
As far as i know it is not possible to fetch the purchase price in sales order.
May be you can define an another condition type asa statistical and maintain the condition records for that. But it will be a tedious job for maintaining all the things.
regards
Prashanth

Workflow for Delivery from Sales Order Creation

Hi All,
I am new to SAP workflow. There is a requirement to create a delivery through VL04 (in background) based on the Shipping Point of the approved Sales Order. How can this be done? I am assuming that I should be using BUS2032 for the Sales Order and BUS2015 for the Delivery.
The first step should be to send an email that gives the user two options (Approve and Reject) once a Sales Order is saved. However, I am unsure of how to pass parameters to VL04 and submit the program.
For example, if the order is approved the Shipping Point will be passed to VL04 and run in background to create the delivery. How can you determine the Shipping Point from BUS2032? I did not see any attribute for this within the BOR. Also, how do you create the step to submit that Shipping Point to transaction VL04 in background?
Any help you can give would be greatly appreciated. Thanks.
John

Hello,
You could try using a BDC with VL04 but first preference would be to see if there are any BAPI functions (search for BAPI) that can do this.
If BUS2032 doesn't have an attribute that you want (eg shipping point) then sub-delegate to ZBUS2032 and add the attribute, it's straightforward. You just have to know how to determine the value programmatically.
regards
Rick Bakker
hanabi technology

Selling pricing superceed scale price in sales order creation

Hi all,
I have a scenario as below.
Material A has maintain 3 pricing condition as below.
1. Selling price (PR00)
material A : normal selling price(PR00) = $2.00.
2. Free goods
material A : free goods -> 12 + 2 (exclusive free items)
3. Scale pricing
material A : scale pricing -> 12 items = $ 1.80
6 items = $1.00
3 items = $ 0.80
If the customer buying 12 items, he will be given 2 items free, the 12 items will be charged for rm2.00(normal selling price) instead of scale price $1.80.
Meaning to say if there's a free goods determine, i need the items to be charged with normal price instead of taking scale price.
How can I do this? I need this urgently.
Kindly advise.
Thanks!

Hi,
Please check if you use inclusive in free goods determination then the price will be picked $2.00 but in exclusive that is 102 or 122 you will get $1.80only, check this and confirm.

Need to write BDC program for Transaction VA01(Sales order creation)

Dear Friends,
I need to write a BDC program for uploading data into sap from an excel sheet file. The data contain Material Description,Customer Name,Date of Delivery,Quantity,Unit of measure etc.
material desc customer date of delivery quantity unit of measure
abcdf xyz ltd 24.12.2011 2 4 gm
The transaction is VA01.How will I find the correct fields and related tables? What are the related fields needed in the transaction VA01.
Thanking you
Sacheen Pukhrambam
Moderator Message: Put some self-effort before posting your question. Thread locked.
Edited by: Suhas Saha on Nov 25, 2011 1:25 PM

Hello,
You could try using a BDC with VL04 but first preference would be to see if there are any BAPI functions (search for BAPI) that can do this.
If BUS2032 doesn't have an attribute that you want (eg shipping point) then sub-delegate to ZBUS2032 and add the attribute, it's straightforward. You just have to know how to determine the value programmatically.
regards
Rick Bakker
hanabi technology

Condition types in Sales order creation process

Hi Friends...
While creating the sales order with BAPI,
What is the condition type i have to pass for pricing procedure...
There many condition types for my pricing procedure, which one o have to select...
Some of them are mannual, and other reuired, which one I have to pass?
I want the information related to this condition types.., as here no SD consultant availble for me.
Sales order creation, Line item error
Thanks,
Naveen.I

Hi Friends...
Please let me know is it mandatory to give condtion type while creating the sales order...?
I am using BAPI_SALESORDER_CREATEFROMDAT2 to create my sales order...
http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Thanks,
Naveen.I

Check sales order exits for category ZTAC

Hi Experts
I have a requirement to modify the iDOC interfaced program,
In the routien which checks for the existence of a production order, I have to modify the following
1. Inspect each item on the sales order
2. If (and only if) there is atleast one item with a category of "ZTAC" then check for a production order otherwise processing the order in the usual manner.
Could anyone tell me how to check (Is there a sales order) if no then display error message if yes then is there a production order if no display error message if yes Create confirmation .......................
I want to know how to write a coding to check sales order exits from table VBAP,VBAK Etc., .
Thanks in Advanced
Regards
Piroz

Hi Prabhu
Thanks for your email and response but I need to check this in program for IDOC ....Modification
Insert code in this way
check sales order for category = 'ZTAN' inspect for each item on sales order
and if you found item with cateogry ZTAN then check for production order otherwise go asual manner
I WANT TO WRITE A CODING HERE **********************
if production order required then check
                for each item on sales order item list
                      with item category = 'ZTAC' then
                                 return true
                            next
                              end function
VBAP TABLE field VBELN and PSTYV (ZTAC,ZTAN Etc)
Eg of coding
if lva_saleord is initial
        select single * from vbap into l_saleord
          where vbelv = lva_saleord
          and   vbeln = lva_vbeln and
          exit.
        endselect.
      endif.
I want to write a small program in between to check the sales order exits if it is then I have to go to deliveries ...................
Regards
Eslam

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

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

While raising Leave Request on ESS: getting warning message displayed

Hi All,
When i am trying to raise a leave request from ESS i am getting the warning message displayed on the page as follows:
"Customizing for employee 00001153 does not exist"
I want this message to be removed.
Is this problem from R/3 end or any configuration needs to be done on ESS ?
Pls let me know how to remove this message.
Regards
Vijay

this message ensues when there is a missing customisation for the pernr, For example :
message is being displayed due to rule group customizing is missing
for a leave '0560' for which a leave record exists on the date
'14th March 2008'.
One possible solution would be to create a record in the customizing or delete the record from the application.
So please check the customisation of the absences, Quotas, rule group etc for this particular employee

Issues in Web service created for updating the Sales Order

Hi All,
We created a Web service using the Web service tool in CRM 7.0 ( Using the Component WS_DESIGN_TOOLS )
Web service was created for three modes such as READ, CREATE and CHANGE Modes.
READ Web Service we tested and its working fine as we were able to see the data for an existing Sales Order in the Web Service.
We expect that the Change Web Service will update the data of an existing Sales Order.
Through our Web service we are passing the Order GUID ,Order ID and some Header Fields as well as Item Fields but the in the Web Service we are getting a message that Web service executed successfully but the CRMD_ORDERADM_H Table isnot getting updated.
What could be problem.
Any suugestions will be highly appreciated.
Regards,
Sijo

Hi Gourav,
I checked in SICF for the Webservice name created.
this is the service path
/default_host/sap/bc/srt/rfc/sap/ for the corresponding Web Service created in DEV 200 Client.
I checked in SOAMANAGER and saw that the endpoitnts were zero.
the Search Operation for Webservice have got three query fields mainly
Object Id, Posting Date,Procees Type
If we give Process Type
sign - blank
option - blank
low - YPO ( Custom )
High - blank we are getting 126 entries.
and if we check for the Process Type YPO (Custom ) in CRMD_ORDERADM_H Tbale also we are getting the same no of entries.
but only for option BT , for Posting Date issue is thr..
Any inputs to move forward will be highly appreciated.
Regards,
Sijo.
Edited by: sijokjohn85 on Mar 5, 2010 10:52 PM

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.

Prerequisites for archiving the sales order

Hi ,
What are the prerequisites for archiving a sales order? What is the last business transaction from which the archiving process is triggered? Is it necessary to set status CLSD on the sales order for archiving ? what are the other system statuses that should be set for archiving a sales order?
Thanks & Regards
San

Hi Santosh,
Sales Order is linked to other subsequent documents in the Order Processing cycle like Delivery, Invoice , Shipments, etc. So, we've to make sure that all the dependencies are removed before we can start to archive an SO.
You can see the dependencies in SARA Transaction (Goto->Network Graphic).
The SO archiving program checks if the status of the subsequent documents are Completed or not. (status in VBUK table is "C") .
There are other options like Residence Time, Existence of PO , Existing of Accouting Doc.
You can select the options, based on your company's decision regarding the extent of SO archiving they wanted to achieve.
The program will throw the messages appropriately, based on the checks it performed and appropriate actions can be taken from the document side .
This is a link , which explains the checks the program does before archiving.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/a9/55c7d490a111d1a5510000e82deaaa/content.htm
Regards,
Shail.

For non valuated sale order

Hi Freinds,
I got the following error while doing customization for Non-valuated sale order. In the Requirement class i selected the 40 and went in to details and have not selected any thing in the field Valuation which means i want to have "Non valuated" sale order.
Only special stock with separate valuation can be marked.
Message no. VT387 Diagnosis It is only possible to price and mark for valued special stock, with reference to a sales document or a project. System Response Procedure Procedure for System Administration
Any ideas in this regards, kindly share with me.
Thanks in advance
Regards
siva

thanks

Warning message display for Price check-Sale order creation

Similar Messages

Maybe you are looking for