ale master data scenario integration with non sap syetem i.e seebeyound

[Former Member]

hi

we have a business process scenario integrating with non sap system (i.e seebeyound)

action code itemnumber plant code

a(add) material1 plant 2

d(delete) material 3 plant 6

etc

we have upto one million materials assigned to 300 plants

we have to send all the above data to non-sap system (see beyound)

should we go for a custom idoc and setup the rfc configuration for the two sytems.

or can you please help how to go for this scaneriao

[Former Member · Accepted solution]

Hi Anil,

Is this a one time transfer?

Idocs are ideal for sending frequent changes from one system to another. This is because idocs are really good when monitoring comes into picture. We can track idocs from source to destination and have logs to inspect at each stage.

If it is a one time transfer, you need to go for what is called a 'conversion'. Dump all records from source system into a file and import it at your source system. A file format ideal for both systems would be needed. Logs may be provided on the extraction and import ends.

I dont think that an RFC is ideal for this scenario as RFC's aren't ideal for large volume data transfers. Also it doesnt have any logging methods on the data transfer.

For large volumes, you can go for a composite strategy where you use conversions for initial loads and idocs for sending deltas or recent changes.

Regards,

Anand.

[Former Member · Accepted solution]

this is not one time.it is on daily basis.

please look at this scenario.what i need is how should i go for ale/idoc scenario for this one

Business case for Heiler Part/Plant Interface:

A key function of the Heiler PBC tool is to provide users a choice

between a "Global Catalog View" (e.g. all parts in the catalog) or a

"Local Catalog View" (e.g. the subset of parts in the catalog that have

a Material Master established for the user's plant in SAP). The "Local

Catalog View" is the default condition and encourages users to procure

parts that are on contract for their plant and potentially already

stocked as an inventory item at their plant. Parts that are not in a

user's "Local Catalog View" can only be procured as a spot buy purchase

order, requiring processing by a buyer.

The new Part/Plant interface is required in order for the Heiler PBC

tool to provide this "Local Catalog View" function. The Heiler

Part/Plant table will document what plants in SAP have a Material Master

record established for each part. SAP will maintain the Heiler

Part/Plant table using this interface. When a user performs a part

search in the Heiler PBC tool, the Part/Plant table determines if a part

is included in the user's "Local Catalog View".

[Former Member · Accepted solution]

Hi Anil,

your scenario should be possible using MATMAS IDoc which contains the plant data in segment E1MARCM.

You can use an initial load to send all materials to your catalog in the cutover and then use change pointers which will send out an IDoc whenever a Material is being changed in a relevant field.

The configuration steps you have to follow are:

- create logical system

- create RFC Destiantion

- create tRFC Port

- create Distribution Model

- create Partner Profile

- activate Change Pointers

- schedule job to create IDocs from Change Pointers

Have a look at SAP help: http://help.sap.com/saphelp_erp2005/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/4bf60b4bab1343a03c004d2cb3566d/content.htm

Be aware that some additional steps might be required in the tool you use to receive the data (i.e. seebeyond). You might need to setup a connection and processing rules there as well.

Regards

Christine

[Former Member]

Anil,

Going for a custom idoc does not depend upon your target system. It depends whether SAP has provided you a standard IDOC that can be used for your requirements or NOT. In this case I am not clear as to which Master data object you are talking about, but SAP has provided standard IDOC's for most the Master data objects, you can as well use one of those.

So, the IDOC's will be generated out of SAP and can be sent to See Beyond (I think you will have to configure a ALE e*Way or something like that on your side).

Regards,

Ravi

Note : Please mark all the helpful answers

[Former Member]

here is the functional design for this scenario and how to prepare the tecnical scenario.how should i go for idoc and ale scenarion in this process

Business case for Heiler Part/Plant Interface:

A key function of the Heiler PBC tool is to provide users a choice

between a "Global Catalog View" (e.g. all parts in the catalog) or a

"Local Catalog View" (e.g. the subset of parts in the catalog that have

a Material Master established for the user's plant in SAP). The "Local

Catalog View" is the default condition and encourages users to procure

parts that are on contract for their plant and potentially already

stocked as an inventory item at their plant. Parts that are not in a

user's "Local Catalog View" can only be procured as a spot buy purchase

order, requiring processing by a buyer.

The new Part/Plant interface is required in order for the Heiler PBC

tool to provide this "Local Catalog View" function. The Heiler

Part/Plant table will document what plants in SAP have a Material Master

record established for each part. SAP will maintain the Heiler

Part/Plant table using this interface. When a user performs a part

search in the Heiler PBC tool, the Part/Plant table determines if a part

is included in the user's "Local Catalog View".