Restrict user access to sales order

Hi all...
We have the following situation:
A user xxxxx creates a sales order with va01 ... how can be limited the access to this sales order??..another user yyyyyy is not allowed to modify this sales order but user yyyyyy can create orders/modiffy ordes with va01/va02.(something like limit access to o sales order created by another user).
Regards,

Hello Viadi,
Your basis person can help you out in providing this restrictions.
I would like to tell you that you can restrict a particular user from accessing a t-code entirely for eg: you can restrict a user to only VA01 & VA03 i.e., creation and display and another user should be given access to VA02 i.e, change SO.
This way you can maintain security measures for SAP usage.
If you give authorization for creation and change there might not be sanctity of usage. But this again depends upon the client requirement.
Hope this helps.
SAP gurus any additions or corrections to this are welcome.
Thanks
Swami

Similar Messages

Price should not be visible to other user's in sales order..

hi friends ...
my client requirement :
price should not be visible to other user's in sales order level, it should be visible after invoice only ...
eg : gurgoan user should not be able to see the sales order price of hyderabad user raised sales order ... but gurgoan user should able to raise the sales order for his customer ..
plz reply me in detail with configuration steps .... thanks in advance ....

Hi
If you are talking about pricing condition control through authorizations in sales transaction VA01, VA02 etc. - please check SAP Note 105621: Suppressing display of Sales Order Conditions.I would suggest that you search for this auth object and note and work accordingly) and it shall enable you to restrict display to specific conditon type (for example VPRS: cost).
For this you need to know the pricing procedure and step number relevant to your sales order. Please seek guidance from functional consultant on it.
Secondly as you want to restrict access on geography you have to use org level controls as applicable along with the above auth object.
Hope this helps
Prashant

How to restrict the Number of sales orders in theTCode:VL10A whil creation

I'm creating the Delivery by using the batch job with program: RVV50R10C Here I need to restrict the number of sales orders numbers while creating deliveries for sales orders
Like system should pick the sales orders (sales documents) from 1 to 100 OR 100 to 200
Please advise me how to do it and what changes I need to do it

Hi,
Aslo, you can see Note 198137 - VL10: Customer-specific enhancements / user exits. As is for SO, check subroutine LV50R_VIEWG03. If cf_subrc = 1 thin this SO isn't seen in list.
***INCLUDE LV50R_VIEWG03 .
*&      Form POSTAB_VEPVG_FILL_USER
FORM POSTAB_VEPVG_FILL_USER
     USING    IX_LIST_PROFIL    TYPE      SHP_VL10_LIST_PROFIL
              IX_PARAMETERS     TYPE      SHP_VL10_PARAMETERS
              IX_SELECT_OPTIONS TYPE      SHP_VL10_SELECT_OPTIONS
              IT_ENQUEUE        TYPE      SHP_VL10_PACKAGE_T
              IX_SD_ORDER       TYPE      SHP_VL10_SD_ORDER
              IS_VEPVG          TYPE      VEPVG
     CHANGING CS_POSTAB         TYPE      SHP_VL10_ITEM
              CF_SUBRC          TYPE      SYSUBRC.
CF_SUBRC = 0.
* cs_postab-zzfield = ......              "add new field to List
* if xxxxxxx = yyyyyyy.
*    cf_subrc = 1.                         "Exclude this index from List
* endif.
ENDFORM.                    " POSTAB_VEPVG_FILL_USER
I hope this helps you
Regards
Eduardo

How to restrict saving of a sales order without a material.

Hi Gurus
Please advice How to restrict saving of a sales order without a material. That is the system saves the order even if no item is assigned to it.

Hi Raghu,
In standard SAP we can not do that. Even for some requirements of the customer this feature is required, specially in case of milestone billings, custom materials etc. client after saving the empty sales order they may create materials based on that sales order number.
If it is mandatary for u to save sales order only after the entry of the materials, u can try user exits or go for a code with the help of an ABAPer.
Regards,
Ravi Duggirala
Edited by: ravi duggirala on Jun 20, 2008 11:11 AM

How to restrict user access in Oracle Application Server 10g (9.0.4)?

Can anybody please let me know how to restrict user access in 10g AS? To be specific, how to allow http requests from specific IPs only?

Hi,
You have to edit httpd.conf and modify acces rights for each protected directory
e.g.
<Directory /var/www/sub/payroll/>
Order allow,deny
Allow from 192.168.1.0/24
</Directory>
then you have to restart Oracle HTTP Server
jm--

Restriction of No. of Sales Orders

Dear Gurus,
How can we restrict the no. of sales orders for a customer ie. if we want to only allow the system to create say 3 orders for the particular customer in a particular month, and the system should not allow to create the fourth order for that month for that customer.

Hi Hari
In customization its not possible.
Blocking /unblocking customer every month will be an extra effort for end user.
Advisable is go for user exit.
Take help of ur abaper, use User exit USEREXIT_SAVE_DOCUMENT.
Write a code such that before saving sales order program will check VBAK table for the Sold to party (KUNNR) and number of sales orders created in SY-DATUM month i.e. current month.
If its already 3 then display an error message and exit. ie not save that sales order.
try and revert.

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

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

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!

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

Time restricted user access

Dear Experts,
we are dealing with the following issue. Is it possible to set up time restricted user access in BPC 7.5? It means e.g. we want user to have access to BPC only in the first half of the year or (a bit trickier) in every first half of each month.
And is it possible to temporarily prohibit access for an user without deleting him or his rights?
Thanks for the reply,
Jakub

Hi Jakub,
Can you explain why you want to set up your system this way? Depending on what you are trying to accomplish, there may be a good way to make it work in BPC (work status, security, data model design), but as Nilanjan said, there is not an easy way to totally lock out users based on date.
Ethan

How to restrict status profile for sales order.

Dear Friends,
Pl suggest me for follwoing scenario
►     As per business process for tender/ institutional sales and exports, the order is complete once the complete delivery and invoicing for the same has been performed.
►     It was also observed that a sales order may be modified (material, quantity, price etc) even after complete invoicing of the same has been performed in SAP.
     The requirement is Possibility to enable a control to restrict any amendments to the sales order after complete delivery and invoicing will be explored as per business requirements.
Is there any solution above scenario without writing any code.
Regards,
Atul
Edited by: atul thakur on Oct 28, 2009 5:09 AM

Mr Atul,
My understanding is, you don't want your user to be able to change the pricing and order quantity once the order is complete, i.e Delivered and Shipped.
The status profile will not help you in the above scenario, Price/Quantity changes will not come up as Business transactions that can be controlled at Status profile.
Standard SAP restricts the price changes to a completed item of the order, so no need to worry about this.
But order quantity can be increased any time.
So to restrict the user to increase the order quantity you need to use the User-Exits that SAP provided.
Use the MV45AFZB user-exit program and form FORM userexit_check_vbap to code this.
Hope this helps you.
Regards,
Aj.

Restrict manual change in sales order with respect to quotation

Hi All,
The user use to create sales order with respect to quotation. The user can able to change pricing as well as some header and item fields. How can I restrict user for manual change in sales order expect some specific fields.
Thanks.

Hi Sunil,
It is possible through configuration better you can post in sd forums.
For the condition type settings , ensure that the manual entries is 'D'. it wont allow any changes in the order.
Regards,
Madhu.
Edited by: madhurao123 on Aug 1, 2011 1:08 PM

Restrict Pricing updates in Sales Order

Hi All,
I have created a pricing conditon formula to get the price for the real time contract price from a third party Contract management system through a RFC call, and assigned the formula to a condition type.
In this formula, if there was an error i am exporting the error message to a memory and importing the value from that memory to set a billing block in the user exit SAVE_PREPARE_DOCUMENT (MV45AFZZ).
The problem i am facing is that the formula is getting called many times uncessarily for eg. when you click pricing etc
and not necessarily updates the price all times. Actually the price is not updated when called from the following routine and is basically because of the following code.
Form: xkomv_bewerten.
IF xkomv-kofrm NE 0 AND wertformel EQ space AND komp-kposn NE 0.* rettkomv = xkomv*.
xkwert   = xkomv-kwert.      frm_kondi_wert-nr = xkomv-kofrm. PERFORM (frm_kondi_wert) IN PROGRAM saplv61a IF FOUND. xkomv    = rettkomv.
    ENDIF.
During Change Sales Order, because of this even a billing block is set before, it is getting cleared without updating the price.
Can somone help me with this?
Thanks.
Martin

Hi,
Do one thing you could ask your functional consultant to restrict pricing update into IMG Guide. There is pricing where SD consultant restrict the Pricing Updates. If they have problem then let me i will tell you how and where you can do the pricing restriction.
Regds,
Rakesh
Edited by: Rakesh Kumar on Aug 8, 2009 1:35 PM

Restrict user access to sales order

Similar Messages

Maybe you are looking for