SAP ABAP Message Class OM Message Number 176 (Further posting constellations - accounts display via F6)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       MB0C (Package) Customizing R/3 inventory management
Attribute
Message class OM  
Short Description Customizing: Materials Management    
Message Number 176  
Documentation status      
Authorization check Error Message      
Changed On    
Message Text
Further posting constellations - accounts display via F6
Help Document

Diagnosis

The posting string for the value posting in the accounting system cannot be uniquely determined for the given simulation scenario.

In the case of simulations based on a material number, the posting string obtained is unique. On the other hand, simulations based on a valuation class may not be unique. Because quantity and value update indicators (stored in table T134W, quantity/value control at plant/material type level) cannot be uniquely determined via the valuation class, the relevant T156 entry (movement type quantity/value posting) cannot be fully qualified.

If, despite partial qualification, only one T156S entry with a value string is found, the simulation result is also unique. Uniqueness is also given in the case of several T156S entries if these contain the same value string and no account grouping codes are defined in table T156X (transaction keys, modification) for the simulation scenario with its various combinations of quantity and value update indicators.

Otherwise, the account assignments are displayable for every posting constellation. For each constellation, the posting string for the posting in the accounting system and the quantity and value update indicators (distinguishing the various constellations) are displayed.

MvT VUp QUp SpStI MvtIn RecIn CnsIn VString
--- --- --- ----- ----- ----- ----- -------
102 B V WE06
102 X B V WE06
102 X X B V WE01

In the foregoing example, the partially qualified accessing of table T156S (without quantity and value update indicators) provides three entries with two different value strings, WE06 and WE01.

Several posting constellations are also given if only one value string - perhaps WE06 - results, but account grouping codes (VBR, VQP etc.) are defined in table T156X for the scenario, with its different combinations of quantity and value update indicators. These account grouping codes can likewise lead to different account assignments for individual posting lines.

System Response

Procedure

History
Last changed on/by 20110908  SAP 
SAP Release Created in