Remove the user status in Sales order

how to remove the user status in sales order header? could you give the function module or BAPI to get this?

Hi,
You Can try this-
BAPI_SALESORDER_CHANGE,
FM 'I_CHANGE_STATUS'
Regards,
Sujit

Similar Messages

Updating the User Status in Sales Order Item

Dear Gurus,
Iam trying to update the User Status on the SO item using STATUS_CHANGE_EXTERN function module and the status is successfully getting updated.
But the problem is if Iam updating the status it has to delete the Purchase Requisition assgined to it, which is not happening.. whereas when Iam manually changing the Status, the PR is getting deleted.. Can anyone suggest some other function module or some other way of doing it other than BDC?
Best Regards,
Sreenivas.

Hi ,
I am also need to update the Item user status. Could you please provide me the logic for the FM 'STATUS_CHANGE_EXTERN'. And also let me know the where we need to write the logic in VA01/VA02.
It would be helpful me a lot.
Thanks
Srihari.

Chance user status in sales order VA02

hi all,
have any FM or BAPI is available to change (block / release) the user status in sales order change,
pls note me about this,
Regards
Usman

Hi Aditya,
thanks,,
which table and which field need to import in this FM "BAPI_SALESORDER_CHANGE" to change User status (Release / Block) in Sales order.
Regards
Usman

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

How to Set User Status of Sales Order at item level.

How to Set User Status of Sales Order at item level by default to 'Purchase Req Not Created' (example)while creating order. Please tell EXIT Name to be triggered & Internal table to be populated.
Thanx,
Srini
Moderator message: please do your own research before asking.
Edited by: Thomas Zloch on Feb 21, 2011 11:19 AM

Mathew,
Here is a document that should help you get started on enhancing 2LIS_11*
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09d5356-d8c4-2d10-8b84-d24723fc1f0a?QuickLink=index&overridelayout=true
Good luck!

Extracting User Status for Sales Orders

I am trying to extract user status transactional data for sales orders (at both the header and item level). I have been following SAP note 300300 to configure the status extractors and map the BW objects to sales order status data sources (2LIS_11_VASTH & 2LIS_11_VASTI). I think I have set up both R/3 and BW correctly according to note 300300 and the IMG documentation, but I am not getting any values in the info source for the new user status info objects, when I run the extract.
Has anyone successfully done this? If so, do you have any documentation or pointers on how I can get this to work? Or, am I better off creating a generic extractor? Thanks for your consideration.
Sincerely, Hashi Chakravarty

Hello Ravi,
well yes, I can derive the status for that order in the update rules if i show the status as an attribute of the 0pm_order; but basically there will be only the last status shown.
My problem:
a. i report on day 1, the status of the order is REL
b. on day 2 i load the master data for the orders, new status is TECO
c. on day three i want to report in the past and see the status of day 1; that's not possible in this scenario because i'll see the current status (TECO).
So that's why I want to have the statuses in the cube...
The 2lis_17_i3hdr extractor is only sensitive to CRT and TECO statuses, but not to the others (like REL / BLC and so on... :_(( )
I could read the statuses from the JEST and TJ02T tables...but still, if a document status is changed, no delta record is written in the queue...
Thanks,
Tudor

Detect change user status on sales order

Hi,
I have a requirement that a custom program must start when a user puts a certain user status on a sales order.
Problem is that I cannot detect on which event I can trigger this custom when the user status is changed. There seems not to be an entry in the change documents table, or an event triggered,...
Does someone has already encountered such an issue ?
thanks in advance !
kind regards,
Björn

Hi Carl and Shiromani,
thank you for your fast reply!
I guess I will give it a try to do this with functions if I just can get it running with the cl_crm_mktpl_appl_base-class.
As you suggested Shiromani the Save_and_commit gets an error in the assignment checks in the check_attributes-method.
So I probably have to take a closer look why this method is returning an error-flag. Unfortunately I am not getting an error message - only an error flag is set.
I will take a closer look at it today and keep you informed if I find out anything useful.
Cheers,
Dennis

User status in sales orders

Hi all!
Can anyone tell me if there is a way to control the possibility of changing a sales order through the status?
I wanted that when a sales order reaches a certain user status, for it to be blocked to modifications, as if it was display only...
Thanks!!!
Best Regards,
Carina Maeiro

Hi Carina,
Requirement is strange, but still may be possible,.
Can you give some more info like..
1. all the users have to be blocked or only particular user?
2. what wud be the next flow processing of tht order ? like after blocking what you wanna do ? want to raise a message or ?
Some Work arounds for the above 2 scenarios wud be.....
1. if a set of users have to be blocked, its very much possible thru customization like, you can define status Authorization keys in Status Management in SPRO where u will be setting the auth key for the user profile
2. if you want to just block the user not to go ahead i e atleast he shudnt save the order, you can implement CRM_ORDER_STATUS Badi in which you have to raise a error message on the application log saying tht it cannot be saved for so and so reason
if this solves..coool ....if not tell me the exact scenario ..
Siva

Removing of billing block in Sale Order through workflow

Hi all,
I want to remove the billing block in sale order when the person approves suing user decision step in workflow .
ANy idea would be great ...
Regards,
Venki

Hi Surjith,
task is not for the billing process ....
and here my big problem is that i was unable to call the custom method in worklofw ....
So attachment is not working in workflow only it works while testing if i pas the key value .
Here my requirment is to remove the billing block if the person approve in decision step ...
Deepa,
Can u tell me how to call a custom method here i am using standard BUS2032 in my task.
already i have BO with custom method but i dont know how to call it when the transaction get executed ....
Thank u for ur reples...
Regards,
venki

Confirmation status in Sales order header

Hi,
I have processed one sales order until billing. The processing status in Sales order is as below.
Overall Status: Completed
Confirmation Status: Not yet confirmed
Delivery Status: Fully delivered
I want to know why the Confirmation status is shown as "Not yet confirmed" when the Overall status is 'Completed'.
Please provide your inputs.
Rgds,
Amit

Dear,
I think after accounting of billing it will show the completed.
VA01-> VL01N (PGI)> Billing---> Accounting.
Regards,
Sandip

Set User status of Maintenance order

Dear All ,
I m trying to update the user status of Maintenance order via a report .I m using the BAPI "BAPI_ISUSMORDER_USERSTATUSSET" for it.
Code details are as follows :
USR_STATUS-STATUS_INT = 'E0006'      "TJ30T-ESTAT
USR_STATUS-STATUS_EXT = 'WIPR'        "TJ30T-TXT04
USR_STATUS-LANGU           = 'EN'.
CALL FUNCTION 'BAPI_ISUSMORDER_USERSTATUSSET'
            EXPORTING
              NUMBER   = WA_FINAL-AUFNR
              STATUS   = USR_STATUS
              INACTIVE = 'X'
            IMPORTING
              RETURN   = WA_RETURN.
Bapi is executing successfully but it is not updating the status when I check it from IW33 .
Suggest me for it....
Thanks
Alok

Thanks SARAVANAN ,
I have done the bapi commit . But it have some other problem and now I have done it.
Thanks for ur suggestion.

How to define a user to raise sales orders in given sales office.

Hi,
Kindly help.
We have a requirement that we need to restrict some of the users from creating sales orders in some of the sales offices.We have a scenario in which all the sales offices are assigned to single sales organisation.But in authorisation tab,we do not have an option to restrict the sales office for VA01(Sales order T-code).We can only restrict any off the below given parameters but no sales office.
-Sales organisation
-Division
-Distribution channel
-Controlling area.
Please let us know how can we define a user to create sales orders in only some of sales offices.
Kindly help.
Thanks and Regards
Syamkrishnan
SAP Basis

hi,
u can control the same using basis authorisation. u can put the restriction on hte basis of the doc type and the sales order.
saurabh

User Exit in the change mode of Sales Order

Dear Guru's
In my requirement I want to stop the user from editing the status of Delivery block and Billing Block into the change view of Sales Order.
I have 2 users for them whenever they may see the change mode of sales order they should see Delivery and Billing Block in gray
that they should not be able to remove the block or change the block.
But I have two other users also who can release and change the Blocks.
Therefore I think mine is the User Exit case but I dont know which is the User Exit I have to give to the ABAPer
Please suggest me the User Exit, Thanks in advance for answer and Suggestions.
regards,
Vojas

Dear Vojas,
As per me User exit will be used, as there are check about the users in your requirement. Please try with in MV45AFZZ, there are seceral user exit, I guess in USEREXIT_READ_DOCUMENT may be used, ask your abaper to put a check on the current user and if the user which is not in your list of authorized one then change the Blocks in Display mode, or uneditable mode.
Thanks,
Raja

The status of sales order is being in processed

Dear All,
The delivery quantity is fully delivered and it is order related billing, this is a Sales Bom, the header is delivered and the line items are billed, the status of sales order is being in processed after the completion of the subsequent documents,
In the document flow the system is showing that the order is being processed, we have checked the copy control and the relevant assignments. As we are facing the problem while creating sales order system giving an error message that there are open items for the customer. Please tell me if there is any customization is there or is there any other way to achieve.
The other requirement is, if the customer credit limit get exceeds then the system should not save the sales order, if the credit lies within the limit and if the stock is not available in that particular plant, it is a dynamic credit limit.
Thanking you in advance for your valuable time and efforts,
Thanks & Regards,
Mani

HI ,
1. For your first issue u201Cstatus of sales order is being in processedu201D
Please check the below settings:
Copy control From Sales order (OR) to Delivery (LF) u2013 T.code: VTLA.
In Item level (TAN) whether u201CUpdate document flowu201D is activated or not.
You should also check in the Item category (VOV7):
Completion Rule: Which one did you maintain?
2. Error message: Open items:
This is related with Credit management. Check whether you maintain any open item days or percentage, please check in OVA8. If you maintain you should get the payment from your customer . This is related with FI ( T.code : F-28 )
Dynamic credit check :
The setting is available in OVA8. Choose your credit control area, Risk category and Credit groups ( Should be Sales order group ). Then select the indicator u201C Dynamic u201C In Reaction you should give B ( Error ). Then the system will not allow to save the sales order if credit limit is exceeded .
3. If the stock is not available in that particular plant, it is a dynamic credit limit.
I think it is not possible . You may use the User exit in OVA8.
Hope this can help you .
Regards
M. Lakshmi Narasimhan

How to update user status in CRM Order depending the delivery status in R/3

Hi All,
In my scenario the partial delivery allowed to the customer while creating the CRM Order. But as per my requirement the status should be updated when the complete order and delivery takes place.
Let me describe you clearly:
Suppose I want to deliver 5 quantities products to the customer but initially I want to deliver only 3 quantities and rest 2 quantities later. When I do the post goods issue of 3 quantities in R/3 system the status should not change in CRM system. When I will do the rest 2 quantities in post goods issue in R/3 then the user status should change in CRM Order. But in current when I do the delivery of 3 quantities the user status is changing in CRM Order.
I need the user status should change in CRM only when the entire deliverytakes place in R/3.
Thanx
Chinmaya

Whenever an item is fully delivered, by standard, a "Completely Delivered" status will be updated into the item. If the I suppose by referring to that you will know an item is partial or completely delivered. When all items in the order is fully delivered, the standard header status will set to "Completed". So, you will also know if the whole order is partial or completely delivered.
If you want to add a user status, the simplest, you can make use of the ORDER_SAVE Badi. Just call the function CRM_STATUS_MAINTAIN_OW. You can update both header and item status.

Remove the user status in Sales order

Similar Messages

Maybe you are looking for