This topic provides the systematic instructions to initiate the Data Enrichment stage of import LC Issuance request.

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

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

   LC Details

   The fields listed under this section are same as the fields listed under the LC Details section in Registration stage. For more information on the fields, refer to LC Details of Table 2-4 stage. During Registration, if user has not captured input, then user can capture the details in this section.

   Figure 2-22 LC Details
   Description of the illustration demainlcdetails.png

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

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

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

   Table 2-22 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 issuance. 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.
   Checklist	Click to view the list of items that needs to be completed and acknowledge. If mandatory checklist items are not selected, system will display an error on submit.
   Overrides	Click to view the overrides accepted by the user.
   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.
   Incoming Message	This button displays the multiple messages. In case of MT798, the User can click and view the MT798 message(770,700/701). In case of MT798-MT726-MT759 request, user can view MT798 message(726-759) in this placeholder in Header of the task. In case of MT798_MT788-MT799 request, user can view MT798 message (788-799) in this placeholder in Header of the process-task.
   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.