Activating Pricing for Sales Order in Retail

Hi All/Vijay/KK,
Please tell me how activate the pricing for sales order, actually in SD we do Pricing Determination, what has to be done for Retail pricing

Hi,
To do sales order pricing
Goto IMG>Sales & Distribution>Basic Functions>Pricing>Pricing Control
Either Follow Standard, condition type PR00
or in case of Custom
1. Use condition table 406 Site/article
2. Define Access Sequences ZPR0
Enter accesses:10 406 Site/article Exclusive x
3. Define Condition Types (ZPR0 assign newly defined access sequence)
4. Define And Assign Pricing Procedures (assign condition types ZPR0..etc. to it)
Then maintain condition record , go to VK11 --> Enter your Z condition type (eg. ZPR0)., enter the amounts.
Add the pricing procedure , to sales document type.
For Retail Sales Pricing
For Retail Sales Pricing based on Purchase pricing you can follow the following method:
The retail price is always based on the purchase net/net price. This purchase net price is built up from the purchasing pricing elements or condition types defined to be included in the purchase net price. A planned mark-up is applied to the purchase net/net to calculate the proposed retail price. The planned mark-up can be set by merchandise category and for exceptions, more specifically by article.
You can perform Two-step calculation for retail pricing, for example, for stores that are supplied by a distribution center (internal vendor). Calculating sales prices for the stores is based on the transfer price for distribution centers (preceding organizational unit).
1. Set up Master Data (WB02) - Relevant Fields should be maintained
2. Set up Article Master Data - Logistics DC and Store View (MM42)
Relevant Fields should be maintained
3. Maintain Mark up for DC(VK11) -Markup % at Distribution channel distribution chain level
Mark ups maintained at two levels:
For DC: At distribution chain level
Condition type used: AUFS
For Stores: At article level
New condition type ZUFS created.
4. Maintain Mark up for Stores (VK11) Markup % at Store distribution chain level
5 Create Pricing Procedures (IMG) -Pricing Procedures created
6. Carry out Price calculation for DC(VKP5) - Pricing Document created - DC Transfer price calculated
7. Carry out Price calculation for Stores (VKP5) - Pricing Document created - Final Retail Price Calculated
The final retail price that is calculated is stored in the condition type VKP0.
Hope it helps,
Regards,
Anirban Roy

Similar Messages

Back Calculation in Pricing for Sales Order.

Hello friends,
Please help me out with this below mentioned problem in the Pricing for Sales order.
I am creating a Contract with Customer and Plant from the same Region (State), while creating the subsequent Sale order I want to use the plant of some other Region which is different from the contract. In this case the pricing will change as there will be different Taxes (%) that would be applicable for different Region.
Now the requirement is that we want to use the Final Selling price which is calculated in the contract, therefore by keeping the Selling Price Fixed we have to backtrack and calculate new pricing accordingly.
An example for the same is explained below:
When Both Customer and Plant are from same Region:
     Particulars                        %           Value
A     Basic Value                                       100000
B     ED                     10.30%           10300
     Sum total (A+B)                                 110300
C     VAT                        5%            5515
     Sale Price (ABC)                                 115815
When Customer and Plant are from different Regions:
     Particulars          %           Value
D     Basic Value (A-B-C)                  92105
C     ED                        10.30%            9487
     Sumtotal (A-B)                  101592
B     VAT                          14%            14223
A     Sale Price                                       115815
Please reply with possible solutions.
Thanks and Regards,
Edited by: Lakshmipathi on Oct 4, 2011 5:41 PM
Thread Locked - Reason Cross Posted

Hi Nitin,
Go through the bellow links you can resolve your problem.
Re: Reverse Calculation in Pricing Procedure
Reverse Pricing???

BAPI or FM to Simulate Pricing for Sales order

Hi,
We are replicating sales order processing using Webdynpro(Portal).In that we are done with sales order Create,Change,Display except pricing for new custom condition types.
The rquirement is whenever the user added new custom Condition Type along with the Condition amount for the line item the net value for the line item should be recalculated and should be dispalyed in the screen.
I have searched for any BAPI or Function Module to calculate the pricing in Simulation mode and return the Netvalue for the Sales order line item.But no luck.I need to know is there any BAPI or FM avaliable for the same?
Regards,
Vigneswaran S

Hi Namesh,
Thanks for the reply.I think you are not getting my point.We dont have any issues in SAP GUI.We are developing Sale order screen in Webdynpro and in that we have to handle the pricing part.Means that whatever operation user can do in pricing (like changing the condition amount and immediately net value will get upadted) in SAP GUI,has to be done using Webdynpro(portal) as well.To do changes in Pricing condition type and amount at webdynpro side,we have to simulate the pricing using BAPI inorder to recalculate the net value and display it on the webdynpro screen.Please tell me is ther any FM or BAPI to calculate the pricing.
Regards,
Vigneswaran S
Edited by: Vigneswaran S on May 14, 2008 11:44 PM

Dectivate pricing condition for sales order not service order.

Hi,
We are on ECC6.0 and CRM5.0
I need to add new condition type to the existing pricing procedure.It should be activtaed only for service orders and not for sales order.I can achive this by adding new requirement in pricing procedure to limit this condition type based on order type.
Example: if KOMK-AUART eq ORDER_TYPE.
sy-subrc = 0.
But I don't want to do this,because I would need to change this requirement everytime I add new service order type.
Is there any field in Pricing structure KOMK bu using which we can achieve this. ?
Please suggest any other idea by which I can achieve this
Thanks
Dona

Currently ,we have one pricing procedures for both the scenarios...
We control if the perticular condition type to be active or not by writing a requirement which checks the order types.
This has been done this way because we built the pricing procedure in ECC and tranfer it to CRM.Also we donot have service orders in ECC.
any further alternatives guys..

Different Pricing Procedure for Sale order and Billing Document

Hello Experts
As per scenario,we create Excise Invoice (T-Code J1IIN) on Basis of Proforma Invoice.Proforma Invoice and Excise Invoice follow Pricing from Sale Order.AS per pricing Some excise condition types are get update in Proforma and excise Invoice.
AS Per Customer Payment Confirmation we Create Export Billing Invoice (T-code VF01) on basis of Outbound delivery.
Issue -: AS per export Billing Rule we don't want to update Excise Condition type in Export Billing Document,and at same time it should not create any accounting entries for same condition type. we Dont want excise Duity in Export Billing Document as Export Billing Doccumnet aslo Follow Pricing procedure of Sale order
Should i create new Pricing procedure or what other things to solve above issue.
Please help me out
Thanks and Regards
Pash@SD

Hello,
The key to your requirement can be maintenance of Excise condition type with proper access sequence and accordingly maintain condition record for them.
You create an access sequence with following access:
- Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp / Materia
- Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp
- Country / Plant / PlntRegion / Region / TaxCl1Cust / Mat.pr.grp
- Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp
For export maintain condition record based on any key combination, say for
Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp - Tax % - Tax Code
FR / 1000 / KR / 03 (EXPORT) / 04 / 0% / V1
I hope this can assist you.
Thanks & Regards
JP

How to get the pricing hierarchy based on the delivery date for sales order

Hi,
How to get the pricing hierarchy based on the delivery date for sales order other than system date.
My requirement is to get the Pricing hierarchy based on the delivery date other than system date.
Waiting for kind response.
Best Regards,
BDP

HI Sai,
please refer teh document already how to write FM based extration on generic extractors.
and here the logic to find the latest records values:-
-> get the data in an internal table
->Sort the internal table data based from date descending
-> Using READ statement , we can read the first record of the table which is nothign but your latest record.
Regards.
Sakthi

User-exit for carry out new pricing while sales order save automatically

Hi all,
I need to carry out new pricing while sales order save automatically. Please any one help me to finding proper user-exit to achieve my requirement.
Thanking You.
Moderator message: please search for available information.
Edited by: Thomas Zloch on Jan 11, 2012 12:53 PM

Pl help.

Update Pricing elements for sales order item

Hello All,
I want to add few manual pricing elements to a sales order item through code (the pricing elements to be added will be determined dynamically). Is there any BAPI or user exit to update the same?
Regards,

Hi
You can use the BAPI_SALESORDER_CREATEFROMDAT2 for creating the sales order.Using this you can populate the pricing conditions for sales order. To pass the Pricing conditions use the str ORDER_CONDITIONS_IN & ORDER_CONDITIONS_INX in BAPI.
Regards,
Raghu.

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

Save Order Reason for Sales Order

Hi Gurus!!
I need an urgent info!
I am trying to save the order reason on the CRM sales order in order to have a pricing condition that is accessing the Combination Sales Organization/Order Reason succesfully fulfilled.
The problem is that - the condition checks the order reason in a condition table with the order reason of type AUGRU - and I checked on CRMD_ORDER and although the order reason seems to be saved, the condition fails when accessing the order reason.
Do you know how I can succesfully save the order reason? Am i supposed to maintain some kind of mapping? Can anybody explain how the order reason in CRM Sales Order is saved in CRM?

Hi
Maintain code entries for catalogue type A1 (activity reason).
Don't forget to maintain business category BUS2000126 (business activity) to your sales order in CRM.
Then maintain the mapping between the code for activity reason in CRM and the order reason in R/3, in CRMV_CODEMAPMSA view (in CRM side).
Any problems look note 678281.
Regards

Workflow for Sales Order Release via Status Profile

Dear all,
i want to make a workflow for sales order which have 4 User Status in One status profile.
Once Event triggered for sales order
1.   Mail should go to main authority with sales order number.
2. Once authority will do some changes in the required field then he/she changes
     the user status-1 from defauts as per line Item and mail should go to department no-1 (Head authority).
3. Once again same changes in sales order but now user status-2 from user status-1
     as per line Item and mail should go to department no-2 (Head authority).
4. Once again same changes in sales order but now user status-3 from user status-2
     as per line Item and mail should go to department no-3 (Head authority).
5. Once again same changes in sales order but now user status-4 from user status-3
     as per line Item and mail should go to department no-4 (Head authority) .
and parrally for each changes of Status mail should also go to User (Event Creator).
6. Finally mail sholud go to User as you are permitted to do next business transaction for this sales order
Please tel me the process as i am very new this topic and i am always going to stuck in Binding.
please help me out.
Thank You

Hi Neeraj,
First of all start with SWELS and SWEL T-Code to check if any standard event is getting triggered or not. If event is getting triggered, then use the same event to trigger the workflow; otherwise create a custom event of BO and use the same to trigger the workflow.
Hope you are aware of T-Code SWO1 and delegation of BO. The BO used for your requirement will be BUS2000115.
As you want the workflow to get triggered only for one status profile and one of its status, so use check function module. There set the condition for you status profile and status.
The FM which you will be using the most is CRM_ORDER_READ. To read the status, you can also use CRM_STATUS_READ_OW.
Now simply make the approval steps in the workflow using activity. In the activity, you can use the standard method USERSTATUSPOPUP to send the workitem for approval. In each step use the same activity with different agents as approvers.
Just go with these things and let me know if you get stuck up somewhere.
Regards,
Guddan

User exit for Sales order

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

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

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

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Using MD50 to run MRP for Sale Order

Dear all,
I have some problem when using MD50 with Mill Product Industry.
When SAP system not activate Mill Product yet. I used transaction code MD50 to run MRP for Sale Order, the system have generated planned order for multilevel. But when SAP system have activated Mill Product, I used transaction code MD50 to run MRP for Sale Order, the system only generate planned order for single level. I think that we have to configure something based on Mill Product Industry. So can you help me for this
Thanks, Regards

Hi,
Check with following links which may help you resolve your issue :
http://www.sap.com/sme/whysap/industries/millproducts/index.epx
http://help.sap.com/saphelp_di471/helpdata/en/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
http://help.sap.com/content/documentation/industry/docu_is_mill.htm
Regards,
Tejas

Activating Pricing for Sales Order in Retail

Similar Messages

Maybe you are looking for