Inbound Processing Error ?

Question

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 . ?

Answer 1

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