Any business applications/requests (such as request for issuance of LC) received in a branch of a bank has to be processed. This transaction (SPTDOC) is used by the branch user to register the applications/requests received from customers and route these requests to respective processing HUBs for completing the process.

Registration panel

For initiating the routing logic, this transaction Registration (SPTDOC) has to be processed by the branch user. The transaction starts with displaying the information of the user logged in and the current timestamp and the active entity details. These details are for information purpose and the user cannot modify them.

Other important inputs:

Business Sector: The respective business sector (Import LC, Export LC, etc.,) for which the application/request was received from the customer.
Transaction Class: The transaction class (i.e. opening, amendment, claim, etc.,) has to be selected.
Transaction: The Transaction ID for the selected business sector and transaction class has to be selected (Note: It won't be auto selected if there are more then one possible transaction for the business module and transaction class combo). Also, only the applicable transactions for the selected business module and transaction class will the listed on search.
Customer: The Customer ID from whom the application/request has been received.
Amount: Currency and Amount of the received application/request.

Optional inputs:

Reference: The customer's reference for the application/request received.
New Contract: Flag to select if the application/request is for a new contract. If empty, it denotes the application is for amendment/claim for an existing contract.
Contract Reference: Existing application reference of an existing contract.

Based on the above inputs, the routing logic defined will be initialized. The resulting entity, user and/or user group responsible for the processing will be displayed in the end of the transaction. If required, any infotext can be sent by the branch user to the HUB user.

Based on the above inputs, the routing logic defined will be initialized. The resulting entity, user and/or user group responsible for the processing will be displayed in the end of the transaction. If required, any infotext can be sent by the branch user to the HUB user.