Sales Order Integration

 Sales Order Integration -Inbound

AppDriven Based on Business Event  :

Prelude: A Sales order of type Replinishment Prepaid when ever created in Fusion OM.SO to PO Integeration will be created scheduled for every 10 min. SO Line EFF details are updated after 

After Receving Goods,

Create Receiving Receipt Event - ERP Cloud integration

SO of different of order type as BILL and Reload

Assign From Lookup to Variables Audit Integration is invoked for storing - instance id , rundate, end date , status set to new, int Name,

Logger To verify Type of order,

define main scope

Payloads and Files will be set to Object Storage

XML-File reference  --> stage write -> XML to XSD online compailer, 

Namespace, Bucket , Filename are mandatory parameters

Invoke DB procedure to Load From Object Storage to DB in order to minimise performance issues

dbms_cloud.

get object --> Credential Name, Complete URL of  Object Storage -- get lob

to_clob()-> to convert lob to clob

Poulated into ATP-- generic Table

Actual Integration:

Cost Collector Integration is invoked 

Dependent Jobs has to be completed -- before creating SO.

Transfer Transaction from receving to costing

Transfer Trasaction from inv to costing

Create Cost accounting Distributions

While Loop -->  Ess Job Status -- BIP Report Called to Get Job set Status,

Ess Request History-- 

Switch Condition

Status --Success or Warning -> BIP Report for Fetch additional Details not present in Response of Businees Event.

Parameters- P_Source PO Type / TO Type

                    PO/TO LineID 

                    Shipment Line ID

SWITCH -- Source Order Number != null

branch1: Scope level Fault handler is added Notification as Errored

Sales Order Generated and Notification as Success

 branch2:  Call Audit Integration and update status as Success 

Instances -ATP

 

A2CFATP-DB

A2CFATP_DB_Connection_Json to Import

Create OIC User and Assign user to Groups

 Create OIC User and Assign user to Groups 

Login to OCI using Admin User :

Navigate to : Identity and Security >>Domain >>Click on Default domain >>User Management >>Create User

First Name : A2CF

Last Name : Viewer 

Email : apps2cloudfusion@gmail.com 

and select Groups to user 

OIC Instance Creation and enable File Server, VBCS and PCS

 OIC  Instance Creation

How to create OIC Instance in OCI?

Login to https://cloud.oracle.com/?region=ap-hyderabad-1

Developer Services >Application Integration >>Integration>>Choose Compartment >>Create Instance >>Select integration instance hyperlink

Copy service console URL https://int1-axz05smvuqua-hy.integration.ap-hyderabad-1.ocp.oraclecloud.com/

Copy OCID ocid1.integrationinstance.oc1.ap-hyderabad-1.amaaaaaajid5unqady4n77bae6nqzaawqkjkcwww6nqq4x22vjzgfa6xohgq

Enable below options with in Integration instance 

File Server 

VBCS

PCS 

Create User

Identity and Security >>Domain >>Click on Default domain >>User Management >>Create User

First Name : A2CF Last Name : Viewer Email : apps2cloudfusion@gmail.com and select Groups 

Prerequisites to create OIC instance 

---------------------------------------

Use Private Window/Incognito mode 

Sign in page https://signup.cloud.oracle.com/?sourceType=_ref_coc-asset-opcSignIn&language=en_US?redirect_uri=https://cloud.oracle.com/

Email address should be unique

fill all details during sign up with respect to Credit card holder and address 

we will get emial activation --should do it over desktop not over phone and to be finish in single shot 

Phone no should be unique and enter address as per credit card

Create payment method as credit card details 

select individual as category  

select home region hyd/mumbai/singapore

credit card which has international transactions set on 

OIC Roles

 OIC Roles

Identity and Security >>Domains >>Select Domain>>Oracle Cloud Services >>Select integration service as highlighted below 

Navigate to Application Roles>>Against Role >>Perform below actions like Manage Users>Search  and Assign User to the corresponding Roles

Even we can down load csv format  template to load in Bulk of User ,Roles 

1. AppRoleMembership.csv --To assign users to roles in bulk
2. Groups --To create Groups 
3. Users --To Create Users 
4. UsersAccounts --to Create User Accounts (Activate accounts)

Sample format for Assign users to Application roles (Point 1 in above list)

HIL Supplier Interfaces -Outbound

 

                         

ü  Project Scope –

 

HIL AMS is the support project in which we have a below focused scope of work as an Oracle Cloud Functional Consultant –

 

ü  Creation of Supplier Master Data in Oracle SAAS which was further replicated in Oracle E – Business Suite.

 

ü  Basically, Oracle SAAS integration with Oracle E – Business Suite through OIC & SOA.

ü  Integration of Supplier Registration Page with GSTIN field with the Government Site through OIC (Oracle Integration Cloud) it calls the Fusion Report and “Signet” interact with Indian Government Portal and through that which we can validate the Information (In Layman language Integration between GSTIN Number validation & cross verification through Indian Government Site).

OIC Integration Name :INTG_SX_TP_CYGNET_ValidateGSTIN

ü  Integration between Oracle SAAS Supplier Master with the Oracle E – Business Suite through SOA.

ü  RFQ (Draft Status in Oracle E – Business Suite) Integration with Oracle SAAS for further Sourcing Cycle happens in Oracle SAAS, but the PO Documents get created in Oracle E – Business Suite.

ü  Manually the Supplier Registration Process happens in Oracle SAAS.

 

 

ü  Basic Integration Process Flow –

 

 

 HIL Supplier Interfaces -Outbound 

ü  Supplier Registration Methods –

 

Supplier Registration can be done through 4 ways in Oracle Cloud, 4 methods as follows –

 

ü  Manual.

ü  External Supplier Registration

ü  Internal Supplier Registration

ü  Import Supplier (Bulk Upload through FBDI)

 

External Supplier Registration – From the below Pathway we can copy the link and send that link to supplier to fill mandatory information.

 

Pathway –

 

Setup & Maintenance > Procurement > Procurement Foundations > Configure Procurement Business Function

 

Note - Copy the URL and sent to Supplier for Registration.

 

 

 

Internal Supplier Registration – From the below Pathway we can be able to Register the Supplier Internally (Supplier Manager or Buyer Generally Perform this Function by gathering the necessary information from Supplier).

 

Pathway –

 

Procurement > Suppliers > Register Supplier

 

Step 1 – Please navigate from the Home Page Procurement > Suppliers > Register Supplier.

 

 

 

Step 2 – Fill out all the Mandatory Information & Register.

 

 

 

 

ü  Supplier Registration Process (Fill Mandatory Inputs as per HIL) –

 

Step 1 – Please navigate from the Home Page Procurement > Suppliers > Register Supplier.

 

 

 

Step 2 – Fill out the Mandatory Information which is required for Supplier Registration.

 

A)     Registration Details -

 

ü  Company Name

ü  Business Relationship

ü  Request Reason

 

 

B)     Company Details –

 

ü  Organization Type

ü  Supplier Type

 

C)    Additional Information –

 

ü  Company Identification Number (Only if your 4^th Letter of Pan Card is “C”).

ü  CIN Status

 

D)    Contacts Information –

Create a contact from Supplier Side and if we want, we can assign Supplier Roles as well.

 

Fill the basic details of Point of Contact from Supplier Side like –

 

ü  First Name

ü  Last Name

ü  Email ID

ü  Phone Number

ü  User Account Checkmark

 

Step 3 – Click on Register Supplier automatically request goes for Approval (Internal Supplier Registration Approval).

 

 

 

 

ü  Approval Management Configuration –

 

Approvals Configuration is different for Internal & External Supplier Registration.

 

Pathway –

 

Setup & Maintenance > Procurement > Approval Management > Manage Internal Supplier Registration Approvals / Manage Supplier Registration Approvals / Manage Supplier Spend Authorization Approvals / Manage Supplier Profile Change Approval

 

 

ü  Manage Internal Registration Approvals –

 

Pathway –

 

Setup & Maintenance > Procurement > Approval Management > Manage Internal Supplier Registration Approvals

 

 

Step 1 – Create a Rule for Selected Approval Type (Parallel Approval First Responder Win) also please select the Priority Level.

 

 

 

Step 2 – For predefined Rule Set we must add Condition (Like Inviting Procurement BU is equals to value).

 

Basically, we are giving Attributes and Values.

 

 

Step 3 – For the Rule & Condition now, we need to setup the Action which has been followed by that specific condition under that rule.

 

Basically, to setup an Action under Rule & Condition we must select “Action Type” and Route Used as “Approval Group” and in the Approval Group we must select the Approval Group which we have setup for Internal Supplier Registration process in the “BPM Worklist”.

 

 

 

Step 3 – The Approvals Rule which we have configure needs to be “Deployed”. So that this approval route is enabled.

 

ü  BPM Worklist Configuration (To Create Approval Groups) –

 

Step 1 – Internal Supplier Registration Approval Groups Setup as per the Branch Plant we can configured by following the below Pathway –

 

Pathway –

 

Setup & Maintenance > Procurement > Approval Management > Manage Approval Group

 

 

Step 2 – Once we enter in BPM Worklist Page, we should click on Right Hand Side Groups “+” to create a New Approval Group.

 

Step 3 – Then we can Provide the “Name” and add members username as per the Business Requirement to create the Approval Hierarchy.

 

 

a)      Click on “+” add & put a member in Approval Level Hierarchy.

b)     Select User.

c)      Add Username (In Member Field).

d)     Click on “OK”.

e)      User Added into Approval Group.

 

 

 

 

Note – This setup will remain common for Manage Internal Supplier Registration Approvals / Manage Supplier Registration Approvals / Manage Supplier Spend Authorization Approvals / Manage Supplier Profile Change Approval.

 

Pathway –

Setup & Maintenance > Procurement > Approval Management > Manage Internal Supplier Registration Approvals / Manage Supplier Registration Approvals / Manage Supplier Spend Authorization Approvals / Manage Supplier Profile Change Approval.

 

 

§  Integrations –

 

 We have currently 4 types of Integrations in HIL AMS –

 

A)     Oracle Cloud Supplier Master Data Integration with Oracle EBS through SOA & OCI.

B)     Oracle Cloud Supplier Data Validation like GSTIN Field Validation with Indian Government Portal who validates GSTIN Information of Suppliers.

C)    Oracle Cloud Supplier Data Validation like PAN Card Field Validation through Internally Developed JAVA Script with specific logic.

D)    RFQ Integration when RFQ Initiated through Oracle EBS and once its in Draft Status it will automatically reflect in Oracle Cloud till Supplier Awarding post awarding at the time of PO Creation, we can create a PO through Oracle EBS (Outbound & Inbound Integration between Oracle EBS & Oracle Cloud).

 

 

 

 

 

A)     Oracle Cloud Supplier Master Data Integration with Oracle EBS through SOA & OCI -

         

 

Conditions for Integration –

 

Data will be transmitted from Oracle Cloud to Oracle EBS if conditions as follows,

 

a)      Pan Card Details & GSTIN Number must be validated.

b)     Supplier must be Spend Authorized.

 

 

Information Flow Details –

 

ü  Once the above two conditions meet and supplier registration process is completed, post that we can be able to see that supplier in “Manage Suppliers” in Oracle Cloud.

ü  Whatever the supplier information we register in Oracle Cloud that should reflect in Oracle Cloud and the information flows as per the above Process Flow Diagram.

ü  Once Supplier Register all the Information will feed to “Supplier Master Data Table” in Oracle Cloud.

ü  From the Supplier Master Data Table of Oracle Cloud through Transformation Logic of “OIC” & “SOA” data has been transferred to Oracle EBS “Custom Staging Table”

ü  Now the Scheduler Program has already been set up in Oracle EBS which was run on a time basis. The Program Name in the Oracle EBS is “XXHL Import Supplier Cloud Program”

 

Purpose of the Program – This Program runs automatically & concurrently on a time basis which will fetch all the data from SOA & store it in Oracle EBS Base Table.

 

If we want to run this program manually, we need to give two parameters “From Date” & “To Date” to fetch the records from Cloud to EBS.

 

ü  Post successful completion of this program all the records related to Supplier (Registration / Profile Change / Site Change / Contact Change) any change will replicate in the Oracle EBS.

 

 

B)     Oracle Cloud Supplier Data Validation like GSTIN Field Validation with Indian Government Portal who validates GSTIN Information of Suppliers –

 

 

 

 

Conditions for Integration –

 

 

Data will be transmitted from Oracle Cloud to Indian Government (GSTIN Validation

Check Site) to verify supplier GSTIN Number.

 

a)      GSTIN Number must be validated through Indian Government GST Site

(Site - https://services.gst.gov.in/services/searchtp )

 

 

Information Flow Details –

 

ü  The flow works basically at the time of supplier registration we suppose to enter “GSTIN Registration & Number” also specify the “GSTIN Classification.” While creating a Adress Records at the time of Supplier Registration.

 

ü  This Data from Oracle Cloud will push to “Signet Interface” basically this data goes into Integration Custom Report i.e.  Unverified GSTIN Details Report post supplier details get enter and then.

 

 

ü  Signet will take a data from the Custom Report which runs automatically on Scheduler Basis and post mapping push that data to Indian Government GST Site (Site - https://services.gst.gov.in/services/searchtp) to validate the GSTIN Number Information enter by supplier.-

 

ü  Post Supplier GSTIN Validation Signet take data from Indian Government Site Mapped the Fields which we have in Oracle Cloud and sent back the Additional Information to Cloud and get it stored in Supplier Master.

 

 

 

 

 

 

 

 

 

 

GSTIN Number Nomenclature –

 

 

 

 

 

 

 

 

 

 

 

 

 

C)    Oracle Cloud Supplier Data Validation like PAN Card Field Validation through Internally Developed JAVA Script with specified logic set by Technical Team –

 

 

Conditions for Integration –

 

 

Data has been validated through Java Script which has been developed by technical team to validate the Pan Card Details

 

a)      Pan Card has been verified by JavaScript.

b)     JavaScript logic might be based on First 5 Alphabets with 4^th Letter has a specific significance where we can say its CIN register and 5^th Letter has a specific significance where it indicates the First Letter of Surname then after 5 Alphabets any 4 Numbers (Any) and at last again 1 Alphabet (Any)

 

c)      The Logic is when any supplier registers its Pan Card Details and suppliers with 4^th Letter of Pan Card is bydefault “C” whose CIN has been registered where “C= Company”.

 

Pan Card Nomenclature –