|
Title Purpose Prerequisites
Data packages can contain both generic materials and single materialsif data package creation could not be completed for the genericmaterial that was sent last. The distribution logic ensures that every data package with a genricmaterial also contains all the changes to the variants of the genericmaterial. This, therefore, ensures that the changes to the genericmaterial and its variants can be sent in an IDoc at a later time. In addition to the distribution of master data changes, the simulationmode enables the user to check the paramaters that have been selectedfor data package creation, without actually having to send any data. Inaddition, the user can also select to have a detailed distribution loggenerated by the system. To ensure that data packages and parallel processing are usedcorrectly, the user must ensure that the selection parameters for datapackage creation are correctly configured. The most important selectionparameters are detailed in the next section of this document. Selection User selects the message type that is to be used. Only message type ARTMAS or associated message types can be used withthis report to distribute master data changes. User can choose to process data in data packages or using parallelprocessing. User enters the name of a valid aRFC Server Group. If data packageprocessing without internal parallel processing is to be used formaster data distribution, this field can be left empty. If data is to be distributed internally using parallel processing, usethis selection parameter to define a maximum number of parallelprocesses. This limit will not be exceeded when data is distributedeven if the server group that is bein used does not allow more than thedefined number of processes to be used. This means that other processescan be run on the same server group at the same time, without all av ailable resources being used to distribute changes to master data. Targets (limitation of main memory consumption/parallel processing) canonly be achieved most efficiently if the selection parameters for datapackage creation have been configured appropriately. For each logistical material unit (single material or generic materialwith all relevant variants), the system checks if one of the parametersfor data package creation has been exceeded. If this is the case, datapackage creation is completed and the package is sent. Note that thedata package creation process groups different logistical materialunits into a single package when one of the parameters that is used isactually undercut. The dimensions of these parameters should not,therefore, be too limited. Depending on the parameters that areselected for data package creation, a package can contain both genericlmaterials and single materials. Data package creation aims to create exactly the right amount of datapackages - not too many but not too few. If too many data packages arecreated (for example, one data package for each individual material),too many individual RFC (parallel processes) have to be managed andcommunication requirements become excessive. It could also be the casethat the distributing processes cannot distribute the new packagesquickly enough into processing. If too few data packages are created,main memory consumption cannot be restricted enough. It may also be thecase that larger, individual data packages may dominate the overalldistributio runtime despite the magjority of the other packages alreadyhaving been processing in a worklist. Using data package creation correctly is reliant on the fixed datastructure on which master data distribution is based, as well as on theavailable system resources. It is, therefore, very difficult to makegeneral recommendations. Default values are displayed on the selectionscreen. The simulation mode also empowers the user to monitor theselected parameters without first having to trigger distribution. Thismeans that no parallel processes have to be triggered, no IDocs aregenerated and no change pointers are flagged as having been previouslyprocessed. Defines the maximum number of materials per process. The variants of ageneric material are counted as a single material. As the variants haveto be processed in the same data package as the base generic article,the number of materials in the package may actually exceed the valuethat has been entered by the user. Defines the maximum number of change pointers per process. If thisvalue is exceeded, the data package will contain few materials than the'Number of Materials Per Process'. As the variants always have to beprocessed in the same data package as the base generic material, thedata package may contain more process change pointers than the maximumnumber entered by the user. The system can generate a detailed log for master data distribution.Alternatively, the user can choose to simulate distribution. Log can be output on the screen or in the spool list for the job. When distribution is simulated, the change pointers are read and datapackages are created in accordance with the parameters described above.When distribution is simulated, a log detailing the process is alsocreated. If medium-sized packages are used in distribution simulation,the amount of main memory consumed represents an approximation of theamount of main memory that would be used, were distribution actually tobe run. Output Displays the task number (sequence number), the number of materials andchange pointers per process, thus indicating the quality of datapackage creation. Displys the task number (sequence number), the start, end and runtimeper task, the server and the number of parallel processes duringruntime, thus indicating the quality of data load distribution. Displays the generic materials sent, the number of variants and thetotal number of change pointers per generic material and variant. Logs start time, end time and the runtime for the individual stepsduring processing (for example, read change pointers, structure keytables). Displays the number of materials sent subdivided into genericmaterials, variants and other materials (for example, single materials)as well as selection parameters (number of materials per process,number of change pointers per process, number of parallel processes). Task Materials Change Pointers 1 + 11 + 1.041 2 + 11 + 1.041 .... 98 + 11 + 1.041 99 + 11 + 1.041 100 + 11 + 1.041 Task Start End Runtime ServerNumber of Parallel Processes 00000001 + 14:18:39 + 14:19:01 + 00:00:22 + PWDF0635_AL0_55 +1 00000002 + 14:18:39 + 14:18:49 + 00:00:10 + PWDF0636_AL0_55 +2 00000003 + 14:18:39 + 14:19:11 + 00:00:32 + PWDF0635_AL0_55 +3 00000004 + 14:18:39 + 14:18:49 + 00:00:10 + PWDF0636_AL0_55 +4 00000005 + 14:18:39 + 14:19:14 + 00:00:35 + PWDF0635_AL0_55 +5 00000006 + 14:18:40 + 14:18:49 + 00:00:09 + PWDF0636_AL0_55 +6 00000007 + 14:18:43 + 14:19:09 + 00:00:26 + PWDF0635_AL0_55 +7 00000008 + 14:18:43 + 14:18:53 + 00:00:10 + PWDF0636_AL0_55 +8 00000009 + 14:18:47 + 14:19:10 + 00:00:23 + PWDF0635_AL0_55 +9 00000010 + 14:18:47 + 14:18:55 + 00:00:08 + PWDF0636_AL0_55 +10 ... 00000099 + 14:20:33 + 14:20:49 + 00:00:16 + PWDF0635_AL0_55 +10 00000100 + 14:20:33 + 14:20:49 + 00:00:16 + PWDF0635_AL0_55 +10 Generic Material,,Variants,,Change Pointers SA10VAR___00001 + 10 + 1.041 SA10VAR___00002 + 10 + 1.041 SA10VAR___00003 + 10 + 1.041 .... SA10VAR___00099 + 10 + 1.041 SA10VAR___00100 + 10 + 1.041 Task Materials Change Pointers 1 + ,,,,31 +,,,,3.069 2 + ,,,,31 + ,,,,3.069 3 +,,,,31 +,,,,3.069 4 +,,,,31 +,,,,3.069 5 +,,,,31 +,,,,3.069 6 +,,,,31 +,,,,3.069 7 +,,,,14 +,,,,1.386 Task Start End Runtime ServerNumber of Parallel Processes 00000001 + 15:14:42 + 15:15:20 + 00:00:38 + PWDF0635_AL0_55 +1 00000002 + 15:14:43 + 15:15:22 + 00:00:39 + PWDF0636_AL0_55 +2 00000003 + 15:14:43 + 15:15:25 + 00:00:42 + PWDF0635_AL0_55 +3 00000004 + 15:14:43 + 15:15:19 + 00:00:36 + PWDF0636_AL0_55 +4 00000005 + 15:14:44 + 15:15:28 + 00:00:44 + PWDF0635_AL0_55 +5 00000006 + 15:14:45 + 15:15:22 + 00:00:37 + PWDF0636_AL0_55 +6 00000007 + 15:14:45 + 15:15:10 + 00:00:25 + PWDF0635_AL0_55 +7 Task Materials Change Pointers 1 + 12 + 1.044 2 + 12 + 1.044 3 + 12 + 1.044 4 + 10 + 942 5 + 10 + 990 6 + 10 + 990 7 + 10 + 990 8 + 10 + 990 9 + 10 + 990 10 + 10 + 990 11 + 10 + 990 12 + 10 + 990 13 + 10 + 990 14 + 4 + 396 Task Start End Runtime ServerNumber of Parallel Processes 00000001 + 18:18:06 + 18:18:50 + 00:00:44 + PWDF0635_AL0_55 +1 00000002 + 18:18:06 + 18:18:44 + 00:00:38 + PWDF0636_AL0_55 +2 00000003 + 18:18:06 + 18:18:18 + 00:00:12 + PWDF0637_AL0_55 +3 .... 00000012 + 18:18:18 + 18:18:27 + 00:00:09 + PWDF0637_AL0_55 +10 00000013 + 18:18:22 + 18:18:43 + 00:00:21 + PWDF0636_AL0_55 +10 00000014 + 18:18:27 + 18:18:31 + 00:00:04 + PWDF0637_AL0_55 +10 Generic Material Variants Change Pointers SA3VAR____00001 + 3 + 348 SA3VAR____00002 + 3 + 348 .... SA3VAR____00008 + 3 + 348 SA3VAR____00009 + 3 + 348 SA3VAR____00010 + 3 + 348 Runtime Measurements Data Package Creation + Parallel Processing: Runtime,,Number of Materials,,Maximum Materials,,MaximumPointers,,Number of Packages 9 min. 11 sec.,,5,,20,,3.000,,170 4 min. 26 sec.,,10,,20,,3.000,,170 3 min. 41 sec. ,,15,,20,,3.000,,170 3 min. 30 sec.,,15,,40,,3.000,,107 3 min. 18 sec.,,20,,40,,3.000,,107 Runtime Measurement for RBDMIDOC In Series (Reference Measurement): Runtime,,Number of Materials,,Maximum Materials,,MaximumPointers,,Number of Packages 31 min. 04 sec.,,1,,0,,0,,1 |