Tuesday, February 21, 2017

Identify the types of components that cooperate to provide the business service implementation

Identify the types of components that cooperate to provide the business service implementation




  • Entity object
    An entity object represents a row in a database table and simplifies modifying its data by handling all data manipulation language (DML) operations for you. It can encapsulate business logic to ensure that your business rules are consistently enforced. You associate an entity object with others to reflect relationships in the underlying database schema to create a layer of business domain objects to reuse in multiple applications.





  • View object
    A view object represents a SQL query and simplifies working with its results. You use the SQL language to join, filter, sort, and aggregate data into the shape required by the end-user task being represented in the user interface. This includes the ability to link a view object with other entity objects to create master-detail hierarchies of any complexity. When end users modify data in the user interface, your view objects collaborate with entity objects to consistently validate and save the changes.





  • Application module
    An application module is the transactional component that UI clients use to work with application data. It defines an updateable data model along with top-level procedures and functions (called service methods) related to a logical unit of work related to an end-user task.




  • [  ]
    Explain how ADF BC components are used in a Web Application
    http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/bcdcpal.htm#BBJBDCHF


    Querying and Persisting Data
    [  ]Describe the characteristics of an ADF BC view object
    [  ]Create a view object that can be used for performing a query in a Web application
    [  ]Define a SQL statement on which to base a query for a view object
    [  ]Explain how entity objects relate to database tables
    [  ]Describe the persistence mechanism of entity objects
    [  ]Use the Create Entity Object wizard to generate entity objects from database tables
    [  ]Create associations between entity objects to represent business relationships
    [  ]Create updatable view objects based on entity objects
    [  ]Link view objects to one another in a master-detail hierarchy
    [  ]Refactor objects in an application


    Exposing Data to Clients
    [  ]Explain the role of application modules
    [  ]Describe the characteristics of application modules
    [  ]Use the Create Application Module wizard to define the data model for an application module
    [  ]Explain how application modules can manage business components transactions
    [  ]Explain how application modules can manage application stateE
    [  ]Explain the role of the ADF Model


    Declaratively Customizing Data Services
    [  ]Declaratively change data behaviour
    [  ]Declaratively modify the default behavior of view objects, entity objects, and application modules
    [  ]Define a view accessor for a list of values(LOV)
    [  ]Define a list of values (LOV) for an attribute


    Programmatically Customizing Data Services
    [  ]Generate Java classes for business components to modify default behavior programmatically
    [  ]Override class methods to change or augment default behavior
    [  ]Modify the WHERE clause of a view object at run time
    [  ]Explain the benefits of adding service methods at the application module level (rather than at the view level)
    [  ]Create a test client for testing your custom code
    [  ]Modify a view object's client code to add a new employee to the employees view object


    Validating User Input
    [  ]Describe the types of validation available for ADF applications
    [  ]Evaluate which validation options are appropriate for different validations
    [  ]Add declarative validation for an entity object
    [  ]Identify the other non-declarative validation options and when they might be used
    [  ]Describe the benefits of using domains for validation


    Troubleshooting ADF BC Applications
    [  ]Identify the JDeveloper tools for logging and diagnostics
    [  ]Use Java code auditing tools
    [  ]Make use of FileMon and Junit to debug an application
    [  ]Use the JDeveloper profiler
    [  ]Use the JDeveloper debugger
    [  ]Identify sources of Help


    Understanding UI Technologies
    [  ]Describe the use of Web browsers and HTML
    [  ]Explain how Java has come into widespread use as a language for developing Web applications
    [  ]Describe the function of Servlets and JSPs
    [  ]Define JavaServer Faces
    [  ]Explain the JSF component architecture
    [  ]Expalin some JSF component types included in the standard implementation
    [  ]Describe the purpose of backing beans
    [  ]Describe the JSF life cycle
    [  ]Explain how ADF Faces augments the JSF life cycle
    Binding UI Components to Data
    [  ]Create an empty JSF page
    [  ]Use three different ways to add ADF Faces UI components to a page
    [  ]Describe the types of data-bound components that can be added to a JSF page
    [  ]Describe the structure of an EL (Expression Language) expression
    Planning the User Interface
    [  ]Describe the Model-View-Controller design pattern
    [  ]Differentiate between bounded and unbounded task flows
    [  ]Create task flows to define control flow in an application
    [  ]Specify control flow rules
    [  ]Define global navigation
    [  ]Use routers to declaratively route control flow to activities based on an EL expression
    [  ]Define the role of managed beans in task flows
    [  ]Explain the types of validation available in the user interface


    Adding Functionality to Pages
    [  ]Internationalize the user interface so that the application can be used in multiple locales
    [  ]Use component facets to specify subordinate elements such as toolbars, headers and footers
    [  ]Implement a list of values (LOV) to enable users to select a value from a list
    [  ]Add a calendar component to an input date field to make it easy for users to select a date
    [  ]Use the table component to display structured data as a formatted table
    [  ]Employ the tree component to display hierarchical data
    [  ]Add icons and images to an application with ADF Faces output componentsE
    [  ]Create Search forms using the ADF query component
    [  ]Use ADF Data Visualization components to add charts, graphs, map etc to your JSF pages
    Implementing Navigation on Pages
    [  ]Implement command buttons and links
    [  ]Create menus - Menu bar
    [  ]Create menus - Popup
    [  ]Create menus - Context
    [  ]Use a navigation page
    [  ]Use breadcrumbs
    [  ]Create trains


    Achieving the Required Layout
    [  ]Build complex page layouts with layout components
    [  ]Explain the role of ADF Faces skins
    [  ]Use dynamic page layout
    Ensuring Reusability
    [  ]Identify the benefits of reusing components
    [  ]Create a resource catalog to enable sharing of resources within and across teams and applications
    [  ]Create ADF libraries to share components within and across teams and applications
    [  ]Create a task flow template for reuse across different bounded task flows
    [  ]Create a page template for reuse across the JSF pages in an application to enable a consistent look and feel
    [  ]Create a declarative component for reuse in different pages of an application
    [  ]Create a page fragment to use in multiple pages of the application
    [  ]Employ a bounded task flow as a region in a JSF page


    Passing Values between UI Elements
    [  ]Evaluate whether the data model contains opportunities to reduce the need for passing values between pages
    [  ]Use a managed bean to pass values between JSF pages
    [  ]Store values in memory-scoped attributes to hold and pass information between pages and life cycle phases
    [  ]Use parameters to pass information to different parts of the application
    Responding to Application Events
    [  ]Configure managed beans to contain code to respond to events
    [  ]Explain the different types of events
    [  ]Use phase listeners to listen for and respond 









    Create Data Entry Form in ADF

    Create Data Entry Form in ADF

    1. Create a New Application
    File > New > Applications > Fusion Web Application (ADF)
    Application Name – DataEntryApplication
    Directory -- (Jdev install dir)/jdeveloper/(project name) 
    Application Package Prefix – Demo.adf.DataEntryApp
     

     

     

     
    \
     

     
     
    2. We need to have table where Data will be saved. Lets Create a table
         CREATE TABLE data_entry_test
         (     Column1   VARCHAR2(100),
               Column2   VARCHAR2(100)
         );

     
    3. Create EO for Page (Entity Object)
    Right Click on Model > New > ADF Business Components > Entity Object
     
    Package -- Demo.adf.DataEntryApp.model
    Name – DataEntryEO 
    Schema Object – DATA_ENTRY_TEST
     

     

     

     
    Note – By default ROWID will be the primary key if we will not make any column to be primary key in Attribute Setting Page 
     
    Check the Accessors, Create Method, and Remove Method
     

     
    Check “Generate Default View Object CheckBox”
    Package – Demo.adf.DataEntryApp.model.queries 
    Name – DataEntryVO
     
     
    Check “Application Module” Checkbox
    Package – Demo.adf.DataEntryApp.model.services 
    Name – DataEntryAM
     

     

     
    4. Create JSF Page for Data Entry Page
    Create a JSF Page
    Right Click on ViewController > New > Web Tier > JSF > JSF Page
    File Name – DataEntry.jspx
    Initial Page Layout and Content – Quick Start Layout 
    Expand Page Implementation region and select Automatically Expose UI Components in a New Managed Bean
     

     
    Select DataControls > DataEntryAMDataControl > DataEntryVO1 and drag to jspx page and choose Form > ADF Form. Choose the fields as shown in the slide
     

     
     
    Remove RowID row
     

     
    5. Add Commit and Create Operations in Page
    Select DataControls > DataEntryAMDataControl > Operations 
    Drag Commit Operation in page
    Similarly Select DataControls > DataEntryAMDataControl > DataEntryVO1 > Operations 
    Drag Create Operation in page
     

     
     
    Select option ADF Button
     

     
    6. Select Commit button and make field Disabled in properties to be NULL
     

     
     
    7. Congratulation you have successfully finished Data Entry ADF Form. Test Your Work
     

     
    Click on Create Button
     

     
     
    Enter Data and Click Commit Button

     
    Check backend table
     

    Monday, February 20, 2017

    Tuesday, February 14, 2017

    P2P(Procure-to-Pay) Cycle Tables with Joins


    P2P(Procure-to-Pay) Cycle Tables with Joins



    Pre Requisites for Purchase Order:

    1.Item Creation:

    2.Supplier Creation:

    3.Buyer Creation:

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

    1.Item Creation:

    1)Attach the Responsibility called "Inventory Vision Operations (USA)"
    2)Open the Items form
      Items=>Master Item
    3)Select the Organization name - Vision Operations
    4)Enter the Item Name , Item Description 
      goto Inventory tab check the checkbox called Inventory 
      goto purchasing tab check the check box called Purchasing
    5)Save
    6)Goto  Tools Menu => Organization Assignment option to assign for the multiple
      organizations.

    SELECT * FROM MTL_SYSTEM_ITEMS_B WHERE SEGMENT1='APACHE'  --INVENTORY_ITEM_ID=20817


    2.Supplier Creation:

    1)Attach the Responsibility called "Purchasing Vision Operations (USA)"
    2)Goto the Supplier Form
      Supply Base=>Suppliers
    3)Enter the Supplier Name . Save supplier number will be created automatically.
    4)Select the Sites button enter the supplier site address and other details
    5)Goto the Contacts tab enter the Contact details 
        Name
        Phno
        Postion and so on.....





    SELECT * FROM PO_VENDORS WHERE SEGMENT1='20067' --VENDOR_ID=7930

    SELECT * FROM PO_VENDOR_SITES_ALL WHERE VENDOR_ID=7930 --VENDOR_SITE_ID IN (4638,4639)

    SELECT * FROM PO_VENDOR_CONTACTS WHERE VENDOR_SITE_ID IN (4638,4639)


    3.Buyer Creation:


    Buyer Creation:
    ==================

    1)attach the Responsibility called "US HRMS Manager"
    2)Create Employee  
      People => Enter and Maintain=>Select New button
    3)Enter Emp name 
      select action option select "create Employement" select the optiona s "Buyer"
    4)enter Data of Birth 
      save => Ok  = > Empoyee number will be generated.
    5)Goto  System Administrator open the User form create or query user
      select the Person field attach the emp name (Which we have created)
    6)Save.
    7)Goto Purchasing Responsibility 
      open the Buyers form 
      enter the employee name and save the transactions.
     Setup => Personnal =>Buyers


    SELECT * FROM PER_ALL_PEOPLE_F --WHERE --PERSON_ID='25'--EMPLOYEE_NUMBER='1289' --PERSON_ID=13496


    Purchase Order Flow:

    1.Requisition
    2.RFQ(Request for Quatation)

    1.REQUISITION:

    Requisition: is one of the purchasing document will be prepared by the employee when
       ever he required the materials or Services or Training and so on.
    we have two types of Requisitions 1)Internal
                        2)Purchase

    Internal requisition will be created if materials are receiving from another Inventory
    inside of the organization.
    Purchase requisition will be created while purchasing the materials from the Suppliers.

    Requisitions=>Requisitions

    We will enter the Requisition at three level 1)Header
                            2)Line
                            3)Distributions.

    Open the Requisition form enter the Reqno and select the type at Header level
     Enter the Items information at line level like Item name,qty,unitprice,tax and so on
    select Distributions button enter the Distributions details.
    Save
    Select the Button called Approve button to go for approving the Requisition Document
    Open the Requisition summary form.
    Enter the Reqno select find button we can find the Requisition status wether it is
    approved or not.
    select Tools menu => View Action History to find the history details
    Select Tools Menu  =>Control option to Cancel the requisition.


    SELECT * FROM PO_REQUISITION_HEADERS_ALL WHERE SEGMENT1='5716' --REQUISITION_HEADER_ID=56885

    SELECT * FROM PO_REQUISITION_LINES_ALL WHERE REQUISITION_HEADER_ID=56885  --REQUISITION_LINE_ID=60797

    SELECT * FROM PO_REQ_DISTRIBUTIONS_ALL WHERE REQUISITION_LINE_ID=60797

    2.RFQ(REQUEST FOR QUOTATION)



    Once the Requisition is Approved Buyer will prepare thre RFQ document which will be
    delivered to the supplier. Supplier will respond for that with quotation.
    we have Three types of RFQ documents

    BID RFQ:This will be prepared for the secific fixed quantity and there won't be any
            PriceBraeaks(Discounts).

    catalog RFQ: This will be create for te materials which we will purchase from the
            suppliers regularley , and large number of quantity. Here we can specify the
            Price Breaks.

    Standard RFQ:  This will be prepared for the Items which we will purchase only once
            not very often,Here we can include the Discounts information at different
            auantity levels.
    RFQ Information will be entered at 3 Level
      1)Headers
      2)Lines
      3)Price Breaks(CATALOG,STANDARD) or Shippments (Only for Bid RFQ)

    Terms And Conditions:
    While creation of the RFQ documents we will select the Terms button and we will enter
    the terms abd condition details.

    Payment Terms: When Organization is going to make the payment and Interest rates
    Fright  Terms: Who is going to Bear the Tansportation chargers wether Buyer or Supplier
    FOB(FreeOnBoard): If any materials damage or any missing quantity is there then the
                 the responsiboility of those materials.
    Carrier     : In which Transportation Company Organization Required Materials
                  Transportation company Name.

    Open the RFQ Form

    RFQ and Quotations=>RFQ's
    select TYpe and Dates and so on
    enter the Items details at line level
    select terms button enter the Terms and Condition Details
    Select the Price Braks button enter the Price break details
    Save
    Select the suppliers button enter the suplier details (Who are receiving this Document)
    Select the Button called Add from List to Include the supplier list automatically.


    SELECT * FROM PO_HEADERS_ALL WHERE SEGMENT1='347' AND TYPE_LOOKUP_CODE='RFQ' --PO_HEADER_ID=32876

    SELECT * FROM PO_LINES_ALL WHERE PO_HEADER_ID=32876 -- PO_LINE_ID=38063

    SELECT * FROM PO_LINE_LOCATIONS_ALL WHERE PO_LINE_ID=38063 --LINE_LOCATION_ID=72425

    3.QUOTATION:



    Quotation is another purchasing document we will receive from the Supplier which
    contains the supplier quote details , Price, Payment terms and so on.

    Whatever the quotations we have received from the supplier we will enter in the system
    through form.

    We have three types of Quotations 1)Bid 2)Catalog 3)Standard

    For Bid RFQ      we will  receive Bid      quotation from the Supplier
    For Catalog RFQ  we will  receive Catalog  quotation from the Supplier
    For Standard RFQ we will  receive Standard quotation from the Supplier.

    After enter all the quotations in the system management will do quote analysis as per
    that one best quotation will be elected as Purchase Order.

    Quotation Report

    Item Name   (Table Value set MTL_SYSTEM_ITEMS_B   Segment1)

    QuoteNo Type  Cdate Supplier Site ContactPerson Buyer   Created(UserName)

    4.PURCHASE ORDER:

    PO is one of the Main document which will be prepared and approved by the buyer and
    send it to the supplier. which contains the following information
    terms and Conditions
    Items deails
    Qty,Price
    Distiribution and Shipment Details and so on.

    We have four types of Purchase Order       1)STANDARD
         2)PLANNED
         3)BLANKET
         4)CONTRACT

    Purchase Orders=> Purchase Orders
    Open the PO form enter the Inforamtion at header level select line level inforamtion
    enter the items and quantity,price details
    select shippments button enter the shippment details select the Distributions button
    enter the Distribution Detauils.
    Save
    Select the Button called Approve (Uncheck Email Check Box) , Document will be submitted
    for approval.
    open the Purchase Order summary form  enter PO number Select Find button we can find
    the status of the Purchase order.
    Goto Tools menu
    Action History => We can find who hs submitted for Approve /Reject /Cancel details
    Copy Document  => To Create Another PO based on this PO
    Control        => To Close the Purchase Order or to cancel the Purchase Order.


    Types of Purchase Order: -


    Standard P.O
    Planned P.O
    Blanket P.O
    ContractP.O
    Terms and Conditions
    Goods or Service Known
    Pricing Known
    Quantity known
    Account Distributions Known
    Delivery Schedule Known
    Can be Encumbered
    Can Encumber releases
    Yes
    Yes
    Yes
    Yes
    Yes
    Yes
    Yes
    N/A

    Yes
    Yes
    Yes
    Yes
    Yes
    May be
    Yes
    Yes

    Yes
    Yes
    May be
    No
    No
    No
    No
    Yes

    Yes
    No
    No
    No
    No
    No
    No
    N/A





    SELECT * FROM PO_HEADERS_ALL WHERE SEGMENT1='4514' AND TYPE_LOOKUP_CODE='STANDARD' --PO_HEADER_ID =32878
     --TYPE_LOOKUP_CODE

    SELECT * FROM PO_LINES_ALL WHERE PO_HEADER_ID =32879 --PO_LINE_ID=38065

    SELECT * FROM PO_LINE_LOCATIONS_ALL WHERE PO_LINE_ID=38066 --LINE_LOCATION_ID=72427

    SELECT * FROM PO_DISTRIBUTIONS_ALL WHERE LINE_LOCATION_ID=72428

    SELECT * FROM PO_LOOKUP_CODES --LOOKUP_CODE

    AUTO CREATE:


    It is one of the Purchasing feature to create the RFQ and  PO documents automatically
    by using requisition lines.

    1)Create Requisition and approve
    2)Open the AutoCreate form
    3)Select Clear button enter the RequisitionNO
    4)Select find button which will shows all the requisition lines
      select the lines whatever we want to include into the RFQ
    5)select Action = Create to create new RFQ
      AddTo  to add lines to exisiting to RFQ
    6)Select DocumentType = RFQ
    7)select Automatic button which will create RFQ document automatically .

    5.RECEIPTS:



               Receipts are one of the documents it will be used to find out how much quantity Supplier has supplied. We will find out Purchase Order status if it is successfully approved then we will create the Receipt. We will give the PO Number select Findbutton check the PO lines right mark and save. It will create the Receipt number select Header button it will shows the receipt number and date.           
                                                                                                                                                                   SELECT * FROM RCV_SHIPMENT_HEADERS WHERE RECEIPT_NUM=7472 --SHIPMENT_HEADER_ID=61421


    SELECT * FROM RCV_SHIPMENT_LINES WHERE SHIPMENT_HEADER_ID=61421 -- SHIPMENT_LINE_ID=68368

    SELECT * FROM RCV_TRANSACTIONS WHERE SHIPMENT_HEADER_ID=61421

    Once Receipt will created go Inventory module and check whether the requested items are received or not by using these tables.

    SELECT * FROM MTL_SYSTEM_ITEMS_B WHERE SEGMENT1='APACHE'

    SELECT * FROM MTL_ONHAND_QUANTITIES WHERE INVENTORY_ITEM_ID=20817 AND ORGANIZATION_ID=204

    SELECT SEGMENT1 FROM PO_HEADERS_ALL WHERE PO_HEADER_ID=32881 AND TYPE_LOOKUP_CODE='STANDARD'


    Match Approval Level :- While creating the Purchase Order we will mention the Match Approval Level at Shipments we will have 3 types they are

    2-way:- Purchase Order and Invoice Quantities must match within tolerance before the corresponding invoice can be paid.
    3-way:- Purchase Order, Receipts and Invoice Quantities must match with in tolerance before the corresponding invoice can be paid.
    4-way:- Purchase Order, Receipts, Inspection and Invoice Quantities must match with in tolerance before the corresponding invoice can be paid.



    Account Payables (A.P) Module:-
               Account payables will be used to do the payment transactions. A.P Module is integrated with both P.O and G.L Modules. In Account Payables we will create the invoices and we will approve once invoice is approved successfully we will make the payment. Once payment is over we will move the transactions from A.P to G.l.

    1.  Without supplier we cannot create Invoice.
    2.  Without invoice we cannot make Payment.                                      

    From the company point of view a person or Organization who is going to receive amount we will call as Supplier.

    Types of Invoices:-

    1.     Standard
    2.     Credit Memo
    3.     Debit Memo
    4.     With Holding Tax                                                                                   
    5.     Po Default
    6.     Mixed
    7.     Pre Payment
    8.     Expense Report
    9.     Recurring Invoices
    10.  Quick Match                                                                                

    Standard Invoice:-    We will create the Standard Invoice to particular Supplier and Supplier site we will enter the invoice amount, invoice date and soon……..

    Credit Memo & Debit Memo Invoices:- Both Invoices has got negative (-ve) amount and adjusted against Standard Invoice. Credit Memo will be created whenever Supplier is giving discount. Debit Memo will be created if buyer is going to deduct the amount.

    With Holding Tax Invoice:-      If supplier is not registered supplier then buyer will make the Income Tax to the government on behalf of supplier.

    Po Default Invoice:-    Here we will create the Invoice as per Purchase Order amount. We will give the Po number system will retrieve PO amount and Invoice will be created as per PO details.

    Prepayment Invoice:-    When ever we want make payment to supplier in advance that tome we will create this Prepayment Invoice and we make the Payment.

    Expense Reports Invoice:-     It will be created for employee expenses as per the employee grade, position this Invoices will be calculated.

    Recurring Invoice:-      For some of the Invoices we will not be having supplier invoice that time we will create Recurring Invoices.

    Ex:-  For rent account we will be creating Invoice which has got fixed amount and fixed rate (duration).
     Quick Match Invoice:- While creating Purchase Order we will be giving the match approval option as per that match approval we will create the Invoice and the Invoice type is Quick Match Invoice.

    Mixed Invoice:- Mixed Invoices will be created for miscellaneous expenses. Once we create the invoice you have to do following 3 activities.
    1.     Validate Invoice
    2.     Approve the Invoice
    3.     Create Accounting entries for Invoice 
     INVOICES
    Here we will select the Invoice type and we will give the Supplier number, name, site invoice date, invoice number, invoice currencies, and amount. Select Distributions button to distribute the Invoice amount into different accounts.

    1.     Invoice total should be equal to the distributions total then we will call it as Invoice validated successfully.
    2.     Select Actions…1 button chooses approve check box press OK then system will approve the Invoice.
    3.     Select Actions…1 button choose create accounting check box press OK button it will create the accounting entries we can see all this accounting transactions from tools view accounting option.



    SELECT * FROM AP_INVOICES_ALL WHERE INVOICE_NUM='INV4516'  --INVOICE_ID=63379 ,--VENDOR_ID(LINK B/WAP INVOICE AND PO_VENDORS
    )
    SELECT * FROM AP_INVOICE_DISTRIBUTIONS_ALL WHERE INVOICE_ID=63379


    Invoice Holds:-    If invoice is not approved then that invoice will be keeping under hold status. By selecting holds button in invoice form we can see the holds details.

    For view Invoice holds details:
               Select * from ap_holds_all
    For view release the Invoice holds names:
               Select * from ap_holds_release_name_v;

    PAYMENTS:
    Payments:-     Once the Invoice is approved then we can go for payments. The Payments are or 3 types. They were

    1.     Manual
    2.     Quick
    3.     Refund

    Manual:-    Here we will issue the checks manually to the supplier and we will capture that information in the payment scheme by using manual payment option.

    Quick:-     Through the Quick Payment type we can generate checks through the system and we can have the transactions directly in the system.

    Refund:-   When ever company is going to give advance back to the customer that time we will select payment type as Refund.
    Navigation steps for Payments:-
                     payments  ==> payments
    For view list of payments:
               Select * from ap_invoice_payments_all;
               Select * from ap_payment_schedules_all;
    For check’s information:
               Select * from ap_checks_all;
    For check format:
               Select * from ap_check_formats;
               Select * from ap_checkrun_conc_processes_all;


    Distribution Set:-     It is one of the option is available in Invoices Screen. While creating the Invoice we will attach distribution set. System will automatically create the transactions in distributions forms as per the distribution set.
     Navigation:




     set-up =>invoice=> distribution set

    To view Distribution sets at header level:
               Select * from ap_distribution_sets_all;
    To view Distribution sets at lines level:
               Select * from ap_distribution_set_lines_all;

    Transferring Transactions from AP to GL:-
               We will execute the concurrent program from SRS Window. This program will transfer all the payment transactions into the G.L Module. It will take following parameters.

    Program Name:-   Payables Transfer to General Ledger
    Parameters:-
               Set of Books Name
               Transfer Reporting Book(s)
               From Date
               To Date
               Journal Category
    Validate Accounts
    Transfer To GL Interface
    Submit Journal Import :  yes  (It should be always YES)
    To view from AP to GL:

               Select * from gl_interface;

    To view journal import details:

               Select * from gl_je_headers  Ã        for Headers
               Select * from gl_je_lines      Ã        for Lines
               Select * from gl_je_batches  Ã        for Batches

    To view posting:
              
               Select * from gl_balances;
              
               After submitting the request select viewà output button. It will shows number of transactions has been transferred to G.L. then select G.L Module (General Ledger, Vision Operations (USA)).




    SELECT * FROM GL_JE_HEADERS

    SELECT * FROM GL_JE_LINES

    SELECT * FROM GL_JE_BATCHES

    SELECT * FROM GL_BALANCES

    Oracle Fusion - Cost Lines and Expenditure Item link in Projects

    SELECT   ccd.transaction_id,ex.expenditure_item_id,cacat.serial_number FROM fusion.CST_INV_TRANSACTIONS cit,   fusion.cst_cost_distribution_...