SAP ABAP Data Element EBELD (PO number in local system)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
Basic Data
Data Element | EBELD |
Short Description | PO number in local system |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR10 | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
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 | PO no. |
Medium | 15 | PO no. (local) |
Long | 20 | PO no. (local) |
Heading | 10 | PO no. |
Documentation
Definition
Number of purchase order in local system.
Use
If your company is using distributed contracts, release orders are created in various local SAP systems against a centrally agreed contract. The PO number is assigned by the relevant local system. As a result, it is possible for a release order issued in plant 1 to have the same number as one issued in plant 3, for example.
As the PO numbers in the central system must be unique, new numbers are assigned. The previous PO numbers assigned by the local system are stored as additional information in the release order documentation of the central system.
History
Last changed by/on | SAP | 19980218 |
SAP Release Created in |