Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to test inbound idoc in WE19

Former Member
0 Kudos

Hi Friends,

I have to update few delivery items data for my scenario. The sender is a non sap system.

I have found :

basic type : delvry05

msg type : desadv

process code : dels

Under logical system

===============

Partner profile: SNCF100

TYPE : LS

added my message type DESADV in inbound parameters.

Now I want to check if I can update my item data fields thru this basic type or not.

But when I do a testing thru WE19 it gives me error.

So how to test it with WE19.

What information do i need to enter in Control record

for SENDER and RECEIVER?

kindly guide.

Thanks,

Pradeep

1 ACCEPTED SOLUTION

Jelena
Active Contributor
0 Kudos

It's the tricky part. See a screenshot below for an example. Because it's an inbound IDoc in the Recipient you should have:
Port = 'SAP<systemID>' (in this case system ID is EGQ). Note - you won't see this port in WE21.

Partner Number = logical system assigned to the current client (see SCC4). Partn. type = LS

For Sender port any valid port (WE21) will do for testing - it does not matter. Partner number and type in your case would be your logical system and LS.

For the logical systems don't forget to maintain distribution model in BD64.

4 REPLIES 4

Former Member
0 Kudos

Hi Pradeep,

Can you pls. share the error message you are getting..!!

For control record, we can not help you, it depends upon your system configuration, pls take help from your team members or else you can check table EDIDC.

Thanking You All..!!

Jelena
Active Contributor
0 Kudos

It's the tricky part. See a screenshot below for an example. Because it's an inbound IDoc in the Recipient you should have:
Port = 'SAP<systemID>' (in this case system ID is EGQ). Note - you won't see this port in WE21.

Partner Number = logical system assigned to the current client (see SCC4). Partn. type = LS

For Sender port any valid port (WE21) will do for testing - it does not matter. Partner number and type in your case would be your logical system and LS.

For the logical systems don't forget to maintain distribution model in BD64.

Former Member
0 Kudos

Hello Jelena,

How are you?

Thanks, for your guidance. I was able to test it.

I am in a situation where :

a) A notepad file is placed on our SAP system by an external vendor at Transaction AL11.

b) After the file is placed, a program will run and create inbound idoc.

c) Now after above 2 steps we need to update outbound delivery with the following fields:

LIPS-BRGEW

LIPS-NTGEW

LIKP-LDDAT

LIKP-LDUHR

and 4 Z fields. These Z fields are already in LIPS table and an enhancement is done for them.

I tried to update standard fields for outbound delivery by

message type = DESADV

basic type = DELVRY03 and also with DELVRY07

fm = IDOC_INPUT_DESADV1

Also tried with

message type = SHPCON

basic type = DELVRY07 and also with DELVRY03

fm = IIDOC_INPUT_DELVRY

But there is no data change in the delivery. The status of the IDOC is 53.

What should i suggest to customer...should we go for BAPI to update this kind requirement. I am totally lost.

Kindly guide.

Thanks,

Pradeep

Jelena
Active Contributor
0 Kudos

Pradeep, this question has nothing to do with the original discussion subject, I believe we're supposed to open a new discussion in such cases. Please search Google for 'idoc change outbound delivery'. There are very many posts on SCN on this.

Personally I have not used IDocs to update outbound deliveries, so can't advise either way.