Hierarchy
BBPCRM (Software Component) BBPCRM⤷
LO-MDS (Application Component) Merchandise Distribution⤷
WFRM (Package) ISR: Cross-Docking and Floor-Ready Merchandise
Basic Data
| Data Element | CPO_SAVE_SELLING_DOC_DATA |
| Short Description | Create Collective PO: Store Issue Document Data Temporarily |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FRM_FLAG | |
| 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 | Save |
| Medium | 15 | Save IssDoc. |
| Long | 29 | Store issue documents tempor. |
| Heading | 12 | Save IssDoc. |
Documentation
Use
By flagging this indicator, issue documents are only store temporarily, thereby reducing the demand on the main memory.
The temporary data is generated at different times:
- When the issue document data is generated
Temporary data is updated using the ABAP command 'EXTRACT'. The data is automatically deleted when this is done by the system.
- When issue document data is aggregated
For technical reasons, it is not possible to update data using an EXTRACT command. The data is therefore written to a cluster table (MDS_TMP). The data is not deleted automatically.
Note
As only some of the temporary data is deleted automatically, you
must run a deletion program at regular intervals. Program R_CPO_DELETE_TEMPORARY_DATA can be run to do this.
Temporary data can normally be deleted immediately after collective purchase orders have been generated.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in | 46C |
