Hierarchy
⤷ IS-M (Application Component) SAP Media
⤷ JAS (Package) Application development R/3 Publishing Advertising System***
Basic Data
Data Element | JH_BDJPOPER_SEQ |
Short Description | IS-M: Sequence Number of Posting Period for Revenue Object |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC03 | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | SqNoPoPerd |
Medium | 15 | SqNo PoPer/RO |
Long | 20 | Seq.no.po.per/rev.ob |
Heading | 8 | Sq.no.PP |
Documentation
Definition
Sequence number that is transferred to pricing as KOMP-BDJPOPER_SEQ for revenue object valuation.
Use
When a revenue object document is valued, several items that are only distinguished by the posting period can exist for the same revenue object. The system assigns a sequence number to items in ascending order according to the posting period so that the value for revenue distribution can be distributed amongst these items.
The KOMP-BDJPOPER_MAX field contains the highest number assigned here.
Example
You sell a date combination in booking unit B that generates one schedule line on Wednesday and another on the following Saturday. If these publication dates are found in different posting periods, revenues should be divided using a ratio of 60:40. You should record the following condition records to do so:
Booking unit KOMP-BDJPOPER_SEQ KOMP-BDJPOPER_MAX Amount
B 1 1 100 %
B 1 2 60 %
B 2 2 40 %
Further notes
During determination of revenue objects (i.e. before their valuation), the system sets KOMP-BDJPOPER_SEQ and KOMP-BDJPOPER_MAX to 1. This means the condition record for 100% can be used as a revenue object simultaneously.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 462 |