This action might not be possible to undo. Are you sure you want to continue?
UltraSeller Project – Phase 2 Sales Product Development
REQUIREMENT ID: DEFINITION: OPPORTUNITY or NEED ADDRESSED: BENEFITS: IMPORTANCE:
USell_Inventory Reassignment Process Updates to the Inventory Reassignment process In phase 2 of the Sales project, when new or migrated sales stock is reassigned UltraSeller will need to communicate with sales platform to ensure that sales platform is updated with the reassignment details and thereby kept in sync with UltraSeller tool High
AS IS Sales Stock can be transferred from one branch to another on UltraSeller but there is no feedback to Legacy that the transfer has taken place. Therefore Legacy and UltraSeller can be out of sync with regards to their records of where stock is located. When new stock is transferred on UltraSeller there is a batch file sent to SALES PLATFORM and response file received by UltraSeller to ensure that SALES PLATFORM is kept in sync with UltraSeller When old stock is transferred on UltraSeller there is no notification back to the sales platform. TO BE UltraSeller will allow the user to select one, some or all of the SALES STOCK cards that remain within a sleeve to be reassigned from the vault of one branch to the vault of another branch. [NB - some cards within the sleeve may have already been sold or reassigned to another branch or to a till – so if the user has selected a ‘whole’ sleeve to be reassigned UltraSeller will only reassign those cards that are left in that sleeve in that specific location (ie the vault)] 2. User can repeat step 1 to reassign as many individual cards or sleeves of cards as they require 3. Each new SALES STOCK or migrated SALES STOCK card will be associated with a specific type. 1. Each un-migrated old SALES STOCK will not be associated with a specific type. Each branch will be associated with one or more types. When a user requests some cards to be reassigned UltraSeller should check if the cards are new or migrated SALES STOCK or un-migrated old SALES STOCK. For new or migrated SALES STOCK only UltraSeller should validate that the branch that the user is trying to transfer the card(s) to is allowed to accept the type associated with the cards that are being transferred. If the transfer is not allowed UltraSeller should display a message on screen informing the user. For un-migrated old SALES STOCK UltraSeller should apply the same rules for reassignment as it does now (eg that the cards can’t be reassigned to a different seller, but no validation or types). [NB1 - in phase 1 the inventory load file will include the type for each card in the file. However UltraSeller will not load that type into it’s database until phase 2 functionality is implemented. Therefore, before phase 2 is implemented there will be a one-off data feed of the subprogram ID for each card that has been created on the SALES PLATFORM platform. UltraSeller will then know the subprogram ID and be able to use this to validate the reassignment as above.
Page 1 of 5
The response codes will also indicate the reason for an unsuccessful reassignment. 6. UltraSeller does not need to wait until positive confirmation has been received back from SALES PLATFORM] There will be no batch file sent to SALES PLATFORM for old Sales Stock prior to card migration. from where UltraSeller will pull the file]. sleeve and card information as appropriate. New SALES STOCK & migrated SALES STOCK cards that failed reassignment are to be included on the Failed Reassignment report detailing the case.e. a log file will be generated which will include a response code and message for each card indicating if the reassignment was completed successfully or not. 5. However the report should not include cases. or the card has been previously destroyed. The batch file will detail each individual card number that is to be reassigned. as there is no action required in this case Once the stock has been reassigned in UltraSeller it will be immediately available for acceptance in the vault of the destination branch [i. Confidential Page 2 of 5 . [SALES PLATFORM will post the log file to a Open SSH server hosted by SALES PLATFORM. e. NB2 – as part of the migration process for old Sales Stock & old MGCs a subprogram ID will be assigned to each card. UltraSeller will require a one-off data feed of the subprogram ID and will then know the subprogram ID and be able to use this to validate the reassignment as above. Once complete.g. 8. the card has already been reassigned to the required destination branch. A complete list of response codes and reasons is to be provided by SALES PLATFORM. sleeves or cards where the reassignment failed due to the card(s) already being in the required destination branch. from where SALES PLATFORM will collect the file]. 7.] At a configurable regular interval (eg hourly) UltraSeller will send a batch file to SALES PLATFORM containing details of all the new SALES STOCK or migrated SALES STOCK cards that have been selected to be reassigned since the last batch file was created. [UltraSeller will push the file to an Open SSH server hosted by SALES PLATFORM. 9. As per point 1 if the user has selected a whole or part of a sleeve to be reassigned UltraSeller will list each individual card number within sleeve UltraSeller will not send any notification to SALES PLATFORM for vault-to-till or till-to-vault transfers within the same branch since SALES PLATFORM does not capture till level details All the exception handling functionality built for the Inventory Reassignment process in Phase 1 will now also be applied to new Sales Stock & migrated Sales Stock SALES PLATFORM will validate and process all reassignment requests in the batch file.REQUIREMENT DESCRIPTION UltraSeller Project – Phase 2 Sales Product Development 4. and also include the response code and associated text outlining the reason for the failure.
Manny Roider John Doe Confidential Page 3 of 5 . and that process is not changing CONSTRAINTS: PRIMARY TYPE: SUB-TYPES REQUIRED STAKEHOLDER: SPONSOR: None identified Functional Functional – required elements of conversion of inputs to outputs. There are no changes to the reassignment process for old stock prior to card migration 5. UltraSeller communicates with SALES PLATFORM to allow the SALES PLATFORM system to be updated and kept in sync with UltraSeller.REQUIREMENT DESCRIPTION UltraSeller Project – Phase 2 Sales Product Development Re-assignment of stock Seler Seler initiates branchto-branch stock transfer Operator receives decline message . Validation successful ? Yes Stock transferred to receiving branch Yes holding area and available to sell (once accepted) UltraSeller generates a batch file containing reassignment requests UltraSeller receivesresponse log file UltraSeller processes file and generates alert/ report of failed reassignments Sales Platform Sales Platform eFunds receives batch file from UltraSeller Sales Platform processes batch file reassignment requests. Corp. Jane Doe. UltraSeller sends alert/report for investigation NET CHANGE: ASSUMPTIONS: The UltraSeller application supports the transfer/reassignment of new SALES PLATFORM based Sales Stock & migrated Sales Stock via a batch process. Once a card has been allocated a type ID it will not change 6. Corp. 7. Operators accept Stock into branch Vault At regular intervals UltraSeller UltraSeller No UltraSeller transfer request in UI UltraSeller will validate reassignment request based on current rules. UltraSeller will validate that the branch the cards are being transferred to is able to accept the subprogram associated with the cards. 1. No development is required to the UltraSeller delivery tool – changes are only required to the ‘Sales Tool’ 3. New Sales Stock & migrated Sales Stock will now have case & sleeve numbers in addition to Receipt numbers 2. There does not need to be a batch file sent to SALES PLATFORM for a tillto-till transfer. Sales Platform generates a log file with response messages at card level. Inventory system is not to be used to reassign stock as UltraSeller would not be aware of this and would become out of sync with SALES PLATFORM. There will be no batch file sent to SALES PLATFORM for old Sales Stock prior to card migration 4.
Reassignment_03 Reassignment_04 Reassignment_05 Reassignment_06 SALES PLATFORM fails to generate a response file. Exceptions The exception handling processes for SALES STOCK inventory load will now be the same as that for MGCs – and no extra exception handling functionality should be required. Exception Ref Reassignment_01 Description UltraSeller is unable to send the batch file after the maximum specified number of retries due to a communication problem. SALES PLATFORM will provide a response for all requests. When the problem has been resolved the file can be resent to update SALES PLATFORM with UltraSeller. the file format has been corrupted during transfer. which will have committed the reassignment details to it’s database.g. The following specific exceptions identified for old stock will now also apply for Sales Stock. successes and failures.g. May require restarting the process and/or manual amendment of UltraSeller. has already been reassigned. UltraSeller will generate a report for Corp. the following new/amended BAU and Exception Handling business processes are required to support the systems capabilities and are required to be owned and implemented by the relevant business team or other group. card number unknown. who will investigate the failures. SCL to resend the file if necessary. Support team to investigate to identify the cause of the problem. possibly in consultation with development. SALES PLATFORM is unable to send the log response file after the maximum specified number of retires due to a Confidential Page 4 of 5 . possibly in consultation with SALES PLATFORM. Support required/solution Support teams will attempt to identify the cause of the problem. The log file will include a response code which will indicate the reason for the failure of the reassignment request. SALES PLATFORM support to notify Corp.REQUIREMENT DESCRIPTION UltraSeller Project – Phase 2 Sales Product Development REQUIREMENTS GROUP: Operations Support SALES PLATFORM business workstream owner SALES PLATFORM Supply Chain Management Project Office QA BUSINESS ANALYST: ASSOCIATED REQUIREMENTS SUPPORTING INFORMATION: Related Business Processes Further to the above stated requirements.e. SALES PLATFORM support to investigate and rectify the issue. SALES PLATFORM is unable to complete the reassignment of a specific card(s) e. has already been activated etc. in a log response file and send to UltraSeller. i. SALES PLATFORM Support will attempt to identify the cause of the problem. Reassignment_02 UltraSeller fails while committing transfer details to its database SALES PLATFORM fails to process the batch file received from UltraSeller e. that the batch loader process has failed.
REQUIREMENT DESCRIPTION UltraSeller Project – Phase 2 Sales Product Development communication problem.g. e. When the problem has been resolved the file can be resent to update UltraSeller.1 – 21 st Detail of Revision Initial Draft Aug 2007 Confidential Page 5 of 5 . the file format has been corrupted during transfer. BAU None Not in Scope Area Further Detail Revision History Revision History Date 0. Reassignment_07 UltraSeller is unable to process the log response file from SALES PLATFORM. Support to notify SALES PLATFORM of the issue. SALES PLATFORM to resend the file if necessary.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.