Question:
Can someone please tell me why M_BANF_FRG is needed? We are currently using M_EINK_FRG to control the release/approval of requisitions based on release group and release code. (Also used for approval of PO's with a different release group value). Why then do we need M_BANF_FRG? Does it offer some other functionality that I am missing? Can someone give me a scenario where you would grant a user different release code values in these two objects. For instance:
M_BANF_FRG = release code = L5 (level 5 = $100,000)
M_EINK_FRG = release code = L3 (level 3 = $20,000) and release group = R1 (requisition strategy).
If not, or if a user would always have the same release code values in both objects when dealing with requisitions, then why are both objects needed? thanks. trent.
Answer:
Have you read the coumentatino for these objects?
M_BANF_FRG -
This authorization enables you to restrict the maintenance of purchase requisitions via the purchasing group.
Defined fields
The authorization object comprises two fields:
Purchasing group
Activity
The various authorizations for this object thus stipulate for which purchasing groups and via which activity requisitions may be processed.
Possible activities include "Display", "Create", "Change" etc.
Example
User A may create, change and display documents for all purchasing groups.
Relevant authorization: purchasing group '*', activities '1-3'.
On the other hand, user B may only display documents for one particular purchasing group.
Relevant authorization: purchasing group 'XYZ', activity '3'.
M_EINK_FRGDefinition
With this authorization object, you can determine which purchasing documents the user may release (approve) and which release codes he or she may use when doing so.
Defined fields
The authorization object comprises the following fields:
Release group
Via the release group, you define which purchasing documents the user may release.
Example
a) You have created different release groups for purchase orders for different plants. (For example: release group 01 for POs in plant 0001, release group 02 for POs in plant 0002. You can thus specify via the release group whether the user may release POs for plant 0001 only, or also for plant 0002.
b) You have created different release groups for different document categories (e.g. release group 01 for purchase orders,02 for RFQs, 03 for contracts. You can thus specify via the release group whether the user may release RFQs only, or also POs and contracts.
Release code
Via the release code, you specify the release codes with which the user may release purchasing documents.
Examples
For user Miller, the following values have been defined in the authorization object:
Release group: 01 and 02 (see example b)
Release code: 01 and 02
The user Miller may thus release POs and RFQs using the release codes 01 and 02.
_________________
Sandi
~~~~
Apparently Father Christmas, the Easter Bunny, the Tooth Fairy and Star Wars aren't real
Tuly kiwi.
Answer:
Sandi, sorry but I was asking the difference in M_EINK_FRG and M_BANF_FRG? You pasted the documentation related to M_BANF_EKG for purchasing group. I understand that object perfectly well. thanks however for taking time to respond. trent.
Answer:
Sorry, hit the wrong paste - M_BANF_FRG is for the Release code ofor requisitions, perhaps it depends on how you are using the requisition, order relase process?
Definition
This authorization object enables you to restrict the release of purchase requisitions via the release code.
Defined fields
The authorization object comprises the field 'release code' only. The various authorizations for this object thus stipulate the release codes with which requisitions may be released.
Example
User A may release requisitions for all release codes.
Relevant authorization: release code '*'.
On the other hand, user B may only effect releases for codes '01' and '02'.
Relevant authorization: release codes '01,02'.
_________________
Sandi
~~~~
Apparently Father Christmas, the Easter Bunny, the Tooth Fairy and Star Wars aren't real
Tuly kiwi.