topic Re: Entry in outbound table not found in Application Development and Automation Discussions

Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 06:21:32 GMT

I am trying to transfer custom table data from client 100 to client 200. I have created the custom message type (ZSR_SEGMENT), basic type and program using MASTER_IDOC_DISTRIBUTE.

But when i see the idos status it is giving me the error with Status 29 (Entry in outbound table not found)

Diagnosis

No partner profile (outbound parameter) could be found using the following key:

/Q10CLNT200/LS//ZSR_SEGMENT////

This refers to the key fields in table EDP13:

RCVPRN Partner number

RCVPRT Partner type

RCVPFC Partner function

MESTYP Logical message

MESTYP Message code

MESCOD Message function

TEST Test indicator

I have created partner profile for both the clients (zsr_segment as inbound parameter in Q10CLNT100 and outbound in Q10CLNT200.)

Thanks,

Shrinivas

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 06:31:43 GMT

check entry in EDP13 table for following:

/Q10CLNT200/LS//ZSR_SEGMENT////. This represents all key fields mentioned in error message so even one field like 'test indicator' is different then it will not find correct entry.

Re: Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 06:54:48 GMT

Hi sanjay

What should i match in which client.

I am able to find correct entries (ZSR_SEGMENT) in EDP13 in client 100. But for client 200 i am not able to find any values for this table since i haven't defined anything in outbound. I have defined ZSR_SEGMENT in inbound parameters.

am I missing something in partner profile?

Thanks

Shrinivas

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 06:55:23 GMT

Hi,

Check the maintained partner profile entry in WE20 and the one in Idoc Control data.

These have to be similar.

Hope this helps.

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 06:59:49 GMT

You are sending data from 100 to 200. So, your partner profile should contain ZSR_SEGMENT as o/b parameters.

Re: Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 08:46:07 GMT

Hi Roopaali

I have checked the control data. there seems to be some mismatch.

In Sender information: Partner number is different to which i created partner profile and also

Port field is blank in recipient information.

I have defined my custom port but that is not seemed to be coming in the control record.

How can i resolve this?

Thanks

Shrinivas

Re: Entry in outbound table not found

gajendra_bhakuni — Mon, 28 May 2007 09:19:23 GMT

Hi Shrinivas,

I think that you are using some custom program to transfer IDoc.

Check whether in your custom logic you have populated the correct parter profile data (idoc_control internal table is filled with the partner data defined in WE20).

You need to fill the following:

rcvpor

rcvprt

rcvprn

mestyp

idoctp

Hope this helps.

Regards,

Gajendra.

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 09:30:54 GMT

Hi,

Suppose you are passing data to Client 200 from Client 100, then on Client 100 you should have the partner profile is the partner of Client 200 ( for ex. SAPCLI200 is the PP of Cli 200 on CLI 100. This is maintained in WE20). In WE20, for the o/b parameters of PP SAPCLI200 you will maintain the outgoing data message type2 say for ex. MATMAS. Further you have to maintain the Receiver port here. This receiver port should have the RFC destination for CLI 200.

Further you maintain the IDOC type and other details here.

I hope you have maintained all this data for your scenario.

Further while using MASTER_IDOC_DISTRIBUTE, in the Import parameter MASTER_IDOC_CONTROL pass the RCVPOR RCVPRN and othe rreqd. data from the Partner profle created.

Re: Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 09:52:30 GMT

i have given my custom code. I have done the necessary configurations (creating and distributing partner profiles). When i am using standard mesage type (HRMD_A) then i am able to transfer the data between these two systems. But when i am using with my custom idoc i am getting above errors.

REPORT ZSR_CUST_IDOC.

parameters : p_logsys like tbdlst-logsys.

data : gen_segment like edidd-segnam value 'ZSR_SEGMENT'.

data : control_dat like edidc.

tables :zsr_table.

data: begin of inttab occurs 0,

PERNR type zsr_table-pernr,

LNAME type zsr_table-lname,

FNAME type zsr_table-fname,

GRADE type zsr_table-grade,

end of inttab.

data: gen_data type zsr_structure.

data :int_edidd like edidd occurs 0 with header line,

int_edidc like edidc occurs 0 with header line.

select * from zsr_table into corresponding fields of table inttab.

if sy-subrc ne 0.

message 'no data' type 'I'.

exit.

endif.

control_dat-mestyp = 'ZSR_SEGMENT'.

control_dat-idoctp = 'ZSR_SEGMENT1'.

control_dat-rcvprt = 'LS'.

control_dat-rcvprn = p_logsys.

control_dat-rcvpor = 'ZSR_PORT'.

loop at inttab.

gen_data-pernr = inttab-pernr.

gen_data-lname = inttab-lname.

gen_data-fname = inttab-fname.

gen_data-grade = inttab-grade.

int_edidd-segnam = gen_segment.

int_edidd-sdata = gen_data.

append int_edidd.

endloop.

call function 'MASTER_IDOC_DISTRIBUTE'

exporting

master_idoc_control = control_dat

OBJ_TYPE = ''
CHNUM = ''

tables

communication_idoc_control = int_edidc

master_idoc_data = int_edidd

exceptions

error_in_idoc_control = 1

error_writing_idoc_status = 2

error_in_idoc_data = 3

sending_logical_system_unknown = 4

others = 5

if sy-subrc <> 0.

message id sy-msgid type sy-msgty number sy-msgno.

else.

loop at int_edidc.

write 😕 'IDOC GENERATED',int_edidc-docnum.

endloop.

commit work.

endif.

Re: Entry in outbound table not found

gajendra_bhakuni — Mon, 28 May 2007 09:59:57 GMT

Hi Shrinivas,

I hope you have maintained the partner profile for client 200 in WE20 as mentioned by Roopali. This partner profile should be entered at the selection screen of the custom program.

Also check the distribution model (BD64). The model should be defined correctly (sender, receiver logical system and message type). After creating the distribution model it should be distributed to the receiver system (client 200).

Regards,

Gajendra.

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 10:38:28 GMT

as you are using a custom message type, have you maintained the message type to Idoc type relation in trx. WE82 ?

Re: Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 11:23:05 GMT

Hi gajendra / roopali

I have maintained partner profile and we82.

Below are the steps i have done till now.

In sender system (client 100)

1. Defining segment type(WE31)

2. Define Basic Type(WE30)

3. Entry of segment type (WE81)

4. Assignment of idoc types (WE82)

5. Defining Target System for RFC Calls (Tcode – SM59)

6. Defining Port

7. Defining Partner Profile (Q10CLNT100)- Outbound parameter - ZSR_SEGMENT with custom port (ZSR_PORT)

8. Creating distribution model (BD64) and adding custom message type

9. Distributing in the model view

In Reciever End

1. Defining Partner Profile (Q10CLNT200)- Inbound parameter - ZSR_SEGMENT with custom process code.

If you guys have any document (Step by Step for creation of custom IDoc it will be greately appreciated).My mail id is shrinivas.shenoy@gmail.com

Re: Entry in outbound table not found

gajendra_bhakuni — Mon, 28 May 2007 11:30:17 GMT

Hi Shrinivas,

I just found one thing in the steps you mentioned.

In the sender system client 100 you need to define the partner profile of the receiver system (Q10CLNT200) and then you need to maintain the outbound parameters corresponding to it.

In the reciever system you need to maintain the partner profile of the sender (Q10CLNT100).

Could you pls. check.

Regards,

Gajendra.

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 12:11:40 GMT

Have you created a Partner profile of teh sending system for itself.

Ideally in your case teh PP's should be maintained as follows.

On Cli 100

Partner profile Q10CLNT100 as blank.

PP Q10CLNT200 with the o/b parameters as mentioned.

in the Idoc control rec.

Sender prn = Q10CLNT100

Receiver prn = Q10CLNT200

Reeceiver port = ZSR_PORT ( this has rfc to Cli 200)

On Cli 200

Partner profile Q10CLNT200 as blank.

PP Q10CLNT100 with the i/b parameters as mentioned.

Re: Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 12:19:11 GMT

HI gajendra/Roopali

I have created the partner profile of the other systems in the respective clients . But still it is giving the same error.

Thanks

Shrinivas

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 12:31:25 GMT

Please could you mentioned the error faced again?

Re: Entry in outbound table not found

former_member31961 — Mon, 28 May 2007 12:34:59 GMT

HI Roopali ,

Below mentioned error came when i see the status in WE02.

Entry in outbound table not found

Message no. E0400

Diagnosis

No partner profile (outbound parameter) could be found using the following key:

/Q10CLNT200/LS//ZSR_SEGMENT////

This refers to the key fields in table EDP13:

RCVPRN Partner number

RCVPRT Partner type

RCVPFC Partner function

MESTYP Logical message

MESTYP Message code

MESCOD Message function

TEST Test indicator

Procedure

Please check the EDI partner profiles.

Execute function

Message was edited by:

Shrinivas Shenoy

Re: Entry in outbound table not found

Former Member — Mon, 28 May 2007 12:43:02 GMT

try to configure like this if you are sending like r/3 to r/3.

RFC Destination - create rfc from a to B.

now create port at WE21 Transaction - Please remember ur Port Number.

now come to BD64 transaction and here maintain distribution model view,

generate partner profile and distribute ur view ( Here you will get Some red color).

Now goto WE20 Transaction ,here give ur port number,message type,idoc type and process code perfectly,

let us maintain both inbound and outbound parameters perfectly

and see the output

Reward Points if it is helpful

Thanks

Seshu

Re: Entry in outbound table not found

Former Member — Tue, 29 May 2007 04:11:27 GMT

Are you populating both Partner type and Partner Function in th ePP and just the Partner type in the Idoc Ctrl rec. or vice-versa.

Please check. These shud be the same.

Re: Entry in outbound table not found

Former Member — Tue, 29 May 2007 06:16:12 GMT

Hi shrinivas,

Go through the following Steps for Creating IDoc Via ALE

ALE IDOC

Sending System(Outbound ALE Process)

Tcode SALE ? for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 ? Create Model View

Tcode BD82 ? Generate partner Profiles & Create Ports

Tcode BD64 ? Distribute the Model view

Message Type MATMAS

Tcode BD10 ? Send Material Data

Tcode WE05 ? Idoc List for watching any Errors

Receiving System(Inbound ALE )

Tcode SALE ? for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 ? Check for Model view whether it has distributed or not

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 ? Idoc List for inbound status codes

ALE IDOC Steps

Sending System(Outbound ALE Process)

Tcode SALE ?3 for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 !V Create Model View

Tcode BD82 !V Generate partner Profiles & Create Ports

Tcode BD64 !V Distribute the Model view

This is Receiving system Settings

Receiving System(Inbound ALE )

Tcode SALE ?3 for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 !V Check for Model view whether it has distributed or not

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 !V Idoc List for inbound status codes

Message Type MATMAS

Tcode BD10 !V Send Material Data

Tcode WE05 !V Idoc List for watching any Errors

1)a Goto Tcode SALE

Click on Sending & Receiving Systems-->Select Logical Systems

Here Define Logical Systems---> Click on Execute Button

go for new entries

1) System Name : ERP000

Description : Sending System

2) System Name : ERP800

Description : Receiving System

press Enter & Save

it will ask Request

if you want new request create new Request orpress continue for transfering the objects

B) goto Tcode SALE

Select Assign Client to Logical Systems-->Execute

000--> Double click on this

Give the following Information

Client : ERP 000

City :

Logical System

Currency

Client role

Save this Data

Step 2) For RFC Creation

Goto Tcode SM59-->Select R/3 Connects

Click on Create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

give the information for required fields

RFC Destination : ERP800

Connection type: 3

Description

Target Host : ERP000

System No:000

lan : EN

Client : 800

User : Login User Name

Password:

save this & Test it & RemortLogin

Goto Tcode BD64 -- click on Change mode button

click on create moduleview

short text : xxxxxxxxxxxxxx

Technical Neme : MODEL_ALV

save this & Press ok

select your just created modelview Name :'MODEL_ALV'.

goto add message type

Model Name : MODEL_ALV

sender : ERP000

Receiver : ERP800

Message type :MATMAS

save & Press Enter

4) Goto Tcode BD82

Give Model View : MODEL_ALV

Partner system : ERP800

execute this by press F8 Button

it will gives you sending system port No :A000000015(Like)

5) Goto Tcode BD64

seelct the modelview

goto ~~>edit~~>modelview-->distribute

press ok & Press enter

6)goto Tcode : BD10 for Material sending

Material : mat_001

Message Type : MATMAS

Logical System : ERP800

and Execute

7)goto Tcode : BD11 for Material Receiving

Material : mat_001

Message Type : MATMAS

and Execute --> 1 request idoc created for message type Matmas

press enter

Here Master Idoc set for Messge type MATMAS-->press Enter

1 Communication Idoc generated for Message Type

this is your IDOC

Change Pointers

I know how to change the description of a material using ALE Change Pointers.

I will give the following few steps

1) Tcode BD61---> check the change pointers activated check box

save and goback.

2) Tcode BD50---> check the MATMAS check box save and comeback.

3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.

4) Tcode BD52---> give message type : matmas press ok button.

select all what ever you want and delete remaining fields.

save & come back.

5) 5) go to Tcode MM02 select one material and try to change the description and save it

it will effects the target systems material desciption will also changes

6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute

give Message type : MATMAS and Executte

ALE/IDOC Status Codes/Messages

01 Error --> Idoc Added

30 Error --> Idoc ready for dispatch(ALE Service)

then goto SE38 --> Execute the Program RBDMIDOC

29 Error --> ALE Service Layer

then goto SE38 --> Execute the Program RSEOUT00

03 Error --> Data Passed to Port ok

then goto SE38 --> Execute the Program RBDMOIND

12 Error --> Dispatch ok

Inbound Status Codes

50 Error --> It will go for ALE Service Layer

56 Error --> Idoc with Errors added

51 Error --> Application Document not posted

65 Error --> Error in ALE Service Layer

for 51 or 56 Errors do the following steps

goto WE19 ~~> give the IDOC Number and Execute~~>

Press on Inbound function Module

for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

Reward if it is useful.

Regards,

Azhar