Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | KALC_PRODPER |
Short Description | Allocation: Derive Production Month |
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 | Prod.Month |
Medium | 18 | Production Month |
Long | 25 | Derive Production Month |
Heading | 25 | Derive Production Month |
Documentation
Definition
You use Production Month (date) to report costs in the production month rather than in the posting period. If you activate Production Month functionality, the production month can be entered in the production date field. If no date is entered, the document date is used as the production date by default.
The production date can be entered in FI documents only. CO always takes the document date (except in the allocation process). MM transactions take the document field, except in the MM invoice process (MIRO), where it takes the highest production date of all goods receipts.
You can set the status of the production date field in the field status maintenance; it is located in JVA Partner.
All subsequent JVA processes (for example, Cutback, Suspense, Overhead) are processed before the original production date.
Use
Production Month is available in assessment and distribution cycles.
Derive Production Month in the cycle header definition enables the production month of the receiver to be derived.
If the indicator is set, the production month is available as selection criteria for the senders and the production month from the sender is passed on to the receiver. If the indicator is not set, the information on the production month is cleared in the resulting cycle posting for sender and receiver.
After the allocation process, you can to perform follow-on actions like billing using the receivers' production month.
Dependencies
Example
History
Last changed by/on | SAP | 20110901 |
SAP Release Created in | 606 |