SAP table TIBRBRITEMCHGRS (Broker Collections: Change Reasons Broker Report Items)
SAP table TIBRBRITEMCHGRS has 2 primary key fields being MANDT,CHGRS.
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 | |
CHGRS | Change Reason for Broker Report Item | CHAR | 3 | 0 | CHGRS_BRITEM_BRO | ||
XVALID_CHANGE | Change reason is valid for changes | CHAR | 1 | 0 | XCHGRS_CHG_BRO | ||
XVALID_REJECT | Change reason is valid for refusals | CHAR | 1 | 0 | XCHGRS_REJ_BRO | ||
XVALID_NEW | Change reason is valid for new broker report items | CHAR | 1 | 0 | XCHGRS_NEW_BRO | ||
XVALID_WO_MD | Change reason is valid if master data is missing | CHAR | 1 | 0 | XVALID_WO_MD_BRO | ||
XVALID_PREM | Change reason is valid for premium | CHAR | 1 | 0 | X_CHGRS_VALID_PREM_BRO | ||
XVALID_COMM | Change reason is valid for commissions | CHAR | 1 | 0 | X_CHGRS_VALID_COMM_BRO | ||
XVALID_CLAI | Change reason is valid for losses | CHAR | 1 | 0 | X_CHGRS_VALID_CLAI_BRO | ||
XVALID_COST | Change reason is valid for costs | CHAR | 1 | 0 | X_CHGRS_VALID_COST_BRO | ||
XOVRPYMNT | Change reason is valid for overpayment | CHAR | 1 | 0 | X_CHGRS_OVRPYMNT_BRO | ||
XUNDRPYMNT | Change reason is valid for underpayment | CHAR | 1 | 0 | X_CHGRS_UNDRPYMNT_BRO | ||
XEQPYMNT | Change reason is valid for equal amounts | CHAR | 1 | 0 | X_CHGRS_EQPYMNT_BRO |