Source determination in backend (R/3) for distributed contract i.e. GOA

Hi,
Source of supply is not getting picked up in R/3 in PR generated for Non- stock item while creating work order (IW31), though GOA exists in R/3 for that material. Maintaining source list also does not help. Please note that it works fine for local contracts. Also it works for PR created using ME51n for GOA as well. Any solution?
Thanks,
Manoj

Hi, did you ever solve this issue? i am suffering the same type o problem, please let me know in case you found a solution.
Best regards.

Similar Messages

Source Determination flag in ME51N

Hi All,
I want to set Source determination flag on as default setting in me51n (NB document type). That should be common for all the users. Setting the default value in personal setting will not be worked. Could you pls tell me how to configure.
Tks
Sujith

Hello Sujith
If you want the source determination field to be default for all users, one of way to achieve this is you manina source list with fixed vendor with ME01 T-code.
Also info record (ME11) must be present for that vendor material combination in the system
If both of the above source lsit and info records are mainatined , the source will be automatically determined when you chcek the tick box in purchase requistion.
All the users should be grouped under one purchasing group which should be used in info record for that vendor materail combination.
Either way with the help of screen control settings you can make source determination filed as REQUIRED Filed, so that purchase requisition will not be saved unlesss source is determined in purchase requistion.
Note : To determine the source in purchase requistion, source list and info records are mandatory.
I hope this helps.
Br,
Tushar

ME52N - Automatic source determination fails

Hello experts!
i have detected an issue at my system when i set the Automatic
Source Determination flag when i change a Purchase Requisition at
ME52N.
Here is the situation.
If we set this flag at the PR creation (ME51N), the source
determination is well done.
However, if the user forgets to set flag "Auto Source Determination" at
the PR creation, at ME52N when it is set, the Source is not
determinate automatically...
If you press button "Assign Source", it is brought to the PR correctly.
Is there any OSS Note that solves this mistake??
Thank you very much in advance.
Regards,
cecil

Hi Maria
The header level "source determination" check box is intended for getting the appropriate source for <b>each</b> PR line items while <b>creation</b>.
As you have created PR lines already without choosing this option, now by simple selection in ME52N will not assign source. You have to use source assignment at individual item level.
warm regards
sairam akundi

Distributed contract release query!

Hi all,
Need help!
As I have created ''distribution contract'' without any plant. Now when trying to release the contract without putting any'' plant'' as I want to leave it open so that as when required ......my other company ''plant'' can create a release order against the contract later.
But during my release order creation... ..system is asking for Plant and now allowing me to save the document. Is it correct for system to ask for PLANT or is there any problem whcih need to be rectified.
Let me know your thoughts and advice.
Thanks in advance.
Cheers!

Thanks to both of you for your time.
But clear me out if I am wrong. I am trying to do my scenerio as per the theory goes for DISTRIBUTED CONTRACT, as follows,,
EXAMPLE -I have company code- ABCD...... & pur org -ABCD............. and plant -A & B with same company code.
now i have created contract with MATERIAL-A (1000 qty) ''without account assignment'' and ''Plant'' in my CENTRAL SYSYTEM.
Therefore now i am trying to do realease order against the contract with proper account assignment , but ''without a plant'' so that my central system makes the contract available to my local system ( so my local company plant A & B can create release order later as per thier need using thier own plant number in my LOCAL SYSTEM)
I guess theory says the same as I describe above. Now could any body let me know if I need to correct somewhere OR how do the actual FLOW happens.
Many thanks in advance.

Sourcing Determination for Automatic Bid invitation.

Helo all,
We have a few issues with Sourcing Determination.
SRM 4.0/EBP 5.0 SP 08
We set the sourcing for all
Product categories - Automatic Bid invitaion for items without source of supply in the Table BBPV_SRC_DETERMINE
It was working fine but all of a sudden it moves all the requirements into the Sourcing cockpit instead of creating a Bid inviation.
Things done after this set up..
Product Categories were replicated again into the SRM system.
All settings for product categories were deleted and entered again. (Ex PPOMA_BBP, Define Bckend sys for prd cat) etc.
Has anyone run into issues like this before.

Hi Claudia,
I have created the contact person for bidder through the web only. There shouldnt be any problem in creating BP or contact person as the bid invitation was sent to bidder sucessfully, even i could create contract in backend after the bids receieved from the same bidder.only some times this error is flashed. ( all atributes, master data used is one and the same).
Now could u please tell me how exactly the bid invitaion is sent to bidder. any FM, prog??? which i should check out??
About creating bidder, I have created the bidder after replicating that vendor from backend. Then for the bidder i have created employee as a contact person through web ( Manage business partner) with bidder role assigned.
thanx please.
Regards,
Vivek

Source Determination for Service PR

Hi Experts,
One of our clients requirement is in their Procurement process, they want to create Service PR (material group, text) with Item category D and Acc Assignment as K. They want the system to determine the Source of supply automatically. When we check the source determination check box- but the system is unable to determine the source.
They want to remove manual intervention. If the source is determined in PR, it will be converted to PO. Please assist.
Thank you,
Surendra

Dear Surendra,
This is to let you know that, there is no provision to maintain source list for services as we do for materials.
Suggestion A:
Since there is no provision to maintain the source list for services, follow the steps, which are explained by AKPT M . Sure it would help you, if not check out the other two suggestions, given below.
Suggestion B:
If you would like to have automatic procurement process as material procurement, better follow the below steps;
Create a material with material type DIEN
Maintain the source list
Create a PO for the service material
Create MIGO document
Note: As you are procuring services through material master, there is no involvement of Service Entry Sheet and the services will be directly posted to consumption account.
Suggestion C:
Try with 'Standard Service Catalog - ML01
Thanks & Regards,
Narayana N

Source Determination for contracts via ME25

Hi All,
We are using ME25 to create PO's. During source determination, a
contract that is valid on the delivery date but not on the current date
is not suggested as a possible source of supply though it has been
maintained in the source list.
We know that this is programmed this way.Check is always carried on the
basis of current date. Though the delivery date falls within the
contract validity date, the system does not suggest the contract as a
source since the validity of that contract has not yet started or it is
not matching with the current date.
But we want the system to suggest the contracts as a source of supply,
though the validity of the contract has not yet started. we want the
system to suggest the contracts which are not valid on current date(but
valid on a particular delivery date) also.
SAP notes 44368 and 427864 suggest that this can be achieved.The note
427864 also tells that "selection with a date other than the current
date could lead to problems (for example in case of MRP runs).With the
corrections of Note 44368 you can solve the problem".
It also says as below:
"The attached correction instruction solves the problem described in
this note. However, these corrections might lead to other problems.
Therefore these corrections are not implemented in the standard system."
It says it might lead to other problems also. But it didn't mention the
exact problems.It would be great if you can list out the MRP run and
other problems and suggest us.
We want this functionality. One more note 116464 is also related to
this. Suggest us which are the notes to be applied. We are currently
using SAP 4.7 Version.
Thanks in advance.
Warm regards,
Shankar Goud.

Hi,
I am not sure that there will be any problems by changing this if you do it the way that the note indicates. I would suggest that SAP are quite right to effectively say "We have designed our system to use the current date, if you want to use anything else then you MAY have problems" (because effectively this is what they are saying).
It is a heavily integrated system and changes like this can cause unforeseen problems, but if you are going to test it thoroughly then it SHOULD be OK.
I would agree with SAP in that it is far better to NOT make this change, but if you really need to do this as part of your business process then you may have no other choice.
Have you thought of bringing the date of the contracts forward to the current date when they are created and controlling their use by setting the source list dates to the dates you want them to be used? This may not work and it too is a scary change but it might be worth having a play with it in your sandbox system (also set the source list as mandatory on the material master if you want to stop manual POs from being allocated too early).
So I guess I am saying go ahead if you have to but beware the warnings (even though they may be unfounded).
Steve B

URGENT PLEASE HELP - Source determination in Limits Carts not working

Dear all,
We have implemented SRM 4 on Server 5.0 and ECC 5 backend.
We have in our environment service masters that have been catalogued and linked to Contracts. When one raises a cart and selects one on these catalogue service items, a backend PO correctly creates and references the contract as specified in the catalog.
The problem we have discovered that if we raise a Limits order and specify the material group stipulated in the contract for a service, source determination fails to "pick up" this contract line. We are forced to enter a supplier all the time!
Also if we raise a text service line and select from "internal Goods/Services" a Service Master record and add it tothe cart, surce determination also does not pick up the R3 contract/line that matched this service. This means that when POs are created in the backend, they are not referencing any contract (no call-off)
Why is this happening? How come catalogue items linked to a service masters and contracts work and correctly and a Limits order do not?
Please help, we need to resolve this issue today.
Thanks,
Grace.

Hi Grace,
The contracts that are created in SRM can only be refered as Source of supplies while creating shopping carts if your are working in Extended Classic scenario.
In case you want to refer the back end contracts, Info. records for creating shopping carts you have to implement classic scenario.
The standard SRM does not provide the functionality you needed where as if you want to use back end contracts for a particular product category you can implement "Controlled Extended Classic Scenario BADI " which makes the classic scenario active for that product category, there by a back end contract can be referred for that product category when ever a shopping cart is made.
Hope this makes you clear. Clarifications are welcome.
Award points for suitable replies.
Rgds,
Teja

Source determination,Quota Arrangement Process

Hi,
Plz tell me how to maintain Source determination,Quota Arrangement.step by step

Dear,
QUOTA ARRANGEMENTS
If a quota arrangement exists for a material, it has the highest priority during source determination. Like source list, the quota arrangement facilitates the administration of sources of supply at plant level.
If you procure a material from different suppliers, you can assign a quota to each individual supplier. A quota arrangement applies to a certain period and specifies how the receipts should be distributed among each source of supply.
If a quota arrangement exists, this does not mean that the quantity of a single manually created purchase requisition is automatically apportioned among different sources. In such case, the entire quantity of the requisition is assigned to one source u2013 the source that is next in line receive the relevant order.
Before you can maintain a quota arrangement item with the procurement type external procurement, a source of supply (info record and / or outline agreement) must exists.
Create quota arrangement:
LOGISTICS u2013MATERIAL MANAGEMENT u2013 PURCHASING u2013 MASTER DATA u2013 QUOTA ARRANGEMNET u2013 MAINTAIN.
Specify number ranges for quota arrangement:
SAP IMG u2013 MATERIAL MANAGEMENT u2013 PURCHASING u2013 QUOTA ARRANGEMENT u2013 DEFINE NUMBER RANGES.
You must specify the business application for which quotation arrangement will be used, for example: in material planning or in purchase requisitions. You make this specification in QUOTA ARRANGEMENT USAGE filed, which is to be found in the plant-specific purchasing/materials planning data of the material master record.
Set quota arrangement usage indicator:
SAP IMG u2013 MATERIALS MANAGEMENT u2013 PURCHASING u2013 QUOTA ARRANGEMENT u2013 DEFINE QUOTA ARRANGEMENT USAGE.
System assign quota rating to each source by calculation as u2013 Quota rating = (quota allocated quantity + quota base quantity / quota).
ADDITIONAL ASPECTS OF SUPPLY SOURCE DETERMINATION
Quota arrangements also can be source of supply.
Quota arrangements for material requirements arising over a certain period divided up among different sources on basis of quota. Quota arrangements determine which source of supply is automatically assigned to a purchase requisition.
SOURCE DETERMINATION
The purpose of the source determination process is to automatically assign a source of supply to a purchase requisition, if source determination indicator set in the requisition header, the system searches for possible sources of supply for all the items of the requisition. Quota arrangements also can be source of supply.
In source list specify a preferred source as fixed for a certain period, the system suggest just only this source, even if other potential sources exists.
Quota arrangements for material requirements arising over a certain period divided up among different sources on basis of quota. Quota arrangements determine which source of supply is automatically assigned to a purchase requisition.
Source list record consists of the following:
1.Validity period u2013 Period of validity
2.Key source data u2013 Number of vendor and responsible purchasing organization or number and item of outline agreement.
3.Fixed source u2013 Within a validity period not more than one source should be flagged as fixed.
4.Procurement plant u2013 if the materials can be procured from a plant or another point within your firm, enter the plant number in PPl field and leave the field for the vendor number empty.
5.Blocked source u2013 To block a source. If you set Blocked indicator and enter only one validity period, the material is excluded from external procurement; that is, it cannot be ordered during this period.
6.Material requirements planning - You use MRP indicator to determine whether an automatic source determination process is carried out during the requirements planning run. The appropriate source is then automatically assigned to a purchase requisition, or scheduling agreement delivery schedule lines can be generated directly via planning run.
If an attempt is made to order a material subject to a source list requirement from a source that is not included in the source list, the standard system issues an error message with the text: Source not included in list despite source list requirement. You can change this to warning message.
If source list requirement defined for a plant, all materials in the plant level must be maintained with source list before procurement.
Analyze source list:
LOGISTICS u2013 MATERIAL MANAGEMNET u2013 PURCHASING u2013 MASTER DATA u2013 SOURCE LIST u2013 FOLLOW ON FUNCTIONS u2013 ANALYSE.
Define source list requirement at plant level:
SAP IMG u2013 MM u2013 PURCHSING u2013 SOURCE LIST u2013 DEFINE SOURCE LIST AT PLANT LEVEL.
Source lists can be created:
-Manually.
-Create from within an outline agreement u2013 on outline agreement overview screen, select an item for which you wish to enter source list record and choose ITEM u2013 MAINTAIN SOURCE LIST.
-Creation from with an info record u2013 you can enter vendor in the source list when creating or changing a purchasing info record. Choose EXTRAS u2013 SOURCE LIST. If the info record valid for entire purchase organization, you can create the source list for all plants of the organization in question. Choose the plant via GOTO u2013 PLANT.
-Automatic u2013 can generate by system automatically.
Create source list manually:
LOGISTICS u2013 MATERIAL MANAGEMENT u2013 PURCHASING u2013 MASTER DATA u2013 SOURCE LIST u2013 MAINTAIN/DISPLAY.
Generate source list automatically:
LOGISTICS u2013 MATERIAL MANAGEMENT u2013 PURCHASING u2013 MASTER DATA u2013 SOURCE LIST u2013 FOLOW ON FUNCTIONS u2013 GENERATE.
Regards,
Syed Hussain

Error occurred while forwarding a message for distributed destination

Is there a change in the way that Uniform Distributed Destinations are handled in the cluster after weblogic9.2?
I am using oracle weblogic 10.3.0.1 in production mode. I have two managed servers, each managed server has a JMS Server.
I create a Uniform distributed Topic on the System module, and publish a message to it.
I can see the message in the topic on the first JMSServer but the following error happens and the message never makes it to the second JMSServer
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on IP:PORT for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ManSvr1" for domain "Domain" running in Production Mode>
<Sep 24, 2009 2:00:46 PM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on mip:mport>
<Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Sep 24, 2009 2:09:52 PM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member JMSSystemResource!JMSServer2@example: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:

I specified the cluster address, but still get the following errors after a message is published to the topic. Are there other configuration items that can be checked?
<Sep 29, 2009 9:51:49 AM GMT+00:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 29, 2009 9:52:01 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultAdministration" is now listening on 10.241.134.92:7018
for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.241.134.92:7019 for
protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ClusManSv
r2" for domain "domain" running in Production Mode>
<Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on 224.0.0.10:7390>
<Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Sep 29, 2009 9:56:14 AM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destinati
on member SOAFJMSSystemResource!SOAFJMSServer1@EventingAdminTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExc
eption: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:testnn
2092.net:domain:ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Def
ault[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination
weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:
managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:managedServer.net:domain:
ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; N
o available router to destination; nested exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
exception is:
java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
ilable router to destination
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:158)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:499)
Truncated. see log file for complete stacktrace
java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,701
7,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No known v

JMSAn error occurred while forwarding a message for distributed destination

Hi,
i have getting issue with JMS Server delivery fail, below is the errors
####<Aug 24, 2012 2:03:54 PM CDT> <Warning> <JMS> < <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default
(self-tuning)'> <<WLS Kernel>> <BEA1-0979336B7FF44582D27D> <> <1345835034568> <BEA-040498> <An error occurred while forwarding a message for distribute
d destination member SystemModule-0!d4a JMS Server@D Distributed Topic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExcepti
on: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, java.rmi.ConnectException: Destina
tion unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, jav
a.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination
weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[
8011,8011,-1,-1,-1,-1,-1]:d:d4a, java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, jav
a.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:155)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:492)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:488)
at weblogic.jms.backend.BEForwardingConsumer.pushMessages(BEForwardingConsumer.java:300)
at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:256)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, java.rmi.Con
nectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, jav
a.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
####<Aug 24, 2012 2:03:54 PM CDT> <Warning> <JMS> <dal604se113com> <a> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default
(self-tuning)'> <<WLS Kernel>> <BEA1-0979336B7FF44582D27D> <> <1345835034568> <BEA-040498> <An error occurred while forwarding a message for distribute
d destination member SystemModule-0!d4a JMS Server@D Distributed Topic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExcepti
on: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, java.rmi.ConnectException: Destina
tion unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:dsa, jav
a.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination
weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[
8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, jav
a.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:155)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:492)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:488)
at weblogic.jms.backend.BEForwardingConsumer.pushMessages(BEForwardingConsumer.java:300)
at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:256)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, java.rmi.Con
nectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, jav
a.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
Edited by: Ikhan on Aug 29, 2012 4:00 AM
Edited by: Ikhan on Aug 29, 2012 4:01 AM

The distributed topic forwarders replicate messages to every member of a "replicated distributed topic". They will report errors if intra-cluster communication is interrupted or if servers in the cluster shut down. I recommend checking your server logs to see if other errors/warnings exist, and, if you suspect an intra-cluster communication problem, consulting the cluster troubleshooting guide(s) in the edoc.
Most newer apps (apps hosted on versions 10.3.4 or higher) should consider using the new "partitioned distributed topics" instead of "replicated distributed topics". These don't use forwarders and scale better.
HTH,
Tom

Assign Source of supply is not working for contract with material group

Dear Experts,
I have searched all the threads and gone through before posting my query. So i would ask moderators to go through the thread properly before rejecting this.
We have value contracts with respect to a particular material group without material and with item category W in the contract item, Please note that for the materials with this material group, the source determination is not set and source list is also not maintained.
When we create PR for the material with this contract, and when we click on assign source of supply contracts used to get popped up, but recently from few days, when we click on assign source of supply we are getting an error " no source found for this item ".
Can anybody help on this.
Regards

@ Biju,
As mentioned earlier, we are not creating PR with reference to contract.
first we are creating contract with item category W (material group), without material and plant details.
we create PR with or without material with account assignment K and with the material group in the transaction ME51N, and after inputting all the fields, we click on assign source of supply, it was proposing the existing contracts with respect to material group earlier, but it is not happening for particular material group(it is working for all other material groups)
Hope it is clear.
@ Dev Patra,
we are using DIEN-Service material types and we assign that particular material group to only service material type.
we have not ticked, source list in the material master, we donot have any source list for the materials under that material group.( please check the note 457110- question number 14.)
Regards

Source determination not happening during PR creation from Planned order

Hi Experts
We have set up source determination and we have created a sourcelist of material and a vendor is fixed, there is a inforecord alos maintined,
I am trying to convert a planned order from MD04 to a purchase requisition, the source is not being assigned for the PR, I am alos getting an information saying that 'the material is defined for inhouse production'
secondly if I click the 'Assign Source of Supply', then I am getting an error 'not possible to assign a source of supply'.
The material is a finished material 'FERT' with procurement key 'X' so in MRP an planned order gets generated for converting a PR or a production order.
Note - I was doing this effectively in a differnt client without any proble. I am unable to find what I am missing, please sugest.

Nagaraj Chaganti wrote:
Thank you everyone for the suggestions, The issue is resolved by testing with a new material with tproper master data. Basically the problem occured when some user created additional inforecord for the same P,Org hence there was no automatic source detemination happening.
>
> Bye with regards.
a second info record may explain that AUTOMATIC source determination ddid not work but it does not explain the error messagees you described earlier.

Best practice for distributing/releasing J2EE applications.

Hi All,
We are developing a J2EE application and would like some information on the best
practices to be followed for distributing/releasing J2EE applications, in general.
In particular, the dilemma we have is centered around the generation of stub, skeleton
and additional classes for the application.
Most App. Servers can generate the required classes while deploying the EJBs in the
application i.e. at install time. While some ( BEA Weblogic and IBM Websphere are
two that we are aware of ) allow these classes to be generated before the installation
time and the .ear file containing the additional classes is the one that is uploaded.
For instance, say we have assembled the application "myapp.ear" . There are two ways
in which the classes can be generated. The first is using 'ejbc' ( assume we are
using BEA Weblogic ), which generates the stub, skeleton and additional classes for
the application and returns the file, say, "Deployable_myapp.ear" containing all
the necessary classes and files. This file is the one that is then installed. The
other option is to install the file "myapp.ear" and let the Weblogic App. server
itself, generate the required classes at the installation time.
If the first way, of 'pre-generating' the stubs is followed, does it require us to
separately generate the stubs for each versions of the App. Server that we support
? i.e. if we generate a deployable file having the required classes using the 'ejbc'
of Weblogic Ver5.1, can the same file be installed on Weblogic Ver6.1 or do we
have to generate a separate file?
If the second method, of 'install-time-generation' of stubs is used, what is the
nature/magnitude of the risk that we are taking in terms of the failure of the installation
Any links to useful resources as well as comments/suggestions will be appreciated.
TIA
Regards,
Aasif

Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
detach/attach, script generation, Microsoft Sync framework, and a few others.
EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
backup/maintenance routine in your environment.
As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

Best Practice for Distributing Databases to Customers

I did a little searching and was surprised to not find a best practice document for how to distribute Microsoft SQL Databases. With other database formats, it's common to distribute them as scripts. It seems that feature is rather limited with the built-in
tools Microsoft provides. There appear to be limits to the length of the script. We're looking to distribute a database several GBs in size. We could detach the database or provide a backup, but that has its own disadvantages by limiting what versions
of the SQL Server will accept the database.
What do you recommend and can you point me to some documentation that handles this practice?
Thank you.

Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
detach/attach, script generation, Microsoft Sync framework, and a few others.
EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
backup/maintenance routine in your environment.
As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

Source determination in backend (R/3) for distributed contract i.e. GOA

Similar Messages

Maybe you are looking for