Release to SNP from DP BOM

Hello everybody,
I need a help of you.
I'm trying to do a release of a key figure in area of a DP-BOM.
I enter the transaction / SAPAPO/MC90 and release runs successfully, however, when I access the transaction / SAPAPO/RRP3 the orders are not created.
Is there any peculiarity in making a release from an area DP-BOM?
Thanks

Hi Geovana Juliani ,
Can u check whether materials/components you have use are create in APO as location-product master data and already assigned to model 000?
Check  the date also.
Thanks,
Nikhil

Similar Messages

  • Release Of Forecast From DP To SNP (For Some Locations, Only Baseline)

    Dear All,
    Generally, we follow the following procedure....In the month begining, we generate the baseline forecast for all the locations (we are having around 20 branches). Then we used to open the DP planning book for a couple of days to our branch persons so that they are able to feed their correction. After which we release the final forecast i.e. Baseline Forecast +/- Branch correction to SNP for further proceesing.
    This month, we opened the planning book (as usual). Branches did  the branch correction. But on final checking, we found that around 4 -  5 branches have done corrections / updations very vagely i.e. roughly. So, we wants to ignore their branch correction.
    My query be that is it possible that while releasing the Forecast from DP to SNP... can we release baseline forecast for selective five branches and for the rest of the branches, we wants to release final forecast key figure i.e. Baseline +/- Branch correction.
    Kindly advise further.
    With Best Regards,
    Sanjeev Chugh
    17-NOV-2010 (AN)

    Sanjeev
    You have not mentioned at what level you are doing the forecasting. If forecasting is done at material- branch level then what you are asking can be achieved easily. All you have to do is go to /n/sapapo/mc90 ( or create a release profile) and for the branches for which you want to release baseline forecast , you have to specify the baseline forecast keyfigure in the input and specify the material branches in the i/p criteria. For adjusted forecast you have to use another variant and specify the adjusted forecast key figure and the corresponding material branches.
    Iam not sure how your requirement can be achieved in case you are forecasting @ material level.
    Thanks
    Aparna

  • Release Planned Orders from SNP to R/3

    Hello Experts:
    I have a business request to release the Production Planned KF from SNP into a frozen MPS (or even an inactive fcst version) in R/3.  Since we have only released a forecast from the DP side to R/3 in the past, can anyone tell me the best practice to release from SNP to R/3?  Do I need to create an info cube to perform the release?
    The business runs a Heuristic in SNP at the finished good level and the makes modifications and would like to release this to be used in the R/3 MRP run for some groups of materials, as opposed to releasing the forecast for MRP to run on.
    Currently, I can send the data from SNP Production Planned KF to a time series KF in DP and release to MD63 from there, but they would like to release directly from SNP in the future.
    Any suggestions are greatly appreciated!
    Andrea

    Hi Andrea,
    If you want to release SNP planning data to ECC, you need to make following settings.
    In customizing
    Maintain Distribution definitions
    Maintain Settings in Configure transfer to OLTP system in SNP customizing-Global Settings.
    If you maintain periodic setting in SNP setting, you need to run transaction /SAPAPO/C5 to transfer data.
    As well as u can do this also :
    1) You need to create a release profile using transaction /sapapo/mc8s
    2) In release profile, you need to maintain planning area,  key figure to
    be transformed, plg version, category, etc.,
    3) Once it is created, using transaction /sapapo/mc8t, maintain the
    R/3 transfer steps
    4) Then create a planning job in background using transaction
    /sapapo/mc8d

  • Release to SNP - period split profile doesn't work as expected

    Hi Gurus,
    I have a DP planning area with monthly storage buckets. I want to release to SNP using a period split profile that distributes the forecast equally to weeks. The problem is that the forecast is always completely released to the first working day in the month (and is not distributed as expected). Further information:
    - using SAP SCM 7.0
    - time stream in the storage bucket profile of the DP planning area = shipping calendar in the locations
    - the simulation of the period split profile shows the expected behavior
    Does anyone know what maybe went wrong?
    Best regards,
    Christoph

    Hi Datta,
    thanks for your quick reply. I found out that I entered the wrong from date for the release of forecast to SNP.
    I used the beginning of the planning area time stream and not the current date. Therefore my settings in the split profile had no effect because the split would only have taken place somewhere in the past.
    Best regards,
    Christoph

  • DP forecast not released to SNP - error "Invalid Data Status"

    Hello,
    When DP forecast was released to SNP, one material - Location went into error. The error is "Invalid Data Status"
    Release to DP to SNP  is thru background job, and it check the material status (only material with active status is considered for release).
    But for the above error, the material is active.
    What could be the possible reason for this error & how can it be  resolved.
    Thanks in advance.

    Hi Datta,
    In consistency match, there are multiple objects. Since DP is new to me, I am not aware of the objects that should be selected. Can you tell me which objects should I select for this and what will be the outcome of this.
    Also can you please explain me why do we execute his transaction?
    Thanks in advance.

  • How to create a Blanket Release in iProc from a approved requistion

    Hi Gurus,
    How to create a blanket Release in iProcurement from a approved requisition. I have followed the below steps.
    1. Created a BPA from Front end.
    2. Run Loader Data program.
    3. Above program reflected the BPA in iProc.
    4. Created requisition from BPA.
    5. Requisition has been approved.
    After this i am stuck. How to proceed ahead. I want to create a Blanket Release from approved PR and then receive in iProcurement.
    please help me on this. We are using 11.5.10.2
    Regards,
    john

    911765 wrote:
    Hi Mahendra,
    Thank you so much for your reply.
    So you mean to say that it all depends upon the Sourcing Rule and ASL based upon that system would automatically create a Blanket Release or If its Automatic Release/Review then we have to manually create release through autocreate.
    The reason why i am asking this query is now when i tested it, system is automatically creating release and starngely there is no Sourcing Rule and ASL has been defined.
    But we are looking for a Manual Release through autocreate window.
    It would be great if you could please suggest.
    Regards,
    JohnJohn,
    When you say system is automatically creating release..as far as i know...it should be referencing a PO..correct...in the releases window..
    can you pull that up..and see if you can get any clue..bcz that PO would BPA...
    Also I am not that much into Iproc...I don't know...whether Iproc has some other setups
    HTH
    Mahendra

  • Error while releasing an activity from NWDS

    Hi,
    I am facing the below error while releasing an activity from NWDS - transport view.
    Internal error: the export of SC_CR com.xxx.xxx/xxx_SOFTWARE_COMPONENT#Track_D.118 failed. tcs returncode was 12
    Check in and activate was successfull and in CMS, the activity is shown as activated.
    Please help me to rectify this error.
    Thanks in advance!
    Regards,
    Manchari. N

    Make sure you are connected to NWDI server.
    Also create a new activity for a different component in the same track.
    Below links may be helpful :
    http://wiki.sdn.sap.com/wiki/display/TechTSG/(NWDI)(CMS)PropagationRequestReleaseinTransportViewFails
    NWDI/CBS - release activity in consolidation
    Re: Error on Release of activity (Version set not found!)
    Regards
    Deepak

  • Error while Releasing the Stock from Quality-CRTD CHCR SPRQ

    Hai Experts
                          While releasing the stock from Quality i got  error like function cannot be caried out,
    The Material Status CRTD CHCR SPRQ.
    Thanks
    Rajakarthik

    Rajakarthik
    It looks like the status you mentioned are of inspection lot.
    CRTD mean created status of inspection lot.
    CHCR means characterstics required. in your case the the material master inspection view says characterstics required however your inspection plan does not have any cahracterstics.
    assign the characterstics to inspection plan & both the status of inspection lot will change. you will be then able to process the inspection lot to move the stock from quality to unrestricted.
    Regards
    Mahesh

  • Releasing Transport task from  either schedule manager or change request

    Hi Gurus,
    I had a doubt regarding releasing of tasks of a transport request.
    Is there any way where I can release a task along with the transport request in the Correction transaction itself?
    Or is it a standard behavior of SAP Solman process where in I have to login to the Satellite system , do the configuration and then release the task from se10 t-code and then finally release the transports.
    Require ur expertise on this point.
    Regards,
    Anubhav

    Hi Anubhav.
    Manually releasing the task in the satellite system (using SE10)
    prior to releasing the transport request in CHARM is a SAP standard process for CHARM in SOLMAN.
    I think SAP made it this way as a precaution in case there are several task included in the transport request
    (assigned to different developers). Manually releasing your task means that your confirming that
    you have completely applied your modifications and ready for import into the test system.
    If this process is included as an automated process along with the releasing of transport request in CHARM,
    you may mistakenly release another person's task which may not be ready for import yet.
    I hope this helps.
    Regards,
    Tess

  • Release of forecast from DP to R/3

    Hi SCM Gurus,
    I am facing problem related to release of forecast from Demand Planning to R/3. When I check for PIR in R/3 no PIR is there.
    1) the product and location are maintained in APO & R/3.
    2) Location Split is maintained.
    3) MPOS with only Product and Location.
    4) PA with one KF of forecast. Disaggregation based on different KF.
    5) Period for Storage bucket and Planning Mucket in Month.
    6)Created Transfer Profile.
    7) created back ground job.
    8) Maintained Publication.
    Still when i release the job no PIR is created in R/3.
    Am I missing any steps . Gurus. pls help..
    Regards,
    Sanjay

    Hi,
    Can you check the Time bucket profile of the Planning book using which you are releasing the forecast to R/3.
    The Time bucket profile which is used for releasing should have only one periodicity(Eg: Either Months, Weeks, or day).
    Best Regards
    Raghu

  • Problem is releasing excel application from memory using webutil

    Hi Experts,
    This code is working fine but it is not releasing the excel from the memory. if i try the same set of code with Wort.Applicationa or Access.Application it works fine. But only with excel it is not working.
    Is there is any way to kill the excel application?
    application := CLIENT_OLE2.create_obj('Excel.Application');
    CLIENT_OLE2.invoke(application,'Quit');
    CLIENT_OLE2.release_obj(application);
    Thanks & Regards
    Rajesh

    This is probably <Bug:3082119 which is fixed in the production release.
    Regards
    Grant Ronald
    Forms Product Management

  • Is it possible to release the request from production to quality

    is it possible to release the request from production to quality

    It's not allowed..
    You can move request from original server ( where a request is created ) to target server.
    Since in production server you are not allowed development work.. so u can not create req there... and u can not move req of dev server ( which were moved to prod ) from prod to quality.
    Reward if helpful
    Regards
    Pradeep

  • Release the space from Tools tablespace

    Hi,
    I have found that TOOLS tablespace is 99%.
    The tools tablespace is typically used for collecting database statistics – not part of the application. These include Quest and Perfstat. How can I check at the objects in the tools tablespace to see what has grown and then determine if we need to purge data and reorg the objects.
    The mount point for this database is only 8 gig and is 84% used so we should not add “overhead” space unless absolutely necessary. The tools tablespace is already large for the size of the rest of the database.
    /dev/orabwelv 8388608 7011424 1377184 84% /ORACLE/BWEBPRD
    These are the contents in the tablespace
    OWNER TABLE_NAME OBJECT_TYPE TABLESPACE_NAME
    ORACLE PLAN_TABLE TABLE TOOLS
    ORACLE_APP STPL_DBAPRVS_PENDINGL TABLE TOOLS
    ORACLE_APP STPL_DBAPRVS_ACTIVITY_LOGL TABLE TOOLS
    ORACLE T_WEBBPRD TABLE TOOLS
    POSTD PLAN_TABLE TABLE TOOLS
    MONITORER TABLESPACE_GROWTH TABLE TOOLS
    MONITORER SEGMENT_GROWTH TABLE TOOLS
    OWNER TABLE_NAME OBJECT_TYPE TABLESPACE_NAME
    PERFSTAT STATS$PGA_TARGET_ADVICE TABLE TOOLS
    PERFSTAT STATS$SQL_WORKAREA_HISTOGRAM TABLE TOOLS
    PERFSTAT STATS$SHARED_POOL_ADVICE TABLE TOOLS
    PERFSTAT STATS$STATSPACK_PARAMETER TABLE TOOLS
    PERFSTAT STATS$INSTANCE_RECOVERY TABLE TOOLS
    PERFSTAT STATS$PARAMETER TABLE TOOLS
    PERFSTAT STATS$IDLE_EVENT TABLE TOOLS
    PERFSTAT STATS$PGASTAT TABLE TOOLS
    PERFSTAT STATS$SEG_STAT_OBJ TABLE TOOLS
    PERFSTAT STATS$SEG_STAT TABLE TOOLS
    PERFSTAT STATS$SQL_PLAN TABLE TOOLS
    OWNER TABLE_NAME OBJECT_TYPE TABLESPACE_NAME
    PERFSTAT STATS$SQL_PLAN_USAGE TABLE TOOLS
    PERFSTAT STATS$UNDOSTAT TABLE TOOLS
    PERFSTAT STATS$DLM_MISC TABLE TOOLS
    PERFSTAT STATS$RESOURCE_LIMIT TABLE TOOLS
    PERFSTAT STATS$SQL_STATISTICS TABLE TOOLS
    PERFSTAT STATS$SQLTEXT TABLE TOOLS
    PERFSTAT STATS$SQL_SUMMARY TABLE TOOLS
    PERFSTAT STATS$ENQUEUE_STAT TABLE TOOLS
    PERFSTAT STATS$WAITSTAT TABLE TOOLS
    PERFSTAT STATS$BG_EVENT_SUMMARY TABLE TOOLS
    PERFSTAT STATS$SESSION_EVENT TABLE TOOLS
    OWNER TABLE_NAME OBJECT_TYPE TABLESPACE_NAME
    PERFSTAT STATS$SYSTEM_EVENT TABLE TOOLS
    PERFSTAT STATS$SESSTAT TABLE TOOLS
    PERFSTAT STATS$SYSSTAT TABLE TOOLS
    PERFSTAT STATS$SGASTAT TABLE TOOLS
    PERFSTAT STATS$SGA TABLE TOOLS
    PERFSTAT STATS$ROWCACHE_SUMMARY TABLE TOOLS
    PERFSTAT STATS$ROLLSTAT TABLE TOOLS
    PERFSTAT STATS$BUFFER_POOL_STATISTICS TABLE TOOLS
    PERFSTAT STATS$LIBRARYCACHE TABLE TOOLS
    PERFSTAT STATS$LATCH_MISSES_SUMMARY TABLE TOOLS
    PERFSTAT STATS$LATCH_PARENT TABLE TOOLS
    OWNER TABLE_NAME OBJECT_TYPE TABLESPACE_NAME
    PERFSTAT STATS$LATCH_CHILDREN TABLE TOOLS
    PERFSTAT STATS$LATCH TABLE TOOLS
    PERFSTAT STATS$TEMPSTATXS TABLE TOOLS
    PERFSTAT STATS$FILESTATXS TABLE TOOLS
    PERFSTAT STATS$DB_CACHE_ADVICE TABLE TOOLS
    PERFSTAT STATS$SNAPSHOT TABLE TOOLS
    PERFSTAT STATS$LEVEL_DESCRIPTION TABLE TOOLS
    PERFSTAT STATS$DATABASE_INSTANCE TABLE TOOLS
    Please Suggest
    Message was edited by:
    user592074

    Thanks Chandra!
    Request you to kindly suggest me how to release the sapce from tool table. Database version is 9.2.0.6 (64 bi Please find the output below.
    SEGMENT_NAME SIZE_MB
    PLAN_TABLE .125
    SEGMENT_GROWTH 25
    STATS$BG_EVENT_SUMMARY 2
    STATS$BG_EVENT_SUMMARY_PK 2
    STATS$BUFFER_POOL_STATISTICS 1
    STATS$BUFFER_POOL_STATS_PK 1
    STATS$DATABASE_INSTANCE 1
    STATS$DATABASE_INSTANCE_PK 1
    STATS$DB_CACHE_ADVICE 2
    STATS$DB_CACHE_ADVICE_PK 1
    STATS$DLM_MISC 1
    STATS$DLM_MISC_PK 1
    STATS$ENQUEUE_STAT 2
    STATS$ENQUEUE_STAT_PK 2
    STATS$FILESTATXS 3
    STATS$FILESTATXS_PK 3
    STATS$IDLE_EVENT .125
    STATS$IDLE_EVENT_PK .125
    STATS$INSTANCE_RECOVERY 1
    STATS$INSTANCE_RECOVERY_PK 1
    STATS$LATCH 25
    STATS$LATCH_CHILDREN 1
    STATS$LATCH_CHILDREN_PK 1
    STATS$LATCH_MISSES_SUMMARY 1
    STATS$LATCH_MISSES_SUMMARY_PK 1
    STATS$LATCH_PARENT 1
    STATS$LATCH_PARENT_PK 1
    STATS$LATCH_PK 22
    STATS$LEVEL_DESCRIPTION .125
    STATS$LEVEL_DESCRIPTION_PK .125
    STATS$LIBRARYCACHE 1
    STATS$LIBRARYCACHE_PK 1
    STATS$PARAMETER 21
    STATS$PARAMETER_PK 24
    STATS$PGASTAT 1
    STATS$PGA_TARGET_ADVICE 1
    STATS$PGA_TARGET_ADVICE_PK 1
    STATS$RESOURCE_LIMIT 1
    STATS$RESOURCE_LIMIT_PK 1
    STATS$ROLLSTAT 2
    STATS$ROLLSTAT_PK 1
    STATS$ROWCACHE_SUMMARY 3
    STATS$ROWCACHE_SUMMARY_PK 3
    STATS$SEG_STAT 3
    STATS$SEG_STAT_OBJ 1
    STATS$SEG_STAT_OBJ_PK 1
    STATS$SEG_STAT_PK 1
    STATS$SESSION_EVENT 1
    STATS$SESSION_EVENT_PK 1
    STATS$SESSTAT 1
    STATS$SESSTAT_PK 1
    STATS$SGA 1
    STATS$SGASTAT 3
    STATS$SGASTAT_U 5
    STATS$SGA_PK 1
    STATS$SHARED_POOL_ADVICE 1
    STATS$SHARED_POOL_ADVICE_PK 1
    STATS$SNAPSHOT 1
    STATS$SNAPSHOT_PK 1
    STATS$SQLTEXT 5
    STATS$SQLTEXT_PK 1
    STATS$SQL_PGASTAT_PK 1
    STATS$SQL_PLAN 5
    STATS$SQL_PLAN_PK 1
    STATS$SQL_PLAN_USAGE 5
    STATS$SQL_PLAN_USAGE_HV 1
    STATS$SQL_PLAN_USAGE_PK 1
    STATS$SQL_STATISTICS 1
    STATS$SQL_STATISTICS_PK 1
    STATS$SQL_SUMMARY 17
    STATS$SQL_SUMMARY_PK 8
    STATS$SQL_WORKAREA_HISTOGRAM 1
    STATS$SQL_WORKAREA_HIST_PK 1
    STATS$STATSPACK_PARAMETER .125
    STATS$STATSPACK_PARAMETER_PK .125
    STATS$SYSSTAT 21
    STATS$SYSSTAT_PK 25
    STATS$SYSTEM_EVENT 3
    STATS$SYSTEM_EVENT_PK 4
    STATS$TEMPSTATXS 1
    STATS$TEMPSTATXS_PK 1
    STATS$UNDOSTAT 1
    STATS$UNDOSTAT_PK 1
    STATS$WAITSTAT 1
    STATS$WAITSTAT_PK 2
    STPL_DBAPRVS_ACTIVITY_LOG .0625
    STPL_DBAPRVS_PENDING .0625
    STPL_DBAPRVS_PENDING_PK .0625
    TABLESPACE_GROWTH .3125
    T_WEBBPRD .0625
    90 rows selected.
    Message was edited by:
    user592074

  • Issue of Components from Sales BOM where user warehouse is defaulted

    In 2007A, where the warehouse is different at row level for the parent item, the component items do not default to the same as the parent, and no warning message is produced. SAP say this is system behaviour as the components are shown on the form and can be changed in the form. In 2005A an Assembly BOM was used which would generate a warning, but no new Assembly BOM's can be created in 2007A. The warning is now only generated if the warehouse is changed in the table area of the form settings window.
    However, I believe they have not allowed for the use of the user defaults in this case.
    The purpose of the user defaults is to take away from the user the possibility of transacting an incorrect warehouse by accident. In order to control stock properly this is essential from a business process and a "best practice" perspective.
    The user is set to default to the warehouse they have access to, then the form settings are turned off for the warehouse so they cannot issue from other warehouses.
    If this is the case (as it is for all of our customers who have many branches) then they cannot update the child items to issue from their own location, and have no visibility that there is a problem until stock taking time.
    The purpose of a sales BOM is to allow for a sales process which requires assembly of several items at the point of sale, The most likely scenario in this instance then is that the child items will be in the same warehouse that the sale document is being recorded in, this should be the default position for the marketing document.
    The only workaround appears to be that a Sales Bom is required for each item for each warehouse, thereby increasing the size of the Item Master.

    THe issue is the same via the DI - add a sales BOM with a different warhouse to the BOM warehouse & the components are issued from the BOM warehouse, not the intended warehouse

  • Function to omitt parts from a BOM

    Hello,
    I would like to know if there is a function that allows to delet a component from an assembly content into a BOM but without having to create a new assembly (a new sub BOM) for example if I usually use assembly B but this time I want to remove component B1 form that assembly, and the rest remain the same, can this be done? kind of a flag that you can put to say "I am using this thing but without this component" and that the exploted bom for that shows everythig but the ommited component? I don´t know If I said it clear but if not please let me know to find a way to say it
    BOM 123
    assembly A
    assembly B
    assembly C
    component D
    component E
    And the assemblys have respectively their BOM
      |----> assembly A
                       |----
    Component A1
                       |----
    Component A2
                       |----
    Component A3
      |----> assembly B
                       |----
    Component B1 (component to be removed just for BOM 123)
                       |----
    Component B2
                       |----
    Component B3
                       |----
    Component B4
                       |----
    Component B5
                       |----
    Component B6
      |----> assembly C
                       |----
    Component C1
                       |----
    Component C2

    Do you mean to say if BOM 123 explodes then B1 component under B should not be included.
    But say if BOM XYZ explodes then B1 component under B should be included?
    If that is the need, then you can meet this need with a multi-level variant configured BOM. But if you're not working with variant configuration, then you will either have to create 2 BOM's & assign them accordingly or do manual intervention (have 2 alternatives, then depending on which BOM you're exploding, make one of the alternatives inactive, repeat process for the other - not user friendly) to meet your need.
    But if the need is to permanently remove B1 from B irrespective of where it is used & if you're working with ECM, raise a new change request & modify the BOM with the new valid-from date. If not working with ECM, then delete the component from the BOM.

Maybe you are looking for