Hierarchy
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
Basic Data
Data Element | SUBMI |
Short Description | Collective Number |
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 | COLLECT_NO | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Coll. No. |
Medium | 15 | Collective No. |
Long | 20 | Collective Number |
Heading | 10 | Coll. No. |
Documentation
Definition
Number or code facilitating the collective management of a number of individual RFQs (or inquiries) or purchase orders.
Use
If the RFQs or purchase orders of a particular procurement process have been assigned to a collective number, it is then possible to list and process all the individual RFQs/inquiries or POs that are grouped under this number.
Example
You have created 30 RFQs/inquiries for the procurement of a machine and have filed them under the collective number "MA-100". The deadline for submission of bids/quotations having passed, you want to establish the following:
- In respect of which RFQs/inquiries have bids or quotations been received?
- What is the net price of each quotation?
You can obtain this information by listing all individual RFQs/inquiries entered under the collective number "MA-100".
Dependencies
You can also use the collective number within the framework of load building (purchase order optimizing) to logically group together individual purchase orders.
POs bearing a collective number count as optimized.
The processes of seasonal procurement also use the collective number to bundle single-store vendor orders. In this case, the bundled purchase orders are not optimized.
History
Last changed by/on | SAP | 19981111 |
SAP Release Created in |