Testing Inbound Idocs

Hi All!
I am trying to fix an inbound Idoc program that is erroring in our testing environment with a REALLY big IDoc. I need to move this IDoc to our development environment in order to be able to accurately fix the program.
Is there any way to move an inbound IDoc from one environment to another without manually re-creating it or having to create an outbound IDoc process of some sort?
Help is MUCH appreciated - thanks!
Abby

Try out this
On the source system
Go to WE19 - > IDoc -> Test Inbound IDoc ->Inbound File
Here enter application server path like
/appl/interfaces/MDDC/MLGA01
Also Uncheck the check box Start IDoc inbound processing of file imm.
On the target system
Go to WE16
Give the same application server file name in Directory + File name
In Port give EDIPORT and run it.
This will create an IDoc
Regards
Kesava
Message was edited by:
Kesava Chandra Rao

Similar Messages

System dump whiling testing Inbound IDoc for BOMMAT(Bill of material)

HI Experts,
I m testing Inbound IDoc from T-Code 'we19' using logical system 'BOMMAT' .System is giving a dump with error"Field Symbol has not yet been assigned". while testing t_code 'we02' A IDoc is genreted with warning with status 64 with error 'No filters , No conversion , No version change . Please suggest some solution.
Thanks
Ravinder Singh

Hi,
Check the data in the idoc.
This dump might happen due to numeric field you might have passed the character value. check throughly.
Regards,
Shanmugavel chandrasekaran

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

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

Error in Testing Inbound Idoc PORDCR102

Hi,
I am creating purchase order using message type PORDCR1.
I have done the partner profile entry and Process code is 'BAPI'.
while testing the Inbound Idoc PORDCR102 using WE19.
I am passing the Control Record and the data record Information.
But when I am executing it in forground it is giving me Dump and IDOC remains in status 62.
Error is :-
Access via 'NULL' object reference not possible.
Error analysis
 An exception occurred that is explained in detail below.
 The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
 caught in
 procedure "PROCESS_COMPONENTS" "(FORM)", nor was it propagated by a RAISIN
 clause.
 Since the caller of the procedure could not have anticipated that the
 exception would occur, the current program is terminated.
 The reason for the exception is:
 You attempted to use a 'NULL' object reference (points to 'nothing')
 access a component (variable: "L_ITEM").
 An object reference must point to an object (an instance of a class)
 before it can be used to access components.
 Either the reference was never set or it was set to 'NULL' using the
 CLEAR statement.
I verified the data by creating the Purchase order using BAPI_PO_CREATE1, purchase order is successfully created.
Do Anyone have done a similar testing for message type PORDCR1, please give me your suggestions.
Thanks
Monika.

Hi Shankar,
check whther u r using the correct function module for correct message type.
anyway check the following configurations for an inbound idoc.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
Regards,
Nagaraj

Testing Inbound IDoc via WE19...

Hi,
I am trying to learn IDOCs via WE19.
I just took a sample IDOC from WE02 and tried to test in WE19.
I am trying to understand what do we mean by following:
1) Process Inbound IDOC via file ?
2) Process Inbound IDOC via function module ?
Regards,
Rajesh,

Rajesh,
Go thru this link
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

Testing Inbound Idoc

Hi All,
I want to test the inbound idoc without the help of the other system? Can I test the idoc in this manner?
Please let me know.
Regards,
Ramana

If you know what information is send in which field in that IDOC you can always create an IDOC manually through transaction WE19 and let it run into the SAP system.
Michael

Error while testing Inbound Idoc

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
PL HELP!!!!!!!
The procedure followed by me was,
WE31 created custom segments,
WE30 Created custom basic type,
we81 Custom message type,
se37 function module,
we82,
we57,
bd51,
we42,
bd67,
we20,
Am not able to figure out why exactly is the error message being shown.
please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

Hi friend,
if it is help full please give max reward point.
Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
Two programs enable cross-system reporting:
     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report
IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
53 Application docu posted     =>     41 Application docu created in receiving sys
51 Error: Application docu      =>     39 IDoc in receiving sys. Status repeated
     not posted                         each time RBDSTATE runs.
68 Error: No further processing     =>     40 Application docu not created
ALE Auditing
BDM7          =>     ALE Audit: Statistical Analysis
BDM8          =>     ALE Audit: Sending the Confirmations
RBDSTATE     =>     Run on Receiving System to return Audit Message

Inbound Idoc Testing

Hi All ,
Can anyone pls let me know how to test Inbound Idocs.
I am writing a ZFM to process orders01 idocs coming from the external system. After writing the code, how can i test the same for the IDOC that has to come . I mean to say : Idoc will not be available at the port in real time now (only once the system is up ,the Idoc really come). SO , what is the way to test the program developed for Inbound processing of Idoc of a certain type ?
Thanks,

Hello,
Use WE19, copy any existing Idoc, and then use your FM to test it.
If there isn't any then make an file on the server, which actually will be generated by Outbound processing.
Regards,
Naimesh

Inbound idoc testing via partner profile

i want to test inbound idoc testing via partner profile.
the problem is i its generating idoc no and giving a message like
"idoc no 12453152.. is saved but cannot or shd not be processed".
what does that mean ..
how shd i veiw properties of partner p[rofiles

i am getting thid message from we 19 ..
in that i am creating a sales order...
i am clicking on startinboung button on application tools bar.
this is an information pop up window ..
if i press f1 on that ..
help says that ...may be you cannot process the idoc immediatly...
check for partner profiles

Inbound IDOC File Testing

Hello friends,
Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
Only these are the 4 segments I am going to use.
E1BPACHE09
E1BPACGL09
E1BPACAR09
E1BPACCR09
Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
I am able to test post one document at a time thru WE19.
Thanks for ur help.
Sam.

Did you find the answer for you question?
I am trying to do the same to run a LSMW that load data through FB50 but I don't find how to fill the structures.
Thanks.

Inbound Idoc Testing File Template

Hello friends,
Could any one guide me in preparing the Test file for testing Inbound IDOC (message type: ACC_DOCUMENT) and (basic type: Acc_Document01).
Only these are the 4 segments I am going to use.
E1BPACHE09
E1BPACGL09
E1BPACAR09
E1BPACCR09
Basically I would like to know how to create a template to upload multiple documents during testing and the procedure to upload.
I am able to test post one document at a time thru WE19.
Thanks for ur help.
Sam.

Hi Sam,
Try this, to my knowledge this is only to test if idoc is posted properly or not (to check the configuration), we can only post one Idoc at a time i think...but try this...
am not sure but try this...
Go to WE19-> acc_docume*>control on the data segment and copy it->insert(next to copy in menu bar) the segment at the same level> fill the data and post it ...to see..just try this...
Thanks
Ajay

Inbound IDOC Failing

HI All,
We are upgrading our 4.6C system to ECC6.We have EDI interface.We are sending and receiving IDOCs through Webmethods.
We are testing inbound IDOCs.IDOC (ORDERS03) got generated in webmethods properly, but it got reached ECC6 system with error message 51.
IDOC in ECC6 system didn't created properly.All data segments didn't filled with data.
Can you please tell me, why it got happened?Do we need to change any setting in terms of port defenitions, RFC destinations?
Kindly let me know.It is urgent.
Regards,
Srinivas.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Cost center not checked during the inbound idoc FIDCCP2

Hi all,
Could you please give any input on this strange issue.
I am testing inbound Idoc FIDCCP2 (GLVOR = 'HRP1' ) with tcode WE19 and when I fill cost center with value 'ZZZZZ' the system post the FI document and deosn't check the cost center like in FB01.
With FB01 I have a error message "Coste center 'ZZZZ 'does not exist on 21.08.2014" and cannot post the document.
Thanks.
Farouk.

Try OSS note 114814.
Regards
Waza

Testing of an inbound idoc.

hi experts,
i have to create an inbound interface for processing message order/ordchg.I have a .txt data file .how do i test my inbound interface so that the data in the text file is passed onto the inbound idoc?
Valuable help will be rewarded.
Regards,
Shrita.

Hi shrita sharma
1)Generating Idoc as a flat File on the outbound.
2)Uploading File as IDoc in the Inbound System
1) Send an outbound IDOC data(ORDERS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
Good Luck and Reward me for the same ..!!
Thanks
Ashok

Testing Inbound Idocs

Similar Messages

Maybe you are looking for