After a control recipe has been created, it is downloaded to the destination assigned to the corresponding phases of the process order. This section describes
how the download of a control recipe can be started
how the control recipe is transferred to its destination
Starting the Download
The function for downloading a control recipe can be started in the following ways:
automatically via a background job defined in Customizing
The download job selects all control recipes that have not yet been downloaded according to their status. Depending on your Customizing settings, it is started either
in regular time intervals or
whenever a new control recipe has been created
All control recipes that can be processed without error are downloaded via this function after they have been created.
manually within the control recipe monitor
You need this option
if you have not defined the background job for downloading in Customizing
if an error occurred during the download of a control recipe and there are no new control recipes to trigger your background job
If you want to download all control recipes with the status "created", you can manually start the background job: see Starting Download Job for Control Recipes .
However, this is only possible if the send job defined in Customizing is triggered by the event "New control recipe" (SAP_NEW_CONTROL_RECIPES).
Alternatively, you can select individual control recipes and send them online: see Downloading Control Recipes Online .
For information on how to access the control recipe monitor, see Accessing the Control Recipe Monitor .
Transfer of the Data
The transfer of the control recipes to external systems is carried out via transactional remote function call (tRFC) as program-to-program communication. The tRFC ensures that each call is carried out only once. The sequence of the calls is not changed. If the target system is not active when the call takes place, the tRFC is repeated according to a repetition rate or duration that can be defined by the user.
The execution of a tRFC is documented in a log which you can access from the control recipe monitor: see Displaying Transactional RFC Log .
For information on how to access the control recipe monitor, see Accessing the Control Recipe Monitor .
For technical details on the transfer of control recipe data and tRFCs, refer to the documents PI-PCS Interface and to the document BC Remote Communications . You can access these documents via the Further Reading menu.