cancel
Showing results for 
Search instead for 
Did you mean: 

PIR in inactive version in ECC

Private_Member_738444
Participant
0 Kudos

Hello,

Release of Demand from APO to ECC via infocube

We have a scenario, for long term biz planning, one of the FCST keyfigure values for future one year, in weekly periods, are first loaded into an APO-BW infocube (first load into PSA, then into Infocube) and then released to ECC from APO using /sapapo/rel_to_oltp

This is done from the spare version of APO to spare version in infocube into inactive version of ECC.

The PIR could be seen in ECC after some time by using the t-code MD63

Q.1 Is there anyways to generate the PIR's for multiple products, period wise, in pare version in ECC? MD63 is product specific and checking the PIR per product/plant/version is a painful repetitive work through MD63. Is there any way to see this through collective mode? (screenshot #1 below)

Q.2 The release from Infocube to ECC doesn't has any mention of the ECC system, how does this program (/sapapo/rel_to_oltp) gets to identify which ECC system and which Category Type needs to be updated in ECC? (screenshot #2 below)

Screenshot#1

Screeshot#2

Please let me know.

Rgds.

NK

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

NK,

Q.1 Is there anyways to generate the PIR's for multiple products, period wise, in pare version in ECC? 

I don't know what you mean by 'spare version'.  ECC PIRs can exist in multiple versions, but only a maximum of 1 version can be 'active' at a time.  The 'active' version is the version whose data is integrated to MRP and other ECC planning functions.

In ECC, there are several ways to create PIRs.  You have already discovered one (release from APO).  Some other ways are:

1. Manually

2. Copy the ECC Material Forecast

3. Copy the results of ECC Sales and Operations Planning

4. Copying from an existing plan

5. Copying from another material, or copying from another version.

MD63 is product specific and checking the PIR per product/plant/version is a painful repetitive work through MD63.

No, MD63 is not product specific.  You can display a single Material, yes, but you can also display a Product Group, and you can display an entire Requirements Plan.  The two final options typically contain multiple Materials.


Q.2 The release from Infocube to ECC doesn't has any mention of the ECC system, how does this program (/sapapo/rel_to_oltp) gets to identify which ECC system

You are copying from the BW system in APO to an ECC system.  The BW system in APO is connected to ONLY one OLTP source system for the purpose of forecast release, regardless of the number of other ECC systems you may choose to connect to APO for other purposes.  This connection is set in SCM configuration.  In SCM standard, using this transaction, you may only release a forecast from a BW Infoprovider to ONE OLTP system.


...and which Category Type needs to be updated in ECC? (screenshot #2 below)

??? There is no 'Category Type' in ECC.  You are copying data from a BW KeyFigure to an ECC PIR with a specific Requirements Type.  There are rules by which the default requirement type is created (ECC Planning Strategy and ECC MRP Group have influence).  However, you can override the default directly in the /SAPAPO/REL_TO_OLTP screen ("Data Target Show Extended Settings").

In closing, I think you need to first familiarize yourself with the standard basic functionalities in this area; stumbling about via trial and error is laborious and time consuming.  SCN is not a suitable forum for basic functional training.  I suggest you speak to a local expert who has done this before. Or, take some basic classes.  Or, try reading standard SAP help.  Here are a couple of interesting docs

from SAP help

In SCM

Release of Forecast Data - SAP Library

In ECC

Planned Independent Requirements (PIRs) - Demand Management (PP-MP-DEM) - SAP Library

Of course, you should also search SCN, which has quite a bit about this subject.

Best Regards,

DB49

Answers (1)

Answers (1)

rupesh_brahmankar3
Active Contributor
0 Kudos

Hello,

Expert DB49 already answered this question.

Target version can be maintain in  /n/sapapo/rel_to_oltp or target version can be set in transfer profile /n/sapapo/mc8u or /n/SAPAPO/DMP2 . If you select here Version as Active tick then forecast  will be transfer in ECC as PIR in active version.


Best Regards,

R.Brahmankar