Mandatory Profile Options in order to setup Oracle iSupplier

Important (Must have) Profile options to setup Oracle iSupplier module 

This article will allow you to have an idea of all the important profile options and their values. 

Go through it and let us know if there are any more details required.

Profile options	Value	Description
RCV: Fail All ASN Lines if One Line Fails	No/Yes Default :No	Indicates whether the creation of ASN/ASBNs in Oracle Internet Supplier Portal will fail all ASN lines if one line Fails.
POS: Limit invoice to single PO	No/Yes Default: No	Indicates whether an Invoice created in Internet Supplier Portal will be limited to the shipments belonging to a single Purchase Order
POS: Invoice Unit Price change for Quantity-Based Matches	Allowable type of price Change.	Whether the user is allowed to change the unit price when creating purchase order-based Invoices.
POS: Allow Invoice Backdating	Yes/No	Whether the use is allowed to backdate the invoice such that the invoice and the purchase Orders have different dates.
POS: Default Promise date acknowledgement	Yes/No	If the promise date is null, whether the promise date defaults to the need-by date after supplier's Acknowledgement.
POS: OSN Hub	Hub name	The name of the pre-defined hub for communication with Oracle Supplier Network. The hub is defined in Oracle XML Gateway.
EDR: E-Records and E-Signatures	No/Yes	Indicates whether E-Signature functionality has been enabled
POS: ASL planning attribute updates from supplier approved by	Buyer's Approval Required Planner's Approval Required No Approval Required	Indicates the person whose approval is required when supplier submits changes via Order Modifiers and Maintain Capacity functionality
POS: ASN Shipment Display Period	Number of days
Default load setting for number of sites allowed to be created during address approval		Limits the number of sites that can be created during a single address approval operation.

Credit Check functionality in Oracle applications functional

Credit checking feature of Oracle OM provides the ability to check that the customer has sufficient credit available with the organization at the point of order booking ,picking, packing and shipping. Credit check rules, order transaction type, payment terms and credit profiles are the key setup entities that influence the credit check process.

Oracle OM credit checking includes:

• Validating orders and lines against existing credit limits defined in the credit profile.
• Placing credit holds at either the order or line level.
• Sending credit hold notifications to order creator.
• Automatically apply or release order or order line credit holds using credit check processor program.
• Reporting and querying tools to effectively manage your credit processes and ensure credit holds are processed in a timely manner.

Main purpose of Credit checking process is to minimize the financial risk that the organization assumes as a result of day-to-day transactions.

For Detailed setup of this functionality kindly check below video. It has covered all the mandatory setups required to have this functionality. Also, It has one test cycle included into it.