You are on page 1of 3

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doc...

ASCP Plan Output Does Not Show Purchase Supplies - Internal Requisitions, PO's, Requisitions, or Shipments [ID 565210.1] Modified 29-AUG-2011 In this Document Symptoms Changes Cause Three Possible Causes: 1. Workbench Preferences Check 2. The Planning Manager is not running. 3. 11.5.9 or 11.5.10 and 10g database is installed or upgraded from 9i Solution Solution For 10g RDBMS and Missing Data Solution for the Planning Manager References Type PROBLEM Status PUBLISHED

Applies to:
Oracle Advanced Supply Chain Planning - Version: 11.5.8 to 12.1.3 - Release: 11.5 to 12.1 Oracle Advanced Supply Chain Planning - Version: 11.5.8 to 12.1.3 [Release: 11.5 to 12.1] Information in this document applies to any platform. FORM:MSCFNSCW.FMB - Planner Workbench EXECUTABLE:MRCRLF - Planning Manager EXECUTABLE:MSCPDP - Planning Data Pull

Symptoms
11.5.9 through R12.1 PROBLEM In the ASCP Plan Output in the Planner Workbench - Supplies created for buy items are missing. The ASCP Plan suggests new planned orders document Any Rate or Allthis of the following Buy type supplies can be missing in this scenario: Do not see the intransit supply for an internal sales order and suggests a new release for this requirement Do not see Requisition supplies Do not see Purchase Orders STEPS 1. ASCP Planning suggested release of a purchase requisition. 2. The user releases the planned order and creates an internal requisition. 3. An Internal SO is created. 4. ISO is released, SO is done. 5. At this point the items are in transit. 6. Run Data Collections and the ASCP plan - then see Plan output has new planned order for the same demand and the supply created is not in the plan. OR 1. ASCP Planning suggested release of a purchase requisition. 2. Release the planned order and creates a requisition 3. The Requisition may or may not be converted to a Purchase Order 4. Run Data Collections and the ASCP plan - then see Plan output has new planned order for the same demand and the supply created is not in the plan. BUSINESS IMPACT Over buying for all purchase type requirements.

Changes
In 11.5.9 or 11.5.10 the database was recently upgraded from 9i to 10g. The process was working without any problem before this install. OR a new installation of 11.5.10.2 was performed with 10g RDBMS (9i version was the originally for 11.5.10.x)

Cause Three Possible Causes:


1. It may be that cutoff dates are wrong in the workbench preferences OR 2. The Planning Manager is not running. OR 3. 11.5.9 or 11.5.10 and 10g database is installed or upgraded from 9i and the latest Data Collections rollup patch is not installed on the system.

1. Workbench Preferences Check


This could be quick solution if preferences are incorrectly setup. NAV: ASCP / Supply Chain Plan / Workbench Then use /Tools / Preferences and check: A> The Material Plan tab to make sure all required Supplies and Demands are checked to be displayed. B> The Other Tab and Days from Today field has number far enough into the future. Note: For standard MRP Planner Workbench, see Note 153001.1

2. The Planning Manager is not running.


1. Profile MRP: Consume MPS =Yes AND 2. MTL_SUPPLY table shows the record for the supply_type_code (PO, REQ, or SHIPMENT) for the quantity.
select * from mtl_supply where item_id in (&inventory_item_id)

1 of 3

1/24/2012 5:12 PM

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doc...

and to_organization_id in (&organization_id) order by last_update_date desc -- In the output of the SQL, find that the MRP% Columns do not have dates/quantities populated.

IF the profile MRP: Consume MPS = Yes THEN the Planning Manager must be running to populate the required columns and informaion in MTL_SUPPLY table Note: If running Distributed/Decentralied installation where Transaction instance (ERP Source Instance) is separate from Planning instance (APS Destination) then this process is run on the ERP source instance. The planning manager must be running to populate the MRP% columns in mtl_supply table or we do not collect the data. This is shown in the code for MSCCLAAB.pls as the requirement for all records collected from mtl_supply. For shipment records, the view used to collect the information is MRP_AP_PO_SHIP_SUPPLY_V

AND ||' ||' ||' ||' ||' ||'

mpp.project_id (+)= x.project_id' and mpp.organization_id (+)= DECODE( :v_mps_consume_profile_value,' 1, x.MRP_TO_Organization_ID,' x.Organization_ID)' and DECODE( :v_mps_consume_profile_value, ' 1, x.MRP_DESTINATION_TYPE_CODE,' x.DESTINATION_TYPE_CODE)= ''INVENTORY'''

-- comment: code chooses MRP% columns if profile = Yes, Otherwise, chooses base columns without MRP prefix. e.g. use MRP_DESTINATION_TYPE_CODE, otherwise use DESTINATION_TYPE_CODE

Notes: 1. The data will exist in the MRP_AP source views, but will not collect if the proper columns are not populated. 2. Collection views (ERP Source instance) used to collect supplies from MTL_SUPPLY are: 1. MRP_AP_PO_PO_SUPPLY_V 2. MRP_AP_PO_RCV_SUPPLY_V 3. MRP_AP_PO_REQ_SUPPLY_V 4. MRP_AP_PO_SHIP_RCV_SUPPLY_V 5. MRP_AP_PO_SHIP_SUPPLY_V 6. MRP_AP_SUPPLIER_RESPONSE_V 3. When profile MRP: Consume MPS = No, then the Collections process will collect these rows using different columns - Columns without MRP prefix. The MRP% Columns used are: 1. MRP_PRIMARY_QUANTITY 2. MRP_PRIMARY_UOM 3. MRP_EXPECTED_DELIVERY_DATE 4. MRP_DESTINATION_TYPE_CODE 5. MRP_TO_ORGANIZATION_ID 6. MRP_TO_SUBINVENTORY 4. Reasons to have the MRP: Consume MPS = Yes and to run the Planning Manager 1. Using Standard MPS Planning or MPS Schedules 2. Using the MRP Forecast API 3. Using MDS Loaded with Sales Orders 4. Using Forecast Consumption in standard MRP or Inventory application

3. 11.5.9 or 11.5.10 and 10g database is installed or upgraded from 9i

1. This issue is usually seen when customers have been running data collections successfully, then perform the upgrade, then suddenly find that some supplies are not showing up the ASCP Plan output 2. There were changes in the way the 10g RDBMS handles the Snapshot entities that are used for Collections. 3. These changes forced code changes and the requirement for all customers who upgrade and encounter any issues with missing data is to apply the latest Collections Rollup patch for their release (11.5.9 or 11.5.10 Section IV of Note 223026.1 - List of High Priority Patches for the APS Suite 4. To check the current rollup patch level on the system, use the standard apscheck.sql output Note 246150.1 and check Section 5.8 of the output. This output comes from SQL in Note 252108.1 which has the list of ro patches for each release for several areas of the APS suite.

Solution Solution For 10g RDBMS and Missing Data

As noted in the Cause statetment above, if 10g was installed as part of a new install or if 9i RDBMS was upgraded, then any missing data could be caused by not having the latest Data Collections rollup patch on th IF the planning manager steps below do not resolve the issue, THEN we highly recommend that you apply the latest patch and test this issue again. See above for more information. Also review the Planning Manager solution below to eliminate this as a possible cause

Solution for the Planning Manager


1. Start the Planning Manager -- NAV Material Planner / Setup / Planning Manager -- press the Start button -- The Planning Manager should only be launched once for all Orgs and OU's. It does not matter which Organization is chosen to activate the Planning Manager. 2. Let the planning manager complete one full cycle. 3. Then check the supply line again and find that the MRP% Columns are populated.
select * from mtl_supply where item_id in (&inventory_item_id) and to_organization_id in (&organization_id) order by last_update_date desc -- In the output of the SQL, find that the MRP% Columns are now populated.

4. Then run standard Data Collections processing with a Complete Refresh 5. Check the results in the View Collected Data (Collections workbench) 6. Then run the ASCP plan and observe the planning results. Notes on the Planning Manager Processes 1. The Planning Manager runs on the MRP Manager 2. The MRP Manager should ONLY run the Planning Manager and no other processes

2 of 3

1/24/2012 5:12 PM

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doc...

3. In System Administrator / Concurrent /Manager / Administer - The MRP Manager should have 1 Target and 1 Actual process running. Make sure the MRP Manager is running before starting the planning manager 4. Planning Manager runs for 24 hours on a single Request Id (or until Midnight after starting), then automatically resubmits itself as a new Request Id. 1. When Launched or during new launch at midnight, the Once-A-Day Task workers are launched. 2. These associated processes run on the Standard Manager and clean up the MRP%INTERFACE tables and MRP_SCHEDULER_MESSAGES table based on the setting of profile MRP Interface History Days setting = 5) 5. The default run interval seen in the Planning Manager screen is 00:00:30 - 30 seconds. The Planning Manager will 'wake up' every 30 seconds and look for a manager to launch it, then check for work to process. 1. It will show Running in the View Concurrent Requests screen during this time 2. If no work is found, then it goes back to Pending status very quickly (a few seconds) 3. IF work is found, then it will process and then go back to Pending status. 4. Overall the time the process rows is usually very short and most of the time the process will be in Pending mode 6. If launching for the first time, or the planning manager was not started for many days, then the 'first cycle' could take anywhere from 10 minutes to several hours depending on type of processing backlog that is pres system. 7. Profiles that influence the planning manager 1. MRP:Purge Batch Size - 75000 (75,000 is default setting) 2. MRP:Perform Planning Manager Functions in Loads = Yes (this will make planning manager process launch while performing Load/Copy/Merge of the MDS or MPS) 3. MRP:Planning Manager Batch Size 1000 (1,000 is suggested setting unless high volume for forecast interface or sales orders, if high volume everyday set 5,000 or if high volume for first launch set 25,000 an after initial processing) 4. MRP:Planning Manager Max Workers - 5 (suggested setting unless very high volume, then suggest 10 Note: These extra workers will launch on the Standard Manager) 8. Tables used during the processing of the planning manager 1. MTL_SUPPLY 2. MRP_FORECAST_INTERFACE 3. MRP_RELIEF_INTERFACE 4. MRP_SCHEDULE_INTERFACE 5. MRP_SALES_ORDER_UPDATES 6. MRP_SO_LINES_TEMP

References
NOTE:223026.1 - List of High Priority Patches for the Value Chain Planning (aka APS - Advanced Planning & Scheduling) Applications NOTE:252108.1 - How to Determine the Latest APS/VCP Patch Applied to the System

Related Products More Applications > Value Chain Planning > Supply Chain Planning > Oracle Advanced Supply Chain Planning More Applications > Value Chain Planning > Supply Chain Planning > Oracle Advanced Supply Chain Planning Keywords INTERNAL REQUISITION; MISSING DATA; MSCFNSCW.FMB; PLANNER WORKBENCH; PLANNING MANAGER; PURCHASE ORDER

Back to top Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

3 of 3

1/24/2012 5:12 PM