genrating Idoc in same client

[Former Member]

Hi,

Is It possible to generate the idoc in same client only.If possible can any one help me ,how to set up logical file system and partner profile for that..

Thanks

kisu

[Former Member]

Hi Kisu,

You don't need a logical file system.

Create a port of type transactional RFC. Then when it prompts you for the RFC destination, put in the RFC destination for your the system you are working on.

For the partner profile, just point to the port you have just created.

One thing to watch though, is that the direction of the Idoc will be outbound (I think that this is value 1), you will need to flip the direction of the Idoc to inbound (I think that this is value 2), so that when it is picked up by inbound processing this does not generate an error.

That should get you going.

Cheers,

Brad

[Former Member]

Hello,

1. T.code : we21Create a Port A000000001 (say)

Enter RFC destination sys_001 (make sure you have one RFC destination (check with sm59 to create and test if the destination is proper).

2. WE20 - create partner SAP0XYZ011 (say)

Outbound paramters say i use ORDERS msgtyp

Receiver port A000000001

Basic type ORDRSP (depends on version)

Fill in INBOUND parameters:

Give Process Code ORDR (it is a standard one you can create your own with WE42)

Now You have Order COnf from Sales Orders on the same .

Regards,

Manohar

[Former Member]

Thanks Dudes for the reply, in creating partner profile, which type should we assign it..

Thanks

[Former Member]

Hi Kisu,

The partner type depends upon your scenario. If you are doing master data distribution (ALE) you can set up your partners as logical systems.

If you are doing transactional data (for example purchase orders outbound, becoming sales orders inbound) then you will need to set up a vendor outbound partner and a customer inbound partner.

If you are doing something else, then let us know.

Cheers,

Brad

[Former Member]

Hi!

There is the way to set up distribution scenario in the same client.

Let's assume that LOGSYS0100 is the logical system name of the client we want to work with, and that MATMAS(material master) is the message type of the distribution model. Follow these steps:

1.Create a "dummy" logical system name. Using transaction SALE, choose "Sending and Receiving Systems->Logical Systems->Define Logical System", enter LOGSYSD100, give it any name you want and save.This dummy logical system will serve as the receiver system in the distribution scenario.

2.Using transaction SM59, create RFC destination LOGSYSD100 for the dummy logical system. The RFC destination addresses the same client.

3.Create a distribution view in transaction BD64 with LOGSYS0100 as the sender, LOGSYSD100 as the receiver, and message type MATMAS.

4.Generate partner profiles for the newly created distribution view using transaction BD82, or in transaction BD64 select "Enviroment->Generate partner profiles". Note that this step will generate only the outbound parameters.

5.Using transaction WE20, create the inbound parameters of logical system LOGSYS0100 for message type MATMAS. The approporiate process code for MATMAS is MATM.

Now test your settings by sending material master IDocs via transaction BD10 to LOGSYSD100 and check the results with monitoring transaction WE02.

Regards,

Maxim.

[Former Member]

Hi Experts,

I am using   MASTER_IDOC_DISTRIBUTE to create a outbound idoc in same client

When I run through we19 by giving the inputs it is creating the IDOC successfully with status 3.

But when i give the same details and pass to the above FM

it is thrwoing error as 29.

RCVPOR                                     ERC200

RCVPRT                                     LS

RCVPRN                                     ERCCLNT200

  MESTYP                                     ZPOS_ADJUST_MSG_TYP

IDOCTP                                     ZPOS_SC_ADJUST_1

SENDER : SAPERC

               LS

               ERCCLNT200

My requirement is to create idoc in same client...which i trigger through a BADI

NOTIF_EVENT_POST.