Hierarchy
⤷ IS-M (Application Component) SAP Media
⤷ JAS (Package) Application development R/3 Publishing Advertising System***
Basic Data
Data Element | JH_MAANW |
Short Description | IS-M: Conflict Control - Situation with Man.Ctrct Assignmts |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | JH_MAANW | |
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 | Appl. |
Medium | 15 | Application |
Long | 20 | Application |
Heading | 4 | Appl |
Documentation
Definition
There are several situations in which the system assigns a level of manual influence to a contract. In each of these situations, you can define (for each conflict control) which level of manual influence is set.
Value range
Assignment that has been created manually
An assignment is created manually. The level of manual influence means that this assignment is retained if contract determination is repeated.
Deleted assignment
A deletion flag is set in an assignment. This is also the case if the assignment is reassigned to a different contract, see below.
Assignment that has been restored
A deletion flag is deselected in an assignment
Assignment that is reassigned
An assignment is created by reassigning a different assignment (a deletion flag is then set in this assignment, see above).
Assignment with conditions that have been changed
Contract conditions are changed in an assignment. The level of manual influence means that you can prevent these conditions being overwritten by conditions in the contract if contract determination is performed again.
Assignment with rate indicators that have been changed
Rate indicators are changed in an assignment. This also occurs if the rate indicators in the assigned contract item are changed.
Assignment selected during a contract conflict
During contract determination, one assignment is selected manually from a number of possible assignments in the case of a conflict situation. If you have chosen a suitable level of manual influence, this assignment is not retained if contract determination is performed again. This means that the same conflict can be resolved differently.
Parallel assignment following manual selection
The remaining assignments in the conflict situation can be created as parallel assignments.
Assignment to a contract for which final settlement has been performed
During subsequent contract determination for services that have been billed, assignments for settlements for which final settlement has been performed can exist that are not therefore to be created again if determination is repeated. The original assignment is therefore retained even if it has a level of manual influence.
Assignment to an inactive contract
As described in the last section, but for inactive contracts (for which final settlement has not been performed).
Assignment during restricted contract determination
If the "Save when assigning" function is used for a contract, the system performs restricted contract determination only, during which assignments are only created for this contract . Assignments are only created here for orders that do not contain any assignment that is granted discount. Original assignments to other contracts that count towards discount are retained if they have a level of manual influence. They are assigned the level of manual influence that is appropriate for this situation unless this is overwritten by an existing level of manual influence.
Assignments in AdMgmtSO.Change or those that are missing in AdMgmtSO.Change
Assignments can be transferred to the AdMgmtSalesOrder.Change and AdMgmtSalesOrder.CreateFromData BAPI. Assignments identified during contract determination are modified as follows during this process:
- Assignments transferred are assigned the level of manual influence for "Assignments in AdMgmtSO.Change" and therefore overwrite any assignments found.
- Assignments identified that have not been transferred to the BAPI are deleted if their level of manual influence is overwritten by a non-initial level of manual influence for assignments that are "missing in AdMgmtSO.Change. (Assignments that are not transferred are therefore assigned the level of manual influence for "assignments that are missing in AdMgmtSO.Change"). If you do not define a level of manual influence for this situation, the 'X' level of manual influence that is then used as a default will result in the deletion of assignments created during contract determination unless they are explicity transferred to the BAPI.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |