change pointers Vs message control , difference?

[Former Member]

can any one tell me the difference between change pointers method of sending data and sending data by message control method?

n. bhardwaj

nehabhardwaj01@gmail.com

[Former Member]

> can any one tell me the difference between change

> pointers method of sending data and sending

> data by message control method?

> n. bhardwaj

>

> nehabhardwaj01@gmail.com

message Control will be generating one server to another server.

But change pointers generate Two servers contains same data will trigging

[Former Member]

hi neha,

change pointer will distribute master data, message control will distribute transactional data.

u can go thro this.

Change Pointer (Master Data Distribution) Purpose

If you want to distribute master data changes with the SMD tool (Shared Master Data), changes to the master data objects are flagged for distribution by change pointers ( ® Master Data Distribution).

The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.

The master IDoc is then passed to the ALE layer, which sends it to all interested systems.

The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.

You can increase the rate of processing by using the Analyze Change Pointer and Reorganize Change Pointer functions.

Prerequisites

You have created change pointers.

Activities

Checklist to keep the change pointer tables as small as possible:

Message Control is a "service program" for other applications. It is initiated via ABAP function modules. An application that uses Message Control must

Call the Message Control

Transfer files which should be compared with the combinations defined in Customizing.

Provide a processed program, that is called from the Message Control, if the transferred data corresponds with the combinations defined in Customizing

Features

The condition technique in the R/3 System is used to formulate the data combinations required. If the current application data corresponds to the conditions defined in Customizing, message determination was successful and created a message default. If the application supports it, the proposal can be changed (processed).

As a result the message is processed immediately or at a defined time. The processing status of the message is stored in a status record. If the application supports it, a processing log is written as well.

Message Control scenarios:

· The credit limit has been exceeded in a sales order, whereupon the block indicator is assigned. The Message Control should respond to the block indicator by printing out this customer’s account history.

· A document is released and receives a corresponding status in its data record. The Message Control should thereupon issue a release message.

There are also applications which can "switch off" message determination and directly generate the message default.

Message Control and connection to the R/3 application

Message control

Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.

In outbound programs(function module) that use message control the key of the

application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the

message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.

The parameteers passed to the function module are

IMPORTING PARAMETERS

OBJECT LIKE NAST

It contains documents key.

CONTROL_RECORD_IN LIKE EDIDC

It contains the partailly filled control record

EXPORETING PARAMETER

OBJECT_TYPE

CONTROL_RECORD_OUT LIKE EDIDC

TABLES

INT_EDID LIKE EDIDD

The internal table used to fill the data records in the same order as they exists in

the IDOC.

The important parameters that should be filled in the custom function module are

CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.

===========================================

Message control and output type. In R/3, message control is a mechanism by which documents are output based on certain selection criteria, requirements, and sequences. Message control determines the type of document, its timing, number, and medium (print, fax, ALE, or EDI.). Outbound messages in SD (Sales and Distribution) and MM (Materials Management, Purchasing) are created and processed by message control records. The output records are stored in the NAST table.

Message control uses the condition technique. The conditions for creating an output message are stored in condition tables that have selection fields picked from a catalog of application fields/tables. To determine if an application document qualifies for output, search strategies are used through access sequences, output procedures, and requirements. Once a message qualifies for output, message control modules use the parameters set in the condition type or output type to determine the timing of transmission and the medium of the message. The output type also specifies the program or module to be invoked to create the output.

Message/output determinations are concepts applicable not only to EDI and ALE, but also to other output mediums.

Regards...

Arun.

Reward points if useful.

[paruchuri_nagesh]

hi

in change pointers

u can send master data in these whenever changes made to a material these changes automatically replicated in target client systems with out any user interaction

for these u have to use tcodes bd50(enable messages for change pointers) bd52(specify fields change pointers to be written) bd61(enable change pointers globally)

in messagecontrol

user can create out type for an application document and also control thier medium of exchange means whether to send print out put or faxing the message

for this u have to maintain condition records by using tcode MN05

in message control u can send transactional data too

reward if u find useful

regards

nagesh .paruchuri

[varma_narayana]

Hi Neha..

This gives u the Overall idea on this:

We can Send IDOCs between systems in 3 ways.

For Master Data in ALE

1. Manually by executing a Application program

For Eg : BE10 - for Sending Material.

2. Change Pointer: To distribute the Changes to Master data automatically.

Tcodes: BD61, BD50 and Statndard program RBDMIDOC.

Tables: BDCP, BDCPS

For Transactional data in both ALE and EDI

3. Using Message Control

This is a technique to generate IDOCs for Transaction documents like Sales order, Delivery Note etc.

Tcode: NACE.

Tables: NAST.

Program RSNAST00 and RSNASTED.

<b>reward if Helpful</b>