Data flow between R/3 AND APO

[Former Member]

How the chars and Navigational attributes are flowing in-between the R/3 AND APO ?

Why we need to maintain the chars and nav attrr in APO? . Any input will be highly appreciated

Thanks

[Former Member]

Data flow between R/3 and APO is mainly for SNP and/or PPDS. The planning object structure used in SNP/PPDS regular planning is a Std SAP defined 9ASNPBAS. Characterstics used in the POS like Product,Location, PPM, Resource are the masterdata CIFd from R/3 which are used for APO planning. Navigational attributes used here are the Transportation start location and Target location which are used for generating TLB orders

[Former Member]

Hello Nick,

Navigational Attributes : Characteristic attributes can be converted into navigation attributes. They can be selected in the query in exactly the same way as the characteristics for an InfoCube. In simple words an attribute is a characteristic that is logically assigned and subordinated to another characteristic. Navigational attributes offer a way to plan multiple objects while achieving optimum system performance in Demand Planning.

e.g. Costs of the cost center drilled down by person responsible: You use the attribute u2018Cost Center Manageru2019 for the characteristic u2018Cost Centeru2019. If you want to navigate in the query using the cost center manager, you have to create the attribute u2018Cost Center Manageru2019 as a navigation attribute, and flag it as a navigation characteristic in the InfoCube.

Characteristics : A planning object such as a product, location, brand or region.

The master data of Demand Planning or Supply Network Planning encompasses the permitted values of the characteristics, the characteristic values. Characteristic values are discrete names or numbers . For example, the characteristic 'location' could have the values London, Delhi and New York.

Regards

Rahul Chitte

Edited by: Rahul Chitte on Aug 30, 2010 5:07 PM