SAP table CVALID (Settlement profile for automatic ERS)
SAP table CVALID has 3 primary key fields being MANDT,EKORG,VALID_PRO.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |||||||||
EKORG | Purchasing organization | CHAR | 4 | 0 | T024E | EKORG | |||||||||
VALID_PRO | Settlement profile for automatic evaluated receipt settlemnt | CHAR | 4 | 0 | VALID_PRO | ||||||||||
REF_POST | Base date: posting date | CHAR | 1 | 0 | REF_POST | ||||||||||
REF_DELI | Base date: delivery note date | CHAR | 1 | 0 | REF_DELI | ||||||||||
P1DHI | Settlement profile: period delimitation | NUMC | 2 | 0 | PXDHI |
|
|||||||||
P1DAY | Payment Due Profile: Payment Due Date | NUMC | 2 | 0 | PXDAY | ||||||||||
P1MON | Payment due profile: month | CHAR | 1 | 0 | PXMON |
|
|||||||||
P2DHI | Settlement profile: period delimitation | NUMC | 2 | 0 | PXDHI |
|
|||||||||
P2DAY | Payment Due Profile: Payment Due Date | NUMC | 2 | 0 | PXDAY | ||||||||||
P2MON | Payment due profile: month | CHAR | 1 | 0 | PXMON |
|
|||||||||
P3DHI | Settlement profile: period delimitation | NUMC | 2 | 0 | PXDHI |
|
|||||||||
P3DAY | Payment Due Profile: Payment Due Date | NUMC | 2 | 0 | PXDAY | ||||||||||
P3MON | Payment due profile: month | CHAR | 1 | 0 | PXMON |
|
|||||||||
ERS_ZTERM | ERS terms of payment key | CHAR | 4 | 0 | ERS_ZTERM | ||||||||||
ERSBA | ERS procedure: type of document selection | CHAR | 2 | 0 | ERS_ERSBA |
CVALID foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 CVALID | EKORG | T024E | Purchasing Organizations | EKORG |
1 CVALID | MANDT | T000 | Clients | MANDT |