cancel
Showing results for 
Search instead for 
Did you mean: 

Config inbound Idoc

Former Member
0 Kudos

Good morning.

Please help me.

I must set up multiple inbound IDOCS, one of them is:

Type base : orders05.

message type : orders.

The process is : data is received xi / pi, and IDOCs must be created to fill the data transaction VA01 and VA02.

I have read many tutorials but I have not been clear what to do if we use a standard IDOC type base as ORDERS05.

what should I set in r / 3?

Thanks!!!

Accepted Solutions (0)

Answers (3)

Answers (3)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

IDOC order05 inbound to SAP - configuration described step by step with screenshots

http://www.sap-press.com/products/Mastering-IDoc-Business-Scenarios-with-SAP-NetWeaver-PI.html

page:

2.4 ... Processing Inbound Orders in SD ... 59

Regards,

Michal Krawczyk

Former Member
0 Kudos

thanks for answering.

I'm driving in accordance with the information that I found:

I realized this:

1) SM59 : create RFC : "ccd100" (this is the one that receives the data)

2) WE21: create the port: "A000000100"

3) WE20: in this transaction i have the interlocutors: ccd100 and XI.

the message type ORDERS I would have to put as input parameter in ccd100?

I should set something else in the we20?

THANKS!

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Detailed ALE configuration as follows... This might be helpful to check both your PI and ECC or R/3.

1. First - Maintain the Sender R/3 System:

SM59 : Create a RFC destination to XI

WE21 : Create a TRFC Port ->Specify the RFC Destination Created

BD54 : Create a Logical System for the Idoc Receiver

WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters

2. Second - Log on to XI System:

SM59 : RFC Destination for Sender System

IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 Optional Step. Not mandatory

IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.

3. To Enable Acknowledgement:

SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:

Category: RUNTIME

Parameters: ACK_SYSTEM_FAILURE

Current Value: 1

4. GO TO SLD:

Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System

Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:

Business System Role: Application System

Related Integration Server: Integration Server

5. IDOC Tunneling in XI

To prevent performance consuming XMLization and de-XMLization IDOCs are tunneled through SAP XI IDOC adapter meaning no XMLiziation is executed before the IDOC is passed onto the pipeline. Note the message is converted to UTF-8 codepage.

6. Start transaction SXMB_ADM on SAP XI.

Select option Configuration->Integration Engine Configuration and add two parameters EXTERNAL_MAPPER in the category IDOC.

Configure the parameter according to the conditions below:

If Message Code and Message Function are specified in the partner profile:

<Snd.Syst.Id>.<Snd.Syst.Client>.ReceiverPort.<Mess.Type>.<Mess.Code>.<Mess.Function>

If only the Message Code is specified in the partner profile:

<Snd. System Id>.<Snd. System Client>.ReceiverPort.<Mess. Type>.<Mess. Code>

If only Message Function is specified in the partner profile:

<Snd.Syst.Id>.<Snd.Syst.Client>.ReceiverPort.<Mess.Type>..<Mess.Function>

7. Integration Builder  Integration Directory:

Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System

IDoc Receiver Communication Channel: port the same as XI System IDX1

Former Member
0 Kudos

HI!

In the steps 1 and 2:

My scenario as I see is file-xi-idoc.

in sm59: sender is XI and destination is the r/3 system?

THANKS!

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>>> what should I set in r / 3?

Basically you need to do ALE config between ECC and PI.

Once you configured you would be able to send idocs from PI to ECC and vice versa.

Please search sdn forum for ALE configuration. After that import idocs in PI from ECC6.

if you need any help on developing idoc scenario please contact us.

Hope I answered your question.

Thanks

Baskar