Quick Checkin or Alternate to Testing iDoc

Hello, I am building some admin pages that will reside within Content Server, right now my process is to develop the pages locally then check into CS, but each time I make a change I need to check out and check in this takes tooo long, is there a faster way to Checkin/Update the file in the CS?
Also is there another tool that I can test iDoc in? It would be nice if there was a extension to Dreamweaver or something similar where I can test iDoc without having to check a file into CS.
Ideally I would love to develop a HCSP in say Dreamweaver, it can contain iDoc etc.. and I can do a preview and see the out put. Then when I am staified then go Check into CS.
Thank you...

I once found a tool that seemed nice, althought never got to try it out.
It´s an interface to develop IDoC.
http://contentoncontentmanagement.com/2007/11/07/idoc-developer-interface-for-stellent-oracle-content-server/idoc-developer-interface/?PHPSESSID=07a861a3186c3e1687065e4d5e348f9f
Regards

Similar Messages

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error: 403 Forbidden
 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
Sender
Service : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
Receiver:
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

Test IDOC inbound processing in WE19

Hello,
I want to test an inbound processing for an IDOC in WE19. I don't have any message so i enter 'via message type' in the initial screen.
Then i fill the segments/fields of the presented segments that i think are necessary and also some data in the 'Edit control record fields'.
But when i click on button 'Standard inbound' i receive the error message 'Initial recipient partner type'. Please note I don't fill any parameter in the control fields for receiver, but even if I enter a value in 'partner type' for receiver I got the same error. If I need to fill this parameter I don't know what should it contains.
Does anyone have an idea about what could be the reason of this error ?
Thanks is advance,
Paulo Sousa

Hello Paulo
Recently I implemented an ALE scenario where the sending and receiving logical system are the same.
Purchase orders are sent to SAP-XI which returns the IDoc to the same logical system als sales order IDoc.
Thus, our logical system has the ORDERS message type as outbound and inbound parameter. SAP-XI is the other receiving and sending logical system.
The easies way is the "Copy&Paste" approach. Look into your system for existing inbound IDocs and compare their control record with the one of your test IDoc.
Regards
Uwe

Test idoc SALESORDER_CREATEFROMDAT201

i have run this test idoc as inbound idoc using we-19 transaction(test tool for idoc).. when im filling the data into the segments it is asking to enter shipt-to-party or sold-to-party details..but i cannot find these fields in any of the segments..so can any one solve this...can i know what are the mandatory segments in this idoc.
BASIC TYPE : SALESORDER_CREATEFROMDAT201
MESSAGE TYPE : SALESORDER_CREATEFROMDAT2

Hi,
I checked idoc definition in WE30 and could not find any segment defined as a mandatory segment.
Which function module are you using to process the idoc using WE19 test transaction?
KR Jaideep,

ABAP Mapping - Testing - IDoc - Trouble

Hi Friends,
There is one ABAP Mapping used in our system. The outbound interface is based on one message in external definition and inbound interface is IDoc.
When I try to test this mapping in our PI System using the transaction "SXI_MAPPING_TEST", in the initial screen/input screen in F4 help for the Sender Interface selection, our outbound interface is not displayed. In the Receiver Interface also, it is not display the IDoc.
What could be the problem ? How to test our Z class in this case with the input XML.
Could you please help me?
Kind regards
Jegathees P.

Hi,
don't use SXI_MAPPING_TEST
use my report which is much better
XI/PI: Easy ABAP mapping tests - no more SXI_MAPPING_TEST
BTW
there is no need to use any HTTP client nor anything to test ABAP mapping - just my report
Regards,
Michal Krawczyk

How to test IDOC in mass test

Hey,
created an IDOC with own function module.
Now I would like to test this with some hundreds IDOCs.
How to do this? I tried the we19 but you can only give static
entries there, but from payload my function module tooks data for
inserting them as key field into the database. Is there a way to fill
the fields different?
This is an inbound IDOC so it is even possible to test them from
R/3 System itself? Using the standard outbound processing in we19
will sent them, but I couldn't see in we02 that they arrived.
So my developing system is eg. S4S. From this I want to send my IDOC
to S4S. So I create an profile in we02 where inbound and outbound include
my IDOC. So could this work?
thx
chris
Edited by: Christian Riekenberg on Aug 27, 2008 3:17 PM

Hello,
Try posting the IDocs using the Standard SAP Report RBDAPP01. Here you can use different Selection Criteria based on Message Type or you can supply more than 1 IDoc to Test your Function Module.
Hope it was helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

Testing IDOC to File Scenario

Hello All -
I have configured the IDOC to the cXML XSD using the IDOC ORDERS.ORDERS05.
Can anyone suggest me how to test the scenario? How do i create the purchase order in R/3 and push it to XI to generate the cXML?
Thanks,
Tirumal

Alright.
I tried to test the scenario using WE19 after verifying all the RFC destinations on the XI as well as R/3 system.
I chose an existing IDOC and changed the PORT to point to the one that i created.
Now i get an error saying that IDOC is saved but cannot or should not be sent.
Any ideas why i am getting this message. I suspect there is a problem in the Sender and Receiver information.
This is the sender port information for the IDOC:
Port: SAPD01 - Sap r/3 System
Partner No: R3IDES
Part. Type: LS
This is the Receiver port information for the IDOC:
Port : SAPXI - port created in R/3 System
Partner No: Partner created in R/3 for XI while configuring partner profiles.
Part. Type: LI
Any idea why i am getting the error message?
Thanks,
Tirumal

How to configure, push and test Idoc from XI to R/3

Assuming mapping between imported Idoc and some file structure is fine ,I have to configure XI and R/3 for pushing Idocs from Xi to r/3. I have to make sure they talk.
-I have done this long time ago for pushing Idocs from R/3 to XI but I wonder if it is same procedure or it is different ?
-Can someone tell me - how to configure both for this purpose partner profiles , logical systems etc ?
-And also after configurations , how I can check if Idocs is received from Xi and the entire process is successful?
-does it make difference the type of Idocs during the configurations?
-Are the test for success same for all type Idocs?
Thanks all !
Jon

Here are the steps:
===========================
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
Additional References
Ale Configuration for pushing Idocs form SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Test IDOC to File scenario

Hey guys
i m doing a IDOC to File scenario and am stuck at testing it.i went in we19 but dont know how should i test my scenario there.
any idea how should i test my scenario
thanx
ahmad

Hi Ahmad,
IDOC to File
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
Regards..
Ramesh.

How to Test IDOC WPUUMS01

Hi All,
I've created a sample idoc file of type WPUUMS01 to upload to IS Retail. I just don't know where to test. I was using WE19, test tool for IDOC processing but Im having a hard time figuring out the errors in my IDOC since it automatically overwrites my file.
Any suggestions on how to test or how to use WE19?
thanks so much.
Kenny

Hi Kenny,
In WE19:-
1.     Select the radio button Basic Typ and enter WPUUMS01
2.     Execute
3.     You will get a template Idoc.
4.     Read the file and input the data manually to the Idoc. Double click the segment name, the fields will be displayed and you can enter the data. Be carefully and enter the data in the correct segments and in correct order. The values which are not present should not be entered. Enter data relevant for one Idoc only.
This way you will populate one Idoc and then you can test.
Hope this is helpful.
Regards,
Sameena

Testing IDOC basic type DELVRY03

Hi,
Can anyone tell me how can i test DELVRY03 idoc for ASN. The Idoc is not being triggered from any document as the data is coming from external system to the Ztable and I don't know how IDOC should be triggered.
Function module is Z_ZZ_IDOC_OUTPUT_DELVRY.
Message Type DESADV.
Can anyone tell me in this scenario until the desicion is made for triggering option, can i test the IDOC somehow.
Regards
Rinku

Hi Rinku,
Could you please clear about your requirement?
If you want to re-test a idoc, use tcode WE19. Input idoc number and execute. Then in the next screen click on the "inbound function module" button, enter the inbound function module and select the radio button process in foreground.
Thnaks & Regards
Vijayanand

Testing IDOC from the sender side

The scenario is IDOC - File.
ALE configuration steps are done from R3 end
in XI, I hav created Port, RFC destination
IR, ID activated succesfully
I have to send an IDOC and test the scenario (DEBMAS) and create and change sold to party, ship to party details as test
Please suggest me the steps I need to perform to test my scenario
regards,
Nikhil.

Hi nikhil,
let me try for u...
U have to trigger DEBMAS from R/3...
There are two ways u can trigger the IDocs
1st way
1)Go to transaction we19 for triggering the idocs
2)Under basic type give DE* and press F4 , u will get all the basic type IDOcs that start with DE.Now select the Idoc DEBMAS(u will definitely find it)
Now execute/F8.
After executing choose option Standard outbound processing option then click OK button.The idoc will be sent to the integration server .U will see an pop-up showing that IDoc is sent successfully for outbound processing.
2nd Way
USING EXTING IDOCS:
Go to transaction we02/we05 to see any existing Idocs for DEBMAS.Copy any one of the Idoc number
Now go to transaction WE19 and choose Existing Idoc option.GIve the Idoc No u have copied.After executing choose option Standard outbound processing option then click OK button.The idoc will be sent to the integration server .U will see an pop-up showing that IDoc is sent successfully for outbound processing.
hope ...it will help u......
Regards
BILL
***reward if it helps u

Dump while testing Idoc from WE19-OBJECTS_OBJREF_NOT_ASSIGNED

Hi Experts,
I am trying to Post inbound PO idoc from we19 tcode.
MessageType:PORDCR1
Idoctype:PORDCR102
FM:BAPI_IDOC_INPUT1
while testing this Idoc it is going dump.
Runtime Errors     :    OBJECTS_OBJREF_NOT_ASSIGNED
Short text            :    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 RAISING
     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.
Could you plz suggest how to resolve this issue.
regards,
Bhuvan.

Hi,
Please implement the OSS Note 1409498 (Relavent to your problem).
I am sure it will resolve your issue.
If not solving your than You can serch for relavent SAP note on SAP serivce market place.
Regards,
Lokesh.
Edited by: Lokesh Tarey on Apr 15, 2010 2:31 PM
Edited by: Lokesh Tarey on Apr 15, 2010 2:33 PM

How to generate Outbound Test IDOC ?

I have the sample IDOC receiver application running and registered with the SAP test system, but now I am trying to find out how to create an IDOC and send it from the SAP system to my test application.
(We are using the test system provided by SAP and I do not have any SAP knowledge)
Can anyone help ?

Hi Andrew,
you can use transaction WE19 for sending IDocs to other systems, for more information see http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/frameset.htm. We alos published a paper a on http://download.microsoft.com/download/5/7/f/57f1490e-8a8d-497b-bbae-ec2a44b3799f/CollaborationBrief.pdf which discusses how to setup the SAP system for IDoc processing, the topic of the paper is different but the steps in SAP should be the same.
- Juergen

Manual Test Script to test iDoc in SD

Hi all
Can you please guide me as to how i should write a manual test script in SD to execute a test for iDocs.
Regards
Hema

Hi,
As far as I know, we can’t change the recorded scripts in the MTM.
I suggest that you could have two configurations for that test case, then it will has two test points, one is used for current test, another is used to preproduction test.
If you just want to achieve that requirement in a test point, you may add the parameter to the test case (URL) and base on that data to redirect to specify website and do test, then you could change the parameter value to let it redirect to other URL to
do test.
On the other hand, you could generate the Coded UI test base on that recording, then modify the code. After that you could link the test method to test case and do automatically test.
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Quick Checkin or Alternate to Testing iDoc

Similar Messages

Maybe you are looking for