Authorization Check in SD for Price and Credit,Debit and Returns Block

Dear Gurus,
Need your help on this
Whom so ever is creating the sales order should not able to see the price of the product on the header and item of the screen of the Sales order or Profit Margin
Whom so ever is creating credit, debit, return request should not be able to release billing and delivery block from the sales order screen of VA01
How can I stop this in authorization . Which authorization object shall I use in this case
Kindly guide me in this
Thanks
Krishna

Hi Krishna
If nobody should see the price of the product at header and item level then you have to go with a enhancement that price condition type should not be viewed.
For Credit , Debit and Return process , if release to billing is there then go with a output that once the billing is blocked then a output should get triggered and that output should go to the concerned person and he should release to billing. and for delivery block maintain delivery block for the sales document type and keep the delivery block feild in disable mode.so in the same way for billing to release to billing as one output type has to be configured in the same way for delivery block also maintain another output type and once the delivery is blocked some person will release the block to create the delivery document.
Thanks and Regards
Srinath

Similar Messages

Credit ,Debit and Derict Debit Transaction

Hi all,
Does anyone know how to do Credit ,Debit and Derict Debit Transaction. I don�t mean the html coding, javascript validation for the form. What i am talking about is that the server is a � point of sale � that the server does the transaction with the financial institutions. If you have a good book has a referal it would be greatly appreciated.
The raison that i am asking these question on this forum is due to the fact that i was told that there is a JAVA API that is freely avalable. I was told that Java has documentations and that there should be some JAVA API for e-transaction, e-check as some might call it. But i have been unable to find it.
If any of you have any suggestion please feel free to post them.
Thank you for you time.

Try the following forum (about EJB technology)
http://forum.java.sun.com/forum.jspa?forumID=13

Authorization check when searching for transactions

Hi all,
We have a requirement to show only those activities for which a user is authorized. A custom authorization object has been maintained and the check in CRMD_ORDER has been extended accordingly. When opening an activity, the check is executed correctly, but when searching for activities, ALL activities are still shown, so the check is not performed at that particular moment. I have tested with standard authorization objects as well, but none of them are taken into account. Does anyone of you know how we can have the authorization check executed before or during the search, so that only those activities are shown, that the user may maintain as well.
Thanks in advance!
Regards,
Joost

Hello Joost,
Check if BADI CRM_ORDER_INDEX_BADI could not map your requirement.
Regards,
Frédéric

Balance Sheet G/L-PL reporting for period range by debit and credit amounts

Hi, good afternoon
This report displays period intervals. One column must display G/L accounts and the others must perform: Initial balance, total debit and total credit.
Example:
<b>Period: mm.dd.yyyy to mm.dd.yyyy</b>
Columns:
G/L Account - Initial Balance - debit - credit - Current Balance
Thanks for attention, ragards!

Hi, I do not get what exactly your question is, but I think you are looking for a "report"
I do not remember any that meets exactly your requirements. I have seen similar reports... but you can only define the periods, not the dates.
Check this one:
S_ALR_87012277
You should take a look to these too:
S_PL0_86000030
S_PL0_86000031
Regards

R12 ACH for wellsfargo (NACHA/CREDIT/DEBIT)

Hi
I am working on 11i to R12 upgrade project.
I need to create and implement ACH(NACHA/CREDIT/DEBIT) format in R12 environment.Can someone tell me how should i do that
All I have is SQL and flatfile from 11.5.10 instance
Do I need to create a Etext RTF template? My bank is wellsfargo
appreciate your reply
kp

Hi,
I'm having the same issue right now. Were you able to resolve the template issue? We are upgrading from 11i to R12 and we also use Wells Fargo. I have been trying for days to create an xml template and can't seem to make it work with etext or an rtf. I need the output to be in text to send to the bank's payment manager. If you were able to create a template, would you be able to share the template with me?
Thank you...
Elizabeth

Outbound IDoc for AR Correspondence (Credit/Debit Memo)

We currently use the Print Correspondence function to generate automatic correspondence. In transaction OB78 we have each correspondence type linked to a print program which generates a .pdf "AR Invoice" via SAPScript.
Our new requirement is to generate an Outbound IDoc for the same miscellaneous AR Correspondence output. There does not seem to be any configuration means by which to generate an IDoc for these financial documents. Enhancement RFKORIEX only allows for fax or email.
Please advise how to generate IDoc via configuration without extensive coding.

We currently use the Print Correspondence function to generate automatic correspondence. In transaction OB78 we have each correspondence type linked to a print program which generates a .pdf "AR Invoice" via SAPScript.
Our new requirement is to generate an Outbound IDoc for the same miscellaneous AR Correspondence output. There does not seem to be any configuration means by which to generate an IDoc for these financial documents. Enhancement RFKORIEX only allows for fax or email.
Please advise how to generate IDoc via configuration without extensive coding.

Authorization checks and objects

Do you have a tutorial for this topic for dummies? thanx in advance

Hi
In general different users will be given different authorizations based on their role in the orgn.
We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.
USe SUIM and SU21 T codes for this.
Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.
If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.
This means you have to allocate an authorization object in the definition of the transaction.
For example:
program an AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT <authorization object>
ID <authority field 1> FIELD <field value 1>.
ID <authority field 2> FIELD <field value 2>.
ID <authority-field n> FIELD <field value n>.
The OBJECT parameter specifies the authorization object.
The ID parameter specifies an authorization field (in the authorization object).
The FIELD parameter specifies a value for the authorization field.
The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.
http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.
You program the authorization check using the ABAP statement AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '02'
ID 'CUSTTYPE' FIELD 'B'.
IF SY-SUBRC <> 0.
MESSAGE E...
ENDIF.
'S_TRVL_BKS' is a auth. object
ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.
The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.
This Authorization concept is somewhat linked with BASIS people.
As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.
Take the help of the basis Guy and create and use.
Thanks
Seshu

Authorization check for KE24

Hi all,
Need to enforce an authorization check on KE24 for certain users are allowed to view records pertaining to some profit centers.
SAP suggested to use KE97 for Authorization Check.
If anybody knows step-by-step document to do this pls share with me.
Thanks

HI,
well, I know that this own-defined authorization objects are working well (I used this once for own defined customer groups), but I am not totally sure what needs to be done in the user authorization maintenance to make it running (my former user-authorization responsible colleague did that).
Maybe its because your test-user has some other user rights that overrule the BUKRS / PRCTR restriction.
So try first to create a test-user with only KE24 authorization AND the limitation to one company code / profit center combination of your new created authorization object to ensure that this works fine.
Second step is to check how this authorization works in combination with all other authorization objects your users will have.
Best regards, Christian

What are authorization checks? And where and what will you write?

hai, plz anybody send me the answer?

Hi
In general different users will be given different authorizations based on their role in the orgn.
We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.
USe SUIM and SU21 T codes for this.
Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.
If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.
This means you have to allocate an authorization object in the definition of the transaction.
For example:
program an AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT <authorization object>
ID <authority field 1> FIELD <field value 1>.
ID <authority field 2> FIELD <field value 2>.
ID <authority-field n> FIELD <field value n>.
The OBJECT parameter specifies the authorization object.
The ID parameter specifies an authorization field (in the authorization object).
The FIELD parameter specifies a value for the authorization field.
The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.
http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.
You program the authorization check using the ABAP statement AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '02'
ID 'CUSTTYPE' FIELD 'B'.
IF SY-SUBRC <> 0.
MESSAGE E...
ENDIF.
'S_TRVL_BKS' is a auth. object
ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.
The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.
This Authorization concept is somewhat linked with BASIS people.
As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.
Take the help of the basis Guy and create and use.
As the name suggest it if for Authority check so that the person who is not having authorization for some data/transaction can be restricted from viewing it. It is very imortant for the security of data. Check below link for details on authorization.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbaccb35c111d1829f0000e829fbfe/content.htm

Credit Check (maximum percentage for open items exceeded)

HI
Can you tell how to release for this block manually which is coming while creating a SO
Regards,
Romesh

Hi,
You can release the credit blocked Sales documents by using VKM3 or VKM5.
Other way is to go to the T-code OVA8 and then select the credit control area, Risk category of the customer, and credit Group and then double click on it.
with respect to Open items field there will be field Max.open.item % a and NoDays openI, so manipulate the values in those fields to oveercome the problem.

LIV tolerance for price variance from PO to LIV

Hi Friends,
I am finding difficulty in setting up the tolerance key for price variance from PO value to invoice value. Suppose if PO price is $100 then system should allow upto $105 with out blocking means with percentage of 5%. If it exceeds 5% system should block the invoice.
Please suggest the tolerance key to use and if any other settings required.
Thanks...
Best Regards

Hi,
Following is the SAP help on the Tolerance settings for Invoice. Check the config and decide what is best for you (from your brief explanation it looks like AP and PP may be relevant fro your case)
===================
Set Tolerance Limits
    In this step, you specify the tolerance limits for each tolerance key
    for each company code.
    When processing an invoice, the R/3 System checks each item for
    variances between the invoice and the purchase order or goods receipt.
    The different types of variances are defined in tolerance keys.
    The system uses the following tolerance keys to check for variances:
    o   AN: Amount for item without order reference
        If you activate the item amount check, the system checks every line
        item in an invoice with no order reference against the absolute
        upper limit defined.
    o   AP: Amount for item with order reference
        If you activate the item amount check, the system checks specific
        line items in an invoice with order reference against the absolute
        upper limit defined. Which invoice items are checked depends on how
        you configure the item amount check.
    o   BD: Form small differences automatically
        The system checks the balance of the invoice against the absolute
        upper limit defined. If the upper limit is not exceeded, the system
        automatically creates a posting line called Expense/Income from
        Small Differences, making the balance zero and allowing the system
        to post the document.
    o   BR: Percentage OPUn variance (IR before GR)
        The system calculates the percentage variance between the following
        ratios: quantity invoiced in order price quantity units : quantity
        invoiced in order units and quantity ordered in order price quantity
        units : quantity ordered in order units. The system compares the
        variance with the upper and lower percentage tolerance limits.
    o   BW: Percentage OPUn variance (GR before IR)
        The system calculates the percentage variance between the following
        ratios: quantity invoiced in order price quantity units: quantity
        invoiced in order units and goods receipt quantity in order price
        quantity units : goods receipt quantity in order units. The system
    compares the variance with the upper and lower percentage limits
    defined.
o   DQ: Exceed amount: quantity variance
    If a goods receipt has been defined for an order item and a goods
    receipt has already been posted, the system multiplies the net order
    price by (quantity invoiced - (total quantity delivered - total
    quantity invoiced)).
    If no goods receipt has been defined, the system multiplies the net
    order price by (quantity invoiced - (quantity ordered - total
    quantity invoiced)).
    The system compares the outcome with the absolute upper and lower
    limits defined.
    This allows relatively high quantity variances for invoice items for
    small amounts, but only small quantity variances for invoice items
    for larger amounts.
    You can also configure percentage limits for the quantity variance
    check. In this case, the system calculates the percentage variance
    from the expected quantity, irrespective of the order price, and
    compares the outcome with the percentage limits configured.
    The system also carries out a quantity variance check for planned
    delivery costs.
o   DW: Quantity variance when GR quantity = zero
    If a goods receipt is defined for an order item but none has as yet
    been posted, the system multiplies the net order price by (quantity
    invoiced + total quantity invoiced so far).
    The system then compares the outcome with the absolute upper
    tolerance limit defined.
    If you have not maintained tolerance key DW for your company code,
    the system blocks an invoice for which no goods receipt has been
    posted yet. If you want to prevent this block, then set the
    tolerance limits for your company code for tolerance key DW to Do
    not check.
o   KW: Variance from condition value
    The system calculates the amount by which each delivery costs item
    varies from the product of quantity invoiced * planned delivery
    costs/ planned quantity. It compares the variance with the upper and
    lower limits defined (absolute limits and percentage limits).
o   LA: Amount of blanket purchase order
        The system determines the number of days by which the invoice is
        outside the planned time interval. If the posting date of the
        invoice is before the validity period, the system calculates the
        number of days between the posting date and the start of the
        validity period. If the posting date of the invoice is after the
        validity period, the system calculates the number of days between
        the posting date and the end of the validity period. The system
        compares the number of days with the with the absolute upper limit
        defined.
    o   PP: Price variance
        The system determines by how much each invoice item varies from the
        product of quantity invoiced * order price. It then compares the
        variance with the upper and lower limits defined (absolute limits
        and percentage limits).
        When posting a subsequent debit/credit, the system first checks if a
        price check has been defined for subsequent debits/credits. If so,
        the system calculates the difference between (value of subsequent
        debit/credit + value invoiced so far) / quantity invoiced so far *
        quantity to be debited/credited and the product of the quantity to
        be debited/credited * order price and compares this with the upper
        and lower tolerance limits (absolute limits and percentage limits).
    o   PS: Price variance: estimated price
        If the price in an order item is marked as an estimated price, for
        this item, the system calculates the difference between the invoice
        value and the product of quantity invoiced * order price and
        compares the variance with the upper and lower tolerance limits
        defined (absolute limits and percentage limits).
        When posting a subsequent debit/credit, the system first checks
        whether a price check has been defined for subsequent
        debits/credits, If so, the system calculates the difference between
        (value of subsequent debit/credit + value invoiced so far) /
        quantity invoiced so far * quantity to be debited/credited and the
        product quantity to be debited/credited * order price. It then
        compares the variance with the upper and lower tolerance limits
        defined (absolute limits and percentage limits).
    o   ST: Date variance (value x days)
        The system calculates for each item the product of amount *
        (scheduled delivery date - date invoice entered) and compares this
        product with the absolute upper limit defined. This allows
        relatively high schedule variances for invoice items for small
        amounts, but only small schedule variances for invoice items for
        large amounts.
    o   VP: Moving average price variance
        When a stock posting line is created as a result of an invoice item,
        the system calculates the new moving average price that results from
        the posting. It compares the percentage variance of the new moving
        average price to the old price using the percentage tolerance limits
        defined.
    Variances are allowed within predefined tolerance limits. If a variance
    exceeds a tolerance limit, however, the system issues a message
    informing the user. If an upper limit (except with BD and VP) is
    exceeded, the invoice is blocked for payment when you post it. You must
    then release the invoice in a separate step. If the tolerance limit for
    BD is breached, the system cannot post the invoice.
    Note that if you set all limits for a tolerance key to Do not check, the
    system does not check that tolerance limit. Therefore any variance would
    be accepted. This does not make sense particularly in the case of the
    tolerance key Form small differences automatically.
    Activities
    Configure the tolerance limits for the individual tolerance keys.
                 Lower limit             Upper limit
                 Absolute    Percentage Absolute    Percentage
     AN          -           -           X           -
     AP          -           -           X           -
     BD          X           -           X           -
     BR          -           X           -           X
     BW          -           X           -           X
     DQ          -           -           X           -
     DW          -           -           X           -
     KW          X           X           X           X
     LA          -           -           X           X
     LD          X           -           X           -
     PP          X           X           X           X
     PS          X           X           X           X
     ST          -           -           X           -
     VP          -           X           -           X
===============================================
Best Regards,
Siva

Credit limit and last paid amount by the customer

Hello,
I have one requirement in Account Receivable cube (0FI_AR_4). I need to find CREDIT LIMIT and LAST PAID DATE
So I had done the enhancement for 0FI_AR_4 data source and populated the required values. I had checked in RSA3 for the accuracy of data and everything looks fine.. (in RSA3 every line item for particular customers will be populated with the Credit limit and last paid date. )
Then I created 2 Info Object KEY FIGURES in BW and added it to the 0FI_AR_4 Cube.. .. the info object should display only the latest credit limit maintained and the last payment date for the particular customer. So i have some doubt about the property setting of the INFO OBJECT. Could any one please assist me, what setting is required to fetch only latest credit limit and last payment date.
Thanks
Sachin

Dear Sachin
The credit limit and last payment date is available as part of the standard source FI_AR_9.
Now if you have appended the same in the FI_AR_4 , you can maintain both the fields as keyfigure. For credit limit bring in the currency also in the append
Credit Limit - Keyfigure as Amount with Unit 0CURRENCY
Date of last payment - Keyfigure as Date
Regards
Gajesh

How to set authorization in more detail for ME11,e.g. material group, etc.?

Hi,
As we know, we can use plant, purchasing organization, purchasing group as authorization object to carry out authorization check when creating purchasing info record in ME11.
But now my customer wants to set authorization in more detail, for example, use material group and some certain fields in vendor master.
It seems standard authorization setting for ME11 cannot do this.
Is there any method to meet the need? or some enhancements or BADi?
Thanks
Wesley

Hi, Akhileshwar
Thanks for your information. I have thought of creating authorization object values, but the problem is where to let SAP carry out the authorization check to the new object in ME11/ME12.
So I think maybe some enhancements can let us write authority check code to do it.
But I am not sure which enhancement or user exit can be used to write this code.
Wesley

Authorization check

Hi ,
i new to authorization so i need help ,
i go to transaction SU21 and i choose some object for example:
Object R_CPM_BSC
Text Authorization Object SEM: BSC Elements
Class SEM Strategic Enterprise Management*
Author STASTNY
Field name Heading
SEMSCARD Scorecard
SEMOBJTYPE Scorecard Elements: Object Type
SEMOBJKEY Scorecard Elements: Object Key
ACTVT Activity
And when i push on permitted activities i get:
R_CPM_BSC Authorization Object SE
ACTVT Activity
activists
01 Create or generate
02 Change
03 Display
04 Print, edit messages
1. i have always just permitted activities for ACTVT ?
if i wont that user just have display Authorization how i have to write it like below?
AUTHORITY-CHECK OBJECT R_CPM_BSC
ID ACTVT FIELD '03'
thats it i don't use the other fields?
Regards

Hi,
In general different users will be given different authorizations based on their role in the orgn.
We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.
USe SUIM and SU21 T codes for this.
Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.
If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.
This means you have to allocate an authorization object in the definition of the transaction.
For example:
program an AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT <authorization object>
ID <authority field 1> FIELD <field value 1>.
ID <authority field 2> FIELD <field value 2>.
ID <authority-field n> FIELD <field value n>.
The OBJECT parameter specifies the authorization object.
The ID parameter specifies an authorization field (in the authorization object).
The FIELD parameter specifies a value for the authorization field.
The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.
http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.
You program the authorization check using the ABAP statement AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '02'
ID 'CUSTTYPE' FIELD 'B'.
IF SY-SUBRC 0.
MESSAGE E...
ENDIF.
'S_TRVL_BKS' is a auth. object
ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.
The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.
This Authorization concept is somewhat linked with BASIS people.
As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.
Take the help of the basis Guy and create and use.
Thanks
Vikranth

Authorization Check Field Name

Hi,
Do we need to specify all field names when coding authorization check in abap?

Hi,
Plz go through this...
AUTHORITY-CHECK OBJECT object
ID name1 FIELD f1
ID name2 FIELD f2
ID name10 FIELD f10.
Explanation of IDs:
object Field which contains the name of the object for which the authorization is to be checked.
name1 ... Fields which contain the names of the name10 authorization fields defined in the object.
f1 ... Fields which contain the values for which the f10 authorization is to be checked.
AUTHORITY-CHECK checks for one object whether the user has an authorization that contains all values of f (see SAP authorization concept).
You must specify all authorizations for an object and a also a value for each ID (or DUMMY ).
The system checks the values for the ID s by AND-ing them together, i.e. all values must be part of an authorization assigned to the user.
If a user has several authorizations for an object, the values are OR-ed together. This means that if the CHECK finds all the specified values in one authorization, the user can proceed. Only if none of the authorizations for a user contains all the required values is the user rejected.
If the return code SY-SUBRC = 0, the user has the required authorization and may continue.
The return code is modified to suit the different error scenarios.
The return code values have the following meaning:
4 User has no authorization in the SAP System for such an action. If necessary, change the user master record.
8 Too many parameters (fields, values). Maximum allowed is 10.
12 Specified object not maintained in the user master record.
16 No profile entered in the user master record.
24 The field names of the check call do not match those of an authorization. Either the authorization or the call is incorrect.
28 Incorrect structure for user master record.
32 Incorrect structure for user master record.
36 Incorrect structure for user master record.
If the return code value is 8 or possibly 24, inform the person responsible for the program. If the return code value is 4, 12, 15 or 24, consult your system administrator if you think you should have the relevant authorization. In the case of errors 28 to 36, contact SAP, since authorizations have probably been destroyed.
Individual authorizations are assigned to users in their respective user profiles, i.e. they are grouped together in profiles which are stored in the user master record.
Instead of ID name FIELD f , you can also write ID name DUMMY . This means that no check is performed for the field concerned.
The check can only be performed on CHAR fields. All other field types result in 'unauthorized'.

Authorization Check in SD for Price and Credit,Debit and Returns Block

Similar Messages

Maybe you are looking for