Kontakt

Ansicht
Dokumentation

/DSD/HH_RAARTT - Define Allowed Route Transaction Types

/DSD/HH_RAARTT - Define Allowed Route Transaction Types

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing table you can define the allowed route transaction types for the upload depending on the settlement types and the settlement office. Several settlement types can be allowed for each settlement office.

For the flow logic this means that the data of the excluded tour transaction types are transferred even if an error message is generated during the automatic settlement run and the transaction requires manuall touch-up work.

To upload data the following settings have to be made:

  • Maintain Partner agreement
  • TA WE20

  • Partner type LS

  • Choose Logical system and maintain the relevant entries for the input parameters.

  • The following message types can be maintained in the input parameters:
  • /DSD/ROUTEACCOUNT_CCOCI0,,,,RA: Create Check-in/ Check-out data

  • /DSD/ROUTEACCOUNT_CCTRDT0,,,,RA: Transfer General control data

  • /DSD/ROUTEACCOUNT_CCUSVI0,,,,RA: Create Customer sales call data

  • /DSD/ROUTEACCOUNT_CDELFU0,,,,RA: Create Delivery execution data

  • /DSD/ROUTEACCOUNT_CENCAS0,,,,RA: Create Payment data

  • /DSD/ROUTEACCOUNT_CINV0,,,,,,RA: Create Invoices

  • /DSD/ROUTEACCOUNT_CIVPRT0,,,,RA: Create Confirmation via invoice print

  • /DSD/ROUTEACCOUNT_CORDER0,,,,RA: Create New orders

  • /DSD/ROUTEACCOUNT_CTDIST0,,,,RA: Create Tour Distance sheet

  • /DSD/ROUTEACCOUNT_CTTIME0,,,,RA: Create Tour Time sheet

  • The transaction code (BAPI) has to be maintained for each message type.

Customer-specific extensions for the relevant route transactions have to be created in the names spaces reserved for this purpose in the chapter 'Basic functions' in the IMG activity 'Define Route transaction types'. The corresponding flow logic for further processing needs to be reprogrammed.

It may, for example, happen that a delivery driver is not allowed to accept customer orders. Should he do so all the same, the data of the customer order will be transferred and manually edited in the settlement office later on.






ROGBILLS - Synchronize billing plans   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 3068 Date: 20240420 Time: 055808     sap01-206 ( 38 ms )