Services

The following services are present in the Applications Manager in the Application Platform module for the Sales Order document type.

Navigate to the service definitions using the following path: Applications Manager > Application Platform > Process Modeling > Document Type > Sales Order > Order Fulfillment > Service Definitions

  • YCD_FTC_AUTO_RESOLVE - This service is used to resolve the fulfillment delay notification alert, and update the dates on the order lines that are delayed. It is invoked by the YCD_FTC_Auto_Resolve monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table:
    Table 1. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType AutoResolve
    NoteText YCD_FTC_AUTO_RESOLVE_NOTE_TEXT
  • YCD_FTC_CANCEL_ORDER_LINES - This service is used to cancel the order lines if the customer has not responded to the delay notifications. It is invoked by the YCD_FTC_Cancel_Lines monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table:

    For details about how this custom API can be customized see the corresponding section. The differences between this service and the YCD_FTC_AUTO_RESOLVE service are the arguments passed to the FTCHandler.

    Table 2. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType CancelLines
    NoteText YCD_FTC_CANCEL_LINES_NOTE_TEXT
    Figure 1. The YCD_fTC_aUTO_rESOLVE and YCD_fTC_cANCEL_oRDER_lINES services
    The order lines are canceled automatically by invoking the YCD_FTC_CANCEL_ORDER_LINES service and passing the appropriate arguments to the FTCHandler API
  • YCD_FTC_DELAY_ALERT - This service is used to update the order dates and send a notification to the customer. It is invoked by the YCD_FTC_Delay_Alert monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table. For details about how this custom API can be customized, see the corresponding section.
    Table 3. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType NextFTCDelay
    NoteText FTC_Delay_Alert_Note_Text
  • YCD_FTC_FIRST_DELAY_ALERT - This service is used to update the order dates and send a notification to the customer. It is invoked by the YCD_FTC_First_Delay_Alert monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table. For details about how this custom API can be customized, see the corresponding section. The differences between this service and the YCD_FTC_DELAY_ALERT service are the arguments that are passed to the FTCHandler custom API.
    Table 4. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType FirstFTCDelay
    NoteText FTC_First_Delay_Alert_Note_Text
  • YCD_FTC_INDEFINITE_DELAY_ALERT - This service is used to update the order dates and send a notification to the customer. It is invoked by the YCD_FTC_Indefinite_Delay_Alert monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table. For details about how this API can be customized, see the corresponding section. The differences between this service and the YCD_FTC_DELAY_ALERT service are the arguments that are passed to the FTCHandler custom API.
    Table 5. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType IndefiniteFTCDelay
    NoteText FTC_Indefinite_Delay_Alert_Note_Text
    Figure 2. YCD_fTC_dELAY_aLERT, YCD_fTC_fIRST_dELAY_aLERT, and YCD_fTC_iNDEFINITE_dELAY_aLERT services
    The order dates are updated and a notification is sent to the customer by calling the YCD_FTC_INDEFINITE_DELAY_ALERT service and passing the appropriate arguments to the FTCHandler custom API.
  • YCD_FTC_DELAY_EMAIL - This service is used to update the order dates and send a notification to the customer. It is invoked by the YCD_FTC_Delay_Email monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table. For details about how this API can be customized, see the corresponding section.
    Table 6. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType FirstFTCDelay
    NoteText FTC_First_Delay_Email_Alert_Note_Text
  • YCD_FTC_INDEFINITE_DELAY_EMAIL - This service is used to update the order dates and send a notification to the customer. It is invoked by the YCD_FTC_Indefinite_Delay_Email monitor event. This service invokes the FTCHandler custom API with the arguments listed in the following table. For details about how this custom API can be customized, see the corresponding section. The differences between this service and the YCD_FTC_DELAY_EMAIL service are the arguments that are passed to the FTCHandler custom API.
    Table 7. Arguments for the fTCHandler custom API
    Fields Description
    FTCDelayType IndefiniteFTCDelay
    NoteText FTC_Indefinite_Delay_Email_Alert_Note_Text
    Figure 3. YCD_fTC_dELAY_eMAIL, YCD_fTC_fIRST_dELAY_ EMAIL, and YCD_fTC_iNDEFINITE_dELAY_ EMAIL services
    The YCD_FTC_INDEFINITE_DELAY_EMAIL service is invoked to update the order dates and send notification to the customer by passing the appropriate arguments in the FTCHandler Custom API.
  • YCD_FTC_SEND_NOTIFICATION - This service determines what type of notification is needed and what the notification must state. This service is invoked by the FTCHandler custom API. This is used in all the services that are described until now. This service is illustrated in the following figure.
    Figure 4. YCD_fTC_sEND_nOTIFICATION service
    YCD_FTC_SEND_NOTIFICATION service defines the notification type and the content of the notification.
  • YCD_SetOrderDefaults_2.0 and YCD_SetOrderDefaultsOnChange_2.0 - These two services are invoked by the beforeCreateOrderUE and beforeChangeOrderUE user exits respectively. These user exits are called by the createOrder API and changeOrder API respectively. For more information about user exits and APIs, refer to the Javadoc. These services are used, in part, to set the promised delivery dates.
    Under the Arguments tab of the Set Order Promised Dates component in both the services, configure the advertised promised date that is used to calculate the first promised delivery date and the number of days after the first promised date, the second promised date must be set to by default. (this value cannot exceed 30). This service is illustrated in the following figure.
    Figure 5. The yCD_setOrderDefaults_2.0 and yCD_setOrderDefaultsOnChange_2.0 services
    The YCD_SetOrderDefaults_2.0 and YCD_SetOrderDefaultsOnChange_2.0 services determine the promised dates to be set on the order.

    Depending on the service you are configuring, you might have to configure the alert or email sender components.