Transaction type of IOM

Similar Questions

• Is it possible to create Transaction Type command in the world?

  Hello

  We do 200 ORGANIZATIONAL unit configuration. Where each OU works the same way.

  In the management of orders, we need create transaction Types of command for each ORGANIZATIONAL unit.

  Is it possible to create a Type of Transaction that can be used worldwide (in multiple OUS).

  Appreciate any help on this.

  Thank you

  LS

  Hello

  The answer is simple-no

  Each transaction type is linked to an ORGANIZATIONAL unit design. There is no way that you can change that.

  Kind regards

  Bashar

• Limit values for Transaction Type LOV in ARXTWMAI in apps11i

  Hi everyone,
  
  I want to know if it is possible using the customization feature of the form of apps11i the process of Transaction Type LOV to restrict values in the form of modules of Receivables Transaction.
  
  Is any doc or example regarding this issue.
  
  Thanks in advance
  
  Soni

  Hi Soni,

  I think what you can do is create a new group record query (use the current request of LOV + restrictions apply) and then the group record assing to the transaction of type LOV. That should do the trick, though according to what you mean by 'limiting values LOV' which could become more or less complicated. If the shape is changing somehow the LOV dynamically, that would be too complicated.

  It will be useful.

• Error for the custom "this intercompany Transaction Type is not associated a valid and active CM type' ACT in operation

  We are in the process of implementation ACT on the R12 upgrade instance. When you try to create an outgoing Transaction, we get the following error.

  'This Type of intercompany Transaction is not associated with a line type and the valid memo CM and active'

  It's the Type of Transaction that was created by requiring billing. We checked the missions of customer accounts and 'Intercompany CM' has been assigned to two units of operation concerned. What could be the reason?

  Kind regards

  Miranga

  Found the problem. Date_creation Type of Transaction was after the Date of GL

• Invalid combination of types of Source/Transaction batch

  I am trying to enter a note of credit of the AR.  I get an error message when you select a transaction type with a manual of the package Source.  The message says "Invalid Source and Transaction Type combination lot".  This Type of Transaction has been used with a Source of non-manual batch for the other transactions.  Can still be used with a manual batch Source?  How can I fix this error message.

  Thank you

  Maura

  OK if the message comes from customization, you should review your business requirements and customization.

  Samir

  (Please check this thread as answered if your question is addressed)

• JTA-data-source not RESOURCE_LOCAL-type of transaction and UserTransaction

  Hi all
  
  I'm curious of my way through an application that I help maintain. Some of the details of the implementation of puzzled me, and I could use a validation test. We use Toplink Essentials.
  
  For starters, the persistence.xml - the one and only - specifies a transaction type of RESOURCE_LOCAL. In addition, we have a non - JTA data source.
  
  My understanding is that because what precedes, we get an EntityManager via an EntityManagerFactory, there is a 1:1 correspondence between any given EntityManager and a persistence context (so we would better not more than one EM at a given time, or be very careful as to how we deal with several living at the same time) , and that we are required to use the EntityTransaction API to the demarcation of the transaction limits.
  
  Here's the thing: the app also has a semblance of a "long running operation. It is bounded in the code, through the use of JTA - raising a UserTransaction with JNDI and using begin(), commit() and rollback() on it as required.
  
  I might also add that from a functional point of view the application works obviously.
  
  My question is this: regardless of how the application has achieved its goal, that the JTA UserTransaction does exactly? I can almost see that he does nothing at all.
  
  Thank you
  Arved

  Correct, resouce_local means no JTA.

  ---
  James: http://www.eclipselink.org

• Bill in query type

  Hello!

  I need to separate the ivoices opened by type. (Products / services / Export)

  I did the following query, but I'm stuck:

  Select

  APS.trx_number "Invoice number"

  HCA.account_number "CustomerID"

  bill_p.party_name "name of the customer."

  APS.due_date "due date."

  Current_date - aps.due_date 'Days',

  case

  When CURRENT_DATE - aps.due_date < 0 then ' one time '.

  When CURRENT_DATE - aps.due_date > 0 and CURRENT_DATE - aps.due_date < 30 then 0 '-30'

  When CURRENT_DATE - aps.due_date > 30 and CURRENT_DATE - aps.due_date < 60 then 30-60'

  When CURRENT_DATE - aps.due_date > 60 and CURRENT_DATE - aps.due_date < 90 then 60-90'

  When CURRENT_DATE - aps.due_date > 90 and CURRENT_DATE - aps.due_date < 120 then 90-120'

  else ' 120 +'

  put an end to "Banding."

  APS.amount_due_remaining "amount Due in the currency of origin."

  case

  When aps.invoice_currency_code <>"HUF" then aps.amount_due_remaining * aps.exchange_rate

  of other aps.amount_due_remaining

  'Sum' end Due in HUF,

  APS.invoice_currency_code "currency."

  APS. EXCHANGE_RATE 'rate. '

  Of

  ar_payment_schedules_all aps,

  hz_cust_accounts bill_ca,

  hz_parties bill_p,

  hz_cust_accounts_all hca

  where

  APS.customer_id = bill_ca.cust_account_id

  and aps.class = 'INV '.

  and aps.status = 'OP '.

  and bill_p.party_id = hca.party_id

  and bill_ca.party_id = bill_p.party_id

  Thanks for your help in advance,

  Zsolt

  ra_cust_trx_types_all table will have AR. transaction types

• Assign an IOM custom role to a user in OIM 11 g R2

  Hello world

  I created a role whose type is "IOM roles."

  Given that this role should not be assigned per catalog.

  This is not seen on the catalog.

  When I opened the details of this role, I can't assign this role to a user directly.

  How can I assign this role to a user?

  Thank you.

  Best regards.

  Rather than defining the category as the roles of the IOM, you can set the IS_REQUESTABLE flag to 0 in the table of the CATALOGUE on the IOM scheme that will not display the item in the catalog, but it can still be assigned to the users.

  -xelsysadm

• Source is taken from another Source of Transaction the assets of RMA with SB

  Hello!

  I created a Type of Transaction to have this attached to a Source of the Transaction to the Type of Transaction Standard column and this and that is attached to the Source column of the invoice of the tab Finance installation of Types of transactions for RMA on the order management program.  Whenever I am billing with this transaction type of RMA RMA, the A.R. transaction created has a different Source of what I put. Is there such a thing as a type of transaction 'by default'? What I'm missing here?

  Thank you.

  Jon

  Hello! Thanks for the reply!

  I saw the problem, the entry in the Type default return line in the Types of transactions OM has entered in the Source of the invoice and is selected as the Source of the AR.

  Thank you.

  Jon

• IOM: Reconciliation with the Tables of database applications connector

  Hello!
  
  I am using the Application Connector 9.1.0.5.0 database Tables in OIM 11 g to reconcile the accounts of my target system: MySQL 5.1.37. I followed the steps described in the guide of the connector to create and set up and configure my system target as a reliable source.
  
  The problem is that user accounts are not created in IOM, however, I know the Connector retrieves the information of every user because I can see it in the log messages generated when I run the reconciliation work, so I supossed the problem may be in the "configuration of the connector to modify page", or some time after that.
  
  In addition, I don't know if it's important, but I don't see "User of Type" field "IOM user account data set" to "change the Connector Configuration Page.
  
  A I forgot to do something in the configuration or there's something I've had to do but the steps described in the guide?
  
  Thanks in advance!
  
  Published by: user10857411 on January 11, 2011 16:10
  
  Published by: user10857411 on January 11, 2011 16:12

  SUN IDM is better than the IOM
  Reconciliation process in Sun IDM (newest oracle) is easier to implement than IOM (worst solution identity)

  Saludos cordial Zam

• THE many transactions are transformed and represented in a single OU - R12

  Hello
  
  In R12, how do to THE number of transactions are handled and accounted for in a single ORGANIZATIONAL unit. Certainly, we define an ORGANIZATIONAL unit, a single legal context can be provided, so do not know how this is possible. An example will be very useful.
  
  Thank you and best regards,
  Araujo

  Hello

  While making the configurations such as the type of Transaction and the Source, you will have two UO and THE, you must associate LE1 and LE2 at OU1. Once you enter AR invoice form when you choose the Source of the Transaction, type of legal person will also get dfaulted.

  In the AP, the default value for HIM will fill in THE field, you must choose the LE2 among the list of values for the cost of treatment against LE2.

  Kind regards
  Sridhar

• How to move from records in a procedure with Table Type as a parameter block

  Hello
  
  How can I move all records in a block of PL/SQL procedure with argument of Type Table or Refcursor.
  
  I created a procedure in the backend with a parameter of Type table. Of the form, I want to call this procedure with the argument that ALL of the records in BULK.
  
  Y at - it a simple method for it.
  
  
  Thanks in advance
  
  Rizly

  Rizly,
  I recently put in place a level of forms audit process that uses this method very - package of database, which takes an array of Records as a parameter. Forms 10 G supports this nicely. We have sought to implement this through a set of database triggers (update, insert, delete) but due to our requirements, it was not the best place to do so that we have implemented this in forms.

  Brief history on my form. The main block was based on a table, and the block has been marked NOT can, Insert and Delete. If the user wants to insert, update, or delete a record they clicked on Insert, Update, or Delete button that opens a popup form where they seized a reason Code and a Description of the transaction and then clicked a button Save.

  Here's what I did.
  Database side *.
  1 package database with a Record of PL/SQL and PL/SQL records in the Table variable declared in the Package specification.
  2. create INSERT_?, warning? and DELETE_? package procedures to manage integration, updates and deletions.
  Secondary forms *.
  1 create a table (control) Non-Base with all fields block
  2. create a button that performs a loop on the block and all values assigns to the variable of records in the Table (ToR) forms (typed off the DB package)
  3. pass the ToR to the appropriate database package procedure.

  Here is an example of the code I wrote:
  Database side *.
  Package specifications * (Note: replace with your database schema name) also note, I use PL/SQL Developer with the PLDoc plug-in so I documentation tags in my code.

  CREATE OR REPLACE PACKAGE .Transaction_Log_pkg IS
  -- Package Global Variables
  -- ------------------------
  TYPE rec_T_Log IS RECORD (
      table_name          .transaction_log.table_name%TYPE
     ,trans_type          .transaction_log.trans_type%TYPE
     ,trans_key           .transaction_log.trans_key%TYPE
     ,action              .transaction_log.action%TYPE
     ,column_name         .transaction_log.column_name%TYPE
     ,old_value           .transaction_log.old_value%TYPE
     ,new_value           .transaction_log.new_value%TYPE
     ,trans_date          .transaction_log.trans_date%TYPE
     ,user_id             .transaction_log.user_id%TYPE
     ,reason_code         .transaction_log.reason_code%TYPE
     ,comments            .transaction_log.comments%TYPE
     );
  
  TYPE tbl_T_Log IS TABLE OF rec_T_Log INDEX BY BINARY_INTEGER;
  
     -- Insert_Record --------------------------------------------------------------------------------
     /** Procedure adds "INSERT" audting records in to the CIR.TRANSACTION_LOG table
     %param      p_t_log      TABLE_OF_RECORDS
     %desc       You can pass a single record or a group of records.  Allows you to package up all of
                 the values inserted in a table and send them to the Insert_Record procedure as a
                 group rather than as individual transactions.
     -- ---------------------------------------------------------------------------------------------- */
     PROCEDURE Insert_Record (p_t_log tbl_T_Log );
  
     -- Update_Record --------------------------------------------------------------------------------
     /** Procedure adds a "UPDATE" record(s) in the CIR.TRANSACTION_LOG table
     %param      p_t_log      TABLE_OF_RECORDS
     %desc       You can pass a single record or a group of records if more than one value in a row is updated.
     -- ---------------------------------------------------------------------------------------------- */
     PROCEDURE Update_Record (p_t_log tbl_T_Log );
  
     -- Delete_Record --------------------------------------------------------------------------------
     /** Procedure adds "DELETE" records in to the CIR.TRANSACTION_LOG table
     %param      p_t_log      TABLE_OF_RECORDS
     %desc       You can pass a single record or a group of records.  Allows you to package up all of
                 the values inserted in a table and send them to the Delete_Record procedure as a
                 group rather than as individual transactions.
     -- ---------------------------------------------------------------------------------------------- */
     PROCEDURE Delete_Record (p_t_log tbl_T_Log );
  
  END Transaction_Log_pkg;
  

  Package body *.

  -- Beginning of Package Body -------------------------------------------------------------------------
  -- ---------------------------------------------------------------------------------------------------
  CREATE OR REPLACE PACKAGE BODY .Transaction_Log_pkg AS
     -- Package EXCEPTIONS
     -- ------------------
     null_table              EXCEPTION;
     null_table_name         EXCEPTION;
     null_trans_type         EXCEPTION;
     null_trans_key          EXCEPTION;
     null_action             EXCEPTION;
     null_column_name        EXCEPTION;
     null_value              EXCEPTION;
     null_user_Id            EXCEPTION;
     null_reason_code        EXCEPTION;
     null_comments           EXCEPTION;
  
     -- Package Variables
     -- -----------------
     vErrMsg                 VARCHAR2(1000);
     vSQL                    VARCHAR2(2000);
  
     -- ----------------------------------------------------------------------------------------------
     PROCEDURE Insert_Record (p_t_log tbl_T_Log ) IS
  
     BEGIN
        IF ( NVL(p_t_log.COUNT,0) = 0 ) THEN
           RAISE null_table;
        ELSE
  
           FOR i IN p_t_log.first .. p_t_log.last LOOP
              vSQL := 'INSERT INTO .transaction_log (seq_no,table_name,trans_type,trans_key,action'
                          ||',column_name,old_value,new_value,trans_date,user_id,reason_code,comments)'
                          ||' VALUES (.TRANSACTION_NO_SEQ.nextval';
  
              -- Build Insert Statement
              IF ( p_t_log(i).table_name IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).table_name||'''';
              ELSE
                 RAISE null_table_name;
              END IF;
              IF ( p_t_log(i).trans_type IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).trans_type||'''';
              ELSE
                 RAISE null_trans_type;
              END IF;
              IF ( p_t_log(i).trans_key IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).trans_key||'''';
              ELSE
                 RAISE null_trans_key;
              END IF;
              IF ( p_t_log(i).action IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).action||'''';
              ELSE
                 RAISE null_action;
              END IF;
              IF ( p_t_log(i).column_name IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).column_name||'''';
              ELSE
                 RAISE null_column_name;
              END IF;
              IF ( p_t_log(i).old_value IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).old_value||'''';
              ELSE
                 vSQL := vSQL||',NULL';
              END IF;
              IF ( p_t_log(i).new_value IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).new_value||'''';
              ELSE
                 RAISE null_value;
              END IF;
  
              --transaction_date
              vSQL := vSQL||',sysdate';
  
              IF ( p_t_log(i).user_id IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).user_id||'''';
              ELSE
                 RAISE null_user_id;
              END IF;
              IF ( p_t_log(i).reason_code IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).reason_code||'''';
              ELSE
                 RAISE null_reason_code;
              END IF;
              IF ( p_t_log(i).comments IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).comments||'''';
              ELSE
                 RAISE null_comments;
              END IF;
  
              vSQL := vSQL||')';
  
              dbms_output.put_line('vSQL = '||vSQL);
  
              EXECUTE IMMEDIATE vSQL;
  
              vSQL := NULL;
  
           END LOOP;
  
           -- The COMMIT is intentionally left out to force the calling
           -- application to perform the commit and complies with the
           -- basics of encapsulation.
           -- ---------------------------------------------------------
  
        END IF;
  
     EXCEPTION
        WHEN null_table THEN
           vErrMSg := 'The p_t_log Collection cannot be null!';
           RAISE_APPLICATION_ERROR(-20990,vErrMsg);
        WHEN null_table_name THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20991,vErrMsg);
        WHEN null_trans_type THEN
           vErrMSg := 'Transaction Type cannot be null!';
           RAISE_APPLICATION_ERROR(-20992,vErrMsg);
        WHEN null_trans_key THEN
           vErrMSg := 'Transaction Key cannot be null!';
           RAISE_APPLICATION_ERROR(-20993,vErrMsg);
        WHEN null_action THEN
           vErrMSg := 'Action cannot be null!';
           RAISE_APPLICATION_ERROR(-20994,vErrMsg);
        WHEN null_column_name THEN
           vErrMSg := 'Column Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20995,vErrMsg);
        WHEN null_value THEN
           vErrMSg := 'Value cannot be null!';
           RAISE_APPLICATION_ERROR(-20996,vErrMsg);
        WHEN null_user_Id THEN
           vErrMSg := 'User ID cannot be null!';
           RAISE_APPLICATION_ERROR(-20997,vErrMsg);
        WHEN null_reason_code THEN
           vErrMSg := 'Reason Code cannot be null!';
           RAISE_APPLICATION_ERROR(-20998,vErrMsg);
        WHEN null_comments THEN
           vErrMSg := 'Comments cannot be null!';
           RAISE_APPLICATION_ERROR(-20999,vErrMsg);
     END Insert_Record;
     -- ------------------------------------------------------------------------------------------------
  
     PROCEDURE Update_Record (p_t_log tbl_T_Log ) IS
  
     BEGIN
        IF ( NVL(p_t_log.COUNT,0) = 0 ) THEN
           RAISE null_table;
        ELSE
  
           FOR i IN p_t_log.first .. p_t_log.last LOOP
              vSQL := 'INSERT INTO .transaction_log (seq_no,table_name,trans_type,trans_key,action'
                          ||',column_name,old_value,new_value,trans_date,user_id,reason_code,comments)'
                          ||' VALUES (.TRANSACTION_NO_SEQ.nextval';
  
              -- Build Insert Statement
              IF ( p_t_log(i).table_name IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).table_name||'''';
              ELSE
                 RAISE null_table_name;
              END IF;
              IF ( p_t_log(i).trans_type IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).trans_type||'''';
              ELSE
                 RAISE null_trans_type;
              END IF;
              IF ( p_t_log(i).trans_key IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).trans_key||'''';
              ELSE
                 RAISE null_trans_key;
              END IF;
              IF ( p_t_log(i).action IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).action||'''';
              ELSE
                 RAISE null_action;
              END IF;
              IF ( p_t_log(i).column_name IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).column_name||'''';
              ELSE
                 RAISE null_column_name;
              END IF;
              IF ( p_t_log(i).old_value IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).old_value||'''';
              ELSE
                 vSQL := vSQL||',NULL';
              END IF;
              IF ( p_t_log(i).new_value IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).new_value||'''';
              ELSE
                 RAISE null_value;
              END IF;
  
              --transaction_date
              vSQL := vSQL||',sysdate';
  
              IF ( p_t_log(i).user_id IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).user_id||'''';
              ELSE
                 RAISE null_user_id;
              END IF;
              IF ( p_t_log(i).reason_code IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).reason_code||'''';
              ELSE
                 RAISE null_reason_code;
              END IF;
              IF ( p_t_log(i).comments IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).comments||'''';
              ELSE
                 RAISE null_comments;
              END IF;
  
              vSQL := vSQL||')';
  
              dbms_output.put_line('vSQL = '||vSQL);
  
              EXECUTE IMMEDIATE vSQL;
  
              vSQL := NULL;
  
           END LOOP;
  
           -- The COMMIT is intentionally left out to force the calling
           -- application to perform the commit and complies with the
           -- basics of encapsulation.
           -- ---------------------------------------------------------
  
        END IF;
  
     EXCEPTION
        WHEN null_table THEN
           vErrMSg := 'The p_t_log Collection cannot be null!';
           RAISE_APPLICATION_ERROR(-20990,vErrMsg);
        WHEN null_table_name THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20991,vErrMsg);
        WHEN null_trans_type THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20992,vErrMsg);
        WHEN null_trans_key THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20993,vErrMsg);
        WHEN null_action THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20994,vErrMsg);
        WHEN null_column_name THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20995,vErrMsg);
        WHEN null_value THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20996,vErrMsg);
        WHEN null_user_Id THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20997,vErrMsg);
        WHEN null_reason_code THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20998,vErrMsg);
        WHEN null_comments THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20999,vErrMsg);
     END Update_Record;
     -- ------------------------------------------------------------------------------------------------
  
     PROCEDURE Delete_Record (p_t_log tbl_T_Log ) IS
  
     BEGIN
        IF ( NVL(p_t_log.COUNT,0) = 0 ) THEN
           RAISE null_table;
        ELSE
  
           FOR i IN p_t_log.first .. p_t_log.last LOOP
              vSQL := 'INSERT INTO .transaction_log (seq_no,table_name,trans_type,trans_key,action'
                          ||',column_name,old_value,new_value,trans_date,user_id,reason_code,comments)'
                          ||' VALUES (.TRANSACTION_NO_SEQ.nextval';
  
              -- Build Insert Statement
              IF ( p_t_log(i).table_name IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).table_name||'''';
              ELSE
                 RAISE null_table_name;
              END IF;
              IF ( p_t_log(i).trans_type IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).trans_type||'''';
              ELSE
                 RAISE null_trans_type;
              END IF;
              IF ( p_t_log(i).trans_key IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).trans_key||'''';
              ELSE
                 RAISE null_trans_key;
              END IF;
              IF ( p_t_log(i).action IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).action||'''';
              ELSE
                 RAISE null_action;
              END IF;
              IF ( p_t_log(i).column_name IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).column_name||'''';
              ELSE
                 RAISE null_column_name;
              END IF;
              IF ( p_t_log(i).old_value IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).old_value||'''';
              ELSE
                 vSQL := vSQL||',NULL';
              END IF;
              IF ( p_t_log(i).new_value IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).new_value||'''';
              ELSE
                 RAISE null_value;
              END IF;
  
              --transaction_date
              vSQL := vSQL||',sysdate';
  
              IF ( p_t_log(i).user_id IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).user_id||'''';
              ELSE
                 RAISE null_user_id;
              END IF;
              IF ( p_t_log(i).reason_code IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).reason_code||'''';
              ELSE
                 RAISE null_reason_code;
              END IF;
              IF ( p_t_log(i).comments IS NOT NULL ) THEN
                 vSQL := vSQL||','''||p_t_log(i).comments||'''';
              ELSE
                 RAISE null_comments;
              END IF;
  
              vSQL := vSQL||')';
  
              dbms_output.put_line('vSQL = '||vSQL);
  
              EXECUTE IMMEDIATE vSQL;
  
              vSQL := NULL;
  
           END LOOP;
  
           -- The COMMIT is intentionally left out to force the calling
           -- application to perform the commit and complies with the
           -- basics of encapsulation.
           -- ---------------------------------------------------------
  
        END IF;
  
     EXCEPTION
        WHEN null_table THEN
           vErrMSg := 'The p_t_log Collection cannot be null!';
           RAISE_APPLICATION_ERROR(-20990,vErrMsg);
        WHEN null_table_name THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20991,vErrMsg);
        WHEN null_trans_type THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20992,vErrMsg);
        WHEN null_trans_key THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20993,vErrMsg);
        WHEN null_action THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20994,vErrMsg);
        WHEN null_column_name THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20995,vErrMsg);
        WHEN null_value THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20996,vErrMsg);
        WHEN null_user_Id THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20997,vErrMsg);
        WHEN null_reason_code THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20998,vErrMsg);
        WHEN null_comments THEN
           vErrMSg := 'Table Name cannot be null!';
           RAISE_APPLICATION_ERROR(-20999,vErrMsg);
     END Delete_Record;
     -- ------------------------------------------------------------------------------------------------
  
  END Transaction_Log_pkg; -----------------------------------------------------------------------------
  -- ---------------------------------------------------------------------------------------------------
  

  Secondary forms * (all this coding was limited to the Insert, update or delete buttons.) The following example is the Insert button)

  /* When-Button-Pressed Trigger */
  DECLARE
       vBlockName     VARCHAR2(20) := 'REPORT_CATEGORIES';
       vBlockItem     VARCHAR2(61);
       vCurrItem      VARCHAR2(61);
       nRecCnt        NUMBER := 1;
  
       /* Here is where you create your Forms Variable TYPEd off the Package Table of Records (ToR) */
       /* Since it is a table of records, you could easily add multiple rows to the ToR if your form uses a multi-record block */
       p_tlog         cir.transaction_log_pkg.tbl_t_log;    
  
  BEGIN
       vCurrItem := vBlockName||'.'||Get_Block_Property(vBlockName,FIRST_ITEM);
  
       Go_Item(vCurrItem);
  
       -- 1. Endure each field if populated.
          -- 2. Check for Duplicates (Handled in W-V-I)
  
       IF ( Name_In(:system.Cursor_Item) IS NULL ) THEN
            --Fail the form at the field that is NULL
            send_alert.msg('s','All fields are required.  Please enter a unique value.');
            RAISE Form_Trigger_Failure;
       END IF;
  
       WHILE ( vCurrItem IS NOT NULL ) LOOP
            vBlockItem := :system.cursor_item;
  
            -- Loop through the block and CALL Insert_Record for each Block Item.
            /* 1 */ p_tlog(nRecCnt).table_name := vBlockName;
            /* 2 */ p_tlog(nRecCnt).trans_type := Name_In(vBlockName||'.CAT_TYPE');
            /* 3 */ p_tlog(nRecCnt).trans_key := Name_In(vBlockName||'.ID');
            /* 4 */ p_tlog(nRecCnt).action := 'INSERT';
            /* 5 */ p_tlog(nRecCnt).column_name := substr(vBlockItem,instr(vBlockItem,'.')+1,length(vBlockItem));
            /* 6 */ p_tlog(nRecCnt).old_value := NULL;
            /* 7 */ p_tlog(nRecCnt).new_value := Name_In(vBlockItem);
            /* 8 */ p_tlog(nRecCnt).trans_date := sysdate;
            /* 9 */ p_tlog(nRecCnt).user_id := :Global.userid;
            /*10 */ p_tlog(nRecCnt).reason_code := Name_In(vBlockName||'.REASON_CODE');
            /*11 */ p_tlog(nRecCnt).comments := Name_In(vBlockName||'.COMMENTS');
  
            vCurrItem := Get_Item_Property(vBlockItem,NEXTITEM);
            next_item;
            nRecCnt := nRecCnt + 1;
       END LOOP;
  
       -- 3. Insert
    -- Call TRANSACTION_LOG_PKG.Insert_Record
    -- --------------------------------------
    .transaction_log_pkg.insert_record(p_t_log => p_tlog);
  
       -- 4. Commit
       Commit;  
  
       -- 5. Clear Block
       Clear_Block(Ask_Commit);
  
       -- 6. Close Form
       Hide_Window('REPORT_CATEGORIES');
       -- 7. ReQuery RC_DISP Block
       Go_Block('REPORT_CATEGORIES_DISP');
       Clear_Block(No_Validate);
       Execute_Query;
       -- 8. Done
  END;
  

  I knew not when I started this process of forms if she was going to work because I tried to do something similar to this when I was working with Forms 6i and Oracle Enterprise Business Suite and Forms 6i supported not Ref Cursor and Table of documents very well so I didn't know at first if it would work. Search in forms documentation, I found that Forms 10 g has supported this type of functionality and this process works very well and it was surprisingly fast - at least in my usage, it is very fast. :)

  I hope this helps.
  Craig...

  If I or someone elses answer was useful, please mark accordingly

• Creating a new type of order in OM

  Hi you
  I need to create a new type of order in the order management.
  Once the order is booked, the inventory must decrease automatically without going through the "release Sales Orders', the 'Transact move orders' and 'shipping Transactions.
  After the closure of the State of the line, I can generate the invoice for the order through the program master autoinvoice on receivables.
  Can someone explain to me how to create such a command?
  Thank you.
  
  Kind regards
  Mustapha.

  Your condition looks good with the behavior of the stream line Bill only with the Interface of the inventory.
  just create a normal header and transaction type of line and when assigning the flow line to the header, choose 'flow line - generic, Bill only with the inventory Interface' flow.
  This should get your order related to interface autoinvoice table and important operations interface.
  Make sure that you enable your material handler Interface to inventory transaction manager to reduce the quantity in stock

  Thank you

• Creating a new type of order

  Hi you
  I need to create a new type of order in the order management.
  Once the command type is reserved, the inventory is expected to decrease automatically and invoice can be created using the program master autoinvoice claims.
  Can someone help me how to do?
  THX.
  
  Kind regards
  Mustapha
  
  Published by: user10619126 on August 20, 2009 22:50
  
  Published by: user10619126 on August 20, 2009 22:51

  Please follow these steps:
  -Set up a transaction type of line
  -Set up a transaction type of header with a stream of realization as "Order Flow" - generic. Complete price list, the operation of line type defined in the previous step
  -In the transaction of the header, type assign line rate as "line flow - generic, Bill only with the Interface of inventory".
  As soon as the order is the line book rate trigger interface of invoice for the line of SO.

  -Create the sequence of documents for the type of transaction header
  -Assign the document for the type of transaction header
  -Create a command using the TT header and add a line for a storable element. Here, it should be noted that according to the type of control used, as appropriate, following should decide.

  _If the question isn't under control of review/batch/Locator, enter in the subinventory on line (Shipping tab > menu file > show field). If the item is under review/batch/Locator control, use the booking form to book it first (Tools menu > Scheduling > booking details) _.
  -Book order
  -Query the command and check the status of the line. Normally it should be filled as "Bill Interface - Line" is postponed.

  -In INV, check that there is no current record in the Interface open transactions (INV > Transactions > open transaction Interface). Query using error in the vacuum indicator and the adequacy of the Organization Code. Can use dates as well

  -If records in open transaction Interface with status as "Background" then in INV make sure that this ' important ' Manager is active (INV > Setup > Transactions > Management Interface). Otherwise, you need to run the "important Operation" in the Tools menu to make it active.
  -INV "Meaningful Transactions" verify that the transaction number of the sales order was created
  -AR use automotive invoice to create the invoice.

  Thank you
  'Ve

• AR lack commitment Transaction

  11.5.10
  
  Trying to setup within the AR transaction types, when I select class engagement is not on the list. I chargeback, credit notes, debit memo, deposit, guarantee, but commitment is missing.
  
  Y at - it something wrong with my ar configuration or do I have to activate the class somewhere that I'm not aware of any action.
  
  Also, how you change the default in AR country when setting up of new customers and address of country keeps failing in the USA, I wanted to its default value in the UK.

  Hello

  Default country is set in "Receivables--> Setup--> System--> System Options" on the tab "miscellaneous". I don't know if you can change this value once the system options are defined for an operating unit.

  You can also replace this value at the level of responsibility/user setting profile country default options * in System Manager > profile > system.

  Kind regards.