Error in creating a schedule agreement

hi friends
i got an error in creating a scheduling agreement
the error reads- 'zjk5(the output type ) is not defined'
condition records,port definition,partner profiles everything is fine.
another error that reads is 'No communication data is set for medium 6ie edi'
please answer this problem.thanks is advance.

Hi,
Check the Output type was created or not for that Scheduling Afreement?
check the table T685 for that Output type?
And n the diocument have you configured the Output type with the correct medium (EDI value 6) and have you assigned the same in NACE tcode?
check
reward points if useful
regards,
Anji

Similar Messages

BAPI for creating sales scheduling agreement

Hi All,
I have a scenario where i need to create a sales scheduling agreement using VA31. I have tried using a function module "SD_SALESDOCUMENT_CREATE". I am able to create the document by inserting the correct data in "SALES_HEADER_IN", "SALES_ITEMS_IN", "SALES_PARTNERS" and using the update flag as " I ".
When I try to insert data in "SALES_SCHEDULES_IN" the function module returns error message "No schedule line category could be determined during quantity adjustment".
please provide help in finding out the right procedure for creating the scheduling agreement with schedule lines data.
Regards.
Anurag

Hi,
Did you shown this to your functional team.
Regards,
Madhu.
Edited by: madhurao123 on Nov 21, 2011 3:29 PM

Error generating release against scheduling agreement

Need help in resolving the below error msg for Scheduling Agreement.
ERROR message:
"Error generating release against scheduling agreement (cause 2)"
"2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated."

Yes.. its solved now...
problem areas:
1: delivery date not matching GR date.
solution: chng delvry date to GR date in ME38 and thn do GR.
2: Release not hapnd properly incase if u hav used doc typ LPA for JIT/Forcasting.
solution: in ME84, chk if the indicator for 'create release' is 'green' for ur SA#. In ME38, select the line and click on 'Release" icon. Select ur relevant delivery schudle line and click on JIT release or Forcast Release icon. See if the indicator is 'Green". If not, the issue is wit message output for the perticular delivry date. (use msg typ LPET process for output) MAKE SURE U SAVE THIS CHNG. Chk againg for the Release indicator for delivry line. If green thn.. its done..
Let me know if it was hlpful... or need clarity

Error generating release against scheduling agreement (cause 6) in ME38

Hello Experts,
Need your inputs on the the below error getting generated in ME38
Error generating release against scheduling agreement (cause 6)
Message no. 06857
Diagnosis
The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
In this case the cause of the error is 6.
System Response
The error may involve one of the following situations:
1: The nature of the error cannot be specified precisely.
2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
6: The factory calendar has not been maintained correctly.
Procedure
Error source 1:
Check whether the vendor and plant shown in the PO actually exist in the system.
Error source 2:
Check the Customizing facility for message determination with respect to delivery schedules created under scheduling agreements (print operation '9').
Error source 3:
In Customizing, maintain the document types accordingly ( Define document types for scheduling agreement). Then create a new scheduling agreement with a document type for which release documentation is defined.
Error source 4:
Maintain the JIT delivery schedule indicator in the material master record.
Error source 5:
Have the scheduling agreement released by the person(s) responsible.
Error source 6:
If you are using a release creation profile without aggregation, you must maintain the factory calendar for the next 999 days
Regards,
Santosh

Hello Mallinath,
I referred the note and following are the observarion in the system.
Step1:Run T-code SE16 (table T001W) to check the calendar ID of the plant.
-----Referred the Calendor ID
Step2: Check the JIT/Forecast delivery schedule of release creation profile in customizing. (T-code OLME -> Scheduling Agreement -> Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu.)
Run T-code SCAL to adjust the period of the calendar ID which checked in STEP 1 according to the JIT/Forecast delivery schedule of the release creation profile which checked in STEP 2.
(For example, if the JIT/Forecast delivery schedule of the release creation profile is "999" days, then the calendar should be extended for the next 999 days at least)
---------In this case factory calendor is valid till 2015 and according to note needs to change the factory calendor till 2018( or for 999 days) ?
Waiting for your inputs.
Thanking you,
Santosh

Error in MIGO for Scheduling Agreement

Dear All,
I have created a Scheduling agreement in LP document type and saved with Net price.
When i do the MIGO the error appears as below.
Transaction cannot be posted due to errors in price determination
Message no. ME573
Diagnosis
The error marked with 'X' occurred during the price determination process for purchasing document 5500000087 00010:
[X] Net price is 0.
[ ] Net price is negative.
and/or there are no valid conditions or the duration of the
contract has ended.
[ ] Effective value is negative.
[ ] Mandatory condition missing.
[ ] Negative delivery costs.
[ ] Delivery costs have been recorded although invoice
receipts are not defined for the item.
[ ] Error during quantity conversion
[ ] Error during currency translation
[ ] Field overflow
[ ] A condition involving delivery costs exists without a
transaction/event key.
[ ]Error during maint. of delivery costs in master conditions
Delivery cost conditions in different validity periods not identical
System Response
The transaction cannot be posted without successful price determination.
Procedure
Check the purchasing document and the associated conditions:
Display purchase order
Display scheduling agreement
If the problem cannot be resolved in this way, contact your system administrator.
The latter can check the Customizing settings for price determination in Purchasing under Conditions -> Define Price Determination Process
When the foregoing steps have been carried out, try posting the transaction again.
Kindly advice how to avoid this error.
Regards

Hi
What type of document type are you using for Scheduling agreement? I think you are using time dependent conditions. (see it in document type definition config). If the tick mark is done for time dependent condition then in additional data of scheduling agreement line item pr.date category will be 5-GR date. So Your validity period for condition is not valid for today thats why you are getting error. You need to change validity period for your conditions. Then you will not get error.
Regards
Antony

Error to change the scheduling agreement

after creating the scheduling agreement, i tried to modify the scheduling agreement that does not have a Delivery Schedule using ME32L. and I got an Error message FGV004 - "SYST:date 00.00.0000 is not expected". however, if i updated the delivery schedule, i didn't get the error message when I modified the scheduling agreement. any suggestion?

Hi AP,
the question is the smiliar, but I'm looking for notes in MM area, not FM area.
Elaine

Funktion to create MM Scheduling agreement

Dear all,
I am looking for a funktion/bapi to create material scheduling agreements in SAP. I think BAPI_PO_CREATE1 does only create purchase orders. Any ideas how to create scheduling agreements by funktion?
Kind regards
Roman

Hi,
Did you read the FM documentation.
there a table parameter for Schedule lines.
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Check it...
you can use it to create the schedule lines also...
Regards
vijay

I have created a scheduling agreement for a material i want to cancel.

i have created a scheduling agreement with a material i want to use the material in a contract with another vendor, is there any way i could use the material or i have to terminate the scheduling agreement and create the contract. in case of canceling the agreement what are the steps involved i mean the T Codes.

Hi,
First af all you have not mention that is ther any subsequent delivery documents are exist against that scheduling agreement or not....if yes then you cannot delete the scheduling agreement unless u reverse the deliveryin t-code VL09 and by cancelling billing docs in VF11(if invoice created) as well...
If thr is no Deliveries, then you can delete that scheduling agreemnt very well, by going VA32 enter agreement no., press enter
on top selct sales doc option and delete the agreeement...
Reg
JJ
Edited by: Jagsap on Jul 9, 2009 2:11 PM

Error generating release against Scheduling agreement (Cause 2)

dear Sap Experts,
Please advise me that Error generating release against Scheduling agreement (Cause 2)
As i have already used transaction code OMQP and click print operation 9 for LPH1 & LPJI A,
How can i sort this problem.
Thanks
mohit

Hi,
pls find below thread
SA delivery schedule release problem
you have to Maintain condition records for LPJ1 and LPF1 in NACE
maintain condition record in transaction MN10 for schedule release. And Generally in the condition records will be maintained for LPH1 & LPJ1in MN10.
Once you maintain that, you can go to ME84 and ME38 release the schedule
the JIT indicator in MMR for your material.
Check that and also you can maintain a release creation profile in VMR or ME31L.
Regards
Raj.

Is it possible to create Automatic Scheduled Agreement like Automatic PO

Could you please explain, is it possible to create an automatic schedule agreement from the PR, PIR (ie.e viz.. as Creation of Automatic Purchase Order)

Hi
Why you want to generate the Scheduling agreement automatically? What is the requirment? Volume is high?
As Sridhar mentioned you have no option in standard SAP to create automatic scheduling agreement. But you can create delivery schdule via MRP.
If you have more volume then go for developing the program with ABAP guys.
if the requirment is for Cut over only then go for LSMW or BDC options.
Hoe it helps
Karthik

Sap Error generating release against scheduling agreement (cause 2)

Hi,
Please help me on this issue
Error generating release against scheduling agreement (cause 2)
Message no. 06857
Regards
Amey

Hi,
For EDI you might be missing settings in:
1) Matrl Mng -> Purchasing -> Messages -> Output control -> Output types -> Define Message Types for Scheduling Agreement Release/Expediter -> Fine-Tuned Control: Forecast Delivery Schedule/Expediter (check one of the outputs for 9 and for A )
2) WE20 - EDI settings for partner that is a vendor who should receive your release information DELFOR / DELJIT (if you do not manage other EDI settings then also other WEDI setings should be maintained)
Best Regards,
Tomek

How are deliveries automatically created from scheduling agreement?

How are deliveries automatically created from the schedule line of the scheduling agreement? Can anybody explain this step by step? Can we use the code VL10BATCH for this purpose? If we can, how is this code used?
Thanks in advance.

hi
A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement or you can create them later.
You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have carried out the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity.
The scheduling agreement is used as a basis for delivering a material. The customer sends in scheduling agreement releases, referred to as delivery schedules, at regular intervals to release a quantity of the material.
Document Types
To configure document types for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Header -> Define sales document types in Customizing for Sales and Distribution.
The R/3 System contains the following document types for component suppliers:
LZ - Scheduling agreement with delivery schedules (no external agents)
LZM - Scheduling agreement with delivery orders
LK - Scheduling agreement with delivery schedules (external agents)
ED - Delivery by external agent (consignment issue)
EDKO - External agent correction
RZ - Scheduling agreement returns (no external agents)
KAZU - Consignment pick-up for external agents
KRZU - Consignment returns for external agents
Item Categories
To configure item categories for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Item -> Define item categories in Customizing for Sales and Distribution.
The system determines the following item categories for the related document types in
documents containing materials with item category group NORM:
Item category LZN for scheduling agreement type LZ
Item category LZMA for scheduling agreement type LZM
Item category LKN for scheduling agreement type LK
Item category KEN for document type ED
Item category EDK for positive corrections (or the manual alternative EDK1 for
negative corrections) for document type EDKO
Item category REN for document type RZ
Item category KAN for document type KAZU
Item category KRN for document type KRZU
Schedule Line Categories
To configure schedule line categories for scheduling agreements, choose Sales -> Sales Documents -> Schedule lines -> Define or Assign schedule line categories in Customizing for Sales and Distribution.
The R/3 System contains the following schedule line categories for component suppliers:
L1, BN, L2, and CN for item category LZN
E4, E0, E5, and BN for item category LKN
L2 for item category LZMA (standard for delivery order processing)
Schedule Line Types
To configure schedule line types for scheduling agreements, choose Sales -> Sales Documents -> Scheduling Agreements with Delivery Schedules -> Define schedule line types in Customizing for Sales and Distribution.
Creating Scheduling Agreements
To create a scheduling agreement with delivery schedules:
1. In the Sales menu http://Ext. choose Scheduling agreement ->Create.
2. Enter scheduling agreement type LK (standard) or LZ (external agents) and the
relevantorganizational data.
3. Choose ENTER.
4. Enter the following data:
Sold-to or ship-to party number
Purchase order or closing number
Material or customer material number
You can use the Description field to identify the scheduling agreement. For
example,
you could enter the model year for a particular production series.
The system allows up to 35 digits for a customer material number.
Rounding quantity
Usage
Choose Goto -> Header -> Sales to enter the usage at header level, or Goto ->
Item-> Sales A to enter it at item level. The system proposes usage S, for series, as default in both cases.
Planning indicator
Choose Goto -> Header ->Sales.
Target quantity
Mark an item and choose Goto -> Item -> Sales A
Partners
For scheduling agreements with external agents , choose Goto -> Header
->Partners to enter the external agent as forwarding agent and special stock partner
on the partner function screen.
5. Create a delivery schedule
Mark an item in the scheduling agreement and choose Goto -> Item -> <Delivery
schedule>. Enter:
A delivery schedule number and date
The cumulative quantity received by the customer
The last delivery confirmed by the customer
A schedule line with date, time, and quantity
To enter additional data in the delivery schedule, choose DlvSch.Hdr (delivery schedule header).
configuration:
img->SD->Sales->sales document->scheduling agreements with delivery schedules->
step1: define schedule line types
schedule line types are not schedule line categories. Schedule line types are used for information purpose only.
stds are 1. fixed date 2. backlog 3. immediate requirement
4. estimate
step2: maintain planning delivery sched. instruct/splitting rules
The planning delivery schedule is an internal delivery schedule used to plan requirement s more efficiently. It is sub divided into 3 parts
2.1 delivery schedule splitting rules
2.2 dly schedule instrusctions
2.3 assign dly schedule splitting rules
step3: define sales documents type
step4 : define item categories
step5: define schedule line categories
step6: maintain copy control
PROCESS
step1: create scheduling agreement
VA31
enter SP,SH valid from, valid to,
goto ITEM OVERVIEW tab
enter material, rouding qty
select ITEM click on FORECAST DLSCH
enter different dly dates and qties
save it.
step2: create sales order with reference to above
step3: create delivery
step4: create billing
regards
krishna

VA31 - Create a scheduling agreement

Dear Gurus,
When trying to create a scheduling agreement using VA31, I input the following data:
Sched. Agreemt Type
Sales Organization   2200   France, Paris
Distribution Channel 14     Service
Division             00     Cross-division
Sales Office         2200   Office Paris
Sales Group          2200
Now, I cannot choose any Scheduling agreement type from a drop down menu as none seems to be linked or created for that sales area.
Can anyone help me create a list of Scheduling agreement I can choose from?
Thanks
Chris

Scheduling agreement type should have been created in VOV8 and then this document type should have been assigned to your sales area 2200 / 14 / 00 in OVAZ. Check whether you have assigned your scheduling agreement type in OVAZ.
thanks
G. Lakshmipathi

Error while creating a Scheduled job in OIM 11g

While creating a scheduled job, if i click on the Task and search to select the value, i get the following error.
<Nov 14, 2011 5:10:24 PM IST> <Error> <oracle.adfinternal.view.faces.config.rich
.RegistrationConfigurator> <BEA-000000> <ADF_FACES-60096:Server Exception during
PPR, #1
javax.servlet.ServletException: java.lang.AssertionError
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:341)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.j
ava:205)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter
(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
istChain.doFilter(TrinidadFilterImpl.java:447)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter
.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
istChain.doFilter(TrinidadFilterImpl.java:447)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilt
erImpl(TrinidadFilterImpl.java:271)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilte
r(TrinidadFilterImpl.java:177)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFi
lter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmt
NavigationFilter.java:122)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthCon
textFilter.java:108)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:1
76)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
3)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
il.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
a:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
61)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:13
6)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsF
ilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
ervletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
ontext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
ava:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.AssertionError
at org.apache.myfaces.trinidad.component.ChildArrayList.__removeFromPare
nt(ChildArrayList.java:191)
at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayLi
st.java:53)
at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayLi
st.java:69)
at org.apache.myfaces.trinidad.component.ChildArrayList.add(ChildArrayLi
st.java:33)
at oracle.iam.consoles.faces.render.canonic.UIValue$UIEntitySelector.sea
rch(UIValue.java:1670)
at oracle.iam.consoles.faces.render.canonic.UIValue$UIEntitySelector.acc
ess$2400(UIValue.java:1467)
at oracle.iam.consoles.faces.render.canonic.UIValue$EntitySelectorQueryL
istener.processQuery(UIValue.java:1787)
at oracle.adf.view.rich.event.QueryEvent.processListener(QueryEvent.java
:67)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcast(UIXC
omponentBase.java:675)
at oracle.adf.view.rich.component.UIXQuery.broadcast(UIXQuery.java:108)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.r
un(ContextSwitchingComponent.java:92)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._pr
ocessPhase(ContextSwitchingComponent.java:361)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.bro
adcast(ContextSwitchingComponent.java:96)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclu
de.java:102)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.r
un(ContextSwitchingComponent.java:93)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._pr
ocessPhase(ContextSwitchingComponent.java:361)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.bro
adcast(ContextSwitchingComponent.java:96)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclu
de.java:96)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents
(LifecycleImpl.java:902)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(L
ifecycleImpl.java:313)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(Lifecyc
leImpl.java:186)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
tyHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.j
ava:205)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter
(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
istChain.doFilter(TrinidadFilterImpl.java:447)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter
.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterL
istChain.doFilter(TrinidadFilterImpl.java:447)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilt
erImpl(TrinidadFilterImpl.java:271)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilte
r(TrinidadFilterImpl.java:177)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFi
lter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmt
NavigationFilter.java:122)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthCon
textFilter.java:108)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:1
76)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:31
3)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUt
il.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.jav
a:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:1
61)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:13
6)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsF
ilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:57)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
ervletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
ontext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
ava:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
This behavior is seen in most of the lookups when we try to search for value.
Please let me know for any configuration steps for the same issue.

Have you tried restarting the db and the server? I have seen this on user search and a db restart along with server restart solved it for me. Also note that this error in my case was due to wrong mds file. so for you also check ur tasks and any custom xml which might have some errors into it.
HTH,
BB

Error while creating a scheduler

Hi,
I have created a scheduler to reconcile the data from trusted resource. It ran fine yesterday and was pushing users in OIm. Now I am not able to push the users. 2nd record has been deleted for OIM console, thereofre it is throwing below error:
oracle.iam.reconciliation.exception.CreateException: oracle.iam.platform.kernel.ValidationFailedException: IAM-3050007:The user with the attribute User Login and value xyz already exists.:User Login:xyz
at oracle.iam.reconciliation.impl.EntityTypeHandler.create(EntityTypeHandler.java:102)
Thanks,

Please follow the below steps to re-create the deleted user.
Update deleted user record, so the login name can be reused:
1. Log in to OIM Console as xelsysadm
2. Click Administration -> Users --> Search
3. Check Match All, enter the User Login, Click Search
4. Select the user, click Delete User. This will delete the user.
5. Login OIM Database as OIM shcema name (default is DEV_OIM)
6, Run following sql command
update usr set usr_login = usr_login || '-deleted' , usr_first_name = usr_first_name || '-deleted', usr_last_name = usr_last_name || '-deleted' , usr_ldap_dn = usr_ldap_dn || '-deleted' , usr_ldap_guid = usr_ldap_guid || '-deleted', usr_common_name = usr_common_name || '-deleted' , usr_email = usr_email || '-deleted' where USR_STATUS='Deleted'
7. Then you can reuse the original user login
These steps are recommended by Oracle in the metalink id 1451717.1.

Error in creating a schedule agreement

Similar Messages

Maybe you are looking for