Field Selection Control of the

Batch master Case study

Table of Contents
Introduction....................................................................................................................................................... 3
Situations where above Authorization requirements are called for....................................................................3
Procedure for Restricting the access to maintenance of particular Class......................................................3
Procedure for Restricting the access to maintenance of particular Characteristic.........................................3
Procedure for Restricting the access to Assign objects for a particular Class...............................................3
Procedure for Restricting the access to maintaining particular characteristic in classification of assigned
object............................................................................................................................................................. 4
Case Study....................................................................................................................................................... 4
Master Data used:......................................................................................................................................... 4
Requirements :.............................................................................................................................................. 4
Solution steps:............................................................................................................................................... 5
Copyright........................................................................................................................................................... 6

Introduction
In any SAP implementation where Batch management is used, there may be Field Selection control related
requirements.
This article explains the following requirements with corresponding solutions along with example in the form
of a Case study

Production date field mandatory, Available from field hidden for all Batches in Transactions
MSC1N & MSC2N
Production date, Shelf life expiration date fields mandatory for all Batches in Transactions
MSC1N
Production date as display (no input) for batches of the Plant 1000 only in Transactions MSC1N
& MSC2N
Production date, Shelf life expiration date fields mandatory for batches of the Plant 1000 only in
Transactions MSC1N & MSC2N

General configuration overview

In the batch master record data, for the input fields, based on requirements fields can be made Required,
Optional or Hidden and input parameters can be controlled per transaction(ex: MSC1N, MSC2N, MSC3N)
All the screen fields in Batch master are assigned to certain Field Selection groups in Standard SAP. Each
field selection group can be maintained as Optional, Required, Hidden or Display only per Transaction
MSC1/MSC2/MSC3/MSC4. As the transactions MSC1, MSC2, MSC3, MSC4 are obsolete; this configuration
reflects in enjoy batch transactions MSC1N, MSC2N, MSC3N & MSC4N respectively.
Relevant Configuration navigation given below:
Logistics General -> Batch Management -> Batch Master -> Field Selection Batch Master -> Assign Fields to
Field Selection Groups
Logistics General -> Batch Management -> Batch Master -> Field Selection Batch Master -> Edit Field
Selection Control
For any additional requirements which cannot be realized with the above configuration, Business Add-In
BATCH_MASTER method SINGLE_FIELD_CONTROL can be used.

Production date field mandatory, Available from field hidden for all Batches in Transactions MSC1N &
MSC2N

Field Production Date(MCHA-HSDAT), Available from (MCHA-VERAB) are assigned to Field Selection
Group 003 in standard SAP configuration

As Field Selection Group 003 has other fields assigned, these fields need to be assigned with new Field
Selection Group.
Assign Field Selection Group 020 to Field Production Date (MCHA-HSDAT) & Field Selection Group 021
to Field Available from (MCHA-VERAB) as shown below.

In the Field selection control, for Transactions MSC1, MSC2 select appropriate position 020 and double
click; change the field option as Required Entry. This will make Field Production date as mandatory in
both the transactions MSC1N & MSC2N.

In the Field selection control, for Transactions MSC1, MSC2 select appropriate position 021 and double
click; change the field option as Display

Observe that in transaction MSC2N, Production date has become mandatory field & Available from field
as display only.

.
Procedure for restricting the access to maintenance of particular Class

Use Transaction CL02, Go to Basic Data tab.

Specify Authorization Group 'X' in the field Class Maintenance.
Specify this Authorization Group 'X' in the authorization object BGRKP in Role of required user in
Transaction PFCG.
User who is having Authorization group 'X' in the authorization object BGRKP can access only those
classes which are having Authorization Group 'X'.

Procedure for restricting the access to maintenance of particular Characteristic

Use Transaction CT04, Go to Basic Data tab.

Specify Authorization Group 'Y' in the field Authorization Group.
Specify this Authorization Group 'Y' in the authorization object C_CABN_GRP -ATATCH in Role of
required user in Transaction PFCG.
User who is having Authorization group 'Y' in the authorization object C_CABN_GRP can access only
those Characteristics which are having Authorization Group 'Y'.

Procedure for restricting the access to assign objects for a particular Class

Use Transaction CL02, Go to Basic Data tab.

Specify Authorization Group 'Z' in the field Classification.
Specify this Authorization Group 'Z' in the authorization object BGRKL in Role of required user in
Transaction PFCG.
User who is having Authorization group 'Z' in the authorization object BGRKL can assign only those
classes which are having Authorization Group 'Z' to the Objects like Material

Procedure for restricting the access to maintaining particular characteristic in classification of

assigned object
Create organizational Areas in Customizing.
Navigation: SPRO -> Cross-Application Components -> Classification system -> Classes ->Maintain Object
Types and class types
Select Table CABN, double click on Organizational Areas; click on New Entries.
Add organizational areas A, B for class type 001.
Use Transaction CL02, Go to Basic Data tab.
Specify, for example A, B in Organizational Areas field in Basic Data tab.
Specify Organizational Area A for set of characteristics and B for other set of Characteristics in Char data tab.
Specify Organizational Area A in the authorization object SICHT in Role of required user in Transaction
PFCG.
User who is having Organizational Area A in authorization object SICHT can maintain only those
Characteristics which are having organizational area A in the respective class.

Case Study

Master Data used:

1. Characteristics
a) Pump_type Char 04
b) Pump_size Char 04
c) Tool_Type Char 07
d) Tool_Size Char 06

values
values
values
values

(PT01, PT02, PT03)

(PS01, PS02, PS03)
(Jig, Fixture)
(Small, Medium, Big)

2. Classes
a) Pump_Class Class type: 001
Assign Characteristics : Pump_Type
Pump_Size
b) Tool_Class Class Type: 001
Assign Characteristics : Tool_Type
Tool_Size
3. Users
a) ENGG1
b) ENGG2
c) ENGG
d) TENG
4. Roles
a) Z_ENGG_1

b) Z_ENGG_2
c) Z_ENGG
d) Z_TENG
Requirements:
1. User ENGG1 should have following authorizations
Access to maintenance of only Characteristic Pump_type in CT04 transaction
Access to assign the Pump_class to Materials in MM01 or CL24N transactions
Access to modify/maintain only characteristic Pump_type in Material master
2. User ENGG2 should have following authorizations
Access to maintenance of only Characteristic Pump_size in CT04 transaction
Access to assign the Pump_class to Materials in MM01 or CL24N transactions
Access to modify/maintain only characteristic Pump_size in Material master
3. User ENGG should have following authorizations
Access to maintenance of Characteristics Pump_type, Pump_size in CT04 transaction
Access to maintenance of only Class Pump_class in CL02 transaction
Access to assign the Pump_class to Materials in MM01 or CL24N transactions
Access to modify/maintain both Pump_type and Pump_size characteristics in Material master
4. User TENG should have following authorizations
Access to maintenance of Characteristics Tool_type, Tool_size in CT04 transaction
Access to maintenance of only Class Tool_class in CL02 transaction
Access to assign the Tool_class to Materials in MM01 or CL24N transactions
Access to modify/maintain both Tool_type and Tool_size characteristics in Material master
Solution steps:
1. In Characteristic Pump_type specify authorization group ZE1
2. In Characteristic Pump_size specify authorization group ZE2
3. In Characteristic Tool_type specify authorization group ZT1
4.
5. In Characteristic Tool_size specify authorization group ZT1
6. In Class Pump_class specify authorization group ZP1 in Class Maintenance & Classification
7. In Class Tool_class specify authorization group ZT2 in Class Maintenance & Classification.
8. Create Organizational Areas in Customizing
9.
10. Nav: SPRO -> Cross-Application Components -> Classification system -> Classes ->Maintain Object
Types and class types
Select Table CABN, double click on Organizational Areas; click on New Entries.
Add following entries
Class type Org. Area
Organizational Area Desc
001
A
Engineering 1
001
B
Engineering 2
001
C
Tool Engineering

8. In Class Pump_Class Specify Organizational Areas A & B in Basic Data. Select Organizational Area A for
Characteristic Pump_type; Select Organizational Area B for characteristic Pump_size.
9.

Maintain following parameters for Role Z_ENGG_1 in Transaction PFCG

Authorization
C_CABN_GRP
C_KLAH_BKL
C_TCLS_BER
C_TCLS_MNT

Authorization Object
ATAUTH
BGRKL
SICHT
SICHT

Value
ZE1
ZP1
A
A

10. Maintain following parameters for Role Z_ENGG_2 in Transaction PFCG

Authorization
C_CABN_GRP
C_KLAH_BKL
C_TCLS_BER
C_TCLS_MNT

Authorization Object
ATAUTH
BGRKL
SICHT
SICHT

Value
ZE2
ZP1
B
B

11. Maintain following parameters for Role Z_ENGG in Transaction PFCG

Authorization
C_CABN_GRP
C_KLAH_BKP
C_KLAH_BKL
C_TCLS_BER
C_TCLS_MNT

Authorization Object
ATAUTH
BGRKP
BGRKL
SICHT
SICHT

Value
ZE1, ZE2
ZP1
ZP1
A, B
A, B

12. Maintain following parameters for Role Z_TENG in Transaction PFCG

Authorization
C_CABN_GRP
C_KLAH_BKP
C_KLAH_BKL
C_TCLS_BER
C_TCLS_MNT

Authorization Object
ATAUTH
BGRKP
BGRKL
SICHT
SICHT

13. Assign roles to Users as specified below

User
ENGG1
ENGG2
ENGG
TENG

Role
Z_ENGG1
Z_ENGG2
Z_ENGG
Z_TENG

Value
ZT1
ZT2
ZT2
C
C