Validation period for sales order

Dear SAP Guru,
I am closing the sales order on monthly basis through mass. I want to know
Is it possible for us to give date validation for sales order. for example the particular sales order will be for the month of Jan.08 so that the user can not use the same SO in the month of Feb.
waiting for your best solution.
nikhil

Hi
You can a make a development where in you have to generate a report for list of all the orders created before a specific date and with incomplete status in the VBUK table and list order items which are not with status complete in VBUP table and a reason for rejection should be assigned to all the order items. This will automatically close all the open orders created before that specific date. This can be run on any day periodically.
Thanks,
Ravi

Similar Messages

Cut off period for sales order settlement

Dear Expert,
Client using SAP from last 13 years. Client implemented MTO with valuated stock and activated the COPA.
Now we are re implementing the COPA. since go live(from last 13 years ) they are not doing any sales order settlements and not using COPA.
In sales order RA key(Requirement class) is assigned and Settlement type is 'FUL'.
Now client has decided to use COPA and going to live with new structure on September 1 2014.
I have do the below changes
1. Removed RA key(Not required as per business requirement)
2. Changed settlement type from 'FUL' to PER., here i am having some questions. Client don't want to settle previous orders(before September). as per business requirement they will use one sales order for long time (3 to 4 months). after going live client will settle the sales orders at that time system will consider all sales orders. How can i avoid selection of all sales orders. i want to settle only sales orders having transactions during one month (September)
To avoid this problem now its self i am moving this changes to Production client (RA key removed and Settlement type change), still i am not confident i will get as expected, because at the time of Sales order settlement system will consider all old sales orders.
Can anyone please suggest beat way to handle this issue...
Thanks.
Chandrasekhar

Hi Chandra,
Check the Below SAP Note
174815
- Selection parameter in VA88 or RKO7VA88
Symptom
During the settlement of sales and distribution documents with Transaction
VA88 or report RKO7VA88, you can only select according to the SD document number
or the sales organization.
For example, you cannot select by plant or SD
document type.
Other Terms
VA88
Reason and Prerequisites
The problem occurs due to a previous program design.
Solution
With the attached advance correction, you can also select according to the
plant or the SD document type in report RKO7VA88.The previous restrictions apply
for Transaction VA88.
To correct the error in advance, proceed as
follows:
1. First implement Notes 174502 and 182735.
2. Using Transaction SE11, add field VBAUART (data element AUART) to
structures LKO74 and RKASS. Activate the structures.
3. Add the following parameter to the interface of function module
SD_DOCUMENT_OBJNR_GET (Transaction SE37):
a) Import parameter:I_WERKS (reference field VBAP-WERKS) and I_AUART
(reference field VBAK-AUART). Both parameters should be indicated as
'optional'.
b) Export parameter:E_WERKS (reference field VBAP-WERKS) and E_AUART
(reference field VBAK-AUART).
4. Implement the source code corrections.
5. Maintain the text elements for report RKO7VA88 (Transaction SE38, Goto
--> Text elements --> Selection texts):Text 'Sales document type' for
VBAUART and 'Plant' for WERKS.
Afterwards, also implement Note 210011.
Regards
Srinu

I need to load for a historical period for sales order ? how to load it?

Hi all,
I need to load the data for the historical period. Say 012.2008 month data. I have deleted the set up tables and trying to reload the setup tables.
but i can find the calendar year, month nor fiscal period.
i can see only sales document number along witht the company code.
How to identify the sales document number for 012.2008 from r/3 and run the setup tables.
Pls help me on this!!
Thanks
Pooja

Hi,
You are trying to do a historical load for 2LIS_11? In that case, check the VBAK/VBAP table, and find the document ranges based on the posting date. VBAK will give you the ranges, while putting the same range in VBAP wll give you the number of item documents that would be loaded. You would be able to split the doc ranges in that case for doing parallel setups.
Alternatively if the data volume is low, do a full setup and then put the selections in the info package itself.
Regards.

Validity for Sales Order

Hi Gurus,
I have a requirement, I want to put validity period for Sales Order.
Customer has given me a PO which is valid for certain fix time. How do I ensure that enduser shall not make PGI and Billing after this date.
Pls advice.
regards
guest

For Sale Order Expiry U can use Userexit Include MV50AFZ1 in program SAPMV50A..
In MV50AFZ1: USEREXIT_MOVE_FIELD_TO_LIKP:Here u can write ur own code according to requirement.
The progam is for Delivery, Since u need to check the Sale document date with the delivery date while doing delivery .
The userexit ,USEREXIT_MOVE_FIELD_TO_LIKP, helps to move some fields like date etc to check the date in delivey with the sale order date.
Regards,
Sam

BAPI or FM for Invoice made for sales order...

Hi Experts,
Is there any BAPI / FM for Invoices made for sales order for the month or date wise, party wise, etc.
I want to make a report invoices made during the given period for sales order.
Yusuf.

check this BAPI to get invoice details
BAPI_BILLINGDOC_GETDETAIL.
see the documentation to know how to use.
Regards
Peram

How settlement rule will be created for Sales order with cost object

Dear Experts,
We are using product cost by sales order with valuated stock. In addition we are not using COPA
We also consume some materials at sales order level and at the end of month we want to do the result analysis and settlement for the same amount. In this case can any on explain how system will behave regarding settlement of sales order cost and what entries will get pass in the system.
In our case we have done below activities...
we have created sales order,
All production order activities completed till final GRN including month end activities
Material consumption against sales order
Result analysis executed
At the time of sales order settlement, system throwing error (Sender doesn't have valid receiver, please create settlement rule for sender object)
Then i checked in sales order there sales order settlement rule not defined.
I guess this settlement rule need be generated by system automatically. If not, please let me know the process of it.

HI kishore
the reason is that sale order always carry the revenue and production order and production period carry the cost .
cost you can settle to the Material and even management want to be settle the cost to material only in production order OR period
but in sales order when u sell the product it carry the revenue not the cost and management want see and analysis based on profitability segment are profit center level .
Prerequisites
If CO-PA is active, the system generates a settlement rule when you create the sales order. The settlement rule determines whether data is settled to other objects or other areas in Controlling. In accordance with this settlement rule, the relevant data is settled to CO-PA.
If CO-PA is not active, create a settlement rule. This settlement rule that you create manually normally contains a G/L account as a receiver (such as 399999). You can also settle costs and revenues or results analysis data to objects with revenue.
You can also settle the cost of sales calculated in results analysis to a fixed asset or a cost center. To do this, you must add to the allocation structure the results analysis cost elements under which the cost of sales is updated to the order.
The settlement rule includes a distribution rule for the sales order item. The distribution rule is made up of a settlement receiver, a settlement share, and a settlement type:
The settlement receiver (such as profitability segment or G/L account) specifies the object to which the actual costs and revenue of the sales order item are settled. The settlement receiver can be proposed through the settlement profile.
The settlement share defines the percentage or the equivalence numbers used to distribute the costs to the individual settlement receivers. The settlement share for sales order items is usually 100%. A settlement share of 100% is preset in the system.
The settlement type specifies full settlement of the sales order item. This ensures that all the data on the sales order is available for results analysis.
Settlement still takes place in each period. The revenues and the cost of sales are transferred to CO-PA by period, and the work in process and the reserves are transferred to FI.

Report for Sales Order Change History CDPOS and CDHDR

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

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

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

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

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

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

Validity period for services in ITS

We are on Extended classic scenario with EBO 4.0 and wanted to have service order created.
When I log into ITS server
Shop -> Describe Requirement ->
I have Description, Internal Note, Quantity, Price, Category and Required on.
However I want "From date" and "To date" instead of just Required on date
Is there any configuration setting that needs to be enabled to have validity period for services.
Any help would be highly appreciated.

Hi,
This is strange!At my place,I can see the foll fields when i goto DESCRIBE REQUIREMENT "link:
Describe Requirement
You can describe your requirement if you are unable to find it in the catalog.
Product Type Goods Services
Description
Internal Note
Quantity
Price
Category
Required BetweenOnFrom -
Pls check whether any BADI(like BBP_SC_UI_CTRL/BBP_SC_MODIFY_UI ) has been implemented to modify this screen in you system.
See these related notes:
Note 976533 - Changing the "Required on"/"Start Date" in shopping cart
Note 1064560 - Disabling Service Button causes change in Label/header.
Note 948473 - Change field labels on 'Describe Requirement' screen
BR,
Disha.

IDOC for Sales order

Dear Guru's,
could anybody help me in creating the IDOC for sales order.
As per My client Business Requirment we require the following Fields in One Basic Type only.
The Fields are as follows.
Order Type,Sales Area,Sales Office,Sales Group,Material Number,Order Quantity,Purchase order Number,Purchase order Date,
Sold to party,Ship to party,Bill to party,Payer,
Vendor no ( It is Third Party order)
Contract Start Date, Contract End Date (in order we will give these dates for periodic billing purpose )..
Now i want all the fields will include in one single Basic Type.
Thank you
suribabu

hi,
please check this link:
this might be help ful.
http://wwwdotsaptechnicaldotcom/Tutorials/ALE/Guide/Index.htm
balajia

Costins for Sales order & Production Order

I require an urgent clarification on the following:
We are in Producing to Sales Order scenario. We are using separate costing variants for Sales Order and Production Order
Sales order is costed first.
the valuation variant in the costing variant for Sales order treats material valuation in the following order:
1. Plan price for the period
2. Price indicator from the material master
2. Future standard price
Then the Production order is released.
In the Production order, the valuation variant says the material valuation as :
1. Preliminary cost estimate from sales order
2. Price indicator from the material master.
My doubt is since the production order costing variant says the first option for material valuation is 'preliminary cost estimate from sales order', which value of the raw materials will be picked in the Production Order cost analysis ? Is it from the Sales order costimate as prer preliminary cost estimate or is it as per the price indicator from the material master ?

I require an urgent clarification on the following:
We are in Producing to Sales Order scenario. We are using separate costing variants for Sales Order and Production Order
Sales order is costed first.
the valuation variant in the costing variant for Sales order treats material valuation in the following order:
1. Plan price for the period
2. Price indicator from the material master
2. Future standard price
Then the Production order is released.
In the Production order, the valuation variant says the material valuation as :
1. Preliminary cost estimate from sales order
2. Price indicator from the material master.
My doubt is since the production order costing variant says the first option for material valuation is 'preliminary cost estimate from sales order', which value of the raw materials will be picked in the Production Order cost analysis ? Is it from the Sales order costimate as prer preliminary cost estimate or is it as per the price indicator from the material master ?

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

Liquidity forecast Downpayment For Sales order

Hi gurus,
When i post down payment for sales order with special indicator "a" system does not decrease sales order amount at liquidity forecast(FF7B). Is it a system bug or are down payments does not considered for sales orders like purchase orders?
Kind Regards
Koray
Edited by: Koray Yanik on Mar 16, 2011 8:17 AM

Hi JH,
I'm using strategy 40. Actually my problem is when a sales order falls outside the consumption period of the forecast then PGI is done. The withdrawal quantity works in Normal scenario but not work if the Sales Order is outside the consumption period.
The withdrawal quantity is not captured when forecast is reloaded in the same week as the Sales Order.
Thanks,
Raymond

Query for Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum] ORDER BY T0.[DocNum]
where U_Total_GP is a UDF for storing the GP of each order.
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. However, the query does not calculate column total for total amount and total GP. Although I know the total for each column can be displayed by pressing "Ctrl" + Click on the column title, it would have to be done from time to time.
Therefore, I would like to modify my query in order to calculate the column totals when executed. Are there any suggestions for this?
Thank you
Regards
Elton

Hi Elton,
Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
ORDER BY T0.[DocNum]
Thanks,
Gordon

Validation period for sales order

Similar Messages

Maybe you are looking for