Standard Concepts: CVC and POS in APO

[Former Member]

Hello All,

please con anybody explain me these standards concepts in APO: CVC and POS, in detail what is the links between these 2 concepts?

my client has given me a brief explanation that CVC is master data of DP, and POS is the principle structure where is based DP and contain the CVC.

is not clear for me these concepts and how should i do to control on the system these informations and the links.

thanks a lot

Bilal

[Former Member · Accepted solution]

Bilal,

Firstly refer to :

http://help.sap.com/saphelp_scm50/helpdata/en/8f/9d6937089c2556e10000009b38f889/frameset.htm

Now, let me try and explain to you briefly.

Consider a table. A table has a certain structure. This structure is defined by its fields. For instance a table for sales orders will have SO Number, Sold to Party, Ship to Party, Reference PO, Delivery Date etc... These fields, constitute the structure. Then there rae records. For the sales order table a record will be

So number=100001

Sold to Party = ABC

Ship to Party = XYZ etc

This is a record.

Now try to draw an analogy with POS. The Master Planning Object structure constitutes a structure. You assign characteristics to an MPOS, which are equivalent to teh fields in the table. For instance the standard DP MPOS 9ADPBAS conatins the follwoing characteristics:

9ABRAND Brand

9ALOCNO APO Location

9ALOCTO APO Destinatn Loc.

9AMATNR APO Product

9AVKORG Sales Organization

This structure is called the MPOS. It defines the lowest level at which data is storeed and planned.

Now draw an analogy of teh table records to the CVC. A characteristic value combination is a record with values assigned to the characteristics of the MPOS. For instance one CVC could be:

9ABRAND PEPSI

9ALOCNO NEW YORK

9ALOCTO PARIS

9AMATNR PEPSI CAN 330 ML

9AVKORG 001

This is ONE CVC. similarl;y for the same MPOS you can have another CVC:

9ABRAND PEPSI

9ALOCNO NEW DELHI

9ALOCTO BANGALORE

9AMATNR PEPSI PET 500 ML

9AVKORG 002

Similarly you can have thousands of CVCs for the same POS.

So, MPOS is nothing but just the structure which defines what are the plannable characteristics. CVCs are records, or values assigned to MPOS characteristics...

MPOS: /sapapo/msdp_admin

CVC: /sapapo/mc62

I have tried to draw an analogy so that you understand better. hope this helps.

I would sugegst you to purchase "Supply Chain Planning in SAP SCM by Jorg Dickersback. Its an awesome book for starters.

Abhi

[Former Member]

HI Friends,

Just wanted to know when i create cvc throgh the process chain some skus are not getting generated why this could be thought the cvc file is correct and upto date ,

Thanks in Advance

Alica

[Former Member]

Hi Bilal,

POS:- Planning object structure comprises of master planning

object structure and aggregates.

MPOS:- Groups together characteristics that can be planned in one or

more planning areas of Demand Planning or Supply Network Planning.

If the master planning object structure is designed for use in Supply

Network Planning, Characteristics-Based Forecasting or Demand Planning

bills of material, it contains standard characteristics. You can not create a

planning area without a master planning object structure

Aggregate:- An APO aggregate contains a subset of the characteristics

in the master planning object structure. The creation and use of aggregates

is optional. The data is always saved on the lowest level of detail. If aggregates

exist, the system saves the planning data on the defined aggregate levels

as well as on the lowest level of detail. The data is saved twice, but consistently;

that is, the sum of the details equals the aggregate value.

CVC:- A characteristic value combination is the combination of characteristic

values with which you want to plan. It is sometimes referred to as a characteristic

combination. You can only plan data if you have defined such a combination.

Characteristic value combinations are planned for MPOS. The combinations are then

valid for all planning areas based on this planning object structure.

Regards

R. Senthil Mareeswaran.