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

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.
<b>Sender</b>
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.
<b>Receiver:</b>
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

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

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 trigger Idoc?

Hi,
I did all design and configuration steps and ALE configuration steps for Idoc to file scenario. Can any one tell me how to put idoc that this scenario should work??

Hi Pavani,
WE19 -> u can enter either basic type or message type.
click on create
go to menu object->edit control record
there give the receiver system paramters and source system parameters
after that double click on idoc segments, window opens with all the fields, give data and click on Test Idoc outbound processing.
check the status in we02.
Regards,
Ravi.

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 convert IDOC to flat file in XI

Hello SDNers
I have a scenario IDOC --> XI --> Flat file. My question is how to conver IDOC to flat file. At least there are two ways to do that:
1) Define a flat structure in PI that reflects the IDOC structure, then using content conversion to convert the flat structure to flat file in hte receiver communication channel.
2) There is a [document |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a] talking about using a generic ABAP mapping to map any IDOC to flat file.
For the option 1, I don't want that way, because I would need to define a flat structure in PI for each IDOC which is too much effort. (I would have dozens of IDOC scenarios)
The second one is very attractive. However the document is not complete to follow. Basically it does not explain how the inbound flat structure looks like. I guess the generic ABAP mapping is used to map any IDOC_XML structure to a flat structure, then in the file receiver communication channel to convert the flat structure to flat file format. But the document does not mention how the flat structure looks like. Has somebody tried this scenario? If yes, can you please let me know the steps to do in ESR (IR) and ID? Basically what structure the IDOC_XML should be mapped to using the generic ABAP mapping class?
Or somebody has other ideas on how to convert IDOC to flat file?
Thank you so much
Eric

> 1) You are saying that for Java mapping and abap mapping, the target data type (messag type) is just a dummy one, the real (XML) message the receiver will recieve is the one (stream) produced by the java or abap mapping. Is that correct?
Definitely yes!
>
> 2) For the abap mapping option, I would define a dummy target data type. Do I need to do any content conversion in the receiver adapter (communication channel)?
None wat so ever.The output of your Java Mapping will be the Native Idoc Format.
>
> 3) I tried with a dummy target data type as mentioned in my second post, can you see any clue in the error message what is wrong?
Dats one thing I cant help much. Just make sure that the ABAP report is valid and take the help of a ABAP'er to debug what is going wrong. Not much of a ABAP guy, can read ABAP code, but cant write one myself
Try to test the program standalone to see how it works. Maybe take some Idoc XML file as input and then dump the output to a .txt file and so on.
Regards
Bhavesh
PS : All this is from what I have read of this guide. I have not convert Idoc XML to Native Idoc but have used this guide to convert Native Idoc to Idoc XML .

How to edit Idoc data in inbound processing

Moved to correct forum by moderator
Hi All,
How to edit idoc data in inbound processing ? We have a custom FM in inbound scenario and requirement is to update a value in idoc, this value comes after certain processing in custom FM.
I tried editing it through
EDI_DOCUMENT_OPEN_FOR_EDIT
EDI_CHANGE_DATA_SEGMENTS
EDI_DOCUMENT_CLOSE_EDIT
but there is problem in this approach. By this procedure two idocs are created in system, one with original data and one with modified data. We want only one with modified data.
We do not want any direct database table updates.
Please provide appropriate solution.
Note : We are not changing status record. Please do not post replies related to status change
Edited by: Matt on Nov 19, 2008 2:24 PM

Hi,
You can edit the idoc by doing the following steps:-
1. Goto WE02 transaction and give the IDOC number and execute
2. Once the required IDOC gets retrieved then double on the text pad icon beside the segment which you wanted to change.
3. Select the Data Record at the top and click Display <-> Change option, which will enable you to change the data in that segment.
4. After doing the step 3 then click the save button to save your changes.
5. Then system will generate a new idoc number to store the actual data and your current idoc will hold the new data and the idoc will be in 69 status.
6. Execute the Program RC1_IDOC_SET_STATUS by giving your idoc number and status as 69 and new status 64 and remove the test flag
7. Then the IDOC will be in 64 status and you can reprocess the idoc with the help of the program RBDAPP01 by giving the idoc number.
The above is the entire process for editing the error idoc and reprocessing it again.
I hope I am clear and you understood the entire flow of editing and reprocessing an idoc.
Thanks,
Mahesh.

How to debug IDoc and waht about WE19

hi experts how to debug idocs waht is we19 and perpose

We19 is Testing Inbound IDOC and you can debugging from we19 Transaction
Outbound IDOC Debugging :
Example of Invoice :
Set ur Break point at your code
now come to VF02 Transaction and use invoice number.
click on enter
GOTO->HEADER->OUTPUT
Give the output type and print medium should be 6(EDI) or A( ALE)
Click on Further data and select->select send with periodically scheduled job and save it.
Now Come to SE38 and use RSNAST00
Output Application : V3
Object key - Invoice Number ( 10 digit)
Output type - RD00( SAP Standard)
Transmission medium = 6(EDI) ,A(ALE)
Now it will stop at your code.
Reward Points if it is helpful
Thanks
Seshu

Unable to Test Idoc to File scenario

Hi All,
I am doing Idoc to file scenario.But dont know how to test this scenario.
I have done all the configuration in Backend and XIServer system.
Please help me out.
Thanks in Advance.
Regards,
Vikas

HI
Chech that these steps have been done
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.
One these are done
1) U can trigger the the IDOC by scheduled job in BD87 immediately after the document is saved in R/3
2) Using transactions like bd10 and bd12 u can trigger IDOC for master data
3) While creating the partner profile there is a option trigger immediately . By enabling this option the idoc gets triggered.
4) Using the transaction WE19 u can trigger the IDOC mannually
Regards
Santhosh

How to test a simple PL SQL function from another PL SQL script

Hi,
I have created a function. Now i need to test that whether it is returning the correct values or not.
For that, i have written anothe pl sql script and trying to call this function. Im passing all the IN parameters in that function. I assume here that OUT parameters will provide me the result. Im trying to display the OUT parameter one by one to see my result.
I'm using toad as sql client here connected with oracle.
pl sql script:-
DECLARE
BEGIN
     DBMS_OUTPUT.PUT_LINE('$$$$$$$ VINOD KUMAR NAIR $$$$$$$');
     FETCH_ORDER_PRODUCT_DATA(320171302, 1006, 6999,
ODNumber OUT VARCHAR2, Line_Number OUT VARCHAR2,
ServiceID OUT VARCHAR2, BilltoNumber OUT VARCHAR2,
AnnualPrice OUT NUMBER, CoverageCode OUT VARCHAR2)
DBMS_OUTPUT.PUT_LINE('HERE IS THE RESULT ' | ODNumber );
DBMS_OUTPUT.PUT_LINE('HERE IS THE RESULT ' | Line_Number );
DBMS_OUTPUT.PUT_LINE('HERE IS THE RESULT ' | ServiceID );
DBMS_OUTPUT.PUT_LINE('HERE IS THE RESULT ' | BilltoNumber );
DBMS_OUTPUT.PUT_LINE('HERE IS THE RESULT ' | AnnualPrice );
DBMS_OUTPUT.PUT_LINE('HERE IS THE RESULT ' | CoverageCode );
END;
Function:-
Program Name : SPOT_Order_Product_Data_For_CFS.sql
Description : Function to Validate parameters from CFS
By : Vinod Kumar
Date : 08/19/2011
Modification History
By When TAR Description
CREATE OR REPLACE FUNCTION FETCH_ORDER_PRODUCT_DATA(orderNumber IN VARCHAR2, customerNumber IN VARCHAR2,
productLine IN VARCHAR2, ODNumber OUT VARCHAR2,
Line_Number OUT VARCHAR2, ServiceID OUT VARCHAR2,
BilltoNumber OUT VARCHAR2, AnnualPrice OUT NUMBER,
CoverageCode OUT VARCHAR2)
RETURN VARCHAR2 IS
lv_err_msg VARCHAR2(100) := '';
lv_bucket_id VARCHAR2(14);
lv_bill_number VARCHAR2(30);
lv_anual_price NUMBER;
lv_coverage_code VARCHAR2(8);
lv_quote_num NUMBER(10) := NULL;
lv_line_num NUMBER(5) := 0;
lv_customer_number VARCHAR2(30) := customerNumber;
lv_product_id VARCHAR2(14) := productLine;
lv_count_quote NUMBER := 0;
lv_quote_status VARCHAR2(5);
lv_quote_version NUMBER(2):=0;
BEGIN
IF INSTR(orderNumber, '-') = 0 THEN
lv_quote_num := orderNumber;
ELSE
lv_quote_num := SPT_Delimiter(orderNumber, 1, '-');
lv_line_num := SPT_Delimiter(orderNumber, 2, '-');
END IF;
--Check status of the quote COM, APP
SELECT COUNT(*) INTO lv_count_quote FROM sot_order_header WHERE ORDER_NUMBER=lv_quote_num
AND ORDER_STATUS IN ('APP', 'COM') AND CUSTOMER_NUMBER = lv_customer_number;
IF lv_count_quote = 0 THEN
lv_err_msg := 'Invalid Order number';
RETURN lv_err_msg;
END IF;
-- Fetch the latest version on SPOT quote
SELECT MAX(VERSION_NUMBER) INTO lv_quote_version FROM SPT_QUOTE_HEADER WHERE QUOTE_NUMBER = lv_quote_num
AND CUSTOMER_NUMBER = lv_customer_number;
-- If quote is valid fetch the data in OUT parameters
IF lv_line_num = 0 THEN
BEGIN
SELECT a.CUSTOMER_BILLTO_NUMBER,
b.LINE_NUMBER, b.BUCKET_ID,
b.ANNUAL_REF_RATE_USD, b.COVERAGE_CODE
INTO lv_bill_number,lv_line_num,lv_bucket_id,lv_anual_price,lv_coverage_code
FROM SPT_QUOTE_HEADER a, SPT_QUOTE_LINE b
WHERE a.QUOTE_NUMBER = lv_quote_num
AND a.CUSTOMER_NUMBER = lv_customer_number
AND a.VERSION_NUMBER = lv_quote_version
AND a.QUOTE_NUMBER = b.QUOTE_NUMBER
AND a.VERSION_NUMBER = b.VERSION_NUMBER
AND b.PRODUCT_ID = lv_product_id;
ODNumber := lv_quote_num;
BilltoNumber := lv_bill_number;
Line_Number := lv_line_num;
ServiceID := lv_bucket_id;
AnnualPrice := lv_anual_price;
CoverageCode := lv_coverage_code;
RETURN '';
EXCEPTION WHEN OTHERS THEN
lv_err_msg := 'Multiple PIDs existing in the SPOT order, please provide the SPOT order + line number as input data';
RETURN lv_err_msg;
END;
ELSE
BEGIN
SELECT a.CUSTOMER_BILLTO_NUMBER,
b.BUCKET_ID, b.ANNUAL_REF_RATE_USD,
b.COVERAGE_CODE
INTO lv_bill_number,lv_bucket_id,lv_anual_price,lv_coverage_code
FROM SPT_QUOTE_HEADER a, SPT_QUOTE_LINE b
WHERE a.QUOTE_NUMBER = lv_quote_num
AND a.CUSTOMER_NUMBER = lv_customer_number
AND a.VERSION_NUMBER = lv_quote_version
AND a.QUOTE_NUMBER = b.QUOTE_NUMBER
AND a.VERSION_NUMBER = b.VERSION_NUMBER
AND b.PRODUCT_ID = lv_product_id
AND b.LINE_NUMBER = lv_line_num;
ODNumber := lv_quote_num;
BilltoNumber := lv_bill_number;
Line_Number := lv_line_num;
ServiceID := lv_bucket_id;
AnnualPrice := lv_anual_price;
CoverageCode := lv_coverage_code;
RETURN '';
EXCEPTION WHEN OTHERS THEN
          lv_err_msg := 'Multiple SPOT lines exist with same parameter';
          RETURN lv_err_msg;
END;
END IF;
EXCEPTION
WHEN OTHERS THEN
lv_err_msg := '@@@ EXCEPTION THROWN @@@ '|| SUBSTR(SQLERRM,1,120);
RETURN lv_err_msg ;
END;
Don't look at the function, it might have errors but my primary concern is how to test this function. Once I start doing its testing then only i can understand any bugs(if any).
My pl sql is not so good. Im still learning. I don't understand IN and OUT parameters are.
I just know that IN parameters r those whick we pass in to the function wen we call it and OUT parameters are those through which we get the result.
Thanks in advance
Vinod Kumar Nair

20100511 wrote:
I wondered how I could test the output of the function from within TOAD?I usually create the following function in my developer schema:
create or replace function BoolToChar( b boolean ) return varchar2 is
begin
if b then
    return( 'TRUE' );
else
    return( 'FALSE' );
end if;
end;To test a function like yours, the following will do in SQL*Plus/TOAD/etc:
begin
DBMS_OUTPUT.put_line(
    BoolToChar( XCCC_PO_APPROVALLIST_S1.does_cpa_exist(1017934) )
end;
I'm probably doing 101 things wrong here, but thought I'd ask anyway and risk being shouted at.Shout at? You reckon? I thought people risked being beaten with a lead pipe, or pelted with beer cans and stale pretzels - which makes being shouted at a really safe and viable alternative. {noformat};-){noformat}

How to test the migrated workflows in SharePoint 2013

Hi, we are migrated the portal from SharePoint (Moss) 2007 to SharePoint 2013 using Doc Ave tool.
Now my concern is how to test all (OOTB and SharePoint Designer) workflows are working properly in SharePoint 2013.
How to approach? Any ideas/help will be appreciated.

Hi Ashok,
Have the business users that use them or the folks that created them test them in the DEV environment prior to the PRD migration...
-Ivan

How to test domain controller on upgraded Win Server 2008 R2

The windows team recently upgraded the development environment for the domain controller from 2003 to Windows 2008 R2 and I am to test the Idm functionality on this upgraded version. Our current configuration is that the DC and Idm gateway runs on different machines. To test this new DC, i want to install the idm gateway on that server and run some onboarding and termination test cases just to make sure if the AD connection is working on the upgraded DC. But i am getting ’Input/output error’ when i try to install the service and from the documentation it says 'The most common cause of this is that you do not have rights to work with this service.'. The server admin tried installing the gateway with his id as well and it failed. He tested installing in on the 2003 version of DC and it worked, so its not a matter of permission (i think..)...
Does anyone have any better idea on how to test an upgrade of a DC from version 2003 to 2008 R2? Any help in this matter is appreciated. We are running Idm 8.1 on a Windows platform and an upgrade to OW 8.1.1. Patch 2 is also in the works..
Thanks in advance.

I may have found a workaround. Can you try to change the "compatibility mode" in 2008 R2 to "Windows XP SP3" and see if it will install?
Admittedly I have not done this myself so I'm not entirely sure where or how it's done, but I have confirmation it resolves the issue from others who have faced it.

How to test the payload in XI

Hi all,
could please explain how to test the payload in xi and with steps.
Thanks in advance,
Radhika

Hi Radhika,
You can test in three ways.
1.) In message mapping directly give the relevant data and then execute. Here you can test whether the mapping is correct or not.
2.) In Integrstion Directory after completing and activating the Configuration, in tool you can find the Test Configuration tab. There you can give the sender and receiver details along with payload. Here you can test whether the Configuration is correct or not.
3.) In RWB in COmponent monitoring. Select the Integration Engine Monitoring. Here give the sender and receiver details, Interface name, name space, Quality of service.
Now give user name and pass word.
Paste the payload from massage mapping and then press test tab. Here yoyu can directly send the message from XI server to the receiver system.
Ok,
Jeevan

How to test the rule if multiline container is passing to the task?

Hi Experts,
                  I am working on leave workflow. I have to get the approvers based on no of days of leave and leave type. I am getting these details in ITEMS_TAB internal table. I am passing this table to a rule. Now my problem is when I tried to simulate the rule I am not getting any input screen to enter the data.
ITEMS_TAB is an internal table type of   "PTREQ_ITEMS_WF_TAB_FLAT".
In the rule I have created a container by selecting the radiobutton "ABAP Dict. Data Type" and entered the above reference parameter is it right way?
Is it possible to test the rule independently if I use multiline container as import parameter in my rule? If so can anybody please tell me how to test the rule?
Thank You.
Srija.

Hi Pavan,
                 Thank you.
                 To copy the values I am not getting any input screen to input the values. I observed one thing that the type that I am referring in the Rule is a deep structure. Is this is the reason that I am not getting the input screen to enter the values?
I tested by creating aother rule by taking a field for that rule I am getting the input screen to simulate the Rule.
Can you please suggest if the rule will not work then what I have to do? without the rule how can I get the agents?
Thank you.
Srija

How to Test IDOC WPUUMS01

Similar Messages

Maybe you are looking for