Hierarchy
⤷ IS-PS-CA (Application Component) Public Sector Contract Accounting
⤷ FMCA_PSOB (Package) PSCD: Contract Object
IMG Activity
ID | _ISPSFICA_PSOB0100 | Configure Field Attributes for Each Activity |
Transaction Code | S_KK4_82000321 | IMG Activity: _ISPSFICA_PSOB0100 |
Created on | 20000721 | |
Customizing Attributes | _ISPSFICA_PSOB0100 | Configure Field Attributes for Each Activity |
Customizing Activity | _ISPSFICA_PSOB0100 | Configure Field Attributes for Each Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _ISPSFICA_PSOB0100 |
Depending on the Activity in question, you determine in this activity which fields during account master data maintenance:
- Require an entry to be made (required entry)
- Do not require an entry to be made (optional entry)
- Can be displayed (display)
- Are hidden (Hide)
Your entry is linked with the field status for the other criteria (per field). This link determines the status of the field on the entry screen for the master data.
Link Rules
- Linking the same criteria
The same criteria can be two or more roles, for example, that a business partner can have, or several roles that can be grouped together into a role grouping.
The field statuses for two identical criteria are linked, and then the result is linked with the third criterion and so on. Required entry has the highest priority here, followed by optional entry, display, hide and the non-specified entry.
In this way the field status is reduced to a single status.
Examples of linking:
Criterion 1 Hide Op.Entry Op.Entry
Criterion 2 Op.Entry Display Req.Entry
Interim Result Op.Entry Op.Entry Req.Entry
- Linking all remaining different criteria (apart from the activity)
Different criteria can be, for example, role(s) and BP type (application object business partner) or relationship category and client (application object relationships).
The field statuses for two different criteria are linked, and then the result is linked with the third criterion and so on. Required entry has the highest priority here, followed by optional entry, display, hide and the non-specified entry.
Examples of linking:Criterion 1 Hide Op.Entry Op.Entry
Criterion 2 Op.Entry Display Req.Entry
Interim Result Op.Entry Op.Entry Req.Entry
- Linking the result with the activity
The result from above is linked with the field status for the activity. In principle, the same rules apply as above. In addition, the activity display means that all the fields are no longer ready for input.
Examples of linking:Interim Result Req.Entry Req.Entry Op.Entry
Field Status Act. Op.Entry Non-spec. Display
Data Maint. Act. Create Display Change
Result Req.Entry Display Display
Example
Only in exceptional cases should it be necessary to control the field status via the activity, for example, if an entry is to be made in a field when it is created, but should not be changeable later.
Activities
Check and, if necessary, change the attributes in the delivery system.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | _ISPSFICA_PSOB0100 | 0 | I500000220 | Public Sector Contract Accounting |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VV_TB105_PSOB | V - View | SM30 |
History
Last changed by/on | SAP | 20010802 |
SAP Release Created in | 462 |