SAP ABAP Data Element PPC_SYNC_POSTED (Status of Synchronous Material Posting)
Hierarchy
☛
ECC-DIMP (Software Component) DIMP
⤷ IS-A-PPC (Application Component) Production Backflush
⤷ PPC1 (Package) Backflushing in PP
⤷ IS-A-PPC (Application Component) Production Backflush
⤷ PPC1 (Package) Backflushing in PP
Basic Data
Data Element | PPC_SYNC_POSTED |
Short Description | Status of Synchronous Material Posting |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PPC_PROCESS_STATUS | |
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 | Synch.Mats |
Medium | 20 | Synchronous Material |
Long | 35 | Synchronous Materials Posted |
Heading | 35 | Synchronous Materials Posted |
Documentation
Definition
Each backflush consists of three subprocesses:
- timely ("synchronous") posting of material movements
- deferred, aggregated ("asynchronous") posting of material movements
- deferred, aggregated ("asynchronous") posting of production activities
The system posts the synchronous process immediately after the receipt of the backflush and the process includes the posting of the goods receipt and the components that are indicated as synchronous in the external system.
The indicator has three characteristic values:
- blank: the synchronous process must still be posted
- V: the backflush had no synchronous material movements to be posted
- X: the material movements have been posted.
Normally, the indicator for synchronous posting should always be set (V or X). If it is blank for some backflushes, start the transaction Processing the Backflushes with the option Post Synchronous Processes. If the indicator is still not set, look in the application log (object PPCONF) to find out where the error occurs.
History
Last changed by/on | SAP | 20050301 |
SAP Release Created in |