Kontakt

Ansicht
Dokumentation

/DSD/ST_CPROF_VC - Define Tour Scenarios and Tour Status Profiles

/DSD/ST_CPROF_VC - Define Tour Scenarios and Tour Status Profiles

ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you decide which tour scenarios you want to use in DSD (including tour status profiles and follow-up activities).

The following tour scenarios are part of the SAP standard delivery:

  • Mobile delivery scenario
  • Mobile preseller scenario
  • Paper-based delivery scenario
  • Paper-based preseller scenario

You can create additional customer-specific tour scenarios. Note that the technical name of a customer tour scenario must start with Y* or Z* in the customer namespace.

Define tour status profiles

You must assign a tour status profile to each tour scenario. The profile shows the chronological order of tour processing in the form of status IDs. A tour status profile is provided for each of the standard tour scenarios.

You define the following in a tour status profile:

  • All tour status IDs that are attained in the relevant tour scenario in the defined sequence are entered in the tour profile.
Each tour status ID is only allowed once per tour scenario.
  • For each tour status ID, you can enter a predecessor tour status that must be attained before the new tour status can be set.
  • If you want the system to log a tour status, select the History field.
  • If you do not want it to be possible to reset processing steps that have already been carried out for the tour, select the No Reset field.
Note:
If the system has already performed difference determination, it is not possible to delete the result and repeat the difference determination process. The No Reset field must therefore be selected for the tour status Difference Determination Complete.
  • It might be the case in a tour scenario that a processing step is optional, but that this particular part of tour processing must be completed before further processing can continue.
Example: Loading confirmation in the mobile process
The system cannot continue with tour processing until the loading confirmation is successfully completed. In this case, the Max. Sequence field is set to the maximum sequence the tour is allowed to attain.
  • You can specify a function module for each tour status. The system then starts a follow-up activity with this function module. As soon as the tour has attained the new tour status, the system starts the defined activity. It can happen that the activity itself writes a tour status.

Define activities

In this IMG activity, you can assign several function modules to a tour status so that the system can start several activities. The system performs the activities asynchronously (IN UPDATE TASK), meaning that the following ABAP commands are not allowed in these function modules:

  • COMMIT WORK
  • ROLLBACK WORK
  • SUBMIT
  • CALL TRANSACTION
  • LEAVE TO TRANSACTION
  • CALL DIALOG
  • CALL SCREEN






Fill RESBD Structure from EBP Component Structure   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 3825 Date: 20240420 Time: 035205     sap01-206 ( 59 ms )