Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
| Data Element | XUSSH_KK |
| Short Description | Use Shadow Table for Business Partner Data |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | BP Table |
| Medium | 15 | BP Shadow Tab. |
| Long | 20 | BP Shadow Table |
| Heading | 15 | BP Shadow Tab. |
Documentation
Definition
Has the effect that for mass runs (for example, in the payment and dunning program), a shadow table for business partner data is used and automatically maintained in business partner maintenance. It contains the most important business partner data.
The use of this table improves the performance for mass runs, but increases the volume of the business partner data by a maximum of 20%.
Procedure
Select the field if you want to manage large business partner datasets.
If the SAP system already contains business partner data, you first have to fill the table using transaction GPSHAD_NEW. For more information, see the Application Help for transaction GPSHAD_NEW.
After you have deactivated the field, make sure that the report RFKKGPSH_DELETE is run. This deletes all existing entries in this table. This prevents obsolete data being read from the shadow table if it is reactivated.
Note
You cannot change business partner data during the mass activity.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
