Hierarchy
DMIS_CNT (Software Component) DMIS_CNT 2011_1⤷
CA-EUR (Application Component) European Monetary Union: Euro⤷
CNV_TDMS_HCM_620_A (Package) TDMS4HMC - Release 620 and higher releases
IMG Activity
| ID | TDHC0_CUSTM_CPARDEF1 | Define Tables for Table Transfer Groups |
| Transaction Code | S_SR9_69000022 | (empty) |
| Created on | 20120716 | |
| Customizing Attributes | TDHC0_CUSTM_CPARDEF1 | Define Tables for Table Transfer Groups |
| Customizing Activity | TDHC0_CUSTM_CPARDEF1 | Define Tables for Table Transfer Groups |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | TDHC0_CUSTM_CPARDEF1 |
Use
In this activity, you define tables that you can assign to groups or categories. This allows you to transfer your own client dependent tables without any extra programming.
The tables in these groups are not infotypes or cluster tables. The program automatically transfers infotypes and cluster tables.
If you want to include a development class that contains infotypes, use the exclude option at table level to exclude them. The example below illustrates this.
Integration
This activity is optional.
Prerequisites
The phase must be active in order to maintain customizing data, and you must already have executed the previous activity Define Tables for Customer Table Transfer Groups. This activity occurs in the sender system. If you are unable to make changes here directly then you must make changes in another system and then transport them. You can use the Maintain Table Views transaction (SM30) to do this. The view is the V_CNVHCM_CPARDEF.
Note that if you want to define PD tables then it is obligatory that the tables contain the field OTYPE which must correspond to the usual PD object types. The field must be a character field called "OTYPE" with the length 2. This is necessarry because it's possible that the transfer program collects different key areas for different object types and without OTYPE information in the PD table we don't know which set of keys to use.
Note also that the field you define that is used to select the data must correspond to either:
a PERNR for PA tables
an OBJID for PD tables
This means that it must be defines as being NUMC with a length of 8 (exactly like the PERNR and OBJID fields). If you fail to do so, there will be no check at this point but within the transfer program this is checked and if the selection fiield has a different format then the table will not be transferred. If the table is a PD table then a check is made that the OTYPE is defined in the table.
Activities
You have decided that you want to transfer your own tables.
Example
You defined some 'Z' tables and some infotypes in a 'Z' development class. You want to transfer the 'Z' tables that include a personnel number. The program transfers the infotypes automatically according to the Transfer Master Data and Infotypes settings.
You maintain the table in the following way:
Maintain the fields:
Table Grouping
Enter the "Transfer Group" that you defined the previous activity, Define Tables for Customer Table Transfer Groups.
Seqnr
This is a sequence number that must be different from the other ones within the specific transfer group.
DEVC/Table
Enter DEVCLASS or TABLE (development class or table).
- I/E
Include or Exclude. A TABLE entry can be either included or excluded, but a DEVCLASS entry can only be included.
- Option
CP = contains pattern, BT = between, EQ = equals
- Lower Value
Enter the name of your development class or table. If you have chosen the option "CP" then you can enter a generic value in the form "Zxxxx*". The star ( '*' ) can only be the last value entered. For example, "Z*xxx" would not work.
- High Value
This works in the same way as the Lower Value field.
- Obj.Type
You enter 'P' if you are dealing with a PA table with a personnel number. If not, then you must enter a PD object type if the table you want to read has a specific object type. If the PD table contains more that one object type that you want to transfer then you should leave the field empty.
- Domain name / Data element / Field name.
The transfer program must know how it should read the tables selected. You must provide information about a field that will be used to read the table. For further information see the following documentation: Valid Domain / Data Element / Field combinations
Example (Continued):
Table Grouping: Z_<table group>
Seqnr: 1
DEVC: DEVC
Table I/E: I
Op: CP
Lower Value: Zxxx*
High Value: SPACE
Obj.Type: P
Domain: SPACE
Data element: SPACE
Field: PERSNO
Table Grouping: Z_<table group>
Seqnr: 2
DEVC: TABLE
Table I/E: E
Op: CP
Lower Value: PA*
High Value: SPACE
Obj.Type: P
Domain: SPACE
Data element: SPACE
Field: SPACE
The first entry includes all tables of the "Zxxx*" development class or classes that are related to the personnel number, and whose key has the PERSNO domain.
The second entry excludes the PA* tables, that is, the infotypes.
The activity has a test function. You can select one of more lines and click on the test icon to determine which tables the program selects using the current criteria. The transfer program returns all the tables that are selected for a given table grouping. You can select a subsection of a table grouping (which may not always be logical). If you select only "E" entries (exclude), then nothing is selected.
This data must be available in the sender system.
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 2 | Optional 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 | TDHC0_CUSTM_CPARDEF1 | 0 | HLB0009110 | Cross-Application Components |
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 |
| V_CNVHCM_CPARDEF | V - View | SM30 |
History
| Last changed by/on | SURANA | 20121227 |
| SAP Release Created in | 2011_1_700 |
