Transfer Mode
In order to recognize changes in the master data objects, POI uses SMD functions (shared master data tools) that already exist in the standard R/3 System. For further information on SMD tools, see the R/3 Library, Cross Applications
® BFA ® BFA-ALE /Programming.Choose Distribution using message types ® Master Data Distribution ® Processing outbound master data
When downloading data in POI, you have the choice between two modi, ‘complete’ or ‘changes’.
Transfer mode Complete: If you select Complete mode, all the master data corresponding to the selection criteria specified in the master data selection screen is sent. Change pointers for message types for master data objects relevant to the download to the external optimization system are set to ‘processed.‘ This ensures that if data is changed and transferred at a later date, only the data changed since the latest complete transfer will be downloaded.
Using reduced message types for POI instead of basic ones prevents problems if another application that is using change pointers together with a basic message type such as MATMAS updates, activates or deactivates the POI change pointers. Before you decide to use message types together with change pointers, make sure you won‘t run into such problems. |
Transfer mode Changes: If you select change mode when master data objects are entered at a later date, only data that has been changed since the latest complete download is sent. Changes in this case include new entries, changes to objects and deletions. A complete data download takes place for master data objects that are not supported by the change mode. In transfer mode change, as in the case of a complete master data download, all change pointers for message types that are sent to the external optimization system are set to ‘processed’. |
Change Pointers
Depending on the message types that were set in Customizing, change pointers are written when changes are made to a master data object. POI processes the change pointers, which in turn cause those master data objects that were changed in R/3 to be sent again to the external logical system.
When making Customizing settings for POI, you must also specify the reduced message types that will be sent to the external system. POI uses the settings, reads the message type change pointers, and processes them. (See IMG for information on Customizing settings for activating the writing of change pointers.)
The following objects are supported when downloading master data changes:
Make sure obsolete and processed change pointers are deleted periodically. Otherwise, performance could slow down.
If the external system receives an IDoc of an object, all information pertaining to it must be replaced completely with the new information.
In order to download changes in POI, you must make the appropriate settings in Customizing.
To register and process data changes in POI, you must activate the writing of change pointers.
You must also activate the usage of change pointers in Customizing under Data Transfer Parameters for POI® Define General Settings for Data Transfer Parameters. If this setting has not been maintained, the change pointers are not read or updated, nor is it possible to download data changes.
See also Procedure: Customize Settings, Step 3.
Reduced message types and the download of data changes :
If you are using the data changes download together with reduced message types, keep in mind that a material master IDoc will only be downloaded again if the changed field in the material master is also contained in the reduced message type. If a field is changed in the material master and it is not contained in the reduced message type, the corresponding material IDoc will not be sent again. Changes in the material master are registered by individual fields.
No change pointers are written if changes are made to the material master long text (segments E1MTXHM and E1MTXLM) and the IDoc is not resent.
In the case of BOM and routing IDocs, however, data changes are registered for the entire object. Thus the change in a specific field of a BOM or routing will not be registered. Only the BOM or routing itself will be registered as having been changed. For this reason, it could happen that a BOM or routing IDoc is sent even though one of the fields that was changed is not contained in the reduced message type.
Further information regarding the download of data changes, consult the POI Implementation Guide (IMG) under Logistics General ® Supply Chain Planning Interfaces ® Production Optimization Interface.
