WE20 PROBLEM

Hi Experts .
I m transfering some data from client 800 to 100 on the same server . I have created rfc destination by sm59. logs log800 , log 100 , port zport. in we20 i have created patnter no log 800 with type ls . in outbound parameters i crated meassage tpye matmas (standard ), idoc matmas05. also i created message synch .
but when i create model view in bd64 with sender log 800 , receiver log 100 mesage matmas . i generate it . andwhen i disribute it i m geeting error" RFC destination for synchronous communication (message type SYNCH) Partner profile LS LOG100 SYNCH does not exist.
Generate partner profile or specify outbound partner profiles for message type SYNCH ".
plz tell me how i can remove this error .

Hi
rajna
your logical system name and rfc destination name should be same so that system can generate some internal communication settings automatically moreover before distributing model view u should generate partner profiles automatically means u have to use BD82 tcode to do this and also check u r model view once again
Thanks & Regards
Nagesh.Paruchuri

Similar Messages

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Error creating outbound parameter in WE20

Hi,
Recently, I tried to create a new partner profile via WE20 of Type B (Bank) in my QA system. The profile got created, however, I could not create outbound parameters for the same. On clicking the '+' symbol to add the outbound parameter, it takes me to 'Telephony' tab. Even after providing some info in the Telephony tab, it doesn't give me a screen where I can enter the outbound parameter details.
I have checked and verified my authorization after comparing it with DEV system and found it to be exactly the same. Infact, I have more authorization in QA than in DEV.
Would someone please help to resolve this issue. Has anyone faced a similar problem before? If yes, how did you resolve it?
Thanks & Regards,
Deoraj Alok.

I had a problem like this years ago.... caused by an inconsitancy but i never could figure out why, i was not able to reproduce it.
to fix it I had to manually remove the entries from EDP12 EDP13 EDP21 EDIPHONE, ... and recreate it from scratch
are you able to create another partner profile or not?

Problems with idoc ORDERS05

Hi experts,
I created a new Z segment for idoc ORDERS05 and it works fine. This idoc is generated whenever a PO is created or modified. But if the PO has locked or deleted items, there is no segment for this items in the IDOC. Should I modify any code or something in SPRO??
Thanks in advance,
Maria

Hi again...
I'm trying to make a copy of the standr FM IDOC_OUTPUT_ORDERS because I think it may be easier to add the segments I need. I have also created in tx. WE41a new operation code ZME10 with my new fm. An in tx. WE20 I have assigned ZME10.
The problem is when I run ME9F i get this error:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
was neither
caught nor passed along using a RAISING clause, in the procedure
"NEW_DYN_PERFORM" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The program "RSNASTED" contains the CALL FUNCTION statement.
The name of the function module to be called is "ZIDOC_OUTPUT_ORDERS".
but "ZIDOC_OUTPUT_ORDERS" cannot be found in its function group.
Any idea ??
thanks in advance !

RFC connection problem

Hello All,
We are setting up communication between R/3 4.7 and SCM 5.0 system for EWM (Extended warehouse management) with RFC connection and using IDocs to transfer data from one box to another box.
IDoc from R/3 to SCM system is working fine, we are able to complete the transactions in SCM system and after successful completion all transaction in SCM it should trigger Idoc for R/3 which is not happening.
It throws error as <b>"An RFC destination could not be specified for the logical system XXXCLNT123"</b>
We have checked SM59 (RFC connection), WE20 (Partner profile), WE21 ( IDoc port connection) it seems fine.
Interesting thing is we are able to get information about stock from R/3 system in SCM system which are correct information.
Can anyone give some idea if we are missing something to check?
Thanks & regards
Arif Mansuri

Hi Team,
We have the same problem , which was mentioned above. Please let us know, which Message type need to be used for sending the stock information to ERP after Delivery completion
The following Process we followed
PO Creation---ERP
Inbound delivery-ERP
Inbound Delivery Process-EWM
WareHouse Task-EWM
Unloading-EWM
WareHouse Task/WareHouse Order Confirmation-EWM
Once the WT/WO is confirmed , Goods receipt status is updated automatically and "Post Processing Framwork (PPF) status shows with RED and error message says."An RFC destination could not be specified for the logical system E6SCLNT900"
Here I have one doubt, We have maintained client names as A0000039 (for EWM,but original client name is SC7CLNT100 ) and E6SCLNT900 ( for ERP , original client name also E6SCLNT900)
Will there be any issue with A0000039?(because we did not maintained as per the original client name ie SC7CLNT100)
Thank you for your help
Thank you

Problem in the formation of communication idoc

Transfering master data from our system to the client system.
After doin all the outbound configurations from BD10 im sending the materials.
ALL the master idoc are created but only 0 communication idoc is created. how can i solve the problem.

Hi,
Since you are transferring the data through ALE, you need to make settings in BD64 (distribution model) and also WE20 paretner profile.
How to maintain:
BD64:
Go to Edit mode and click on button 'Create model view' and fill the popup inputs 'Short text, Technical name, start date and enddate'.
Now click on button 'Add message type' and give 'Model view, Sendor, Receiver and message type'.
These should be same as that of WE20.
Save it and then try once again. now issue will be resolved.
Please reward if useful.
Regards,
Ramesh

Problem in Idoc creation in ME22N

Hi All,
We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
Are any other config settings required to be maintained for this?
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma,
I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
Only settings u have to do is
1>generate partner profiles(WE20)
2>Distribute model view(BD64).
REGARDS,
Nagaraj

Problem with Date in EDI posting

PO created and updated by the EDI 945 from mexico SAP system. Once the EDI is sent,it changes the arrival date of the PO to the ship date. An example is STO 506613882. When created this PO, it had a delivery date of 02-01-08. It was updated by the system to reflect a date of 01-26-08. This creating problem because the receiving sites are on ATP. Any got any idea of Resolving this issue.
Thank you,
Raj

Hi,
How did you create this PO? Was it automatic or manual?
Whatever, if there was no manual intervention in all the process, then you need to check the Inbound Idoc that has created or updated the PO.
Go to the control Record of the Idoc concerned and take the Sender Partner of the Idoc.
Now check the Partner Profile on [WE20]>Inbound Parameters> select the message type (ORDERS for e.g) and then click on details Icon. You can see the Process Code double clicking on which you get the "Function Module" which is responsible for the Integration of this Idoc into SAP.
Now go thru this Func Mod and search for the required field i.e Ship Date filed for example (find-->gloabl search). You can see in the program how the field is mapped to Idoc segment and how it is getting updated.
Hope it helps!!!
Bunni

Performance problem in IDoc receive (DELFOR01)

Hi,
I have serious problems in receive of Idoc Delfor01 (IDOC_INPUT_DELINS). We receive more than 3000 Idoc daily of this type and the process of then during all day....
One of more common error is foreing_lock of VBAK table. This error occurs in the Form beleg_sperren (line 459 from IDOC_INPUT_DELINS) when the process try enqueue one vbeln entrie from VBAK (o think by the high number of Idoc received) and, the process waits a large time trying enqueue the table entry until the error...
When I analyze the IDOC_INPUT_DELINS i see a batch-input for the VA32 transaction (at line 528). I think if call a Bapi instead a Call Transaction have more performance... it´s right?
I would appreciate help with possible solutions to this problem.. Have a better mode to process large amount of these IDoc type? Or have other FM than IDOC_INPUT_DELINS with better performance???
Regards,

Not need immediatly, but a quickly possible... In WE20 if I choose the background program the process will executed* fastly than I choose Imediattly start?
*executed via schedule job of program RBDAPP01.
I stil reading the notes above..

Problem in : File to IDoc

Hi,
   I am working on a file to IDoc scenario.The logical name for the sender system is maintained in the SLD.I am not populating the control record in the mapping.
   When am executing the scenario, the status message in SXMB_MONI is showing request processed but in the outbound status it is showing error and the message displayed is " EDI Partner Profile not found ".
   Can anyone help me out with this.
Thanks and regards,
Pravesh Puria.

Hi,
Transaction :WE20
Choose partner Type : LS
Give partner Number ( give Logical System Name ( Sender System ..check with basis or Bd54 Transaction .if the sender is Business Service ..give XI Logical system)
and Inbound parameter add the Idoc and give the process code and save.
ur problem will solve..
let us know if U need any
regards
Ram

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Problem with call-offs between APO and R/3 system

Hi, gurus.
We have following problem:
APO system receives DELINS idocs. They are processed correctly (status 53). But sometimes the call-offs in R/3 system are not updated. I do not know much about the underlaying process but how can I check where the problem is?
I suppose it can be caused by blocking of particular material or order or whatever in R/3 system when the call-off is being processed. But then the system should give some warning. I need to know where it could be found.
The only workaround at the moment we do is to create copies of DELINS in APO system and let them be processed.by APO and consequently by R/3 system.
Thank you.
Stano Letko

Hi Stano,
When ever IDOC fail you can trigger a workflow to the respective person through Partner profile and message type setting .(we20) as Post processing permitted agent .
Get in touch with techincal person who have idea of IDOC configuration.
Message type : DELINS
Partner number : XXX
Workflow tcode : PPOSE
Manish

Problem with Inbound Idoc

Hi everybody.
I´ve got a problem with an inbound idoc. I've got a standard idoc INOTIF with an extension.
To receive this Idoc from external systema I´ve created a Z FM to process this idoc.
The problem is that when this idoc get to SAP the FM never is executed and the idoc appears with red flag and show me
the next error: No status record was passed to ALE by the application and the idoc is shown with the status 51.
¿¿How can I fix this??
Thanks a lot
Regards

hi
and also give the funtion type is function module in we57 and in BD51 give ur ZFM and give 1 in input.t field.
now you can see ur FM in WE42 under Identification field F4 value.
The FM which is created by you it should be in F4 help list fo field Identification in we42.
and give the Message type and Process code in we20 in inbound parameters.
i am sure this will work .
regards,
Kiran Jagana

Problem with "Confirmation" changes in PO using ORDRSP Idoc

Hi all,
I have an issue when changing "Confirmations" tab in PO.
I configured Output Message Z001 that should be determined when I change values in that tab. That scenario is working fine, but the real change will be done by ORDRSP Idoc. Using that Idoc, change is done in the PO but no output message is determined (condition records are fine). I need to send a Custom Idoc once that change is done so I need to determine the output message.
I searched for an OSS note, as it should work using Idoc process, but I didn't found anything. Does anyone know if it exist?
Thanks in advance for your help.
Regards.
David.

Thanks for your answer Jelena,
The main problem here is that all the flow works fine if I execute if manually:
Change in "Confirmations" tab is done --> output message Z001 is generated --> Custom Idoc Z is created.
Therefore, WE20 is correctly configured and also all the required fields that can be changed in "Confirmations" section.
The problem is that real scenario should modify that values using ORDRSP inbound Idoc (ORDERS05). That Idoc is changing the PO, but that change is not triggering any output message (although the same change did it manually), so custom Idoc Z is not created.
Maybe I didn't explain myself very well in my previous message.
Thanks & Regards,
David.

Problem Unable to convert the sender service to an ALE logical system

Hi to All..
I'm facing a problem in one scenario File to Idoc .. I got this problem
"Unable to convert the sender service to an ALE logical system" in pipeline Call Adapter.
I check this blog but the problem persist . /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Also I have another scenario in other Software Component Version SCW and the Idoc works correctly..
I wonder if I miss something
this the trace
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service Sys_XXX</Trace>
<Trace level="1" type="T">Receiver service Sys_EDV_XXX</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Edited by: Luis Ortiz on Jan 25, 2010 3:37 PM

Hi,
in order to use only one logical system (PI's) in we20 in ECC and not as many as you have sender systems
Regards,
Michal Krawczyk

WE20 PROBLEM

Similar Messages

Maybe you are looking for