Problem in we19

hi all....
i 've a problem in we19(test tool to generate idoc).
my receiver port and partner no is not getting generated....
plz tell me the possible methods to hit the receiver port and partner no from the sender...
thanks in advance...

thanks a lot......
i 've tried all the possiblities ...
but still am getting the same error.
is there any specific procedure in creating the receiver port n partner no...?
thanks in advance...

Similar Messages

Problem with WE19 Test tool for idoc process

Hi,
I have a idoc in 51 status. This idoc is used for order creation and its an inbound idoc.
This idoc has around 2000 line items. On checking the status for this idoc, i find that in a particular line item(223) error is showing.
So in WE19, I entered this idoc no. and deleted all the line items below the error line item. Now when I click on 'Standard Inbound', I am getting error mssg 'Receipient port invalid', 'idoc was saved but cannot/ should not be processed'.
How to correct this. After this idoc is processed and generates a sales order, I want to insert the error line item and find the issue.
Please help.
Thanks & Regards,
Hari Om

Hi,
Receipient port invalid You must have taken the IDOC from Production and put it in the development or quality I guess.That is why system gives this error.
To solve this issue Click on edit control record fields that is first line. Change the port for the reciepient for example change it from SAPproduction to SAP development /SAP quality
Incase of further queries please reply
Regards
Mano

Fields display in WE02 but not in WE19

Hi Gurus,
May i ask for a solution regarding IDOC problem in WE19.
I have problem regarding to IDOC . The IDOC is SHP_OBDLV_SAVE_REPLICA. There are some fields in the Customer Master - Sold to Party KATR1,KATR2,KATR6 and RPMKR that should be copied to E1BPEXTC of SHP_OBDLV_SAVE_REPLICA. Thru user exit EXIT_SAPLV50K_007, the data is copied to the IDOC.
If thru WE02 , i am able to see the values but if thru WE19 i cant see the values.
Am i trying to manually input the data but i encountered is error "Output lenght of field FIELD1 in table E1BPEXTC is greater than 132"
Kindly inform me of what should i do. Thanks

Yes. I am able to see the values of fields for segment E1BPEXTC in WE02. for example the values of Field01=01,field02=11,Field03=12 and Field04=9.
But in WE19 , i am only able to see the value of Field01. For others, it's empty. I am trying to insert manually the value by clicking the E1BPEXTC but there is an error that not doesnt allowed more than 132 chars.
Please help.
Thanks
aileen

Port created in Idx1 not reflecting in WE19 (R3 side)

Hii Gurus,
when im doing idoc to file scenario., i have to release the idoc from r3, for that im using tcode we19 testing tool. But the problem is the created receiver port (The port created in IDX1 in pi side) not reflecting R3. I mean I am getting error like " "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS" when i try to do outbound processing.
RFC800 is the port name which i have created in IDX1 and i have already added the metadata to that port using idx2 tcode.
please help experts,
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 26, 2009 7:43 AM
Edited by: Balaji Pichaimuthu on Jul 26, 2009 7:45 AM

Here is my steps,
In R3 system:
1. RFC destination which points the PI with name is PICLNT001.
2. In we21 . created port (PORT800) in this i gave the RFC destination as PICLNT001.
3. WE20 - Partner Profile -- gave the Logical System name of SAP (APOCLNT800) with type LS.
    in outbound parameter
    Gave the Port name as PORT800 (Which i created in R3).. and gave the message type and Basic type..
    and click the Option "Transfer Immediate"
4.IN BD64 created the distribution model.. and gave source and destination logical systems and message type..
after that goto Environment---> Generate partner profile.. In that gave the Receiver Logical system and model view name.
In PI System.
1. RFC destination which points the R3 , name E63CLNT800.
2 .IDX1 , creating a port name ( RFC800 ) and specify the RFC destination (E63CLNT800),
     Logical system is PICLNT001( PI ). and Client is 001.
    (Note: i had used this port when i done file to idoc scenario.. it was worked fine)
Now the problem
In we19 trying to release a port
in Control Record
Receiver side
port               :RFC800
partner NO   :PICLNT001
part. type     :LS
Sender side
Port              : PORT800
partner NO   :APOCLNT800
part. type     :LS
message type cremas04.
outbound processing
The same error : "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS"
Did i missing something here?
Please help me.
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 26, 2009 12:04 PM

ALE idoc (MM)

Hello Gurus!!
I want to know the exact procedure how to post the idoc(ale) in material mapping using transactions BD10, BD91, BD92, BD30, CLD1, CLD2 and MEK3.
Kindly let me know the same and please it would help me if u give the step-by-step implementation.
Thanks and Regards,
Sachin

Outbound steps:
Define Logical System (TCODE: SALE)
Assign client to Logical System (TCODE: SALE)
Maintain RFC Destination (SM59)
Maintain Customer Distribution Model (BD64)
Generate Partner Profiles (WE20) - Here use MATMAS as message type
Distribute Customer Distribution Model (BD64)
Execute Stand-alone program to send
Execute WE05 to view IDoc list
Inbound steps:
Define Logical System
Assign client to Logical System
Generate Partner Profiles
View IDoc list through WE05
Any problem execute WE19 a testing tool for IDoc processing
If you still want more details.. send a mail to me so that i will forward a document to you.
Hope u know that program to run to tranfer material detls

Problem in idoc to file scenario

hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan

>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

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

Idoc ERROR IN WE19

Hi SAP gurus,
i had a problem in IDOC..i am using the message type CREMAS.CREMAS03
I designed the IDOC-XI-JDBC scenario. Using BD14 i posted some idocs to XI. in sender side r3, idocs is in green color, i received the idoc in XI also. its not there in sm58 of XI .. its is there in we02.. its shows red color i used we19 to do something.it was not happening.. But in SXMB_MONI.. i am unable to see the idoc..what was the error.. How to solve this
please send you ideas ASAP.
regards
kumar

hi Kumar,
WE 19 is used to send the test data ..however, in ur case it seems the ALE settings are not done on XI and R/3 side.Just check if u have done all the f following steps on both ends.
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,
Ashwin M
Reward if helpful

Problem in IDoc XML Port Configuration

Hi All,
I'm trying the XML port scenario as per the blog /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
The problem is the output XML file contains all the IDocs, not the exact number what we specify in the report RSEOUT00. For example if I specify 5 as Max No.Of IDocs for that report, the output file should have only 5 IDocs and not all which are waiting in the ALE layer. Is that correct? Or am I missing any configuration?
Thanks,
Joe.

Hi Ravi,
I've used the option EDI_PATH_CREATE_DATE_TIME for the filename (Function Module Description). So it should create new files for every execution. Correct?
Actually, I had given the Max IDocs no to 3 (scheduled every hour) and executed 7 Idocs from WE19 expecting 2 files and 1 IDoc in the ALE Queue. But all 7 of them were written to the file.
Thanks,
Joe.

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

IDoc to Fie Scenario Problem In PI

Hi Experts,
i am doing scenario like IDoc to file , i have created evrthing configurations all and all.
i trigger IDoc on r3 system using T-code we19, it showing sucess on r3 sytem. i am checking IDOc monitoring using t-code we05 to showing status 03. but the message not coming to PI system, what is problem it may be, please guide me
regards,
alekhya reddy.

Hi,
The Following are the Possible checks
1) Check in R/3 side SMQ1 & SMQ2
2) Check in R/3 side SM58
In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
If the entry is available then select it and press F6, to push it manually.
This happens normally if IDOC stuck up in queues.
regards,
ganesh.

Problem in processing incoming IDOC

Hi All,
I have a problem while processing Incoming IDOC in the system.
While I try to process and FI IDOC (without purchase order) in the system, by giving the appropriate GL account and cost centre where the document should get posted to (in transaction WE19), I find that the system creates the IDOC successfully with status 53. However, it creates a parked document in the system for the vendor.
When I try to post the document through transaction FBV0, the system asks for a cost centre. Can you please clarify, why the system is asking for a cost object though it is given in WE19 transaction. Ideally while processing the IDOC the system should post the document directly as it has all the relevant details in the IDOC right?
(Just for info, I have given the GL account details in segment E1EDP19 with qualifier 002 and the cost centre in segment E1EDP30 with qualifier 045)
Expecting your help in this regard.
Regards
Nagarajan N

Hi
You can use WE19 to debug the Idoc FM.
Check this link if it is helpful:
Debugging Idocs
Regards
Neha

Idoc with error message when coming from middleware but not in we19

Hi Experts
I am facing a very strange issue !
I have a Z - Idoc type and corresponding inbound function module for creating schedule lines i.e. doing something what me38 does.
When my middleware i.e. Mercator Websphere is sending the idocs, they fail with the error message in the status record as
Field EKET-MENGE (19) does not exist in the screen SAPMM06E 1117.
But when I try processing the same idoc using we19, the scheduling lines are created and the schedule agreement is changed.
Is there any difference between we19 and when idocs come from the middleware ?
Points would be rewareded if useful answers received.
Regards
Shubhankar

Well i think that the problem is with your BDC. there is an option to use standard size in BDC. I think your table control falls short of 19 rows in your program. Please see the thread below and incorporate the same changes in your BDC. I think u might need to record the BDC again.
Re: BDC tabel control for QE01
DATA OPT TYPE CTU_PARAMS.
OPT-DEFSIZE = 'X'.
CALL TRANSACTION 'FB01' USING ITAB OPTIONS FROM OPT.

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

Problem with IDOC TO FILE Scenario

Hi Experts,
I am doing IDOC TO FILE Scenario.
I have done all the configuration.I have cretaed RFC,PORT,LS and Partner profile at both R/3 and
XI Side.
when I am trying to generate IDOC using we19 and I put the r/3 port,partner in sender and XI
port and partner in receiver it gives me error as "Port 'SAPCU6_100' does not exist in the table
of port descriptions.
Please help me.....
Regards

HI Saras,
Please go through the below weblog which has all the stpes which is required for ur scenario...I think screen by screen help u to debug ur problem and it will help u to find out the msitake which u have made.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

Problem in we19

Similar Messages

Maybe you are looking for