Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
CN (Package) R/3 Application development: PS Basic data
Basic Data
| Data Element | PS_FLGSD |
| Short Description | Indicator: New structure for each sales order item |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | SD/PS ass. |
| Medium | 15 | SD/PS assignmnt |
| Long | 20 | SD/PS assignmnt |
| Heading | 15 | SD/PS assignmnt |
Documentation
Definition
Specifies that when an operative work breakdown structure is generated from a sales document in assembly processing, one structure is created per sales document item.
If this indicator is not set, the system creates one WBS for the whole sales document.
Dependencies
If you set the SD/PS Assignment indicator, you must use a suitable project edit screen for the standard work breakdown structure. The screen is suitable if it contains at least two sections.
An edit screen is a prerequisite so that the numbers of the generated WBS elements can be uniquely generated from the sales document number (first section of the edit screen) and the sales document item (second section of the edit screen).
We recommend that the first section have the length of 10, and the second section have the length of 6 (as is the case with number and item in the sales document).
History
| Last changed by/on | SAP | 20010427 |
| SAP Release Created in |
