Store procedure for sale order

hi
i want store procedure that we can't add stand alone sale order without sale quatation

hi,
you can check my post in this link
Re: Storeprocedure for sale order without sale quotation
regards
Fidel

Similar Messages

Approval Procedure for Sale Orders

Hi Experts:
Anyone can help me?...I´m needing an Approval Procedure for Sale Orders to be activated whenever the user is trying to give diferent discount percentage from the one assigned in the price list throughout Period Discounts. We have Sap Business One 2007A SP01 PL05
Thanks very much in advance
CLAUDIA

Hi CLAUDIA,
This has to be done through user query approval. However, since I don't have similar environment to try, you may start to create your own query first.
Thanks,
Gordon

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

Store Procedure for Purchase Order

Hi Experts,
I want Stored Procedure in which if user tries to edit User Defined Fields already added in Purchase Order Item & Service.

hi
YOU CAN DO THIS THROUGH FORM SETTINGS BY UNTICKING THE FIELD "ACTIVE" FOR THAT PARTICULAR USER.

Query Based Approval Procedure for Sales order .

Hi
I have created query for SO which results above 5000 d 50,000 .
By using this each query i created two seperate Approval Procedures which So is >5000 d >50000.
If So>5000 Approval Procedure wants to activate same thing for >50,000., Bur approval Procedure is not working wat will be the cause. i have linked this query In Terms as when the following applies.
If SO >5000 approved by user A.
If SO>50,000approved by User A & B.
Regards
Giridharan

Hi Giri
Your query for the first should be as follows:
SELECT DISTINCT TRUE
WHERE $[$29.0.NUMBER] > 5000 AND $[$29.0.NUMBER] < 50000
For the second query:
SELECT DISTINCT TRUE
WHERE $[$29.0.NUMBER] > 50000
The query you were trying to use is looking at the table which will only apply to documents already posted, and as that query is not being filtered specifically it is bringing back all the records and getting confused. You must reference to the runtime value of the document being posted.
Kind regards
Peter Juby

Problem after change item status procedure in sales orders.

Hello experts,
I have changed item status procedure for sales orders. But now all BDoc with queue name CSA_ORDER_xxxxx remain in state 'Written to qRFC Queue (intermediate state)' and needs to be reprocessed manually.
No problem reprocessing.
Have somebody any idea ?
Best regards
Juan Salom

Hi,
Is your inbound queue un-registered(type U)? Look at trx.
SMQR
and see if it is in un-registered. If yes, select the CSA_ORDER_*** queue and click on
Registration
button.
If this does not help, re-generate your Bdoc services (for Bdoc BUS_TRANS_MSG) using
SMOGGEN
or
using the generation workbench.
Then try the delta once again and observe for queue and Bdoc status in the
SMW01
Hope it helps! Reward if helpful.
Regards,
Sudipta

Different pricing procedures on Sales order and billing documents

Hello All,
I have come across a situation where I will have to maintain seperate pricing procedures for Sales order and the corresponding billing document.
I was just wondering if this is normal. In my previous projects I always had same pricing procedure for the order and the billing.
Please share your experience.
Appreciate your help.
Thanks,
Raj

Hello Friend
This is a very common requirement in many implementations depending on the scenario
Sales order with one pricing procedure The same sales order when goes for billing
Billing document with another pricing procedure
Settings needed
Order type VOV8 has a document pricing procedure Say A
Billing type VOFA has a document pricing procedure Say B
Sales area 1000,10,00 and CPP is 1
OVKK settings is like this
1000,10,00 DPP A, CPP1 Pricing procedure is RVAA01
1000,10,00 DPP B, CPP1 Pricing procedure is RVAA02
The control data in both RVAA01 and RVAA02 is different
In VTFL between your del type to billing type aunder the header that item level The pricing type should be B (carry out new pricing) if delivery related billing
In VTFA betwen your ord type to billing type aunder the header that item level The pricing type should be B (carry out new pricing) if ordery related billing
Now the same sales order will carry PP RVAA01at order level and RVAA02 at the billing document
There can be some business scenarios you want to add some extra discount at the time of billing
That time you have a discount type added in the billing PP so that it is reflected in the billing
This is scenario dependent
Hence SAP has given the option of DPP in VOFA so that by billing documentwise we can differentiate
To achieve this Copy control settings and DPP should be different both in VOV8 and VOFa
Regards
Raja

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

Approval for Sales Order

Hi All,
Is it possible for me to set an approval procedure on sales order in case the user forgets to fill in the remarks column??? please help with the query.
Thanks in advance,
Joseph

Hai!
If, your requirement is block users to add SO without remarks, then u do with Strored Procedure.
if @transaction_type = 'A' and @object_type = '17'
begin
if exists(select T.docentry from ORDR T where T.docentry = @list_of_cols_val_tab_del and
(T.comments is null or T.Comments=''))
begin
SET @error = 17
SET @error_message = N'Enter the Remarks'
end
end
Add this code in SP_TransNotification of your company DB.
Please test it in a test system and put in Live
Regards,
Thanga Raj.K

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

Error reading material cost estimate for sales order (KE292)

Dear All,
I have an issue with billing. we are posting july month transactions, the material cost is maintained through MR21. When releasing billing document for accounting we are getting error message like"Error reading the material cost estimate for sales order "11"
Message no. KE292
Diagnosis
In Profitability Analysis (CO-PA), the system tried to valuate item 000010 of sales order 11 by reading the corresponding product cost estimate.
However, no product cost estimate could be found for this sales order item.
The system accessed product costing for product AMLFP011011XX00P using costing key YB3 as defined in the
CO-PA Customizing settings.
System Response
The system cannot process the document any further.
Procedure
Check your Customizing settings."
We cross checked with other client as a current date and we ran cost estimate through CK40N with same material. and we posted entries. Here it is working fine. but in above process it is not working. Can you pls guide me where i missed.
Regards,
Nagaraju,

Hi,
When the Costing Key is assigned to the material types in the COPA customizing, then system expects Cost estimation when billing is released to Accounts.
If you dont run cost estimation but update the material master through MR21, system will not accept as in the Costing key configuration you must have selected the Current Standard price field for the valuation.
Hence, try to run cost estimation and then do releasing.
Thanks & Regards
Ravi Kumar

Account Determination Procedure in Sales Order

Hi All,
I have a problem regarding account determination procedure in sales order.
When I create a new sales document, and go to menu Environment --> Analysis --> Account Determination, the information about the procedure is blank.
For your information, I already assign this sales document type to a billing type.
This billing type also already has an account determination procedure, which is KOFI00.
The G/L Account in VKOA also already been set up for the combination of Condition Type - Chart of Acct - Sales Org - Account Assignment Category in Customer and Material - Account Key.
But every time I create a new sales order, I cannot get the account determination procedure.
Anyone can please help me to solve this problem?
Thank you in advance

Hi Surya,
Have you assigned Billing type For Ex: F2 or F1 to respective Sales Order Type in Sales Document Type controls VOV8.
Assign these F2 against Delivery Related billing and F1 is for Order Related billing.
Assign KOFI0000 to respective Billing Types F2 and F1.
And check, hope issue may resolve.
Revert if u have any query.
Regards
Durga sana.

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

Pricing Procedure in Sales Order

Hi everyone,
I realize this question has been posted a couple of times before but I am posting the question really after doing all my research and trying all my options.
Order Type: ZOR has Doc. Pricing Proc: A while Billing Type: ZF2 has Doc. Pricing Proc.: Z. Cust Pricing Proc is 1 in all cases. In Pricing Proc (PP) determinations I have
Sales Area + A (Doc. Pricing Proc) + 1 (Cust Pricing Proc) = ZRVA01
Sales Area + Z (Doc. Pricing Proc) + 1 (Cust Pricing Proc) = ZRVZ01
Now when I create my order ZOR from scratch, the PP is ZRVA01 but when I create ZOR w.r.t a ZF2, the PP determined is ZRVZ01. Whereas I want it to be ZRVA01 (based on Doc. Pricing Proc of ZOR). Is this possible? I doubt if this has anything to do with copy controls.
Any help is appreciated.

Hi
If i have understood your requirement correctly now
You are creating sales order ZOR with mandatory reference of billing type ZF2
Your billing type or billing doc has already a pricing procedure of Z RVZ 01
But now your sales order is also picking Z RVZ 01which you dont want
You want your sales order to have PP of ZRVA01 and you have done necessary settings in OVKK and still it is not getting picked
If this is the issue
I feel because of two reasons your requirement is not possible
1.your sales order is created with mandatory reference to billing doc and hence the price of billing doc is getting copied in sales order
2.Pricing type is mainly for sales order to billing and not in the reverse like your scenario that is billing to sales
That is why pricing type B is not working for you
Others elite members correct me if i am wrong
For your requirement i think you need to develop a new routine or program thro ABAP so that when you create a sales order referring billing doc the PP is not getting copied and to be determined new
Regards
Raja

How to configured pricing procedure to sales order type

Dear Sir,
Please tale me how to configure / change pricing procedure to sales order type. we have required to change pricing procedure from a to b for particular sales document type.
Regards
BK GAIKWAD

HI
Create a new document pricing pricedure
SPRO>sales & distribution>basic functions>Pricing>Pricing Control-->Define And Assign Pricing Procedures
and in the same path assign to your document
and assign it to your document and also then to your Pricing procedure determination in OVKK
regards
Prashanth
Edited by: Prashanth@SD on Jan 29, 2011 11:00 AM

Store procedure for sale order

Similar Messages

Maybe you are looking for