PO Document type Authorizations

All,
Whether its possible to give authorizations based on PO Document types ?
Authorization object is M_BEST_BSA.
pLS ADVISE.
REGARDS

Hi,
I am not an authorisations expert but I am sure that you can control which PO document type can be used by each user.
Hopefuly someoen with authorisations knowledge will confirm this???
Sorry I misunderstood your qiestion, it was my fault, your question was very clear.
Steve B

Similar Messages

Authorization for Document type in FB60.

Hello everybody,
On executing FB60 transaction code, i want to control the document type entry means
we have basically 2 types of document V1- Pune vendor bill and V2 Mumbai Vendor bill.
I have to give V1 document type authorization only for pune location user and V2 for Mumbai location user.
I had check the object in FB60 but I can't find the authorization object for document type.
I tried by creating test role name z:test and assign transaction FB60 in that role. when I assign this role to
test user he can post both the document type invoice.
So please suggest me how to give the authorization for the V1 and V2.
Thanks

Hello Ganesh!
I believe that authorizations object F_BKPF_BLA is what you're looking for. To use it, however, you will first need to define an authorization group for document type you want to protect. This is done in transaction OBA7; select the document type you want to protect, go into details view and define a value for "Authorization Group" field (this is freely defined, you can enter any value you want).
After you've done this, a check will be performed on auth. object F_BKPF_BLA with the authorization group value you defined for the document type and activity.
(I've never implemented this in our system, but I'm fairly certain that this will work.)

Document Posting restriction using posting key,document type combination

Hi
We have a authorization restriction issue using posting key&document type&Accoutn type combination.
Requirement is
User A should be able to post to vendors only for particular posting key&document type.He should be able to post to with any other posting keys and document types to vendors.
We have tried with document type authorization object/vendor authorization objects from user profile but it does,t work.
can any one suggest some way please/
r
regards

Hi
I think you should be able to achieve the same through Validation rule:
Prerequisite
Document Type - XXXX
Check
User name = 123 and Posting Key = XX
You can set a an error messsage which would be bleeped when the check fails
Regards
Sanil Bhandari

Document type Authorisation in FBL1N

Hi Friends,
We have one requirement to restrict the Document type authorization in FBL1N for one user.
Since in SAP we have created the employee as the Vendor so we are passing the salary voucher vendor wise.
We have tried to check the the authorization object through SU24 for transaction code FBL1N and found the F_BKPF_BLA after that, one authorization group is assigned to Document type in OBA7. there after, in table TBRG the authorization group has been assigned to authorization object. Now that authorisation group is being removed from the user id.
but the same is not working.
Please help.
Thanks in advance !!

Hi Janeet,
You can able to restrict those values in 2 methods.
1. Create document type authorization object in OBA7 and exclude this authorization object to business user through mentioned object F_BKPF_BLA
2. Create separate account group for Employee vendors and assign one authorization group in Vendor master and restrict those values in FBL1N through authorization object F_BKPF_BEK
You have to exclude those object from obhjects.
Regards
Mani

BASIS--to restrict authorization for a PO document type & 122 movement type

Dear All,
Plz guide me how to restrict authorization for a PO document type & for a movement type 122 i.e. for eg. if a user has authorization for PO document type IC then he should not be able to rum movement type 122 for any T-code he runs.
Thanks in advance
Arpit
Basis

Hi,
Your request was not too clear to me.. As per my unde
Here is some details of Authorization object related to Purchase Order:
Document Type in Purchase Order( M_BEST_BSA )
Purchasing Group in Purchase Order (M_BEST_EKG )
Purchasing Organization in Purchase Order (M_BEST_EKO)
Plant in Purchase Order (M_BEST_WRK )
Document Type in Outline Agreement (M_RAHM_BSA )
Purchasing Group in Outline Agreement (M_RAHM_EKG )
Purchasing Organization in Outline Agreement ( M_RAHM_EKO )
Plant in Outline Agreement ( M_RAHM_WRK )
This can be helpfull to you to restrict authorization to PO..
In Organization Level, it can be restricted by Purchasing group, Purchasing organization and plant..
Regards,
Sandip

MIGO_GR Authorization check for PO Document type

Hi Friends,
We would like restrict users processing GR's against certain PO document types. In brief, <b>X</b> group of users are allowed to process GR's against PO document type <b>'NB'</b> only. This validation should take place soon after they enter the PO number or at the check level in MIGO_GR.
Unfortunately, MIGO does not provide relevant standard authorization object... or EXITS to achieve this.
Appreciate, if you share your expertice in this regard . Points will be awarded...
Regards
Kumar

By defining custom authorisation object.

Authorization based on plant and Purchase order document type

Hi
My client has a requirement wherein a user will have authorization for transactions only in his plant. But only for Purchase order document type UB (Stock Transport Order) the user should be allowed to create for all plants.
In short, if Purchase order document type is UB, should be allowed for all plants
if Purchase order document type is NB, should be allowed to only one particular plant.
My Basis person says that such a restriction is not possible.
Kindly suggest me on how to provide a solution to this.
Thank U.

Hi,
This is possible.In this case you need to create two seperate roles.
1)Create purchase order for all plants (This can be used in long text)
2)Create purchase order for <plant no> plants.
For case 1:--
i)Populate field BSART of M_BEST_BSA with UB.
ii)Populate field WERKS of M_BEST_WRK with '*'. SAP reccomends to fill up organizational data through organizational level tab only.So while doing this step you need to put * from organizational level tab only.
For case 2:--
i)Populate field BSART of M_BEST_BSA with NB.
ii)Populate field WERKS of M_BEST_WRK with 'plant no'.
Dont worry about the objects i mentioned those are maintained through SU24 and will be automatically pulled once you insert ME21 transaction code.
Let me know if it helps.
Thanks,
Aveek

Authorization for UB document type in PO create

Hi All,
We wanted to restirct some user from creating PO other than UB. We want them to give authorization only for UB document type in ME21N. What is teh best way to make it work?
Thanks for your support.
KHAN

Hi Khan,
If you want to restrict the User for creating PO other than UB document type. You need to discuss with Basis consultant.
For that particular user you need to restrict the activites like Create, Change , display for the authorization object "M_BEST_BSA" which is assigned for Document type for Purchase order.
Based on your requirement inform the basis consultant to remove the all other document type or * symbol and assign only UB document type to that user. So he/she will be restricted to that document type only when ever he creates any PO.
rgds
Chidanand

Authorization restriction on amount and document type

Hi,
The business need is to resctrict the authorization of docuemnt posting on the below levels:-
1.) Transaction Type - This can be controlled by document type / transaction code
2.) Amount per transaction type
Example,
Let us say there are two user ids FIUSER1 and FIUSER2.
FIUSER1 should have the authorization of posting cash transactions will 5,000 amount and vendor invoices will 1,00,000 amount.
while
FIUSER2 should have the authorization of posting cash transactions will 25,000 amount and vendor invoices will 10,00,000 amount.
Can we do it with standard SAP without using validations / user exits / exhancements?
Thanks,
Nitish

Use GGB0 to create a validation and in that you can create different sets using GS01 to validate diffrent user ID's.
Like you can set the validation on - BLART , TCODE and WRBTR .
Else you can use the exit functionality in GGB0 and then activate the same in OB28 or GGB4 .
Cheers ,
Dewang

Filter Document Type based on Authorization Object

Hello Everyone,
I have a requirement where i was asked to filter the document type based on authorization object M_BEST_BSA in transaction /KCP/2,ME21N, ME22N and ME23N.
When I create or modify a purchase order, I dont want to be lost in choosing the PO type. I want the field EKKO-BSART displays only the values authorized for the user(me).
Thanks a lot

RE is standard for MIRO .This is SAp standard .
Please clarify what u require .
Did you need other RE for example LE for miro doc type in your co code 1130 and miro doc type EE for your co code 1145.
like wise
Edited by: manu m on Jul 13, 2009 7:53 AM

Authorization for Document type AA

Hi,
I would like to assign authorization for document type AA only(related to FI), let me know how to assign ?
Urgent ....
Thanks in advance
Vijay

HI,
You may ask from user to provide you SU53 screenshot or if you know how to simulate the required authorization, you can trace the object using tcode ST01.
Thanks
Tarmizee

Billing block for customer for sales document type OR

Hi
I want to block a customer for a particular sales document type OR
How to do it?
Regards

Hi Nikhil
There is a field called "Check Partner Auth.", but it is necessary to create the order from a contract. This field is in sales document customizing VOV8.
SAP Documentation:
Check partner authorizations
This check determines whether a partner is authorized to release against a contract.
Procedure
Here you can specify whether the check is to be performed against the partners in the contract or the partners in the customer hierarchy. If you do not want the check to be performed, leave the field blank.
When you create a release order for a contract, the system determines whether a partner is authorized to release against the contract. The check is performed at header level. Depending on the rule you enter in this field, the system checks against one of the following:
Partners in the contract
If the partner has the partner function AG (sold-to party) or AA (sold-to party authorized to release) in the contract, the system accepts the partner as the sold-to party for the release order.
Partners in the hierarchy
If the sold-to party of the contract is at a higher level in the customer hierarchy to the partner who wants to release against the contract, the system accepts the partner as the sold-to party for the release order.
Note
If you create a contract with reference to another contract, the system does not run a check and it copies all the partners created in the target contract. If you do not want it to do this, use copying control in Customizing to change it.
Regards.
Mikel

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

PO Document type

Hi,
How to configure to get only the required document types for Purchase order
Regards,
Sattuj

Hi,
If you don't want to see the SAP Standard PO Document Types in Search Help of ME21N or any other Transaction then the only option is to delete these document types from config. (Path: - SPRO > MM > Purchasing > Purchase Order > Define Document Types).
But it is not recommended to delete the SAP Standard PO Document Types since in future if you want to create any new PO document type then you need to by copying SAP Standard PO Document Types.
It is suggested to control the usage of SAP Standard PO Document Types by Authorization using Authorization Object M_BEST_BSA (Take help of BASIS Consultant). By this SAP Standard PO Document Types will be visible in the search help but user will not be able to use these.

Po document type to a tcode

Hi,
1.i have created a new feild settings for a PO and assing that to a particular document type.Is there any way to make a Price feild in dispaly mode in ME22n tcode for that document type only not to all.
What is the way to find out whether the price feild is dispaly aothorisation in tcode me22n for a particular user

hii SP,
there are several ways to do it
first go to IMG - MM - Purchasing - Purchase Order -- Screen layout at document level
Select your document ME21n or ME22n
then select quantity and price
make price and price unit as DISPLAY
If you are maintaining purchase inforecord then 2nd option is goto M/06
select your condition type
in changes can be made area make manual entry as
B Automatic entry has priority OR D Not possible to process manually
Third option using authorizations
rgrds,
Shweta

PO Document type Authorizations

Similar Messages

Maybe you are looking for