Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD03 (Package) Appl. development R/3 MPS/determin. requirements planning
Basic Data
Data Element | MD_LAST_ORD |
Short Description | BAPI: Indicator - Last Planned Order for Collective Update |
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 | IndLastOrd |
Medium | 15 | Ind. Last Order |
Long | 20 | Ind. Last Order |
Heading | 0 |
Documentation
Definition
Indicator: Last planned order during collective update of planning file entries for planned orders via BAPIs.
Use
During mass processing of planned orders, you can collectively update planning file entries. You activate collective processing by setting HEADERDATA-USE_COLL_UPD. You must, however, ensure that the indicator HEADERDATA-LAST_ORDER is set when one of the BAPI methods CREATE or CHANGE is called for the last time. This ensures that the system transfers all of the planning file entries collected up to that point to the database.
Dependencies
Example
BAPI method CREATE (function module BAPI_PLANNEDORDER_CREATE) is called in the form of a loop to create several planned orders. Generally, the parameter HEADERDATA-USE_COLL_UPD must be set here. The parameter HEADERDATA-LAST_ORDER is only set for the last loop pass, triggering the update of all of the planning file entries collected up to that point.
History
Last changed by/on | SAP | 20020124 |
SAP Release Created in | 470 |