Inbound Processing Error ?

[Former Member]

I create an outbpund idoc as a file on a file port : FILEIN.

FILEIN port is defined as a file port with Dir parameter set as : /tmp/

and FM parameter set as : EDI_PATH_CREATE_DATE_TIME . No parameters are maintained for Inbound file .

I create outbound idoc with :

Reciever Port FILEIN and Sender port A00001 (defined as a trfc port ).

The Idocs are generated in the specified directory .

Now i want to process these idocs with RSEINB00 Program .

I give the filename and Port name : FILEIN to the program .

The partner profile is maintained for the inbound processing .

But I somehow recieve the error : '56 : Reciever port in control record is invalid. '

How can this be solved ? DO i need to maintain the Inbound file parameters too in the File port . ?

[Former Member]

Raymond,

Can you please copy-paste the Control record.

Cheers,

Nilesh

[Former Member]

Yes, I think you need to have a different port for the inbound and outbound.

Regards,

Ravi

Note : Please mark the helpful answers

[ferry_lianto]

Hi Raymond,

No need to create separate file port for inbpound and outbund file. You only need to maintain both outbound file and inbound file and specify the physical directory in your file port FILEIN. Once done, please do access test.

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

[Former Member]

Hello Everyone ,

Thanks for all the responses.

Here is what I did :

I created an Inbound Parameter for the same FILEIN port but it still gives the same error.

If I create a sperate port FILEIN1 with the inbound parameters and give it as a parameter to the RSEINB00 Program , it is working fine .

But I am not able to understand the reason behind this ? Why cant we do it withe same File port ( as the inbound and outbound parameters are maintained seperately ) ?

Thanks,

[ferry_lianto]

Hi Raymond,

You don't need to maintain separate file port for inbound and outbound purposes. That's way SAP provides two tabs for inbound and outbound files setup.

Unless you have more than one physical directory for either inbound or outbound then you need to create separate file ports.

It is working fine in my system. Are you sure that you are not missing something?

Regards,

Ferry Lianto

[Former Member]

Hi Ferry ,

Yeah , It really makes sense to use the parameters provided by SAP for the same as you say .

But , Somehow its not working in my system.

I am telling u the details of the Set up . pls see if i have missed out on something :

For Outbound File Directory :

Dir: /tmp.

FM : EDI_PATH_CREATE_DATE_TIME.

For Inbound tab:

Dir: /usr/sap/UR4/DVEBMGS00/work.

FM EDI_PATH_CREATE_CLIENT_DOCNUM.

Let me know if i need to check something other than this .

Thanks Much ,

Ray

[Former Member]

Hi,

You should first turn your output IDoc file to an Inbound IDoc file. use the transaction code we12 to that.

Following is the more info on Using We12.

-

---

We12 - IDoc testing tool which will emulate an EDI subsystem, by taking a outbound text file IDoc previously generated by SAP and use it to create and process an inbound IDoc. It is also possible to create an outbound IDoc from an inbound IDoc as well. Commonly referred to as the ‘Turn-around’ program

Field level documentation on each field on the We12 screen..

Source:

Directory + file: The field contains the path and filename of the existing IDoc text file at the operating system level.

Target:

Directory + file: the target fields contain the path and filename of the IDoc text file that is to be created. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (see WE46 for IDoc Administration; WE 21 for Port Definition).

Sender:

Partner Number: Customer or Vendor number of the sender - when testing inbound messages, this partner number must exist as a valid inbound partner (transaction WE20).

Partner Type: Code, which identifies the type of sender (i.e. LI – Vendor; KU – Customer).

Partn.function: Code, which identifies role of the partner (i.e. SH – Ship-to).

Message type: Code, which identifies the type of data, based on the EDI message type (i.e. ORDERS, INVOIC).

Variant: Code, which further subdivides the type of message (i.e. MM or FI for a logical message type of INVOIC).

Function: Code, which defines the function of the message with regard to its transmission.

Test: Flag indicating that this is a test message. This is one of the keys to finding the inbound partner profile.

Port: Logical ID of the sending system. Enter the logical name of the receiving as defined in the transaction WE21. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (WE46).

Recipient:

Partner Number: Customer or Vendor number of the receiver.

Partner Type: Code, which identifies the type of receiver (i.e. LI - Vendor; KU - Customer).

Partn.function: Code, which identifies role of the partner (i.e. SH - Ship-to).

Direction: The direction that the newly created IDoc will be assuming -1 for outbound, 2 for inbound. Default is ‘2’.

Client: The client that the newly created IDoc will be processed in. The default is the client that the user is logged into when executing this transaction.

Port: Logical ID of the receiving system. Enter the logical name of the receiving system in the form 'SAPxxx'. 'xxx' stands for the ID of the SAP System. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (WE46).

Turn-around program examples: When taking an outbound purchase order IDoc (which was generated via MM purchase order create) and turning it around to test inbound SD sales order creation via EDI, the ‘Sender’ would be a customer while the ‘Receiver’ would be a vendor. If using an outbound advanced ship notice IDoc (generated via SD delivery processing) and turning it around to test inbound shipping notification, the ‘Sender’ would be a vendor, and the ‘Receiver’ would be a customer. If using an outbound invoice IDoc (generated via SD invoicing) and turning it around to test inbound EDI invoice processing, the ‘Sender’ would be a vendor, and the ‘Receiver’

Hope this helps.

Mark the Helpful answerers..

Regards,

Nagaraju Chidurupalli

[ferry_lianto]

Hi Raymond,

Nothing wrong with your file port setup, it is perfect.

The only thing I can see that program RSEINB00 does not validate the file port whether for outbound or inbound file. It seems always pick the first setup which in your cas the outbound file (left -> right). If you only setup the inbound file then the default is inbound file.

Therefore you need to have multi file ports for program RSEINB00.

Other alternative, you can use this FM <b>EDI_DATA_INCOMING</b> which has file port valdation for inbound or outbound file. Therefore you only need to have one file port setup. But you need to write custom program to call thsi FM.

Again, hope this will help.

Regards,

Ferry Lianto

[Former Member]

I would need to schedule the interface so i thought RSEINB00 will be a good option .

But , looks like i will need to a custom program to call the EDI_DATA_INCOMING FM .

All the help is relly appreciated .

*have assigned the points

Thanks Much ,

Ray