Monday, 17 September 2012

Sample script to insert secondary price lists to the primary price list

Sample script to insert secondary price lists to the primary price list


Sample script to insert secondary price lists to the primary price list with
 mandatory columns to be populated in the following bulk loader interface tables:
 QP_INTERFACE_LIST_HEADERS
 QP_INTERFACE_QUALIFIERS

 This script assumes that both primary price list and the secondary price lists
 have been created already and exist. This script populates
 * QP_INTERFACE_LIST_HEADERS table with ORIG_SYS_HEADER_REF of the secondary price list.
 * QP_INTERFACE_QUALIFIERS table with primary price list Name in
      QUALIFIER_ATTR_VALUE_CODE. Alternatively populate primary price list header id in
      QUALIFIER_ATTRIBUTE_CODE.




/* Attach two secondary price lists to the Sample_BLK_PL price list.*/
/* Attach Secondary Price List 1 */
INSERT INTO QP_INTERFACE_LIST_HEADERS (
ORIG_SYS_HEADER_REF,
LIST_TYPE_CODE,
LAST_UPDATED_BY,
LAST_UPDATE_DATE,
INTERFACE_ACTION_CODE,
PROCESS_FLAG,
PROCESS_STATUS_FLAG,
REQUEST_ID,
PROCESS_ID
) VALUES (
'SAMPLE_HEADER11',        /* ORIG_SYS_HEADER_REF of the secondary price list to be attached.*/
'PRL',                    /* List Type Code */
1318,                     /* Last Updated By */
sysdate,                  /* Last Update Date */
'UPDATE',                 /* Interface Action Code. The possible values are INSERT/UPDATE/DELETE.*/
'Y',                      /* Process Flag */
'P',                      /* Process Status Flag */
NULL,                     /* Request Id */
999                       /* Process Id */
);

INSERT INTO QP_INTERFACE_QUALIFIERS (
ORIG_SYS_QUALIFIER_REF,
ORIG_SYS_HEADER_REF,
QUALIFIER_GROUPING_NO,
QUALIFIER_CONTEXT,
QUALIFIER_ATTRIBUTE_CODE,
QUALIFIER_ATTR_VALUE_CODE,
COMPARISON_OPERATOR_CODE,
QUALIFIER_PRECEDENCE,
INTERFACE_ACTION_CODE,
PROCESS_FLAG,
PROCESS_STATUS_FLAG,
PROCESS_ID
) VALUES (
'SAMPLE_QUAL11',          /* ORIG_SYS_QUALIFIER_REF */
'SAMPLE_HEADER11',        /* ORIG_SYS_HEADER_REF of the secondary price list.*/
-1,                       /* Qualifier Grouping No */
'MODLIST',                /* Qualifier Context */
'PRICE_LIST',             /* Qualifier Attribute Code */
'Sample_BLK_PL',          /* Qualifier Attribute Value Code. Primary Price List Name.*/
'=',                      /* Comparison Operator Code */
100,                      /* Qualifier Precedence */
'INSERT',                 /* Interface Action Code. The possible values are INSERT/UPDATE/DELETE.*/
'Y',                      /* Process Flag */
'P',                      /* Process Status Flag */
999                       /* Process Id */
);

/* Attach Secondary Price List 2.*/
INSERT INTO QP_INTERFACE_LIST_HEADERS (
ORIG_SYS_HEADER_REF,
LIST_TYPE_CODE,
LAST_UPDATED_BY,
LAST_UPDATE_DATE,
INTERFACE_ACTION_CODE,
PROCESS_FLAG,
PROCESS_STATUS_FLAG,
REQUEST_ID,
PROCESS_ID
) VALUES (
'SAMPLE_HEADER2012',        /* ORIG_SYS_HEADER_REF of the secondary price list.*/
'PRL',                    /* List Type Code */
1318,                     /* Last Updated By */
sysdate,                  /* Last Update Date */
'UPDATE',                 /* Interface Action Code. The possible values are INSERT/UPDATE/DELETE.*/
'Y',                      /* Process Flag */
'P',                      /* Process Status Flag */
NULL,                     /* Request Id */
999                       /* Process Id */
);

INSERT INTO QP_INTERFACE_QUALIFIERS (
ORIG_SYS_QUALIFIER_REF,
ORIG_SYS_HEADER_REF,
QUALIFIER_GROUPING_NO,
QUALIFIER_CONTEXT,
QUALIFIER_ATTRIBUTE_CODE,
QUALIFIER_ATTR_VALUE_CODE,
COMPARISON_OPERATOR_CODE,
QUALIFIER_PRECEDENCE,
INTERFACE_ACTION_CODE,
PROCESS_FLAG,
PROCESS_STATUS_FLAG,
PROCESS_ID
) VALUES (
'SAMPLE_QUALIFIER',          /* ORIG_SYS_QUALIFIER_REF */
'SAMPLE_HEADER2012',        /* ORIG_SYS_HEADER_REF of the secondary price list.*/
-1,                       /* Qualifier Grouping No */
'MODLIST',                /* Qualifier Context */
'PRICE_LIST',             /* Qualifier Attribute Code */
'Sample_BLK_PL',          /* Qualifier Attribute Value Code. Primary Price List Name.*/
'=',                      /* Comparison Operator Code */
100,                      /* Qualifier Precedence */
'INSERT',                 /* Interface Action Code. The possible values are INSERT/UPDATE/DELETE.*/
'Y',                      /* Process Flag */
'P',                      /* Process Status Flag */
999                       /* Process Id */                      
);

COMMIT;
EXIT;

Thursday, 13 September 2012

OM faqs

OM Questions  1) What are the Base Tables and Interface Tables for Order Management?  Interface Tables : OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL  OE_PRICE_ADJS_IFACE_ALL, OE_ACTIONS_IFACE_ALL  OE_CREDITS_IFACE_ALL (Order holds like credit check holds etc)  Base Tables : OE_ORDER_HEADERS_ALL: Order Header Information  OE_ORDER_LINES_ALL: Items Information  OE_PRICE_ADJUSTMENTS: Discounts Information  OE_SALES_CREDITS: Sales Representative Credits.  Shipping Tables :WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERIES.    2) What are the Base Tables and Interface Tables for Order Management?  Interface Tables : OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL  OE_PRICE_ADJS_IFACE_ALL, OE_ACTIONS_IFACE_ALL  OE_CREDITS_IFACE_ALL (Order holds like credit check holds etc)  Base Tables : OE_ORDER_HEADERS_ALL: Order Header Information  OE_ORDER_LINES_ALL: Items Information  OE_PRICE_ADJUSTMENTS: Discounts Information  OE_SALES_CREDITS: Sales Representative Credits.  Shipping Tables :WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERIES.    3) What is Order Import and What are the Setup's involved in Order Import?  A) Order Import is an open interface that consists of open interface tables and a set of API's. It imports New, updated, or changed sales orders from other applications such as Legacy systems. Order Import features include validations, Defaulting, Processing Constraints checks, Applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting orders from the OM base tables. Order management checks all the data during the import process to ensure its validity with OM. Valid Transactions are then converted into orders with lines, reservations ,price adjustments, and sales credits in the OM base tables.  B) Setups:  · Setup every aspect of order management that we want to use with imported orders, including customers, pricing, items, and bills.  · Define and enable the order import sources using the order import source window.    4) Explain the Order Cycle?  i) Enter the Sales Order  ii) Book the Sales Order(SO will not be processed until booked(Inventory confirmation))  iii) Release sales order(Pickslip Report is generated and Deliveries are created)  (Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.  iv) Transaction Move Order (creates reservations determines the source and transfers the inventory into the staging areas)  v) Launch Pick Release (  vi) Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))  vii) Auto invoice and closed    5) Explain the Order to Cash Flow?  I. Enter the Sales Order  II. Book the Sales Order(SO will not be processed until booked(Inventory confirmation))  III. Release sales order(Pickslip Report is generated and Deliveries are created)  (Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.  IV. Transaction Move Order (Selects the serial number of the product which has to be moved/ shipped)  V. Launch Pick Release  VI. Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))  VII. AutoInvoice (Creation of Invoice in Accounts Receivable Module)  VIII.Autolockbox ( Appling Receipts to Invoices In AR)  IX. Transfer to General Ledger ( Populates GL interface tables)  X. Journal Import ( Populates GL base tables)  XI. Posting ( Account Balances Updated).    5. What are the Process Constraints?  A. Process Constraints prevent users from adding updating, deleting, splitting lines and canceling order or return information beyond certain points in the order cycle. Oracle has provided certain process constraints which prevent data integrity violations.  Process constraints are defined for entities and attributes. Entities include regions on the sales order window such as order, line, order price adjustments, line price adjustments, order sales credits and line sales credits. Attributes include individual fields (of a particular entity) such as warehouse, shit to location, or agreement.    6. What are Validation Templates?  A) Validation Templates are used to define the validation conditions in process constraints. A validation template names a conditions and defines the semantic of how to validate that condition. These are used in processing constraints framework to specify the constraining conditions for a given constraint. These conditions are based on  1 Where the entity is in its work flow.  2 The state of attributes on an entity.  3 Any other validation condition that cannot be modeled using the above condition.    7. What are different types of Holds?  1 GSA(General Services Administration) Violation Hold(Ensures that specific customers always get better pricing for example Govt. Customers)  2 Credit Checking Hold( Used for credit checking feature Ex: Credit Limit)  3 Configurator Validation Hold ( Cause: If we invalidate a configuration after booking)    8. What is Document Sequence?  A) Document sequence is defined to automatically generate numbers for your orders or returns as you enter them. Single / multiple document sequences can be defined for different order types.  Document sequences can be defined as three types Automatic (Does not ensure that the numbers are contiguous), Gapless (Ensures that the numbering is contiguous), Manual Numbering. Order Management validates that the number specified is unique for order type.    9. What are Defaulting Rules?  A) A defaulting rule is a value that OM automatically places in an order field of the sales order window. Defaulting rules reduce the amount of information one must enter. A defaulting rule is a collection of defaulting sources for objects and their attributes.  It involves the following steps  1 Defaulting Conditions - Conditions for Defaulting  2 Sequence – Priority for search  3 Source – Entity ,Attribute, Value  4 Defaulting source/Value    10. When an order cannot be cancelled?  A) An order cannot be cancelled if,  1 It has been closed  2 It has already been cancelled  3 A work order is open for an ATO line  4 Any part of the line has been shipped or invoiced  5 Any return line has been returned or credited.    11. When an order cannot be deleted?  A) you cannot delete an order line until there is a need for recording reason.    12. What is order type?  A) An order type is the classification of order. It controls the order work flow activity, order number sequence, credit check point and transaction type. Order Type is associated to a work flow process which drives the processing of the order.    13. What are primary and secondary price lists?  A) Every order is associated to a price list as each item on the order ought to have a price. A price list is contains basic list information and one or more pricing lines, pricing attributes, qualifiers, and secondary price lists. The price list that is primarily associated to an order is termed as Primary price list.  The pricing engine uses a Secondary Price list if it cannot determine the price of the item ordered in the Primary price list.    14. What is pick slip? Types?  A) It is an internal shipping document that pickers use to locate items to ship for an order.  1 Standard Pick Slip – Each order will have its own pick slip with in each picking batch.  2 Consolidated Pickslip – Pick slip will have all the orders released in the each picking batch.    15. What is packing slip?  A) It is an external shipping document that accompanies the shipment itemizing the contents of the shipment.    16. What are picking rules?  A) Picking rules define the sources and prioritization of sub inventories, lots, revisions and locators when the item is pick released by order management. They are user defined set of rules to define the priorities order management must use when picking items from finished goods inventory to ship to a customer.    17. Where do you find the order status column?  A) In the base tables, Order Status is maintained both at the header and line level. The field that maintains the Order status is FLOW_STATUS_CODE. This field is available in both the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.    18. When the order import program is run it validates and the errors occurred can be seen in?A) Responsibility: Order Management Super User  Navigation: Order, Returns > Import Orders > Corrections

--


Scheduling the Concurrent program

Scheduling the Concurrent program
We can submit the Concurrent program future date or date by using 
the schedule button in SRS window
As soon as possible: This is default option whenever we submit the
 request it will submit the as soon as possible
Once: It will submit the rest only once for future date.
Periodically: WE can specify the from_date and to_date to submit 
program periodically no of. Days months, hours, minutes and so on.
Specific Days: If we want submit concurrent program in the specific 
days we write select this option
Save this Schedule: This check box will be used to save the schedule 
and apply same schedule to other concurrent programs 
by selecting the button called 'Apply save schedule'
NOTE: After schedule the Concurrent program we can also 
cancel by selecting the cancel button.

--


Monday, 10 September 2012

HOW TO COMPILE AND OPEN ORACLE FORMS IN UNIX:


HOW TO COMPILE AND OPEN ORACLE FORMS IN UNIX:

Below are the commands to open and compile Oracle Forms in UNIX.

FORMS6I:
to open- f60desm
to compile/generate - f60genm



FORMS 9I:
to open - frmbld
to compile/generate – frmcmp



f90genm userid=scott/tiger@bs817 batch=yes module=$i module_type=form

compile_all=yes window_state=minimize

For 10gR1 = forms 9.0.4.x, you can use f90gen also

For 10gR2 = forms 10.x, you can use frmcmp.sh or frmcmp_batch.sh


Demo script (Linux) – Compiling forms application


frmcmp_batch.sh Module_type=LIBRARY Module=$ff userid=username/password@database upgrade=yes batch=yes window_state=minimize compile_all=yes

--


Value Sets

Dependent value Set:  ====================  This is another LOV which will be used to displays the   list of values which are depending on the previous parameter value.    Before going to create Dependent first we have to create Independent  then we have to create Dependent  First parameter will be Independent  Second parameter will be Dependent.    Note:Without Independent we can not create Dependent Value set.    Country	IND  	        US  	        UK  City   Banglore	Chennai 	Delhi	 Mumbai  Pune         Chikago  California      Anderson         London   Hungrant    1)We have to create Independent value set and enter the values.  2)Create Dependent value set attach independent and then enter values.      Job	  Manager  	  Developer  	  Programmer    Position   Delivery Manager   Project manager Financce manager  	   Software Developer Test Developer  	   Trainee  Fresher    Table Value set :    Table value set will be used to displays the list of values from the  oracle apps base tables.  we have to give the table name and column name which will automatically  displays the values.    Note: If values are not stored in the database table then we have to         go for Independent  value set.        If values are there in the table then we will create table value        set.    1.Open the value set form Select  validation type as table select the     button called Edit Information enter table name and column name     in the value field   2.Use where/Order By clause to implement Where/Order By clause.  3.Use Additional Columns field to displays extra columns for reference    purpose.  4.Use the ID column to pass the ineternally other columns data     for ex displaying username to the user and pass userID internally.  5.If multiple tables are required then enter the table names in the     table name field with alias name and enter the Join Condition in the    Where clause field.    6.If we know the table name we can find the Table application name from    Application Developer responsibility   Application Developer => Application => Database => table   Query the records based on the table Name.      Translated Independent and Translated Dependent:  ================================================  Both  value sets will work like Independent and Dependent value sets  will be used to displays the transalation values which will be enabled  if there is multilanguage implementation.    Special and Pair:  =================  Both Value sets will be used to displays the Flexfield data as LOV to  the User.  


--


Tuesday, 4 September 2012

R12 SLA Tables join conditions to AP, AR, INV,Payments and Receiving

R12 SLA Tables connection to AP, AR, INV,Payments, Receiving


R12 SLA (Sub ledger Accounting)


1) All accounting performed before transfer to the GL. Accounting data generated and stored in "Accounting Events" tables prior to transfer to GL


2) Run "Create Accounting" to populate accounting events (SLA) tables. User can "View Accounting" only after "Create Accounting" is run. Create Accounting process

Applies accounting rules

Loads SLA tables, GL tables

Creates detailed data per accounting rules, stores in SLA "distribution links" table


3) Below are the key tables for SLA in R12


XLA_AE_HEADERS xah

XLA_AE_LINES xal

XLA_TRANSACTION_ENTITIES xte

XLA_DISTRIBUTION_LINKS xdl

GL_IMPORT_REFERENCES gir


Below are the possible joins between these XLA Tables


xah.ae_header_id = xal.ae_header_id

xah.application_id = xal.application_id

xal.application_id = xte.application_id

xte.application_id = xdl.application_id

xah.entity_id = xte.entity_id

xah.ae_header_id = xdl.ae_header_id

xah.event_id = xdl.event_id

xal.gl_sl_link_id = gir.gl_sl_link_id

xal.gl_sl_link_table = gir.gl_sl_link_table

xah.application_id = (Different value based on Module)


xte.entity_code =

'TRANSACTIONS' or

'RECEIPTS' or

'ADJUSTMENTS' or

'PURCHASE_ORDER' or

'AP_INVOICES' or

'AP_PAYMENTS' or

'MTL_ACCOUNTING_EVENTS' or

'WIP_ACCOUNTING_EVENTS'


xte.source_id_int_1 =

'INVOICE_ID' or

'CHECK_ID' or

'TRX_NUMBER'


XLA_DISTRIBUTION_LINKS table join based on Source Distribution Types


xdl.source_distribution_type = 'AP_PMT_DIST'

and xdl.source_distribution_id_num_1 = AP_PAYMENT_HIST_DISTS.payment_hist_dist_id

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

xdl.source_distribution_type = 'AP_INV_DIST'

and xdl.source_distribution_id_num_1 = AP_INVOICE_DISTRIBUTIONS_ALL.invoice_distribution_id

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

xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'

and xdl.source_distribution_id_num_1 = AR_DISTRIBUTIONS_ALL.line_id

and AR_DISTRIBUTIONS_ALL.source_id = AR_RECEIVABLE_APPLICATIONS_ALL.receivable_application_id

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

xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL'

and xdl.source_distribution_id_num_1 = RA_CUST_TRX_LINE_GL_DIST_ALL.cust_trx_line_gl_dist_id

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

xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS'

and xdl.source_distribution_id_num_1 = MTL_TRANSACTION_ACCOUNTS.inv_sub_ledger_id

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

xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS'

and xdl.source_distribution_id_num_1 = WIP_TRANSACTION_ACCOUNTS.wip_sub_ledger_id

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

xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER'

and xdl.source_distribution_id_num_1 = RCV_RECEIVING_SUB_LEDGER.rcv_sub_ledger_id



--