Inventory Management (CRM # 70004000)

Stock

Overview

Stock is read-only and shows only the items of the currently logged in rep and reps hierarchically below the current rep (done with the hierarchy code defined in the Rights module).

Stock Inventory

Overview

Stock Inventory is used for recording the rep’s current (counted by hand) stock and comparing that with the stock values provided in the BS (Stock) info area, approving the values by the rep’s superior and completing the process by the backoffice person that is assigned to the rep. After the inventory is completed the differences are added/subtracted from the current BS (Stock) quantity and the originally created BV (Stock Inventory) gets flagged as ‘booked’.

The SearchAndList has a global filter named ‘BV.TypeInventory’ which limits the visible records to ‘Stock management type’= ‘Inventory’ and ‘Quantity factor’ = ‘0’ is filtered. Additionally there are 3 filter buttons in the header which use the following filters: BV.StatusRunning, BV.StatusSubmitted, BV.StatusCompleted.

Rights

Access to BV (Stock Management) and BP (Stock Management Item) records are granted if the record is assigned to the currently logged in rep, someone higher in the rep’s hierarchy code or the assigned backoffice person for this rep.

Depending on the status of the BV record different users may edit the linked BP records. The rep of the record may edit his BP records in the ‘open’ or ‘declined’ states. In ‘submitted’ status the superior of the rep may edit the BP records. After the superior approved the BV record the rep’s assigned backoffice user may edit the BP records.

Most of these rights are configured in ‘TE_SR Template Main – LSI’. Some of them additionally in ‘TE_RR Backoffice - LSI’, ‘TE_RR Management - LSI’ and ‘TE_RR Sales OTC - LSI’.

Additionally there are 2 new triggers set in the main right which update entered counting differences in BP (the actual difference between the rep’s entered values and the BS values) and BV (the number of records differing from the original stock item): ‘TE_BP_UPD_Difference’ and ‘TE_BV_UPD_Difference’.

Workflows

There are 2 different workflows in the process of correcting the stock through inventory: TE_BV_BP_ManageStockForCurrentRep:

This workflow is started by clicking the ‘New’ button in the BV result list. It creates a new BV record, looks up all BS records of the current rep and creates a copy of them as linked BP records to it.

TE_BV_Automatic_Booking_Inventorydifferences:

This workflow is executed (by the backoffice rep clicking on ‘Complete’) after the rep has counted his/her stock items and the differences between these values and the respective BS records are calculated, approved by his superior and booked by his backoffice rep.

The workflow creates a second BV record with the same linked BP records as the original and sets the ‘Booked’ field to “True” in both BV records. With the difference that the ‘Quantity factor’ field is set to ‘+Qty’ (which is shown nowhere on the interface but used by the business logic). The business logic then corrects the BS records accordingly.

Stock Transaction

Overview

Data model

Callable from

• Menu Sales -> Stock Transaction

• Sales start page, backoffice start page, management start page

Processes

New Order process

The following picture shows the “New order” process. White boxes display buttons in web.

New Loss process

The following picture shows the “New loss” process. White boxes display buttons in web.

New Theft process

The following picture shows the “New theft” process. White boxes display buttons in web.

Dito.

New Return process

The following picture shows the “New Return” process. White boxes display buttons in web.

New Transfer process

CRM Processes

Basically there are three different CRM processes which are blocked in thegGlobal CRM process configuration and unlocked in the different roles.

• Stock Inventory Sales (1.2.6.8.1.400)

• Stock Inventory BackOffice (1.2.6.8.1.401)

• Stock Inventory Management (1.2.6.8.1.402)

Buttons

TE_BV_NewOrder

This button calls the TE_BV_New process.

CRM process: Stock Inventory Sales (1.2.6.8.1.400)

TE_BV_NewReshipment

This button calls the TE_BV_NewReshipment process.

CRM process: Stock Inventory Sales (1.2.6.8.1.400)

TE_BV_NewLoss

This button calls the process TE_BV_NewLoss.

CRM process: Stock Inventory Sales (1.2.6.8.1.400)

TE_BV_NewTheft

This button calls the TE_BV_NewTheft process.

CRM process: Stock Inventory Sales (1.2.6.8.1.400)

TE_BV_NewTransfer

This button calls the TE_BV_NewTransfer process.

CRM process: Stock Inventory Sales (1.2.6.8.1.400)

TE_BV_Submit

This button calls the TE_BV_UPD_SubmitInventoryVerify trigger.

CRM process: Stock Inventory Sales (1.2.6.8.1.400)

This button is only unlocked for sales reps because a user with management or backoffice role does not have the possibility to create new BV records. Therefore this button is not needed for these user roles.

TE_BV_Approve

This button calls the TE_BV_UPD_SubmitInventoryChecking trigger.

CRM process: Stock Inventory BackOffice (1.2.6.8.1.400), Stock Inventory Management (1.2.6.8.1.402)

This button is unlocked for backoffice and management reps because a user with sales role should have no possibility to approve a BV record. Therefore this button is not needed for sales user roles.

TE_BV_Decline

This button calls the TE_BV_UPD_DeclineInventory trigger.

CRM process: Stock Inventory BackOffice (1.2.6.8.1.400), Stock Inventory Management (1.2.6.8.1.402)

This button is unlocked for BackOffice and Management reps because a user with sales role should have no possibility to decline a BV record. Therefore there is no use of this button for sales userroles.

TE_BV_Delivered

This button calls the workflow TE_BV_TriggerHandler.

CRM process: Stock Inventory BackOffice (1.2.6.8.1.400), Stock Inventory Sales (1.2.6.8.1.402)

This button is unlocked for BackOffice and Sales reps because a user with management role should have no possibility to click the deliver button on BV record. Therefore this button is not used for management user roles.

TE_BV_Received

This button calls the TE_BV_UPD_CompleteInventory trigger.

CRM process: Stock Inventory BackOffice (1.2.6.8.1.400), Stock Inventory Sales (1.2.6.8.1.402)

To change this vi sibility you have to change the CRM process status in your specific CRM process configuration within the role.This button is unlocked for backoffice and sales reps because a user with management role should not be able to click the “Complete” button in the BV record. Therefore this button is not used for management user roles.

Visibility Overview

Table 4: This table shows which user role has access to which buttons.

Process

TE_BV_New

This process is responsible for adding new BV records and create linked BP records via the serial entry.

Graph

Process Storage Variables

Step - TE_BV_Initial

This step creates a new BV record with some default values. Therefore we used the crud service (u8.services.crud.create).

Action Template: JavaScriptWithCallback

Input Arguments

Output Arguments

Dispatching

Step - TE_BV_Transfer

This step is responsible for selecting a rep if the transaction type is "Transfer". It is a sub-step between the initial step and the serial entry. After selecting the rep the uid is passed to the “TE_BV_Update” step which updates the BV record which was created in the “TE_BV_Initial” step. The selected rep uid is entered in the “Transfer to (Z/51) field.

Action Template: ExecuteSelectRecordSubStep

Input Arguments

Output Arguments

Dispatching

Step - TE_BV_SelectRep

Action Template: Search

Input Arguments

Output Arguments

Dispatching

Step - TE_BV_Update

This step has two tasks. First of all there is a data provider which reads the repID from the selected rep in the “TE_BV_SelectRep” step. Afterwards there is the crud service to update the created BV record in the “TE_BV_Initial” step with the repID.

Action Template: JavaScriptWithCallback

Data provider: GetRepID

Action: ReadRecordDataProvider

Input Arguments

Output Arguments

Dispatching

Step - TE_BV_SerialEntryBP

This step is the last step in the process. If the user clicks on the “I’m done” button in the serial entry the process is closed and dispatched back to the BV main search. Basically this step is responsible for creating BP records in with the standard serial entry. No special filters are provided.

Action Template: Serial Entry

Input Arguments

Output Arguments

Dispatching

Filters

• BV.TypeTransaction

• BV.TypeTransactionAndOpen

• BV.TypeTransactionAndOpenDelivered

• BV.TypeTransactionAndVerifying

• BV.TypeTransactionCanceledOpenAndDelivered

Forms

TE_BV_StockTrasaction

This form includes only one search view. Due to that the system has to react to ‘onSelect’ and ‘inSelectionChange’ events and some special configuration values and a separate form is needed.

Events & JavaScript Calls

There is the same JavaScript Code used behind the ‘onSelect’ and ‘obSelectionChange’ events! For detailed information see section JavaScript function below.

• TE_BV_SerialEntry_Totals

Web Config Parameter

In order to keep everything customizable, there are 6 web config parameters where values can be defined!

Status Mapping Button

Table 5: This table shows the mapping between the BV status and the button visibility.

JavaScript Functions

A new JavaScript function was created for stock transaction:

checkBVpermission_onRecordSelect(); (File lsiquerystates.js)

Basically the function consists of 6 main blocks:

For detailed information please take a look at the file and comments within it.

Triggers

Overview

• TE_BV_UPD_SubmitInventoryVerify

Executed by: Button - TE_BV_Submit

This trigger is executed by the “TE_BV_Submit” button and the status set to “to be verified” if the user clicks the button.

• TE_BV_UPD_SubmitInventoryChecking

Executed by: Button - TE_BV_Approve

	Field	Field content	Condition
1	Submitted at (5002/T)	Actual Time
2	Status (5000/K)	“Submitted”
3	Status (5000/K)	“Completed”
4	Counting completed on (5008/D)	Actual Date

This trigger is executed by the “TE_BV_Approve” button. As this button is available for backoffice and Management users and act in two different ways at the same time, there are conditions if the “Status” field is filled or not.

• TE_BV_UPD_DeclineInventory

  Executed by: Button - TE_BV_Decline

Workflows

Special Case: “TE_BV_Delivered” Button

Button Visibility

If one of these buttons

• TE_BV_Approve

• TE_BV_Decline

• TE_BV_Delivered

• TE_BV_Received

• TE_BV_Submit

is displayed or not, depends on the following settings:

1. Given CRM process in designer
2. Locked or unlocked CRM prcosses in the user rights
3. The value of the "Status" field (K/5000; catalog 5039); because it is an important factor for the JavaScript function which handles visibility.
4. Mapping in web config parameter.
5. Exception defined in web config parameter.

Territory Management

Buttons

TE_GL_Allocate

Calls JavaScript: u8.TeLSI.Allocate

The function that is called displays first a question mark type message box and after selecting “OK”, a trigger is called ("TE_TD_NEW_Create ToDo for Allocation"). An information type message box is then displayed with information about action taken by the trigger.

Menu Actions

TE_A_FillUpAllocationConfiguration

Used to fill up specialties (generate GL records with different specialties) for the chosen business area and the chosen account type

Calls javascript u8.TeLSI.TerritoryMgmt.FillUpAllocationConfiguration with allocateAll = false.

TE_A_FillUpAllocationConfigurationAll

Used to fill up specialties (generate GL records with different specialties) for all account types and the chosen business area.

Calls javascript u8.TeLSI.TerritoryMgmt.FillUpAllocationConfiguration with allocateAll = true

Filters

• TD.TE_Allocation

Forms

TE_TerritoryManagement

The form consists of 3 tabs:

• Allocation (ZU) Search&Result + Expand View

• Allocation Configuration (GL) Search&Result + Expand View

• To-Do (TD) Search&Result

  ToDos are filtered (automatically applied TD.TE_Allocation filter) so that the user can only see records of his interest.

Account Manager

Overview

Menu Actions

• TE_SB_AccountManager

Filters

• SB.TE_CompanyRelated

• SB.TE_PersonRelated