Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
BBP_APPLICATION (Package) Structure Package EBP⤷
ME (Package) Application development R/3 Purchasing
Basic Data
| Data Element | OBJLG |
| Short Description | Generate separate message per release |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | Rel. mess. |
| Medium | 15 | Message/release |
| Long | 20 | Message per release |
| Heading | 0 |
Documentation
Definition
Control that outputs a separate message for a scheduling agreement item during release creation for each release that was created.
Use
This indicator dictates how many messages are generated for each release type when a scheduling agreement release is created:
- One message per scheduling agreement item/release
If you select this indicator, the system creates a separate message for each scheduling agreement item for each release. In other words, several messages could be generated per scheduling agreement. - One message per scheduling agreement/release (type)
If you do not select this indicator, the system only creates one message for all releases of a scheduling agreement, even if releases were created for several scheduling agreement items.
Procedure
Examples
Scheduling agreement 5500000012 contains 2 items.
During release creation for the scheduling agreement, the following releases were created because the next transmission date was reached:
Item Material During release creation
010 Bolt 01 Created in release number 12
is created in scheduling agreement number 4
020 Bolt 02 Created in release number 5
Result
If this indicator is selected, two separate messages are created for the JIT delivery schedule number 12 and the forecast delivery schedule number 4 for the item 10 and the JIT delivery schedule number 5 for the item 20. In other words, three messages are generated for this scheduling agreement.
If the indicator was not selected, exactly one message is created for both releases. In other words, only one message is created for the entire scheduling agreement.
Dependencies
History
| Last changed by/on | SAP | 19980617 |
| SAP Release Created in |
