Error in we19.

hi all!
i am getting error 51.
with following error msg.
"Error in subroutine read_namtb for structure of infotype."
see this message also.
Check the entry for infotype in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
how can i trace this error.
thanks.
partha.

Hi,
what do you mean with : trace this error ?
if you would like to debug do like this :
- Prepare your transaction
- in the transaction field put /hs
- set a breakpoint to the statement : message
- execute (F8)
good luck
Frédéric

Similar Messages

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

IDoc Issue : Error in WE19 'Recipient port invalid: '

Hello,
I am trying to repost an IDoc using we19. When I click on 'Standard Inbound' Button i get the error : 'Recipient port Invalid:<port name> '.
Replaced the port with a new port name (tRFC port). But i still get the same error. I am not able to get what i am missing.
can somebody help here.
Thanks.

hi Experts
Please Let me know what is going wrong as i have configured the
Port ,Logical System using the sender system details such as assigning the sender system client in sender logical system
i have also configured RFc but it is not a trusted connection
with regards,
msk

Error- No partner profile could be found [Idoc(KU) to File(LS)

Hi Experts,
I am creating Idoc to file scenario i.e KU to LS
I have already created an outbound partner profile using transaction WE20.
SNTPRT- Partner number - 1100024 RCVPRN Partner number - PEVCLNT100
Partner Type- KU RCVPRT Partner type - LS
It is showing below error in We19 :-
Entry in outbound table not found
No partner profile (outbound parameter) could be found using the following key:
/PEVCLNT100/LS//DELINF////
What could be the problem ?
Regards,
Anshul

Hi,
Go thru the following threads...might help you..
Entry in outbound table not found
Re: Outbound Program using ALE/IDOC
Regds,
Pinangshuk.

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

In WE19 getting error Message as Function module missing

Hi Friends,
I need to debug the Inbound function module
so in WE19 i am providing the IDOC number and clicking on the Inbound function module then i am getting pop-up
i am able to select my function module name
and checking the Fore ground processing Radio button
for debugging
I am getting a Warring Message as
Interface or Function module <NAME> is Incorrect
Kindly suggest me
where the mistake might be
and how to correct IT
Thanks in Advance
Ganesh

Hi Ganesh,
I believe you are using a non IDOC function module, that's the reason you are getting that error.
Use the appropriate IDOC function module and then select the Debug check box and it will stop.
If you can provide me the IDOC message then I can help you by giving the correct Function Module.
Thanks,
Mahesh.

Error in number range while testing inbound idoc via we19

hi all,
i have done all configurations but while testing the inbound idoc via we19 i am getting an error 'error in assigning number to idoc'..i checked and found that the number range object for idoc is edidoc in it number interval is defined from 1 to 99
i dont think that anything is wrong with the number object..
Can u tell me how dow i eliminate this error?

Increase Higher limit the reason is when you look at current idoc number ( This idoc number already exists ) ,it will not create new idoc number.
System will get the number from SNRO Based on IDOC Object.
Just look at EDIDC and see the current idoc number.
Simple example :
I have one number - 100 ,it is already exists in database,if i insert same record to the database ,did system will accept ?
Thanks
Seshu

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.

Error in function module for inbound processingwhile testing from we19

hi,
I have developed a custom function module for processing inbound idoc for creating material using bdc...the problem is that when i am trying to test my idoc using we19 and calling my function module in debug mode an error is displayed showing 'interface for function module is incorrect' and also i am unable to see my function module in debugging mode.It is only displaying the error message...
I have given all the parameters necessary (import,export or tables) and found no error in the interface...I think the problem is appearing before my function module is being called....Also on seeing the short dump analysis I have seen that the error is in the form 'Idocs passed to application' which is not a part of the function module developed by me...
I am unable to understand why this error message is being displayed...
Please help me out of this..

ya i know that ..But I wanted to create a simple one..moreover the problem is not with bdc....It is with the function module interface..
Also I want to ask a question that I had to define all the parameters (in the function module ) by data declaration statements in the function group top include..
If i dont do that say the first error is when i write loop at idoc_contrl ..idoc_contrl is not declared by a data statement..So IO had to write a data statement:
Idoc_contrl type table of edidc..I have seen that in other function modules (idoc inbound processing) no such data declaration is done..

ALE WE19 ERROR

I am trying to post a FI document using transaction code we19. Below are the steps that I have performed. The message type is FIDCC2.
SCENARIO 1 - Without entering the business area.
I enter the data into the segments and after checking the partner profiles I click Inbound Function Module /Standard Inbound.
After the IDoc is created I check the status. It says, "Accounting transaction not permitted for posting in FI/CO." I got the data checked from the functional consultant and the data was correct.
Scenario 2 . After entering the business area.
I clicked the Inbound Function module and I checked the status. It said, "Cross-system business area 1000 does not exist."
I guess it is a functional error, because if it was a technical error it would have given errors like, "partner profile not found," etc. Do you have a solution for this?
Regards
Kumar

Hi,
I think you should look into following steps.
Goto TCODE
SALE -> Modelling and Implementing Business Process -> Cross Application Settings -> Global Organization unit -> Cross System Business Areas.
The reason is that if there are 2 systems
System1 having BArea as 100 and System2 is having 200 then in both the system 1000 will be maintain as a Cross-Business Area which will act as a intermidiate Business Area for converting Business Area 100 to 200.

WE19 inbound error

Hello,
I try to send a material idoc inbound via WE19 in my netweaver system.
I can send an idoc via WE 19, but there is the msg that the function module is not allowed or it that there is no function module für
aii_delinf_in.
In WE42 I can configure an "identification" for the process code. My AII Master Guide says that there should be a IDOC_INPUT_DELVRY or an IDOC_INPUT_DESADV1 but there is none.
Do I have to code sth there or where and how can I implement these IDOC_INPUT_* to assign them as an identification in WE42?
Since there is no identification at the moment, everything seems to work (concerning the partner profiles in WE20), but I get this error. How can I fix this? Pls answer, thx.

Does no one know what to do?
Do I have to program this function module?
The right one does not exist in AII, only in XI. But our solution shall be without XI, so I have to create the missing function module by myself. But what do I have to check?
What do I have to do to create a function module?

Error while using Test tool -WE19

Hi All,
When I am trying to use Test tool for IDOC processing ( WE19) in R/3 System for any Basic Type ,for example: PEXR2002 and select the Standard Outbound Processing, I am getting the message as Port does not exist in the table of port descriptions.
Is this error something where port configuration is missing or some standard error.
Please provide your inputs.
Regards
Pragya Dubey

Hello Dubey,
Check it once u r configaration..
Step by Step Procedure..
Create the tRFC port definition
Refer to the following steps to create the tRFC port definition.
1. SAP transaction code: WE21 Type /nwe21 on the SAP input window and press the
Enter key.
2. Highlight Transactional RFC.
3. Click the Port pull-down menu, which is located in the upper left corner of the SAP
screen. Click Create (or press F7).
4. Select the own port name radio button.
5. Type a port name such as ALEport. If you use a port name different from this, update
Table 2 at the beginning of this chapter for future reference.
6. Click the green check icon to continue.
7. Fill in the description field with tRFC port (You are free to write anything you want here).
8. Fill in the RFC destination field with ALESERVER. This must match the name you used on the previous RFC Destination step. If the name you enter here does not exist, the
system will flag an error and you will need to provide an existing RFC destination.
9. Make sure that IDoc record types SAP Release 4.x is selected.
10. Click on save.
Thanks,
Satya Kumar
Reward points if it is useful..

Reg: WE19 - IDOC (time_out error) Urgent

Experts,
   I'm repushing the IDOC using WE19 manually.
   Since there is more than 1 lakh of segments in the idoc , it gives me "Time-limit exceeded" dump.
   Please let me know is there any other way to push the idoc ??? any background schedule...
   any inputs on this will be highly rewarded & appreciated
Rgds
Lakshmiraj

Hi,
Is it inbound or outbound IDOC
Thanks
Naren

Error in Inbound Customer IDOC (WE19)

Hi All
I am creating Inbound Customer IDOC
Message Type : DEBMAS
& FM : IDOC_INPUT_DEBITOR.
But getting error(51) : "No batch input data for screen SAPMF02D 0340".
According to previous threads, I have seen this screen for Mandatory fields but I didnt found any.
Could anyone tell me what mandatory fields to enter in DEBMAS or the Solution for this Error.
Regards.

Hi Nikhil I am getting this error which you got it before but this time I am getting it in LSMW when creating customer master screen."No batch input data for screen SAPMF02D 0340"
what am i supposed to check?
Can u plz send me ur mail ID.

Error while testing Inbound INVOIC with we19

Hello Friends,
I want to test inbound invoic with we19.
I get now the mistake : external sender not avaiable (status 51) (translated from the german : Externer Sender wurde nicht angegeben).
I guess the INVOIC-Idoc ist correct.
Whal could it be?
thanks and best regards

Hi Check the following config
Data Transfer(System Settings for Idoc Interface
Define Conversion of External Item Identification
Basic Settings for Document Transfer
Also check the partner profile and check if you have additional segments for item data. If yes then maintain it Document transfer from external system
Hths
Saj

Error in we19.

Similar Messages

Maybe you are looking for