Idoc to file (MATMAS04)

[Former Member]

Hi

I have a scenario Idoc to File.. i am using MATMAS04 . The requirement is on Daily basis the interface

should run.. the interface should collect the New material and changes made and deletion of material

send it to the file on dialy basis..

what are the configuration we need to do in R/3 side ... i want to do using the change pointers

SV

[Former Member · Accepted solution]

Hi,

Please find the below technical setting which has to done for an outbound Idoc.

Pre-requisites for Outbound IDoc from R/3 to PI:

Configurations required in R/3:

Maintain Logical System (SALE)

Define RFC Destination (SM59) which points to PI system

Maintain Port (WE21)

Maintain partner profile. (WE20):

Maintain Distribution Model (BD64):

Thanks,

Kiran

[Former Member]

Steps for ALE settings:-

Steps for XI

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the R3 system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto IDX1.

Create a new port.

Give the port name.

Give the client number for the R3 system.

Select the created Rfc Destination.

Step 3)

Goto IDX2

Create a new Meta data.

Give the Idoc type.

Select the created port.

Steps for R3.

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the XI system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto WE21.

Create a port under transactional RFC.(R3->XI)

Designate the RFC destination created in prev step.

Step 3)

Goto SALE.

Basic settings->Logical Systems->Define logical system.

Create two logical systems(one for XI and the other for R3)

Basic settings->Logical Systems->Assign logical system.

Assign the R3 logical system to respective client.

Step 4)

Goto WE20.

Partner type LS.

Create two partner profile(one for XI the other for R3).

Give the outbound or inbound message type based on the direction.

Step 5)

Goto WE19

Give the basic type and execute.

fill in the required fields.

Goto IDOC->edit control records.

Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)

Click outbound processing.

Step 6)

Go to SM58

if there are any messages then there is some error in execution.

Goto WE02.

Check the status of the IDOC.

Goto WE47.

TO decode the status code.

Step 7)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

BD87 to check the status of IDOC.

In case if not authorized then go to the target system and check in SU53, see for the missing object

and assign it to the user.

[Former Member]

Hi

I tried using the RBDIDOC but it sending the Single idoc at a time..but i want to collect the changes and on daily basis want to send to to the file .. How we do that

SV

[turmoll]

Hi,

Looks like you need to go for BPM.

Check this weblog: [Using a BPM to collect messages for a set interval of time|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4369] [original link is broken] [original link is broken] [original link is broken];.

Regards,

Jakub

[former_member556603]

Hello SV,

A background program should be scheduled to run every XX minutes to analyse any material records that have been created or changed or deleted that have occurred to the material master records in the last minute.

There are two Message Mappings involved in the whole scenario. First mapping is N:1 Mapping which will be used in BPM and second Mapping is 1:1 Mapping:

1.First Message Mapping  N: 1 – Mapping between IDoc (occurrence – 0...unbounded in “Messages” tab) to IDoc with changed occurrence of its top node (IDOC) as 0...unbounded. This message mapping will be used in BPM – transformation step.

Use

You use a wait step ( ) to incorporate a delay in a process. Usually, you use a delay to define when the next step in the process is to start. You can define a delay as either a point in time or a period of time.

At runtime, the step waits until the specified point in time is reached or the specified period of time has passed. The system then continues the process by proceeding with the next step.

Description: This BPM collects all Idocs for 15 minutes which are of Message Type (ZMATMAS05) according to Receiver Partner Number (Field – RCVPRN) and calls N: 1 mapping to bundle the collected Idocs in a One External Definition for that IDOC.

Thanks,

Satya Kumar

Reward if it is useful..

[turmoll]

Hi,

- make sure if change pointers are activated globally: BD61 - Active change pointers generally.

- turn on change pointers for your message type: MATMAS: BD50 - Active change pointers for Message Type.

- check if RFC destination to XI is set up: SM59 - RFC Destination.

- check if "transactional RFC" port pointing XI is maintained: WE21 - Ports in IDoc processing.

- set up outbound partner profile for message MATMAS: WE20 - Partner Profiles. It is recommended to collect IDocs instead of sending them immediately on production environment - you will trigger IDocs by scheduling background job for RESOUT00 program.

- set up distribution model for MATMAS: BD64 - Change Distribution Model

- schedule background job for program RBDMIDOC for message MATMAS to create IDocs from change pointers.

Furthermore, you might consider filtering of IDocs based on Class Types/ALE objects etc.

Regards,

Jakub

[former_member556603]

Hello SV,

Interface Trigger & Result

A background program RBDMIDOC should be scheduled to run every 15 minutes to analyse any material records that have been created or changed or deleted that have occurred to the material master records in the last minute. This program should generate IDocs containing material data. The ALE layer will be configured to send the IDocs out from SAP immediately.

Send created/changed/deleted materials to respective 3PLPs based on, whether the materials are extended for the respective 3PLP plants only

Change pointers will be activated for all the fields required by the receiving system so that when a MATERIAL is created, changed or deleted, change documents are written to the SAP database. The SAP program RBDMIDOC will be scheduled to run every 15 minutes to analyze change documents and generate the outbound IDocs. The snapshot of materials with all the fields should be populated in the IDOC even if certain fields are only changed. User-exit needs to be used for this.

All newly created & deleted materials will be sent to the concerned 3PLPs.

Activate Change Pointers for Message

Activate the following change pointers, so that Idocs are generated for the message type when these fields are changed in the material master.

Error Handling and Restart Considerations

..................................................................

On SAP side, transaction BD87 will be used for error correction & reposting of IDOC.

On XI side, SXMB-MONI transaction will be used as a central monitoring tool to reprocess failed messages.

Thanks,

Satya KUmar

Reward points if it is useful

[Former Member]

Hi

I did all this configuration its working fine for me...my question is how we trigger the interface when there is any change and create and delete is happen in material master data..

SV

[Former Member]

Hi SV,

Create a proxy for each of the function that you need........

In this case as you need update the external system then u need to create client proxys(Outbound side) for each of the application(create, Change.....etc)

So whichever application u required assign the app to respective proxy.....

In this the inteface can trigger........

Following links can help u kindly refer

ABAP Server Proxies (Inbound Proxy)

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

OutBound Proxy (Client Proxy)

/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies

Outbound Proxy (Client Proxy)

/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy

Thanks

Sai

PS: kindly reward points if helpful

[Former Member]

Hi S V,

In this case what we all need to do is

Activate the Change Pointers for Message Types ( Ex:MATMAS)

Activate the change pointers globally ---BD61

One Standard Pragram will be there for this MATMAS , find out it and Use that and schedule it for Background job.

Result: When we run the Program it will collect the changes which was done to the Message Types and will generate the Idocs to the corresponding Message Types

Regards

Seshagiri

[Former Member]

Hi,

Activate the Change Pointers for Message Types for MATMAS

Activate the change pointers globally ---BD61

Standard Program RBDMIDOC will be scheduled in Background

When the program would run it will collect the changes which was done to the Message Types and will generate the Idocs to the corresponding Message Types

Regards,

Shabari

[Former Member]

hai friend

iam also working on this kind of problem.

so pls guide me how to do this .

if find the soltion pls tel to me .

with regards

srikanth vipparla

[former_member556603]

Hello Srikanth,

Interface Trigger & Result

A background program RBDMIDOC should be scheduled to run every 15 minutes to analyse any material records that have been created or changed or deleted that have occurred to the material master records in the last minute. This program should generate IDocs containing material data. The ALE layer will be configured to send the IDocs out from SAP immediately.

Send created/changed/deleted materials to respective 3PLPs based on, whether the materials are extended for the respective 3PLP plants only

Change pointers will be activated for all the fields required by the receiving system so that when a MATERIAL is created, changed or deleted, change documents are written to the SAP database. The SAP program RBDMIDOC will be scheduled to run every 15 minutes to analyze change documents and generate the outbound IDocs. The snapshot of materials with all the fields should be populated in the IDOC even if certain fields are only changed. User-exit needs to be used for this.

All newly created & deleted materials will be sent to the concerned 3PLPs.

Activate Change Pointers for Message

Activate the following change pointers, so that Idocs are generated for the message type when these fields are changed in the material master.

Error Handling and Restart Considerations

..................................................................

On SAP side, transaction BD87 will be used for error correction & reposting of IDOC.

On XI side, SXMB-MONI transaction will be used as a central monitoring tool to reprocess failed messages.

Thanks,

Satya Kumar

Reward points if it is useful

[Former Member]

HI SV,

For this senario u required to follow 4 steps

I) You need to create RFC destination in "SM59"

2) Create Port through which the Idoc will process and assign the port to the above Created RFc destination and transaction for this "WE21".

3) Create logical system in Transaction code "BD54".

4) Create Partner profile with outbound parameter in Transaction 'we20'

Below mentioned link will help with screenshots

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd...

Thanks

Sai

PS: kindly reward points if helpful