SNP Planning area extraction with 0 data records,navigational attributes

[Former Member]

Hi All,

We have an issue while extracting data from the SNP planning area for the data source 9AMALO.The planning area is built on the standard SNP MPOS 9ASNPBAS where we have planning objects like APO LOCATION,APO ACTIVITY and APO PRODUCT and each have their own navigational attributes.

When we created a datasource on the planning area during extraction its not pulling data i.e getting a pop up 0 data records extracted.

My questions here are

1.Does SNP MPOS supports navigational attributes.If not how to remove these navigational attributes from the active MPOS without loosing the existing data.If business need these navigational attributes to exist than what will be the alternate option.

2.Are there any alternative methods to extract the data from the planning area without hiding the navigational attributes in the datasource,because all the navigational attributes are built on APO LOCATION and APO PRODUCT.

3.Are there any suggestions to extract data from existing planning area,or have to build a new planning area or remove the nav attributes on this connected MPOS.

Your valuable inputs are appreciated.

Best Regards,

Dhanunjay.

[Former Member · Accepted solution]

Hi Dhanunjay,

For SNP planning area extraction refr to the note: 428147

This note states:

Symptom

For the extraction of data from a Supply Network Planning (SNP) planning area, you must take some special features into account. This are explained in this consulting note.

Solution

1. Data can be extracted only for existing SNP aggregates.

Existing SNP aggregates are:

9AAC (9AACTNAME)

9AACPR (9AACTNAME, 9APPMNAME)

9ALA (9ATRNAME)

9ALO (9ALOCNO)

9ALORE (9ALOCNO, 9ARNAME)

9AMA (9AMATNR)

9AMALA (9AMATNR, 9ATRNAME)

9AMALARE (9AMATNR, 9ARNAME, 9ATRNAME)

9AMALO (9ALOCNO, 9AMATNR)

9AMALORE (9ALOCNO, 9AMATNR, 9ARNAME)

9AMAPR (9AMATNR, 9APPMNAME)

9AMARE (9AMATNR, 9ARNAME)

9APR (9APPMNAME)

9ARE (9ARNAME)

9AREPR (9APPMNAME, 9ARNAME)

In the SNP planning areas, only export DataSources can be generated for the SNP aggregates and no longer for the master planning object structure 9ASNPBAS.

Only the characteristics or characteristics combination contained in these aggregates can be used in the InfoSource, transfer structure and transfer rules.

Ensure that the navigation attributes 9ATTYPE, 9ALOCTO, and 9ALOCFROM are used for the SNP aggregates 9AMALA (9AMATNR/9ATRNAME) and 9AMALARE (9AMATNR/9ATRNAME/9ARNAME).

Due to technical restrictions, the characteristics 9ATRNAME and 9ATTYPE can be restricted only with single values in the selection for the data extraction. The use of intervals and wildcard characters (+/*) is not allowed for these characteristics.

2. For an SNP aggregate, only the key figures assigned to it can be extracted. You can see which key figures are assigned to an aggregate in transaction /SAPAPO/MSDP_ADMIN on the key figure assignment tab page for the relevant planning area. For the generation of an export DataSource for an SNP aggregate, only the key figures assigned to this aggregate are taken into account.

3. Note the following restrictions for the definition of queries:

For queries for the aggregates 9AMALA and 9AMALARE, certain key figures can be extracted only together with another key figure. This is due to technical reasons. The key figure combinations that can only be extracted together are:

(9AFSHIP, 9ADMDDF, 9ADMDDFVMI)

(9AFSHIPLP, 9ADMDDFLP)

(9AFSHIPVMI, 9ADMDDFVMI)

(9APSHIP, 9ADMDDI, 9ADMDDIVMI)

(9APSHIPLP, 9ADMDDILP)

(9APSHIPVMI, 9ADMDDIVMI)

(9ATSHIP, 9ADMDDT, 9ADMDDTVMI)

(9ATSHIPVMI, 9ADMDDTVMI)

The navigation attributes 9ATTYPE, 9ALOCTO, and 9ALOCFROM must be defined in the InfoSource and the query.

Header Data

Release Status: Released for Customer

Released on: 21.07.2010 09:23:17

Master Language: German

Priority: Correction with medium priority

Category: Consulting

Primary Component: SCM-APO-FCS-EXT Extraction

Secondary Components: SCM-APO-SNP Supply Network Planning (SNP)

Affected Releases

Release-Independent

Related Notes

1045639 - Consulting notes in SNP/CTM

895561 - Reading data for aggregate 9AMALA

837004 - Values from auxiliary key figures are not extracted

657774 - SNP data extraction: Error "Invalid data status"

549184 - FAQ: What is important for extraction

540571 - Collective consulting note on data extraction in DP

453644 - No use of navigation attributes in SNP

441653 - SNP: Data extraction to transportation lanes

373756 - Data extraction from a planning area

Print Selected Notes (PDF)

Regards,

Chetana

Edited by: ChetanaSankhe on Aug 27, 2010 12:03 PM