Академический Документы
Профессиональный Документы
Культура Документы
1
Demantra Solutions And Value Chain
Planning Live Advisor Webcast
MarchDay,
14,Date,
20122004 Upcoming Community Webcasts:
time
11:00 am ETp.m. ET am
/ 9:00
April 11, 2012: Using the Automatic Workload
MT / 8:00 am PT
Repository (AWR) to Cool Demantra Hot Spots in Doc
Teleconference Access: Id 800030.1
VOICE
North STREAMING
America: xxxx
ENABLED April 12, 2012: 12.1.3.6 Rapid Planning Enhancements
International: xxxx
in Doc Id 837233.1
Password: Advisor
North America:
For complete details on Demantra Solutions Webcast Events,
(866) 627-3315 please see Note 800030.1.
The integration interface profiles define the data, levels and intermediary
tables involved with the integrations.
Integration interfaces are define in Business Modeler > Tools > Integration
Interface
If you want to export and use multiple sets of forecast entries then you should
create as many data profiles and as many workflows and select those data
profiles as demand schedules in the ASCP plan options.
Those can be modified so you can generate forecast exports that best suit your
organization
For Series:
Forecast Series - predefined Final Forecast series or any other series where the internal
name should start with 'FCST_
Demand Priority Series - The internal name should start with 'PRTY_
Forecast Accuracy Series - The internal name should start with 'ACRY_
Destination Key Series - The internal name should start with 'DKEY_
For levels :
Item or Product Family
(if Item is chosen then the series Item Destination Key should also be selected for export)
Organization
Site or Account or Trading Partner Zone or Zone
Demand Class
S&OP Scenario
if the BIEO_% view is not getting populated with the right values
Review your integration interface definition. Maybe you do not
have forecast to export for the time and filters you have specified
on the integration interface
Create a worksheet with the same levels, time, series, filters as
you have in the integration interface and ensure you have data
EXEC UPDATE_MDP_MATRIX_DATES;
if demantra plan does not show in this view, then it will not
be seen in the ASCP plan names/options form .
select scn.scenario_name,
scn.demand_plan_name||':'||scn.scenario_name,
lu.meaning,
7 designator_type,
scn.scenario_id input_schedule_id,
scn.error_type error_type ,
null ship_to
from mfg_lookups lu, msd_dp_ascp_scenarios_v scn
where lu.lookup_type = 'MSC_DESIGNATOR_TYPE_SHORT'
and lu.lookup_code = 7
and scn.global_scenario_flag ='N'
and scn.scenario_name <> :mrp_plans.compile_designator
and ( scn.sr_instance_id = -23453
or scn.sr_instance_id = :mrp_plan_orgs.sr_instance_id )
and scn.last_revision is not null ;
Troubleshoot :
you had provided wrong parameter to the store procedure step of the workflow. You should provide the application_id
Log into your database as your demantra user and execute:
select query_name FROM TRANSFER_QUERY WHERE application_id = <the parameter you have passed>;
It should return 1 records , for your integration interface.
If not, then check again the application_id for your integration interface:
select APPLICATION_ID from transfer_query
where QUERY_NAME = <your integration interface>;
Then pass the right parameter to your store procedure step.
Log into your database as apps user and execute:
select query_name FROM <demantra>.TRANSFER_QUERY WHERE application_id = <the parameter you have passed>;
Replace <demantra> with your demantra schema name.
If it does not return any row, but it does when you are logged in as your demantra user, you may either have demantra
schema on a different database then the apps (that is not supported) or you are missing some privileges. Please ensure you
had run Update Synonyms
For a predefined integration interface:
select APPLICATION_ID from transfer_query
where QUERY_NAME = 'Global Zone Forecast';
APPLICATION_ID
---------------------------------------------------------------
B7C2E4FD6B7B32E7E040FE0A76A44C65
Cause: Rebuilding data model (as opposed to update model) will delete some objects which will cause issues like the ORA-
20015 error
Solution: Restore from a backup created before Rebuilding the Data Model
While trying to upload Global Zone Forecast an error occurs. Error description:'Database internal error:ORA-20015:
Exception: msd_dem_upload_forecast.upload_forecast_with_app_id - ORA-06550: line 1, column 15
Collaborator.log file shows:
[WFProcess_7] FATAL workflow.general:
ORA-20015: Exception: msd_dem_upload_forecast.upload_forecast_with_app_id -
ORA-06550: line 1, column 15: PLS-00904: insufficient privilege to access object DL_LOG_STATUS
ORA-06550: line 1, column 8: PL/SQL: Statement i
ORA-06512: at "APPS.MSD_DEM_UPLOAD_FORECAST", line 1276
ORA-06512: at line 1 java.sql.SQLException:
ORA-20015: Exception: msd_dem_upload_forecast.upload_forecast_with_app_id -
ORA-06550: line 1, column 15: PLS-00904: insufficient privilege to access object ORADEM.DL_LOG_STATUS
ORA-06550: line 1, column 8: PL/SQL: Statement i
ORA-06512: at "APPS.MSD_DEM_UPLOAD_FORECAST", line 1276
ORA-06512: at line 1
Cause:
There is an issue with privileges. 'APPS' user is missing execute privilege on the procedure
'DL_LOG_STATUS :
Solution:
Run the following from demantra schema :
GRANT EXECUTE ON DL_LOG_STATUS TO APPS;
Run again the workflow and check if it completes without error.
While running EBS Upload Global Zone Forecast workflow, the following error shows up:
Cause
Profile option MSC: Organization containing generic BOM for forecast explosion was not
populated with a value in the source instance.
SELECT fnd_profile.value('MSC_ORG_FOR_BOM_EXPLOSION') FROM dual;
return NULL
Solution:
Set profile option MSC: Organization containing generic BOM for forecast explosion with a
value in the source instance. It should be set to the organization containing your Master
Items
or the organization setup for validations of BOMs
Rerun ASCP Standard Collection to pickup the profile change.
Process ID: 2562 Schema ID: 1153 Schema name: ''Fcst Exp ASCP'' Step ID: ''PopulateDenormTable''
Step name: ''PopulateDenormTable'' Error description ''Database internal error: ORA-20015:
Exception: msd_dem_upload_forecast.upload_forecast - ORA-20005: Error:
: msd_dem_upload_forecast.upload_forecast - Incremental export type is not supported''.
Solution: Log in to Business Modeler > Tools > Integration Interface > Data Profile Naming page for option "Export Data" use
only "FULL
34
ERRORS
Running the Workflow EBS Upload Local Forecast or Upload Consensus Forecast-Org,Week is failing at the populate
Denorm Table step. In the Collaborator Workbench this was the error that was displayed.
Error description : Database internal error:ORA-6550: line 1, column 36:
Following is the error in the collaborator.log
PLS-302: component 'UPLOAD_FORECAST_WITH_APP_ID' must be declared
Cause: Demantra was upgraded to 7.3 and now the workflow were calling UPLOAD_FORECAST_WITH_APP_ID while
previously were calling UPLOAD_FORECAST
Solution : apply latest EBS-Demantra Integration Patch
CTO UPLOAD GLOBAL FORECAST - DEMAND CLASS, WEEK NOT PUBLISHING DATA
Navigation -> Demand Maangement System Administrator -> Workflow Manager -> CTO Upload Global Forecast - Demand
Class, Week
We can also see the status of workflow in INTEG_STATUS Table and its showing loaded data.
We can see view generated based on integration profile shows all data but when workflow calls
"apps.msd_dem_upload_forecast.UPLOAD_FORECAST_WITH_APP_ID", its not publishing any data in DENORM Table.
Cause: 'MSC: Organization containing generic BOM for forecast explosion' profile must be set to some value and then run
Standard collections.
Solution: set up profiles
1) MSD_DEM: Source Instance for Global Forecast
2) MSC: Organization containing generic BOM for forecast explosion
35
To ask a question on the
phone line, select *1 on your
phone.
To ask a question online, use
the Q&A area at the top.