Configurations for End Tour Activities

Tour Details Review Configurations

• The drivers can select a different warehouse as the end warehouse depending on the Consider Multiple Warehouses setting of the tour. If the Consider Multiple Warehouses setting is set as No, then the app doesn’t permit the tour driver to select different warehouses and automatically assigns the start warehouse as the end warehouse. The end warehouse field becomes noneditable.
• The driver must be an associated user for the start and end warehouse.
• The codriver must be related to the start warehouse and the end warehouse.
• The Allow End Day Time Tracking setting in the tour template must be set to Yes to automatically determine the actual tour end date as the current date and time in the Consumer Goods Cloud offline mobile app.

Vehicle Details Review Confirgurations

• The driver can enter the odometer reading in miles or kilometers depending on the Distance Unit setting set in the sales org.
• The Consider Mileage setting in the tour template as Yes for the validation to be in place where the driver must enter a valid odometer reading.
• The driver must complete the vehicle condition check depending on the Consider Vehicle Status setting in the tour template. The driver can skip this step if you have set the Consider Vehicle Status as No.
• The Consider Vehicle Status setting as No or Only Status in the tour template for the driver to skip the selection of Vehicle Condition Status.
• The Allow End Day Time Tracking setting in the tour template as Yes to update Complete Release Time field on the desktop app with the actual end time.

Check-In Initiation

Consumer Goods Cloud includes relevant templates for check-in document via the demo data upload in Static Resources. The check-in templates are prepopulated with key fields along with the relevant fields to perform a product check-in and you don’t need to manually make these configurations. To customize these templates or create new check-in templates, you can configure these key fields along with the fields required for the template.

• In Tour Object Reference, order template with usage as Product Check In.
• In Order Template
  • Record Type as Truck Load
  • Document type as Product Check In
  • Responsible as the tour driver
  • Mobility Relevant as Yes
  • Creation Platform as Mobility
  • Product Check In Policy as Complete, Partial, or Optional based on the project requirements
  • Checkout type as SKU
  • Checkout Item presetting policy as Prepopulated
  • Consider Modification Reason field as needed for the display of the Reason Type field on the Product Check In page.
• Have order item templates for all types of inventory such as sellable and damaged and associate them with check-in order template.
• Have atleast one order item template must be marked as Main.
• Have Modification Reason field set depending on the behavior you need for the Reason Type field on the Product Check In page on the mobile app. You can declare this field as not required, optional, or enforce the user as needed.

The reason for the difference in quantity for the product Unit of Measure (UoM) when provided by the tour driver is captured in the Check In Reason Code field on the desktop app.

Only the order items in a check in document that have the Check in Qty, Expected Qty, or Left on Vehicle greater than 0 are saved.

Prepopulation of Check-In Items

In a check-in document, the check-in and expected quantity are prepopulated for products based on the inventory balances. For a product, the Check in Qty and the Expected Qty from the inventory balance is first distributed to a unit of measure that is marked as order unit. The left over fraction quantity is distributed to the smallest unit of measure.

Tour drivers can also see other unit of measures for the products that have Order Ability as True with the check-in and expected quantity as 0. Tour Drivers can edit the check-in quantity for all units of measure, including the one’s that have the expected quantity as 0. The app automatically calculates the difference as Check in Qty + Left On Vehicle (LoV) - Expected Qty.

Prepopulation of Check In and Expected Qty works accurately only if the Inventory Control Measure in Inventory Control Template is set to the smallest unit of measure.

Your user can’t edit the LoV quantity when Product Check In Policy is Optional or Partial.

Signing and Release of Check-In Documents

Configurations needed for the signature and release process to happen in ‌a product check-in document:

• The workflow and signature template associated with the check-in order template.
• The attributes and the flow for the signature process must be configured, using the Signature Template and Signature Flow Steps.

After the sync, you can view the signatures in the Signature section on the Order Header page on the Consumer Goods Cloud desktop app.

Inventory Transaction Creation for Check-In Documents

Configurations needed for creation of inventory and inventory withdrawal transactions for products in a released check-in document. Make sure that the inventory references are aligned with the inventory references of the checkout document. Records are created only for items that have the actual or expected, left on vehicle value populated (and not zero) in a product check-in document.

• In Order Template
  • Consider Inventory as Yes
  • Inventory Reference 1 with only one inventory reference (for example, as Tour, Vehicle, or User) as needed.
• In Order Item Template, Order Item Inventory Transaction is created with:
  • Used for Display as Yes
  • Inventory Control Template as Tour Inventory (Tour) in line with the inventory reference. If the inventory reference is Vehicle, the Inventory Control Template must be Tour Inventory (Vehicle) and similarly Tour Inventory (User) for the user.
• In the Inventory object, Record Type as Inventory
• In Inventory Control Template
  • Product Policy, and (Tour or Vehicle or User) Policy with the value as One.
  • Inventory Control Measure as Qty/Consumer Unit or Qty/Order Unit. This setting determines the product UoM for calculating the total amount in the inventory transaction.
• In Inventory Transaction Template, the Inventory Reference in set in correlation to the Inventory Reference in the Order Template.

Tour End

The tour data is synced with Salesforce org after the tour driver completes a tour if the Sync Options in tour template are OnTourEnd or ​​OnTourStart End.

The mobile app automatically sets the actual tour end date as the current date and time when the Allow End Day Time Tracking setting in the tour template is set to Yes.