IDoc (MATMAS) to File Scenario (Dual Stack)

ALE Configuration/Connectivity settings b/w SAP-PI

ECC/SAP Level Configurations:
1.Creation of RFC Destination -----> T-Code - SM59
 Select the Connection Type 3/ABAP and Create New

RFC Destination: RFCDEST_SAPTOPID

Description: RFC Destination from ECC to PID

Technical Settings Logon & Security

Target Host (PI Details): PIECC Language: EN
System No: 01 Client (PI No): 001
Save as: Hostname User: sapuser
Password: welcome@123

 Save and click Connection Test on Top. If it is millisecond(msec) it is working fine.

 Then click Remote Logon (Here connection from ECC to PI happens).

2.Creation of PORT----> T-Code – WE21

 1.Select TRFC Port and Create New
 2.Select Own Port Name and give NAME: PORT_ PID
Port: PORT_PID
Description: Port for PID
RFC Destination: RFCDEST_SAPTOPID (Port depends on RFC Destination)

3.Creation of Logical Systems for SAP & PI -----> T-Code – SALE/BD54

 IDoc Interface/ Application Link Enabling (ALE)
 Basic Settings
 Logical Systems (It is to identify the Client)
 Define Logical System ----- First Select this one
 Assign Logical System to Client
9
 Then Click New Entries
Log. System Name
ECDCLNT800 Logical System for ECD
PIDCLNT001 Logical System for PID Then SAVE.
 Now go back and select Assign Logical System to Client Option
 Select 800 and change the Logical System Name as ECDCLNT800 as per your requirement
 Select 001 and change the Logical System Name as PIDCLNT800 as per your requirement

4.Creation of Partner Profile -----> T-Code --- WE20

 Select Partner Type LS
Partner No: PIDCLNT001 (Partner for SAP)
Partner Type: LS Then SAVE.

 Select Create Outbound parameters (select symbol)

Message Type: MATMAS
Receiver Port: PORT_PID
Output Mode: Transfer IDoc Immed. (Collect IDocs – For IDocs Packaging)
Basic Type: MATMAS05

PI Level Configurations:
1.Creation of RFC Destination -----> T-Code - SM59
 Select the Connection Type 3/ABAP and Create New

RFC Destination: RFCDEST_PIDTOSAP

Description: RFC Destination from ECC to PID

Technical Settings Logon & Security

Target Host (ECC Details): piecc Language: EN
System No: 00 Client (PI No): 800
Save as: Hostname User: sapuser
Password: welcome@123

10
 Save and click Connection Test Option on Top. If it is millisecond(msec) it is working fine.

2.Creation of PORT----> T-Code –- IDX1

 Select Port and Create
Port: ECDCLNT800
Client: 800
Description: Port for ECC
RFC Destination: RFCDEST_PIDTOSAP

3.Creation of Metadata ---> T-Code --- IDX2

 Select Create
IDoc Type: MATMAS05
Source Port: ECDCLNT800 Click Continue.

End-to-End Testing / Troubleshooting IDoc (Outbound)-to-File Scenario ---- Dual Stack

1. Trigger/Fetch/Push IDoc from SAP/ECC/S/4 HANA system using T-Code ---- WE19
 Basic Type: MATMAS05 --- Create
 You can see EDIDC Standard outbound Processing
E1MARAM
E1UPSLINK
 Click on EDIDC. It will ask you for details as below

Receiver Sender

Port: PORT_PID Port: ECDCLNT800

Partner No: PIDCLNT001 Partner No: PIDCLNT001
Partner Type: LS Partner Type: LS

Message Type: MATMAS

 Now click on E1MARAM. Fill the required details.

 Click Standard outbound Processing option and check PORT details and click Continue.

11
 At this point we have Two Cases.
Case -1: ERROR
 It will generate one IDoc number: xxxxxxxxxxxxxx. Copy it for later use.

IDoc xxxxxxxxxxxx was saved but cannot or should not be sent

2. Check/Track IDoc record status based on IDoc No/Date/Direction etc. by T-Code – WE02
Topmost Status Code is important for Us. It will be like as shown below
 IDoc xxxxxxxxxxxxx
Technical Info
 Control Rec.
 Data Records 1. Direction: 1 Outbox
 Status Records 2. Current Status: 37
 37 ----------------- IDoc added Incorrectly 3. Basic Type: MATMAS05
 EDI Sender port in control record is invalid 4. Partner No: PIDCLNT001
 42
5. Partner Type: LS
6. Port: PORT_PID
Click on Control Records and select Partner Tab.
Check Sender information and you can observe Port was changed
 Port: SAPEC5T800 ----- Above we mentioned Sender Port as ‘ECDCLNT800 ‘. But our SAP
system taking ‘SAPEC5T800’ as a default sender port. It is default Logical System.

 Now go to PI level - Metadata using T-Code --- IDX2. Delete the ECDCLNT800 MATMAS Record.
 Next go to PI Port level using T-Code --- IDX1 and delete the ECDCLNT800 Port.
 Again, Create New Port in PI Level
Port: SAPEC5T800 (Previously it is ---- ECDCLNT800)
Client: 800
Description: Port for ECC
RFC Destination: RFCDEST_PIDTOSAP Then SAVE.

 Again, Create Metadata using T-Code --- IDX2

IDoc Type: MATMAS05
Source Port: SAPEC5T800 (Previously it is ---- ECDCLNT800) Click Continue.

 Again, Trigger IDoc File at ECC level using T- Code --- WE19 and Fill the Control & Data records
details and click Start outbound Processing. You will see below message.

CASE-2 :(Success) IDoc sent to SAP System or external program Copy IDoc Number
12
 Check/Track IDoc record status based on IDoc No/Date/Direction etc. by T-Code – WE02
Topmost Status Code is important for Us. It will be like as shown below
 IDoc xxxxxxxxxxxxx
Technical Info
 Control Rec.
 Data Records 7. Direction: 1 Outbox
 Status Records 8. Current Status: 03
 03 ----------------- Data Passed Port OK 9. Basic Type: MATMAS05
 IDoc sent to SAP System or external program 10.Partner No: PIDCLNT001
 30 11.Partner Type: LS
 01
12.Port: PORT_PID
 42
 Now Check for the IDoc at PI level using T-Code ----- IDX5 using IDOC No: xxxxxxxxxxx.
It will show you “NO Message Selected”.
 Reason for this is as wee seen above in Status Records Code 03 states Data passed to Port OK.
Here we are using TRFC port b/w SAP and PI.
 So, we have to check TRFC port at ECC level using T-Code ----- SM58 and click on execute button.
 It will show you one error in Status Text – No Service for System SAPEC5T800, client 800 in ID.
 Now go to ID Part, select the Business Component you created for IDoc Sender side.
 Go to Communication Component --> Adapter Specific Identifiers
Logical System: SAPEC5T800
R/3 System ID: EC5
Client: 800 Save and Activate the Business Component.
 Again, go to TRFC port at ECC level using T-Code --- SM58
 Select IDOC and go to EDIT  Execute LUW
 Now check for IDoc at PI level using T-Code ---- IDX5. You can see IDoc received at PI level.
SUMMARY OF IDoc-To-File Scenario (Dual Stack)
ECC Level Configuration PI Level Configuration
1. Create RFC Destination: T-Code – SM59 1. Create RFC Destination: T-Code – SM59
2. Create Port: T-Code – WE21 2. Create Port: T-Code – IDX1
3. Create Logical System: T-Code – SALE 3. Create Meta Data: T-Code – IDX2
4. Create Partner Profile: T-Code – WE20

Testing/Troubleshooting IDoc -To -File Scenario (Dual Stack)

ECC Level: 1. Trigger IDoc T-Code – WE19 PI Level: 1. IDoc Status T-Code – IDX5
2. IDoc Status Check – T-Code – WE02 3. TRFC Port Level – SM58
13