Where Used List (Table) for SAP ABAP Data Element KAPAR (Capacity category)
SAP ABAP Data Element
KAPAR (Capacity category) is used by
| # | Object Type | Object Name | Object Description | Package | Structure Package | Software Component |
|---|---|---|---|---|---|---|
| 1 | /KYK/CM38_OUTPUT - KAPAR | Output Structure for Capacity Planning | ||||
| 2 | /SAPCEM/SALV4 - /SAPCEM/KAPAR | Structure for ABAP List Viewer - Confirmed Requirements | ||||
| 3 | ACTIVITY_CONF_KEY - CAP_TYPE | Confirmation Key for Activity | ||||
| 4 | ALM_ME_CONFIRMATION_DOC - CAP_TYPE | Time confirmation | ||||
| 5 | ALM_ME_CONF_DETAILS - CAP_TYPE | Confirmation for Confirmation Number and -Counter (2.5) | ||||
| 6 | BAPICONFCO - CAP_TYPE | BAPI confirmation: Confirmations | ||||
| 7 | BAPICONFER - CAP_TYPE | BAPI confirmation: Error | ||||
| 8 | BAPI_CONF_KEY - CAP_TYPE | BAPI structure key for confirmation | ||||
| 9 | BAPI_NETWORK_CONF_GETLIST - CAP_TYPE | BAPI Structure for Confirmation: GetList | ||||
| 10 | CAPSHIFT - KAPAR | Shift Information for the Capacity | ||||
| 11 | CATSCOMP2 - KAPAR | CATS: Comparison Structure for Worklist | ||||
| 12 | CC1ERP - KAPAR | Incorrect Time Events from CC1, Postings | ||||
| 13 | CLOIKAKOU - KAPAR | KAKO Information for Update via Interface (LOI) | ||||
| 14 | CLOIKAPAU - KAPAR | Available Capacity Update via Interface (LOI) | ||||
| 15 | CLOIKAZYD - KAPAR | Delete Capacity Interval via Interface (LOI) | ||||
| 16 | CLOIKAZYI - KAPAR | Capacity Interval Generation via Interface (LOI) | ||||
| 17 | COMES_EQUI_CAPA_ALLOCATION - KAPAR | Assignment Between Individual Capacities and Equipment | ||||
| 18 | CONFCO - CAP_TYPE | Transfer structure for confirmations with work | ||||
| 19 | CONFER - CAP_TYPE | Transfer structure for errors from confirmation | ||||
| 20 | DTINFO - KAPAR | Downtime Entered | ||||
| 21 | EVHR - KAPAR | HR Order Confirmations (Times/Time Events) | ||||
| 22 | IBIPCONF - KAPAR | IBIP: Completion confirmation | ||||
| 23 | IBIP_CONF_CREATE - CAP_TYPE | IBIP: Create Confirmations | ||||
| 24 | KAZA - KAPAR | General structure for KAZY and KAPA | ||||
| 25 | LSHR - KAPAR | HR Order Confirmations (Durations/Time Tickets) | ||||
| 26 | MAM_25_CONFIRMATION_DETAILS - CAP_TYPE | Confirmation Details | ||||
| 27 | MAM_25_CONF_DETAILS - CAP_TYPE | Confirmation for Confirmation Number and -Counter (2.5) | ||||
| 28 | MAM_30_CONFIRMATION_DETAILS - CAP_TYPE | Confirmation Details | ||||
| 29 | MAM_30_CONF_DETAILS - CAP_TYPE | Confirmation for Confirmation Number and Counter (2.5) | ||||
| 30 | MSAM10_ORDER_TIMECONF - CAP_TYPE | Confirmation for Confirmation Number and Counter (2.5) | ||||
| 31 | PDA01 - KAPAR | Internal struct. for PP pair formation/determ. of act. times | ||||
| 32 | PDC31 - KAPAR | Account Assignment of PDC Time Ticket | ||||
| 33 | PDC54 - KAPAR | Daily Status Administration | ||||
| 34 | PLL80 - KAPAR | Integration with Logistics: Confirmations | ||||
| 35 | PLL81 - KAPAR | Integration with Logistics: Confirmations with PDSNR | ||||
| 36 | PMWCCP_BW - KAPAR | Capacity and Usage for Work Center | ||||
| 37 | PTCOR_LOGISTIC_DATA - KAPAR | Logistics Integration (Correction Scenario) | ||||
| 38 | PTCOR_LOGISTIC_STRUC - KAPAR | Logistics Orders (Correction Scenario) | ||||
| 39 | PTCOR_TEVDATA_STRUC - KAPAR | Time Events: CORE, APL, KOSTL,... (Correction Scenario) | ||||
| 40 | PTCOR_UIA_DREQ - KAPAR | Summary | ||||
| 41 | PTCOR_UIA_ITEM - KAPAR | UIA Item (Correction Scenario) | ||||
| 42 | PTCOR_UIA_ITEM_FIELDS - KAPAR | UIA Items Fields (Correction Scenario) | ||||
| 43 | RANGE_S_KAPAR - LOW | Line for Range Table for Data Element KAPAR | ||||
| 44 | RANGE_S_KAPAR - HIGH | Line for Range Table for Data Element KAPAR | ||||
| 45 | RMAN_PRPL_WC_PERIOD_HEADER - KAPAR | Header Structure for Work Center/Period Evaluation | ||||
| 46 | TEVEN_MORE - KAPAR | Additional Data for Time Events | ||||
| 47 | TIME_DATA_TEVENT - KAPAR | Time Events Fields | ||||
| 48 | TIME_DATA_TEVENT_DIS - KAPAR | Display Time Events Fields | ||||
| 49 | TPTCOR_LOGISTIC - KAPAR | Logistics Orders (Correction Scenario) |