Goods Receipt Sources

Module Guide: Goods Receipt Sources

Module Location

Utilities > Goods Receipt Sources

Module Purpose

The Goods Receipt Sources module is used to define and map the data sources related to the origin of incoming goods within the system. This module is essential for integrated warehouse operations where the system must differentiate incoming stock data originating from various platforms, applications, or other digital workflows (e.g., integration with an external application like C-App).

1. Main View (List of Goods Receipt Sources)

View Explanation

• Goods Receipt Source Table:

  • Warehouse: The name of the warehouse or receiving location.

  • Data Source from C-App: Indicates whether the receipt originates from C-App or another digital channel.

  • Reason: A column for recording notes or the reason for the configuration/customization of the receipt source.

  • Action: Provides actions (like edit/delete) to modify the mapping of the goods receipt source.

• The data in this table will be empty if no configuration or mapping has been set up.

2. Steps for Inputting/Mapping Goods Receipt Sources

• Navigate to Utilities > Goods Receipt Sources.

• (If available) click Add to create a new mapping/category for a receipt source.

• Fill in the warehouse name, the data source (e.g., select C-App if the receipt is from that application), and the reason for the setting.

• Save the data so the system recognizes the receipt source according to the configuration for each warehouse/platform.

3. Integrated Workflow & Business Process

• Accurate Incoming Stock Data: A well-mapped goods receipt source is crucial in a multi-application integration to prevent double-counting of stock or unrecognized goods receipts in reporting and logistics dashboards.

• Auditing & Reconciliation: By knowing the receipt source, the internal audit team can trace the data's origin and validate the integrity of stock receipt data across different applications/platforms.

4. Tips & Important Notes

• Perform the mapping of receipt sources carefully, especially if new applications are being developed and integrated into the core system.

• Write clear reasons for each mapping to make it easier to trace issues if stock discrepancies or data disputes occur.

• Only users with a thorough understanding of the system and cross-departmental application integration should be given access to add, edit, or delete entries in this menu.