Ansicht
Dokumentation
/ISDFPS/ASSIGN_KEYS - Assign Customer Tables
Vendor Master (General Section) General Data in Customer MasterThis documentation is copyright by SAP AG.
In this customizing activity you can connect a Customer Table to IDOCS.
- The table area Table Assignment (/ISDFPS/CT_TABLE) defines the link between the standard table, the customer table, and object type.
- The table area Field Assignment( /ISDFPS/CT_FIELD) defines the key fields relation between the standard table and the customer table.
- You can overwrite the master data “Changed On” information via Field - Change Date in Table Assignment.
In the following example the customer table ZZ_EQUI contains additional Equipment Data. The customer table refers to the standard table EQUI, the relation is created via the field EQUNR. In this example it is assumed that the "last change date" is in the CHA_DATE field of the customer table ZZ_EQUI.
Table Assignment - /ISDFPS/CT_TABLE:
| Master Data Table | Customer Table | Object Cus. D | Field - Change Date | |
|---|---|---|---|---|
| EQUI | ZZ_EQUI | /ISDFPS/ET | CHA_DATE |
Field Assignment - /ISDFPS/CT_FIELD:
| Master Data Table | Field - Master Data Table | Customer Table | Field - Customer Table |
|---|---|---|---|
| EQUI | EQUNR | ZZ_EQUI | EQUNR |
| Determination of the Changed On (= last change of the data record) Date of the Customer Table: |
For a standard data object, the decision whether a single data record has already been distributed or if it still needs to be distributed is based on the Changed on date field (e.g. equipment) of the data record which is checked against the replication table.
To extend this logic to the customer tables, the customer tables would by default be distributed based on the "Changed on" date of the corresponding standard logic.
This function is extended by two additional options to replace the standard logic so the last "Changed on" date which is necessary to decide if the data will be distributed or not can be determined.
Option 1:
In Field - Change Date (DATE_FIELD) you can enter the field name of the customer table (field "CC_TABNAME") into the mapping table Table Assignment(/ISDFPS/CT_TABLE). This field contains the last modification date of the data record in the customer table. In the customer table, you must fill the field with a date and determine the data type DATS (length 8). If Field - Change Date is not filled in the mapping table, this function will not be executed.
Example 1:
Equipment with number 1234567 was changed on 01.01.2017, the field CHA_DATE in table ZZ_EQUI received the date 01.01.2017 from customer table.
| Deployed on | Status | Date in Replication Table after Deployment | Add. Information |
|---|---|---|---|
| 01.01.2017 | Deployed | 01.01.2017 | Change date determined from master data |
| 02.01.2017 | Not Deployed | 01.01.2017 | Date not changed |
Example 2:
Equipment with number 1234567 was changed on 01.01.2017, the field CHA_DATE in table ZZ_EQUI received the date 02.01.2017 from customer table.
| Deployed on | Status | Date in Replication Table after Deployment | Add. Information |
|---|---|---|---|
| 01.01.2017 | Deployed | 01.01.2017 | Change date determined from master data |
| 02.01.2017 | Deployed | 02.01.2017 | Change date determined from customer table |
Example 3:
Equipment with number 1234567 was changed on 02.01.2017, the field CHA_DATE in table ZZ_EQUI received the date 01.01.2017 from customer table.
| Deployed on | Status | Date in Replication Table after Deployment | Add. Information |
|---|---|---|---|
| 01.01.2017 | Deployed | 01.01.2017 | Change date determined from customer table |
| 02.01.2017 | Deployed | 02.01.2017 | Change date determined from master data |
Option 2:
If you want to determine your change date from a different location than Customer Table or Master Data, you can use BAdI ISDFPS/CHANGE_LAST_CHANGED.
For further information see BAdI /ISDFPS/CHANGE_LAST_CHANGED
Remark: Make sure not to use or determine a date like 31.12.9999 in the CHA_DATE field. If an undefined date like this is copied into the replication table, the distribution of the corresponding object will never be triggered again!
BAL Application Log Documentation CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 7401 Date: 20240420 Time: 054739 sap01-206 ( 80 ms )
