Transaction for using change pointer technique in ALE -IDOCS

Hi,
please let me know the following points.
1: while using change pointer technique , any change in the sale order(any field ) will trigger IDOC or only specific field change. Or do we have to specify field on which we want to trigger IDOC?
2:When IDOC gets genrated from change pointer , does it contain complete sales order or only change fields?
3:Do we have Native format of IDOC in 4.6c ?? XML format??
Please reply soon.

Hi,
For the changes to be carried over by change pointers, the steps followed are,
If it's gonna be the vendor master for which change pointers needs to be activated,
- goto SALE transaction ->Modelling and Implementing business processes ->Replication of Modified data -> Activate Change pointers - generally / for message types.... or as said in the earlier post, alternatively BD61/BD50.
- Schedule a background job for program RBDMDIOC providing the message type(CREMAS) for which the change pointers needs to be processed.
- Now for any changes made to the vendor via transaction XK02, automatically CREMAS IDocs would get generated with the IDoc carrying the changed fields in it. You would also be able to find the number master and communication IDocs generated from the joblog of the scheduled RBDMIDOC background job.
~ Bineah.

Similar Messages

Reading deleted field values using change pointer

hi
i am triggering DEBMAS06 using change pointer technique for XD01/02/05/06 transactions.
now when i delete data(make nulll values) in partner functions the generated IDOC is not showing the complete field itself.when i am deleting the field value and making it null the IDOC must send the fields with null values.but unable to trace out how to do this.
can anyone let me know how to handle this situation?
and i have extended DEBMAS06 with customer hierarchy data i.e. KNVH.i have written change pointers.now how can i populate these fields into my extension?

Hello Moorthy,
1. This message function in the Idoc is populated as 005 then it should replace the entrire values while posting,
2. To populate KNVH extension you have to populate this only if you have KNVV data.. so you can either create enhance menti perfrom FILL_SEGMENT_E1KNVVM i(nf Function moduler MASTERIDOC_CREATE_DEBMAS) inclduer LVV01F01. or you can write the logic in BAdi CUSTOMER_ADD_DATA->FILL_ALE_SEGMENTS_OWN_D or in user eixt EXIT_SAPLVV01_001.
Regards
Naresh

What is the use of change pointer technique in IDOC

hi
could anybody suggest me
what is the use of change pointer technique and how to use it
thank you
kalyan.

Change pointers are used for changes to the master data objects are flagged for distribution by SMD Tool.i.e.shared Master Data.
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61
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.

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

Change pointer technique for idocs

I have to generate idoc whenever some fields of the sales order changes (Transaction VA02)
I thought of doing this using change documents. There is a standard change document object VERKBELEG   for sales order.
In transaction BD52 for the message type ORDRSP I have mentioned the fields names as below (my idea is to generate the idoc when these fields of the sales order changes).
VERKBELEG          VBAP          ABGRU
VERKBELEG          VBAP          KWMENG
VERKBELEG          VBAP          KZWI1
VERKBELEG          VBAP          KZWI2
VERKBELEG          VBAP          MATNR
VERKBELEG          VBAP          PRCTR
VERKBELEG          VBEP          WMENG
VERKBELEG          VBKD          KDKG3
VERKBELEG          VBPA          PARNR
It seems that the report RBDMIDOC will not support for transaction data.
When I tried to execute the report RBDMIDOC by giving message type    ORDRSP in the selection-screen it gave the following error
Message type ORDRSP cannot be sent with change pointers
Message no. B1157
Diagnosis
You attempted to send message tyoe ORDRSP. Unfortunately you cannot choose data for this message type using change pointers.
System Response
The system does not carry out the action.
Procedure
If message type ORDRSP is for master data, it can be sent directly. If it is for transaction data, the message tyoe is sent automatically via the transaction.
is there a way to generate idoc via the transaction VA02 (sales order change) instead of executing the report
RBDMIDOC

Hi Srinivas,
This can be done but some development would be required.
If you know about requirement routines ( transaction VOFM ) you can create your own requiremnet routine for application V1. For reference see routine 002 for V1 .
( program LV61B002 ). You can create your own req routine say 901 for V1 and then assign it in output procedure in NACE for BA00. Output will be generated only when you pass a SY-SUBRC = 0 from the custom routine that you will create .
But another problem would be how to determine whether the field values you have mentioned has changed or not.
You can use user exit MV5AFZZ , subroutine SAVE_DOCUMENT_PREPARE , to analyze your fields .
Here you have XVBAP[] table with ( user ) changed values in current transaction , YVBAP[] with current database state at runtime. ( same is true for XVBKD & YVBKD ) . You can analyze the values and then set a flag here to say that "Generate Output" or "Supress Output" . This single caharacter flag "X" or space you can pass to ABAP memory , which you can read ( import ) in requirement routine ( VOFM ) and then set SY-SUBRC = 4 or 0 depending on this flag value.
Above solution will not mean any modification to SAP .
Otherwise you can also look at OSS note 395569 wherein its a modification but you can achieve desired results.
( You can use the code given here as refernce and put this same code with the solution I have proposed above with some additional checks. )
If answers were helpful reward and close.
Cheers.

End User Transaction for Mass Change Sales Orders

Hello,
Transaction MASS can be used to change sales orders using object type BUS2032, however, end users are not allowed access to MASS.
In most other cases, the object types can be accessed by individual transactions, for example, MEMASSPO for BUS2012 and XD99 for KNA1.
But I cannot seem to find a similar transaction for object type BUS2032, does anyone know whether one exists or how to create such a shortcut.
Thanks,
Jake.

Hi
See SAP Note 483303 - BUS2032: Only sales orders of category VBAK-VBTYP = 'C'
Regards
Eduardo

IDOC to XI (Using Change Pointer) - Error

Hi all,
I have 1 scenario to update external GL master data using XI. in this case i already configure the source system (SAP) to sending the IDOC to XI whenever got changes.
BD61 ---> Activate Change Pointer Globally,
BD50 ---> Activate Change Pointer for GLMAST Message Type.
SM59 ---> RFC destination for XI system (PX6CLNT300).
BD54 ---> Logical System source (ST6CLNT100) and target xi (PX6CLNT300)
WE20 ---> Partner Profile for XI (PX6CLNT300).
BD64 ---> Create Distribution Model View. Sender = ST6CLNT100, Receiver = PX6CLNT300 and Message Type = GLMAST
The system can generate the IDOC whenever changes happen with running program RBDMIDOC. but the got error with no sender / receiver information in WE05.
Please advise any step that i have to do ?
Best Regards
Fernand

Hi Matias,
Thank you for your answer. The problem is because i had used wrong logical system in my distribusion model. The system using not common logical system. nomarly it will use "PX6CLNT100" but in my system the basis people using different logical system that's why the GLMAST IDOC cannot pass throught to XI system.
Best Regards
Fernand

Transaction for Customer changes

Hi,
Did we have any specific T-code to view Customer changes, Which will show all the changes happened as on date.
and also i found 2 tables for customer changes.
FD15 Transfer customer changes: send
FD16 Transfer customer changes: receive
What is the difference between FD15 and FD16.
Thanks.
Pardha

customer changes can be viewed through OV51 or S_ALR_87012182. they're both the same except the latter can be found in the FI nodes.
you use FD15 to create a customer in another company code, which already exists in a different company code. the result of this transaction is a file that you use to receive using FD16.
regards.

Code sample for using change document function modules

Can someone send me some sample code for using function modules CHANGEDOCUMENT_READ_HEADER and CHANGEDOCUMENT_READ_POSITIONS? I'm specifically looking for changes that occured to the standard price field in the material master (MBEW-STPRS) and I need to pull the most recent price change for a given material. I'm not sure how to write the code efficiently since I don't have a date to pass (again, since we're looking for the most recent change.)
Thanks!

hi check this..
CHANGEDOCUMENT_READ_HEADERS
Example:
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING
objectclass = 'EINKBELEG'
objectid = l_objectid
username = space
TABLES
i_cdhdr = lt_cdhdr.
LOOP AT lt_cdhdr WHERE udate IN s_aedat.
CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
EXPORTING
changenumber = lt_cdhdr-changenr
TABLES
editpos = lt_editpos.
LOOP AT lt_editpos WHERE fname = 'LOEKZ'
AND f_new = 'L'.
p_desc = text-r01. " Cancel Contract
ENDLOOP.
ENDLOOP.
CHANGEDOCUMENT_READ_POSITIONS
Example:
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING
objectclass = 'EINKBELEG'
objectid = l_objectid
username = space
TABLES
i_cdhdr = lt_cdhdr.
LOOP AT lt_cdhdr WHERE udate IN s_aedat.
CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
EXPORTING
changenumber = lt_cdhdr-changenr
TABLES
editpos = lt_editpos.
LOOP AT lt_editpos WHERE fname = 'LOEKZ'
AND f_new = 'L'.
p_desc = text-r01. " Cancel Contract
ENDLOOP.
ENDLOOP.
Check this link.
http://www.sap-img.com/mm001.htm
<REMOVED BY MODERATOR>
venkat.
Edited by: Alvaro Tejada Galindo on Mar 18, 2008 4:05 PM

How to send changes in the Database Table Periodically using Change Pointe

Hi,
How to send changes in the Database Table to the external system Periodically using Change Pointers.
Thanks & Regards,
Gopi.

That depends on what table you are referring to.

Transfering data from ztable across the r/3 systems by using change pointer

hi all,
what we have to do at the field of domain level when we are transfering data from custom table across the r/3 systems by using change pointers.

Hi Deepak,
Check this blog.. it gives a very good explanation on extraction of data through function modules...
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Hope it helps..
Regards
Manick
Message was edited by:
Manickavasagan M

Looking for materials in badi bapi and ale idoc

dude
i got materials from <removed by moderator> and other few sites also.i need to know the full structure of bapi badi and ale idoc.
ppl who are working in these areas pls post materials as well the real time issues facing in their comp.so that i can get a wide knowledge.
pls post........
waiting ..
thnx in advance.
Edited by: Jan Stallkamp on Aug 18, 2008 8:16 PM

Check these links before posting any further:
[Step 1|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] <= this one is important for you dude!
[Step 2|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] <= see the "Why is no one answering" docs!
[Step 3|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] <= check your own profile dude!
[Step 4|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] <= optional, but for a good cause!
[Step 5|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] <= not applicable for you yet
* * * * * Please read the rules if found usefull! * * * * * *

Best practices for using Vanishing Point tool?

Hi All,
I'm wondering if anyone can give me some guidance on using the vanishing point tool...
Basically I've tried using the vanishing point tool (in PS CC) on a couple of projects and it always takes me a hell of a lot of time, mainly fiddling around to get the correct proportions.
A perfect example is a project I'm working on today, I have an exhibition stand which is pretty straight forward, all flat, rectangle surfaces. I have the correct dimensions from the supplier of the exhibition stand which I've designed the artwork to scale. Now when I try to apply the artwork to the relevant sections of the stand using the vanishing point tool, the artwork stretches then I have to resize it but each time I resize the artwork it seems to get dissorted and the artwork now looks poor quality and there is loads of space above and below the artwork. This is really puzzling me.
I've seen a design from another company and they have applied the artwork to the stand with no problems by the look of things, it looks crystal clear so I'm obviously doing something wrong.
If anyone could point me in the right direction, which I understand could be difficult to do because it's hard to determine what I'm doing wrong just from this post. Therefore any tutorials that throughly explain how to effectively use the vanishing point, would be very much appreciated.
Thanks for your time
James

Hi Richard,
If you need to configure dynamic pricing that may vary by tenant and/or if you want to set up cost drivers that are service item attributes, you should configure Billing Tables in the Demand Management module in 10.0.
The cost detail functionality in 9.4 will likely be changed to merged with the new pricing feature in 10.0. The current plan is not to bring cost detail into the Service Catalog module.

Capturing change code/Reason code in CAT2 transaction for time change

Experts,
Wanted your suggestion and expertise in a solution where in CAT2 if a user changes the time/wbs element/tax area/work type he should be forced to put the reason code for change. The change event would populate/capture the change code, reason for change at cell level in CAT2
Your pointers would be of great help

The following enhancements are required to achieve the new pop up window functionality:
1.     A new customer field should be added to the CATS time entry screen in the CATSDB.
2.     A new check table should be created in CATSDB containing the allowable drop down entries for the new field.
Customer fields are inserted into the CI_CATSDB structure. This structure is contained in the database table for the Time Sheet (CATSDB).
Steps:
1. Create a customer project using the SAP enhancement CATS0005.
2. On the initial project administration screen, select the Enhancement components field and choose Change.
3. Select the entry CI_CATSDB and choose Edit -> Components.
4. Create the structure CI_CATSDB.
5. Insert the new field to the Time Sheet database table into the structure.
    Select the data dictionary type CHAR
6. Check and save the structure.
7. Activate the structure.
8. In the Cross Application > Time sheet section of the IMG Choose Make field assignment.
9. Assign the new field to the view.
10. Assign a number from 1 - 10 specify the name of the field, u201CChange Reasonu201D.
Then Conditions Check for New Field:According to requirement

Ale/Idocs ..... what is the role of message control

Hi Guy s..
Can Any one.. tell me.. Importance of message control , Stand alone and change pointer s in Ale Idoc''' and where to use...

Hi,
Message Control:
With Message Control is documents are output based on
certain conditions. In ALE scenarios this is basically used for transfer transaction data (fulfilling configuration settings defined in message control) from one system to another system.
Example: If you want to send purchase order IDocs from customer to vendor system using ALE. When saving of purchase order the IDocs should be triggered. Further the IDocs should only be sent when the purchasing document fulfils certain conditions - purchase document of a certain document type only needs to be sent. By output control we can configure the conditions and the timing (when the document should be triggered) and using ALE (as interfacing technology) we can send IDocs (containing application data fulfilling conditions) from one system to another system.
For More Info on Message Control,
/people/gajendra.bhakuni/blog/2007/03/13/message-control-output-control-for-ale
Change Pointers:
Change pointers are the mechanism through which you can send data to another SAP system or external system if there is a change happening to specific fields of master data.
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.
do the following steps for Change pointers ::
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
go through this link which ll give you detail about the change pointer
http://www.angeli.biz/www5/cookbooks/workflow/workflow_30/docu.htm
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
http://help.sap.com/saphelp_470/helpdata/en/dc/eb683c00e8a646e10000000a11402f/frameset.htm
Regards,
Padmam.

Transaction for using change pointer technique in ALE -IDOCS

Similar Messages

Maybe you are looking for