This topic provides the systematic instructions to capture the additional details in Data Enrichment stage of Guarantee SBLC Advised Claim Update process.

1. On Additional Details screen, click the 3 dots on any Additional Details tile to view the details.

   Figure 2-12 Additional Details
   
   Description of the illustration deadditionaldetails.png
   

   Tracer Details

   The bank users can capture these tracer details for Guarantee SBLC Advised Claim Update in Guarantee and send the tracers to the customer till its Settled / Extended / Rejected / Injunction.
   
   Description of the illustration detracerdetails.png
   

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

   Table 2-17 Tracer Details - Field Description

   Field	Description
   Tracer Code	Read only field. Tracer code is defaulted by the system maintained in the Product level.
   Description	Read only field. Description of the tracer code is auto populated.
   Party Type	Specify the party type or click Search icon to search and select the receiver party type from the lookup.
   Required	Enable the option, if tracer is required. Toggle On: Required Toggle Off: Not required.
   Maximum Tracers	Specify the value for maximum number of tracers to be sent. Maximum allowed is 99 exceeding the same system should prompt an error message for the same “Maximum number of numerals allowed is: 2” and should clear the field to enter the correct value by the user. Maximum Tracers cannot be less than the “Number Sent”, system needs to validate the same.
   Number Sent	Number Sent is defaulted by the System with the value, where the number of tracers sent so far. And it cannot be greater than the “Maximum Tracers”.
   Start Days	Specify the number of days after which the tracer has to be sent from the Tracer Start date. It should be positive numeric value.
   Last Sent On	Read only field. Tracer last sent date is defaulted by the system.
   Medium	Select the the medium in which the Tracer has to be generated. It lists all the possible mediums maintained in the system. The options are: MAIL SWIFT
   Frequency	Specify the medium in which the Tracer has to be generated. It should be positive numeric value. System should default the Frequency captured as part of the Contract here and should allow the user to modify the same.
   Template ID	Click Search icon to search and select the template ID, in which the tracer has to be generated from the lookup. It is a lookup which lists all the possible templates maintained in the system. Template ID is nothing but the data that goes in Tag 79 in MT799. This template ID is applicable only for medium 'SWIFT' Template lookup displays all the template ids applicable for the given Tracer Code.
   Action	Click Edit icon to edit the tracer details.

2. Click Save and Close to save the details and close the screen.

   Charge Details

   This section displays charge details. On landing the additional tab, charges and tax if any will get defaulted from Back end simulation. If default charges are available under the product, they should be defaulted here with values. If customer or customer group specific charges are maintained, then the same will be defaulted from back end system.

   
   
   Description of the illustration dechargedetails.png
   

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

   Table 2-18 Charge Details - Field Description

   Field	Description
   Commission Details	Specify the Commission Details based on the description of following table.
   Component	Read only field. This field displays the commission component. Click the link to view the commission component details.
   Rate	Read only field. This field displays the rate that is defaulted from product. The commission rate, if available in Back Office defaults in Oracle Banking Trade Finance Process Management Cloud Service.
   Mod. Rate	From the default value, if the rate is changed the value gets updated in this field. The user can specify the modified rate value.
   Currency	Read only field. This field displays the currency in which the commission have to be collected.
   Amount	Read only field. This field displays the amount that is maintained under the product code.
   Modified	From the default value, if the amount is changed, the value gets updated in the modified amount field. The user can specify the modified value.
   Defer	If enabled, charges/commissions has to be deferred and collected at any future step.
   Waive	Based on the customer maintenance, the charges/commission can be marked for Billing or Defer. If the defaulted Commission is changed to defer or billing or waive, system must capture the user details and the modification details in the ‘Remarks’ place holder.
   Charge Party	Charge party is Applicant by default. User can change the value to Beneficiary.
   Settl. Accnt	Select the settlement account.
   Amendable	The value is auto-populated as the commission is amendable or not.
   Charge Details
   Component	This field displays the charge component type.
   Tag Currency	This field displays the tag currency in which the charges have to be collected.
   Tag Amount	This field displays the tag amount that is maintained under the product code.
   Currency	This field displays the currency in which the charges have to be collected.
   Amount	This field displays the amount that is maintained under the product code.
   Modified	From the default value, if the rate is changed or the amount is changed, the value gets updated in the modified amount field.
   Billing	If charges are handled by separate billing engine, then by selecting billing the details to be available for billing engine for further processing. On simulation of charges/commission from Back Office, if any of the Charges/Commission component for the customer is ‘Billing’ enabled, ‘Billing’ toggle for that component should be automatically enabled in Oracle Banking Trade Finance Process Management Cloud Service. The user can not enable/disable the option, if it is de-selected by default. This field is disabled, if ‘Defer’ toggle is enabled.
   Defer	If charges have to be deferred and collected at any future step, this check box has to be selected. On simulation of charges/commission from Back Office, if any of the Charges/Commission component for the customer is AR-AP tracking enabled, ‘Defer’ toggle for that component should be automatically checked in Oracle Banking Trade Finance Process Management Cloud Service. The user can enable/disable the option the check box. On de-selection the user has to click on ‘Recalculate’ charges button for re-simulation.
   Waive	Enble the toggle, if charges has to be waived. Based on the customer maintenance, the charges should be marked for Billing or for Defer. This field is disabled, if Defer toggle is enabled.
   Charge Party	Charge party is applicant by default. User can change the value to beneficiary.
   Settlement Account	Select the settlement account.
   Tax Details	The tax component is calculated based on the commission and defaults if maintained at product level. User cannot update tax details and any change in tax amount on account of modification of charges/ commission will be available on click of Re-Calculate button or on hand off to back-end system.
   Component	This field displays the tax component.
   Type	This field displays the type of tax component.
   Value Date	This field displays the value date of tax component.
   Currency	This field displays the currency in which the tax have to be collected. The tax currency is the same as the commission.
   Amount	This field displays the tax amount based on the percentage of commission maintained. You can edit the tax amount, if applicable.
   Billing	If taxes are handled by separate billing engine, then by selecting billing the details to be available for billing engine for further processing. This field is disabled, if ‘Defer’ toggle is enabled.
   Defer	If taxes have to be deferred and collected at any future step, this option has to be enabled. The user can enable/disable the option the check box. On de-selection the user has to click on ‘Recalculate’ charges button for re-simulation.
   Settl. Accnt	System defaults the settlement account. The user can modify the settlement account.

3. Click Save and Close to save the details and close the screen.
   Preview Mesage

   The bank user can view a preview of the message and advice simulated from back office which is based on the guarantee Claim captured in the previous screen.
   
   Description of the illustration depreviewmessage.png
   

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

   Table 2-19 Preview Message - Field Description

   Field	Description
   Preview SWIFT Message	This sectiom displays the Preview SWIFT Message details.
   Language	Read only field. The language to preview the draft guarantee details. English is set as default language for the preview.
   Message Type	Select the message type from the drop down.
   Message Status	Read only field. Display the message status of draft message of guarantee details.
   Repair Reason	Read only field. Display the message repair reason of draft message of guarantee details.
   Preview Message	This field displays a preview of the draft message. Based on the guarantee text captured in the previous screen, guarantee draft is generated in the back office and is displayed in this screen.
   Preview Mail Device	This sectiom displays the Preview Mail Device details.
   Language	Read only field. The language for the advice message. English is set as default language for the preview.
   Advice Type	Select the advice type.
   Message Status	Read only field. Display the message status of draft message of guarantee details.
   Repair Reason	Read only field. Display the message repair reason of draft message of guarantee details.
   Preview Message	This field displays a preview of advice.

4. Click Save and Close to save the details and close the screen.
   FX Linkage

   This section enables the user to link the existing FX contract(s) to the Guarantee/SBLC Claim Settlement. FX Linkage call should be triggered on DE-submit.

   
   
   Description of the illustration fxlinkagedetails.png
   

   Figure 2-13 FX Linkage Details
   
   Description of the illustration fxlinkagedetails1.png
   

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

   Table 2-20 FX Linkage - Field Description

   Field	Description
   	Click + to add multiple FX Details. Below fields are displayed on the FX Linkage pop-up screen, if the user clicks the plus icon.
   FX Reference Number	Click Search to search and select the FX contract reference number. On select and save and close, system defaults the available amount, bot currency, sold currency and rate. Forward FX Linkage available for selection at bill would be as follows, Counterparty of the FX contract should be the counterparty of the Bill contract. Active Forward FX transactions authorized not marked for auto liquidation. Bill contract currency should be BOT currency of the FX transaction in case of an export Bill or the SOLD currency in case of an Import Bill.
   Currency	Read only field. This field displays the FX BOT currency from the linked FX contract.
   Contract Amount	This field displays the FX BOT currency and Amount. The user can change the currency.
   Available FX Contract Amount	Read only field. This field displays the available FX contract amount. The value is from the “Available Amount” in FXDLINKG screen in OBTR. Available Amount BOT currency and Amount is displayed.
   Linkage Amount	System defaults the amount available for linkage. The Linkage amount should default the LC Contract Currency and allowed to change the linkage amount alone. The validation “Sum of Linked amount will not be greater than contract amount” or “Linkage amount will not be greater than the available amount for linkage” should be triggered on save of the FX linkage screen when trying to link the single FX or multiple FX.
   Rate	Read only field. This field displays the rate at which the contract is booked.
   FX Amount in Local Currency	Read only field. This field displays the FX amount in local currency. The value is defaulted as FX BOT currency and Amount from FXDTRONL
   FX Expiry Date	Read only field. This field displays the expiry date from the linked FX contract.
   FX Delivery Period - From	Read only field. This field displays the date from which the contract is valid for utilization.
   FX Delivery Period - To	Read only field. This field displays the date to which the contract is valid for utilization.
   FX Linkage grid	Below fields appear in the FX linkage grid along with the above fields.
   Bought Currency	Read only field. This field displays the currency from the linked FX contract.
   Sold Currency	Read only field. This field displays the currency from the linked FX contract.
   Available Contract Amount	Read only field. Available amount will be FX contract amount minus the linked amount. Available amount for linkage should be greater than Zero.
   Linked Amount	Sum of Linked amount will not be greater than LC contract amount. Linked amount will not be greater than the available amount for linkage.
   Total Utilized Amount	Read only field. This field displays the total amount utilized against the corresponding linked FX. On query, both Utilized and Total Utilized amount holds the amount of latest version. The value is Total Utilized Amount BOT currency and Amount for Import LC/Guarantee Issuance from FXDLINKG .
   Average FX Rate	Read only field. Multiple forward FX contract could be linked,and exchange rate of FX contract vary from each. Hence, effective exchange rate for bill would be arrived using weighted average method and it is utilized during purchase/negotiation/discount or liquidation of the bill. This will be populated in the Average FX Rate.
   Action	Click Edit icon to edit the FX details. Click Delete icon to delete the FX details.

5. Click Save and Close to save the details and close the screen.
6. Click Next.
   The task will move to next data segment.

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

   Table 2-21 Additional 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 Guarantee Issuance Claim Update. 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 overrides accepted by the user.
   Customer Instruction	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, Oracle Banking Trade Finance Process Management Cloud Service user can input any Customer Instructions received as part of transaction processing. This section will be enabled only for customer initiated transactions.
   Incoming Message	Clicking this button allows the user should be able to see the message in case of STP of incoming MT 767. 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.
   View Undertaking	Clicking this button allows the user to view the undertaking details.
   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 required, system should display all the signatures
   Request Clarification	Clicking this button allows the user to submit the request for clarification to the “Trade Finance Portal” for the transactions that are initiated offline.
   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
   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.
   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.
   Save & Close	Save the details provided and holds the task in ‘My Task’ queue for further update. This option will not submit the request.
   Back	Clicking on Back button, takes the user to the previous screen.
   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.