This topic provides the systematic instructions to initiate the Data Enrichment stage of Import LC Amendment Benificiary Consent - Islamic request.

1. On Data Enrichment - Main Details screen, specify the fields that were not entered at Registration stage.

   Figure 2-7 Data Enrichment - Main Details
   
   Description of the illustration demainapplicationdetails.png
   

   For more information on fields, refer to the field description table below:

   Table 2-6 Data Enrichment - Main Details - Application Details - Field Description

   Field	Description
   Documentary Credit Number	Read only field. Documentary credit number is defaulted from LC.
   Received From - Customer ID	Read only field. Customer ID will be auto-populated based on the selected LC in Registration stage.
   Received From - Customer Name	Read only field. Customer name will be defaulted as available in LC.
   Branch	Read only field. Branch details will be auto-populated based on the selected LC from the lookup.
   Process Reference Number	Read only field. Unique OBTFPM task reference number for the transaction. This is auto generated by the system based on process name and branch code.
   Priority	Set the priority of the Import LC Amendment - Beneficiary Consent request as: Essential Critical Low Medium High If priority is not maintained for the customer, system will populate 'Medium' as the default priority.
   Submission Mode	Read only field. Submission mode will be defaulted based on the selected LC in Registration stage.
   User Reference Number	Read only field. User reference number will be defaulted based on the selected LC in Registration stage.
   Response Received Date	Read only field. The application displays the branch’s current date by default.

   Beneficiary Response Capture

   The fields listed under this section are same as the fields listed under the Beneficiary Response Capture section in Registration. For more information on the fields refer Beneficiary Response Capture in the Registration stage. If user has not captured input, then user can capture the details in this section.

   Figure 2-8 Beneficiary Response Capture
   
   Description of the illustration demainbeneficiaryresponsedetails.png
   

   For more information on fields, refer to the field description table below:

   Table 2-7 Data Enrichment - Main Details - Beneficiary Response Capture - Field Description

   Field	Description
   Amendment Number	Read only field. Amendment number will be auto-populated based on selected LC using documentary credit number.
   Amendment Date	Read only field. This field displays the date on which the amendment was made to LC.
   Bene Conf Req	Read only field. This field displays whether beneficiary consent is required or not. It is auto-populated based on selected LC using documentary credit number.
   Beneficiary Response	Select the beneficiary response from the drop-down. The options are: Confirmed Unconfirmed Rejected Note: Beneficiary Response field will be read only if Beneficiary Consent Required is ‘No’.
   Remarks	Specify the remarks of the beneficiary response.
   Action	Click the edit icon to edit the beneficiary response.

   Audit
   

   
   Description of the illustration audit.png

   
   

   This button provides information about user initiated the transaction, initiated date, stage wise detail etc.

   For more information on fields, refer to the field description table below.

   Table 2-8 Audit - Field Description

   Field	Description
   Application No.	This field displays the appliation number of the process.
   Branch Code	This field displays the branch code.
   Initiated Date	This field displays the date on which process is initiated.
   Initiated By	This field displays the user ID of the user who had initiated the process.
   Process Name	This field displays the name of the process which is initiated.
   S. No	This field displays the serial number of the audit record.
   Stage Name	This field displays the current stage of the process.
   Completed Time	This field displays the time on which the audit of the current stage is completed.
   Completed By	This field displays the user ID of the user who had completed the audit.
   Outcome	This field displays the outcome of the audit.

2. Click Next.
   The task will move to next data segment.

   For more information on fields, refer to the field description table below:

   Table 2-9 Main Details - Action Buttons - Field Description

   Field	Description
   Clarification Details	Clicking the button opens a detailed screen, user can see the clarification details in the window and the status will be 'Clarification Requested'.
   Documents	Click to View/Upload the required document. Application displays the mandatory and optional documents. The user can view and input/view application details simultaneously. When a user clicks on the uploaded document, Document window get opened and on clicking the view icon of the uploaded document, Application screen should get split into two. The one side of the document allows to view and on the other side allows to input/view the details in the application.
   Remarks	Specify any additional information regarding the LC amendment beneficiary consent - Islamic. This information can be viewed by other users processing the request. Content from Remarks field should be handed off to Remarks field in Backend application.
   Overrides	Click to view the various overrides that have been generated and accepted.
   Customer Instructions	Click to view/ input the following Standard Instructions – In this section, the system will populate the details of Standard Instructions maintained for the customer. User will not be able to edit this. Transaction Level Instructions – In this section, OBTFPM user can input any Customer Instructions received as part of transaction processing. This section will be enabled only for customer initiated transactions.
   View LC	Click to view the details of the LC.
   Signatures	Click the Signature button to verify the signature of the customer/ bank if required. The user can view the Customer Number and Name of the signatory, Signature image and the applicable operation instructions if any available in the back-office system. If more than one signature is available, system should display all the signatures.
   Request Clarification	Submit the request for clarification to the “Trade Finance Portal” for the transactions initiated offline.
   Save & Close	Save the details provided and holds the task in ‘My Task’ queue for further update. This option will not submit the request.
   Cancel	Cancel the Data Enrichment stage inputs. The details updated in this stage are not saved. The task will be available in 'My Task' queue.
   Hold	The details provided will be saved and status will be on hold.User must update the remarks on the reason for holding the task. This option is used, if there are any pending information yet to be received from applicant.
   Reject	On click of Reject, user must select a Reject Reason from a list displayed by the system. Reject Codes are: R1- Documents missing R2- Signature Missing R3- Input Error R4- Insufficient Balance/Limits R5 - Others Select a Reject code and give a Reject Description. This reject reason will be available in the remarks window throughout the process.
   Refer	Select a Refer Reason from the values displayed by the system. Refer Codes are: R1- Documents missing R2- Signature Missing R3- Input Error R4- Insufficient Balance/Limits R5 - Others
   Next	On click of Next, system validates if all the mandatory fields have been captured. Necessary error and override messages to be displayed. On successful validation, system moves the task to the next data segment.