SAP table EBAB (Settlement Runs Subsequent Settlement, Header Data)
SAP table EBAB has 3 primary key fields being MANDT,ABRLF,KNUMA.
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 | * | MANDT | |||||||||||||||||||
ABRLF | Number of a settlement run (subsequent settlement) | CHAR | 10 | 0 | ABRLF | ||||||||||||||||||||
KNUMA | Agreement (various conditions grouped together) | CHAR | 10 | 0 | * | KNUMA | |||||||||||||||||||
ERZET | Entry time | TIMS | 6 | 0 | ERZET | ||||||||||||||||||||
ERDAT | Date on which the record was created | DATS | 8 | 0 | ERDAT | ||||||||||||||||||||
ERNAM | Name of Person Responsible for Creating the Object | CHAR | 12 | 0 | ERNAM | ||||||||||||||||||||
ABRDATE | Settlement date for rebate arrangements (Purchasing) | DATS | 8 | 0 | ABRDATE | ||||||||||||||||||||
BUDATE | Subseq. settlement: Billing/posting date, settlement docs | DATS | 8 | 0 | ABRBUDAT | ||||||||||||||||||||
ATYPE | Type of sett. re condition rec.: reb. arrangements (Purch.) | CHAR | 1 | 0 | ATYPE |
|
|||||||||||||||||||
UMSVT | Type of business volume distribution across plants involved | CHAR | 1 | 0 | UMSVT_C |
|
|||||||||||||||||||
S_ABRLF | Number of cancelled settlement run (subsequent settlement) | CHAR | 10 | 0 | S_ABRLF | ||||||||||||||||||||
BLDATE | Subsequent Settlement: Doc. Date (Supplier Billing Doc Only) | DATS | 8 | 0 | ABRBLDAT | ||||||||||||||||||||
WAERS | Rebate arangement currency | CUKY | 5 | 0 | * | ABSPW_ABR |