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

Similar Messages

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 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

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

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

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.

Inbound IDOC:Not able to create OBJID while testing basic type HRMD_A07

Hi Friends,
I am trying to test creation of organization data (HRP1000) for inbound idoc via tcode WE19 using basic idoc type HRMD_A07.I am using inbound fm IDOC_INPUT_HRMD.After test data entry,The idoc status is showing as 53 but in the database table HRP1000 objid is blank.It is not creating objid.can any body suggest solution for this.In this case,i want to create objid internally by the system.
Thanks,
Rajesh Kumar
Edited by: rajeshvatsa2005 on Feb 17, 2011 9:03 AM

Hi Rajanidhi,
Thank you for following up!
Perhaps optomizing the choice of forum for the questions could also help somewhat, in addition to following up on them. For example [this one|Forgot username & password; would have enjoyed more knowledgable attention in the NW Admin or Security forum.
Hope that helps in future,
Julius

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

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

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

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.

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

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

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

Hello all,
I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc.
So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
During the development and testing phase in the Sandbox system this works.
However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
I was wondering if there are any ideas why this could have happened?
Oh ... I also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
Well I hope to hear from you.
Regards
Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

Hi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay

Inbound Idoc Testing

Similar Messages

Maybe you are looking for