Hierarchy
⤷ GRC-SPC (Application Component) Process Controls
⤷ GRPC_CUSTOMIZING (Package) Customizing
IMG Activity
ID | GRPC_GENERAT_INFOTYP | Generate Infotypes |
Transaction Code | S_GR1_31000113 | (empty) |
Created on | 20071121 | |
Customizing Attributes | GRPC_GENERAT_INFOTYP | Generate Infotypes |
Customizing Activity | GRPC_GENERAT_INFOTYP | Generate Infotypes |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | GRPC_GENERAT_INFOTYP |
Use
Once you have created the dictionary structure for the new infotypes, you can complete the generation of the infotype.
Requirements
Standard settings
Activities
1. Click on the Generate Infotypes activity. (You can also use transaction PPCI).
2. In the Infotype field, enter infotype number. For example, enter 9101.
3. In the Infotype Name field, enter the name of the infotype.
4. Click Create.
5. The Create Infotype screen appears. The Infotype and Infotype Name fields are automatically populated. In the Infotype Category pane, select the Field Infotype radio button.
6. Click Create.
Note: After the confirmation that the infotype has been properly created, continue bringing the infotype into the context of Process Control objects, in particular, the control.
7. Return to the initial screen for Create Infotype. (You can use transaction PPCI). Click the Change icon. A directory tree structure appears with all pertinent infotypes that can be edited.
Note: All entries in green indicate that they were generated automatically by the transaction PPCI within the creation of the infotype. These entries are good for being released and transported. The entries in orange indicate that they need to be resolved.
8. Position the cursor over the first entry in orange and select the Change icon. (You can double-click on the entry directly) For example if you double-click on the entry, T777I, which is a table entry, the Maintain Table Views: Initial Screen appears.
9. Click Maintain. The Change View "Infotypes": Overview screen appears.
10. Select the infotype you wish to resolve. For example, select infotype 9101.
11. Double-click Time Constraint.
12. Click New Entries.
13. In the Object Type field, enter an object type. In this case, select P2 for Local Process Step. You will later need to create an additional entry for P5. Use the same MT 9101 and the next object types.
14. In the Infotype field, enter the number of the infotype. In this case, use 9101.
15. Leave the Subtype field blank. In the Time Constraint field, enter a value for time constraint. In this case, enter 1.
Note:
For Object Type entries you can choose from the following:
- P2 for local control.
- P3 for reference control. This control does not contain data.
- P5 for central control.
For the Time Constraint field, you can give the following possible time constraints that are relevant for Process Control:
- The value 1 indicates that it is time-dependent without gaps. This is the most probable variant. For a given date, the relationship of the object and the infotype record is 1:1.
- The value 2 indicates that it is time-dependent with gaps. For a given date, the relationship of the object and the infotype record is 1:0 in each point of time. (There is either one infotype record or no infotype record in each point in time.)
- The value 3 indicates that there are multiple values at any time. This is good variant for tabular data where the relationship between the object and the infotype is 1:N (many). For a given date, one object can be related with zero, one, or multiple records.
16. Double-click Infotype per object type. You must include entries for two object types P2 and P5.
17. In the Infotype field, enter the infotype number. In this case, use 9101. Leave the rest of the fields blank.
18. Click the Save icon.
19. Restart the Generate Infotypes activity. (You can also use transaction PPCI).
20. Click the Change icon to confirm that the entries that were in orange are now in green. In this case, the entry T777I should now be in green.
Note: The following list displays all Process Control objects that can be enhanced:
0 Organization P7 Entity Level Control
P0 Local Process P8 Local Account Group
P1 Local Subprocess P9 Local Entity Level Control
P2 Local Process Step PK Central Process
P3 Referred Process Step PL Central Subprocess
P4 Process in Scope PM Control Objective
P5 Central Process Step PN Risk
P6 Account Group PQ Test Plan
21. To get your new fields into SAP GUI (transaction GRPC_STR_CHAGE), return to the Generate Infotype screen. (Use transaction code PPCI).
22. Click the Create icon.
23. Navigate to Choose Infotype>Create Subscreen. You have properly generated the storage for your data. Your data objects are attached to Process Control objects and are time-dependent.
24. To check your new data storage and add data to your objects, use transaction code, PP01.
25. The Maintain object screen appears. This screen allows you to maintain HR-Org data.
26. In the Plan Version field, specify a version. Usually, the plan version is "01".
27. In the Object Type field, select an object. In this case, select a local process step (P2).
28. In the Object ID field, enter an object ID.
29. Click Enter.
Example
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-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 | GRPC_GENERAT_INFOTYP | 0 | GR11000001 | Process Controls |
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 |
IMGDUMMY | D - Dummy object | PPCI |
History
Last changed by/on | SAP | 20071121 |
SAP Release Created in | 250 |