diff b/w change pointers amd message control

[Former Member]

hi,

can any one just differenciate b/w chnage pointers and msg control.

as far i know..

for change pointers the logic to create is build in application program..

i.e, we can find selection program for change pointers(masteridoc_create_sd_<msgtype>) in the stand alone program (bd10,12,14).

for msg ctrl..we need to configure the out bound idoc(idoc_output_msgtype) seperately. it's a seperate logic which is not built in application program.

if am wrong plz correct me n update me

[Former Member]

Hi,

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

[Former Member]

Basically, in ALE , Change Pointers are used for distributing Master data whereas Message Control for Transactional data

[Former Member]

Hi venkat

Q) Change pointers?

check General scenariao for Change pointers ::

Steps to configure change Pointers:

1.Activate the change pointers globally(BD61)

2.Activate the change pointers for individual message types(BD50)

3.Schedule the program RBDMIDOC to run periodically on the sending system.

To Delete Change pointers use transaction BD22 and the standard program is RBDCPCLR

1) Tcode BD61---> check the change pointers activated check box

save and goback.

2) Tcode BD50---> check the MATMAS check box save and comeback.

3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.

4) Tcode BD52---> give message type : matmas press ok button.

select all what ever you want and delete remaining fields.

save & come back.

5) 5) go to Tcode MM02 select one material and try to change the description and save it

it will effects the target systems material desciption will also changes

6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute

give Message type : MATMAS and Executte

Change pointers are R/3 objects that mark changes to SAP master data. Change pointers are managed by mechanisms in a Shared Master Data (SMD) tool and are based on Change Document (CD) objects. CD objects record the changes occurring to master data at a field level. These changes are stored in tables CDHDR (header table) and CDPOS (detail table). ALE configuration provides a link between CD objects and change pointers. Internal mechanisms update tables BDCP and BDCPS, which host the change pointers. While CD objects are application-data-specific, the processing status of change pointers is message-type-specific. Also, the ALE change pointers are activated first at a general level and then at the message-type level.

Reward points if helpful