Sales Order Being Processed

Hi All ,
I my client created sales order with 100000.700 ton and with 42 Piratical delivery document with different dates and 42 billing document and clear accounting documents
But the problem is Sales order status showing as Being Processed
I check all delivery documents if was showing total quantity delivers and i check copy controls OR to ZLF Updated document flow is there
and i Item category TAN don't not having completion rule
My question is it is mandatory to maintain Completion rule in item category
The Problem With Only One sales order it showing Being Processed, rest of sales document Showing completed
Do we need to Updated Status manually ?
Can any one guide me what could be a Problem
Thanks
Rajesh

Dear Rajesh,
Please check the status of the sales order at
Go to the order VA03 --> Environment --> status overview, check what is the cause of this...
Again In item category completion rule can be set as B if you want the item to be completed only after full quanity reference it has impact only when the document flow check in copy control setting is checked.
Anyways If all setting are ok then run report SDVBUK00 for updating the document flow.
Thanks,
Raja

Similar Messages

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

Sale order costing process : Help required

Hello All,
Belatted Happy New Year 2011 to all.
I have a question related to Sale Order Costing. It goes like this,
My client is into Pipe coating business who receives the pipe from the customers, coats it as per there requirements and despatches it thereon. There is no concept of FG here as its only the service he is doing on it and also when he receives the pipe there is no raw material cost on it. Raw materials for him would be chemicals etc which he uses to coat the pipe.
And also this demands variant configuration from SD and PP angel.
As this scenario is customer specific, it demands Sale Order based costing(Sale order cost estimate).
My doubt is, how the sale order costing process goes with.
In general scenarios, Make to stock, we use production order based costing where standard cost estimate is calculated for planned cost and actuals are incurred on PO settling the variance to COPA
Similarly how the costing goes with if Sale order cost estimate is used. What i think is, here instead of Standard cost estimate for plan, we will go with Sale order cost estimate at sale order level, and incur actual cost at production order and settle the cost of Production order to Sale order. Correct me if i am wrong, and request you ppl there to explain me the process of costing in the scenario said above.
apart from that, my client wants the flexibility to change the cost estimate at quotation level.
Please suggest me with solution explaining the process of costing here.
Thanks in advance,
Ravi Kumar

Hi Ravi
Your understanding of the scenario is very much right...
In your case, you need to have sales order as cost object...
Process
Your stock would be non valuated stock, because the FG is not your stock.. You are just doing a service
Based on the characteristics chosen in the Sales orders, system would determine the Sales order BOM
Based on sales order BOM, Sales order cost estimate would be calculated....
You would receive the Customer pipe in your stock against the sales order... It would be a non valuated GR... You can track the Qty only
Sales order would trigger a production order... The prod order can have its planned cost, which is only for information sake
The Customer Pipe, Chemicals would be issued to prod order to coat the pipe... And also Labor/machine hrs may be confirmed
There after your production order would be settled on Sales order
Then you would do PGI (Post Goods Isue).. This will not trigger any accounting doc
Then you do billing... The sales revenue would be posted on the sales order
Then you settle the sales order to COPA.. This will close the cycle
Configuration
The IMG Settings required would be as below
1. You would use account assignment category (AAC) E
2. Create a Requirement class with
a. AAC = E.... (Means sales order is CO Object)
b. Valuation Indicator = BLANK (Means Non Valuated Stock)
c. Costing ID/Costing Method = As per your choice to calculate the Sales order cost estimate
3. Assign this req class to Requirement Type
4. Give this req type to your PP/SD team.. They would assign it to Strategy group / Item Category to determine it in the sales order
Regards
Ajay M

Function Module to fetch Customer Number from Sales Order or Process Order

Hi Gurus,
I am looking for a Function module which gives me customer number from Sales order or Process order.
Please let me know of any FM's available.
Regards,
Madan

Hi,
Thanks for your response.
I am actually looking for function modules which take "Sales Order" or "Process Order" as input (import parameter) and return Customer Number as output (export parameter).
Please suggest some function modules you know any.
Many Thanks,
Madan

Sales order stock process

Hi All,
We are planning to implement sales order stock process. There is some confusion regarding the picking process of sales order stock. Can anyone help me in this matter, how to do picking for sales order stock item? Is this in the normal way or not?
Thanks,
Vijesh

Hi,
yes the stock is maintained for sales order and even blocked in MB1B using 412 -E ..in MMBE now the stock is showing as sales order stock .
this part is clear,
now the issue is regarding picking... how can we to picking process..can we do picking using sales order stock..it is because , in LS24 the stock is showing as E which is not in any bin locations.
In the normal process we are doing the picking from bin locations..
thanks to advise the picking process in sales order stock.
Best Regards,
Vijesh

Sales order reles process

hello guru's
i need sales order relese process.
how can i map in sap.
if know any one please help me?
regards
dharma

Hi Dharma,
There is nothing like release strategy for sales order. There is a release strategy for purchase order. A bit of search on sdn forum in MM section will help you a lot on this area.
For your reference, The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 0
1
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Overall Status of order Being processed after complete PGI & Billing

Dear All,
Before writing this post i tried all possible solution available on SCN & internet.
In sales order overall status (GBSTK) is Being processed after doing complete delivery and Billing.
I tried many things changed the completion rule also run the program SDVBUK00 but the status is not updated to complete.
Created 1 sales order with 1 material without any reference then done PGI for 1 material then done billing successfully.
In table VBUK / VBUP the field GBSTK / GBSTA showing Being processed, for delivery and invoice its showing completed "C".
I checked the Incompletion Log also there is nothing pending.
Please refer screenshots and provide me solutions.
Thanks in advance.
Tarun Kumar

There is no additional schedule line.
I have taken 1 quantity and it confirmed.
I change the completion rule also but no luck.
Copy control screenshot-

To change/overwrite material price in sales order - while processing

The scenario is - when the user creates a sales order in system 1, there has to be an RFC called to another SAP system to get the price of the materials in that system. Then it has to overwrite that price in this S.O in system 1.
Which user exit in S.O processing can be used for this ? (Lets say to get price we use some BAPI to the other system). But how the price can be overwritten on this S.O in system 1 ? Any help ?

HI,
you do a RFC while entering your order to get the price.
If you store the price in vk12 in System 1 and do new-pricing, in our system, that woult take too long. The pricing conditions need several secondes ( i wait up to 10 seconds ) from vk12 up to the time, you can use it in va01. ( due to the synchronisation between several application-servers ).
I would try to do it in MV45afZB in the form new-pricing. Insert a manual condition in xkonv ( check in ther is an xkonv-updkz ) and select new-pricing = 'C'. ( at this time i have no access on you system - i don't know, if xkonv is avalible - if not my next choice would be mv45afzz / userexit vbap ).
perhps that will do. good luck.
hans

MTO-Need to block (Not to Change)plant in sales order after process order

Hi All,
We are creating MTO sales order and requirement has been forwarded to MRP. Planning person is creating process order and will start their work. Sometime sales person change the plant in the existing sales order. Say for ex: changing the plant from 1000 to 1001. But requirement is already been transferred to 1000 plant. After changing the plant in sales order again the same requirement transferring to 1001 plant for planning. So based on this, 1001 plant also started producing the material. Here the problem is both the plants are producing for the same requirement. Now I need to control the this problem. Is there any way to control in std sap? if possible which way we can control? Please share your ideas.
Thanks in advance,
Babu

hi
use user exit
MV45AFZZ
FORM USEREXIT_FIELD_MODIFICATION
here you write the logic
when production order exit that line item plant is not changeable ,

Purchase order being processed msg

Hello All
I am trying to amend a purchase order but getting message, "Document is still being processed in background, Please try later"
Using SRM 5.0 EC
Does anyone have a solution for the above msg?
Thanks
Prakash

Hi Prakash,
Please go through the following threads:
Document is still being processed in the background
Document is still being processed in the backgroud
Document is still being processed in the background
Also have a look at this note:
Note 820040 - Canceling a workflow lock in the BBP_WFLOCK table
Thanks,
Pradeep

Belated costs during a make-to-order/sales order controlling process

Hello Experts,
We implemented a make-to-order process where we collect actual costs of a repackaging process. The cost object of that process order is the sales order item (VBP, Vertriebsbelegposition). So far that cost collection works absolutely fine and the actual costs are collected in the conditions of the sales order item.
Unfortunately it can be the case that after billing the sales order item, operations debits the process order with an activity (e.g. quality analysis). After using transaction KO88 the balance of the process order is posted to the sales order item even if it has been already billed. But when I open the sales order with TA VA02 the conditions of these sales order item are already grey and not editable anymore. And therefore it is not possible to actualize the price and the extra costs of the belated positing of operations.
Do you know any possibilty to creat a second bill of the same sales order item to collect the additional costs?
BR
Mike

Hi,
Finance person would need to create a JV to knock off those costs. The same wont be possible through SD route again.
Regards,
Amit

Notification Mailers Up - P-Orders being processed - i-Expenses not!

Hi all.
I hope somebody can shed some light here..
As title suggests, The Notification Mailer is Up (although it has been going down intermittently) with Purchase Order notifications being processed but i-Expense notifications are not. At All.
We're on 11i, DBMS 11.5.10.2, Sun Solaris (I think..)
This HAS been working. All user iExpenses are using valid email client applications and all of their email addresses in their employee and user records are populated.
Any suggestions of why PO's are being processed by Notif Mailer but NOT i-Expenses?
Are there any other processes I should be checking?
thanks for looking..
Steven

Hi;
If it was working before what you have been changed? Did you check i the workflow mailer log file and database log file for any errors? Did you try to bounce the workflow services? If answer is no please try those
Please also check:
Subject: Notifications Not Being Sent In Workflow Doc ID: 1012344.7
Subject: Workflow Mailers Not Sending Notifications Doc ID: 560472.1
Hope it helps
Regard
Helios

Sales order being cost object

Dear All,
I need to make myself understand as I read few post which quite confusing.
Why sometimes sales order can be cost object for certain processes but not for some processes? In this case, GL can be cost element and also not a cost element.
Why third party order and MTS, sales order is not cost object whereas MTO, sales order is cost object?
thanks

Hi,
Below information helps you to understand the difference between MTO and MTS further:
MTO:
You will receive an order, it can take huge time to deliver this sales order, you need to follow the legal compliance on Revenue recognition, the functionality of Result Analsysis which is possible when the sales order is a cost object provides you the flexibility to manage the revenue recognition methods (OKG3). You can track the costing by Sales Order.Finally the costs and revnues are transferred to CO-PA.
MTS:
You will manufacture a product and send back to stores. You will receive the Order later, and you will pick the goods from the stores and delivers to the customer. Revenue recognition directly when the Billing is done together with costs.directly in CO-PA. No individual lot based costing required.
Kind Regards
Umapathi G
Edited by: Umapathi Naidu G on Aug 3, 2011 3:47 PM

User Exit/ Enahancement/BADI in the sales order creation process

Hi,
We have an EDI process for creating a sales order, we want to change one of the partners on some of the lines according to the document type,
We know how to do it using the MV45AFZZ user exits but we want to do it using a BADI or an Enhancement,
Can anyone help us find a User Exit/ Enahancement/BADI ?
Thanks,
Mickey

Hi,
Thanks for the quick answer,
i created an implementation for this BADI and put a break point there but it didnt stop there,
i also tried a break point on FM "SXV_GET_CLIF_BY_NAME" to see if this BADI is on the list but i didnt find it,
i tried creating the sales order via VA01 and via the IDOC process,
Thanks,
Mickey

Order being processed for 24 hours and more questions

i ordered lightroom 5 yesterday and my troubles begain immediately. first of all, while creating my billing adress, i was given the option to choose as coubtry of residence usa, mexico or canada - since i had to choose sth i chose mexico even though i'm from greece. afteri placed my order and up to that moment, 24 hrs later, my order is being processed, a notice in spanish tells me every time i check. what do i do??

It can take up to 48 hours for the orders to be processed, according to http://helpx.adobe.com/x-productkb/policy-pricing/adobe-stores-online-order-payment-faq.ht ml
If it still doesn't go through, try Adobe’s one-to-one chat support at http://adobe.ly/yxj0t6

Sales Order Being Processed

Similar Messages

Maybe you are looking for