SAP ABAP Data Element BPROC (ATP: Business Transaction for RBA)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BF (Application Component) Basic Functions
⤷
ATPI (Package) From APO Interfaces bapi_apotp_check
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
ATPI (Package) From APO Interfaces bapi_apotp_check
Basic Data
| Data Element | BPROC |
| Short Description | ATP: Business Transaction for RBA |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BPROC | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | TVBPROC |
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 | Processing |
| Medium | 15 | Processing |
| Long | 20 | Business transaction |
| Heading | 2 | BT |
Documentation
Definition
This entry makes it possible to use the availability check settings in the APO planning system for this order type.
Use
Using the business transaction, you can control in which business contexts a rule-based availability check is carried out. A rule-based availability check is therfore, as a rule, not sensible for a rush order.
When called from the ERP system, this value is created using the order type for the sales order from which calling takes place.
History
| Last changed by/on | SAP | 20000127 |
| SAP Release Created in |
