Public Documentations

Feature Overview¶

This functionality is associated with the Transfer Out Voucher, facilitating the transfer of stock between different branches. It involves the relocation of stock from one warehouse/division to another. The challenge arises in determining the responsible party during the transit phase in the warehouse. To address this issue, a new process has been devised as a solution.

To implement this process, it is crucial to create both an 'In Transit' warehouse and a main warehouse within all divisions.

Database Changes¶

• Enabletransitwisetransferin = 1 /EnableTransitWareHouseInBranchTransfer
  • Transit warehouse feature will be activated
• Enabletransitwisetransferin ‘0’
  • Transit warehouse feature will be deactivated
• Centralizeddbmode = ‘1’
  • Single database
    • Directly save of TC Voucher to transit warehouse because it is single database no need of VPN,API and SYNC
• Centralizeddbmode = ‘0’
  • Multidatabase
    • In the case of VPN connectivity, data for the TC voucher will be saved directly
    • Data saving to TC voucher for non-VPN connectivity will occur either through API or SYNC processes. (Separate setting needed)
  • If the setting is enabled ‘EnableCompanyWiseNotification=’1’ than application need to generate the notification to receiver of transfer TC voucher and dont need to generate the notification when ‘EnableCompanyWiseNotification=’0’ and table used are
    Table 1 : Pos_notification
    Table 2 : Trnmain_download
  • When testing the application flow for transferring out through an in-transit warehouse, the setting is configured as 'isbbsm=0'.

Limitation¶

• It will be only supported in VPN connectivity. API and SYNC service is under development
• The complete TC voucher must be received, as partial transfer functionality is not supported in this module.

Application Flow¶

Step 1: Create a Transfer Out Voucher from Division 1 for Division 2, specifying the list of items to be transferred. And click on save

Step 2: Upon clicking the save button,

• The system stores data in the 'INVPROD' table within Division 1 of the sending branch to reduce stock levels.
• Simultaneously, the TC voucher is generated and stored in the receiving division, specifically in the "in-transit warehouse" of the receiving branch. This action will add the transferred stock from the TC voucher into the in-transit warehouse of the receiving branch.
• After saving the data in receiving branch at the same time notification need to be generated and will be displayed in the receiving branch notification icon if ‘EnableCompanyWiseNotification= 1 ’
  • Upon clicking on the voucher number in the notification icon, the user will be directed to the transfer-in screen for initiating the transfer-in process and saving the transfer-in voucher.
    OR
  • The user will load and select the Transfer Out (TO) voucher from the pending TO list before saving the Transfer In voucher.

• Upon saving the Transfer In voucher, the transferred stock should be deducted from the in-transit warehouse of the receiving branch and added to the main warehouse of the same branch.

Note :

• Branch transfers in and out do not involve accounting entries. Instead, real-time value transfers in and out will be computed in the final reports, similar to how opening and closing stock values are handled.
• Notification will be closed
  • If the user clicks on the notification and loads the TR page, saving the data successfully,
  • if the user loads the data from the TR form, loads the pending TO, and saves the data successfully.

Flow Diagram¶

https://drive.google.com/file/d/1LudL8vscMhmON5uf_TzaBpIeyrRNQ1TY/view?usp=sharing

Definition of Done¶

• Generate the Transfer Out (TO) voucher and convert the TC voucher into a Transfer In (TR) voucher. Generate notifications as outlined in the process described earlier. The process should run seamlessly without interruptions.

Things to be Considered¶

Note :

• This feature is only applicable when 'isbbsm=0'. If 'isbbsm=1', the dispatch entry form will be available instead of the transfer out entry form, incorporating the in-transit warehouse features mentioned earlier.
• The BBSM flow will be activated only when 'isbbsm=1'. However, when the 'isbbsm' setting is set to 0, all in-transit features for transfer out should remain uninterrupted.