Skip to main content

Script to insert on hand quantity in to MTL_TRANSACTIONS_INTERFACE




Script to insert on hand quantity  into MTL_TRANSACTIONS_INTERFACE

To insert on hand quantity  into MTL_TRANSACTIONS_INTERFACE



INSERT INTO MTL_TRANSACTIONS_INTERFACE
                            (
    TRANSACTION_INTERFACE_ID,
                   SOURCE_CODE,
                            SOURCE_LINE_ID,
                            SOURCE_HEADER_ID,
                            PROCESS_FLAG,
                            VALIDATION_REQUIRED,
                            TRANSACTION_MODE,
                            LOCK_FLAG,
                            LAST_UPDATE_DATE,
                            LAST_UPDATED_BY,
                            CREATION_DATE,
                            CREATED_BY,
                            INVENTORY_ITEM_ID,
                            ORGANIZATION_ID,
                            TRANSACTION_QUANTITY ,
                       TRANSACTION_UOM,
                            TRANSACTION_DATE,
                            SUBINVENTORY_CODE,
   locator_id,
                            DISTRIBUTION_ACCOUNT_ID,
                            TRANSACTION_TYPE_ID ,
   flow_schedule,
   scheduled_flag
                            )
                 VALUES(
                            MTL_MATERIAL_TRANSACTIONS_S.nextval ,--TRANSACTION_INTERFACE_ID,
                   'ORATECH_LEGACY',--SOURCE_CODE,
                            1,--SOURCE_LINE_ID,
                            1,--SOURCE_HEADER_ID,
                            1,--PROCESS_FLAG,
                            1, --VALIDATION_REQUIRED,
                            3,--TRANSACTION_MODE,
                            2,--LOCK_FLAG,
                            sysdate,--LAST_UPDATE_DATE,
                            1318,--LAST_UPDATED_BY,
                            sysdate,--CREATION_DATE,
                            1318,--CREATED_BY,
                            6068,--INVENTORY_ITEM_ID,
                            204,--ORGANIZATION_ID,
                            15,--TRANSACTION_QUANTITY ,
                       'EA',--TRANSACTION_UOM,
                            to_date('25-11-2007','DD-MM-YYYY'),--TRANSACTIOn_DATE
                            'AWC_MS',--SUBINVENTORY_CODE,
   2034,--locator_id,
                            13401,--DISTRIBUTION_ACCOUNT_ID,
                            42,--TRANSACTION_TYPE_ID ,
   'Y',--flow_schedule
   2--scheduled_flag)
)





Script to insert on hand quantity into MTL_TRANSACTIONS_INTERFACE

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide
Labels:

Comments

Post a Comment

Popular posts from this blog

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12?

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12? The main purpose of a lookup is to keep programs flexible and easier to configure. Lookups are an approach of creating a configurable “list of values” in E-Business Suite. One of the simplest examples of a lookup type is gender. A “gender lookup” will have definitions as shown next: Code       Meaning M             Male F              Female U             Unknown Suppose that there is a table for employees named PER_ALL_PEOPLE_F and it has the following columns: FIRST_NAME LAST_NAME DATE_OF_BIRTH GENDER The screen that displays an employee’s gender will display a value of Male, Female, or Unknown. However, the database column PER_ALL_PEOPLE_F table. GENDER will store a value of M, F, or U. Hence, the screen displays the meaning, whereas the dat...
Post a Comment
Read more

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

Main Interface and Base table in Oracle Apps R12 GL Module (General Ledger Module tables in Oracle Apps R12) Interface Table Base Table gl_interface gl_budget_interface gl_je_batches gl_je_headers gl_je_lines gl_je_sources gl_je_categories gl_sets_of_books gl_daily_rates gl_balances gl_periods gl_period_sets gl_code_conbinations AR Module (Account Receivable Module  tables  in Oracle Apps R12) Interface Table Base Table ra_customers_interface_all   ra_contact_phones_int_all ra_customer_profiles_int_all hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles ra_interface_lines_all ra_interface_distributions_all ra_interface_salescredits_all ra_customer_trx_all ra_customer_trx_lines_all ra_cust_trx_line_gl_dist_all ra_cust_trx_types_all ar_payment_schedules_all ra_batch_sources_All ar_vat_tax_all ra_terms ...
2 comments
Read more

Example of $FLEX$ Syntax Used In Value Set

Example of $FLEX$ Syntax Used In Value Set ($flex$ in oracle apps) Example of using “ :$FLEX$.Value_Set_Name” to set up value sets where one segment depends on a prior segment that itself depends on a prior segment. Suppose you have a three-segment flexfield where the first segment is Country , the second segment is State , and the third segment is District . You could limit your third segment's values to only include Districts that are available for the Address specified in the first two segments. Your three value sets might be defined as follows:  Segment Name               Country_Segment Value Set Name              Country_Value_Set Validation Table              Country_Table Value Column                Country_NAME Description Column    ...
5 comments
Read more